rfc2373.txt

bind 9.3结合mysql数据库

   |0              1|1              3|3              4|4              6|
   |0              5|6              1|2              7|8              3|
   +----------------+----------------+----------------+----------------+
   |0000000000000000|0000000000000000|0000000000000000|0000000001001111|
   +----------------+----------------+----------------+----------------+

   Note that this results in the universal/local bit set to "0" to
   indicate local scope.

Links without Identifiers

   There are a number of links that do not have any type of built-in
   identifier.  The most common of these are serial links and configured
   tunnels.  Interface identifiers must be chosen that are unique for
   the link.

   When no built-in identifier is available on a link the preferred
   approach is to use a global interface identifier from another
   interface or one which is assigned to the node itself.  To use this
   approach no other interface connecting the same node to the same link
   may use the same identifier.




Hinden & Deering            Standards Track                    [Page 20]

RFC 2373              IPv6 Addressing Architecture             July 1998


   If there is no global interface identifier available for use on the
   link the implementation needs to create a local scope interface
   identifier.  The only requirement is that it be unique on the link.
   There are many possible approaches to select a link-unique interface
   identifier.  They include:

      Manual Configuration
      Generated Random Number
      Node Serial Number (or other node-specific token)

   The link-unique interface identifier should be generated in a manner
   that it does not change after a reboot of a node or if interfaces are
   added or deleted from the node.

   The selection of the appropriate algorithm is link and implementation
   dependent.  The details on forming interface identifiers are defined
   in the appropriate "IPv6 over <link>" specification.  It is strongly
   recommended that a collision detection algorithm be implemented as
   part of any automatic algorithm.
































Hinden & Deering            Standards Track                    [Page 21]

RFC 2373              IPv6 Addressing Architecture             July 1998


APPENDIX B: ABNF Description of Text Representations
----------------------------------------------------

   This appendix defines the text representation of IPv6 addresses and
   prefixes in Augmented BNF [ABNF] for reference purposes.

      IPv6address = hexpart [ ":" IPv4address ]
      IPv4address = 1*3DIGIT "." 1*3DIGIT "." 1*3DIGIT "." 1*3DIGIT

      IPv6prefix  = hexpart "/" 1*2DIGIT

      hexpart = hexseq | hexseq "::" [ hexseq ] | "::" [ hexseq ]
      hexseq  = hex4 *( ":" hex4)
      hex4    = 1*4HEXDIG





































Hinden & Deering            Standards Track                    [Page 22]

RFC 2373              IPv6 Addressing Architecture             July 1998


APPENDIX C: CHANGES FROM RFC-1884
---------------------------------

   The following changes were made from RFC-1884 "IP Version 6
   Addressing Architecture":

      - Added an appendix providing a ABNF description of text
        representations.
      - Clarification that link unique identifiers not change after
        reboot or other interface reconfigurations.
      - Clarification of Address Model based on comments.
      - Changed aggregation format terminology to be consistent with
        aggregation draft.
      - Added text to allow interface identifier to be used on more than
        one interface on same node.
      - Added rules for defining new multicast addresses.
      - Added appendix describing procedures for creating EUI-64 based
        interface ID's.
      - Added notation for defining IPv6 prefixes.
      - Changed solicited node multicast definition to use a longer
        prefix.
      - Added site scope all routers multicast address.
      - Defined Aggregatable Global Unicast Addresses to use "001" Format
        Prefix.
      - Changed "010" (Provider-Based Unicast) and "100" (Reserved for
        Geographic) Format Prefixes to Unassigned.
      - Added section on Interface ID definition for unicast addresses.
        Requires use of EUI-64 in range of format prefixes and rules for
        setting global/local scope bit in EUI-64.
      - Updated NSAP text to reflect working in RFC1888.
      - Removed protocol specific IPv6 multicast addresses (e.g., DHCP)
        and referenced the IANA definitions.
      - Removed section "Unicast Address Example".  Had become OBE.
      - Added new and updated references.
      - Minor text clarifications and improvements.
















Hinden & Deering            Standards Track                    [Page 23]

RFC 2373              IPv6 Addressing Architecture             July 1998


REFERENCES

   [ABNF]    Crocker, D., and P. Overell, "Augmented BNF for
             Syntax Specifications: ABNF", RFC 2234, November 1997.

   [AGGR]    Hinden, R., O'Dell, M., and S. Deering, "An
             Aggregatable Global Unicast Address Format", RFC 2374, July
             1998.

   [AUTH]    Atkinson, R., "IP Authentication Header", RFC 1826, August
             1995.

   [ANYCST]  Partridge, C., Mendez, T., and W. Milliken, "Host
             Anycasting Service", RFC 1546, November 1993.

   [CIDR]    Fuller, V., Li, T., Yu, J., and K. Varadhan, "Classless
             Inter-Domain Routing (CIDR): An Address Assignment and
             Aggregation Strategy", RFC 1519, September 1993.

   [ETHER]   Crawford, M., "Transmission of IPv6 Pacekts over Ethernet
             Networks", Work in Progress.

   [EUI64]   IEEE, "Guidelines for 64-bit Global Identifier (EUI-64)
             Registration Authority",
             http://standards.ieee.org/db/oui/tutorials/EUI64.html,
             March 1997.

   [FDDI]    Crawford, M., "Transmission of IPv6 Packets over FDDI
             Networks", Work in Progress.

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

   [MASGN]   Hinden, R., and S. Deering, "IPv6 Multicast Address
             Assignments", RFC 2375, July 1998.

   [NSAP]    Bound, J., Carpenter, B., Harrington, D., Houldsworth, J.,
             and A. Lloyd, "OSI NSAPs and IPv6", RFC 1888, August 1996.

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

   [TOKEN]   Thomas, S., "Transmission of IPv6 Packets over Token Ring
             Networks", Work in Progress.

   [TRAN]    Gilligan, R., and E. Nordmark, "Transition Mechanisms for
             IPv6 Hosts and Routers", RFC 1993, April 1996.




Hinden & Deering            Standards Track                    [Page 24]

RFC 2373              IPv6 Addressing Architecture             July 1998


AUTHORS' ADDRESSES

   Robert M. Hinden
   Nokia
   232 Java Drive
   Sunnyvale, CA 94089
   USA

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


   Stephen E. Deering
   Cisco Systems, Inc.
   170 West Tasman Drive
   San Jose, CA 95134-1706
   USA

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





























Hinden & Deering            Standards Track                    [Page 25]

RFC 2373              IPv6 Addressing Architecture             July 1998


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.
























Hinden & Deering            Standards Track                    [Page 26]