IPv6, MPLS IPv6 History Next generation IP (AKA IPng) Intended - - PowerPoint PPT Presentation

ipv6 mpls ipv6
SMART_READER_LITE
LIVE PREVIEW

IPv6, MPLS IPv6 History Next generation IP (AKA IPng) Intended - - PowerPoint PPT Presentation

IPv6, MPLS IPv6 History Next generation IP (AKA IPng) Intended to extend address space and routing limitations of IPv4 Requires header change Attempted to include everything new in one change IETF moderated Based


slide-1
SLIDE 1

IPv6, MPLS

slide-2
SLIDE 2

IPv6

 History

Next generation IP (AKA IPng)

Intended to extend address space and routing limitations of IPv4

Requires header change

Attempted to include everything new in one change

IETF moderated

Based on Simple Internet Protocol Plus (SIPP)

slide-3
SLIDE 3

IPv6

Wish list

128-bit addresses

Multicast traffic

Mobility

Real-time traffic/quality of service guarantees

Authentication and security

Autoconfiguration for local IP addresses

End-to-end fragmentation

Protocol extensions

Smooth transition!

Note

Many of these functionalities have been retrofit into IPv4

slide-4
SLIDE 4

IPv6 Addresses

128-bit

3.4 x 1038 addresses (as compared to 4 x 109)

Classless addressing/routing (similar to CIDR)

Address notation

String of eight 16-bit hex values separated by colons

5CFA:0002:0000:0000:CF07:1234:5678:FFCD

Set of contiguous 0’s can be elided

5CFA:0002::CF07:1234:5678:FFCD

Address assignment

Provider-based

geographic

slide-5
SLIDE 5

IPv6 Addresses

128-bit

3.4 x 1038 addresses (as compared to 4 x 109)

Classless addressing/routing (similar to CIDR)

Address notation

String of eight 16-bit hex values separated by colons

5CFA:0002:0000:0000:CF07:1234:5678:FFCD

Set of contiguous 0’s can be elided

5CFA:0002::CF07:1234:5678:FFCD

Address assignment

Provider-based

geographic

010 Region ID Provider ID Subscriber ID Subnet Host 3 m n

  • p

125-m-n-o-p

slide-6
SLIDE 6

IPv6

unassigned Other Multicast address 1111 1111 Site local address 1111 1110 11 Link local address 1111 1110 10 Geographic multicast 100 Provider-based unicast 010 Novell IPX allocation 0000 010 ISO NSAP (Network Service Point) Allocation 0000 0001 Reserved (includes transition addresses) 0000 0000 Address type Prefix

slide-7
SLIDE 7

IPv4 Packet Format

20 Byte minimum

Mandatory fields are not always used

e.g. fragmentation

Options are an unordered list of (name, value) pairs

slide-8
SLIDE 8

IPv4 Packet Format

20 Byte minimum

Mandatory fields are not always used

e.g. fragmentation

Options are an unordered list of (name, value) pairs

TTL source address destination address

  • ptions (variable)

version length

  • ffset

ident 8 16 31 hdr len TOS flags checksum protocol pad (variable)

slide-9
SLIDE 9

IPv6 Packet Format

destination address word 4

  • ptions (variable number, usually fixed length)

version flow label hop limit payload length 8 16 31 priority next header source address word 1 source address word 2 source address word 3 source address word 4 destination address word 1 destination address word 2 destination address word 3

slide-10
SLIDE 10

IPv6 Packet Format

40 Byte minimum

Mandatory fields (almost) always used

Strict order on options reduces processing time

No need to parse irrelevant options

slide-11
SLIDE 11

IPv6 Packet Format

40 Byte minimum

Mandatory fields (almost) always used

Strict order on options reduces processing time

No need to parse irrelevant options

  • ptions (variable number, usually fixed length)

version flow label hop limit payload length 8 16 31 priority next header source address 4 words destination address 4 words

slide-12
SLIDE 12

IPv6 Packet Format

Version

6

Priority and Flow Label

Support service guarantees

Allow “fair” bandwidth allocation

Payload Length

Header not included

Next Header

Combines options and protocol

Linked list of options

Ends with higher-level protocol header (e.g. TCP)

Hop Limit

TTL renamed to match usage

slide-13
SLIDE 13

IPv6 Extension Headers

Must appear in order

Hop-by-hop options

Miscellaneous information for routers

Routing

Full/partial route to follow

Fragmentation

IP fragmentation info

Authentication

Sender identification

Encrypted security payload

Information about contents

Destination options

Information for destination

slide-14
SLIDE 14

IPv6 Extension Headers

 Hop-by-Hop extension

Length is in bytes beyond mandatory 8

Jumbogram option (packet longer than 65,535 bytes)

Payload length in main header set to 0

slide-15
SLIDE 15

IPv6 Extension Headers

 Hop-by-Hop extension

Length is in bytes beyond mandatory 8

next header type value 8 16 31 length

Jumbogram option (packet longer than 65,535 bytes)

Payload length in main header set to 0

slide-16
SLIDE 16

IPv6 Extension Headers

 Hop-by-Hop extension

Length is in bytes beyond mandatory 8

next header type value 8 16 31 length next header 194 Payload length in bytes 8 16 31

Jumbogram option (packet longer than 65,535 bytes)

Payload length in main header set to 0

slide-17
SLIDE 17

IPv6 Extension Headers

Routing extension

Up to 24 “anycast” addresses target AS’s/providers

Next address tracks current target

Strict routing requires direct link

Loose routing allows intermediate nodes

next header # of addresses strict/loose routing bitmap 8 16 31 next address 1 – 24 addresses

slide-18
SLIDE 18

IPv6 Extension Headers

 Fragmentation extension

 Similar to IPv4 fragmentation

 13-bit offset  Last fragment mark (M)

 Larger fragment identification field

next header

  • ffset

ident 8 16 31 reserved reserved M

slide-19
SLIDE 19

IPv6 Extension Headers

Authentication extension

Designed to be very flexible

Includes

Security parameters index (SPI)

Authentication data

Encryption Extension

Called encapsulating security payload (ESP)

Includes an SPI

All headers and data after ESP are encrypted

slide-20
SLIDE 20

IPv6 Design Controversies

slide-21
SLIDE 21

IPv6 Design Controversies

 Address length

slide-22
SLIDE 22

IPv6 Design Controversies

 Address length

8 byte

Might run out in a few decades

Less header overhead

slide-23
SLIDE 23

IPv6 Design Controversies

 Address length

8 byte

Might run out in a few decades

Less header overhead

16 byte

More overhead

Good for foreseeable future

slide-24
SLIDE 24

IPv6 Design Controversies

 Address length

8 byte

Might run out in a few decades

Less header overhead

16 byte

More overhead

Good for foreseeable future

20 byte

Even more overhead

Compatible with OSI

slide-25
SLIDE 25

IPv6 Design Controversies

 Address length

8 byte

Might run out in a few decades

Less header overhead

16 byte

More overhead

Good for foreseeable future

20 byte

Even more overhead

Compatible with OSI

Variable length

slide-26
SLIDE 26

IPv6 Design Controversies

slide-27
SLIDE 27

IPv6 Design Controversies

Hop limit

slide-28
SLIDE 28

IPv6 Design Controversies

Hop limit

65,535

32 hop paths are common now

In a decade, we may see much longer paths

slide-29
SLIDE 29

IPv6 Design Controversies

Hop limit

65,535

32 hop paths are common now

In a decade, we may see much longer paths

255

Objective is to limit lost packet lifetime

Good network design makes long paths unlikely

Source to backbone

Across backbone

Backbone to destination

slide-30
SLIDE 30

IPv6 Design Controversies

 Greater than 64KB data

Good for supercomputer/high bandwidth applications

Too much overhead to fragment large data packets

 64 KB data

More compatible with low-bandwidth lines

1 MB packet ties up a 1.5MBps line for more than 5 seconds

Inconveniences interactive users

slide-31
SLIDE 31

IPv6 Design Controversies

 Keep checksum

 Removing checksum from IP is

analogous to removing brakes from a car

 Light and faster  Unprepared for the unexpected

 Remove checksum

 Typically duplicated in data link and

transport layers

 Very expensive in IPv4

slide-32
SLIDE 32

IPv6 Design Controversies

slide-33
SLIDE 33

IPv6 Design Controversies

Mobile hosts

slide-34
SLIDE 34

IPv6 Design Controversies

Mobile hosts

Direct or indirect connectivity

Reconnect directly using canonical address

Use home and foreign agents to forward traffic

slide-35
SLIDE 35

IPv6 Design Controversies

Mobile hosts

Direct or indirect connectivity

Reconnect directly using canonical address

Use home and foreign agents to forward traffic

Mobility introduces asymmetry

Base station signal is strong, heard by mobile units

Mobile unit signal is weak and susceptible to interference, may not be heard by base station

slide-36
SLIDE 36

IPv6 Design Controversies

slide-37
SLIDE 37

IPv6 Design Controversies

 Security

slide-38
SLIDE 38

IPv6 Design Controversies

 Security

Where?

Network layer

A standard service

Application layer

No viable standard

Application susceptible to errors in network implementation

Expensive to turn on and off

slide-39
SLIDE 39

IPv6 Design Controversies

 Security

Where?

Network layer

A standard service

Application layer

No viable standard

Application susceptible to errors in network implementation

Expensive to turn on and off

How?

Political import/export issues

Cryptographic strength issues

slide-40
SLIDE 40

Transition From IPv4 To IPv6

 Not all routers can be upgraded

simultaneous

 no “flag days”  How will the network operate with mixed IPv4

and IPv6 routers?

 Tunneling: IPv6 carried as payload in IPv4

datagram among IPv4 routers

slide-41
SLIDE 41

Tunneling

Physical view: A B E F

IPv6 IPv6 IPv6 IPv6 IPv4 IPv4

slide-42
SLIDE 42

Tunneling

A B E F

IPv6 IPv6 IPv6 IPv6 tunnel

Logical view: Physical view: A B E F

IPv6 IPv6 IPv6 IPv6 IPv4 IPv4

slide-43
SLIDE 43

Tunneling

A B E F

IPv6 IPv6 IPv6 IPv6 tunnel

Logical view: Physical view: A B E F

IPv6 IPv6 IPv6 IPv6

C D

IPv4 IPv4

Flow: X Src: A Dest: F data Flow: X Src: A Dest: F data Flow: X Src: A Dest: F data

Src:B Dest: E

Flow: X Src: A Dest: F data

Src:B Dest: E

A-to-B: IPv6 E-to-F: IPv6 B-to-C: IPv6 inside IPv4 B-to-C: IPv6 inside IPv4

slide-44
SLIDE 44

Multiprotocol label switching (MPLS)

 initial goal: speed up IP forwarding by using

fixed length label (instead of IP address) to do forwarding

borrowing ideas from Virtual Circuit (VC) approach

but IP datagram still keeps IP address!

PPP or Ethernet header IP header remainder of link-layer frame MPLS header label Exp S TTL

20 3 1 5

slide-45
SLIDE 45

MPLS capable routers

 a.k.a. label-switched router  forwards packets to outgoing interface based

  • nly on label value (don’t inspect IP address)

MPLS forwarding table distinct from IP forwarding tables

 signaling protocol needed to set up forwarding

RSVP-TE

forwarding possible along paths that IP alone would not allow (e.g., source-specific routing) !!

use MPLS for traffic engineering

 must co-exist with IP-only routers

slide-46
SLIDE 46

R1 R2 D R3 R4 R5

1

A R6

in out out label label dest interface

6 - A 0

in out out label label dest interface

10 6 A 1 12 9 D 0

in out out label label dest interface

10 A 0 12 D 0

1 in out out label label dest interface

8 6 A 0 8 A 1

MPLS forwarding tables