0% found this document useful (0 votes)
27 views

Ipv6 Protocol: (RFC 2460 DS)

IPv6 simplifies the header from IPv4 by reducing optional header fields and standardizing the base header to 40 bytes. The IPv6 header includes fields for version, traffic class, flow label, payload length, next header, and hop limit. Optional extension headers can be used for routing, fragmentation, authentication, and security and have a defined processing order important for ensuring packets are handled correctly.

Uploaded by

philippevaly
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
27 views

Ipv6 Protocol: (RFC 2460 DS)

IPv6 simplifies the header from IPv4 by reducing optional header fields and standardizing the base header to 40 bytes. The IPv6 header includes fields for version, traffic class, flow label, payload length, next header, and hop limit. Optional extension headers can be used for routing, fragmentation, authentication, and security and have a defined processing order important for ensuring packets are handled correctly.

Uploaded by

philippevaly
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 12

IPv6 Protocol

(RFC 2460 DS)

Where and when ?

IPv4 Header
32 bits

Options

Where and when ?

20 Bytes

Ver.

IHL Total Length ToS Identifier flags fragment Checksum TTL Protocol Source Address Destination Address

IPv4 Header
32 bits

Where and when ?

20 Bytes

Ver.

Total Length Identifier flags fragment Checksum TTL Protocol Source Address Destination Address ToS

IPv4 Header
32 bits

TTL

Checksum Protocol Source Address Destination Address

Where and when ?

20 Bytes

Ver.

ToS

Total Length

IPv6: Header simplification


32 bits

Ver. Traffic Class Payload length

Flow label Next Header Hop Limit

5 words

Source Address

Destination Address

Where and when ?

40 Bytes

IPv6 header
Version Traffic class
Next slide

Flow label
RFC 3697

Payload length
Use Jumbogram for specific cases (payload = 0)

Hop limit Next header


Where and when ?

CoS support in IPv6


The Traffic Class field: used as in IPv4
Work done in diffserv wg (closed): RFCs 2474, 2475, 2597, 3260,

6 bits

2 bits

DSCP

CU

The Flow Label field: designed to enable classification of packets belonging to a specific flow
A flow is a sequence of packets that should receive specific non-default handling from the network Intuitively: 5-tuple of the same source/destination address/port and transport protocol values Without the flow label the classifier must use transport next header value and port numbers
Less efficient (need to parse the option headers) May be impossible (fragmentation or IPsec ESP)

Further info: RFC 3697 (PS)


Where and when ?

IPv6: Optional headers


IPv6 Header Next Header = TCP

TCP Header + DATA

IPv6 Header Next Header = Routing

Routing Header Next Header = TCP

TCP Header + DATA

IPv6 Header Next Header = Routing

Routing Header Next Header = Fragment

Fragment Header TCP Header Next Header + DATA = TCP

Where and when ?

IPv6: Optional extensions


Hop-by-hop (jumbogram, router alert)
Always the first extension Replace IPv4 options, Analyzed by every router.

Destination Routing (loose source routing) Fragmentation Authentication Security


Where and when ?

v4 options vs. v6 extensions


A R1 A -> B R1

A -> R1 B

IPv4 options : processed in each router slow down packets B

Where and when ?

v4 options vs. v6 extensions


A R1

A -> R1 B

A -> B R1

IPv6 extensions (except Hop-by-Hop) are processed only by the destination. B

Where and when ?

Order is important (RFC 2460)


IPv6 Hop by hop Destination Routing Fragmentation Authentication Security Destination Upper Layer
Where and when ?

Processed by every router Processed by routers listed in Routing extension List of routers to cross Processed by the destination After reassembling the packet Cipher the content of the remaining information Processed only by the destination

You might also like