idnits 2.17.1 draft-ietf-v6ops-ipv4survey-int-03.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** There are 4 instances of lines with control characters in the document. == There are 1 instance of lines with non-RFC2606-compliant FQDNs in the document. == There are 1 instance of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. RFC 2119 keyword, line 764: '... EtherType (16 bits) SHALL be set as defined in Assigned Numbers [8]:...' RFC 2119 keyword, line 1440: '... ar$hrd - SHALL contain 28. (HI...' RFC 2119 keyword, line 1442: '... ar$pro - SHALL contain the IP ...' RFC 2119 keyword, line 1444: '... ar$op - SHALL contain the ope...' RFC 2119 keyword, line 1450: '... ar$pln - SHALL contain 4....' (1 more instance...) Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 1431 has weird spacing: '... 8 bits byte ...' == Line 1432 has weird spacing: '... 8 bits reque...' == Line 1433 has weird spacing: '... 8 bits targe...' == Line 1434 has weird spacing: '...32 bits reque...' == Line 1435 has weird spacing: '...32 bits targe...' == (2 more instances...) -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (Oct 2003) is 7498 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Looks like a reference, but probably isn't: 'RFC-1010' on line 540 == Missing Reference: '8' is mentioned on line 764, but not defined == Missing Reference: '7' is mentioned on line 1180, but not defined == Missing Reference: '4' is mentioned on line 661, but not defined == Missing Reference: '6' is mentioned on line 1171, but not defined == Missing Reference: '3' is mentioned on line 862, but not defined -- Looks like a reference, but probably isn't: 'LA' on line 1468 == Missing Reference: '18' is mentioned on line 1506, but not defined == Outdated reference: A later version (-06) exists of draft-ietf-v6ops-ipv4survey-intro-04 ** Downref: Normative reference to an Informational draft: draft-ietf-v6ops-ipv4survey-intro (ref. '1') Summary: 5 errors (**), 0 flaws (~~), 17 warnings (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 IPv6 Operations C. Mickles, Ed. 2 Internet-Draft 3 Expires: March 31, 2004 P. Nesser 4 Nesser & Nesser Consulting 5 Oct 2003 7 Survey of IPv4 Addresses in Currently Deployed IETF Internet Area 8 Standards 9 draft-ietf-v6ops-ipv4survey-int-03.txt 11 Status of this Memo 13 This document is an Internet-Draft and is in full conformance with 14 all provisions of Section 10 of RFC2026. 16 Internet-Drafts are working documents of the Internet Engineering 17 Task Force (IETF), its areas, and its working groups. Note that other 18 groups may also distribute working documents as Internet-Drafts. 20 Internet-Drafts are draft documents valid for a maximum of six months 21 and may be updated, replaced, or obsoleted by other documents at any 22 time. It is inappropriate to use Internet-Drafts as reference 23 material or to cite them other than as "work in progress." 25 The list of current Internet-Drafts can be accessed at http:// 26 www.ietf.org/ietf/1id-abstracts.txt. 28 The list of Internet-Draft Shadow Directories can be accessed at 29 http://www.ietf.org/shadow.html. 31 This Internet-Draft will expire on March 31, 2004. 33 Copyright Notice 35 Copyright (C) The Internet Society (2003). All Rights Reserved. 37 Abstract 39 This document seeks to document all usage of IPv4 addresses in 40 currently deployed IETF Internet Area documented standards. In order 41 to successfully transition from an all IPv4 Internet to an all IPv6 42 Internet, many interim steps will be taken. One of these steps is the 43 evolution of current protocols that have IPv4 dependencies. It is 44 hoped that these protocols (and their implementations) will be 45 redesigned to be network address independent, but failing that will 46 at least dually support IPv4 and IPv6. To this end, all Standards 47 (Full, Draft, and Proposed) as well as Experimental RFCs will be 48 surveyed and any dependencies will be documented. 50 Table of Contents 52 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . 9 53 2. Document Organization . . . . . . . . . . . . . . . . . . 10 54 3. Full Standards . . . . . . . . . . . . . . . . . . . . . . 11 55 3.1 RFC 791 Internet Protocol . . . . . . . . . . . . . . . . 11 56 3.2 RFC 792 Internet Control Message Protocol . . . . . . . . 11 57 3.3 RFC 826 Ethernet Address Resolution Protocol . . . . . . . 11 58 3.4 RFC 891 DCN Local-Network Protocols . . . . . . . . . . . 11 59 3.5 RFC 894 Standard for the transmission of IP datagrams 60 over Ethernet networks . . . . . . . . . . . . . . . . . . 11 61 3.6 RFC 895 Standard for the transmission of IP datagrams 62 over experimental Ethernet networks . . . . . . . . . . . 11 63 3.7 RFC 903 Reverse Address Resolution Protocol . . . . . . . 11 64 3.8 RFC 919 Broadcasting Internet Datagrams . . . . . . . . . 11 65 3.9 RFC 922 Broadcasting Internet datagrams in the presence 66 of subnets . . . . . . . . . . . . . . . . . . . . . . . . 11 67 3.10 RFC 950 Internet Standard Subnetting Procedure . . . . . . 12 68 3.11 RFC 1034 Domain Names: Concepts and Facilities . . . . . . 12 69 3.12 RFC 1035 Domain Names: Implementation and Specification . 13 70 3.13 RFC 1042 Standard for the transmission of IP datagrams 71 over IEEE 802 networks . . . . . . . . . . . . . . . . . 14 72 3.14 RFC 1044 Internet Protocol on Network System's 73 HYPERchannel: Protocol Specification . . . . . . . . . . 14 74 3.15 RFC 1055 Nonstandard for transmission of IP datagrams 75 over serial lines: SLIP . . . . . . . . . . . . . . . . . 14 76 3.16 RFC 1088 Standard for the transmission of IP datagrams 77 over NetBIOS networks . . . . . . . . . . . . . . . . . . 15 78 3.17 RFC 1112 Host Extensions for IP Multicasting . . . . . . . 15 79 3.18 RFC 1132 Standard for the transmission of 802.2 packets 80 over IPX networks . . . . . . . . . . . . . . . . . . . . 15 81 3.19 RFC 1201 Transmitting IP traffic over ARCNET networks . . 15 82 3.20 RFC 1209 The Transmission of IP Datagrams over the SMDS 83 Service . . . . . . . . . . . . . . . . . . . . . . . . . 15 84 3.21 RFC 1390 Transmission of IP and ARP over FDDI Networks . . 15 85 3.22 RFC 1661 The Point-to-Point Protocol (PPP) . . . . . . . . 15 86 3.23 RFC 1662 PPP in HDLC-like Framing . . . . . . . . . . . . 16 87 3.24 RFC 2427 Multiprotocol Interconnect over Frame Relay . . . 16 88 4. Draft Standards . . . . . . . . . . . . . . . . . . . . . 17 89 4.1 RFC 951 Bootstrap Protocol (BOOTP) . . . . . . . . . . . . 17 90 4.2 RFC 1188 Proposed Standard for the Transmission of IP 91 Datagrams over FDDI Networks . . . . . . . . . . . . . . . 18 92 4.3 RFC 1191 Path MTU discovery . . . . . . . . . . . . . . . 18 93 4.4 RFC 1356 Multiprotocol Interconnect on X.25 and ISDN . . . 18 94 4.5 RFC 1534 Interoperation Between DHCP and BOOTP . . . . . . 18 95 4.6 RFC 1542 Clarifications and Extensions for the 96 Bootstrap Protocol . . . . . . . . . . . . . . . . . . . . 18 97 4.7 RFC 1629 Guidelines for OSI NSAP Allocation in the 98 Internet . . . . . . . . . . . . . . . . . . . . . . . . . 18 99 4.8 RFC 1762 The PPP DECnet Phase IV Control Protocol (DNCP) . 18 100 4.9 RFC 1989 PPP Link Quality Monitoring . . . . . . . . . . . 18 101 4.10 RFC 1990 The PPP Multilink Protocol (MP) . . . . . . . . . 18 102 4.11 RFC 1994 PPP Challenge Handshake Authentication 103 Protocol (CHAP) . . . . . . . . . . . . . . . . . . . . . 19 104 4.12 RFC 2067 IP over HIPPI . . . . . . . . . . . . . . . . . . 19 105 4.13 RFC 2131 Dynamic Host Configuration Protocol . . . . . . . 20 106 4.14 RFC 2132 DHCP Options and BOOTP Vendor Extensions . . . . 20 107 4.15 RFC 2390 Inverse Address Resolution Protocol . . . . . . . 20 108 4.16 RFC 2460 Internet Protocol, Version 6 (IPv6) 109 Specification . . . . . . . . . . . . . . . . . . . . . . 20 110 4.17 RFC 2461 Neighbor Discovery for IP Version 6 (IPv6) . . . 20 111 4.18 RFC 2462 IPv6 Stateless Address Autoconfiguration . . . . 20 112 4.19 RFC 2463 Internet Control Message Protocol (ICMPv6) for 113 the Internet Protocol Version 6 (IPv6) Specification . . 20 114 4.20 RFC 3596 DNS Extensions to support IP version 6 . . . . . 20 115 5. Proposed Standards . . . . . . . . . . . . . . . . . . . . 21 116 5.1 RFC 1234 Tunneling IPX traffic through IP networks . . . . 21 117 5.2 RFC 1256 ICMP Router Discovery Messages . . . . . . . . . 22 118 5.3 RFC 1277 Encoding Network Addresses to Support 119 Operation over Non-OSI Lower Layers . . . . . . . . . . . 22 120 5.4 RFC 1332 The PPP Internet Protocol Control Protocol 121 (IPCP) . . . . . . . . . . . . . . . . . . . . . . . . . . 22 122 5.5 RFC 1377 The PPP OSI Network Layer Control Protocol 123 (OSINLCP) . . . . . . . . . . . . . . . . . . . . . . . . 22 124 5.6 RFC 1378 The PPP AppleTalk Control Protocol (ATCP) . . . . 22 125 5.7 RFC 1469 IP Multicast over Token-Ring Local Area 126 Networks . . . . . . . . . . . . . . . . . . . . . . . . . 22 127 5.8 RFC 1552 The PPP Internetworking Packet Exchange 128 Control Protocol (IPXCP) . . . . . . . . . . . . . . . . . 22 129 5.9 RFC 1570 PPP LCP Extensions . . . . . . . . . . . . . . . 23 130 5.10 RFC 1598 PPP in X.25 PPP-X25 . . . . . . . . . . . . . . . 23 131 5.11 RFC 1618 PPP over ISDN . . . . . . . . . . . . . . . . . . 23 132 5.12 RFC 1663 PPP Reliable Transmission . . . . . . . . . . . . 23 133 5.13 RFC 1752 The Recommendation for the IP Next Generation 134 Protocol . . . . . . . . . . . . . . . . . . . . . . . . . 23 135 5.14 RFC 1755 ATM Signaling Support for IP over ATM . . . . . . 23 136 5.15 RFC 1763 The PPP Banyan Vines Control Protocol (BVCP) . . 23 137 5.16 RFC 1764 The PPP XNS IDP Control Protocol (XNSCP) . . . . 23 138 5.17 RFC 1973 PPP in Frame Relay . . . . . . . . . . . . . . . 23 139 5.18 RFC 1981 Path MTU Discovery for IP version 6 . . . . . . . 23 140 5.19 RFC 1982 Serial Number Arithmetic . . . . . . . . . . . . 23 141 5.20 5.21 RFC 1995 Incremental Zone Transfer in DNS . . . . . . 24 142 5.21 RFC 1996 A Mechanism for Prompt Notification of Zone 143 Changes (DNS NOTIFY) . . . . . . . . . . . . . . . . . . . 24 144 5.22 RFC 2003 IP Encapsulation within IP . . . . . . . . . . . 24 145 5.23 RFC 2004 Minimal Encapsulation within IP . . . . . . . . . 24 146 5.24 RFC 2005 Applicability Statement for IP Mobility Support . 24 147 5.25 RFC 2022 Support for Multicast over UNI 3.0/3.1 based 148 ATM Networks . . . . . . . . . . . . . . . . . . . . . . . 24 149 5.26 RFC 2043 The PPP SNA Control Protocol (SNACP) . . . . . . 24 150 5.27 RFC 2097 The PPP NetBIOS Frames Control Protocol (NBFCP) . 24 151 5.28 RFC 2113 IP Router Alert Option . . . . . . . . . . . . . 24 152 5.29 RFC 2125 The PPP Bandwidth Allocation Protocol (BAP) / 153 The PPP Bandwidth Allocation Control Protocol (BACP) . . . 25 154 5.30 RFC 2136 Dynamic Updates in the Domain Name System (DNS 155 UPDATE) . . . . . . . . . . . . . . . . . . . . . . . . . 25 156 5.31 RFC 2181 Clarifications to the DNS Specification . . . . . 25 157 5.32 RFC 2225 Classical IP and ARP over ATM . . . . . . . . . . 25 158 5.33 RFC 2226 IP Broadcast over ATM Networks . . . . . . . . . 25 159 5.34 RFC 2241 DHCP Options for Novell Directory Services . . . 25 160 5.35 RFC 2242 NetWare/IP Domain Name and Information . . . . . 26 161 5.36 RFC 2290 Mobile-IPv4 Configuration Option for PPP IPCP . . 26 162 5.37 RFC 2308 Negative Caching of DNS Queries (DNS NCACHE) . . 26 163 5.38 RFC 2331 ATM Signaling Support for IP over ATM - UNI 164 Signaling 4.0 Update . . . . . . . . . . . . . . . . . . . 26 165 5.39 RFC 2332 NBMA Next Hop Resolution Protocol (NHRP) . . . . 26 166 5.40 RFC 2333 NHRP Protocol Applicability . . . . . . . . . . . 27 167 5.41 RFC 2335 A Distributed NHRP Service Using SCSP . . . . . . 27 168 5.42 RFC 2363 PPP Over FUNI . . . . . . . . . . . . . . . . . . 27 169 5.43 RFC 2364 PPP Over AAL5 . . . . . . . . . . . . . . . . . . 27 170 5.44 RFC 2371 Transaction Internet Protocol Version 3.0 171 (TIPV3) . . . . . . . . . . . . . . . . . . . . . . . . . 27 172 5.45 RFC 2464 Transmission of IPv6 Packets over Ethernet 173 Networks . . . . . . . . . . . . . . . . . . . . . . . . . 29 174 5.46 RFC 2467 Transmission of IPv6 Packets over FDDI Networks . 29 175 5.47 RFC 2470 Transmission of IPv6 Packets over Token Ring 176 Networks . . . . . . . . . . . . . . . . . . . . . . . . . 29 177 5.48 RFC 2472 IP Version 6 over PPP . . . . . . . . . . . . . . 29 178 5.49 RFC 2473 Generic Packet Tunneling in IPv6 Specification . 29 179 5.50 RFC 2484 PPP LCP Internationalization Configuration 180 Option . . . . . . . . . . . . . . . . . . . . . . . . . . 29 181 5.51 RFC 2485 DHCP Option for The Open Group's User 182 Authentication Protocol . . . . . . . . . . . . . . . . . 29 183 5.52 RFC 2486 The Network Access Identifier . . . . . . . . . . 29 184 5.53 RFC 2491 IPv6 over Non-Broadcast Multiple Access (NBMA) 185 networks . . . . . . . . . . . . . . . . . . . . . . . . . 29 186 5.54 RFC 2492 IPv6 over ATM Networks . . . . . . . . . . . . . 29 187 5.55 RFC 2497 Transmission of IPv6 Packets over ARCnet 188 Networks . . . . . . . . . . . . . . . . . . . . . . . . . 30 189 5.56 RFC 2507 IP Header Compression . . . . . . . . . . . . . . 30 190 5.57 RFC 2526 Reserved IPv6 Subnet Anycast Addresses . . . . . 30 191 5.58 RFC 2529 Transmission of IPv6 over IPv4 Domains without 192 Explicit Tunnels . . . . . . . . . . . . . . . . . . . . . 30 193 5.59 RFC 2563 DHCP Option to Disable Stateless 194 Auto-Configuration in IPv4 Clients . . . . . . . . . . . . 30 195 5.60 RFC 2590 Transmission of IPv6 Packets over Frame Relay 196 Networks Specification . . . . . . . . . . . . . . . . . . 30 197 5.61 RFC 2601 ILMI-Based Server Discovery for ATMARP . . . . . 30 198 5.62 RFC 2602 ILMI-Based Server Discovery for MARS . . . . . . 30 199 5.63 RFC 2603 ILMI-Based Server Discovery for NHRP . . . . . . 30 200 5.64 RFC 2610 DHCP Options for Service Location Protocol . . . 30 201 5.65 RFC 2615 PPP over SONET/SDH . . . . . . . . . . . . . . . 31 202 5.66 RFC 2625 IP and ARP over Fibre Channel . . . . . . . . . . 31 203 5.67 RFC 2661 Layer Two Tunneling Protocol (L2TP) . . . . . . . 31 204 5.68 RFC 2671 Extension Mechanisms for DNS (EDNS0) . . . . . . 31 205 5.69 RFC 2672 Non-Terminal DNS Name Redirection . . . . . . . . 31 206 5.70 RFC 2673 Binary Labels in the Domain Name System . . . . . 31 207 5.71 RFC 2675 IPv6 Jumbograms . . . . . . . . . . . . . . . . . 31 208 5.72 RFC 2684 Multiprotocol Encapsulation over ATM 209 Adaptation Layer 5 . . . . . . . . . . . . . . . . . . . . 31 210 5.73 RFC 2685 Virtual Private Networks Identifier . . . . . . . 31 211 5.74 RFC 2686 The Multi-Class Extension to Multi-Link PPP . . . 32 212 5.75 RFC 2687 PPP in a Real-time Oriented HDLC-like Framing . . 32 213 5.76 RFC 2688 Integrated Services Mappings for Low Speed 214 Networks . . . . . . . . . . . . . . . . . . . . . . . . . 32 215 5.77 RFC 2710 Multicast Listener Discovery (MLD) for IPv6 . . . 32 216 5.78 RFC 2711 IPv6 Router Alert Option . . . . . . . . . . . . 32 217 5.79 RFC 2728 The Transmission of IP Over the Vertical 218 Blanking Interval of a Television Signal . . . . . . . . . 32 219 5.80 RFC 2734 IPv4 over IEEE 1394 . . . . . . . . . . . . . . . 33 220 5.81 RFC 2735 NHRP Support for Virtual Private Networks . . . . 33 221 5.82 RFC 2765 Stateless IP/ICMP Translation Algorithm (SIIT) . 33 222 5.83 RFC 2766 Network Address Translation - Protocol 223 Translation (NAT-PT) . . . . . . . . . . . . . . . . . . . 33 224 5.84 RFC 2776 Multicast-Scope Zone Announcement Protocol 225 (MZAP) . . . . . . . . . . . . . . . . . . . . . . . . . . 33 226 5.85 RFC 2782 A DNS RR for specifying the location of 227 services . . . . . . . . . . . . . . . . . . . . . . . . . 33 228 5.86 RFC 2794 Mobile IP Network Access Identifier Extension 229 for IPv4 . . . . . . . . . . . . . . . . . . . . . . . . . 33 230 5.87 RFC 2834 ARP and IP Broadcast over HIPPI-800 . . . . . . . 33 231 5.88 RFC 2835 IP and ARP over HIPPI-6400 . . . . . . . . . . . 35 232 5.89 RFC 2855 DHCP for IEEE 1394 . . . . . . . . . . . . . . . 35 233 5.90 RFC 2874 DNS Extensions to Support IPv6 Address 234 Aggregation and Renumbering . . . . . . . . . . . . . . . 35 235 5.91 RFC 2893 Transition Mechanisms for IPv6 Hosts and 236 Routers . . . . . . . . . . . . . . . . . . . . . . . . . 36 237 5.92 RFC 2916 E.164 number and DNS . . . . . . . . . . . . . . 36 238 5.93 RFC 2937 The Name Service Search Option for DHCP . . . . . 36 239 5.94 RFC 3004 The User Class Option for DHCP . . . . . . . . . 36 240 5.95 RFC 3011 The IPv4 Subnet Selection Option for DHCP . . . . 36 241 5.96 RFC 3021 Using 31-Bit Prefixes for IPv4 P2P Links . . . . 36 242 5.97 RFC 3024 Reverse Tunneling for Mobile IP, revised . . . . 36 243 5.98 RFC 3046 DHCP Relay Agent Information Option . . . . . . . 36 244 5.99 RFC 3056 Connection of IPv6 Domains via IPv4 Clouds . . . 36 245 5.100 RFC 3068 An Anycast Prefix for 6to4 Relay Routers . . . . 36 246 5.101 RFC 3070 Layer Two Tunneling Protocol (L2TP) over Frame 247 Relay . . . . . . . . . . . . . . . . . . . . . . . . . . 37 248 5.102 RFC 3074 DHC Load Balancing Algorithm . . . . . . . . . . 37 249 5.103 RFC 3077 A Link-Layer Tunneling Mechanism for 250 Unidirectional Links . . . . . . . . . . . . . . . . . . . 37 251 5.104 RFC 3115 Mobile IP Vendor/Organization-Specific 252 Extensions . . . . . . . . . . . . . . . . . . . . . . . . 37 253 5.105 RFC 3145 L2TP Disconnect Cause Information . . . . . . . . 37 254 5.106 RFC 3344 IP Mobility Support for IPv4 . . . . . . . . . . 37 255 5.107 RFC 3376 Internet Group Management Protocol, Version 3 . . 37 256 5.108 RFC 3402 Dynamic Delegation Discovery System (DDDS) 257 Part Two: The Algorithm . . . . . . . . . . . . . . . . . 37 258 5.109 RFC 3403 Dynamic Delegation Discovery System (DDDS) 259 Part Three: The Domain Name System (DNS) Database . . . . 37 260 5.110 RFC 3513 IP Version 6 Addressing Architecture . . . . . . 37 261 5.111 RFC 3518 Point-to-Point Protocol (PPP) Bridging Control 262 Protocol (BCP) . . . . . . . . . . . . . . . . . . . . . . 38 263 6. Experimental RFCs . . . . . . . . . . . . . . . . . . . . 39 264 6.1 RFC 1149 Standard for the transmission of IP datagrams 265 on avian carriers . . . . . . . . . . . . . . . . . . . . 39 266 6.2 RFC 1183 New DNS RR Definitions . . . . . . . . . . . . . 39 267 6.3 RFC 1226 Internet protocol encapsulation of AX.25 frames . 39 268 6.4 RFC 1241 Scheme for an internet encapsulation protocol: 269 Version 1 . . . . . . . . . . . . . . . . . . . . . . . . 39 270 6.5 RFC 1307 Dynamically Switched Link Control Protocol . . . 39 271 6.6 RFC 1393 Traceroute Using an IP Option . . . . . . . . . . 40 272 6.7 RFC 1433 Directed ARP . . . . . . . . . . . . . . . . . . 40 273 6.8 RFC 1464 Using the Domain Name System To Store 274 Arbitrary String Attributes . . . . . . . . . . . . . . . 40 275 6.9 RFC 1475 TP/IX: The Next Internet . . . . . . . . . . . . 40 276 6.10 RFC 1561 Use of ISO CLNP in TUBA Environments . . . . . . 40 277 6.11 RFC 1712 DNS Encoding of Geographical Location . . . . . . 41 278 6.12 RFC 1735 NBMA Address Resolution Protocol (NARP) . . . . . 41 279 6.13 RFC 1768 Host Group Extensions for CLNP Multicasting . . . 42 280 6.14 RFC 1788 ICMP Domain Name Messages . . . . . . . . . . . . 42 281 6.15 RFC 1797 Class A Subnet Experiment . . . . . . . . . . . . 42 282 6.16 RFC 1819 Internet Stream Protocol Version 2 (ST2) 283 Protocol Specification - Version ST2+ . . . . . . . . . . 42 284 6.17 RFC 1868 ARP Extension - UNARP . . . . . . . . . . . . . . 43 285 6.18 RFC 1876 A Means for Expressing Location Information in 286 the Domain Name System . . . . . . . . . . . . . . . . . . 43 287 6.19 RFC 1888 OSI NSAPs and IPv6 . . . . . . . . . . . . . . . 43 288 6.20 RFC 2009 GPS-Based Addressing and Routing . . . . . . . . 43 289 6.21 RFC 2143 Encapsulating IP with the SCSI . . . . . . . . . 43 290 6.22 RFC 2345 Domain Names and Company Name Retrieval . . . . . 43 291 6.23 RFC 2443 A Distributed MARS Service Using SCSP . . . . . . 43 292 6.24 RFC 2471 IPv6 Testing Address Allocation . . . . . . . . . 44 293 6.25 RFC 2520 NHRP with Mobile NHCs . . . . . . . . . . . . . . 44 294 6.26 RFC 2521 ICMP Security Failures Messages . . . . . . . . . 44 295 6.27 RFC 2540 Detached Domain Name System (DNS) Information . . 44 296 6.28 RFC 2823 PPP over Simple Data Link (SDL) using 297 SONET/SDH with ATM-like framing . . . . . . . . . . . . . 44 298 6.29 RFC 3123 A DNS RR Type for Lists of Address Prefixes . . . 44 299 6.30 RFC 3168 The Addition of Explicit Congestion 300 Notification (ECN) to IP . . . . . . . . . . . . . . . . 44 301 6.31 RFC 3180 GLOP Addressing in 233/8 . . . . . . . . . . . . 44 302 7. Summary of the Results . . . . . . . . . . . . . . . . . . 45 303 7.1 Standards . . . . . . . . . . . . . . . . . . . . . . . . 45 304 7.1.1 RFC 791 Internet Protocol . . . . . . . . . . . . . . . . 45 305 7.1.2 RFC 792 Internet Control Message Protocol . . . . . . . . 45 306 7.1.3 RFC 891 DCN Networks . . . . . . . . . . . . . . . . . . . 45 307 7.1.4 RFC 894 IP over Ethernet . . . . . . . . . . . . . . . . . 45 308 7.1.5 RFC 895 IP over experimental Ethernets . . . . . . . . . . 45 309 7.1.6 RFC 922 Broadcasting Internet Datagrams in the Presence 310 of Subnets . . . . . . . . . . . . . . . . . . . . . . . . 45 311 7.1.7 RFC 950 Internet Standard Subnetting Procedure . . . . . . 46 312 7.1.8 RFC 1034 Domain Names: Concepts and Facilities . . . . . . 46 313 7.1.9 RFC 1035 Domain Names: Implementation and Specification . 46 314 7.1.10 RFC 1042 IP over IEEE 802 . . . . . . . . . . . . . . . . 46 315 7.1.11 RFC 1044 IP over HyperChannel . . . . . . . . . . . . . . 46 316 7.1.12 RFC 1088 IP over NetBIOS . . . . . . . . . . . . . . . . . 46 317 7.1.13 RFC 1112 Host Extensions for IP Multicast . . . . . . . . 46 318 7.1.14 RFC 1122 Requirements for Internet Hosts . . . . . . . . . 46 319 7.1.15 RFC 1201 IP over ARCNET . . . . . . . . . . . . . . . . . 46 320 7.1.16 RFC 1209 IP over SMDS . . . . . . . . . . . . . . . . . . 47 321 7.1.17 RFC 1390 Transmission of IP and ARP over FDDI Networks . . 47 322 7.2 Draft Standards . . . . . . . . . . . . . . . . . . . . . 47 323 7.2.1 RFC 951 Bootstrap Protocol (BOOTP) . . . . . . . . . . . . 47 324 7.2.2 RFC 1191 Path MTU Discovery . . . . . . . . . . . . . . . 47 325 7.2.3 RFC 1356 Multiprotocol Interconnect on X.25 and ISDN . . . 47 326 7.2.4 RFC 1990 The PPP Multilink Protocol (MP) . . . . . . . . . 47 327 7.2.5 RFC 2067 IP over HIPPI . . . . . . . . . . . . . . . . . . 47 328 7.2.6 RFC 2131 DHCP . . . . . . . . . . . . . . . . . . . . . . 47 329 7.3 Proposed Standards . . . . . . . . . . . . . . . . . . . . 48 330 7.3.1 RFC 1234 Tunneling IPX over IP . . . . . . . . . . . . . . 48 331 7.3.2 RFC 1256 ICMP Router Discovery . . . . . . . . . . . . . . 48 332 7.3.3 RFC 1277 Encoding Net Addresses to Support Operation 333 Over Non OSI Lower Layers . . . . . . . . . . . . . . . . 48 334 7.3.4 RFC 1332 PPP Internet Protocol Control Protocol (IPCP) . . 48 335 7.3.5 RFC 1469 IP Multicast over Token Ring . . . . . . . . . . 48 336 7.3.6 RFC 2003 IP Encapsulation within IP . . . . . . . . . . . 48 337 7.3.7 RFC 2004 Minimal Encapsulation within IP . . . . . . . . . 48 338 7.3.8 RFC 2022 Support for Multicast over UNI 3.0/3.1 based 339 ATM Networks . . . . . . . . . . . . . . . . . . . . . . . 48 340 7.3.9 RFC 2113 IP Router Alert Option . . . . . . . . . . . . . 48 341 7.3.10 RFC 2165 SLP . . . . . . . . . . . . . . . . . . . . . . . 49 342 7.3.11 RFC 2225 Classical IP & ARP over ATM . . . . . . . . . . . 49 343 7.3.12 RFC 2226 IP Broadcast over ATM . . . . . . . . . . . . . . 49 344 7.3.13 RFC 2371 Transaction IPv3 . . . . . . . . . . . . . . . . 49 345 7.3.14 RFC 2625 IP and ARP over Fibre Channel . . . . . . . . . . 49 346 7.3.15 RFC 2672 Non-Terminal DNS Redirection . . . . . . . . . . 49 347 7.3.16 RFC 2673 Binary Labels in DNS . . . . . . . . . . . . . . 49 348 7.3.17 IP over Vertical Blanking Interval of a TV Signal (RFC 349 2728) . . . . . . . . . . . . . . . . . . . . . . . . . . 49 350 7.3.18 RFC 2734 IPv4 over IEEE 1394 . . . . . . . . . . . . . . . 49 351 7.3.19 RFC 2834 ARP & IP Broadcasts Over HIPPI 800 . . . . . . . 49 352 7.3.20 RFC 2835 ARP & IP Broadcasts Over HIPPI 6400 . . . . . . . 50 353 7.3.21 RFC 3344 Mobility Support for IPv4 . . . . . . . . . . . . 50 354 7.3.22 RFC 3376 Internet Group Management Protocol, Version 3 . . 50 355 7.4 Experimental RFCs . . . . . . . . . . . . . . . . . . . . 50 356 7.4.1 RFC 1307 Dynamically Switched Link Control Protocol . . . 50 357 7.4.2 RFC 1393 Traceroute using an IP Option . . . . . . . . . . 50 358 7.4.3 RFC 1735 NBMA Address Resolution Protocol (NARP) . . . . . 50 359 7.4.4 RFC 1788 ICMP Domain Name Messages . . . . . . . . . . . . 50 360 7.4.5 RFC 1868 ARP Extension - UNARP . . . . . . . . . . . . . . 50 361 7.4.6 RFC 2143 IP Over SCSI . . . . . . . . . . . . . . . . . . 51 362 7.4.7 RFC 3180 GLOP Addressing in 233/8 . . . . . . . . . . . . 51 363 8. Security Considerations . . . . . . . . . . . . . . . . . 52 364 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . 53 365 Normative References . . . . . . . . . . . . . . . . . . . 54 366 Authors' Addresses . . . . . . . . . . . . . . . . . . . . 54 367 Intellectual Property and Copyright Statements . . . . . . 55 369 1. Introduction 371 This document is part of a document set aiming to document all usage 372 of IPv4 addresses in IETF standards. In an effort to have the 373 information in a manageable form, it has been broken into 7 documents 374 conforming to the current IETF areas (Application, Internet, 375 Management & Operations, Routing, Security, Sub-IP and Transport). 377 This specific document focuses on usage of IPv4 addresses within the 378 Internet area. 380 For a full introduction, please see the introduction [1] document. 382 2. Document Organization 384 The following sections 3, 4, 5, and 6 each describe the raw analysis 385 of Full, Draft, and Proposed Standards, and Experimental RFCs. Each 386 RFC is discussed in turn starting with RFC 1 and ending in (about) 387 RFC 3100. The comments for each RFC are "raw" in nature. That is, 388 each RFC is discussed in a vacuum and problems or issues discussed do 389 not "look ahead" to see if any of the issues raised have already been 390 fixed. 392 Section 7 is an analysis of the data presented in Sections 3, 4, 5, 393 and 6. It is here that all of the results are considered as a whole 394 and the problems that have been resolved in later RFCs are 395 correlated. 397 3. Full Standards 399 Full Internet Standards (most commonly simply referred to as 400 "Standards") are fully mature protocol specification that are widely 401 implemented and used throughout the Internet. 403 3.1 RFC 791 Internet Protocol 405 This specification defines IPv4 and is replaced by the IPv6 406 specifications. 408 3.2 RFC 792 Internet Control Message Protocol 410 This specification defines ICMP, and is inherently IPv4 dependent. 412 3.3 RFC 826 Ethernet Address Resolution Protocol 414 There are no IPv4 dependencies in this specification. 416 3.4 RFC 891 DCN Local-Network Protocols 418 There are many implicit assumptions about the use of IPv4 addresses 419 in this document. 421 3.5 RFC 894 Standard for the transmission of IP datagrams over Ethernet 422 networks 424 This specification specifically deals with the transmission of IPv4 425 packets over Ethernet. 427 3.6 RFC 895 Standard for the transmission of IP datagrams over 428 experimental Ethernet networks 430 This specification specifically deals with the transmission of IPv4 431 packets over experimental Ethernet. 433 3.7 RFC 903 Reverse Address Resolution Protocol 435 There are no IPv4 dependencies in this specification. 437 3.8 RFC 919 Broadcasting Internet Datagrams 439 This specification defines broadcasting for IPv4; IPv6 uses multicast 440 so this is not applicable. 442 3.9 RFC 922 Broadcasting Internet datagrams in the presence of subnets 444 This specification defines how broadcasts should be treated in the 445 presence of subnets. IPv6 uses multicast so this is not applicable. 447 3.10 RFC 950 Internet Standard Subnetting Procedure 449 This specification defines IPv4 subnetting; similar functionality is 450 part of IPv6 addressing architecture to begin with. 452 3.11 RFC 1034 Domain Names: Concepts and Facilities 454 In Section 3.6, "Resource Records", the definition of A record is: 456 RDATA which is the type and sometimes class dependent 457 data which describes the resource: 459 A For the IN class, a 32 bit IP address 461 And Section 5.2.1, "Typical functions" defines: 463 1. Host name to host address translation. 465 This function is often defined to mimic a previous HOSTS.TXT 466 based function. Given a character string, the caller wants 467 one or more 32 bit IP addresses. Under the DNS, it 468 translates into a request for type A RRs. Since the DNS does 470 not preserve the order of RRs, this function may choose to 471 sort the returned addresses or select the "best" address if 472 the service returns only one choice to the client. Note that 473 a multiple address return is recommended, but a single 474 address may be the only way to emulate prior HOSTS.TXT 475 services. 477 2. Host address to host name translation 479 This function will often follow the form of previous 480 functions. Given a 32 bit IP address, the caller wants a 481 character string. The octets of the IP address are reversed, 482 used as name components, and suffixed with "IN-ADDR.ARPA". A 483 type PTR query is used to get the RR with the primary name of 484 the host. For example, a request for the host name 485 corresponding to IP address 1.2.3.4 looks for PTR RRs for 486 domain name "4.3.2.1.IN-ADDR.ARPA". 488 There are, of course, numerous examples of IPv4 addresses scattered 489 throughout the document. 491 3.12 RFC 1035 Domain Names: Implementation and Specification 493 Section 3.4.1, "A RDATA format", defines the format for A records: 495 +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ 496 | ADDRESS | 497 +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ 499 where: 501 ADDRESS A 32 bit Internet address. 503 Hosts that have multiple Internet addresses will have 504 multiple A records. 506 A records cause no additional section processing. The 507 RDATA section of an A line in a master file is an Internet 508 address expressed as four decimal numbers separated by dots 509 without any imbedded spaces (e.g.,"10.2.0.52" or "192.0.5.6"). 511 And Section 3.4.2, "WKS RDATA", format is: 513 +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ 514 | ADDRESS | 515 +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ 516 | PROTOCOL | | 517 +--+--+--+--+--+--+--+--+ | 518 | | 519 / / 521 / / 522 +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ 524 where: 526 ADDRESS An 32 bit Internet address 528 PROTOCOL An 8 bit IP protocol number 530 A variable length bit map. The bit map 531 must be a multiple of 8 bits long. 533 The WKS record is used to describe the well known services 534 supported by a particular protocol on a particular internet 535 address. The PROTOCOL field specifies an IP protocol number, 536 and the bit map has one bit per port of the specified protocol. 537 The first bit corresponds to port 0, the second to port 1, etc. 538 If the bit map does not include a bit for a protocol of 539 interest, that bit is assumed zero. The appropriate values and 540 mnemonics for ports and protocols are specified in [RFC-1010]. 542 For example, if PROTOCOL=TCP (6), the 26th bit corresponds to 543 TCP port 25 (SMTP). If this bit is set, a SMTP server should be 544 listening on TCP port 25; if zero, SMTP service is not supported 545 on the specified address. 547 The purpose of WKS RRs is to provide availability information for 548 servers for TCP and UDP. If a server supports both TCP and UDP, 549 or has multiple Internet addresses, then multiple WKS RRs are 550 used. 552 WKS RRs cause no additional section processing. 554 Section 3.5, "IN-ADDR.ARPA domain", describes reverse DNS lookups and 555 is clearly IPv4 dependent. 557 There are, of course, numerous examples of IPv4 addresses scattered 558 throughout the document. 560 3.13 RFC 1042 Standard for the transmission of IP datagrams over IEEE 561 802 networks 563 This specification specifically deals with the transmission of IPv4 564 packets over IEEE 802 networks. 566 3.14 RFC 1044 Internet Protocol on Network System's HYPERchannel: 567 Protocol Specification 569 There are a variety of methods used in this standard to map IPv4 570 addresses to 32 bits fields in the HYPERchannel headers. This 571 specification does not support IPv6. 573 3.15 RFC 1055 Nonstandard for transmission of IP datagrams over serial 574 lines: SLIP 576 This specification is more of a analysis of the shortcomings of SLIP 577 which is unsurprising. The introduction of PPP as a general 578 replacement of SLIP has made this specification essentially unused. 579 No update need be considered. 581 3.16 RFC 1088 Standard for the transmission of IP datagrams over NetBIOS 582 networks 584 This specification documents a technique to encapsulate IP packets 585 inside NetBIOS packets. 587 The technique presented of using NetBIOS names of the form 588 IP.XX.XX.XX.XX will not work for IPv6 addresses since the length of 589 IPv6 addresses will not fit within the NetBIOS 15 octet name 590 limitation. 592 3.17 RFC 1112 Host Extensions for IP Multicasting 594 This specification defines IP multicast. Parts of the document are 595 IPv4 dependent. 597 3.18 RFC 1132 Standard for the transmission of 802.2 packets over IPX 598 networks 600 There are no IPv4 dependencies in this specification. 602 3.19 RFC 1201 Transmitting IP traffic over ARCNET networks 604 The major concerns of this specification with respect to IPv4 605 addresses occur in the resolution of ARCnet 8bit addresses to IPv4 606 addresses in an "ARPlike" method. This is incompatible with IPv6. 608 3.20 RFC 1209 The Transmission of IP Datagrams over the SMDS Service 610 This specification defines running IPv4 and ARP over SMDS. The 611 methods described could easily be extended to support IPv6 packets. 613 3.21 RFC 1390 Transmission of IP and ARP over FDDI Networks 615 This specification defines the use of IPv4 address on FDDI networks. 616 There are numerous IPv4 dependencies in the specification. 618 In particular the value of the Protocol Type Code (2048 for IPv4) and 619 a corresponding Protocol Address length (4 bytes for IPv4) needs to 620 be created. A discussion of broadcast and multicast addressing 621 techniques is also included, and similarly must be updated for IPv6 622 networks. The defined MTU limitation of 4096 octets of data (with 623 256 octets reserved header space) should remain sufficient for IPv6. 625 3.22 RFC 1661 The Point-to-Point Protocol (PPP) 627 There are no IPv4 dependencies in this specification. 629 3.23 RFC 1662 PPP in HDLC-like Framing 631 There are no IPv4 dependencies in this specification. 633 3.24 RFC 2427 Multiprotocol Interconnect over Frame Relay 635 There are no IPv4 dependencies in this specification. 637 4. Draft Standards 639 Draft Standards represent the penultimate standard level in the IETF. 640 A protocol can only achieve draft standard when there are multiple, 641 independent, interoperable implementations. Draft Standards are 642 usually quite mature and widely used. 644 4.1 RFC 951 Bootstrap Protocol (BOOTP) 646 This protocol is designed specifically for use with IPv4, for 647 example: 649 Section 3. Packet Format 651 All numbers shown are decimal, unless indicated otherwise. The 652 BOOTP packet is enclosed in a standard IP [8] UDP [7] datagram. For 653 simplicity it is assumed that the BOOTP packet is never fragmented. 654 Any numeric fields shown are packed in 'standard network byte 655 order', i.e. high order bits are sent first. 657 In the IP header of a bootrequest, the client fills in its own IP 658 source address if known, otherwise zero. When the server address is 659 unknown, the IP destination address will be the 'broadcast address' 660 255.255.255.255. This address means 'broadcast on the local cable, 661 (I don't know my net number)' [4]. 663 FIELD BYTES DESCRIPTION 664 ----- ----- --- 666 [...] 667 ciaddr 4 client IP address; 668 filled in by client in bootrequest if known. 670 yiaddr 4 'your' (client) IP address; 671 filled by server if client doesn't 672 know its own address (ciaddr was 0). 674 siaddr 4 server IP address; 675 returned in bootreply by server. 677 giaddr 4 gateway IP address, 678 used in optional cross-gateway booting. 680 Since the packet format is a fixed 300 bytes in length, an updated 681 version of the specification could easily accommodate an additional 682 48 bytes (4 IPv6 fields of 16 bytes to replace the existing 4 IPv4 683 fields of 4 bytes). 685 4.2 RFC 1188 Proposed Standard for the Transmission of IP Datagrams 686 over FDDI Networks 688 This document is clearly informally superceded by RFC 1390, 689 "Transmission of IP and ARP over FDDI Networks", even though no 690 formal deprecation has been done. Therefore, this specification is 691 not considered further in this memo. 693 4.3 RFC 1191 Path MTU discovery 695 The entire process of PMTU discovery is predicated on the use of the 696 DF bit in the IPv4 header, an ICMP message (also IPv4 dependent) and 697 TCP MSS option. This is not compatible with IPv6. 699 4.4 RFC 1356 Multiprotocol Interconnect on X.25 and ISDN 701 Section 3.2 defines an NLPID for IP as follows: 703 The value hex CC (binary 11001100, decimal 204) is IP [6]. 704 Conformance with this specification requires that IP be supported. 705 See section 5.1 for a diagram of the packet formats. 707 Clearly a new NLPID would need to be defined for IPv6 packets. 709 4.5 RFC 1534 Interoperation Between DHCP and BOOTP 711 There are no IPv4 dependencies in this specification. 713 4.6 RFC 1542 Clarifications and Extensions for the Bootstrap Protocol 715 There are no new issues other than those presented in Section 4.1. 717 4.7 RFC 1629 Guidelines for OSI NSAP Allocation in the Internet 719 There are no IPv4 dependencies in this specification. 721 4.8 RFC 1762 The PPP DECnet Phase IV Control Protocol (DNCP) 723 There are no IPv4 dependencies in this specification. 725 4.9 RFC 1989 PPP Link Quality Monitoring 727 There are no IPv4 dependencies in this specification. 729 4.10 RFC 1990 The PPP Multilink Protocol (MP) 731 Section 5.1.3, "Endpoint Discriminator Option", defines a Class 732 header field: 734 Class 735 The Class field is one octet and indicates the identifier 737 address space. The most up-to-date values of the LCP Endpoint 738 Discriminator Class field are specified in the most recent 739 "Assigned Numbers" RFC [7]. Current values are assigned as 740 follows: 742 0 Null Class 744 1 Locally Assigned Address 746 2 Internet Protocol (IP) Address 748 3 IEEE 802.1 Globally Assigned MAC Address 750 4 PPP Magic-Number Block 752 5 Public Switched Network Directory Number 754 A new class field needs to be defined by the IANA for IPv6 addresses. 756 4.11 RFC 1994 PPP Challenge Handshake Authentication Protocol (CHAP) 758 There are no IPv4 dependencies in this specification. 760 4.12 RFC 2067 IP over HIPPI 762 Section 5.1, "Packet Formats", contains the following excerpt: 764 EtherType (16 bits) SHALL be set as defined in Assigned Numbers [8]: 765 IP = 2048 ('0800'h), ARP = 2054 ('0806'h), RARP = 32,821 ('8035'h). 767 Section 5.5, "MTU", has the following definition: 769 The MTU for HIPPI-SC LANs is 65280 bytes. 771 This value was selected because it allows the IP packet to fit in 772 one 64K byte buffer with up to 256 bytes of overhead. The overhead 773 is 40 bytes at the present time; there are 216 bytes of room for 774 expansion. 776 HIPPI-FP Header 8 bytes 777 HIPPI-LE Header 24 bytes 778 IEEE 802.2 LLC/SNAP Headers 8 bytes 779 Maximum IP packet size (MTU) 65280 bytes 780 ------------ 781 Total 65320 bytes (64K - 216) 783 This definition is not applicable for IPv6 packets since packets can 784 be larger than the IPv4 limitation of 65280 bytes. 786 4.13 RFC 2131 Dynamic Host Configuration Protocol 788 This version of DHCP is highly assumptive of IPv4. It is not 789 compatible with IPv6. 791 4.14 RFC 2132 DHCP Options and BOOTP Vendor Extensions 793 This is an extension to an IPv4-only specification. 795 4.15 RFC 2390 Inverse Address Resolution Protocol 797 There are no IPv4 dependencies in this specification. 799 4.16 RFC 2460 Internet Protocol, Version 6 (IPv6) Specification 801 This document defines IPv6 and has no IPv4 issues. 803 4.17 RFC 2461 Neighbor Discovery for IP Version 6 (IPv6) 805 This document defines an IPv6 related specification and has no IPv4 806 issues. 808 4.18 RFC 2462 IPv6 Stateless Address Autoconfiguration 810 This document defines an IPv6 related specification and has no IPv4 811 issues. 813 4.19 RFC 2463 Internet Control Message Protocol (ICMPv6) for the 814 Internet Protocol Version 6 (IPv6) Specification 816 This document defines an IPv6 related specification and has no IPv4 817 issues. 819 4.20 RFC 3596 DNS Extensions to support IP version 6 821 This specification defines the AAAA record for IPv6 as well as PTR 822 records using the ip6.arpa domain, and as such has no IPv6 issues. 824 5. Proposed Standards 826 Proposed Standards are introductory level documents. There are no 827 requirements for even a single implementation. In many cases 828 Proposed are never implemented or advanced in the IETF standards 829 process. They therefore are often just proposed ideas that are 830 presented to the Internet community. Sometimes flaws are exposed or 831 they are one of many competing solutions to problems. In these later 832 cases, no discussion is presented as it would not serve the purpose 833 of this discussion. 835 5.1 RFC 1234 Tunneling IPX traffic through IP networks 837 The section "Unicast Address Mappings" has the following text: 839 For implementations of this memo, the first two octets of the host 840 number will always be zero and the last four octets will be the 841 node's four octet IP address. This makes address mapping trivial 842 for unicast transmissions: the first two octets of the host number 843 are discarded, leaving the normal four octet IP address. The 844 encapsulation code should use this IP address as the destination 845 address of the UDP/IP tunnel packet. 847 This mapping will not be able to work with IPv6 addresses. 849 There are also numerous discussions on systems keeping a "peer list" 850 to map between IP and IPX addresses. The specifics are not discussed 851 in the document and are left to the individual implementation. 853 The section "Maximum Transmission Unit" also has some implications on 854 IP addressing: 856 Although larger IPX packets are possible, the standard maximum 857 transmission unit for IPX is 576 octets. Consequently, 576 octets 858 is the recommended default maximum transmission unit for IPX packets 859 being sent with this encapsulation technique. With the eight octet 860 UDP header and the 20 octet IP header, the resulting IP packets will 861 be 604 octets long. Note that this is larger than the 576 octet 862 maximum size IP implementations are required to accept [3]. Any IP 863 implementation supporting this encapsulation technique must be 864 capable of receiving 604 octet IP packets. 866 As improvements in protocols and hardware allow for larger, 867 unfragmented IP transmission units, the 576 octet maximum IPX packet 868 size may become a liability. For this reason, it is recommended 869 that the IPX maximum transmission unit size be configurable in 870 implementations of this memo. 872 5.2 RFC 1256 ICMP Router Discovery Messages 874 This specification defines a mechanism very specific to IPv4. 876 5.3 RFC 1277 Encoding Network Addresses to Support Operation over 877 Non-OSI Lower Layers 879 Section 4.5, "TCP/IP (RFC 1006) Network Specific Format" describes a 880 structure that reserves 12 digits for the textual representation of 881 an IP address. 883 This 12 octet field for decimal versions of IP addresses is 884 insufficient for a decimal version of IPv6 addresses. It is possible 885 to define a new encoding using the 20 digit long IP Address + Port + 886 Transport Set fields in order to accommodate a binary version of an 887 IPv6 address, port number and Transport Set. There are several 888 schemes that could be envisioned. 890 5.4 RFC 1332 The PPP Internet Protocol Control Protocol (IPCP) 892 This specification defines a mechanism for devices to assign IPv4 893 addresses to PPP clients once PPP negotiation is completed. Section 894 3, "IPCP Configuration Options", defines IPCP option types which 895 embed the IP address in 4-byte long fields. This is clearly not 896 enough for IPv6. 898 However, the specification is clearly designed to allow new Option 899 Types to be added and Should offer no problems for use with IPv6 once 900 appropriate options have been defined. 902 5.5 RFC 1377 The PPP OSI Network Layer Control Protocol (OSINLCP) 904 There are no IPv4 dependencies in this specification. 906 5.6 RFC 1378 The PPP AppleTalk Control Protocol (ATCP) 908 There are no IPv4 dependencies in this specification. 910 5.7 RFC 1469 IP Multicast over Token-Ring Local Area Networks 912 This document defines the usage of IPv4 multicast over IEEE 802.5 913 Token Ring networks. This is not compatible with IPv6. 915 5.8 RFC 1552 The PPP Internetworking Packet Exchange Control Protocol 916 (IPXCP) 918 There are no IPv4 dependencies in this specification. 920 5.9 RFC 1570 PPP LCP Extensions 922 There are no IPv4 dependencies in this specification. 924 5.10 RFC 1598 PPP in X.25 PPP-X25 926 There are no IPv4 dependencies in this specification. 928 5.11 RFC 1618 PPP over ISDN 930 There are no IPv4 dependencies in this specification. 932 5.12 RFC 1663 PPP Reliable Transmission 934 There are no IPv4 dependencies in this specification. 936 5.13 RFC 1752 The Recommendation for the IP Next Generation Protocol 938 This document defines a roadmap for IPv6 development and is not 939 relevant to this discussion. 941 5.14 RFC 1755 ATM Signaling Support for IP over ATM 943 There are no IPv4 dependencies in this specification. 945 5.15 RFC 1763 The PPP Banyan Vines Control Protocol (BVCP) 947 There are no IPv4 dependencies in this specification. 949 5.16 RFC 1764 The PPP XNS IDP Control Protocol (XNSCP) 951 There are no IPv4 dependencies in this specification. 953 5.17 RFC 1973 PPP in Frame Relay 955 There are no IPv4 dependencies in this specification. 957 5.18 RFC 1981 Path MTU Discovery for IP version 6 959 This specification describes an IPv6 related specification and is not 960 discussed in this document. 962 5.19 RFC 1982 Serial Number Arithmetic 964 There are no IPv4 dependencies in this specification. 966 5.20 5.21 RFC 1995 Incremental Zone Transfer in DNS 968 Although the examples used in this document use IPv4 addresses, 969 (i.e., A records) there is nothing in the specification to preclude 970 full and proper functionality using IPv6. 972 5.21 RFC 1996 A Mechanism for Prompt Notification of Zone Changes (DNS 973 NOTIFY) 975 There are no IPv4 dependencies in this specification. 977 5.22 RFC 2003 IP Encapsulation within IP 979 This document is designed for use in IPv4 networks. There are many 980 references to a specified IP version number of 4 and 32-bit 981 addresses. This is incompatible with IPv6. 983 5.23 RFC 2004 Minimal Encapsulation within IP 985 This document is designed for use in IPv4 networks. There are many 986 references to a specified IP version number of 4 and 32-bit 987 addresses. This is incompatible with IPv6. 989 5.24 RFC 2005 Applicability Statement for IP Mobility Support 991 This specification documents the interoperation of IPv4 Mobility 992 Support; this is not relevant to this discussion. 994 5.25 RFC 2022 Support for Multicast over UNI 3.0/3.1 based ATM Networks 996 This specification specifically maps IPv4 multicast in UNI based ATM 997 networks. This is incompatible with IPv6. 999 5.26 RFC 2043 The PPP SNA Control Protocol (SNACP) 1001 There are no IPv4 dependencies in this specification. 1003 5.27 RFC 2097 The PPP NetBIOS Frames Control Protocol (NBFCP) 1005 There are no IPv4 dependencies in this specification. 1007 5.28 RFC 2113 IP Router Alert Option 1009 This document provides a new mechanism for IPv4. This is incompatible 1010 with IPv6. 1012 5.29 RFC 2125 The PPP Bandwidth Allocation Protocol (BAP) / The PPP 1013 Bandwidth Allocation Control Protocol (BACP) 1015 There are no IPv4 dependencies in this specification. 1017 5.30 RFC 2136 Dynamic Updates in the Domain Name System (DNS UPDATE) 1019 There are no IPv4 dependencies in this specification. 1021 5.31 RFC 2181 Clarifications to the DNS Specification 1023 There are no IPv4 dependencies in this specification. The only 1024 reference to IP addresses discuss the use of an anycast address, so 1025 but one can assume that these techniques are IPv6 operable. 1027 5.32 RFC 2225 Classical IP and ARP over ATM 1029 From the many references in this document it is clear that this 1030 document is designed for IPv4 only. It is only later in the document 1031 that it is implicitly stated, as in: 1033 ar$spln - length in octets of the source protocol address. Value 1034 range is 0 or 4 (decimal). For IPv4 ar$spln is 4. 1036 ar$tpln - length in octets of the target protocol address. Value 1037 range is 0 or 4 (decimal). For IPv4 ar$tpln is 4. 1039 and: 1041 For backward compatibility with previous implementations, a null 1042 IPv4 protocol address may be received with length = 4 and an 1043 allocated address in storage set to the value 0.0.0.0. Receiving 1044 stations must be liberal in accepting this format of a null IPv4 1045 address. However, on transmitting an ATMARP or InATMARP packet, a 1046 null IPv4 address must only be indicated by the length set to zero 1047 and must have no storage allocated. 1049 5.33 RFC 2226 IP Broadcast over ATM Networks 1051 This document is limited to IPv4 multicasting. This is incompatible 1052 with IPv6. 1054 5.34 RFC 2241 DHCP Options for Novell Directory Services 1056 This is an extension to an IPv4-only specification. 1058 5.35 RFC 2242 NetWare/IP Domain Name and Information 1060 This is an extension to an IPv4-only specification, for example: 1062 PREFERRED_DSS (code 6) 1064 Length is (n * 4) and the value is an array of n IP addresses, 1065 each four bytes in length. The maximum number of addresses is 5 1066 and therefore the maximum length value is 20. The list contains 1067 the addresses of n NetWare Domain SAP/RIP Server (DSS). 1069 NEAREST_NWIP_SERVER (code 7) 1071 Length is (n * 4) and the value is an array of n IP addresses, 1072 each four bytes in length. The maximum number of addresses is 5 1073 and therefore the maximum length value is 20. The list contains 1074 the addresses of n Nearest NetWare/IP servers. 1076 PRIMARY_DSS (code 11) 1078 Length of 4, and the value is a single IP address. This field 1080 identifies the Primary Domain SAP/RIP Service server (DSS) for 1081 this NetWare/IP domain. NetWare/IP administration utility uses 1082 this value as Primary DSS server when configuring a secondary 1083 DSS server. 1085 5.36 RFC 2290 Mobile-IPv4 Configuration Option for PPP IPCP 1087 This document is designed for use with Mobile IPv4. There are 1088 numerous referrals to other IP "support" mechanisms (i.e. ICMP Router 1089 Discover Messages) that specifically refer to the IPv4 of ICMP. 1091 5.37 RFC 2308 Negative Caching of DNS Queries (DNS NCACHE) 1093 Although there are numerous examples in this document that use IPv4 1094 "A" records, there is nothing in the specification that limits its 1095 effectiveness to IPv4. 1097 5.38 RFC 2331 ATM Signaling Support for IP over ATM - UNI Signaling 4.0 1098 Update 1100 There are no IPv4 dependencies in this specification. 1102 5.39 RFC 2332 NBMA Next Hop Resolution Protocol (NHRP) 1104 This document is very generic in its design and seems to be able to 1105 support numerous layer 3 addressing schemes and should include both 1106 IPv4 and IPv6. 1108 5.40 RFC 2333 NHRP Protocol Applicability 1110 This document is very generic in its design and seems to be able to 1111 support numerous layer 3 addressing schemes and should include both 1112 IPv4 and IPv6. 1114 5.41 RFC 2335 A Distributed NHRP Service Using SCSP 1116 There are no IPv4 dependencies in this specification. 1118 5.42 RFC 2363 PPP Over FUNI 1120 There are no IPv4 dependencies in this specification. 1122 5.43 RFC 2364 PPP Over AAL5 1124 There are no IPv4 dependencies in this specification. 1126 5.44 RFC 2371 Transaction Internet Protocol Version 3.0 (TIPV3) 1128 This document states: 1130 TIP transaction manager addresses take the form: 1132 1134 The component comprises: 1136 [:] 1138 where is either a or an ; and 1139 is a decimal number specifying the port at which the transaction 1140 manager (or proxy) is listening for requests to establish TIP 1141 connections. If the port number is omitted, the standard TIP port 1142 number (3372) is used. 1144 A is a standard name, acceptable to the domain name 1145 service. It must be sufficiently qualified to be useful to the 1146 receiver of the command. 1148 An is an IP address, in the usual form: four decimal 1149 numbers separated by period characters. 1151 And further along it states: 1153 A TIP URL takes the form: 1155 tip://? 1157 where identifies the TIP transaction 1158 manager (as defined in Section 7 above); and 1159 specifies a transaction identifier, which may take one of two forms 1160 (standard or non-standard): 1162 i. "urn:" ":" 1164 A standard transaction identifier, conforming to the proposed 1165 Internet Standard for Uniform Resource Names (URNs), as specified 1166 by RFC2141; where is the Namespace Identifier, and is 1167 the Namespace Specific String. The Namespace ID determines the 1168 syntactic interpretation of the Namespace Specific String. The 1169 Namespace Specific String is a sequence of characters representin 1170 a transaction identifier (as defined by ). The rules for the 1171 contents of these fields are specified by [6] (valid characters, 1172 encoding, etc.). 1174 This format of may be used to express global 1175 transaction identifiers in terms of standard representations. 1176 Examples for might be or . e.g. 1178 tip://123.123.123.123/?urn:xopen:xid 1180 Note that Namespace Ids require registration. See [7] for details 1181 on how to do this. 1183 ii. 1185 A sequence of printable ASCII characters (octets with values in 1186 the range 32 through 126 inclusive (excluding ":") representing a 1187 transaction identifier. In this non-standard case, it is the 1188 combination of and which ensures global uniqueness. e.g. 1191 tip://123.123.123.123/?transid1 1193 These are incompatible with IPv6. 1195 5.45 RFC 2464 Transmission of IPv6 Packets over Ethernet Networks 1197 This specification documents a method for transmitting IPv6 packets 1198 over Ethernet and is not considered in this discussion. 1200 5.46 RFC 2467 Transmission of IPv6 Packets over FDDI Networks 1202 This specification documents a method for transmitting IPv6 packets 1203 over FDDI and is not considered in this discussion. 1205 5.47 RFC 2470 Transmission of IPv6 Packets over Token Ring Networks 1207 This specification documents a method for transmitting IPv6 packets 1208 over Token Ring and is not considered in this discussion. 1210 5.48 RFC 2472 IP Version 6 over PPP 1212 This specification documents a method for transmitting IPv6 packets 1213 over PPP and is not considered in this discussion. 1215 5.49 RFC 2473 Generic Packet Tunneling in IPv6 Specification 1217 This specification documents an IPv6 aware specification and is not 1218 considered in this discussion. 1220 5.50 RFC 2484 PPP LCP Internationalization Configuration Option 1222 There are no IPv4 dependencies in this specification. 1224 5.51 RFC 2485 DHCP Option for The Open Group's User Authentication 1225 Protocol 1227 This is an extension to an IPv4-only specification. 1229 5.52 RFC 2486 The Network Access Identifier 1231 There are no IPv4 dependencies in this specification. 1233 5.53 RFC 2491 IPv6 over Non-Broadcast Multiple Access (NBMA) networks 1235 This specification documents a method for transmitting IPv6 packets 1236 over NBMA networks and is not considered in this discussion. 1238 5.54 RFC 2492 IPv6 over ATM Networks 1240 This specification documents a method for transmitting IPv6 packets 1241 over ATM networks and is not considered in this discussion. 1243 5.55 RFC 2497 Transmission of IPv6 Packets over ARCnet Networks 1245 This specification documents a method for transmitting IPv6 packets 1246 over ARCnet networks and is not considered in this discussion. 1248 5.56 RFC 2507 IP Header Compression 1250 This specification is both IPv4 and IPv6 aware. 1252 5.57 RFC 2526 Reserved IPv6 Subnet Anycast Addresses 1254 This specification documents IPv6 addressing and is not discussed in 1255 this document. 1257 5.58 RFC 2529 Transmission of IPv6 over IPv4 Domains without Explicit 1258 Tunnels 1260 This specification documents IPv6 transmission methods and is not 1261 discussed in this document. 1263 5.59 RFC 2563 DHCP Option to Disable Stateless Auto-Configuration in 1264 IPv4 Clients 1266 This is an extension to an IPv4-only specification. 1268 5.60 RFC 2590 Transmission of IPv6 Packets over Frame Relay Networks 1269 Specification 1271 This specification documents IPv6 transmission method over Frame 1272 Relay and is not discussed in this document. 1274 5.61 RFC 2601 ILMI-Based Server Discovery for ATMARP 1276 This specification is both IPv4 and IPv6 aware. 1278 5.62 RFC 2602 ILMI-Based Server Discovery for MARS 1280 This specification is both IPv4 and IPv6 aware. 1282 5.63 RFC 2603 ILMI-Based Server Discovery for NHRP 1284 This specification is both IPv4 and IPv6 aware. 1286 5.64 RFC 2610 DHCP Options for Service Location Protocol 1288 This is an extension to an IPv4-only specification. 1290 5.65 RFC 2615 PPP over SONET/SDH 1292 There are no IPv4 dependencies in this specification. 1294 5.66 RFC 2625 IP and ARP over Fibre Channel 1296 This document states: 1298 Objective and Scope: 1300 The major objective of this specification is to promote 1301 interoperable implementations of IPv4 over FC. This specification 1302 describes a method for encapsulating IPv4 and Address Resolution 1303 Protocol (ARP) packets over FC. 1305 This is incompatible with IPv6. 1307 5.67 RFC 2661 Layer Two Tunneling Protocol (L2TP) 1309 There are no IPv4 dependencies in this specification. 1311 5.68 RFC 2671 Extension Mechanisms for DNS (EDNS0) 1313 There are no IPv4 dependencies in this specification. 1315 5.69 RFC 2672 Non-Terminal DNS Name Redirection 1317 This document is only defined for IPv4 addresses. An IPv6 1318 specification may be needed. 1320 5.70 RFC 2673 Binary Labels in the Domain Name System 1322 This document is only defined for IPv4 addresses. An IPv6 1323 specification may be needed. 1325 5.71 RFC 2675 IPv6 Jumbograms 1327 This document defines a IPv6 packet format and is therefore not 1328 discussed in this document. 1330 5.72 RFC 2684 Multiprotocol Encapsulation over ATM Adaptation Layer 5 1332 There are no IPv4 dependencies in this specification. 1334 5.73 RFC 2685 Virtual Private Networks Identifier 1336 There are no IPv4 dependencies in this specification. 1338 5.74 RFC 2686 The Multi-Class Extension to Multi-Link PPP 1340 There are no IPv4 dependencies in this specification. 1342 5.75 RFC 2687 PPP in a Real-time Oriented HDLC-like Framing 1344 There are no IPv4 dependencies in this specification. 1346 5.76 RFC 2688 Integrated Services Mappings for Low Speed Networks 1348 There are no IPv4 dependencies in this specification. 1350 5.77 RFC 2710 Multicast Listener Discovery (MLD) for IPv6 1352 This document defines an IPv6 specific specification and is not 1353 discussed in this document. 1355 5.78 RFC 2711 IPv6 Router Alert Option 1357 This document defines an IPv6 specific specification and is not 1358 discussed in this document. 1360 5.79 RFC 2728 The Transmission of IP Over the Vertical Blanking Interval 1361 of a Television Signal 1363 The following data format is defined: 1365 0 1 2 3 1366 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 1367 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1368 |0| group | uncompressed IP header (20 bytes) | 1369 +-+-+-+-+-+-+-+-+ + 1370 | | 1371 : .... : 1372 + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1373 | | uncompressed UDP header (8 bytes) | 1374 +-+-+-+-+-+-+-+-+ + 1375 | | 1376 + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1377 | | payload (<1472 bytes) | 1378 +-+-+-+-+-+-+-+-+ + 1379 | | 1380 : .... : 1381 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1382 | CRC | 1383 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1385 This is incompatible with IPv6. 1387 5.80 RFC 2734 IPv4 over IEEE 1394 1389 This specification is IPv4 only. 1391 5.81 RFC 2735 NHRP Support for Virtual Private Networks 1393 This specification implies only IPv4 operations, but does not seem to 1394 present any reason that it would not function for IPv6. 1396 5.82 RFC 2765 Stateless IP/ICMP Translation Algorithm (SIIT) 1398 This specification defines a method for IPv6 transition and is not 1399 discussed in this document. 1401 5.83 RFC 2766 Network Address Translation - Protocol Translation 1402 (NAT-PT) 1404 This specification defines a method for IPv6 transition and is not 1405 discussed in this document. 1407 5.84 RFC 2776 Multicast-Scope Zone Announcement Protocol (MZAP) 1409 This specification is both IPv4 and IPv6 aware and needs no changes. 1411 5.85 RFC 2782 A DNS RR for specifying the location of services 1413 There are no IPv4 dependencies in this specification. 1415 5.86 RFC 2794 Mobile IP Network Access Identifier Extension for IPv4 1417 This is an extension to an IPv4-only specification. 1419 5.87 RFC 2834 ARP and IP Broadcast over HIPPI-800 1421 This document uses the generic term "IP Address" in the text but it 1422 also contains the text: 1424 The HARP message has several fields that have the following format 1425 and values: 1427 Data sizes and field meaning: 1428 ar$hrd 16 bits Hardware type 1429 ar$pro 16 bits Protocol type of the protocol fields below 1430 ar$op 16 bits Operation code (request, reply, or NAK) 1431 ar$pln 8 bits byte length of each protocol address 1432 ar$rhl 8 bits requester's HIPPI hardware address length (q) 1433 ar$thl 8 bits target's HIPPI hardware address length (x) 1434 ar$rpa 32 bits requester's protocol address 1435 ar$tpa 32 bits target's protocol address 1436 ar$rha qbytes requester's HIPPI Hardware address 1437 ar$tha xbytes target's HIPPI Hardware address 1439 Where : 1440 ar$hrd - SHALL contain 28. (HIPARP) 1442 ar$pro - SHALL contain the IP protocol code 2048 (decimal). 1444 ar$op - SHALL contain the operational value (decimal): 1445 1 for HARP_REQUESTs 1446 2 for HARP_REPLYs 1447 8 for InHARP_REQUESTs 1448 9 for InHARP_REPLYs 1449 10 for HARP_NAK 1450 ar$pln - SHALL contain 4. 1452 And later: 1454 31 28 23 21 15 10 7 2 0 1455 +-----+---------+-+-+-----------+---------+-----+---------+-----+ 1456 0 | 04 |1|0| 000 | 03 | 0 | 1457 +---------------+-+-+---------------------+---------------+-----+ 1458 1 | 45 | 1459 +-----+-+-------+-----------------------+-----------------------+ 1460 2 |[LA] |W|MsgT= 0| 000 | Dest. Switch Addr | 1461 +-----+-+-------+-----------------------+-----------------------+ 1462 3 | 2 | 2 | 000 | Source Switch Addr | 1463 +---------------+---------------+-------+-----------------------+ 1464 4 | 00 00 | | 1465 +-------------------------------+ | 1466 5 | Destination ULA | 1467 +-------------------------------+-------------------------------+ 1468 6 | [LA] | | 1469 +-------------------------------+ | 1470 7 | Source ULA | 1471 +===============+===============+===============+===============+ 1473 8 | AA | AA | 03 | 00 | 1474 +---------------+---------------+---------------+---------------+ 1475 9 | 00 | 00 | Ethertype (2054) | 1476 +---------------+---------------+-------------------------------+ 1477 10 | hrd (28) | pro (2048) | 1478 +---------------+---------------+---------------+---------------+ 1479 11 | op (ar$op) | pln (6) | rhl (q) | 1480 +---------------+---------------+---------------+---------------+ 1481 12 | thl = (x) | Requester IP Address upper (24 bits) | 1482 +---------------------------------------------------------------+ 1483 13 | Req. IP lower | Target IP Address upper (24 bits) | 1484 +---------------+-----------------------------------------------+ 1485 14 | Tgt. IP lower | Requester HIPPI Hardware Address bytes 0 - 2 | 1486 +---------------+-----------------------------------------------+ 1487 15 | Requester HIPPI Hardware Address bytes 3 - 6 | 1488 +-----------------------------------------------+---------------+ 1489 16 | Requester HW Address bytes 7 - q | Tgt HW byte 0 | 1490 +---------------+---------------+---------------+---------------+ 1491 17 | Target HIPPI Hardware Address bytes 1 - 4 | 1492 +---------------------------------------------------------------+ 1493 18 | Target HIPPI Hardware Address bytes 5 - 8 | 1494 +---------------+---------------+---------------+---------------+ 1495 19 |Tgt HW byte 9-x| FILL | FILL | FILL | 1496 +---------------+---------------+---------------+---------------+ 1497 HARP - InHARP Message 1499 This is incompatible with IPv6. 1501 5.88 RFC 2835 IP and ARP over HIPPI-6400 1503 This document states: 1505 The Ethertype value SHALL be set as defined in Assigned Numbers 1506 [18]: 1508 IP 0x0800 2048 (16 bits) 1510 This is limited to IPv4, and similar to the previous section, 1511 incompatible with IPv6. There are numerous other points in the 1512 documents that confirm this assumption. 1514 5.89 RFC 2855 DHCP for IEEE 1394 1516 This is an extension to an IPv4-only specification. 1518 5.90 RFC 2874 DNS Extensions to Support IPv6 Address Aggregation and 1519 Renumbering 1521 This document defines a specification to interact with IPv6 and is 1522 not considered in this document. 1524 5.91 RFC 2893 Transition Mechanisms for IPv6 Hosts and Routers 1526 This document defines a transition mechanism for IPv6 and is not 1527 considered in this document. 1529 5.92 RFC 2916 E.164 number and DNS 1531 There are no IPv4 dependencies in this specification. 1533 5.93 RFC 2937 The Name Service Search Option for DHCP 1535 This is an extension to an IPv4-only specification. 1537 5.94 RFC 3004 The User Class Option for DHCP 1539 This is an extension to an IPv4-only specification. 1541 5.95 RFC 3011 The IPv4 Subnet Selection Option for DHCP 1543 This is an extension to an IPv4-only specification. 1545 5.96 RFC 3021 Using 31-Bit Prefixes for IPv4 P2P Links 1547 This specification is specific to IPv4 address architecture, where a 1548 modification was needed to use both addresses of a 31-bit prefix. 1549 This is possible by IPv6 address architecture, but in most cases not 1550 recommended; see RFC 3627, Use of /127 Prefix Length Between Routers 1551 Considered Harmful. 1553 5.97 RFC 3024 Reverse Tunneling for Mobile IP, revised 1555 This is an extension to an IPv4-only specification. 1557 5.98 RFC 3046 DHCP Relay Agent Information Option 1559 This is an extension to an IPv4-only specification. 1561 5.99 RFC 3056 Connection of IPv6 Domains via IPv4 Clouds 1563 This is an IPv6 related document and is not discussed in this 1564 document. 1566 5.100 RFC 3068 An Anycast Prefix for 6to4 Relay Routers 1568 This is an IPv6 related document and is not discussed in this 1569 document. 1571 5.101 RFC 3070 Layer Two Tunneling Protocol (L2TP) over Frame Relay 1573 There are no IPv4 dependencies in this specification. 1575 5.102 RFC 3074 DHC Load Balancing Algorithm 1577 There are no IPv4 dependencies in this specification. 1579 5.103 RFC 3077 A Link-Layer Tunneling Mechanism for Unidirectional Links 1581 This specification is both IPv4 and IPv6 aware and needs no changes. 1583 5.104 RFC 3115 Mobile IP Vendor/Organization-Specific Extensions 1585 This is an extension to an IPv4-only specification. 1587 5.105 RFC 3145 L2TP Disconnect Cause Information 1589 There are no IPv4 dependencies in this specification. 1591 5.106 RFC 3344 IP Mobility Support for IPv4 1593 There are IPv4 dependencies in this specification. 1595 5.107 RFC 3376 Internet Group Management Protocol, Version 3 1597 This document describes of version of IGMP used for IPv4 multicast. 1598 This is not compatible with IPv6. 1600 5.108 RFC 3402 Dynamic Delegation Discovery System (DDDS) Part Two: The 1601 Algorithm 1603 There are no IPv4 dependencies in this specification. 1605 5.109 RFC 3403 Dynamic Delegation Discovery System (DDDS) Part Three: 1606 The Domain Name System (DNS) Database 1608 There are no IPv4 dependencies in this specification. 1610 5.110 RFC 3513 IP Version 6 Addressing Architecture 1612 This specification documents IPv6 addressing and is not discussed in 1613 this document. 1615 5.111 RFC 3518 Point-to-Point Protocol (PPP) Bridging Control Protocol 1616 (BCP) 1618 There are no IPv4 dependencies in this specification. 1620 6. Experimental RFCs 1622 Experimental RFCs typically define protocols that do not have 1623 widescale implementation or usage on the Internet. They are often 1624 propriety in nature or used in limited arenas. They are documented 1625 to the Internet community in order to allow potential 1626 interoperability or some other potential useful scenario. In a few 1627 cases they are presented as alternatives to the mainstream solution 1628 to an acknowledged problem. 1630 6.1 RFC 1149 Standard for the transmission of IP datagrams on avian 1631 carriers 1633 There are no IPv4 dependencies in this specification. In fact the 1634 flexibility of this specification is such that all versions of IP 1635 should function within its boundaries, presuming that the packets 1636 remain small enough to be transmitted with the 256 milligrams weight 1637 limitations. 1639 6.2 RFC 1183 New DNS RR Definitions 1641 There are no IPv4 dependencies in this specification. 1643 6.3 RFC 1226 Internet protocol encapsulation of AX.25 frames 1645 There are no IPv4 dependencies in this specification. 1647 6.4 RFC 1241 Scheme for an internet encapsulation protocol: Version 1 1649 This specification defines a specification that assumes IPv4 but does 1650 not actually have any limitations which would limit its operation in 1651 an IPv6 environment. 1653 6.5 RFC 1307 Dynamically Switched Link Control Protocol 1655 This specification is IPv4 dependent, for example: 1657 3.1 Control Message Format 1659 0 1 2 3 1660 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 1661 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1662 | Identifier | Total length | 1663 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1664 | Function | Event Status | 1665 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1666 | Endpoint 1 | 1667 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1668 | Endpoint 2 | 1669 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1670 | Message | 1671 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1672 | Body | 1673 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1675 Endpoint addresses: 32 bits each 1677 The internet addresses of the two communicating parties for 1678 which the link is being prepared. 1680 6.6 RFC 1393 Traceroute Using an IP Option 1682 This document uses an IPv4 option. It is therefore limited to IPv4 1683 networks, and is incompatible with IPv6. 1685 6.7 RFC 1433 Directed ARP 1687 There are no IPv4 dependencies in this specification. 1689 6.8 RFC 1464 Using the Domain Name System To Store Arbitrary String 1690 Attributes 1692 There are no IPv4 dependencies in this specification. 1694 6.9 RFC 1475 TP/IX: The Next Internet 1696 This document defines IPv7 and has been abandoned by the IETF as a 1697 feasible design. It is not considered in this document. 1699 6.10 RFC 1561 Use of ISO CLNP in TUBA Environments 1701 This document defines the use of NSAP addressing and does not use any 1702 version of IP, so there are no IPv4 dependencies in this 1703 specification. 1705 6.11 RFC 1712 DNS Encoding of Geographical Location 1707 There are no IPv4 dependencies in this specification. 1709 6.12 RFC 1735 NBMA Address Resolution Protocol (NARP) 1711 This document defines a specification that is IPv4 specific, for 1712 example: 1714 4. Packet Formats 1716 NARP requests and replies are carried in IP packets as protocol type 1717 54. This section describes the packet formats of NARP requests and 1718 replies: 1720 NARP Request 1722 0 1 2 3 1723 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 1724 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1725 | Version | Hop Count | Checksum | 1726 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1727 | Type | Code | Unused | 1728 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1729 | Destination IP address | 1730 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1731 | Source IP address | 1732 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1733 | NBMA length | NBMA address | 1734 +-+-+-+-+-+-+-+-+ | 1735 | (variable length) | 1736 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1738 Source and Destination IP Addresses 1739 Respectively, these are the IP addresses of the NARP requestor 1740 and the target terminal for which the NBMA address is desired. 1742 And: 1744 NARP Reply 1746 0 1 2 3 1747 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 1748 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1749 | Version | Hop Count | Checksum | 1750 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1751 | Type | Code | Unused | 1752 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1753 | Destination IP address | 1754 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1755 | Source IP address | 1756 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1757 | NBMA length | NBMA address | 1758 +-+-+-+-+-+-+-+-+ | 1759 | (variable length) | 1760 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1762 Source and Destination IP Address 1763 Respectively, these are the IP addresses of the NARP requestor 1764 and the target terminal for which the NBMA address is desired. 1766 This is incompatible with IPv6. 1768 6.13 RFC 1768 Host Group Extensions for CLNP Multicasting 1770 This specification defines multicasting for CLNP, which is not an IP 1771 protocol, and therefore has no IPv4 dependencies. 1773 6.14 RFC 1788 ICMP Domain Name Messages 1775 This specification is used for updates to the in-addr.arpa reverse 1776 DNS maps, and is limited to IPv4. 1778 6.15 RFC 1797 Class A Subnet Experiment 1780 This document is specific to IPv4 address architecture, and as such, 1781 has no IPv6 dependencies. 1783 6.16 RFC 1819 Internet Stream Protocol Version 2 (ST2) Protocol 1784 Specification - Version ST2+ 1786 This specification is IPv4 limited. In fact it is the definition of 1787 IPv5. It has been abandoned by the IETF as feasible design, and is 1788 not considered in this discussion. 1790 6.17 RFC 1868 ARP Extension - UNARP 1792 This specification defines an extension to IPv4 ARP to delete entries 1793 from ARP caches on a link. 1795 6.18 RFC 1876 A Means for Expressing Location Information in the Domain 1796 Name System 1798 This document defines a methodology for applying this technology 1799 which is IPv4 dependent. The specification itself has no IPv4 1800 dependencies. 1802 6.19 RFC 1888 OSI NSAPs and IPv6 1804 This is an IPv6 related document and is not discussed in this 1805 document. 1807 6.20 RFC 2009 GPS-Based Addressing and Routing 1809 The document states: 1811 The future version of IP (IP v6) will certainly have a sufficient 1812 number of bits in its addressing space to provide an address for 1813 even smaller GPS addressable units. In this proposal, however, we 1814 assume the current version of IP (IP v4) and we make sure that we 1815 manage the addressing space more economically than that. We will 1816 call the smallest GPS addressable unit a GPS-square. 1818 This specification does not seem to have real IPv4 dependencies. 1820 6.21 RFC 2143 Encapsulating IP with the SCSI 1822 This specification will only operate using IPv4. As stated in the 1823 document: 1825 It was decided that the ten byte header offers the greatest 1826 flexibility for encapsulating version 4 IP datagrams for the 1827 following reasons: [...] 1829 This is incompatible with IPv6. 1831 6.22 RFC 2345 Domain Names and Company Name Retrieval 1833 There are no IPv4 dependencies in this specification. 1835 6.23 RFC 2443 A Distributed MARS Service Using SCSP 1837 This document gives default values for use on IPv4 networks, but is 1838 designed to be extensible so it will work with IPv6 with appropriate 1839 IANA definitions. 1841 6.24 RFC 2471 IPv6 Testing Address Allocation 1843 This is an IPv6 related document and is not discussed in this 1844 document. 1846 6.25 RFC 2520 NHRP with Mobile NHCs 1848 This specification is both IPv4 and IPv6 aware and needs no changes. 1850 6.26 RFC 2521 ICMP Security Failures Messages 1852 There are no IPv4 dependencies in this specification. 1854 6.27 RFC 2540 Detached Domain Name System (DNS) Information 1856 There are no IPv4 dependencies in this specification. 1858 6.28 RFC 2823 PPP over Simple Data Link (SDL) using SONET/SDH with 1859 ATM-like framing 1861 There are no IPv4 dependencies in this specification. 1863 6.29 RFC 3123 A DNS RR Type for Lists of Address Prefixes 1865 This specification is both IPv4 and IPv6 aware and needs no changes. 1867 6.30 RFC 3168 The Addition of Explicit Congestion Notification (ECN) to 1868 IP 1870 This specification is both IPv4 and IPv6 aware and needs no changes. 1872 6.31 RFC 3180 GLOP Addressing in 233/8 1874 This document is specific to IPv4 multicast addressing. 1876 7. Summary of the Results 1878 In the initial survey of RFCs 52 positives were identified out of a 1879 total of 186, broken down as follows: 1881 Standards 17 of 24 or 70.83% 1883 Draft Standards 6 of 20 or 30.00% 1885 Proposed Standards 22 of 111 or 19.91% 1887 Experimental RFCs 7 of 31 or 22.58% 1889 Of those identified many require no action because they document 1890 outdated and unused protocols, while others are document protocols 1891 that are actively being updated by the appropriate working groups. 1892 Additionally there are many instances of standards that should be 1893 updated but do not cause any operational impact if they are not 1894 updated. 1896 7.1 Standards 1898 7.1.1 RFC 791 Internet Protocol 1900 RFC 791 has been updated in the definition of IPv6 in RFC 2460. 1902 7.1.2 RFC 792 Internet Control Message Protocol 1904 RFC 792 has been updated in the definition of ICMPv6 in RFC 2463. 1906 7.1.3 RFC 891 DCN Networks 1908 DCN has long since been ceased to be used, so this specification is 1909 no longer relevant. 1911 7.1.4 RFC 894 IP over Ethernet 1913 This problem has been fixed by RFC2464, A Method for the Transmission 1914 of IPv6 Packets over Ethernet Networks. 1916 7.1.5 RFC 895 IP over experimental Ethernets 1918 It is believed that experimental Ethernet networks are not being used 1919 anymore, so the specification is no longer relevant. 1921 7.1.6 RFC 922 Broadcasting Internet Datagrams in the Presence of Subnets 1923 Broadcasting is not used in IPv6, but similar functionality has been 1924 included in RFC 3513, IPv6 Addressing Architecture. 1926 7.1.7 RFC 950 Internet Standard Subnetting Procedure 1928 Broadcasting is not used in IPv6, but similar functionality has been 1929 included in RFC 3513, IPv6 Addressing Architecture. 1931 7.1.8 RFC 1034 Domain Names: Concepts and Facilities 1933 The problems have been fixed by defining new resource records for 1934 IPv6 addresses. 1936 7.1.9 RFC 1035 Domain Names: Implementation and Specification 1938 The problems have been fixed by defining new resource records for 1939 IPv6 addresses. 1941 7.1.10 RFC 1042 IP over IEEE 802 1943 This problem has been fixed by RFC2470, Transmission of IPv6 Packets 1944 over Token Ring Networks. 1946 7.1.11 RFC 1044 IP over HyperChannel 1948 No updated document exists for this specification. It is unclear 1949 whether one is needed. 1951 7.1.12 RFC 1088 IP over NetBIOS 1953 No updated document exists for this specification. It is unclear 1954 whether one is needed. 1956 7.1.13 RFC 1112 Host Extensions for IP Multicast 1958 The IPv4-specific parts of RFC 1112 have been updated in RFC 2710, 1959 Multicast Listener Discovery for IPv6. 1961 7.1.14 RFC 1122 Requirements for Internet Hosts 1963 RFC 1122 is essentially a requirements document for IPv4 hosts. 1964 Similar work is in progress 1965 (draft-ietf-ipv6-node-requirements-xx.txt). 1967 7.1.15 RFC 1201 IP over ARCNET 1969 This problem has been fixed by RFC 2497, A Method for the 1970 Transmission of IPv6 Packets over ARCnet Networks. 1972 7.1.16 RFC 1209 IP over SMDS 1974 No updated document exists for this specification. It is unclear 1975 whether one is needed. 1977 7.1.17 RFC 1390 Transmission of IP and ARP over FDDI Networks 1979 This problem has been fixed by RFC 2467, "Transmission of IPv6 1980 Packets over FDDI Networks". 1982 7.2 Draft Standards 1984 7.2.1 RFC 951 Bootstrap Protocol (BOOTP) 1986 This problem has been fixed by RFC 2462, IPv6 Stateless Address 1987 Autoconfiguration, and RFC3315, Dynamic Host Configuration Protocol 1988 for IPv6 (DHCPv6). 1990 7.2.2 RFC 1191 Path MTU Discovery 1992 This problem has been fixed in RFC 1981, Path MTU Discovery for IP 1993 version 6. 1995 7.2.3 RFC 1356 Multiprotocol Interconnect on X.25 and ISDN 1997 This problem can be fixed by defining a new NLPID for IPv6. Note that 1998 an NLPID has already been defined in RFC 2427, Multiprotocol 1999 Interconnect over Frame Relay. 2001 7.2.4 RFC 1990 The PPP Multilink Protocol (MP) 2003 A new class identifier ("6") for IPv6 packets has been registered 2004 with the IANA by the original author, fixing this problem. 2006 7.2.5 RFC 2067 IP over HIPPI 2008 No updated document exists for this specification. It is unclear 2009 whether one is needed. 2011 7.2.6 RFC 2131 DHCP 2013 This problem has been fixed in RFC 3315, Dynamic Host Configuration 2014 Protocol for IPv6 (DHCPv6). 2016 Further, the consensus of the DHC WG has been that the options 2017 defined for DHCPv4 will not be automatically "carried forward" to 2018 DHCPv6. Therefore, any further analysis of additionally specified 2019 DHCPv4 Options has been omitted from this memo. 2021 7.3 Proposed Standards 2023 7.3.1 RFC 1234 Tunneling IPX over IP 2025 No updated document exists for this specification. In practice, the 2026 similar effect can be achieved by the use of a layer 2 tunneling 2027 protocol. It is unclear whether an updated document is needed. 2029 7.3.2 RFC 1256 ICMP Router Discovery 2031 This problem has been resolved in RFC 2461, Neighbor Discovery for IP 2032 Version 6 (IPv6). 2034 7.3.3 RFC 1277 Encoding Net Addresses to Support Operation Over Non OSI 2035 Lower Layers 2037 No updated document exists for this specification; the problem might 2038 be resolved by the creation of a new encoding scheme if necessary. It 2039 is unclear whether an update is needed. 2041 7.3.4 RFC 1332 PPP Internet Protocol Control Protocol (IPCP) 2043 This problem has been resolved in RFC 2472, IP Version 6 over PPP. 2045 7.3.5 RFC 1469 IP Multicast over Token Ring 2047 The functionality of this specification has been essentially covered 2048 in RFC 2470, Transmission of IPv6 Packets over Token Ring Networks. 2050 7.3.6 RFC 2003 IP Encapsulation within IP 2052 This problem has been fixed by defining different IP-in-IP 2053 encapsulation, for example, RFC 2473, Generic Packet Tunneling in 2054 IPv6 Specification. 2056 7.3.7 RFC 2004 Minimal Encapsulation within IP 2058 No updated document exists for this specification. It is unclear 2059 whether one is needed. 2061 7.3.8 RFC 2022 Support for Multicast over UNI 3.0/3.1 based ATM Networks 2063 No updated document exists for this specification. It is unclear 2064 whether one is needed. 2066 7.3.9 RFC 2113 IP Router Alert Option 2068 This problem has been fixed in RFC 2711, IPv6 Router Alert Option. 2070 7.3.10 RFC 2165 SLP 2072 The problems have been addressed in RFC 3111, Service Location 2073 Protocol Modifications for IPv6. 2075 7.3.11 RFC 2225 Classical IP & ARP over ATM 2077 The problems have been resolved in RFC 2492, IPv6 over ATM Networks. 2079 7.3.12 RFC 2226 IP Broadcast over ATM 2081 The problems have been resolved in RFC 2492, IPv6 over ATM Networks. 2083 7.3.13 RFC 2371 Transaction IPv3 2085 No updated document exists for this specification. It is unclear 2086 whether one is needed. 2088 7.3.14 RFC 2625 IP and ARP over Fibre Channel 2090 There is work in progress to fix these problems 2091 (draft-desanti-ipv6-over-fibre-channel-02.txt). 2093 7.3.15 RFC 2672 Non-Terminal DNS Redirection 2095 No updated document exists for this specification. It is unclear 2096 whether one is needed. 2098 7.3.16 RFC 2673 Binary Labels in DNS 2100 No updated document exists for this specification. It is unclear 2101 whether one is needed. 2103 7.3.17 IP over Vertical Blanking Interval of a TV Signal (RFC 2728) 2105 No updated document exists for this specification. It is unclear 2106 whether one is needed. 2108 7.3.18 RFC 2734 IPv4 over IEEE 1394 2110 This problem has been fixed by RFC 3146, Transmission of IPv6 Packets 2111 Over IEEE 1394 Networks. 2113 7.3.19 RFC 2834 ARP & IP Broadcasts Over HIPPI 800 2115 No updated document exists for this specification. It is unclear 2116 whether one is needed. 2118 7.3.20 RFC 2835 ARP & IP Broadcasts Over HIPPI 6400 2120 No updated document exists for this specification. It is unclear 2121 whether one is needed. 2123 7.3.21 RFC 3344 Mobility Support for IPv4 2125 The problems have been resolved by two upcoming RFCs, already waiting 2126 publication (draft-ietf-mobileip-ipv6-24.txt and 2127 draft-ietf-mobileip-mipv6-ha-ipsec-06.txt). 2129 Since the first Mobile IPv4 specification in RFC 2002, a number of 2130 extensions to it have been specified. As all of these depend on on 2131 MIPv4, they have been omitted from further analysis in this memo. 2133 7.3.22 RFC 3376 Internet Group Management Protocol, Version 3 2135 This problem is being fixed by MLDv2 specification 2136 (draft-vida-mld-v2-xx.txt). 2138 7.4 Experimental RFCs 2140 7.4.1 RFC 1307 Dynamically Switched Link Control Protocol 2142 No updated document exists for this specification. It is unclear 2143 whether one is needed. 2145 7.4.2 RFC 1393 Traceroute using an IP Option 2147 This specification relies on the use of an IPv4 option. No 2148 replacement document exists, and it is unclear whether one is needed. 2150 7.4.3 RFC 1735 NBMA Address Resolution Protocol (NARP) 2152 This functionality has been defined in RFC 2491, IPv6 over 2153 Non-Broadcast Multiple Access (NBMA) networks and RFC 2332, NBMA Next 2154 Hop Resolution Protocol (NHRP). 2156 7.4.4 RFC 1788 ICMP Domain Name Messages 2158 No updated document exists for this specification. However, DNS 2159 Dynamic Updates should provide similar functionality, so an update 2160 does not seem necessary. 2162 7.4.5 RFC 1868 ARP Extension - UNARP 2164 This mechanism defined a mechanism to purge ARP caches on a link. 2165 That functionality already exists in RFC 2461, Neighbor Discovery for 2166 IPv6. 2168 7.4.6 RFC 2143 IP Over SCSI 2170 No updated document exists for this specification. It is unclear 2171 whether one is needed. 2173 7.4.7 RFC 3180 GLOP Addressing in 233/8 2175 Similar functionality is provided by RFC 3306, Unicast-Prefix-based 2176 IPv6 Multicast Addresses, and no action is necessary. 2178 8. Security Considerations 2180 This memo examines the IPv6-readiness of specifications; this does 2181 not have security considerations in itself. 2183 9. Acknowledgements 2185 The author would like to acknowledge the support of the Internet 2186 Society in the research and production of this document. Additionally 2187 the author would like to thanks his partner in all ways, Wendy M. 2188 Nesser. 2190 The editor, Cleveland Mickles, would like to thank Steve Bellovin and 2191 Russ Housley for their comments and Pekka Savola for his comments and 2192 guidance during the editing of this document. Additionally he would 2193 like to thank his wife, Lesia, for her patient support. 2195 Pekka Savola helped in editing the latest versions of the document. 2197 Normative References 2199 [1] II, P. and A. Bergstrom, "Introduction to the Survey of IPv4 2200 Addresses in Currently Deployed IETF Standards", 2201 draft-ietf-v6ops-ipv4survey-intro-04 (work in progress), October 2202 2003. 2204 Authors' Addresses 2206 Cleveland Mickles (editor) 2208 Reston, VA 20191 2209 USA 2211 EMail: cmickles.ee88@gtalumni.org 2213 Philip J. Nesser II 2214 Nesser & Nesser Consulting 2215 13501 100th Ave NE, #5202 2216 Kirkland, WA 98034 2217 USA 2219 EMail: phil@nesser.com 2221 Intellectual Property Statement 2223 The IETF takes no position regarding the validity or scope of any 2224 intellectual property or other rights that might be claimed to 2225 pertain to the implementation or use of the technology described in 2226 this document or the extent to which any license under such rights 2227 might or might not be available; neither does it represent that it 2228 has made any effort to identify any such rights. Information on the 2229 IETF's procedures with respect to rights in standards-track and 2230 standards-related documentation can be found in BCP-11. Copies of 2231 claims of rights made available for publication and any assurances of 2232 licenses to be made available, or the result of an attempt made to 2233 obtain a general license or permission for the use of such 2234 proprietary rights by implementors or users of this specification can 2235 be obtained from the IETF Secretariat. 2237 The IETF invites any interested party to bring to its attention any 2238 copyrights, patents or patent applications, or other proprietary 2239 rights which may cover technology that may be required to practice 2240 this standard. Please address the information to the IETF Executive 2241 Director. 2243 Full Copyright Statement 2245 Copyright (C) The Internet Society (2003). All Rights Reserved. 2247 This document and translations of it may be copied and furnished to 2248 others, and derivative works that comment on or otherwise explain it 2249 or assist in its implementation may be prepared, copied, published 2250 and distributed, in whole or in part, without restriction of any 2251 kind, provided that the above copyright notice and this paragraph are 2252 included on all such copies and derivative works. However, this 2253 document itself may not be modified in any way, such as by removing 2254 the copyright notice or references to the Internet Society or other 2255 Internet organizations, except as needed for the purpose of 2256 developing Internet standards in which case the procedures for 2257 copyrights defined in the Internet Standards process must be 2258 followed, or as required to translate it into languages other than 2259 English. 2261 The limited permissions granted above are perpetual and will not be 2262 revoked by the Internet Society or its successors or assignees. 2264 This document and the information contained herein is provided on an 2265 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 2266 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 2267 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 2268 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 2269 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 2271 Acknowledgment 2273 Funding for the RFC Editor function is currently provided by the 2274 Internet Society.