[ Pobierz całość w formacie PDF ]
.(With IPv6, addresses belong to interfaces rather than machines.)The subnetting capability of IPv6 is much more flexible than that of IPv4: subnetting can now be carriedout on bit boundaries, in much the same way as Classless InterDomain Routing (CIDR).The internal structure of the Public Topology for an A6 global unicast address consists of:3 13 8 24FP TLA ID RES NLA IDA 3 bit FP (Format Prefix) of 001 indicates this is a global Unicast address.FP lengths for other types ofaddresses may vary.13 TLA (Top Level Aggregator) bits give the prefix of your top-level IP backbone carrier.8 Reserved bits24 bits for Next Level Aggregators.This allows organizations with a TLA to hand out portions of their IPspace to client organizations, so that the client can then split up the network further by filling in moreNLA bits, and hand out IPv6 prefixes to their clients, and so forth.98 Appendix A.AppendicesThere is no particular structure for the Site topology section.Organizations can allocate these bits in anyway they desire.The Interface Identifier must be unique on that network.On ethernet networks, one way to ensure this isto set the address to the first three bytes of the hardware address, "FFFE", then the last three bytes of thehardware address.The lowest significant bit of the first byte should then be complemented.Addressesare written as 32-bit blocks separated with a colon, and leading zeros of a block may be omitted, forexample:3ffe:8050:201:9:a00:20ff:fe81:2b32IPv6 address specifications are likely to contain long strings of zeros, so the architects have included ashorthand for specifying them.The double colon ( :: ) indicates the longest possible string of zeros thatcan fit, and can be used only once in an address.A.4.Bibliography (and Suggested Reading)A.4.1.Request for Comments (RFCs)Specification documents for the Internet protocol suite, including the DNS, are published as part of theRequest for Comments (RFCs) series of technical notes.The standards themselves are defined by theInternet Engineering Task Force (IETF) and the Internet Engineering Steering Group (IESG).RFCs canbe obtained online via FTP at ftp://www.isi.edu/in-notes/RFCxxx.txt (ftp://www.isi.edu/in-notes/)(wherexxx is the number of the RFC).RFCs are also available via the Web at http://www.ietf.org/rfc/.BibliographyStandards[RFC974] C.Partridge, Mail Routing and the Domain System, January 1986.[RFC1034] P.V.Mockapetris, Domain Names Concepts and Facilities, November 1987.[RFC1035] P.V.Mockapetris, Domain Names Implementation and Specification, November 1987.99 Appendix A.AppendicesProposed Standards[RFC2181] R., R.Bush Elz, Clarifications to the DNS Specification, July 1997.[RFC2308] M.Andrews, Negative Caching of DNS Queries, March 1998.[RFC1995] M.Ohta, Incremental Zone Transfer in DNS, August 1996.[RFC1996] P.Vixie, A Mechanism for Prompt Notification of Zone Changes, August 1996.[RFC2136] P.Vixie, S.Thomson, Y.Rekhter, and J.Bound, Dynamic Updates in the Domain NameSystem, April 1997.[RFC2845] P.Vixie, O.Gudmundsson, D.Eastlake, 3rd, and B.Wellington, Secret Key TransactionAuthentication for DNS (TSIG), May 2000.Proposed Standards Still Under Development[RFC1886] S.Thomson and C.Huitema, DNS Extensions to support IP version 6, December 1995.[RFC2065] D.Eastlake, 3rd and C.Kaufman, Domain Name System Security Extensions, January 1997.[RFC2137] D.Eastlake, 3rd, Secure Domain Name System Dynamic Update, April 1997.Other Important RFCs About DNS Implementation[RFC1535] E.Gavron, A Security Problem and Proposed Correction With Widely Deployed DNSSoftware., October 1993.[RFC1536] A.Kumar, J.Postel, C.Neuman, P.Danzig, and S.Miller, Common DNS ImplementationErrors and Suggested Fixes, October 1993.[RFC1982] R.Elz and R.Bush, Serial Number Arithmetic, August 1996.100 Appendix A.AppendicesResource Record Types[RFC1183] C.F.Everhart, L.A.Mamakos, R.Ullmann, and P.Mockapetris, New DNS RR Definitions,October 1990.[RFC1706] B.Manning and R.Colella, DNS NSAP Resource Records, October 1994.[RFC2168] R.Daniel and M.Mealling, Resolution of Uniform Resource Identifiers using the DomainName System, June 1997.[RFC1876] C.Davis, P.Vixie, T., and I.Dickinson, A Means for Expressing Location Information in theDomain Name System, January 1996.[RFC2052] A.Gulbrandsen and P.Vixie, A DNS RR for Specifying the Location of Services., October1996.[RFC2163] A.Allocchio, Using the Internet DNS to Distribute MIXER Conformant Global AddressMapping, January 1998.[RFC2230] R.Atkinson, Key Exchange Delegation Record for the DNS, October 1997.DNS and the Internet[RFC1101] P.V.Mockapetris, DNS Encoding of Network Names and Other Types, April 1989.[RFC1123] Braden, Requirements for Internet Hosts - Application and Support, October 1989.[RFC1591] J
[ Pobierz całość w formacie PDF ]