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
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
|
<pre>Network Working Group M. Crawford
Request for Comments: 2467 Fermilab
Obsoletes: <a href="./rfc2019">2019</a> December 1998
Category: Standards Track
<span class="h1">Transmission of IPv6 Packets over FDDI Networks</span>
Status of this Memo
This document specifies an Internet standards track protocol for the
Internet community, and requests discussion and suggestions for
improvements. Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol. Distribution of this memo is unlimited.
Copyright Notice
Copyright (C) The Internet Society (1998). All Rights Reserved.
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
This document specifies the frame format for transmission of IPv6
packets and the method of forming IPv6 link-local addresses and
statelessly autoconfigured addresses on FDDI networks. It also
specifies the content of the Source/Target Link-layer Address option
used in Router Solicitation, Router Advertisement, Neighbor
Solicitation, Neighbor Advertisement and Redirect messages when those
messages are transmitted on an FDDI network.
This document replaces <a href="./rfc2019">RFC 2019</a>, "Transmission of IPv6 Packets Over
FDDI", which will become historic.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [<a href="./rfc2119">RFC 2119</a>].
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Maximum Transmission Unit</span>
FDDI permits a frame length of 4500 octets (9000 symbols), including
at least 22 octets (44 symbols) of Data Link encapsulation when
long-format addresses are used. Subtracting 8 octets of LLC/SNAP
header, this would, in principle, allow the IPv6 [<a href="#ref-IPV6" title=""Internet Protocol, Version 6 (IPv6) Specification"">IPV6</a>] packet in the
Information field to be up to 4470 octets. However, it is desirable
to allow for the variable sizes and possible future extensions of the
MAC header and frame status fields. The default MTU size for IPv6
packets on an FDDI network is therefore 4352 octets. This size may
be reduced by a Router Advertisement [<a href="#ref-DISC" title=""Neighbor Discovery for IP Version 6 (IPv6)"">DISC</a>] containing an MTU option
<span class="grey">Crawford Standards Track [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc2467">RFC 2467</a> IPv6 over FDDI December 1998</span>
which specifies a smaller MTU, or by manual configuration of each
node. If a Router Advertisement received on an FDDI interface has an
MTU option specifying an MTU larger than 4352, or larger than a
manually configured value, that MTU option may be logged to system
management but must be otherwise ignored.
For purposes of this document, information received from DHCP is
considered "manually configured" and the term FDDI includes CDDI.
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Frame Format</span>
FDDI provides both synchronous and asynchronous transmission, with
the latter class further subdivided by the use of restricted and
unrestricted tokens. Only asynchronous transmission with
unrestricted tokens is required for FDDI interoperability.
Accordingly, IPv6 packets shall be sent in asynchronous frames using
unrestricted tokens. The robustness principle dictates that nodes
should be able to receive synchronous frames and asynchronous frames
sent using restricted tokens.
IPv6 packets are transmitted in LLC/SNAP frames, using long-format
(48 bit) addresses. The data field contains the IPv6 header and
payload and is followed by the FDDI Frame Check Sequence, Ending
Delimiter, and Frame Status symbols.
<span class="grey">Crawford Standards Track [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc2467">RFC 2467</a> IPv6 over FDDI December 1998</span>
0 1
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
+-+-+-+-+-+-+-+-+
| FC |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Destination |
+- -+
| FDDI |
+- -+
| Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Source |
+- -+
| FDDI |
+- -+
| Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| DSAP | SSAP |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| CTL | OUI ... |
+-+-+-+-+-+-+-+-+ +
| ... OUI |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Ethertype |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IPv6 |
+- -+
| header |
+- -+
| and |
+- -+
/ payload ... /
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
(Each tic mark represents one bit.)
FDDI Header Fields:
FC The Frame Code must be in the range 50 to 57
hexadecimal, inclusive, with the three low order bits
indicating the frame priority.
DSAP, SSAP Both the DSAP and SSAP fields shall contain the value AA
hexadecimal, indicating SNAP encapsulation.
CTL The Control field shall be set to 03 hexadecimal,
indicating Unnumbered Information.
<span class="grey">Crawford Standards Track [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc2467">RFC 2467</a> IPv6 over FDDI December 1998</span>
OUI The Organizationally Unique Identifier shall be set to
000000 hexadecimal.
Ethertype The Ethernet protocol type ("ethertype") shall be set to
the value 86DD hexadecimal.
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Interaction with Bridges</span>
802.1d MAC bridges which connect different media, for example
Ethernet and FDDI, have become very widespread. Some of them do IPv4
packet fragmentation and/or support IPv4 Path MTU discovery [RFC
1981], many others do not, or do so incorrectly. Use of IPv6 in a
bridged mixed-media environment must not depend on support from MAC
bridges, unless those bridges are known to correctly implement IPv6
Path MTU Discovery [RFC 1981, ICMPV6].
For correct operation when mixed media are bridged together by
bridges which do not support IPv6 Path MTU Discovery, the smallest
MTU of all the media must be advertised by routers in an MTU option.
If there are no routers present, this MTU must be manually configured
in each node which is connected to a medium with a default MTU larger
than the smallest MTU.
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Stateless Autoconfiguration</span>
The Interface Identifier [<a href="#ref-AARCH" title=""IP Version 6 Addressing Architecture"">AARCH</a>] for an FDDI interface is based on
the EUI-64 identifier [<a href="#ref-EUI64" title=""Guidelines For 64-bit Global Identifier (EUI-64)"">EUI64</a>] derived from the interface's built-in
48-bit IEEE 802 address. The EUI-64 is formed as follows.
(Canonical bit order is assumed throughout. See [<a href="#ref-CANON" title=""A Caution On The Canonical Ordering Of Link-Layer Addresses"">CANON</a>] for a
caution on bit-order effects in LAN interfaces.)
The OUI of the FDDI MAC address (the first three octets) becomes the
company_id of the EUI-64 (the first three octets). The fourth and
fifth octets of the EUI are set to the fixed value FFFE hexadecimal.
The last three octets of the FDDI MAC address become the last three
octets of the EUI-64.
The Interface Identifier is then formed from the EUI-64 by
complementing the "Universal/Local" (U/L) bit, which is the next-to-
lowest order bit of the first octet of the EUI-64. For further
discussion on this point, see [<a href="#ref-ETHER" title=""Transmission of IPv6 Packets over Ethernet Networks"">ETHER</a>] and [<a href="#ref-AARCH" title=""IP Version 6 Addressing Architecture"">AARCH</a>].
<span class="grey">Crawford Standards Track [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc2467">RFC 2467</a> IPv6 over FDDI December 1998</span>
For example, the Interface Identifier for an FDDI interface whose
built-in address is, in hexadecimal,
34-56-78-9A-BC-DE
would be
36-56-78-FF-FE-9A-BC-DE.
A different MAC address set manually or by software should not be
used to derive the Interface Identifier. If such a MAC address must
be used, its global uniqueness property should be reflected in the
value of the U/L bit.
An IPv6 address prefix used for stateless autoconfiguration [<a href="#ref-ACONF" title=""IPv6 Stateless Address Autoconfiguration"">ACONF</a>]
of an FDDI interface must have a length of 64 bits.
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Link-Local Addresses</span>
The IPv6 link-local address [<a href="#ref-AARCH" title=""IP Version 6 Addressing Architecture"">AARCH</a>] for an FDDI interface is formed
by appending the Interface Identifier, as defined above, to the
prefix FE80::/64.
10 bits 54 bits 64 bits
+----------+-----------------------+----------------------------+
|1111111010| (zeros) | Interface Identifier |
+----------+-----------------------+----------------------------+
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Address Mapping -- Unicast</span>
The procedure for mapping IPv6 unicast addresses into FDDI link-layer
addresses is described in [<a href="#ref-DISC" title=""Neighbor Discovery for IP Version 6 (IPv6)"">DISC</a>]. The Source/Target Link-layer
Address option has the following form when the link layer is FDDI.
0 1
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+- FDDI -+
| |
+- Address -+
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
<span class="grey">Crawford Standards Track [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="./rfc2467">RFC 2467</a> IPv6 over FDDI December 1998</span>
Option fields:
Type 1 for Source Link-layer address.
2 for Target Link-layer address.
Length 1 (in units of 8 octets).
FDDI Address
The 48 bit FDDI IEEE 802 address, in canonical bit order.
This is the address the interface currently responds to,
and may be different from the built-in address used to
derive the Interface Identifier.
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Address Mapping -- Multicast</span>
An IPv6 packet with a multicast destination address DST, consisting
of the sixteen octets DST[1] through DST[16], is transmitted to the
FDDI multicast address whose first two octets are the value 3333
hexadecimal and whose last four octets are the last four octets of
DST.
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0 0 1 1 0 0 1 1|0 0 1 1 0 0 1 1|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| DST[13] | DST[14] |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| DST[15] | DST[16] |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
<span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. Differences From <a href="./rfc2019">RFC 2019</a></span>
The following are the functional differences between this
specification and <a href="./rfc2019">RFC 2019</a>.
"FDDI adjacency detection" has been removed, due to recent work
in IEEE 802.1p.
The Address Token, which was a node's 48-bit MAC address, is
replaced with the Interface Identifier, which is 64 bits in
length and based on the EUI-64 format [<a href="#ref-EUI64" title=""Guidelines For 64-bit Global Identifier (EUI-64)"">EUI64</a>]. An IEEE-defined
mapping exists from 48-bit MAC addresses to EUI-64 form.
A prefix used for stateless autoconfiguration must now be 64 bits
long rather than 80. The link-local prefix is also shortened to
64 bits.
<span class="grey">Crawford Standards Track [Page 6]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
<span class="grey"><a href="./rfc2467">RFC 2467</a> IPv6 over FDDI December 1998</span>
<span class="h2"><a class="selflink" id="section-10" href="#section-10">10</a>. Security Considerations</span>
The method of derivation of Interface Identifiers from MAC addresses
is intended to preserve global uniqueness when possible. However,
there is no protection from duplication through accident or forgery.
<span class="h2"><a class="selflink" id="section-11" href="#section-11">11</a>. References</span>
[<a id="ref-AARCH">AARCH</a>] Hinden, R. and S. Deering "IP Version 6 Addressing
Architecture", <a href="./rfc2373">RFC 2373</a>, July 1998.
[<a id="ref-ACONF">ACONF</a>] Thomson, S. and T. Narten, "IPv6 Stateless Address
Autoconfiguration", <a href="./rfc2462">RFC 2462</a>, December 1998.
[<a id="ref-CANON">CANON</a>] Narten, T. and C. Burton, "A Caution On The Canonical
Ordering Of Link-Layer Addresses", <a href="./rfc2469">RFC 2469</a>, December 1998.
[<a id="ref-DISC">DISC</a>] Narten, T., Nordmark, E. and W. Simpson, "Neighbor Discovery
for IP Version 6 (IPv6)", <a href="./rfc2461">RFC 2461</a>, December 1998.
[<a id="ref-ETHER">ETHER</a>] Crawford, M., "Transmission of IPv6 Packets over Ethernet
Networks", <a href="./rfc2464">RFC 2464</a>, December 1998.
[<a id="ref-EUI64">EUI64</a>] "Guidelines For 64-bit Global Identifier (EUI-64)",
<a href="http://standards.ieee.org/db/oui/tutorials/EUI64.html">http://standards.ieee.org/db/oui/tutorials/EUI64.html</a>.
[<a id="ref-ICMPV6">ICMPV6</a>] Conta, A. and S. Deering, "Internet Control Message
Protocol (ICMPv6) for the Internet Protocol Version 6
(IPv6) Specification", <a href="./rfc2463">RFC 2463</a>, December 1998.
[<a id="ref-IPV6">IPV6</a>] Deering, S. and R. Hinden, "Internet Protocol, Version 6
(IPv6) Specification", <a href="./rfc2460">RFC 2460</a>, December 1998.
[<a id="ref-RFC 1981">RFC 1981</a>] McCann, J., Deering, S. and J. Mogul, "Path MTU Discovery
for IP version 6", <a href="./rfc1981">RFC 1981</a>, August 1996.
[<a id="ref-RFC 2119">RFC 2119</a>] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997.
<span class="grey">Crawford Standards Track [Page 7]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
<span class="grey"><a href="./rfc2467">RFC 2467</a> IPv6 over FDDI December 1998</span>
<span class="h2"><a class="selflink" id="section-12" href="#section-12">12</a>. Author's Address</span>
Matt Crawford
Fermilab MS 368
PO Box 500
Batavia, IL 60510
USA
Phone: +1 630 840-3461
EMail: crawdad@fnal.gov
<span class="grey">Crawford Standards Track [Page 8]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
<span class="grey"><a href="./rfc2467">RFC 2467</a> IPv6 over FDDI December 1998</span>
<span class="h2"><a class="selflink" id="section-13" href="#section-13">13</a>. Full Copyright Statement</span>
Copyright (C) The Internet Society (1998). All Rights Reserved.
This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than
English.
The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Crawford Standards Track [Page 9]
</pre>
|
