10.12. References Here's a list of the most important RFCs and drafts mentioned in this chapter. Sometimes I include additional subject-related RFCs for your personal further study. 10.12.1. RFCs RFC 2185, "Routing Aspects Of IPv6 Transition," 1997 RFC 2473, "Generic Packet Tunneling in IPv6 Specification," 1998 RFC 2529, "Transmission of IPv6 over IPv4 Domains without Explicit Tunnels," 1999 RFC 2553, "Basic Socket Interface Extensions for IPv6," March 1999 RFC 2663, "IP Network Address Translator (NAT) Terminology and Considerations," 1999 RFC 2765, "Stateless IP/ICMP Translation Algorithm (SIIT)," 2000 RFC 2766, "Network Address TranslationProtocol Translation (NAT-PT)," 2000 RFC 2767, "Dual Stack Hosts using the "Bump-In-the-Stack" Technique (BIS)," 2000 RFC 2784, "Generic Routing Encapsulation (GRE)," 2000 RFC 3022, "Traditional IP Network Address Translator (Traditional NAT)," 2001 RFC 3053, "IPv6 Tunnel Broker," 2001 RFC 3056, "Connection of IPv6 Domains via IPv4 Clouds," 2001 RFC 3068, "An Anycast Prefix for 6to4 Relay Routers," 2001 RFC 3142, "An IPv6-to-IPv4 Transport Relay Translator," 2001 RFC 3162, "RADIUS and IPv6," 2001 RFC 3338, "Dual Stack Hosts Using BIA," 2002 RFC 3484, "Default Address Selection for Internet Protocol version 6 (IPv6)," 2003 RFC 3489, "STUN - Simple Traversal of User Datagram Protocol (UDP) Through Network Address Translators (NATs)," 2003 RFC 3493, "Basic Socket Interface Extensions for IPv6" 2003 RFC 3542, "Advanced Sockets Application Program Interface (API) for IPv6," 2003 RFC 3582, "Goals for IPv6 Site-Multihoming Architectures," 2003 RFC 3715, "IPsec-Network Address Translation (NAT) Compatibility Requirements," 2004 RFC 3789, "Introduction to the Survey of IPv4 Addresses in Currently Deployed IETF Standards Track and Experimental Documents," 2004 RFC 3790, "Survey of IPv4 Addresses in Currently Deployed IETF Internet Area Standards Track and Experimental Documents," 2004 RFC 3791, "Survey of IPv4 Addresses in Currently Deployed IETF Routing Area Standards Track and Experimental Documents," 2004 RFC 3792, "Survey of IPv4 Addresses in Currently Deployed IETF Security Area Standards Track and Experimental Documents," 2004 RFC 3793, "Survey of IPv4 Addresses in Currently Deployed IETF Sub-IP Area Standards Track and Experimental Documents," 2004 RFC 3794, "Survey of IPv4 Addresses in Currently Deployed IETF Transport Area Standards Track and Experimental Documents," 2004 RFC 3795, "Survey of IPv4 Addresses in Currently Deployed IETF Application Area Standards Track and Experimental Documents," 2004 RFC 3796, "Survey of IPv4 Addresses in Currently Deployed IETF Operations & Management Area Standards Track and Experimental Documents," 2004 RFC 3901, "DNS IPv6 Transport Operational Guidelines," 2004 RFC 3964, "Security Considerations for 6to4," 2004 RFC 3971, "SEcure Neighbor Discovery (SEND)," 2005 RFC 3972, "Cryptographically Generated Addresses (CGA)," 2005 RFC 4029, "Scenarios and Analysis for Introducing IPv6 into ISP Networks," 2005 RFC 4038, "Application Aspects of IPv6 Transition," 2005 RFC 4057, "IPv6 Enterprise Network Scenarios," 2005 RFC 4159, "Deprecation of 'ip6.int'," 2005 RFC 4177, "Architectural Approaches to Multi-homing for IPv6," 2005 RFC 4191, "Default Router Preferences and More-Specific Routes," 2005 RFC 4213, "Basic Transition Mechanisms for IPv6 Hosts and Routers," 2005 RFC 4214, "Intra-Site Automatic Tunnel Addressing Protocol (ISATAP)," 2005 RFC 4215, "Analysis on IPv6 Transition in Third Generation Partnership Project (3GPP) Networks," 2005 RFC 4218, "Threats Relating to IPv6 Multihoming Solutions," 2005 RFC 4219, "Things Multihoming in IPv6 (MULTI6) Developers Should Think About," 2005 RFC 4241, "A Model of IPv6/IPv4 Dual Stack Internet Access Service," 2005 RFC 4282, "The Network Access Identifier," 2005 RFC 4380, "Teredo: Tunneling IPv6 over UDP through Network Address Translations (NATs)," 2006
10.12.2. Drafts Drafts can be found at http://www.ietf.org/ID.html. To locate the latest version of a draft, refer to https://datatracker.ietf.org/public/pidtracker.cgi. You can enter the draft name without a version number, and the most current version will come up. If a draft does not show up, it was either deleted or published as an RFC. Alternatively, you can go to the new Internet drafts database interface at https://datatracker.ietf.org/public/idindex.cgi. http://tools.ietf.org/wg is also a very useful site. More information on the process of standardization, RFCs, and drafts can be found in Appendix A. Here's a list of interesting drafts related to the topics or drafts to which I referred in this chapter: draft-bound-dstm-exp-04.txt, Dual Stack IPv6 Dominant Transition Mechanism (DSTM) draft-blanchet-v6ops-tunnelbroker-tsp-03.txt, IPv6 Tunnel Broker with the Tunnel Setup Protocol (TSP) draft-ietf-v6ops-vlan-usage-01.txt, Use of VLANs for IPv4-IPv6 Coexistence in Enterprise Networks draft-ietf-dnsop-ipv6-dns-issues-12.txt, Operational Considerations and Issues with IPv6 DNS (RFC queue) draft-ietf-v6ops-bb-deployment-scenarios-04.txt, ISP IPv6 Deployment Scenarios in Broadband Access Networks draft-shin-v6ops-802-16-deployment-scenarios-00.txt, ISP IPv6 Deployment Scenarios in Wireless Broadband Access Networks draft-ietf-v6ops-natpt-to-exprmntl-03.txt, Reasons to Move NAT-PT to Experimental draft-ietf-v6ops-nap-02.txt, IPv6 Network Architecture Protection draft-ietf-shim6-proto-04.txt, Level 3 multihoming shim protocol draft-ietf-shim6-failure-detection-03.txt, Failure Detection and Locator Pair Exploration Protocol for IPv6 Multihoming draft-ietf-shim6-hba-01.txt, Hash Based Addresses (HBA) draft-ietf-shim6-reach-detect-01.txt, Shim6 Reachability Detection draft-vandevelde-v6ops-addcon-00.txt, IPv6 Unicast Address Assignment Considerations
|
