draft-ietf-v6ops-ipv4survey-int-02.txt | draft-ietf-v6ops-ipv4survey-int-03.txt | |||
---|---|---|---|---|
IPv6 Operations C. Mickles, Ed. | ||||
IPv6 Operations C. Mickles | ||||
Internet-Draft | Internet-Draft | |||
Expires: March 31, 2004 P. Nesser | Expires: March 31, 2004 P. Nesser | |||
Nesser & Nesser Consulting | Nesser & Nesser Consulting | |||
Oct 2003 | Oct 2003 | |||
Survey of IPv4 Addresses in Currently Deployed IETF Internet Area | Survey of IPv4 Addresses in Currently Deployed IETF Internet Area | |||
Standards | Standards | |||
draft-ietf-v6ops-ipv4survey-int-02.txt | draft-ietf-v6ops-ipv4survey-int-03.txt | |||
Status of this Memo | Status of this Memo | |||
This document is an Internet-Draft and is in full conformance with | This document is an Internet-Draft and is in full conformance with | |||
all provisions of Section 10 of RFC2026. | all provisions of Section 10 of RFC2026. | |||
Internet-Drafts are working documents of the Internet Engineering | Internet-Drafts are working documents of the Internet Engineering | |||
Task Force (IETF), its areas, and its working groups. Note that other | Task Force (IETF), its areas, and its working groups. Note that other | |||
groups may also distribute working documents as Internet-Drafts. | groups may also distribute working documents as Internet-Drafts. | |||
skipping to change at page 5, line 13 | skipping to change at page 5, line 13 | |||
5.59 RFC 2563 DHCP Option to Disable Stateless | 5.59 RFC 2563 DHCP Option to Disable Stateless | |||
Auto-Configuration in IPv4 Clients . . . . . . . . . . . . 30 | Auto-Configuration in IPv4 Clients . . . . . . . . . . . . 30 | |||
5.60 RFC 2590 Transmission of IPv6 Packets over Frame Relay | 5.60 RFC 2590 Transmission of IPv6 Packets over Frame Relay | |||
Networks Specification . . . . . . . . . . . . . . . . . . 30 | Networks Specification . . . . . . . . . . . . . . . . . . 30 | |||
5.61 RFC 2601 ILMI-Based Server Discovery for ATMARP . . . . . 30 | 5.61 RFC 2601 ILMI-Based Server Discovery for ATMARP . . . . . 30 | |||
5.62 RFC 2602 ILMI-Based Server Discovery for MARS . . . . . . 30 | 5.62 RFC 2602 ILMI-Based Server Discovery for MARS . . . . . . 30 | |||
5.63 RFC 2603 ILMI-Based Server Discovery for NHRP . . . . . . 30 | 5.63 RFC 2603 ILMI-Based Server Discovery for NHRP . . . . . . 30 | |||
5.64 RFC 2610 DHCP Options for Service Location Protocol . . . 30 | 5.64 RFC 2610 DHCP Options for Service Location Protocol . . . 30 | |||
5.65 RFC 2615 PPP over SONET/SDH . . . . . . . . . . . . . . . 31 | 5.65 RFC 2615 PPP over SONET/SDH . . . . . . . . . . . . . . . 31 | |||
5.66 RFC 2625 IP and ARP over Fibre Channel . . . . . . . . . . 31 | 5.66 RFC 2625 IP and ARP over Fibre Channel . . . . . . . . . . 31 | |||
5.67 RFC 2671 Extension Mechanisms for DNS (EDNS0) . . . . . . 31 | 5.67 RFC 2661 Layer Two Tunneling Protocol (L2TP) . . . . . . . 31 | |||
5.68 RFC 2672 Non-Terminal DNS Name Redirection . . . . . . . . 31 | 5.68 RFC 2671 Extension Mechanisms for DNS (EDNS0) . . . . . . 31 | |||
5.69 RFC 2673 Binary Labels in the Domain Name System . . . . . 31 | 5.69 RFC 2672 Non-Terminal DNS Name Redirection . . . . . . . . 31 | |||
5.70 RFC 2675 IPv6 Jumbograms . . . . . . . . . . . . . . . . . 31 | 5.70 RFC 2673 Binary Labels in the Domain Name System . . . . . 31 | |||
5.71 RFC 2684 Multiprotocol Encapsulation over ATM | 5.71 RFC 2675 IPv6 Jumbograms . . . . . . . . . . . . . . . . . 31 | |||
5.72 RFC 2684 Multiprotocol Encapsulation over ATM | ||||
Adaptation Layer 5 . . . . . . . . . . . . . . . . . . . . 31 | Adaptation Layer 5 . . . . . . . . . . . . . . . . . . . . 31 | |||
5.72 RFC 2685 Virtual Private Networks Identifier . . . . . . . 31 | 5.73 RFC 2685 Virtual Private Networks Identifier . . . . . . . 31 | |||
5.73 RFC 2686 The Multi-Class Extension to Multi-Link PPP . . . 31 | 5.74 RFC 2686 The Multi-Class Extension to Multi-Link PPP . . . 32 | |||
5.74 RFC 2687 PPP in a Real-time Oriented HDLC-like Framing . . 32 | 5.75 RFC 2687 PPP in a Real-time Oriented HDLC-like Framing . . 32 | |||
5.75 RFC 2688 Integrated Services Mappings for Low Speed | 5.76 RFC 2688 Integrated Services Mappings for Low Speed | |||
Networks . . . . . . . . . . . . . . . . . . . . . . . . . 32 | Networks . . . . . . . . . . . . . . . . . . . . . . . . . 32 | |||
5.76 RFC 2710 Multicast Listener Discovery (MLD) for IPv6 . . . 32 | 5.77 RFC 2710 Multicast Listener Discovery (MLD) for IPv6 . . . 32 | |||
5.77 RFC 2711 IPv6 Router Alert Option . . . . . . . . . . . . 32 | 5.78 RFC 2711 IPv6 Router Alert Option . . . . . . . . . . . . 32 | |||
5.78 RFC 2728 The Transmission of IP Over the Vertical | 5.79 RFC 2728 The Transmission of IP Over the Vertical | |||
Blanking Interval of a Television Signal . . . . . . . . . 32 | Blanking Interval of a Television Signal . . . . . . . . . 32 | |||
5.79 RFC 2734 IPv4 over IEEE 1394 . . . . . . . . . . . . . . . 33 | 5.80 RFC 2734 IPv4 over IEEE 1394 . . . . . . . . . . . . . . . 33 | |||
5.80 RFC 2735 NHRP Support for Virtual Private Networks . . . . 33 | 5.81 RFC 2735 NHRP Support for Virtual Private Networks . . . . 33 | |||
5.81 RFC 2765 Stateless IP/ICMP Translation Algorithm (SIIT) . 33 | 5.82 RFC 2765 Stateless IP/ICMP Translation Algorithm (SIIT) . 33 | |||
5.82 RFC 2766 Network Address Translation - Protocol | 5.83 RFC 2766 Network Address Translation - Protocol | |||
Translation (NAT-PT) . . . . . . . . . . . . . . . . . . . 33 | Translation (NAT-PT) . . . . . . . . . . . . . . . . . . . 33 | |||
5.83 RFC 2776 Multicast-Scope Zone Announcement Protocol | 5.84 RFC 2776 Multicast-Scope Zone Announcement Protocol | |||
(MZAP) . . . . . . . . . . . . . . . . . . . . . . . . . . 33 | (MZAP) . . . . . . . . . . . . . . . . . . . . . . . . . . 33 | |||
5.84 RFC 2782 A DNS RR for specifying the location of | 5.85 RFC 2782 A DNS RR for specifying the location of | |||
services . . . . . . . . . . . . . . . . . . . . . . . . . 33 | services . . . . . . . . . . . . . . . . . . . . . . . . . 33 | |||
5.85 RFC 2794 Mobile IP Network Access Identifier Extension | 5.86 RFC 2794 Mobile IP Network Access Identifier Extension | |||
for IPv4 . . . . . . . . . . . . . . . . . . . . . . . . . 33 | for IPv4 . . . . . . . . . . . . . . . . . . . . . . . . . 33 | |||
5.86 RFC 2834 ARP and IP Broadcast over HIPPI-800 . . . . . . . 33 | 5.87 RFC 2834 ARP and IP Broadcast over HIPPI-800 . . . . . . . 33 | |||
5.87 RFC 2835 IP and ARP over HIPPI-6400 . . . . . . . . . . . 35 | 5.88 RFC 2835 IP and ARP over HIPPI-6400 . . . . . . . . . . . 35 | |||
5.88 RFC 2855 DHCP for IEEE 1394 . . . . . . . . . . . . . . . 35 | 5.89 RFC 2855 DHCP for IEEE 1394 . . . . . . . . . . . . . . . 35 | |||
5.89 RFC 2874 DNS Extensions to Support IPv6 Address | 5.90 RFC 2874 DNS Extensions to Support IPv6 Address | |||
Aggregation and Renumbering . . . . . . . . . . . . . . . 35 | Aggregation and Renumbering . . . . . . . . . . . . . . . 35 | |||
5.90 RFC 2893 Transition Mechanisms for IPv6 Hosts and | 5.91 RFC 2893 Transition Mechanisms for IPv6 Hosts and | |||
Routers . . . . . . . . . . . . . . . . . . . . . . . . . 36 | Routers . . . . . . . . . . . . . . . . . . . . . . . . . 36 | |||
5.91 RFC 2916 E.164 number and DNS . . . . . . . . . . . . . . 36 | 5.92 RFC 2916 E.164 number and DNS . . . . . . . . . . . . . . 36 | |||
5.92 RFC 2937 The Name Service Search Option for DHCP . . . . . 36 | 5.93 RFC 2937 The Name Service Search Option for DHCP . . . . . 36 | |||
5.93 RFC 3004 The User Class Option for DHCP . . . . . . . . . 36 | 5.94 RFC 3004 The User Class Option for DHCP . . . . . . . . . 36 | |||
5.94 RFC 3011 The IPv4 Subnet Selection Option for DHCP . . . . 36 | 5.95 RFC 3011 The IPv4 Subnet Selection Option for DHCP . . . . 36 | |||
5.95 RFC 3021 Using 31-Bit Prefixes for IPv4 P2P Links . . . . 36 | 5.96 RFC 3021 Using 31-Bit Prefixes for IPv4 P2P Links . . . . 36 | |||
5.96 RFC 3024 Reverse Tunneling for Mobile IP, revised . . . . 36 | 5.97 RFC 3024 Reverse Tunneling for Mobile IP, revised . . . . 36 | |||
5.97 RFC 3046 DHCP Relay Agent Information Option . . . . . . . 36 | 5.98 RFC 3046 DHCP Relay Agent Information Option . . . . . . . 36 | |||
5.98 RFC 3056 Connection of IPv6 Domains via IPv4 Clouds . . . 36 | 5.99 RFC 3056 Connection of IPv6 Domains via IPv4 Clouds . . . 36 | |||
5.99 RFC 3068 An Anycast Prefix for 6to4 Relay Routers . . . . 36 | 5.100 RFC 3068 An Anycast Prefix for 6to4 Relay Routers . . . . 36 | |||
5.100 RFC 3074 DHC Load Balancing Algorithm . . . . . . . . . . 37 | 5.101 RFC 3070 Layer Two Tunneling Protocol (L2TP) over Frame | |||
5.101 RFC 3077 A Link-Layer Tunneling Mechanism for | Relay . . . . . . . . . . . . . . . . . . . . . . . . . . 37 | |||
5.102 RFC 3074 DHC Load Balancing Algorithm . . . . . . . . . . 37 | ||||
5.103 RFC 3077 A Link-Layer Tunneling Mechanism for | ||||
Unidirectional Links . . . . . . . . . . . . . . . . . . . 37 | Unidirectional Links . . . . . . . . . . . . . . . . . . . 37 | |||
5.102 RFC 3115 Mobile IP Vendor/Organization-Specific | 5.104 RFC 3115 Mobile IP Vendor/Organization-Specific | |||
Extensions . . . . . . . . . . . . . . . . . . . . . . . . 37 | Extensions . . . . . . . . . . . . . . . . . . . . . . . . 37 | |||
5.103 RFC 3145 L2TP Disconnect Cause Information . . . . . . . . 37 | 5.105 RFC 3145 L2TP Disconnect Cause Information . . . . . . . . 37 | |||
5.104 RFC 3344 IP Mobility Support for IPv4 . . . . . . . . . . 37 | 5.106 RFC 3344 IP Mobility Support for IPv4 . . . . . . . . . . 37 | |||
5.105 RFC 3376 Internet Group Management Protocol, Version 3 . . 37 | 5.107 RFC 3376 Internet Group Management Protocol, Version 3 . . 37 | |||
5.106 RFC 3402 Dynamic Delegation Discovery System (DDDS) | 5.108 RFC 3402 Dynamic Delegation Discovery System (DDDS) | |||
Part Two: The Algorithm . . . . . . . . . . . . . . . . . 37 | Part Two: The Algorithm . . . . . . . . . . . . . . . . . 37 | |||
5.107 RFC 3403 Dynamic Delegation Discovery System (DDDS) | 5.109 RFC 3403 Dynamic Delegation Discovery System (DDDS) | |||
Part Three: The Domain Name System (DNS) Database . . . . 37 | Part Three: The Domain Name System (DNS) Database . . . . 37 | |||
5.108 RFC 3404 Dynamic Delegation Discovery System (DDDS) | 5.110 RFC 3513 IP Version 6 Addressing Architecture . . . . . . 37 | |||
Part Four: The Uniform Resource Identifiers (URI) . . . . 37 | 5.111 RFC 3518 Point-to-Point Protocol (PPP) Bridging Control | |||
5.109 RFC 3513 IP Version 6 Addressing Architecture . . . . . . 37 | ||||
5.110 RFC 3518 Point-to-Point Protocol (PPP) Bridging Control | ||||
Protocol (BCP) . . . . . . . . . . . . . . . . . . . . . . 38 | Protocol (BCP) . . . . . . . . . . . . . . . . . . . . . . 38 | |||
6. Experimental RFCs . . . . . . . . . . . . . . . . . . . . 39 | 6. Experimental RFCs . . . . . . . . . . . . . . . . . . . . 39 | |||
6.1 RFC 1149 Standard for the transmission of IP datagrams | 6.1 RFC 1149 Standard for the transmission of IP datagrams | |||
on avian carriers . . . . . . . . . . . . . . . . . . . . 39 | on avian carriers . . . . . . . . . . . . . . . . . . . . 39 | |||
6.2 RFC 1183 New DNS RR Definitions . . . . . . . . . . . . . 39 | 6.2 RFC 1183 New DNS RR Definitions . . . . . . . . . . . . . 39 | |||
6.3 RFC 1226 Internet protocol encapsulation of AX.25 frames . 39 | 6.3 RFC 1226 Internet protocol encapsulation of AX.25 frames . 39 | |||
6.4 RFC 1241 Scheme for an internet encapsulation protocol: | 6.4 RFC 1241 Scheme for an internet encapsulation protocol: | |||
Version 1 . . . . . . . . . . . . . . . . . . . . . . . . 39 | Version 1 . . . . . . . . . . . . . . . . . . . . . . . . 39 | |||
6.5 RFC 1307 Dynamically Switched Link Control Protocol . . . 39 | 6.5 RFC 1307 Dynamically Switched Link Control Protocol . . . 39 | |||
6.6 RFC 1393 Traceroute Using an IP Option . . . . . . . . . . 40 | 6.6 RFC 1393 Traceroute Using an IP Option . . . . . . . . . . 40 | |||
skipping to change at page 8, line 21 | skipping to change at page 8, line 22 | |||
7.3.15 RFC 2672 Non-Terminal DNS Redirection . . . . . . . . . . 49 | 7.3.15 RFC 2672 Non-Terminal DNS Redirection . . . . . . . . . . 49 | |||
7.3.16 RFC 2673 Binary Labels in DNS . . . . . . . . . . . . . . 49 | 7.3.16 RFC 2673 Binary Labels in DNS . . . . . . . . . . . . . . 49 | |||
7.3.17 IP over Vertical Blanking Interval of a TV Signal (RFC | 7.3.17 IP over Vertical Blanking Interval of a TV Signal (RFC | |||
2728) . . . . . . . . . . . . . . . . . . . . . . . . . . 49 | 2728) . . . . . . . . . . . . . . . . . . . . . . . . . . 49 | |||
7.3.18 RFC 2734 IPv4 over IEEE 1394 . . . . . . . . . . . . . . . 49 | 7.3.18 RFC 2734 IPv4 over IEEE 1394 . . . . . . . . . . . . . . . 49 | |||
7.3.19 RFC 2834 ARP & IP Broadcasts Over HIPPI 800 . . . . . . . 49 | 7.3.19 RFC 2834 ARP & IP Broadcasts Over HIPPI 800 . . . . . . . 49 | |||
7.3.20 RFC 2835 ARP & IP Broadcasts Over HIPPI 6400 . . . . . . . 50 | 7.3.20 RFC 2835 ARP & IP Broadcasts Over HIPPI 6400 . . . . . . . 50 | |||
7.3.21 RFC 3344 Mobility Support for IPv4 . . . . . . . . . . . . 50 | 7.3.21 RFC 3344 Mobility Support for IPv4 . . . . . . . . . . . . 50 | |||
7.3.22 RFC 3376 Internet Group Management Protocol, Version 3 . . 50 | 7.3.22 RFC 3376 Internet Group Management Protocol, Version 3 . . 50 | |||
7.4 Experimental RFCs . . . . . . . . . . . . . . . . . . . . 50 | 7.4 Experimental RFCs . . . . . . . . . . . . . . . . . . . . 50 | |||
7.4.1 RFC 1393 Traceroute using an IP Option . . . . . . . . . . 50 | 7.4.1 RFC 1307 Dynamically Switched Link Control Protocol . . . 50 | |||
7.4.2 RFC 1307 Dynamically Switched Link Control Protocol . . . 50 | 7.4.2 RFC 1393 Traceroute using an IP Option . . . . . . . . . . 50 | |||
7.4.3 RFC 1735 NBMA Address Resolution Protocol (NARP) . . . . . 50 | 7.4.3 RFC 1735 NBMA Address Resolution Protocol (NARP) . . . . . 50 | |||
7.4.4 RFC 1788 ICMP Domain Name Messages . . . . . . . . . . . . 50 | 7.4.4 RFC 1788 ICMP Domain Name Messages . . . . . . . . . . . . 50 | |||
7.4.5 RFC 1868 ARP Extension - UNARP . . . . . . . . . . . . . . 50 | 7.4.5 RFC 1868 ARP Extension - UNARP . . . . . . . . . . . . . . 50 | |||
7.4.6 RFC 2143 IP Over SCSI . . . . . . . . . . . . . . . . . . 51 | 7.4.6 RFC 2143 IP Over SCSI . . . . . . . . . . . . . . . . . . 51 | |||
7.4.7 RFC 3180 GLOP Addressing in 233/8 . . . . . . . . . . . . 51 | 7.4.7 RFC 3180 GLOP Addressing in 233/8 . . . . . . . . . . . . 51 | |||
8. Security Considerations . . . . . . . . . . . . . . . . . 52 | 8. Security Considerations . . . . . . . . . . . . . . . . . 52 | |||
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . 53 | 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . 53 | |||
Normative References . . . . . . . . . . . . . . . . . . . 54 | Normative References . . . . . . . . . . . . . . . . . . . 54 | |||
Authors' Addresses . . . . . . . . . . . . . . . . . . . . 54 | Authors' Addresses . . . . . . . . . . . . . . . . . . . . 54 | |||
Intellectual Property and Copyright Statements . . . . . . 55 | Intellectual Property and Copyright Statements . . . . . . 55 | |||
skipping to change at page 31, line 22 | skipping to change at page 31, line 22 | |||
Objective and Scope: | Objective and Scope: | |||
The major objective of this specification is to promote | The major objective of this specification is to promote | |||
interoperable implementations of IPv4 over FC. This specification | interoperable implementations of IPv4 over FC. This specification | |||
describes a method for encapsulating IPv4 and Address Resolution | describes a method for encapsulating IPv4 and Address Resolution | |||
Protocol (ARP) packets over FC. | Protocol (ARP) packets over FC. | |||
This is incompatible with IPv6. | This is incompatible with IPv6. | |||
5.67 RFC 2671 Extension Mechanisms for DNS (EDNS0) | 5.67 RFC 2661 Layer Two Tunneling Protocol (L2TP) | |||
There are no IPv4 dependencies in this specification. | There are no IPv4 dependencies in this specification. | |||
5.68 RFC 2672 Non-Terminal DNS Name Redirection | 5.68 RFC 2671 Extension Mechanisms for DNS (EDNS0) | |||
There are no IPv4 dependencies in this specification. | ||||
5.69 RFC 2672 Non-Terminal DNS Name Redirection | ||||
This document is only defined for IPv4 addresses. An IPv6 | This document is only defined for IPv4 addresses. An IPv6 | |||
specification may be needed. | specification may be needed. | |||
5.69 RFC 2673 Binary Labels in the Domain Name System | 5.70 RFC 2673 Binary Labels in the Domain Name System | |||
This document is only defined for IPv4 addresses. An IPv6 | This document is only defined for IPv4 addresses. An IPv6 | |||
specification may be needed. | specification may be needed. | |||
5.70 RFC 2675 IPv6 Jumbograms | 5.71 RFC 2675 IPv6 Jumbograms | |||
This document defines a IPv6 packet format and is therefore not | This document defines a IPv6 packet format and is therefore not | |||
discussed in this document. | discussed in this document. | |||
5.71 RFC 2684 Multiprotocol Encapsulation over ATM Adaptation Layer 5 | 5.72 RFC 2684 Multiprotocol Encapsulation over ATM Adaptation Layer 5 | |||
There are no IPv4 dependencies in this specification. | There are no IPv4 dependencies in this specification. | |||
5.72 RFC 2685 Virtual Private Networks Identifier | 5.73 RFC 2685 Virtual Private Networks Identifier | |||
There are no IPv4 dependencies in this specification. | There are no IPv4 dependencies in this specification. | |||
5.73 RFC 2686 The Multi-Class Extension to Multi-Link PPP | 5.74 RFC 2686 The Multi-Class Extension to Multi-Link PPP | |||
There are no IPv4 dependencies in this specification. | There are no IPv4 dependencies in this specification. | |||
5.74 RFC 2687 PPP in a Real-time Oriented HDLC-like Framing | 5.75 RFC 2687 PPP in a Real-time Oriented HDLC-like Framing | |||
There are no IPv4 dependencies in this specification. | There are no IPv4 dependencies in this specification. | |||
5.75 RFC 2688 Integrated Services Mappings for Low Speed Networks | 5.76 RFC 2688 Integrated Services Mappings for Low Speed Networks | |||
There are no IPv4 dependencies in this specification. | There are no IPv4 dependencies in this specification. | |||
5.76 RFC 2710 Multicast Listener Discovery (MLD) for IPv6 | 5.77 RFC 2710 Multicast Listener Discovery (MLD) for IPv6 | |||
This document defines an IPv6 specific specification and is not | This document defines an IPv6 specific specification and is not | |||
discussed in this document. | discussed in this document. | |||
5.77 RFC 2711 IPv6 Router Alert Option | 5.78 RFC 2711 IPv6 Router Alert Option | |||
This document defines an IPv6 specific specification and is not | This document defines an IPv6 specific specification and is not | |||
discussed in this document. | discussed in this document. | |||
5.78 RFC 2728 The Transmission of IP Over the Vertical Blanking Interval | 5.79 RFC 2728 The Transmission of IP Over the Vertical Blanking Interval | |||
of a Television Signal | of a Television Signal | |||
The following data format is defined: | The following data format is defined: | |||
0 1 2 3 | 0 1 2 3 | |||
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 | 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 | |||
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | |||
|0| group | uncompressed IP header (20 bytes) | | |0| group | uncompressed IP header (20 bytes) | | |||
+-+-+-+-+-+-+-+-+ + | +-+-+-+-+-+-+-+-+ + | |||
| | | | | | |||
skipping to change at page 32, line 47 | skipping to change at page 33, line 4 | |||
+-+-+-+-+-+-+-+-+ + | +-+-+-+-+-+-+-+-+ + | |||
| | | | | | |||
+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | |||
| | payload (<1472 bytes) | | | | payload (<1472 bytes) | | |||
+-+-+-+-+-+-+-+-+ + | +-+-+-+-+-+-+-+-+ + | |||
| | | | | | |||
: .... : | : .... : | |||
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | |||
| CRC | | | CRC | | |||
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | |||
This is incompatible with IPv6. | This is incompatible with IPv6. | |||
5.79 RFC 2734 IPv4 over IEEE 1394 | 5.80 RFC 2734 IPv4 over IEEE 1394 | |||
This specification is IPv4 only. | This specification is IPv4 only. | |||
5.80 RFC 2735 NHRP Support for Virtual Private Networks | 5.81 RFC 2735 NHRP Support for Virtual Private Networks | |||
This specification implies only IPv4 operations, but does not seem to | This specification implies only IPv4 operations, but does not seem to | |||
present any reason that it would not function for IPv6. | present any reason that it would not function for IPv6. | |||
5.81 RFC 2765 Stateless IP/ICMP Translation Algorithm (SIIT) | 5.82 RFC 2765 Stateless IP/ICMP Translation Algorithm (SIIT) | |||
This specification defines a method for IPv6 transition and is not | This specification defines a method for IPv6 transition and is not | |||
discussed in this document. | discussed in this document. | |||
5.82 RFC 2766 Network Address Translation - Protocol Translation | 5.83 RFC 2766 Network Address Translation - Protocol Translation | |||
(NAT-PT) | (NAT-PT) | |||
This specification defines a method for IPv6 transition and is not | This specification defines a method for IPv6 transition and is not | |||
discussed in this document. | discussed in this document. | |||
5.83 RFC 2776 Multicast-Scope Zone Announcement Protocol (MZAP) | 5.84 RFC 2776 Multicast-Scope Zone Announcement Protocol (MZAP) | |||
This specification is both IPv4 and IPv6 aware and needs no changes. | This specification is both IPv4 and IPv6 aware and needs no changes. | |||
5.84 RFC 2782 A DNS RR for specifying the location of services | 5.85 RFC 2782 A DNS RR for specifying the location of services | |||
There are no IPv4 dependencies in this specification. | There are no IPv4 dependencies in this specification. | |||
5.85 RFC 2794 Mobile IP Network Access Identifier Extension for IPv4 | 5.86 RFC 2794 Mobile IP Network Access Identifier Extension for IPv4 | |||
This is an extension to an IPv4-only specification. | This is an extension to an IPv4-only specification. | |||
5.86 RFC 2834 ARP and IP Broadcast over HIPPI-800 | 5.87 RFC 2834 ARP and IP Broadcast over HIPPI-800 | |||
This document uses the generic term "IP Address" in the text but it | This document uses the generic term "IP Address" in the text but it | |||
also contains the text: | also contains the text: | |||
The HARP message has several fields that have the following format | The HARP message has several fields that have the following format | |||
and values: | and values: | |||
Data sizes and field meaning: | Data sizes and field meaning: | |||
ar$hrd 16 bits Hardware type | ar$hrd 16 bits Hardware type | |||
ar$pro 16 bits Protocol type of the protocol fields below | ar$pro 16 bits Protocol type of the protocol fields below | |||
skipping to change at page 35, line 32 | skipping to change at page 35, line 32 | |||
17 | Target HIPPI Hardware Address bytes 1 - 4 | | 17 | Target HIPPI Hardware Address bytes 1 - 4 | | |||
+---------------------------------------------------------------+ | +---------------------------------------------------------------+ | |||
18 | Target HIPPI Hardware Address bytes 5 - 8 | | 18 | Target HIPPI Hardware Address bytes 5 - 8 | | |||
+---------------+---------------+---------------+---------------+ | +---------------+---------------+---------------+---------------+ | |||
19 |Tgt HW byte 9-x| FILL | FILL | FILL | | 19 |Tgt HW byte 9-x| FILL | FILL | FILL | | |||
+---------------+---------------+---------------+---------------+ | +---------------+---------------+---------------+---------------+ | |||
HARP - InHARP Message | HARP - InHARP Message | |||
This is incompatible with IPv6. | This is incompatible with IPv6. | |||
5.87 RFC 2835 IP and ARP over HIPPI-6400 | 5.88 RFC 2835 IP and ARP over HIPPI-6400 | |||
This document states: | This document states: | |||
The Ethertype value SHALL be set as defined in Assigned Numbers | The Ethertype value SHALL be set as defined in Assigned Numbers | |||
[18]: | [18]: | |||
IP 0x0800 2048 (16 bits) | IP 0x0800 2048 (16 bits) | |||
This is limited to IPv4, and similar to the previous section, | This is limited to IPv4, and similar to the previous section, | |||
incompatible with IPv6. There are numerous other points in the | incompatible with IPv6. There are numerous other points in the | |||
documents that confirm this assumption. | documents that confirm this assumption. | |||
5.88 RFC 2855 DHCP for IEEE 1394 | 5.89 RFC 2855 DHCP for IEEE 1394 | |||
This is an extension to an IPv4-only specification. | This is an extension to an IPv4-only specification. | |||
5.89 RFC 2874 DNS Extensions to Support IPv6 Address Aggregation and | 5.90 RFC 2874 DNS Extensions to Support IPv6 Address Aggregation and | |||
Renumbering | Renumbering | |||
This document defines a specification to interact with IPv6 and is | This document defines a specification to interact with IPv6 and is | |||
not considered in this document. | not considered in this document. | |||
5.90 RFC 2893 Transition Mechanisms for IPv6 Hosts and Routers | 5.91 RFC 2893 Transition Mechanisms for IPv6 Hosts and Routers | |||
This document defines a transition mechanism for IPv6 and is not | This document defines a transition mechanism for IPv6 and is not | |||
considered in this document. | considered in this document. | |||
5.91 RFC 2916 E.164 number and DNS | 5.92 RFC 2916 E.164 number and DNS | |||
There are no IPv4 dependencies in this specification. | There are no IPv4 dependencies in this specification. | |||
5.92 RFC 2937 The Name Service Search Option for DHCP | 5.93 RFC 2937 The Name Service Search Option for DHCP | |||
This is an extension to an IPv4-only specification. | This is an extension to an IPv4-only specification. | |||
5.93 RFC 3004 The User Class Option for DHCP | 5.94 RFC 3004 The User Class Option for DHCP | |||
This is an extension to an IPv4-only specification. | This is an extension to an IPv4-only specification. | |||
5.94 RFC 3011 The IPv4 Subnet Selection Option for DHCP | 5.95 RFC 3011 The IPv4 Subnet Selection Option for DHCP | |||
This is an extension to an IPv4-only specification. | This is an extension to an IPv4-only specification. | |||
5.95 RFC 3021 Using 31-Bit Prefixes for IPv4 P2P Links | 5.96 RFC 3021 Using 31-Bit Prefixes for IPv4 P2P Links | |||
This specification is specific to IPv4 address architecture, where a | This specification is specific to IPv4 address architecture, where a | |||
modification was needed to use both addresses of a 31-bit prefix. | modification was needed to use both addresses of a 31-bit prefix. | |||
This is possible by IPv6 address architecture, but in most cases not | This is possible by IPv6 address architecture, but in most cases not | |||
recommended; see RFC 3627, Use of /127 Prefix Length Between Routers | recommended; see RFC 3627, Use of /127 Prefix Length Between Routers | |||
Considered Harmful. | Considered Harmful. | |||
5.96 RFC 3024 Reverse Tunneling for Mobile IP, revised | 5.97 RFC 3024 Reverse Tunneling for Mobile IP, revised | |||
This is an extension to an IPv4-only specification. | This is an extension to an IPv4-only specification. | |||
5.97 RFC 3046 DHCP Relay Agent Information Option | 5.98 RFC 3046 DHCP Relay Agent Information Option | |||
This is an extension to an IPv4-only specification. | This is an extension to an IPv4-only specification. | |||
5.98 RFC 3056 Connection of IPv6 Domains via IPv4 Clouds | 5.99 RFC 3056 Connection of IPv6 Domains via IPv4 Clouds | |||
This is an IPv6 related document and is not discussed in this | This is an IPv6 related document and is not discussed in this | |||
document. | document. | |||
5.99 RFC 3068 An Anycast Prefix for 6to4 Relay Routers | 5.100 RFC 3068 An Anycast Prefix for 6to4 Relay Routers | |||
This is an IPv6 related document and is not discussed in this | This is an IPv6 related document and is not discussed in this | |||
document. | document. | |||
5.100 RFC 3074 DHC Load Balancing Algorithm | 5.101 RFC 3070 Layer Two Tunneling Protocol (L2TP) over Frame Relay | |||
There are no IPv4 dependencies in this specification. | There are no IPv4 dependencies in this specification. | |||
5.101 RFC 3077 A Link-Layer Tunneling Mechanism for Unidirectional Links | 5.102 RFC 3074 DHC Load Balancing Algorithm | |||
There are no IPv4 dependencies in this specification. | ||||
5.103 RFC 3077 A Link-Layer Tunneling Mechanism for Unidirectional Links | ||||
This specification is both IPv4 and IPv6 aware and needs no changes. | This specification is both IPv4 and IPv6 aware and needs no changes. | |||
5.102 RFC 3115 Mobile IP Vendor/Organization-Specific Extensions | 5.104 RFC 3115 Mobile IP Vendor/Organization-Specific Extensions | |||
This is an extension to an IPv4-only specification. | This is an extension to an IPv4-only specification. | |||
5.103 RFC 3145 L2TP Disconnect Cause Information | 5.105 RFC 3145 L2TP Disconnect Cause Information | |||
There are no IPv4 dependencies in this specification. | There are no IPv4 dependencies in this specification. | |||
5.104 RFC 3344 IP Mobility Support for IPv4 | 5.106 RFC 3344 IP Mobility Support for IPv4 | |||
There are IPv4 dependencies in this specification. | There are IPv4 dependencies in this specification. | |||
5.105 RFC 3376 Internet Group Management Protocol, Version 3 | 5.107 RFC 3376 Internet Group Management Protocol, Version 3 | |||
This document describes of version of IGMP used for IPv4 multicast. | This document describes of version of IGMP used for IPv4 multicast. | |||
This is not compatible with IPv6. | This is not compatible with IPv6. | |||
5.106 RFC 3402 Dynamic Delegation Discovery System (DDDS) Part Two: The | 5.108 RFC 3402 Dynamic Delegation Discovery System (DDDS) Part Two: The | |||
Algorithm | Algorithm | |||
There are no IPv4 dependencies in this specification. | There are no IPv4 dependencies in this specification. | |||
5.107 RFC 3403 Dynamic Delegation Discovery System (DDDS) Part Three: | 5.109 RFC 3403 Dynamic Delegation Discovery System (DDDS) Part Three: | |||
The Domain Name System (DNS) Database | The Domain Name System (DNS) Database | |||
There are no IPv4 dependencies in this specification. | There are no IPv4 dependencies in this specification. | |||
5.108 RFC 3404 Dynamic Delegation Discovery System (DDDS) Part Four: | 5.110 RFC 3513 IP Version 6 Addressing Architecture | |||
The Uniform Resource Identifiers (URI) | ||||
There are no IPv4 dependencies in this specification. | ||||
5.109 RFC 3513 IP Version 6 Addressing Architecture | ||||
This specification documents IPv6 addressing and is not discussed in | This specification documents IPv6 addressing and is not discussed in | |||
this document. | this document. | |||
5.110 RFC 3518 Point-to-Point Protocol (PPP) Bridging Control Protocol | 5.111 RFC 3518 Point-to-Point Protocol (PPP) Bridging Control Protocol | |||
(BCP) | (BCP) | |||
There are no IPv4 dependencies in this specification. | There are no IPv4 dependencies in this specification. | |||
6. Experimental RFCs | 6. Experimental RFCs | |||
Experimental RFCs typically define protocols that do not have | Experimental RFCs typically define protocols that do not have | |||
widescale implementation or usage on the Internet. They are often | widescale implementation or usage on the Internet. They are often | |||
propriety in nature or used in limited arenas. They are documented | propriety in nature or used in limited arenas. They are documented | |||
to the Internet community in order to allow potential | to the Internet community in order to allow potential | |||
skipping to change at page 45, line 8 | skipping to change at page 45, line 8 | |||
This specification is both IPv4 and IPv6 aware and needs no changes. | This specification is both IPv4 and IPv6 aware and needs no changes. | |||
6.31 RFC 3180 GLOP Addressing in 233/8 | 6.31 RFC 3180 GLOP Addressing in 233/8 | |||
This document is specific to IPv4 multicast addressing. | This document is specific to IPv4 multicast addressing. | |||
7. Summary of the Results | 7. Summary of the Results | |||
In the initial survey of RFCs 52 positives were identified out of a | In the initial survey of RFCs 52 positives were identified out of a | |||
total of 185, broken down as follows: | total of 186, broken down as follows: | |||
Standards 17 of 24 or 70.83% | Standards 17 of 24 or 70.83% | |||
Draft Standards 6 of 20 or 30.00% | Draft Standards 6 of 20 or 30.00% | |||
Proposed Standards 22 of 110 or 20.00% | Proposed Standards 22 of 111 or 19.91% | |||
Experimental RFCs 7 of 31 or 22.58% | Experimental RFCs 7 of 31 or 22.58% | |||
Of those identified many require no action because they document | Of those identified many require no action because they document | |||
outdated and unused protocols, while others are document protocols | outdated and unused protocols, while others are document protocols | |||
that are actively being updated by the appropriate working groups. | that are actively being updated by the appropriate working groups. | |||
Additionally there are many instances of standards that should be | Additionally there are many instances of standards that should be | |||
updated but do not cause any operational impact if they are not | updated but do not cause any operational impact if they are not | |||
updated. | updated. | |||
skipping to change at page 50, line 27 | skipping to change at page 50, line 27 | |||
extensions to it have been specified. As all of these depend on on | extensions to it have been specified. As all of these depend on on | |||
MIPv4, they have been omitted from further analysis in this memo. | MIPv4, they have been omitted from further analysis in this memo. | |||
7.3.22 RFC 3376 Internet Group Management Protocol, Version 3 | 7.3.22 RFC 3376 Internet Group Management Protocol, Version 3 | |||
This problem is being fixed by MLDv2 specification | This problem is being fixed by MLDv2 specification | |||
(draft-vida-mld-v2-xx.txt). | (draft-vida-mld-v2-xx.txt). | |||
7.4 Experimental RFCs | 7.4 Experimental RFCs | |||
7.4.1 RFC 1393 Traceroute using an IP Option | 7.4.1 RFC 1307 Dynamically Switched Link Control Protocol | |||
This specification relies on the use of an IPv4 option. No | ||||
replacement document exists, and it is unclear whether one is needed. | ||||
7.4.2 RFC 1307 Dynamically Switched Link Control Protocol | ||||
No updated document exists for this specification. It is unclear | No updated document exists for this specification. It is unclear | |||
whether one is needed. | whether one is needed. | |||
7.4.2 RFC 1393 Traceroute using an IP Option | ||||
This specification relies on the use of an IPv4 option. No | ||||
replacement document exists, and it is unclear whether one is needed. | ||||
7.4.3 RFC 1735 NBMA Address Resolution Protocol (NARP) | 7.4.3 RFC 1735 NBMA Address Resolution Protocol (NARP) | |||
This functionality has been defined in RFC 2491, IPv6 over | This functionality has been defined in RFC 2491, IPv6 over | |||
Non-Broadcast Multiple Access (NBMA) networks and RFC 2332, NBMA Next | Non-Broadcast Multiple Access (NBMA) networks and RFC 2332, NBMA Next | |||
Hop Resolution Protocol (NHRP). | Hop Resolution Protocol (NHRP). | |||
7.4.4 RFC 1788 ICMP Domain Name Messages | 7.4.4 RFC 1788 ICMP Domain Name Messages | |||
No updated document exists for this specification. However, DNS | No updated document exists for this specification. However, DNS | |||
Dynamic Updates should provide similar functionality, so an update | Dynamic Updates should provide similar functionality, so an update | |||
skipping to change at page 54, line 14 | skipping to change at page 54, line 14 | |||
Normative References | Normative References | |||
[1] II, P. and A. Bergstrom, "Introduction to the Survey of IPv4 | [1] II, P. and A. Bergstrom, "Introduction to the Survey of IPv4 | |||
Addresses in Currently Deployed IETF Standards", | Addresses in Currently Deployed IETF Standards", | |||
draft-ietf-v6ops-ipv4survey-intro-04 (work in progress), October | draft-ietf-v6ops-ipv4survey-intro-04 (work in progress), October | |||
2003. | 2003. | |||
Authors' Addresses | Authors' Addresses | |||
Cleveland Mickles | Cleveland Mickles (editor) | |||
Reston, VA 20191 | Reston, VA 20191 | |||
USA | USA | |||
EMail: cmickles.ee88@gtalumni.org | EMail: cmickles.ee88@gtalumni.org | |||
Philip J. Nesser II | Philip J. Nesser II | |||
Nesser & Nesser Consulting | Nesser & Nesser Consulting | |||
13501 100th Ave NE, #5202 | 13501 100th Ave NE, #5202 | |||
Kirkland, WA 98034 | Kirkland, WA 98034 | |||
End of changes. | ||||
This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/ |