draft-ietf-v6ops-ipv4survey-sec-02.txt   draft-ietf-v6ops-ipv4survey-sec-03.txt 
Network Working Group Philip J. Nesser II Network Working Group Philip J. Nesser II
draft-ietf-v6ops-ipv4survey-sec-02.txt Nesser & Nesser Consulting draft-ietf-v6ops-ipv4survey-sec-03.txt Nesser & Nesser Consulting
Internet Draft Andreas Bergstrom Internet Draft Andreas Bergstrom (Ed.)
Ostfold University College Ostfold University College
September 2003 November 2003
Expires February 2004 Expires April 2004
Survey of IPv4 Addresses in Currently Deployed Survey of IPv4 Addresses in Currently Deployed
IETF Security Area Standards IETF Security Area Standards
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.
Status of this Memo
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.
Internet-Drafts are draft documents valid for a maximum of six Internet-Drafts are draft documents valid for a maximum of six
months and may be updated, replaced, or obsoleted by other documents at months and may be updated, replaced, or obsoleted by other documents at
any time. It is inappropriate to use Internet-Drafts as reference any time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
skipping to change at line 60 skipping to change at line 60
5. Proposed Standards 5. Proposed Standards
6. Experimental RFCs 6. Experimental RFCs
7. Summary of Results 7. Summary of Results
7.1 Standards 7.1 Standards
7.2 Draft Standards 7.2 Draft Standards
7.3 Proposed Standards 7.3 Proposed Standards
7.4 Experimental RFCs 7.4 Experimental RFCs
8. Security Consideration 8. Security Consideration
9. Acknowledgements 9. Acknowledgements
10. References 10. References
11. Authors Address 11. Authors' Addresses
12. Intellectual Property Statement 12. Intellectual Property Statement
13. Full Copyright Statement 13. Full Copyright Statement
1.0 Introduction 1.0 Introduction
This document is part of a document set aiming to document all usage of This document is part of a document set aiming to document all usage of
IPv4 addresses in IETF standards. In an effort to have the information IPv4 addresses in IETF standards. In an effort to have the information
in a manageable form, it has been broken into 7 documents conforming in a manageable form, it has been broken into 7 documents conforming
to the current IETF areas (Application, Internet, Manangement & to the current IETF areas (Application, Internet, Management &
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 introduction [1].
2.0 Document Organization 2.0 Document Organization
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 and Proposed Standards, and Experimental RFCs. Each RFC is discussed
in its turn starting with RFC 1 and ending with RFC 3247. The comments in its turn starting with RFC 1 and ending with (around) RFC 3100.
for 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
vacuum and problems or issues discussed do not "look ahead" to see if is discussed in a vacuum and problems or issues discussed do not
the problems have already been fixed. "look 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.
3.1 RFC 2289 A One-Time Password System 3.1 RFC 2289 A One-Time Password System
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
4.0 Draft Standards 4.0 Draft Standards
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 1864 The Content-MD5 Header Field 4.1 RFC 1864 The Content-MD5 Header Field
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
4.2 RFC 2617 HTTP Authentication: Basic and Digest Access 4.2 RFC 2617 HTTP Authentication: Basic and Digest Access
Authentication Authentication
Section 3.2.1 The WWW-Authenticate Response Header include he following Section 3.2.1 The WWW-Authenticate Response Header include he following
text: text:
(Note: including the IP address of the client in the (Note: including the IP address of the client in the
nonce would appear to offer the server the ability to limit the nonce would appear to offer the server the ability to limit the
reuse of the nonce to the same client that originally got it. reuse of the nonce to the same client that originally got it.
skipping to change at line 136 skipping to change at line 136
it contains a digest of the client IP, a time-stamp, the resource it contains a digest of the client IP, a time-stamp, the resource
ETag, and a private server key (as recommended above) then a replay ETag, and a private server key (as recommended above) then a replay
attack is not simple. An attacker must convince the server that the attack is not simple. An attacker must convince the server that the
request is coming from a false IP address and must cause the server request is coming from a false IP address and must cause the server
to deliver the document to an IP address different from the address to deliver the document to an IP address different from the address
to which it believes it is sending the document. An attack can only to which it believes it is sending the document. An attack can only
succeed in the period before the time-stamp expires. Digesting the succeed in the period before the time-stamp expires. Digesting the
client IP and time-stamp in the nonce permits an implementation which client IP and time-stamp in the nonce permits an implementation which
does not maintain state between transactions. does not maintain state between transactions.
Both of these statements are IP version independent and once again must Both of these statements are IP version independent and must
rely on the implementers discretion. rely on the implementers discretion.
4.3 RFC 2865 Remote Authentication Dial In User Service (RADIUS) 4.3 RFC 2865 Remote Authentication Dial In User Service (RADIUS)
Section 3. Packet Format has the following notes: Section 3. Packet Format has the following notes:
Identifier Identifier
The Identifier field is one octet, and aids in matching requests The Identifier field is one octet, and aids in matching requests
and replies. The RADIUS server can detect a duplicate request if and replies. The RADIUS server can detect a duplicate request if
skipping to change at line 371 skipping to change at line 371
class A prefixes, 16 bits for class B prefixes, and 24 bits for class A prefixes, 16 bits for class B prefixes, and 24 bits for
class C prefixes. For example, "192.168.1.0 192.168.1.1 1". class C prefixes. For example, "192.168.1.0 192.168.1.1 1".
Whenever the gateway address is specified as "0.0.0.0" the IP Whenever the gateway address is specified as "0.0.0.0" the IP
address of the user SHOULD be used as the gateway address. address of the user SHOULD be used as the gateway address.
There are also several example authentication sequences that use the There are also several example authentication sequences that use the
attributes discussed above and hence have IPv4 addresses. attributes discussed above and hence have IPv4 addresses.
Although the definitions in this RFC are limited to IPv4 addresses, Although the definitions in this RFC are limited to IPv4 addresses,
the protocol is easily extensible for new attribute types. It is the specification is easily extensible for new attribute types. It is
therefore relatively simple to create new IPv6 specific attributes. therefore relatively simple to create new IPv6 specific attributes.
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 many Internet community. Sometimes flaws are exposed or they are one of many
competing solutions to problems. In these later cases, no discussion is competing solutions to problems. In these later cases, no discussion is
presented as it would not serve the purpose of this discussion. presented as it would not serve the purpose of this discussion.
5.001 RFC 1413 Identification Protocol 5.001 RFC 1413 Identification Protocol
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.002 RFC 1421 Privacy Enhancement for Internet Electronic Mail: 5.002 RFC 1421 Privacy Enhancement for Internet Electronic Mail:
Part I Part I
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.003 RFC 1422 Privacy Enhancement for Internet Electronic Mail: 5.003 RFC 1422 Privacy Enhancement for Internet Electronic Mail:
Part II Part II
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.004 RFC 1423 Privacy Enhancement for Internet Electronic Mail: 5.004 RFC 1423 Privacy Enhancement for Internet Electronic Mail:
Part III Part III
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.005 RFC 1424 Privacy Enhancement for Internet Electronic Mail: 5.005 RFC 1424 Privacy Enhancement for Internet Electronic Mail:
Part IV Part IV
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.006 RFC 1510 The Kerberos Network Authentication Service 5.006 RFC 1510 The Kerberos Network Authentication Service (V5)
(V5)
Although this protocol specifies optional use of host addresses, there Although this specification specifies optional use of host addresses,
are no specific requirements that the addresses be IPv4. The protocol there are no specific requirements that the addresses be IPv4. The
has no IPv4 dependencies, but implementations might have issues. specification has no IPv4 dependencies, but implementations might
have issues.
5.007 RFC 1731 IMAP4 Authentication Mechanisms 5.007 RFC 1731 IMAP4 Authentication Mechanisms
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.008 RFC 1734 POP3 AUTHentication command 5.008 RFC 1734 POP3 AUTHentication command
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.009 RFC 1828 IP Authentication using Keyed MD5 5.009 RFC 1828 IP Authentication using Keyed MD5
There are no IPv4 dependencies in this protocol. The operations There are no IPv4 dependencies in this specification. The operations
described operate on the entire IP packet without specifying that described operate on the entire IP packet without specifying that
the IP packet be IPv4 or IPv6. the IP packet be IPv4 or IPv6.
5.010 RFC 1829 The ESP DES-CBC Transform 5.010 RFC 1829 The ESP DES-CBC Transform
There are no IPv4 dependencies in this protocol. The operations There are no IPv4 dependencies in this specification. The operations
described operate on the entire IP packet without specifying that described operate on the entire IP packet without specifying that
the IP packet be IPv4 or IPv6. the IP packet be IPv4 or IPv6.
5.011 RFC 1847 Security Multiparts for MIME: Multipart/Signed and 5.011 RFC 1847 Security Multiparts for MIME: Multipart/Signed and
Multipart/Encrypted Multipart/Encrypted
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.012 RFC 1848 MIME Object Security Services 5.012 RFC 1848 MIME Object Security Services
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.013 RFC 1928 SOCKS Protocol Version 5.013 RFC 1928 SOCKS Protocol Version
This protocol is IPv6 aware and will function normally on either This specification is IPv6 aware and will function normally on either
IPv4 and IPv6. IPv4 and IPv6.
5.014 RFC 1929 Username/Password Authentication for SOCKS V5 5.014 RFC 1929 Username/Password Authentication for SOCKS V5
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.015 RFC 1961 GSS-API Authentication Method for SOCKS Version 5 5.015 RFC 1961 GSS-API Authentication Method for SOCKS Version 5
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.016 RFC 1964 The Kerberos Version 5 GSS-API Mechanism 5.016 RFC 1964 The Kerberos Version 5 GSS-API Mechanism
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.017 RFC 1968 The PPP Encryption Control Protocol (ECP) 5.017 RFC 1968 The PPP Encryption Control Protocol (ECP)
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.018 RFC 2015 MIME Security with Pretty Good Privacy (PGP) 5.018 RFC 2015 MIME Security with Pretty Good Privacy (PGP)
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.019 RFC 2025 The Simple Public-Key GSS-API Mechanism (SPKM) 5.019 RFC 2025 The Simple Public-Key GSS-API Mechanism (SPKM)
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.020 RFC 2082 RIP-2 MD5 Authentication 5.020 RFC 2082 RIP-2 MD5 Authentication
This RFC documents a security mechanism for an IPv4 only routing This RFC documents a security mechanism for an IPv4 only routing
protocol. It is expected that a similar (or better) mechanism will specification. It is expected that a similar (or better) mechanism will
be developed for RIPng. be developed for RIPng.
5.021 RFC 2085 HMAC-MD5 IP Authentication with Replay Prevention 5.021 RFC 2085 HMAC-MD5 IP Authentication with Replay Prevention
This document defines an IP version independent protocol and has no This document defines an IP version independent specification and has no
IPv4 dependencies. IPv4 dependencies.
5.022 RFC 2195 IMAP/POP AUTHorize Extension for Simple Challenge/ 5.022 RFC 2195 IMAP/POP AUTHorize Extension for Simple Challenge/
Response Response
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.023 RFC 2203 RPCSEC_GSS Protocol Specification 5.023 RFC 2203 RPCSEC_GSS Protocol Specification
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.024 RFC 2222 Simple Authentication and Security Layer (SASL) 5.024 RFC 2222 Simple Authentication and Security Layer (SASL)
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.025 RFC 2228 FTP Security Extensions 5.025 RFC 2228 FTP Security Extensions
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.026 RFC 2243 OTP Extended Responses 5.026 RFC 2243 OTP Extended Responses
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.027 RFC 2245 Anonymous SASL Mechanism 5.027 RFC 2245 Anonymous SASL Mechanism
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.028 RFC 2246 The TLS Protocol Version 1.0 5.028 RFC 2246 The TLS Protocol Version 1.0
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.029 RFC 2284 PPP Extensible Authentication Protocol (EAP) 5.029 RFC 2284 PPP Extensible Authentication Protocol (EAP)
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.030 RFC 2385 Protection of BGP Sessions via the TCP MD5 Signature 5.030 RFC 2385 Protection of BGP Sessions via the TCP MD5 Signature
Option Option
Although the protocol enhancements have no IPv4 dependencies, it is Although the specification enhancements have no IPv4 dependencies, it is
an update to an IPv4 only routing protocol. It is expected that a an update to an IPv4 only routing specification.
newer version of BGP that is IPv6 aware will also implement this
enhancement.
5.031 RFC 2401 Security Architecture for the Internet Protocol 5.031 RFC 2401 Security Architecture for the Internet Protocol
This protocol is both IPv4 and IPv6 aware. This specification is both IPv4 and IPv6 aware.
5.032 RFC 2402 IP Authentication Header 5.032 RFC 2402 IP Authentication Header
This protocol is both IPv4 and IPv6 aware. This specification is both IPv4 and IPv6 aware.
5.033 RFC 2403 The Use of HMAC-MD5-96 within ESP and AH 5.033 RFC 2403 The Use of HMAC-MD5-96 within ESP and AH
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.034 RFC 2404 The Use of HMAC-SHA-1-96 within ESP and AH 5.034 RFC 2404 The Use of HMAC-SHA-1-96 within ESP and AH
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.035 RFC 2405 The ESP DES-CBC Cipher Algorithm With Explicit 5.035 RFC 2405 The ESP DES-CBC Cipher Algorithm With Explicit IV
IV
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.036 RFC 2406 IP Encapsulating Security Payload (ESP) 5.036 RFC 2406 IP Encapsulating Security Payload (ESP)
This protocol is both IPv4 and IPv6 aware.
This specification is both IPv4 and IPv6 aware.
5.037 RFC 2407 The Internet IP Security Domain of Interpretation 5.037 RFC 2407 The Internet IP Security Domain of Interpretation
for ISAKMP for ISAKMP
This protocol is both IPv4 and IPv6 aware. This specification is both IPv4 and IPv6 aware.
5.038 RFC 2408 Internet Security Association and Key Management 5.038 RFC 2408 Internet Security Association and Key Management
Protocol (ISAKMP) Protocol (ISAKMP)
This protocol is both IPv4 and IPv6 aware. This specification is both IPv4 and IPv6 aware.
5.039 RFC 2409 The Internet Key Exchange (IKE) 5.039 RFC 2409 The Internet Key Exchange (IKE)
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.040 RFC 2410 The NULL Encryption Algorithm and Its Use With 5.040 RFC 2410 The NULL Encryption Algorithm and Its Use With
IPsec IPsec
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.041 RFC 2419 The PPP DES Encryption Protocol, Version 2 5.041 RFC 2419 The PPP DES Encryption Protocol, Version 2
(DESE-bis) (DESE-bis)
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.042 RFC 2420 The PPP Triple-DES Encryption Protocol (3DESE) 5.042 RFC 2420 The PPP Triple-DES Encryption Protocol (3DESE)
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.043 RFC 2440 OpenPGP Message Format 5.043 RFC 2440 OpenPGP Message Format
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.044 RFC 2444 The One-Time-Password SASL Mechanism 5.044 RFC 2444 The One-Time-Password SASL Mechanism
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.045 RFC 2451 The ESP CBC-Mode Cipher Algorithms 5.045 RFC 2451 The ESP CBC-Mode Cipher Algorithms
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.046 RFC 2478 The Simple and Protected GSS-API Negotiation 5.046 RFC 2478 The Simple and Protected GSS-API Negotiation
Mechanism Mechanism
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.047 RFC 2510 Internet X.509 Public Key Infrastructure 5.047 RFC 2510 Internet X.509 Public Key Infrastructure
Certificate Management Protocols Certificate Management Protocols
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.048 RFC 2511 Internet X.509 Certificate Request Message 5.048 RFC 2511 Internet X.509 Certificate Request Message
Format Format
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.049 RFC 2535 Domain Name System Security Extensions 5.049 RFC 2535 Domain Name System Security Extensions
There are no IPv4 dependencies in this protocol. There are There are no IPv4 dependencies in this specification. There are
discussions of A and AAAA records in the document, but have no discussions of A and AAAA records in the document, but have no
real implications on IPv4 dependency or on any IP related real implications on IPv4 dependency or on any IP related
address records. address records.
5.050 RFC 2536 DSA KEYs and SIGs in the Domain Name System (DNS) 5.050 RFC 2536 DSA KEYs and SIGs in the Domain Name System (DNS)
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.052 RFC 2538 Storing Certificates in the Domain Name System 5.051 RFC 2538 Storing Certificates in the Domain Name System
(DNS) (DNS)
Section 3.1 X.509 CERT RR Names Section 3.1 X.509 CERT RR Names
Some X.509 versions permit multiple names to be associated with Some X.509 versions permit multiple names to be associated with
subjects and issuers under "Subject Alternate Name" and "Issuer subjects and issuers under "Subject Alternate Name" and "Issuer
Alternate Name". For example, x.509v3 has such Alternate Names with Alternate Name". For example, x.509v3 has such Alternate Names with
an ASN.1 specification as follows: an ASN.1 specification as follows:
GeneralName ::= CHOICE { GeneralName ::= CHOICE {
skipping to change at line 656 skipping to change at line 654
(1) widget.foo.example, (1) widget.foo.example,
(2) 201.13.251.10.in-addr.arpa, and (2) 201.13.251.10.in-addr.arpa, and
(3) hacker.mail.widget.foo.example. (3) hacker.mail.widget.foo.example.
Since the definition of X.509v3 certificates is not discussed in this Since the definition of X.509v3 certificates is not discussed in this
document it is unclear if IPv6 addresses are also supported in the document it is unclear if IPv6 addresses are also supported in the
above mentioned field. The document does however refer to RFC 2459 above mentioned field. The document does however refer to RFC 2459
for the definition of a certificate, and RFC 2459 is IPv6 and IPv4 for the definition of a certificate, and RFC 2459 is IPv6 and IPv4
aware. aware.
5.053 RFC 2539 Storage of Diffie-Hellman Keys in the Domain Name 5.052 RFC 2539 Storage of Diffie-Hellman Keys in the Domain Name
System (DNS) System (DNS)
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.054 RFC 2560 X.509 Internet Public Key Infrastructure Online 5.053 RFC 2560 X.509 Internet Public Key Infrastructure Online
Certificate Status Protocol - OCSP Certificate Status Specification - OCSP
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.055 RFC 2585 Internet X.509 Public Key Infrastructure Operational 5.054 RFC 2585 Internet X.509 Public Key Infrastructure Operational
Protocols: FTP and HTTP Protocols: FTP and HTTP
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.056 RFC 2587 Internet X.509 Public Key Infrastructure LDAPv2 Schema 5.055 RFC 2587 Internet X.509 Public Key Infrastructure LDAPv2 Schema
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.057 RFC 2623 NFS Version 2 and Version 3 Security Issues and the 5.056 RFC 2623 NFS Version 2 and Version 3 Security Issues and the
NFS Protocol's Use of RPCSEC_GSS and Kerberos V5 NFS Protocol's Use of RPCSEC_GSS and Kerberos V5
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.059 RFC 2631 Diffie-Hellman Key Agreement Method
There are no IPv4 dependencies in this protocol.
5.060 RFC 2632 S/MIME Version 3 Certificate Handling 5.057 RFC 2631 Diffie-Hellman Key Agreement Method
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.061 RFC 2633 S/MIME Version 3 Message Specification 5.058 RFC 2632 S/MIME Version 3 Certificate Handling
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.062 RFC 2634 Enhanced Security Services for S/MIME 5.059 RFC 2633 S/MIME Version 3 Message Specification
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.063 RFC 2661 Layer Two Tunneling Protocol "L2TP" 5.060 RFC 2634 Enhanced Security Services for S/MIME
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.064 RFC 2712 Addition of Kerberos Cipher Suites to Transport Layer 5.061 RFC 2712 Addition of Kerberos Cipher Suites to Transport Layer
Security (TLS) Security (TLS)
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.065 RFC 2743 Generic Security Service Application Program Interface 5.062 RFC 2743 Generic Security Service Application Program Interface
Version 2 Update 1 Version 2 Update 1
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.066 RFC 2744 Generic Security Service API Version 2 : C-bindings 5.063 RFC 2744 Generic Security Service API Version 2 : C-bindings
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.067 RFC 2747 RSVP Cryptographic Authentication 5.064 RFC 2747 RSVP Cryptographic Authentication
This protocol is both IPv4 and IPv6 aware and needs no changes. This specification is both IPv4 and IPv6 aware and needs no changes.
5.068 RFC 2797 Certificate Management Messages over CMS 5.065 RFC 2797 Certificate Management Messages over CMS
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.069 RFC 2817 Upgrading to TLS Within HTTP/1.1 5.066 RFC 2817 Upgrading to TLS Within HTTP/1.1
FIXME: requires to be analyzed by subject matter experts. There are no IPv4 dependencies in this specification.
5.069 RFC 2829 Authentication Methods for LDAP 5.067 RFC 2829 Authentication Methods for LDAP
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.070 RFC 2830 Lightweight Directory Access Protocol (v3): 5.068 RFC 2830 Lightweight Directory Access Protocol (v3):
Extension for Transport Layer Security (LDAP) Extension for Transport Layer Security (LDAP)
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.071 RFC 2831 Using Digest Authentication as a SASL Mechanism 5.069 RFC 2831 Using Digest Authentication as a SASL Mechanism
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.072 RFC 2845 Secret Key Transaction Authentication for DNS (TSIG) 5.070 RFC 2845 Secret Key Transaction Authentication for DNS (TSIG)
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.073 RFC 2847 LIPKEY - A Low Infrastructure Public Key Mechanism 5.071 RFC 2847 LIPKEY - A Low Infrastructure Public Key Mechanism
Using SPKM Using SPKM
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.074 RFC 2853 Generic Security Service API Version 2 : Java 5.072 RFC 2853 Generic Security Service API Version 2 : Java
Bindings Bindings
The document uses the InetAddress variable which does not The document uses the InetAddress variable which does not
necessarily limit it to IPv4 addresses so there are no IPv4 necessarily limit it to IPv4 addresses so there are no IPv4
dependencies in this protocol. dependencies in this specification.
5.075 RFC 2857 The Use of HMAC-RIPEMD-160-96 within ESP and AH 5.073 RFC 2857 The Use of HMAC-RIPEMD-160-96 within ESP and AH
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.076 RFC 2875 Diffie-Hellman Proof-of-Possession Algorithms 5.074 RFC 2875 Diffie-Hellman Proof-of-Possession Algorithms
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.077 RFC 2930 Secret Key Establishment for DNS (TKEY RR) 5.075 RFC 2930 Secret Key Establishment for DNS (TKEY RR)
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.078 RFC 2931 DNS Request and Transaction Signatures 5.076 RFC 2931 DNS Request and Transaction Signatures
(SIG(0)s) (SIG(0)s)
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.079 RFC 2935 Internet Open Trading Protocol (IOTP) HTTP 5.077 RFC 2935 Internet Open Trading Protocol (IOTP) HTTP
Supplement Supplement
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.080 RFC 2941 Telnet Authentication Option 5.078 RFC 2941 Telnet Authentication Option
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.081 RFC 2942 Telnet Authentication: Kerberos Version 5 5.079 RFC 2942 Telnet Authentication: Kerberos Version 5
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.082 RFC 2943 TELNET Authentication Using DSA 5.080 RFC 2943 TELNET Authentication Using DSA
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.083 RFC 2944 Telnet Authentication: SRP 5.081 RFC 2944 Telnet Authentication: SRP
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.084 RFC 2945 The SRP Authentication and Key Exchange 5.082 RFC 2945 The SRP Authentication and Key Exchange
System System
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.085 RFC 2946 Telnet Data Encryption Option 5.083 RFC 2946 Telnet Data Encryption Option
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.086 RFC 2947 Telnet Encryption: DES3 64 bit Cipher 5.084 RFC 2947 Telnet Encryption: DES3 64 bit Cipher
Feedback Feedback
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.087 RFC 2948 Telnet Encryption: DES3 64 bit Output 5.085 RFC 2948 Telnet Encryption: DES3 64 bit Output
Feedback Feedback
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.088 RFC 2949 Telnet Encryption: CAST-128 64 bit Output 5.086 RFC 2949 Telnet Encryption: CAST-128 64 bit Output
Feedback Feedback
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.089 RFC 2950 Telnet Encryption: CAST-128 64 bit Cipher 5.087 RFC 2950 Telnet Encryption: CAST-128 64 bit Cipher
Feedback Feedback
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.090 RFC 2984 Use of the CAST-128 Encryption Algorithm in CMS 5.088 RFC 2984 Use of the CAST-128 Encryption Algorithm in CMS
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.091 RFC 3007 Secure Domain Name System (DNS) Dynamic Update 5.089 RFC 3007 Secure Domain Name System (DNS) Dynamic Update
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.092 RFC 3008 Domain Name System Security (DNSSEC) Signing 5.090 RFC 3008 Domain Name System Security (DNSSEC) Signing
Authority Authority
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.093 RFC 3012 Mobile IPv4 Challenge/Response Extensions 5.091 RFC 3012 Mobile IPv4 Challenge/Response Extensions
This document is specifically designed for IPv4. This document is specifically designed for IPv4.
5.094 RFC 3039 Internet X.509 Public Key Infrastructure Qualified 5.092 RFC 3039 Internet X.509 Public Key Infrastructure Qualified
Certificates Profile Certificates Profile
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.095 RFC 3041 Privacy Extensions for Stateless Address 5.093 RFC 3041 Privacy Extensions for Stateless Address
Autoconfiguration in IPv6 Autoconfiguration in IPv6
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.096 RFC 3062 LDAP Password Modify Extended Operation 5.094 RFC 3062 LDAP Password Modify Extended Operation
There are no IPv4 dependencies in this protocol.
5.097 RFC 3070 Layer Two Tunneling Protocol (L2TP) over
Frame Relay
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.099 RFC 3090 DNS Security Extension Clarification on Zone Status 5.095 RFC 3090 DNS Security Extension Clarification on Zone Status
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.100 RFC 3097 RSVP Cryptographic Authentication -- Updated Message 5.096 RFC 3097 RSVP Cryptographic Authentication -- Updated Message
Type Value Type Value
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.101 RFC 3110 RSA/SHA-1 SIGs and RSA KEYs in the Domain Name 5.097 RFC 3110 RSA/SHA-1 SIGs and RSA KEYs in the Domain Name
System (DNS) System (DNS)
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.102 RFC 3118 Authentication for DHCP Messages 5.098 RFC 3118 Authentication for DHCP Messages
This document is only designated for IPv4. It is expected that This document is only designated for IPv4. It is expected that
similar functionality is available in DHCPv6. similar functionality is available in DHCPv6.
5.103 RFC 3207 SMTP Service Extension for Secure SMTP over Transport 5.099 RFC 3207 SMTP Service Extension for Secure SMTP over Transport
Layer Security Layer Security
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.104 RFC 3275 (Extensible Markup Language) XML-Signature Syntax and 5.100 RFC 3275 (Extensible Markup Language) XML-Signature Syntax and
Processing Processing
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.105 RFC 3280 Internet X.509 Public Key Infrastructure Certificate and 5.101 RFC 3280 Internet X.509 Public Key Infrastructure Certificate and
Certificate Revocation List (CRL) Profile Certificate Revocation List (CRL) Profile
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.106 RFC 3369 Cryptographic Message Syntax (CMS) 5.102 RFC 3369 Cryptographic Message Syntax (CMS)
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
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
alternatives to the mainstream solution to an acknowledged problem. alternatives to the mainstream solution to an acknowledged problem.
6.01 RFC 1004 Distributed-protocol authentication scheme 6.01 RFC 1004 Distributed-protocol authentication scheme
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
6.02 RFC 1411 Telnet Authentication: Kerberos Version 4 6.02 RFC 1411 Telnet Authentication: Kerberos Version 4
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
6.03 RFC 1412 Telnet Authentication: SPX 6.03 RFC 1412 Telnet Authentication: SPX
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
6.04 RFC 1507 DASS - Distributed Authentication Security Service 6.04 RFC 1507 DASS - Distributed Authentication Security Service
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
6.05 RFC 1851 The ESP Triple DES Transform 6.05 RFC 1851 The ESP Triple DES Transform
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
6.06 RFC 1949 Scalable Multicast Key Distribution (SMKD) 6.06 RFC 1949 Scalable Multicast Key Distribution (SMKD)
This protocol assumes the use of IGMP and is therefore limited to This specification assumes the use of IGMP and is therefore limited to
IPv4 multicast. It is assumed that a similar mechanism may be IPv4 multicast. It is assumed that a similar mechanism may be
defined for IPv6 multicasting. defined for IPv6 multicasting.
6.07 RFC 2093 Group Key Management Protocol (GKMP) Specification 6.07 RFC 2093 Group Key Management Protocol (GKMP) Specification
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
6.08 RFC 2094 Group Key Management Protocol (GKMP) Architecture 6.08 RFC 2094 Group Key Management Protocol (GKMP) Architecture
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
6.09 RFC 2154 OSPF with Digital Signatures 6.09 RFC 2154 OSPF with Digital Signatures
This OSPF option is IPv4 limited. See the following packet This OSPF option is IPv4 limited. See the following packet
format: format:
7.2. Router Public Key Certificate 7.2. Router Public Key Certificate
A router public key certificate is a package of data signed by a A router public key certificate is a package of data signed by a
Trusted Entity. This certificate is included in the router PKLSA and Trusted Entity. This certificate is included in the router PKLSA and
skipping to change at line 992 skipping to change at line 981
mask=0 will allow a router to advertise any address. mask=0 will allow a router to advertise any address.
IP ADDRESS & ADDRESS MASK IP ADDRESS & ADDRESS MASK
Define a range of addresses that this router may Define a range of addresses that this router may
advertise. Each is a 32 bit value. One range with advertise. Each is a 32 bit value. One range with
address=0 and mask=0 will allow a router to advertise address=0 and mask=0 will allow a router to advertise
any address. any address.
6.10 RFC 2522 Photuris: Session-Key Management Protocol 6.10 RFC 2522 Photuris: Session-Key Management Protocol
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
6.11 RFC 2523 Photuris: Extended Schemes and Attributes 6.11 RFC 2523 Photuris: Extended Schemes and Attributes
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
6.12 RFC 2659 Security Extensions For HTML 6.12 RFC 2659 Security Extensions For HTML
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
6.13 RFC 2660 The Secure HyperText Transfer Protocol 6.13 RFC 2660 The Secure HyperText Transfer Protocol
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
6.14 RFC 2692 SPKI Requirements 6.14 RFC 2692 SPKI Requirements
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
6.15 RFC 2693 SPKI Certificate Theory 6.15 RFC 2693 SPKI Certificate Theory
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
6.16 RFC 2716 PPP EAP TLS Authentication Protocol 6.16 RFC 2716 PPP EAP TLS Authentication Protocol
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
6.17 RFC 2773 Encryption using KEA and SKIPJACK 6.17 RFC 2773 Encryption using KEA and SKIPJACK
This protocol is both IPv4 and IPv6 aware and needs no changes. This specification is both IPv4 and IPv6 aware and needs no changes.
6.18 RFC 3029 Internet X.509 Public Key Infrastructure Data 6.18 RFC 3029 Internet X.509 Public Key Infrastructure Data
Validation and Certification Server Protocols Validation and Certification Server Protocols
There are no IPv4 dependencies in this 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 6 positives were identified out of a In the initial survey of RFCs 4 positives were identified out of a
total of 126, broken down as follows: total of 124, broken down as follows:
Standards 0 of 1 or 0.00% Standards 0 of 1 or 0.00%
Draft Standards 1 of 3 or 33.33% Draft Standards 1 of 3 or 33.33%
Proposed Standards 3 of 104 or 2.88% Proposed Standards 1 of 102 or 0.98%
Experimental RFCs 2 of 18 or 11.11% Experimental RFCs 2 of 18 or 11.11%
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. The remaining instances are documented below. updated. The remaining instances are documented below.
7.1 Standards 7.1 Standards
7.2 Draft Standards 7.2 Draft Standards
7.2.1 RADIUS (RFC 2865) 7.2.1 RADIUS (RFC 2865)
The problems have been resolved in RFC 3162, RADIUS and IPv6. The problems have been resolved in RFC 3162, RADIUS and IPv6.
7.3 Proposed Standards 7.3 Proposed Standards
7.3.1 RIPv2 MD5 Authentication (RFC 2082) 7.3.1 RIPv2 MD5 Authentication (RFC 2082)
This functionality has been assumed by the use of the IPsec AH This functionality has been assumed by the use of the IPsec AH
header as defined in RFC 2402, IP Authentication Header. header as defined in RFC 2402, IP Authentication Header.
7.3.2 Protection of BGP via TCP MD5 Signatures (RFC 2385) 7.3.2 Mobile IPv4 Challenge Response Extension (RFC 3012)
These issues are addressed via using BGP4 plus RFC 2283,
Multiprotocol Extensions for BGP-4.
7.3.3 Mobile IPv4 Challenge Response Extension (RFC 3012)
The problems are not being addressed and must be addressed in a new The problems are not being addressed and similar functions may
protocol. be needed in Mobile IPv6.
7.3.4 Authentication for DHCP Messages (RFC 3118) 7.3.3 Authentication for DHCP Messages (RFC 3118)
The problem is being fixed by the work of the DHC WG. Several very This problem has been fixed in RFC 3315, Dynamic Host Configuration
advanced IDs address all the issues. Protocol for IPv6 (DHCPv6).
7.4 Experimental RFCs 7.4 Experimental RFCs
7.4.1 Scalable Multicast Key Distribution (RFC 1949) 7.4.1 Scalable Multicast Key Distribution (RFC 1949)
This protocol relies on IPv4 IGMP Multicast and a new protocol This specification relies on IPv4 IGMP Multicast and a new specification
standard may be produced. may be produced; however, the SMKD is not believed to be in use.
8.0 Security Consideration 8.0 Security Consideration
This memo examines the IPv6-readiness of specifications; this does not This memo examines the IPv6-readiness of specifications; this does not
have security considerations in itself. have security considerations in itself.
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.
skipping to change at line 1103 skipping to change at line 1087
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. document.
10.0 References 10.0 References
10.1 Normative 10.1 Normative
[1] Philip J. Nesser II, Andreas Bergstrom. "Introduction to the [1] Philip J. Nesser II, Andreas Bergstrom. "Introduction to the
Survey of IPv4 Addresses in Currently Deployed IETF Standards", Survey of IPv4 Addresses in Currently Deployed IETF Standards",
draft-ietf-v6ops-ipv4survey-intro-04.txt IETF work in progress, draft-ietf-v6ops-ipv4survey-intro-05.txt IETF work in progress,
September 2003 November 2003
11.0 Authors Addresses 11.0 Authors' Addresses
Please contact the author with any questions, comments or suggestions Please contact the author with any questions, comments or suggestions
at: at:
Philip J. Nesser II Philip J. Nesser II
Principal Principal
Nesser & Nesser Consulting Nesser & Nesser Consulting
13501 100th Ave NE, #5202 13501 100th Ave NE, #5202
Kirkland, WA 98034 Kirkland, WA 98034
Email: phil@nesser.com Email: phil@nesser.com
Phone: +1 425 481 4303 Phone: +1 425 481 4303
Fax: +1 425 48 Fax: +1 425 48
Andreas Bergstrom Andreas Bergstrom (Editor)
Ostfold University College Ostfold University College
Email: andreas.bergstrom@hiof.no Email: andreas.bergstrom@hiof.no
Address: Rute 503 Buer Address: Rute 503 Buer
N-1766 Halden N-1766 Halden
Norway Norway
12.0 Intellectual Property Statement 12.0 Intellectual Property Statement
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to intellectual property or other rights that might be claimed to
 End of changes. 

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