1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
|
IP VERSION 6 PARAMETERS
(last updated 2001 Jun 29)
Taken from [IPV6]
1. Version Number = 6
2. Traffic Class
[TBD based on work of Differentiated Services W.G.]
3. Flow Label
[Not a parameter]
4. Payload Length
[Not a parameter]
5. Next Header
5.a. Header types
00 = Hop-by-Hop Options
43 = Routing
44 = Fragment
51 = Authentication
60 = Destination Options
50 = Encapsulating Security Payload
xx = Upper Layer Header
58 = Internet Control Message Protocol (ICMP)
59 - no next header
For the "xx" values see the list of protocol numbers for the values to
use for the upper layer protocol (see the file: protocol-numbers).
5.b. Options Types
From [IPV6]: IPv6 Option Types are 8-bit values, structured as three
subfields:
act - 2 bits, specifying action if Option Type is unrecognized:
00 = skip over option
01 = discard packet, silently
10 = discard packet and send ICMP
11 = discard packet and send ICMP if packet was unicast
chg - 1 bit, specifying whether or not option data can change
while packet is en-route:
0 = option data does not change en-route
1 = option data may change en-route
rest - 5 bits, the rest of the Option Type
Each distinct 8-bit Option Type identifies a different option, i.e., the
high-order 3 bits are considered part of the option identification.
However, it is recommended that Option Types be assigned with distinct
values in the "rest" subfield, until and unless that 5-bit space becomes
full.
These are the currently assigned IPv6 Option Types, in order of increasing
value of the "rest" subfield:
b BINARY
HEX act chg rest
--- --- --- -----
0 00 0 00000 Pad1 [IPV6]
1 00 0 00001 PadN [IPV6]
C2 11 0 00010 Jumbo Payload [JUMBOGRAM]
C3 11 0 00011 NSAP Address [RFC 1888]
4 00 0 00100 Tunnel Encapsulation Limit [TUNNEL]
5 00 0 00101 Router Alert [RFC 2711]
C6 11 0 00110 Binding Update [MOBILE-IPV6]
7 00 0 00111 Binding Acknowledgment [MOBILE-IPV6]
8 00 0 01000 Binding Request [MOBILE-IPV6]
C9 11 0 01001 Home Address [MOBILE-IPV6]
8A 10 0 01010 Endpoint Identification [CHARLES LYNN]
5.c. Routing Types
0 - Source Route [IPV6]
1 - Nimrod [CHARLES LYNN]
6. Hop Limit
[Not a parameter]
7. Source Address
[Not a parameter]
8. Destination Address
[Not a parameter]
REFERENCES
----------
[IPV6] Deering, S., R. Hinden, "Internet Protocol, Version 6
(IPv6) Specification", Internet Draft, August 1998.
[JUMBOGRAM] Deering, S., R. Hinden, "The IPv6 Jumbo Payload
Option", Internet Draft, August 1998.
[MOBILE-IPv6] Johnson, D., C. Perkins, "Mobility Support in IPv6",
Internet Draft, August 1998.
[RFC 2711] Partridge, C., A. Jackson, "IPv6 Router Alert Option",
RFC 2711, October 1999.
[RFC 1888] Bound, J., B. Carpenter, D. Harrington, J. Houldsworth,
and A. Lloyd, "OSI NSAPs and IPv6", RFC 1888, Digital
Equipment Corporation, CERN, ICL Network Systems,
Datacraft Technologies, August 1996.
[TUNNEL] Conta, A., S. Deering, "Generic Packet Tunneling in
IPv6 Specification", Internet Draft, January 1998..
PEOPLE
------
[CHARLES LYNN] <clynn@bbn.com>
[]
|
