draft-ietf-v6ops-ipv4survey-trans-02.txt   draft-ietf-v6ops-ipv4survey-trans-03.txt 
Network Working Group Philip J. Nesser II Network Working Group Philip J. Nesser II
draft-ietf-v6ops-ipv4survey-trans-02.txt Nesser & Nesser Consulting draft-ietf-v6ops-ipv4survey-trans-03.txt Nesser & Nesser Consulting
Internet Draft Andreas Bergstrom Internet Draft Andreas Bergstrom
Ostfold University College Ostfold University College
September 2003 October 2003
Expires February 2004 Expires March 2004
Survey of IPv4 Addresses in Currently Deployed Survey of IPv4 Addresses in Currently Deployed
IETF Transport Area Standards IETF Transport Area Standards
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.
Status of this Memo Status of this Memo
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
skipping to change at line 80 skipping to change at line 80
Operations, Routing, Security, Sub-IP and Transport). Operations, Routing, Security, Sub-IP and Transport).
For a full introduction, please see the intro[1] draft. For a full introduction, please see the intro[1] draft.
2.0 Document Organization 2.0 Document Organization
The rest of the document sections are described below. The rest of the document sections are described below.
Sections 3, 4, 5, and 6 each describe the raw analysis of Full, Draft, Sections 3, 4, 5, and 6 each describe the raw analysis of Full, Draft,
and Proposed Standards, and Experimental RFCs. Each RFC is discussed in and Proposed Standards, and Experimental RFCs. Each RFC is discussed in
its turn starting with RFC 1 and ending with RFC 3247. The comments for its turn starting with RFC 1 and ending with (around) RFC 3100.
each RFC are "raw" in nature. That is, each RFC is discussed in a The comments for each RFC are "raw" in nature. That is, each RFC is
vacuum and problems or issues discussed do not "look ahead" to see if discussed in a vacuum and problems or issues discussed do not "look
the problems have already been fixed. ahead" to see if the problems have already been fixed.
Section 7 is an analysis of the data presented in Sections 3, 4, 5, and Section 7 is an analysis of the data presented in Sections 3, 4, 5, and
6. It is here that all of the results are considered as a whole and the 6. It is here that all of the results are considered as a whole and the
problems that have been resolved in later RFCs are correlated. problems that have been resolved in later RFCs are correlated.
3.0 Full Standards 3.0 Full Standards
Full Internet Standards (most commonly simply referred to as " Full Internet Standards (most commonly simply referred to as "
Standards") are fully mature protocol specification that are widely Standards") are fully mature protocol specification that are widely
implemented and used throughout the Internet. implemented and used throughout the Internet.
skipping to change at line 117 skipping to change at line 117
is free from IPv4 references but there is an inconsistency in the is free from IPv4 references but there is an inconsistency in the
computation of checksums. The text says: "The checksum also covers a computation of checksums. The text says: "The checksum also covers a
96 bit pseudo header conceptually prefixed to the TCP header. This 96 bit pseudo header conceptually prefixed to the TCP header. This
pseudo header contains the Source Address, the Destination Address, pseudo header contains the Source Address, the Destination Address,
the Protocol, and TCP length." The first and second 32-bit words are the Protocol, and TCP length." The first and second 32-bit words are
clearly meant to specify 32-bit IPv4 addresses. While no modification clearly meant to specify 32-bit IPv4 addresses. While no modification
of the TCP protocol is necessitated by this problem, an alternate needs of the TCP protocol is necessitated by this problem, an alternate needs
to be specified as an update document, or as part of another IPv6 to be specified as an update document, or as part of another IPv6
document. document.
3.1 RFC 907 Host Access Protocol specification 3.3 RFC 907 Host Access Protocol specification
FIXME: requires to be analyzed by subject matter experts. FIXME: requires to be analyzed by subject matter experts.
This is a layer 3 protocol, and has no IPv4 dependencies. This is a layer 3 protocol, and has no IPv4 dependencies.
3.3 NetBIOS Service Protocols. RFC1001, RFC1002 3.4 NetBIOS Service Protocols. RFC1001, RFC1002
3.3.1 RFC 1001 PROTOCOL STANDARD FOR A NetBIOS SERVICE ON A TCP/UDP 3.4.1 RFC 1001 PROTOCOL STANDARD FOR A NetBIOS SERVICE ON A TCP/UDP
TRANSPORT: TRANSPORT:
CONCEPTS AND METHODS CONCEPTS AND METHODS
Section 15.4.1. RELEASE BY B NODES defines: Section 15.4.1. RELEASE BY B NODES defines:
A NAME RELEASE DEMAND contains the following information: A NAME RELEASE DEMAND contains the following information:
- NetBIOS name - NetBIOS name
- The scope of the NetBIOS name - The scope of the NetBIOS name
- Name type: unique or group - Name type: unique or group
skipping to change at line 403 skipping to change at line 403
- BROADCAST_ADDRESS: the IP address B-nodes use to send datagrams - BROADCAST_ADDRESS: the IP address B-nodes use to send datagrams
with group name destinations and broadcast datagrams. The with group name destinations and broadcast datagrams. The
default is the IP broadcast address for a single IP network. default is the IP broadcast address for a single IP network.
There is also a large amount of pseudo code for most of the protocols There is also a large amount of pseudo code for most of the protocols
functionality that make no specific reference to IPv4 addresses. functionality that make no specific reference to IPv4 addresses.
However they assume the use of the above defined packets. The pseudo However they assume the use of the above defined packets. The pseudo
code may be valid for IPv6 as long as the packet formats are updated. code may be valid for IPv6 as long as the packet formats are updated.
3.4 RFC 1006 ISO Transport Service on top of the TCP (Version: 3) 3.5 RFC 1006 ISO Transport Service on top of the TCP (Version: 3)
Section 5. The Protocol defines a mapping specification Section 5. The Protocol defines a mapping specification
Mapping parameters is also straight-forward: Mapping parameters is also straight-forward:
network service TCP network service TCP
------- --- ------- ---
CONNECTION RELEASE CONNECTION RELEASE
Called address server's IP address Called address server's IP address
skipping to change at line 431 skipping to change at line 431
Draft Standards represent the penultimate standard level in the IETF. Draft Standards represent the penultimate standard level in the IETF.
A protocol can only achieve draft standard when there are multiple, A protocol can only achieve draft standard when there are multiple,
independent, interoperable implementations. Draft Standards are usually independent, interoperable implementations. Draft Standards are usually
quite mature and widely used. quite mature and widely used.
4.1 RFC 3551 RTP Profile for Audio and Video Conferences with Minimal 4.1 RFC 3551 RTP Profile for Audio and Video Conferences with Minimal
Control. Control.
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
4.2 RFC 3530 Network File System (NFS) version 4 Protocol
There are no IPv4 dependencies in this specification.
5.0 Proposed Standards 5.0 Proposed Standards
Proposed Standards are introductory level documents. There are no Proposed Standards are introductory level documents. There are no
requirements for even a single implementation. In many cases Proposed requirements for even a single implementation. In many cases Proposed
are never implemented or advanced in the IETF standards process. They are never implemented or advanced in the IETF standards process. They
therefore are often just proposed ideas that are presented to the therefore are often just proposed ideas that are presented to the
Internet community. Sometimes flaws are exposed or they are one of Internet community. Sometimes flaws are exposed or they are one of
many competing solutions to problems. In these later cases, no many competing solutions to problems. In these later cases, no
discussion is presented as it would not serve the purpose of this discussion is presented as it would not serve the purpose of this
discussion. discussion.
skipping to change at line 513 skipping to change at line 517
* NC_NIT "nit" * NC_NIT "nit"
* NC_IEEE802 "ieee802" * NC_IEEE802 "ieee802"
* NC_OSI "osi" * NC_OSI "osi"
* NC_X25 "x25" * NC_X25 "x25"
* NC_OSINET "osinet" * NC_OSINET "osinet"
* NC_GOSIP "gosip" * NC_GOSIP "gosip"
It is clear that the value for NC_INET is intended for the IP protocol It is clear that the value for NC_INET is intended for the IP protocol
and is seems clear that it is IPv4 dependent. and is seems clear that it is IPv4 dependent.
5.08 RFC 1962 The PPP Compression Control Protocol (CCP) 5.07 RFC 1962 The PPP Compression Control Protocol (CCP)
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this protocol.
5.09 RFC 2018 TCP Selective Acknowledgement Options 5.08 RFC 2018 TCP Selective Acknowledgement Options
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this protocol.
5.10 RFC 2029 RTP Payload Format of Sun's CellB Video Encoding 5.09 RFC 2029 RTP Payload Format of Sun's CellB Video Encoding
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this protocol.
5.11 RFC 2032 RTP Payload Format for H.261 Video Streams 5.10 RFC 2032 RTP Payload Format for H.261 Video Streams
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this protocol.
5.12 RFC 2126 ISO Transport Service on top of TCP (ITOT) 5.11 RFC 2126 ISO Transport Service on top of TCP (ITOT)
This protocol is IPv6 aware and has no issues. This protocol is IPv6 aware and has no issues.
5.13 RFC 2190 RTP Payload Format for H.263 Video Streams 5.12 RFC 2190 RTP Payload Format for H.263 Video Streams
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this protocol.
5.14 RFC 2198 RTP Payload for Redundant Audio Data 5.13 RFC 2198 RTP Payload for Redundant Audio Data
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this protocol.
5.15 RFC 2205 Resource ReSerVation Protocol (RSVP) -- 5.14 RFC 2205 Resource ReSerVation Protocol (RSVP) --
Version 1 Functional Specification Version 1 Functional Specification
In Section 1. Introduction the statement is made: In Section 1. Introduction the statement is made:
RSVP operates on top of IPv4 or IPv6, occupying the place of a RSVP operates on top of IPv4 or IPv6, occupying the place of a
transport protocol in the protocol stack. transport protocol in the protocol stack.
Appendix A defines all of the header formats for RSVP and there are Appendix A defines all of the header formats for RSVP and there are
multiple formats for both IPv4 and IPv6. multiple formats for both IPv4 and IPv6.
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this protocol.
5.16 RFC 2207 RSVP Extensions for IPSEC Data Flows 5.15 RFC 2207 RSVP Extensions for IPSEC Data Flows
The defined IPsec extensions are valid for both IPv4 & IPv6. The defined IPsec extensions are valid for both IPv4 & IPv6.
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this protocol.
5.17 RFC 2210 The Use of RSVP with IETF Integrated Services 5.16 RFC 2210 The Use of RSVP with IETF Integrated Services
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this protocol.
5.18 RFC 2211 Specification of the Controlled-Load Network 5.17 RFC 2211 Specification of the Controlled-Load Network
Element Service Element Service
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this protocol.
5.19 RFC 2212 Specification of Guaranteed Quality of Service 5.18 RFC 2212 Specification of Guaranteed Quality of Service
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this protocol.
5.20 RFC 2215 General Characterization Parameters for 5.19 RFC 2215 General Characterization Parameters for
Integrated Service Network Elements Integrated Service Network Elements
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this protocol.
5.21 RFC 2250 RTP Payload Format for MPEG1/MPEG2 Video 5.20 RFC 2250 RTP Payload Format for MPEG1/MPEG2 Video
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this protocol.
5.22 RFC 2326 Real Time Streaming Protocol (RTSP) 5.21 RFC 2326 Real Time Streaming Protocol (RTSP)
Section 3.2 RTSP URL defines: Section 3.2 RTSP URL defines:
The "rtsp" and "rtspu" schemes are used to refer to network resources The "rtsp" and "rtspu" schemes are used to refer to network resources
via the RTSP protocol. This section defines the scheme-specific via the RTSP protocol. This section defines the scheme-specific
syntax and semantics for RTSP URLs. syntax and semantics for RTSP URLs.
rtsp_URL = ( "rtsp:" | "rtspu:" ) rtsp_URL = ( "rtsp:" | "rtspu:" )
"//" host [ ":" port ] [ abs_path ] "//" host [ ":" port ] [ abs_path ]
host = <A legal Internet host domain name of IP address host = <A legal Internet host domain name of IP address
skipping to change at line 633 skipping to change at line 637
a=recvonly a=recvonly
m=audio 3456 RTP/AVP 0 m=audio 3456 RTP/AVP 0
m=video 2232 RTP/AVP 31 m=video 2232 RTP/AVP 31
m=whiteboard 32416 UDP WB m=whiteboard 32416 UDP WB
a=orient:portrait a=orient:portrait
which implies the use of the "IP4" tag and it should be possible to which implies the use of the "IP4" tag and it should be possible to
use an "IP6" tag. There are also numerous other similar examples use an "IP6" tag. There are also numerous other similar examples
using the "IP4" tag. using the "IP4" tag.
There seems to be nothing that requires IPv4, and a small set of RTSP is also dependent on IPv6 support in a protocol capable of
updates can be created to document IPv6 functionality. describing media configurations, for example SDP RFC 2327.
5.23 RFC 2327 SDP: Session Description Protocol (SDP) RTSP can be used over IPv6 as long as the media description protocol
supports IPv6, but only for certain restricted use cases. For full
functionality there is need for IPv6 support. The amount of updates
needed are small.
5.22 RFC 2327 SDP: Session Description Protocol (SDP)
This protocol is under revision, and IPv6 support was addded in This protocol is under revision, and IPv6 support was addded in
RFC 2327 which updates this protocol. RFC 3236 which updates this protocol.
5.24 RFC 2380 RSVP over ATM Implementation Requirements 5.23 RFC 2380 RSVP over ATM Implementation Requirements
This protocol is both IPv4 and IPv6 aware. This protocol is both IPv4 and IPv6 aware.
5.25 RFC 2381 Interoperation of Controlled-Load Service and 5.24 RFC 2381 Interoperation of Controlled-Load Service and
Guaranteed Service with ATM Guaranteed Service with ATM
There does not seem any inherent IPv4 limitations in this protocol, There does not seem any inherent IPv4 limitations in this protocol,
but it assumes work of other standards that have IPv4 limitations. but it assumes work of other standards that have IPv4 limitations.
5.26 RFC 2429 RTP Payload Format for the 1998 Version of ITU-T 5.25 RFC 2429 RTP Payload Format for the 1998 Version of ITU-T
Rec. H.263 Video (H.263+) Rec. H.263 Video (H.263+)
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this protocol.
5.27 RFC 2431 RTP Payload Format for BT.656 Video Encoding 5.26 RFC 2431 RTP Payload Format for BT.656 Video Encoding
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this protocol.
5.28 RFC 2435 RTP Payload Format for JPEG-compressed Video 5.27 RFC 2435 RTP Payload Format for JPEG-compressed Video
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this protocol.
5.29 RFC 2474 Definition of the Differentiated Services Field 5.28 RFC 2474 Definition of the Differentiated Services Field
(DS Field) in the IPv4 and IPv6 Headers (DS Field) in the IPv4 and IPv6 Headers
This protocol is both IPv4 and IPv6 aware. This protocol is both IPv4 and IPv6 aware.
5.30 RFC 2508 Compressing IP/UDP/RTP Headers for Low-Speed 5.29 RFC 2508 Compressing IP/UDP/RTP Headers for Low-Speed
Serial Links Serial Links
This protocol is both IPv4 and IPv6 aware. This protocol is both IPv4 and IPv6 aware.
5.31 RFC 2581 TCP Congestion Control 5.30 RFC 2581 TCP Congestion Control
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this protocol.
5.32 RFC 2597 Assured Forwarding PHB Group 5.31 RFC 2597 Assured Forwarding PHB Group
This protocol is both IPv4 and IPv6 aware. This protocol is both IPv4 and IPv6 aware.
5.33 RFC 2658 RTP Payload Format for PureVoice(tm) Audio 5.32 RFC 2658 RTP Payload Format for PureVoice(tm) Audio
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this protocol.
5.34 RFC 2678 IPPM Metrics for Measuring Connectivity 5.33 RFC 2678 IPPM Metrics for Measuring Connectivity
This protocol only supports IPv4. An updated protocol for IPv6 will This protocol only supports IPv4. An updated protocol for IPv6 will
need to be defined. need to be defined.
5.35 RFC 2679 A One-way Delay Metric for IPPM 5.34 RFC 2679 A One-way Delay Metric for IPPM
This protocol only supports IPv4. An updated protocol for IPv6 will This protocol only supports IPv4. An updated protocol for IPv6 will
need to be defined. need to be defined.
5.36 RFC 2680 A One-way Packet Loss Metric for IPPM 5.35 RFC 2680 A One-way Packet Loss Metric for IPPM
This protocol only supports IPv4. An updated protocol for IPv6 will This protocol only supports IPv4. An updated protocol for IPv6 will
need to be defined. need to be defined.
5.37 RFC 2681 A Round-trip Delay Metric for IPPM 5.36 RFC 2681 A Round-trip Delay Metric for IPPM
This protocol only supports IPv4. An updated protocol for IPv6 will This protocol only supports IPv4. An updated protocol for IPv6 will
need to be defined. need to be defined.
5.38 RFC 2730 Multicast Address Dynamic Client Allocation Protocol 5.37 RFC 2730 Multicast Address Dynamic Client Allocation Protocol
(MADCAP) (MADCAP) (MADCAP)
This protocol is both IPv4 and IPv6 aware and needs no changes. This protocol is both IPv4 and IPv6 aware and needs no changes.
5.39 RFC 2733 An RTP Payload Format for Generic Forward Error 5.38 RFC 2733 An RTP Payload Format for Generic Forward Error
Correction Correction
This protocol is dependent on SDP which has IPv4 dependencies. Once This protocol is dependent on SDP which has IPv4 dependencies. Once
that limitation is fixed, then this protocol should support IPv6. that limitation is fixed, then this protocol should support IPv6.
5.40 RFC 2745 RSVP Diagnostic Messages 5.39 RFC 2745 RSVP Diagnostic Messages
This protocol is both IPv4 and IPv6 aware and needs no changes. This protocol is both IPv4 and IPv6 aware and needs no changes.
5.41 RFC 2746 RSVP Operation Over IP Tunnels 5.40 RFC 2746 RSVP Operation Over IP Tunnels
This protocol is both IPv4 and IPv6 aware and needs no changes. This protocol is both IPv4 and IPv6 aware and needs no changes.
5.42 RFC 2750 RSVP Extensions for Policy Control 5.41 RFC 2750 RSVP Extensions for Policy Control
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this protocol.
5.43 RFC 2793 RTP Payload for Text Conversation 5.42 RFC 2793 RTP Payload for Text Conversation
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this protocol.
5.44 RFC 2814 SBM (Subnet Bandwidth Manager): A Protocol for 5.42 RFC 2814 SBM (Subnet Bandwidth Manager): A Protocol for
RSVP-based Admission Control over IEEE 802-style networks RSVP-based Admission Control over IEEE 802-style networks
This protocol claims to be both IPv4 and IPv6 aware, but all of This protocol claims to be both IPv4 and IPv6 aware, but all of
the examples are given with IPv4 addresses. That, by itself is the examples are given with IPv4 addresses. That, by itself is
not a telling point but the following statement is made: not a telling point but the following statement is made:
a) LocalDSBMAddrInfo -- current DSBM's IP address (initially, a) LocalDSBMAddrInfo -- current DSBM's IP address (initially,
0.0.0.0) and priority. All IP addresses are assumed to be in 0.0.0.0) and priority. All IP addresses are assumed to be in
network byte order. In addition, current DSBM's L2 address is network byte order. In addition, current DSBM's L2 address is
also stored as part of this state information. also stored as part of this state information.
which could just be sloppy wording. Perhaps a short document which could just be sloppy wording. Perhaps a short document
clarifying the text is appropriate. clarifying the text is appropriate.
5.45 RFC 2815 Integrated Service Mappings on IEEE 802 Networks 5.44 RFC 2815 Integrated Service Mappings on IEEE 802 Networks
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this protocol.
5.46 RFC 2833 RTP Payload for DTMF Digits, Telephony Tones 5.45 RFC 2833 RTP Payload for DTMF Digits, Telephony Tones
and Telephony Signals and Telephony Signals
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this protocol.
5.47 RFC 2848 The PINT Service Protocol: Extensions to SIP and SDP 5.46 RFC 2848 The PINT Service Protocol: Extensions to SIP and SDP
for IP Access to Telephone Call Services for IP Access to Telephone Call Services
This protocol is dependent on SDP which has IPv4 dependencies. This protocol is dependent on SDP which has IPv4 dependencies.
Once these limitations are fixed, then this protocol should support Once these limitations are fixed, then this protocol should support
IPv6. IPv6.
5.48 RFC 2862 RTP Payload Format for Real-Time Pointers 5.47 RFC 2862 RTP Payload Format for Real-Time Pointers
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this protocol.
5.49 RFC 2872 Application and Sub Application Identity Policy Element 5.48 RFC 2872 Application and Sub Application Identity Policy Element
for Use with RSVP for Use with RSVP
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this protocol.
5.50 RFC 2873 TCP Processing of the IPv4 Precedence Field 5.49 RFC 2873 TCP Processing of the IPv4 Precedence Field
This protocol documents a technique using IPv4 headers. A similar This protocol documents a technique using IPv4 headers. A similar
technique, if needed, will need to be defined for IPv6. technique, if needed, will need to be defined for IPv6.
5.51 RFC 2883 An Extension to the Selective Acknowledgement (SACK) 5.50 RFC 2883 An Extension to the Selective Acknowledgement (SACK)
Option for TCP Option for TCP
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this protocol.
5.52 RFC 2907 MADCAP Multicast Scope Nesting State Option 5.51 RFC 2907 MADCAP Multicast Scope Nesting State Option
This protocol is both IPv4 and IPv6 aware and needs no changes. This protocol is both IPv4 and IPv6 aware and needs no changes.
5.53 RFC 2960 Stream Control Transmission Protocol 5.52 RFC 2960 Stream Control Transmission Protocol
This protocol is both IPv4 and IPv6 aware and needs no changes. This protocol is both IPv4 and IPv6 aware and needs no changes.
5.54 RFC 2961 RSVP Refresh Overhead Reduction Extensions 5.53 RFC 2961 RSVP Refresh Overhead Reduction Extensions
This protocol is both IPv4 and IPv6 aware and needs no changes. This protocol is both IPv4 and IPv6 aware and needs no changes.
5.55 RFC 2976 The SIP INFO Method 5.54 RFC 2976 The SIP INFO Method
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this protocol.
5.56 RFC 2988 Computing TCP's Retransmission Timer 5.55 RFC 2988 Computing TCP's Retransmission Timer
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this protocol.
5.57 RFC 2996 Format of the RSVP DCLASS Object 5.56 RFC 2996 Format of the RSVP DCLASS Object
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this protocol.
5.58 RFC 2997 Specification of the Null Service Type 5.57 RFC 2997 Specification of the Null Service Type
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this protocol.
5.59 RFC 3003 The audio/mpeg Media Type 5.58 RFC 3003 The audio/mpeg Media Type
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this protocol.
5.60 RFC 3006 Integrated Services in the Presence of 5.59 RFC 3006 Integrated Services in the Presence of
Compressible Flows Compressible Flows
This document defines a protocol that discusses compressible This document defines a protocol that discusses compressible
flows, but only in an IPv4 context. When IPv6 compressible flows flows, but only in an IPv4 context. When IPv6 compressible flows
are defined, a similar technique should also be defined. are defined, a similar technique should also be defined.
5.61 RFC 3016 RTP Payload Format for MPEG-4 Audio/Visual 5.60 RFC 3016 RTP Payload Format for MPEG-4 Audio/Visual
Streams Streams
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this protocol.
5.62 RFC 3033 The Assignment of the Information Field and Protocol 5.61 RFC 3033 The Assignment of the Information Field and Protocol
Identifier in the Q.2941 Generic Identifier and Q.2957 Identifier in the Q.2941 Generic Identifier and Q.2957
User-to-user Signaling for the Internet Protocol User-to-user Signaling for the Internet Protocol
This protocol is both IPv4 and IPv6 aware and needs no changes. This protocol is both IPv4 and IPv6 aware and needs no changes.
5.63 RFC 3042 Enhancing TCP's Loss Recovery Using Limited Transmit 5.62 RFC 3042 Enhancing TCP's Loss Recovery Using Limited Transmit
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this protocol.
5.64 RFC 3047 RTP Payload Format for ITU-T Recommendation G.722.1 5.63 RFC 3047 RTP Payload Format for ITU-T Recommendation G.722.1
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this protocol.
5.65 RFC 3057 ISDN Q.921-User Adaptation Layer 5.64 RFC 3057 ISDN Q.921-User Adaptation Layer
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this protocol.
5.66 RFC 3095 Robust Header Compression (ROHC): Framework and four 5.65 RFC 3095 Robust Header Compression (ROHC): Framework and four
profiles profiles
This protocol is both IPv4 and IPv6 aware and needs no changes. This protocol is both IPv4 and IPv6 aware and needs no changes.
5.67 RFC 3108 Conventions for the use of the Session Description 5.66 RFC 3108 Conventions for the use of the Session Description
Protocol (SDP) for ATM Bearer Connections Protocol (SDP) for ATM Bearer Connections
This protocol is currently limited to IPv4 as amplified below: This protocol is currently limited to IPv4 as amplified below:
The range and format of the <rtcpPortNum> and <rtcpIPaddr> The range and format of the <rtcpPortNum> and <rtcpIPaddr>
subparameters is per [1]. The <rtcpPortNum> is a decimal number subparameters is per [1]. The <rtcpPortNum> is a decimal number
between 1024 and 65535. It is an odd number. If an even number in between 1024 and 65535. It is an odd number. If an even number in
this range is specified, the next odd number is used. The this range is specified, the next odd number is used. The
<rtcpIPaddr> is expressed in the usual dotted decimal IP address <rtcpIPaddr> is expressed in the usual dotted decimal IP address
representation, from 0.0.0.0 to 255.255.255.255. representation, from 0.0.0.0 to 255.255.255.255.
and and
<rtcpIPaddr> IP address for receipt Dotted decimal, 7-15 chars <rtcpIPaddr> IP address for receipt Dotted decimal, 7-15 chars
of RTCP packets of RTCP packets
5.68 RFC 3119 A More Loss-Tolerant RTP Payload Format for MP3 Audio 5.67 RFC 3119 A More Loss-Tolerant RTP Payload Format for MP3 Audio
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this protocol.
5.69 RFC 3124 The Congestion Manager 5.68 RFC 3124 The Congestion Manager
This document is IPv4 limited since it uses the IPv4 TOS header This document is IPv4 limited since it uses the IPv4 TOS header
field. field.
5.70 RFC 3140 Per Hop Behavior Identification Codes 5.69 RFC 3140 Per Hop Behavior Identification Codes
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this protocol.
5.71 RFC 3390 Increasing TCP's Initial Window 5.70 RFC 3173 IP Payload Compression Protocol (IPComp)
There are no IPv4 dependencies in this specification.
5.71 RFC 3181 Signaled Preemption Priority Policy Element
There are no IPv4 dependencies in this specification.
5.72 RFC 3182 Identity Representation for RSVP
There are no IPv4 dependencies in this specification.
5.73 RFC 3246 An Expedited Forwarding PHB (Per-Hop Behavior)
There are no IPv4 dependencies in this specification.
5.74 RFC 3261 SIP: Session Initiation Protocol
There are no IPv4 dependencies in this specification.
5.75 RFC 3262 Reliability of Provisional Responses in Session
Initiation Protocol (SIP)
There are no IPv4 dependencies in this specification.
5.76 RFC 3263 Session Initiation Protocol (SIP): Locating SIP Servers
There are no IPv4 dependencies in this specification.
5.77 RFC 3264 An Offer/Answer Model with Session Description Protocol
(SDP)
There are no IPv4 dependencies in this specification.
5.78 RFC 3265 Session Initiation Protocol (SIP)-Specific Event
Notification
There are no IPv4 dependencies in this specification.
5.79 RFC 3390 Increasing TCP's Initial Window
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this protocol.
5.71 RFC 3550 RTP: A Transport Protocol for Real-Time Applications 5.80 RFC 3525 Gateway Control Protocol Version 1
There are no IPv4 dependencies in this specification.
5.81 RFC 3544 IP Header Compression over PPP
There are no IPv4 dependencies in this specification.
5.82 RFC 3550 RTP: A Transport Protocol for Real-Time Applications
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this protocol.
6.0 Experimental RFCs 6.0 Experimental RFCs
Experimental RFCs typically define protocols that do not have widescale Experimental RFCs typically define protocols that do not have widescale
implementation or usage on the Internet. They are often propriety in implementation or usage on the Internet. They are often propriety in
nature or used in limited arenas. They are documented to the Internet nature or used in limited arenas. They are documented to the Internet
community in order to allow potential interoperability or some other community in order to allow potential interoperability or some other
potential useful scenario. In a few cases they are presented as potential useful scenario. In a few cases they are presented as
skipping to change at line 1087 skipping to change at line 1143
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this protocol.
6.09 RFC 1791 TCP And UDP Over IPX Networks With Fixed Path MTU 6.09 RFC 1791 TCP And UDP Over IPX Networks With Fixed Path MTU
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this protocol.
6.10 RFC 2343 RTP Payload Format for Bundled MPEG 6.10 RFC 2343 RTP Payload Format for Bundled MPEG
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this protocol.
6.12 RFC 2582 The NewReno Modification to TCP's Fast Recovery 6.11 RFC 2582 The NewReno Modification to TCP's Fast Recovery
Algorithm Algorithm
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this protocol.
6.13 RFC 2762 Sampling of the Group Membership in RTP 6.12 RFC 2762 Sampling of the Group Membership in RTP
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
6.14 RFC 2859 A Time Sliding Window Three Colour Marker (TSWTCM) 6.13 RFC 2859 A Time Sliding Window Three Colour Marker (TSWTCM)
This protocol is both IPv4 and IPv6 aware and needs no changes. This protocol is both IPv4 and IPv6 aware and needs no changes.
6.15 RFC 2861 TCP Congestion Window Validation 6.14 RFC 2861 TCP Congestion Window Validation
This protocol is both IPv4 and IPv6 aware and needs no changes. This protocol is both IPv4 and IPv6 aware and needs no changes.
6.16 RFC 2909 The Multicast Address-Set Claim (MASC) Protocol 6.15 RFC 2909 The Multicast Address-Set Claim (MASC) Protocol
This protocol is both IPv4 and IPv6 aware and needs no changes. This protocol is both IPv4 and IPv6 aware and needs no changes.
6.17 RFC 3173 IP Payload Compression Protocol (IPComp)
There are no IPv4 dependencies in this specification.
6.18 RFC 3181 Signaled Preemption Priority Policy Element
There are no IPv4 dependencies in this specification.
6.19 RFC 3182 Identity Representation for RSVP
There are no IPv4 dependencies in this specification.
6.20 RFC 3246 An Expedited Forwarding PHB (Per-Hop Behavior)
There are no IPv4 dependencies in this specification.
6.21 RFC 3261 SIP: Session Initiation Protocol
There are no IPv4 dependencies in this specification.
6.22 RFC 3262 Reliability of Provisional Responses in Session
Initiation Protocol (SIP)
There are no IPv4 dependencies in this specification.
6.23 RFC 3263 Session Initiation Protocol (SIP): Locating SIP Servers
There are no IPv4 dependencies in this specification.
6.24 RFC 3264 An Offer/Answer Model with Session Description Protocol
(SDP)
There are no IPv4 dependencies in this specification.
6.25 RFC 3265 Session Initiation Protocol (SIP)-Specific Event
Notification
There are no IPv4 dependencies in this specification.
6.26 RFC 3525 Gateway Control Protocol Version 1
There are no IPv4 dependencies in this specification.
6.27 RFC 3544 IP Header Compression over PPP
There are no IPv4 dependencies in this specification.
6.28 RFC 3530 Network File System (NFS) version 4 Protocol
There are no IPv4 dependencies in this specification.
7.0 Summary of Results 7.0 Summary of Results
In the initial survey of RFCs 24 positives were identified out of a In the initial survey of RFCs 24 positives were identified out of a
total of 100, broken down as follows: total of 100, broken down as follows:
Standards 4 of 5 or 80.00% Standards 4 of 5 or 80.00%
Draft Standards 0 of 0 or 0.00% Draft Standards 0 of 0 or 0.00%
Proposed Standards 15 of 79 or 18.99% Proposed Standards 15 of 79 or 18.99%
Experimental RFCs 5 of 16 or 31.25% Experimental RFCs 5 of 16 or 31.25%
skipping to change at line 1320 skipping to change at line 1325
9.0 Acknowledgements 9.0 Acknowledgements
The authors would like to acknowledge the support of the Internet The authors would like to acknowledge the support of the Internet
Society in the research and production of this document. Society in the research and production of this document.
Additionally the author, Philip J. Nesser II, would like to thanks Additionally the author, Philip J. Nesser II, would like to thanks
his partner in all ways, Wendy M. Nesser. his partner in all ways, Wendy M. Nesser.
The editor, Andreas Bergstrom, would like to thank Pekka Savola The editor, Andreas Bergstrom, would like to thank Pekka Savola
for guidance and collection of comments for the editing of this for guidance and collection of comments for the editing of this
document. He would further like to thank Allison Mankin and document. He would further like to thank Allison Mankin, Magnus Westerlund and
Collins Perkins for valuable feedback on some points of this document. Colin Perkins for valuable feedback on some points of this document.
10.0 References 10.0 References
10.1 Normative 10.1 Normative
[1] Philip J. Nesser II, Andreas Bergstrom. "Introduction to the Survey [1] Philip J. Nesser II, Andreas Bergstrom. "Introduction to the Survey
of IPv4 Addresses in Currently Deployed IETF Standards", of IPv4 Addresses in Currently Deployed IETF Standards",
draft-ietf-v6ops-ipv4survey-intro-04.txt IETF work in progress, draft-ietf-v6ops-ipv4survey-intro-04.txt IETF work in progress,
September 2003 September 2003
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/