This RFC states:
The active end specifies a passive client through a client-
specific "well-known" 16 bit port number on which the passive
end listens. The active end identifies itself through a 32 bit
Internet address and a unique 16 bit port number.
Clearly, this is IPv4 dependent, but could easily be modified to
support IPv6 addressing.
6.04. RFC 1045 VMTP: Versatile Message Transaction Protocol
This specification has many IPv4 dependencies in its
implementation appendices. For operations over IPv6 a similar
implementation procedure must be defined. The IPv4 specific
information is show below.
IV.1. Domain 1
For initial use of VMTP, we define the domain with Domain
identifier 1 as follows:
+-----------+----------------+------------------------+
| TypeFlags | Discriminator | Internet Address |
+-----------+----------------+------------------------+
4 bits 28 bits 32 bits
The Internet address is the Internet address of the host on
which this entity-id is originally allocated. The
Discriminator is an arbitrary value that is unique relative to
this Internet host address. In addition, the host must
guarantee that this identifier does not get reused for a long
period of time after it becomes invalid. ("Invalid" means that
no VMTP module considers in bound to an entity.) One technique
is to use the lower order bits of a 1 second clock. The clock
need not represent real-time but must never be set back after a
crash. In a simple implementation, using the low order bits of
a clock as the time stamp, the generation of unique identifiers
is overall limited to no more than 1 per second on average.
The type flags were described in Section 3.1.
An entity may migrate between hosts. Thus, an implementation
can heuristically use the embedded Internet address to locate
an entity but should be prepared to maintain a cache of
redirects for migrated entities, plus accept Notify operations
indicating that migration has occurred.
Entity group identifiers in Domain 1 are structured in one of
two forms, depending on whether they are well-known or
dynamically allocated identifiers. A well-known entity
identifier is structured as:
+-----------+----------------+------------------------+
| TypeFlags | Discriminator |Internet Host Group Addr|
+-----------+----------------+------------------------+
4 bits 28 bits 32 bits
with the second high-order bit (GRP) set to 1. This form of
entity identifier is mapped to the Internet host group address
specified in the low-order 32 bits. The Discriminator
distinguishes group identifiers using the same Internet host
group. Well-known entity group identifiers should be allocated
to correspond to the basic services provided by hosts that are
members of the group, not specifically because that service is
provided by VMTP. For example, the well-known entity group
identifier for the domain name service should contain as its
embedded Internet host group address the host group for Domain
Name servers.
A dynamically allocated entity identifier is structured as:
+-----------+----------------+------------------------+
| TypeFlags | Discriminator | Internet Host Addr |
+-----------+----------------+------------------------+
4 bits 28 bits 32 bits
with the second high-order bit (GRP) set to 1. The Internet
address in the low-order 32 bits is a Internet address assigned
to the host that dynamically allocates this entity group
identifier. A dynamically allocated entity group identifier is
mapped to Internet host group address 232.X.X.X where X.X.X are
the low-order 24 bits of the Discriminator subfield of the
entity group identifier.
We use the following notation for Domain 1 entity identifiers
<10> and propose it use as a standard convention.
<flags>-<discriminator>-<Internet address>
where <flags> are [X]{BE,LE,RG,UG}[A]
X = reserved
BE = big-endian entity
LE = little-endian entity
RG = restricted group
UG = unrestricted group
A = alias
and <discriminator> is a decimal integer and <Internet address> is
in standard dotted decimal IP address notation.
V.1. Authentication Domain 1
A principal identifier is structured as follows.
+---------------------------+------------------------+
| Internet Address | Local User Identifier |
+---------------------------+------------------------+
32 bits 32 bits
VI. IP Implementation
VMTP is designed to be implemented on the DoD IP Internet
Datagram Protocol (although it may also be implemented as a
local network protocol directly in "raw" network packets.)
The well-known entity identifiers specified to date are:
VMTP_MANAGER_GROUP RG-1-224.0.1.0
Managers for VMTP operations.
VMTP_DEFAULT_BECLIENT BE-1-224.0.1.0
Client entity identifier to use when a (big-
endian) host has not determined or been allocated
any client entity identifiers.
VMTP_DEFAULT_LECLIENT LE-1-224.0.1.0
Client entity identifier to use when a (little-
endian) host has not determined or been allocated
any client entity identifiers.
Note that 224.0.1.0 is the host group address assigned to VMTP and
to which all VMTP hosts belong.
6.05. RFC 1146 TCP alternate checksum options
There are no IPv4 dependencies in this specification.
6.06. RFC 1151 Version 2 of the Reliable Data Protocol (RDP)
There are no IPv4 dependencies in this specification.
6.07. RFC 1644 T/TCP -- TCP Extensions for Transactions Functional
Specification
There are no IPv4 dependencies in this specification.
6.08. RFC 1693 An Extension to TCP : Partial Order Service
There are no IPv4 dependencies in this specification.
6.09. RFC 1791 TCP And UDP Over IPX Networks With Fixed Path MTU
There are no IPv4 dependencies in this specification.
6.10. RFC 2343 RTP Payload Format for Bundled MPEG
There are no IPv4 dependencies in this specification.
6.11. RFC 2582 The NewReno Modification to TCP’s Fast Recovery
Algorithm
There are no IPv4 dependencies in this specification.
6.12. RFC 2762 Sampling of the Group Membership in RTP
There are no IPv4 dependencies in this specification.
6.13. RFC 2859 A Time Sliding Window Three Colour Marker (TSWTCM)
This specification is both IPv4 and IPv6 aware and needs no
changes.
6.14. RFC 2861 TCP Congestion Window Validation
This specification is both IPv4 and IPv6 aware and needs no
changes.
6.15. RFC 2909 The Multicast Address-Set Claim (MASC) Protocol
This specification is both IPv4 and IPv6 aware and needs no
changes.
7.0. Summary of Results
In the initial survey of RFCs 24 positives were identified out of a
total of 104, broken down as follows:
Standards: 3 out of 5 or 60.00%
Draft Standards: 0 out of 2 or 0.00%
Proposed Standards: 17 out of 82 or 20.73%
Experimental RFCs: 4 out of 15 or 26.67%
Of those identified many require no action because they document
outdated and unused protocols, while others are document protocols
that are actively being updated by the appropriate working groups.
Additionally there are many instances of standards that SHOULD be
updated but do not cause any operational impact if they are not
updated. The remaining instances are documented below.
7.1. Standards
7.1.1. STD 7 Transmission Control Protocol (RFC 793)
Section 3.1 defines the technique for computing the TCP checksum
that uses the 32 bit source and destination IPv4 addresses. This
problem is addressed in RFC 2460 Section 8.1.
7.1.2. STD 19 Netbios over TCP/UDP (RFCs 1001 & 1002)
These two RFCs have many inherent IPv4 assumptions and a new set
of protocols must be defined.
7.1.3. STD 35 ISO Transport over TCP (RFC 1006)
This problem has been fixed in RFC 2126, ISO Transport Service on
top of TCP.
7.2. Draft Standards
There are no draft standards within the scope of this document.
7.3. Proposed Standards
7.3.01. TCP/IP Header Compression over Slow Serial Links (RFC 1144)
This problem has been resolved in RFC2508, Compressing IP/UDP/RTP
Headers for Low-Speed Serial Links. See also RFC 2507 & RFC 2509.
7.3.02. ONC RPC v2 (RFC 1833)
The problems can be resolved with a definition of the NC_INET6
protocol family.
7.3.03. RTSP (RFC 2326)
Problem has been acknowledged by the RTSP developer group and will
be addressed in the move from Proposed to Draft Standard. This
problem is also addressed in RFC 2732, IPv6 Literal Addresses in
URL’s.
7.3.04. SDP (RFC 2327)
One problem is addressed in RFC 2732, IPv6 Literal Addresses in
URL’s. The other problem can be addressed with a minor textual
clarification. This must be done if the document is to transition
from Proposed to Draft. These problems are solved by documents
currently in Auth48 or IESG discuss.
7.3.05. IPPM Metrics (RFC 2678)
The IPPM WG is working to resolve these issues.
7.3.06. IPPM One Way Delay Metric for IPPM (RFC 2679)
The IPPM WG is working to resolve these issues. An ID is
available (draft-ietf-ippm-owdp-03.txt).
7.3.07. IPPM One Way Packet Loss Metric for IPPM (RFC 2680)
The IPPM WG is working to resolve these issues.
7.3.09. Round Trip Delay Metric for IPPM (RFC 2681)
The IPPM WG is working to resolve these issues.
7.3.08. The PINT Service Protocol: Extensions to SIP and SDP for IP
Access to Telephone Call Services(RFC 2848)
This specification is dependent on SDP which has IPv4
dependencies. Once these limitations are fixed, then this
protocol should support IPv6.
7.3.09. TCP Processing of the IPv4 Precedence Field (RFC 2873)
The problems are not being addressed.
7.3.10. Integrated Services in the Presence of Compressible Flows
(RFC 3006)
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.
7.3.11. SDP For ATM Bearer Connections (RFC 3108)
The problems are not being addressed, but it is unclear whether
the specification is being used.
7.3.12. The Congestion Manager (RFC 3124)
An update to this document can be simply define the use of the
IPv6 Traffic Class field since it is defined to be exactly the
same as the IPv4 TOS field.
7.4. Experimental RFCs
7.4.1. Reliable Data Protocol (RFC 908)
This specification relies on IPv4 and a new protocol standard may
be produced.
7.4.2. Internet Reliable Transaction Protocol functional and
interface specification (RFC 938)
This specification relies on IPv4 and a new protocol standard may
be produced.
7.4.3. NETBLT: A bulk data transfer protocol (RFC 998)
This specification relies on IPv4 and a new protocol standard may
be produced.
7.4.4. VMTP: Versatile Message Transaction Protocol (RFC 1045)
This specification relies on IPv4 and a new protocol standard may
be produced.
7.4.5. OSPF over ATM and Proxy-PAR (RFC 2844)
This specification relies on IPv4 and a new protocol standard may
be produced.
8.0. Security Considerations
This memo examines the IPv6-readiness of specifications; this does
not have security considerations in itself.
9.0. Acknowledgements
The authors would like to acknowledge the support of the Internet
Society in the research and production of this document.
Additionally the author, Philip J. Nesser II, would like to thanks
his partner in all ways, Wendy M. Nesser.
The editor, Andreas Bergstrom, would like to thank Pekka Savola for
guidance and collection of comments for the editing of this document.
He would further like to thank Allison Mankin, Magnus Westerlund and
Colin Perkins for valuable feedback on some points of this document.
10.0. Normative Reference
[1] Nesser, II, P. and A. Bergstrom, Editor, "Introduction to the
Survey of IPv4 Addresses in Currently Deployed IETF Standards",
RFC 3789, June 2004.
11.0. Authors’ Addresses
Please contact the authors with any questions, comments or
suggestions at:
Philip J. Nesser II
Principal
Nesser & Nesser Consulting
13501 100th Ave NE, #5202
Kirkland, WA 98034
Phone: +1 425 481 4303
Fax: +1 425 48
EMail: phil@nesser.com
Andreas Bergstrom, Editor
Ostfold University College
Rute 503 Buer
N-1766 Halden
Norway
EMail: andreas.bergstrom@hiof.no
12.0. Full Copyright Statement
Copyright (C) The Internet Society (2004). This document is subject
to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property
The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at ietf-
ipr@ietf.org.
Acknowledgement
Funding for the RFC Editor function is currently provided by the
Internet Society.