There is also a large amount of pseudo code for most of the
protocols functionality that make no specific reference to IPv4
addresses. 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.
3.5. RFC 1006 ISO Transport Service on top of the TCP (Version: 3)
Section 5. The Protocol defines a mapping specification
Mapping parameters is also straight-forward:
network service TCP
------- ---
CONNECTION RELEASE
Called address server’s IP address
(4 octets)
Calling address client’s IP address
(4 octets)
4.0. Draft Standards
Draft Standards represent the penultimate standard level in the IETF.
A protocol can only achieve draft standard when there are multiple,
independent, interoperable implementations. Draft Standards are
usually quite mature and widely used.
4.1. RFC 3530 Network File System (NFS) version 4 Protocol
There are no IPv4 dependencies in this specification.
4.2. RFC 3550 RTP: A Transport Protocol for Real-Time Applications
There are no IPv4 dependencies in this specification.
4.3. RFC 3551 RTP Profile for Audio and Video Conferences with
Minimal Control.
There are no IPv4 dependencies in this specification.
5.0. Proposed Standards
Proposed Standards are introductory level documents. There are no
requirements for even a single implementation. In many cases
Proposed are never implemented or advanced in the IETF standards
process. They therefore are often just proposed ideas that are
presented to the Internet community. Sometimes flaws are exposed or
they are one of many competing solutions to problems. In these later
cases, no discussion is presented as it would not serve the purpose
of this discussion.
5.01. RFC 1144 Compressing TCP/IP headers for low-speed serial
links
This RFC is specifically oriented towards TCP/IPv4 packet headers
and will not work in it’s current form. Significant work has
already been done on similar algorithms for TCP/IPv6 headers.
5.02. RFC 1323 TCP Extensions for High Performance
There are no IPv4 dependencies in this specification.
5.03. RFC 1553 Compressing IPX Headers Over WAN Media (CIPX)
There are no IPv4 dependencies in this specification.
5.04. RFC 1692 Transport Multiplexing Protocol (TMux)
Section 6. Implementation Notes is states:
Because the TMux mini-header does not contain a TOS field, only
segments with the same IP TOS field should be contained in a
single TMux message. As most systems do not use the TOS
feature, this is not a major restriction. Where the TOS field
is used, it may be desirable to hold several messages under
construction for a host, one for each TOS value.
Segments containing IP options should not be multiplexed.
This is clearly IPv4 specific, but a simple restatement in IPv6
terms will allow complete functionality.
5.05. RFC 1831 RPC: Remote Procedure Call Protocol
Specification Version 2 RPC
There are no IPv4 dependencies in this specification.
5.06. RFC 1833 Binding Protocols for ONC RPC Version 2
In Section 2.1 RPCBIND Protocol Specification (in RPC Language)
there is the following code fragment:
* Protocol family (r_nc_protofmly):
* This identifies the family to which the protocol belongs.
* The following values are defined:
* NC_NOPROTOFMLY "-"
* NC_LOOPBACK "loopback"
* NC_INET "inet"
* NC_IMPLINK "implink"
* NC_PUP "pup"
* NC_CHAOS "chaos"
* NC_NS "ns"
* NC_NBS "nbs"
* NC_ECMA "ecma"
* NC_DATAKIT "datakit"
* NC_CCITT "ccitt"
* NC_SNA "sna"
* NC_DECNET "decnet"
* NC_DLI "dli"
* NC_LAT "lat"
* NC_HYLINK "hylink"
* NC_APPLETALK "appletalk"
* NC_NIT "nit"
* NC_IEEE802 "ieee802"
* NC_OSI "osi"
* NC_X25 "x25"
* NC_OSINET "osinet"
* NC_GOSIP "gosip"
It is clear that the value for NC_INET is intended for the IP
protocol and is seems clear that it is IPv4 dependent.
5.07. RFC 1962 The PPP Compression Control Protocol (CCP)
There are no IPv4 dependencies in this specification.
5.08. RFC 2018 TCP Selective Acknowledgement Options
There are no IPv4 dependencies in this specification.
5.09. RFC 2029 RTP Payload Format of Sun’s CellB Video Encoding
There are no IPv4 dependencies in this specification.
5.10. RFC 2032 RTP Payload Format for H.261 Video Streams
There are no IPv4 dependencies in this specification.
5.11. RFC 2126 ISO Transport Service on top of TCP (ITOT)
This specification is IPv6 aware and has no issues.
5.12. RFC 2190 RTP Payload Format for H.263 Video Streams
There are no IPv4 dependencies in this specification.
5.13. RFC 2198 RTP Payload for Redundant Audio Data
There are no IPv4 dependencies in this specification.
5.14. RFC 2205 Resource ReSerVation Protocol (RSVP) --
Version 1 Functional Specification
In Section 1. Introduction the statement is made:
RSVP operates on top of IPv4 or IPv6, occupying the place of a
transport protocol in the protocol stack.
Appendix A defines all of the header formats for RSVP and there
are multiple formats for both IPv4 and IPv6.
There are no IPv4 dependencies in this specification.
5.15. RFC 2207 RSVP Extensions for IPSEC Data Flows
The defined IPsec extensions are valid for both IPv4 & IPv6.
There are no IPv4 dependencies in this specification.
5.16. RFC 2210 The Use of RSVP with IETF Integrated Services
There are no IPv4 dependencies in this specification.
5.17. RFC 2211 Specification of the Controlled-Load Network
Element Service
There are no IPv4 dependencies in this specification.
5.18. RFC 2212 Specification of Guaranteed Quality of Service
There are no IPv4 dependencies in this specification.
5.19. RFC 2215 General Characterization Parameters for
Integrated Service Network Elements
There are no IPv4 dependencies in this specification.
5.20. RFC 2250 RTP Payload Format for MPEG1/MPEG2 Video
There are no IPv4 dependencies in this specification.
5.21. RFC 2326 Real Time Streaming Protocol (RTSP)
Section 3.2 RTSP URL defines:
The "rtsp" and "rtspu" schemes are used to refer to network
resources via the RTSP protocol. This section defines the
scheme-specific syntax and semantics for RTSP URLs.
rtsp_URL = ( "rtsp:" | "rtspu:" )
"//" host [ ":" port ] [ abs_path ]
host = <A legal Internet host domain name of IP
address (in dotted decimal form), as defined
by Section 2.1 of RFC 1123 \cite{rfc1123}>
port = *DIGIT
Although later in that section the following text is added:
The use of IP addresses in URLs SHOULD be avoided whenever
possible (see RFC 1924 [19]).
Some later examples show:
Example:
C->S: DESCRIBE rtsp://server.example.com/fizzle/foo RTSP/1.0
CSeq: 312
Accept: application/sdp, application/rtsl,
application/mheg
S->C: RTSP/1.0 200 OK
CSeq: 312
Date: 23 Jan 1997 15:35:06 GMT
Content-Type: application/sdp
Content-Length: 376
v=0
o=mhandley 2890844526 2890842807 IN IP4 126.16.64.4
s=SDP Seminar
i=A Seminar on the session description protocol
u=http://www.cs.ucl.ac.uk/staff/M.Handley/sdp.03.ps
e=mjh@isi.edu (Mark Handley)
c=IN IP4 224.2.17.12/127
t=2873397496 2873404696
a=recvonly
m=audio 3456 RTP/AVP 0
m=video 2232 RTP/AVP 31
m=whiteboard 32416 UDP WB
a=orient:portrait
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 using the "IP4" tag.
RTSP is also dependent on IPv6 support in a protocol capable of
describing media configurations, for example SDP RFC 2327.
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 specification is under revision, and IPv6 support was added
in RFC 3266 which updates this specification.
5.23. RFC 2380 RSVP over ATM Implementation Requirements
This specification is both IPv4 and IPv6 aware.
5.24. RFC 2381 Interoperation of Controlled-Load Service and
Guaranteed Service with ATM
There does not seem any inherent IPv4 limitations in this
specification, but it assumes work of other standards that have
IPv4 limitations.
5.25. RFC 2429 RTP Payload Format for the 1998 Version of ITU-T
Rec. H.263 Video (H.263+)
There are no IPv4 dependencies in this specification.
5.26. RFC 2431 RTP Payload Format for BT.656 Video Encoding
There are no IPv4 dependencies in this specification.
5.27. RFC 2435 RTP Payload Format for JPEG-compressed Video
There are no IPv4 dependencies in this specification.
5.28. RFC 2474 Definition of the Differentiated Services Field
(DS Field) in the IPv4 and IPv6 Headers
This specification is both IPv4 and IPv6 aware.
5.29. RFC 2508 Compressing IP/UDP/RTP Headers for Low-Speed
Serial Links
This specification is both IPv4 and IPv6 aware.
5.30. RFC 2581 TCP Congestion Control
There are no IPv4 dependencies in this specification.
5.31. RFC 2597 Assured Forwarding PHB Group
This specification is both IPv4 and IPv6 aware.
5.32. RFC 2658 RTP Payload Format for PureVoice(tm) Audio
There are no IPv4 dependencies in this specification.
5.33. RFC 2678 IPPM Metrics for Measuring Connectivity
This specification only supports IPv4.
5.34. RFC 2679 A One-way Delay Metric for IPPM
This specification only supports IPv4.
5.35. RFC 2680 A One-way Packet Loss Metric for IPPM
This specification only supports IPv4.
5.36. RFC 2681 A Round-trip Delay Metric for IPPM
This specification only supports IPv4.
5.37. RFC 2730 Multicast Address Dynamic Client Allocation Protocol
(MADCAP)
This specification is both IPv4 and IPv6 aware and needs no
changes.
5.38. RFC 2733 An RTP Payload Format for Generic Forward Error
Correction
This specification is dependent on SDP which has IPv4
dependencies. Once that limitation is fixed, then this
specification should support IPv6.
5.39. RFC 2745 RSVP Diagnostic Messages
This specification is both IPv4 and IPv6 aware and needs no
changes.
5.40. RFC 2746 RSVP Operation Over IP Tunnels
This specification is both IPv4 and IPv6 aware and needs no
changes.
5.41. RFC 2750 RSVP Extensions for Policy Control
There are no IPv4 dependencies in this specification.
5.42. RFC 2793 RTP Payload for Text Conversation
There are no IPv4 dependencies in this specification.
5.43. RFC 2814 SBM (Subnet Bandwidth Manager): A Protocol for
RSVP-based Admission Control over IEEE 802-style networks
This specification claims to be both IPv4 and IPv6 aware, but all
of the examples are given with IPv4 addresses. That, by itself is
not a telling point but the following statement is made:
a) LocalDSBMAddrInfo -- current DSBM’s IP address (initially,
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
also stored as part of this state information.
which could just be sloppy wording. Perhaps a short document
clarifying the text is appropriate.
5.44. RFC 2815 Integrated Service Mappings on IEEE 802 Networks
There are no IPv4 dependencies in this specification.
5.45. RFC 2833 RTP Payload for DTMF Digits, Telephony Tones
and Telephony Signals
There are no IPv4 dependencies in this specification.
5.46. RFC 2848 The PINT Service Protocol: Extensions to SIP and
SDP for IP Access to Telephone Call Services
This specification is dependent on SDP which has IPv4
dependencies. Once these limitations are fixed, then this
specification should support IPv6.
5.47. RFC 2862 RTP Payload Format for Real-Time Pointers
There are no IPv4 dependencies in this specification.
5.48. RFC 2872 Application and Sub Application Identity Policy
Element for Use with RSVP
There are no IPv4 dependencies in this specification.
5.49. RFC 2873 TCP Processing of the IPv4 Precedence Field
This specification documents a technique using IPv4 headers. A
similar technique, if needed, will need to be defined for IPv6.
5.50. RFC 2883 An Extension to the Selective Acknowledgement (SACK)
Option for TCP
There are no IPv4 dependencies in this specification.
5.51. RFC 2907 MADCAP Multicast Scope Nesting State Option
This specification is both IPv4 and IPv6 aware and needs no
changes.
5.52. RFC 2960 Stream Control Transmission Protocol
This specification is both IPv4 and IPv6 aware and needs no
changes.
5.53. RFC 2961 RSVP Refresh Overhead Reduction Extensions
This specification is both IPv4 and IPv6 aware and needs no
changes.
5.54. RFC 2976 The SIP INFO Method
There are no IPv4 dependencies in this specification.
5.55. RFC 2988 Computing TCP’s Retransmission Timer
There are no IPv4 dependencies in this specification.
5.56. RFC 2996 Format of the RSVP DCLASS Object
There are no IPv4 dependencies in this specification.
5.57. RFC 2997 Specification of the Null Service Type
There are no IPv4 dependencies in this specification.
5.58. RFC 3003 The audio/mpeg Media Type
There are no IPv4 dependencies in this specification.
5.59. RFC 3006 Integrated Services in the Presence of
Compressible Flows
This document defines a protocol that discusses compressible
flows, but only in an IPv4 context. When IPv6 compressible flows
are defined, a similar technique should also be defined.
5.60. RFC 3016 RTP Payload Format for MPEG-4 Audio/Visual
Streams
There are no IPv4 dependencies in this specification.
5.61. RFC 3033 The Assignment of the Information Field and
Protocol Identifier in the Q.2941 Generic Identifier and
Q.2957 User-to-user Signaling for the Internet Protocol
This specification is both IPv4 and IPv6 aware and needs no
changes.
5.62. RFC 3042 Enhancing TCP’s Loss Recovery Using Limited Transmit
There are no IPv4 dependencies in this specification.
5.63. RFC 3047 RTP Payload Format for ITU-T Recommendation G.722.1
There are no IPv4 dependencies in this specification.
5.64. RFC 3057 ISDN Q.921-User Adaptation Layer
There are no IPv4 dependencies in this specification.
5.65. RFC 3095 Robust Header Compression (ROHC): Framework and four
profiles
This specification is both IPv4 and IPv6 aware and needs no
changes.
5.66. RFC 3108 Conventions for the use of the Session Description
Protocol (SDP) for ATM Bearer Connections
This specification is currently limited to IPv4 as amplified
below:
The range and format of the <rtcpPortNum> and <rtcpIPaddr>
subparameters is per [1]. The <rtcpPortNum> is a decimal
number 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 <rtcpIPaddr> is expressed in the usual dotted
decimal IP address representation, from 0.0.0.0 to
255.255.255.255.
and
<rtcpIPaddr> IP address for receipt Dotted decimal,
7-15 chars of RTCP packets
5.67. RFC 3119 A More Loss-Tolerant RTP Payload Format for MP3 Audio
There are no IPv4 dependencies in this specification.
5.68. RFC 3124 The Congestion Manager
This document is IPv4 limited since it uses the IPv4 TOS header
field.
5.69. RFC 3140 Per Hop Behavior Identification Codes
There are no IPv4 dependencies in this specification.
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 specification.
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.
6.0. Experimental RFCs
Experimental RFCs typically define protocols that do not have
widescale implementation or usage on the Internet. They are often
propriety in nature or used in limited arenas. They are documented
to the Internet community in order to allow potential
interoperability or some other potential useful scenario. In a few
cases they are presented as alternatives to the mainstream solution
to an acknowledged problem.
6.1. RFC 908 Reliable Data Protocol (RDP)
This document is IPv4 limited as stated in the following section:
4.1. IP Header Format
When used in the internet environment, RDP segments are sent
using the version 4 IP header as described in RFC791, "Internet
Protocol." The RDP protocol number is ??? (decimal). The
time-to-live field should be set to a reasonable value for the
network.
All other fields should be set as specified in RFC-791.
A new protocol specification would be needed to support IPv6.
6.02. RFC 938 Internet Reliable Transaction Protocol functional and
interface specification (IRTP)
This specification states:
4.1. State Variables
Each IRTP is associated with a single internet address. The
synchronization mechanism of the IRTP depends on the
requirement that each IRTP module knows the internet addresses
of all modules with which it will communicate. For each remote
internet address, an IRTP module must maintain the following
information (called the connection table):
rem_addr (32 bit remote internet address)
A new specification that is IPv6 aware would need to be created.
6.03. RFC 998 NETBLT: A bulk data transfer protocol