rfc2467.txt

来自「RFC 的详细文档！」· 文本 代码 · 共 508 行 · 第 1/2 页

   +----------+-----------------------+----------------------------+
   |1111111010|         (zeros)       |    Interface Identifier    |
   +----------+-----------------------+----------------------------+

7.  Address Mapping -- Unicast

   The procedure for mapping IPv6 unicast addresses into FDDI link-layer
   addresses is described in [DISC].  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           -+
                |                               |
                +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+






Crawford                    Standards Track                     [Page 5]

RFC 2467                     IPv6 over FDDI                December 1998


   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.

8.  Address Mapping -- Multicast

   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]     |
                 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

9.  Differences From RFC 2019

   The following are the functional differences between this
   specification and RFC 2019.

       "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 [EUI64].  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.






Crawford                    Standards Track                     [Page 6]

RFC 2467                     IPv6 over FDDI                December 1998


10.  Security Considerations

   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.

11.  References

   [AARCH] Hinden, R. and S. Deering "IP Version 6 Addressing
           Architecture", RFC 2373, July 1998.

   [ACONF] Thomson, S. and T. Narten, "IPv6 Stateless Address
           Autoconfiguration", RFC 2462, December 1998.

   [CANON] Narten, T. and C. Burton, "A Caution On The Canonical
           Ordering Of Link-Layer Addresses", RFC 2469, December 1998.

   [DISC]  Narten, T., Nordmark, E. and W. Simpson, "Neighbor Discovery
           for IP Version 6 (IPv6)", RFC 2461, December 1998.

   [ETHER] Crawford, M., "Transmission of IPv6 Packets over Ethernet
           Networks", RFC 2464, December 1998.

   [EUI64] "Guidelines For 64-bit Global Identifier (EUI-64)",
           http://standards.ieee.org/db/oui/tutorials/EUI64.html.

   [ICMPV6]  Conta, A. and S. Deering, "Internet Control Message
             Protocol (ICMPv6) for the Internet Protocol Version 6
             (IPv6) Specification", RFC 2463, December 1998.

   [IPV6]  Deering, S. and R. Hinden, "Internet Protocol, Version 6
           (IPv6) Specification", RFC 2460, December 1998.

   [RFC 1981]  McCann, J., Deering, S. and J. Mogul, "Path MTU Discovery
               for IP version 6", RFC 1981, August 1996.

   [RFC 2119]  Bradner, S., "Key words for use in RFCs to Indicate
               Requirement Levels", BCP 14, RFC 2119, March 1997.













Crawford                    Standards Track                     [Page 7]

RFC 2467                     IPv6 over FDDI                December 1998


12.  Author's Address

   Matt Crawford
   Fermilab MS 368
   PO Box 500
   Batavia, IL 60510
   USA

   Phone: [phone]
   EMail: [e-mail]









































Crawford                    Standards Track                     [Page 8]

RFC 2467                     IPv6 over FDDI                December 1998


13.  Full Copyright Statement

   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]