There are no IPv4 dependencies in this specification.
5.045. RFC 2451 The ESP CBC-Mode Cipher Algorithms
There are no IPv4 dependencies in this specification.
5.046. RFC 2478 The Simple and Protected GSS-API Negotiation
Mechanism
There are no IPv4 dependencies in this specification.
5.047. RFC 2510 Internet X.509 Public Key Infrastructure
Certificate Management Protocols
There are no IPv4 dependencies in this specification.
5.048. RFC 2511 Internet X.509 Certificate Request Message
Format
There are no IPv4 dependencies in this specification.
5.049. RFC 2535 Domain Name System Security Extensions
There are no IPv4 dependencies in this specification. There are
discussions of A and AAAA records in the document, but have no
real implications on IPv4 dependency or on any IP related address
records.
5.050. RFC 2536 DSA KEYs and SIGs in the Domain Name System (DNS)
There are no IPv4 dependencies in this specification.
5.051. RFC 2538 Storing Certificates in the Domain Name System
(DNS)
Section 3.1 X.509 CERT RR Names
Some X.509 versions permit multiple names to be associated with
subjects and issuers under "Subject Alternate Name" and "Issuer
Alternate Name". For example, x.509v3 has such Alternate Names
with an ASN.1 specification as follows:
GeneralName ::= CHOICE {
otherName [0] INSTANCE OF OTHER-NAME,
rfc822Name [1] IA5String,
dNSName [2] IA5String,
x400Address [3] EXPLICIT OR-ADDRESS.&Type,
directoryName [4] EXPLICIT Name,
ediPartyName [5] EDIPartyName,
uniformResourceIdentifier [6] IA5String,
iPAddress [7] OCTET STRING,
registeredID [8] OBJECT IDENTIFIER
}
uses a potential IPv4 only address. It goes on with the following
example:
Example 2: Assume that an X.509v3 certificate is issued to
/CN=James Hacker/L=Basingstoke/O=Widget Inc/C=GB/ with Subject
Alternate names of (a) domain name widget.foo.example,
(b) IPv4 address 10.251.13.201, and (c) string "James Hacker
<hacker@mail.widget.foo.example>". Then the storage locations
recommended, in priority order, would be
(1) widget.foo.example,
(2) 201.13.251.10.in-addr.arpa, and
(3) hacker.mail.widget.foo.example.
Since the definition of X.509v3 certificates is not discussed in this
document it is unclear if IPv6 addresses are also supported in the
above mentioned field. The document does however refer to RFC 2459
for the definition of a certificate, and RFC 2459 is IPv6 and IPv4
aware -- so it seems this specification is IPv4 and IPv6 aware.
5.052. RFC 2539 Storage of Diffie-Hellman Keys in the Domain
Name System (DNS)
There are no IPv4 dependencies in this specification.
5.053. RFC 2560 X.509 Internet Public Key Infrastructure Online
Certificate Status Specification - OCSP
There are no IPv4 dependencies in this specification.
5.054. RFC 2585 Internet X.509 Public Key Infrastructure Operational
Protocols: FTP and HTTP
There are no IPv4 dependencies in this specification.
5.055. RFC 2587 Internet X.509 Public Key Infrastructure
LDAPv2 Schema
There are no IPv4 dependencies in this specification.
5.056. RFC 2623 NFS Version 2 and Version 3 Security Issues and the
NFS Protocol’s Use of RPCSEC_GSS and Kerberos V5
There are no IPv4 dependencies in this specification.
5.057. RFC 2631 Diffie-Hellman Key Agreement Method
There are no IPv4 dependencies in this specification.
5.058. RFC 2632 S/MIME Version 3 Certificate Handling
There are no IPv4 dependencies in this specification.
5.059. RFC 2633 S/MIME Version 3 Message Specification
There are no IPv4 dependencies in this specification.
5.060. RFC 2634 Enhanced Security Services for S/MIME
There are no IPv4 dependencies in this specification.
5.061. RFC 2712 Addition of Kerberos Cipher Suites to Transport
Layer Security (TLS)
There are no IPv4 dependencies in this specification.
5.062. RFC 2743 Generic Security Service Application Program
Interface Version 2 Update 1
There are no IPv4 dependencies in this specification.
5.063. RFC 2744 Generic Security Service API Version 2:
C-bindings
There are no IPv4 dependencies in this specification.
5.064. RFC 2747 RSVP Cryptographic Authentication
This specification is both IPv4 and IPv6 aware and needs no
changes.
5.065. RFC 2797 Certificate Management Messages over CMS
There are no IPv4 dependencies in this specification.
5.066. RFC 2817 Upgrading to TLS Within HTTP/1.1
There are no IPv4 dependencies in this specification.
5.067. RFC 2829 Authentication Methods for LDAP
There are no IPv4 dependencies in this specification.
5.068. RFC 2830 Lightweight Directory Access Protocol (v3):
Extension for Transport Layer Security (LDAP)
There are no IPv4 dependencies in this specification.
5.069. RFC 2831 Using Digest Authentication as a SASL Mechanism
There are no IPv4 dependencies in this specification.
5.070. RFC 2845 Secret Key Transaction Authentication for DNS (TSIG)
There are no IPv4 dependencies in this specification.
5.071. RFC 2847 LIPKEY - A Low Infrastructure Public Key
Mechanism Using SPKM
There are no IPv4 dependencies in this specification.
5.072. RFC 2853 Generic Security Service API Version 2 :
Java Bindings
The document uses the InetAddress variable which does not
necessarily limit it to IPv4 addresses so there are no IPv4
dependencies in this specification.
5.073. RFC 2857 The Use of HMAC-RIPEMD-160-96 within ESP and AH
There are no IPv4 dependencies in this specification.
5.074. RFC 2875 Diffie-Hellman Proof-of-Possession Algorithms
There are no IPv4 dependencies in this specification.
5.075. RFC 2930 Secret Key Establishment for DNS (TKEY RR)
There are no IPv4 dependencies in this specification.
5.076. RFC 2931 DNS Request and Transaction
Signatures (SIG(0)s)
There are no IPv4 dependencies in this specification.
5.077. RFC 2935 Internet Open Trading Protocol (IOTP)
HTTP Supplement
There are no IPv4 dependencies in this specification.
5.078. RFC 2941 Telnet Authentication Option
There are no IPv4 dependencies in this specification.
5.079. RFC 2942 Telnet Authentication: Kerberos Version 5
There are no IPv4 dependencies in this specification.
5.080. RFC 2943 TELNET Authentication Using DSA
There are no IPv4 dependencies in this specification.
5.081. RFC 2944 Telnet Authentication: SRP
There are no IPv4 dependencies in this specification.
5.082. RFC 2945 The SRP Authentication and Key
Exchange System
There are no IPv4 dependencies in this specification.
5.083. RFC 2946 Telnet Data Encryption Option
There are no IPv4 dependencies in this specification.
5.084. RFC 2947 Telnet Encryption: DES3 64 bit Cipher
Feedback
There are no IPv4 dependencies in this specification.
5.085. RFC 2948 Telnet Encryption: DES3 64 bit Output
Feedback
There are no IPv4 dependencies in this specification.
5.086. RFC 2949 Telnet Encryption: CAST-128 64 bit Output
Feedback
There are no IPv4 dependencies in this specification.
5.087. RFC 2950 Telnet Encryption: CAST-128 64 bit Cipher
Feedback
There are no IPv4 dependencies in this specification.
5.088. RFC 2984 Use of the CAST-128 Encryption Algorithm in CMS
There are no IPv4 dependencies in this specification.
5.089. RFC 3007 Secure Domain Name System (DNS) Dynamic Update
There are no IPv4 dependencies in this specification.
5.090. RFC 3008 Domain Name System Security (DNSSEC) Signing
Authority
There are no IPv4 dependencies in this specification.
5.091. RFC 3012 Mobile IPv4 Challenge/Response Extensions
This document is specifically designed for IPv4.
5.092. RFC 3039 Internet X.509 Public Key Infrastructure
Qualified Certificates Profile
There are no IPv4 dependencies in this specification.
5.093. RFC 3041 Privacy Extensions for Stateless Address
Autoconfiguration in IPv6
This is an IPv6 related document and is not discussed in this
document.
5.094. RFC 3062 LDAP Password Modify Extended Operation
There are no IPv4 dependencies in this specification.
5.095. RFC 3090 DNS Security Extension Clarification on Zone
Status
There are no IPv4 dependencies in this specification.
5.096. RFC 3097 RSVP Cryptographic Authentication --
Updated Message Type Value
There are no IPv4 dependencies in this specification.
5.097. RFC 3110 RSA/SHA-1 SIGs and RSA KEYs in the Domain
Name System (DNS)
There are no IPv4 dependencies in this specification.
5.098. RFC 3118 Authentication for DHCP Messages
This document is only designated for IPv4. It is expected that
similar functionality is available in DHCPv6.
5.099. RFC 3207 SMTP Service Extension for Secure SMTP over
Transport Layer Security
There are no IPv4 dependencies in this specification.
5.100. RFC 3275 (Extensible Markup Language) XML-Signature
Syntax and Processing
There are no IPv4 dependencies in this specification.
5.101. RFC 3280 Internet X.509 Public Key Infrastructure
Certificate and Certificate Revocation List (CRL) Profile
This specification is IPv4 and IPv6 aware.
5.102. RFC 3369 Cryptographic Message Syntax (CMS)
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.01. RFC 1004 Distributed-protocol authentication scheme
There are no IPv4 dependencies in this specification.
6.02. RFC 1411 Telnet Authentication: Kerberos Version 4
There are no IPv4 dependencies in this specification.
6.03. RFC 1412 Telnet Authentication: SPX
There are no IPv4 dependencies in this specification.
6.04. RFC 1507 DASS - Distributed Authentication Security Service
There are no IPv4 dependencies in this specification.
6.05. RFC 1851 The ESP Triple DES Transform
There are no IPv4 dependencies in this specification.
6.06. RFC 1949 Scalable Multicast Key Distribution (SMKD)
This specification assumes the use of IGMP and is therefore
limited to IPv4 multicast. It is assumed that a similar mechanism
may be defined for IPv6 multicasting.
6.07. RFC 2093 Group Key Management Protocol (GKMP) Specification
There are no IPv4 dependencies in this specification.
6.08. RFC 2094 Group Key Management Protocol (GKMP) Architecture
There are no IPv4 dependencies in this specification.
6.09. RFC 2154 OSPF with Digital Signatures
This OSPF option is IPv4 limited. See the following packet
format:
7.2. Router Public Key Certificate
A router public key certificate is a package of data signed by
a Trusted Entity. This certificate is included in the router
PKLSA and in the router configuration information. To change
any of the values in the certificate, a new certificate must be
obtained from a TE.
1 1 1 1 1 1 1 1 1 1 2 2 2 2 2 2 2 2 2 2 3 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
+-+-+-+-+-+-+-+-*-+-+-+-+-+-+-+-*-+-+-+-+-+-+-+-*-+-+-+-+-+-+-+-+
| Router Id |
+-+-+-+-+-+-+-+-*-+-+-+-+-+-+-+-*-+-+-+-+-+-+-+-*-+-+-+-+-+-+-+-+
| TE Id | TE Key Id | Rtr Key Id | Sig Alg |
+-+-+-+-+-+-+-+-*-+-+-+-+-+-+-+-*-+-+-+-+-+-+-+-*-+-+-+-+-+-+-+-+
| Create Time |
+-+-+-+-+-+-+-+-*-+-+-+-+-+-+-+-*-+-+-+-+-+-+-+-*-+-+-+-+-+-+-+-+
| Key Field Length | Router Role | #Net Ranges |
+-+-+-+-+-+-+-+-*-+-+-+-+-+-+-+-*-+-+-+-+-+-+-+-*-+-+-+-+-+-+-+-+
| IP Address |
+-+-+-+-+-+-+-+-*-+-+-+-+-+-+-+-*-+-+-+-+-+-+-+-*-+-+-+-+-+-+-+-+
| Address Mask |
+-+-+-+-+-+-+-+-*-+-+-+-+-+-+-+-*-+-+-+-+-+-+-+-*-+-+-+-+-+-+-+-+
| IP Address/Address Mask for each Net Range ... /
| ... /
+-+-+-+-+-+-+-+-*-+-+-+-+-+-+-+-*-+-+-+-+-+-+-+-*-+-+-+-+-+-+-+-+
| Router Public Key |
+-+-+-+-+-+-+-+-*-+-+-+-+-+-+-+-*-+-+-+-+-+-+-+-*-+-+-+-+-+-+-+-+
| Certification /
+-+-+-+-+-+-+-+-*-+-+-+-+-+-+-+-*-+-+-+-+-+-+-+-*-+-+-+-+-+-+-+-+
#NET RANGES The number of network ranges that follow. A
network range is defined to be an IP Address
and an Address Mask. This list of ranges
defines the addresses that the Router is
permitted to advertise in its Router Links LSA.
Valid values are 0-255. If there are 0 ranges
the router cannot advertise anything. This is
not generally useful. One range with address=0
and mask=0 will allow a router to advertise any
address.
IP ADDRESS & ADDRESS MASK Define a range of addresses that this
router may advertise. Each is a 32 bit value.
One range with address=0 and mask=0 will allow
a router to advertise any address.
6.10. RFC 2522 Photuris: Session-Key Management Protocol
There are no IPv4 dependencies in this specification.
6.11. RFC 2523 Photuris: Extended Schemes and Attributes
There are no IPv4 dependencies in this specification.
6.12. RFC 2659 Security Extensions For HTML
There are no IPv4 dependencies in this specification.
6.13. RFC 2660 The Secure HyperText Transfer Protocol
There are no IPv4 dependencies in this specification.
6.14. RFC 2692 SPKI Requirements
There are no IPv4 dependencies in this specification.
6.15. RFC 2693 SPKI Certificate Theory
There are no IPv4 dependencies in this specification.
6.16. RFC 2716 PPP EAP TLS Authentication Protocol
There are no IPv4 dependencies in this specification.
6.17. RFC 2773 Encryption using KEA and SKIPJACK
This specification is both IPv4 and IPv6 aware and needs no
changes.
6.18. RFC 3029 Internet X.509 Public Key Infrastructure Data
Validation and Certification Server Protocols
There are no IPv4 dependencies in this specification.
7.0. Summary of Results
In the initial survey of RFCs 4 positives were identified out of a
total of 124, broken down as follows:
Standards: 0 out of 1 or 0.00%
Draft Standards: 1 out of 3 or 33.33%
Proposed Standards: 1 out of 102 or 0.98%
Experimental RFCs: 2 out of 18 or 11.11%
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.2. Draft Standards
7.2.1. RADIUS (RFC 2865)
The problems have been resolved in RFC 3162, RADIUS and IPv6.
7.3. Proposed Standards
7.3.1. RIPv2 MD5 Authentication (RFC 2082)
This functionality has been assumed by the use of the IPsec AH
header as defined in RFC 2402, IP Authentication Header.
7.3.2. Mobile IPv4 Challenge Response Extension (RFC 3012)
The problems are not being addressed and similar functions may be
needed in Mobile IPv6.
7.3.3. Authentication for DHCP Messages (RFC 3118)
This problem has been fixed in RFC 3315, Dynamic Host
Configuration Protocol for IPv6 (DHCPv6).
7.4. Experimental RFCs
7.4.1. Scalable Multicast Key Distribution (RFC 1949)
This specification relies on IPv4 IGMP Multicast and a new
specification may be produced; however, the SMKD is not believed
to be in use.
7.4.2. OPSF with Digital Signatures (RFC 2154)
This specification is IPv4-only, and relies on an IPv4-only
routing protocol, OSPFv2. Due to increased focus on routing
security, this specification may need to be revisited, and in that
case it should support both OSPFv2 and OPSFv3.
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.
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 author 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.