draft-ietf-v6ops-ipv4survey-sec-04.txt   rfc3792.txt 
Network Working Group Philip J. Nesser II
draft-ietf-v6ops-ipv4survey-sec-04.txt Nesser & Nesser Consulting Network Working Group P. Nesser, II
Internet Draft Andreas Bergstrom (Ed.) Request for Comments: 3792 Nesser & Nesser Consulting
Category: Informational A. Bergstrom, Ed.
Ostfold University College Ostfold University College
December 2003 June 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 Track and Experimental Documents
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This memo provides information for the Internet community. It does
all provisions of Section 10 of RFC2026. not specify an Internet standard of any kind. Distribution of this
memo is unlimited.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that other
groups may also distribute working documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six
months and may be updated, replaced, or obsoleted by other documents at
any time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at Copyright Notice
http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at Copyright (C) The Internet Society (2004).
http://www.ietf.org/shadow.html.
Abstract Abstract
This document seeks to document all usage of IPv4 addresses in currently This document seeks to document all usage of IPv4 addresses in
deployed IETF Security Area documented standards. In order to currently deployed IETF Security Area documented standards. In order
successfully transition from an all IPv4 Internet to an all IPv6 to successfully transition from an all IPv4 Internet to an all IPv6
Internet, many interim steps will be taken. One of these steps is the Internet, many interim steps will be taken. One of these steps is
evolution of current protocols that have IPv4 dependencies. It is hoped the evolution of current protocols that have IPv4 dependencies. It
that these protocols (and their implementations) will be redesigned to is hoped that these protocols (and their implementations) will be
be network address independent, but failing that will at least dually redesigned to be network address independent, but failing that will
support IPv4 and IPv6. To this end, all Standards (Full, Draft, and at least dually support IPv4 and IPv6. To this end, all Standards
Proposed) as well as Experimental RFCs will be surveyed and any (Full, Draft, and Proposed) as well as Experimental RFCs will be
dependencies will be documented. surveyed and any dependencies will be documented.
Table of Contents Table of Contents
1. Introduction 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Document Organisation 2. Document Organisation. . . . . . . . . . . . . . . . . . . . . 2
3. Full Standards 3. Full Standards . . . . . . . . . . . . . . . . . . . . . . . . 2
4. Draft Standards 4. Draft Standards. . . . . . . . . . . . . . . . . . . . . . . . 2
5. Proposed Standards 5. Proposed Standards . . . . . . . . . . . . . . . . . . . . . . 8
6. Experimental RFCs 6. Experimental RFCs. . . . . . . . . . . . . . . . . . . . . . . 20
7. Summary of Results 7. Summary of Results . . . . . . . . . . . . . . . . . . . . . . 22
7.1 Standards 7.1. Standards. . . . . . . . . . . . . . . . . . . . . . . . 23
7.2 Draft Standards 7.2. Draft Standards. . . . . . . . . . . . . . . . . . . . . 23
7.3 Proposed Standards 7.3. Proposed Standards . . . . . . . . . . . . . . . . . . . 23
7.4 Experimental RFCs 7.4. Experimental RFCs. . . . . . . . . . . . . . . . . . . . 23
8. Security Consideration 8. Security Considerations. . . . . . . . . . . . . . . . . . . . 24
9. Acknowledgements 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 24
10. References 10. Normative Reference. . . . . . . . . . . . . . . . . . . . . . 24
11. Authors' Addresses 11. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 24
12. Intellectual Property Statement 12. Full Copyright Statement . . . . . . . . . . . . . . . . . . . 25
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
IPv4 addresses in IETF standards. In an effort to have the information of IPv4 addresses in IETF standards. In an effort to have the
in a manageable form, it has been broken into 7 documents conforming information in a manageable form, it has been broken into 7 documents
to the current IETF areas (Application, Internet, Management & conforming to the current IETF areas (Application, Internet,
Operations, Routing, Security, Sub-IP and Transport). Operations and Management, Routing, Security, Sub-IP, and Transport).
For a full introduction, please see the introduction [1]. 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,
and Proposed Standards, and Experimental RFCs. Each RFC is discussed Draft, and Proposed Standards, and Experimental RFCs. Each RFC is
in its turn starting with RFC 1 and ending with (around) RFC 3100. discussed in its turn starting with RFC 1 and ending with (around)
The comments for each RFC are "raw" in nature. That is, each RFC RFC 3100. The comments for each RFC are "raw" in nature. That is,
is discussed in a vacuum and problems or issues discussed do not each RFC is discussed in a vacuum and problems or issues discussed do
"look ahead" to see if the problems have already been fixed. not "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,
6. It is here that all of the results are considered as a whole and the and 6. It is here that all of the results are considered as a whole
problems that have been resolved in later RFCs are correlated. and the 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 specification. 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
quite mature and widely used. usually 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 specification. 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
text: following text:
(Note: including the IP address of the client in the (Note: including the IP address of the client in the nonce
nonce would appear to offer the server the ability to limit the would appear to offer the server the ability to limit the reuse
reuse of the nonce to the same client that originally got it. of the nonce to the same client that originally got it.
However, that would break proxy farms, where requests from a single However, that would break proxy farms, where requests from a
user often go through different proxies in the farm. Also, IP single user often go through different proxies in the farm.
address spoofing is not that hard.) Also, IP address spoofing is not that hard.)
Section 4.5 Replay Attacks contains the text: Section 4.5 Replay Attacks contains the text:
Thus, for some purposes, it is necessary to protect against replay Thus, for some purposes, it is necessary to protect against
attacks. A good Digest implementation can do this in various ways. replay attacks. A good Digest implementation can do this in
The server created "nonce" value is implementation dependent, but if various ways. The server created "nonce" value is
it contains a digest of the client IP, a time-stamp, the resource implementation dependent, but if it contains a digest of the
ETag, and a private server key (as recommended above) then a replay client IP, a time-stamp, the resource ETag, and a private
attack is not simple. An attacker must convince the server that the server key (as recommended above) then a replay attack is not
request is coming from a false IP address and must cause the server simple. An attacker must convince the server that the request
to deliver the document to an IP address different from the address is coming from a false IP address and must cause the server to
to which it believes it is sending the document. An attack can only deliver the document to an IP address different from the
succeed in the period before the time-stamp expires. Digesting the address to which it believes it is sending the document. An
client IP and time-stamp in the nonce permits an implementation which attack can only succeed in the period before the time-stamp
does not maintain state between transactions. expires. Digesting the client IP and time-stamp in the nonce
permits an implementation which does not maintain state between
transactions.
Both of these statements are IP version independent and must Both of these statements are IP version independent and must rely on
rely on the implementers discretion. 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
and replies. The RADIUS server can detect a duplicate request if requests and replies. The RADIUS server can detect a duplicate
it has the same client source IP address and source UDP port and request if it has the same client source IP address and source
Identifier within a short span of time. UDP port and Identifier within a short span of time.
and and
A RADIUS server MUST use the source IP address of the RADIUS UDP A RADIUS server MUST use the source IP address of the RADIUS
packet to decide which shared secret to use, so that RADIUS UDP packet to decide which shared secret to use, so that RADIUS
requests can be proxied. requests can be proxied.
This text is version neutral but implementers should allow for the use This text is version neutral but implementers should allow for the
of both IPv4 and IPv6 addresses. use of both IPv4 and IPv6 addresses.
Section 5. Attributes defines a number of IP specific attributes: Section 5. Attributes defines a number of IP specific attributes:
4 NAS-IP-Address 4 NAS-IP-Address
8 Framed-IP-Address 8 Framed-IP-Address
9 Framed-IP-Netmask 9 Framed-IP-Netmask
10 Framed-Routing 10 Framed-Routing
14 Login-IP-Host 14 Login-IP-Host
22 Framed-Route 22 Framed-Route
and definitions for the "value" field of the following type: and definitions for the "value" field of the following type:
address 32 bit value, most significant octet first. address 32 bit value, most significant octet first.
The attributes are further defined as follows: The attributes are further defined as follows:
5.4. NAS-IP-Address 5.4. NAS-IP-Address
Description Description
This Attribute indicates the identifying IP Address of the NAS This Attribute indicates the identifying IP Address of the
which is requesting authentication of the user, and SHOULD be NAS which is requesting authentication of the user, and
unique to the NAS within the scope of the RADIUS server. NAS-IP- SHOULD be unique to the NAS within the scope of the RADIUS
Address is only used in Access-Request packets. Either NAS-IP- server. NAS-IP-Address is only used in Access-Request
Address or NAS-Identifier MUST be present in an Access-Request packets. Either NAS-IP-Address or NAS-Identifier MUST be
packet. present in an Access-Request packet.
Note that NAS-IP-Address MUST NOT be used to select the shared Note that NAS-IP-Address MUST NOT be used to select the
secret used to authenticate the request. The source IP address of shared secret used to authenticate the request. The source
the Access-Request packet MUST be used to select the shared IP address of the Access-Request packet MUST be used to
secret. select the shared secret.
A summary of the NAS-IP-Address Attribute format is shown below. The A summary of the NAS-IP-Address Attribute format is shown
fields are transmitted from left to right. below. The fields are transmitted from left to right.
0 1 2 3 0 1 2 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 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Address | Type | Length | Address
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Address (cont) | Address (cont) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type Type
skipping to change at line 218 skipping to change at page 5, line 30
Address Address
The Address field is four octets. The Address field is four octets.
5.8. Framed-IP-Address 5.8. Framed-IP-Address
Description Description
This Attribute indicates the address to be configured for the This Attribute indicates the address to be configured for the
user. It MAY be used in Access-Accept packets. It MAY be used in user. It MAY be used in Access-Accept packets. It MAY be used
an Access-Request packet as a hint by the NAS to the server that in an Access-Request packet as a hint by the NAS to the server
it would prefer that address, but the server is not required to that it would prefer that address, but the server is not
honor the hint. required to honor the hint.
A summary of the Framed-IP-Address Attribute format is shown below. A summary of the Framed-IP-Address Attribute format is shown below.
The fields are transmitted from left to right. The fields are transmitted from left to right.
0 1 2 3 0 1 2 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 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Address | Type | Length | Address
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Address (cont) | Address (cont) |
skipping to change at line 241 skipping to change at page 6, line 4
Address (cont) | Address (cont) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type Type
8 for Framed-IP-Address. 8 for Framed-IP-Address.
Length Length
6 6
Address Address
The Address field is four octets. The value 0xFFFFFFFF indicates The Address field is four octets. The value 0xFFFFFFFF indicates
that the NAS Should allow the user to select an address (e.g. that the NAS Should allow the user to select an address (e.g.,
Negotiated). The value 0xFFFFFFFE indicates that the NAS should Negotiated). The value 0xFFFFFFFE indicates that the NAS should
select an address for the user (e.g. Assigned from a pool of select an address for the user (e.g., Assigned from a pool of
addresses kept by the NAS). Other valid values indicate that the addresses kept by the NAS). Other valid values indicate that the
NAS should use that value as the user's IP address. NAS should use that value as the user's IP address.
5.9. Framed-IP-Netmask 5.9. Framed-IP-Netmask
Description Description
This Attribute indicates the IP netmask to be configured for the This Attribute indicates the IP netmask to be configured for
user when the user is a router to a network. It MAY be used in the user when the user is a router to a network. It MAY be
Access-Accept packets. It MAY be used in an Access-Request packet used in Access-Accept packets. It MAY be used in an Access-
as a hint by the NAS to the server that it would prefer that Request packet as a hint by the NAS to the server that it would
netmask, but the server is not required to honor the hint. prefer that netmask, but the server is not required to honor
the hint.
A summary of the Framed-IP-Netmask Attribute format is shown below. A summary of the Framed-IP-Netmask Attribute format is shown below.
The fields are transmitted from left to right. The fields are transmitted from left to right.
0 1 2 3 0 1 2 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 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Address | Type | Length | Address
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Address (cont) | Address (cont) |
skipping to change at line 289 skipping to change at page 7, line 9
Address Address
The Address field is four octets specifying the IP netmask of the The Address field is four octets specifying the IP netmask of the
user. user.
5.14. Login-IP-Host 5.14. Login-IP-Host
Description Description
"This Attribute indicates the system with which to connect the user, "This Attribute indicates the system with which to connect the
when the Login-Service Attribute is included. It MAY be used in user, when the Login-Service Attribute is included. It MAY be
Access-Accept packets. It MAY be used in an Access-Request packet as used in Access-Accept packets. It MAY be used in an Access-
a hint to the server that the NAS would prefer to use that host, but Request packet as a hint to the server that the NAS would
the server is not required to honor the hint." prefer to use that host, but the server is not required to
honor the hint."
A summary of the Login-IP-Host Attribute format is shown below. The A summary of the Login-IP-Host Attribute format is shown below. The
fields are transmitted from left to right. fields are transmitted from left to right.
0 1 2 3 0 1 2 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 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Address | Type | Length | Address
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Address (cont) | Address (cont) |
skipping to change at line 326 skipping to change at page 7, line 47
The Address field is four octets. The value 0xFFFFFFFF indicates The Address field is four octets. The value 0xFFFFFFFF indicates
that the NAS SHOULD allow the user to select an address. The that the NAS SHOULD allow the user to select an address. The
value 0 indicates that the NAS SHOULD select a host to connect the value 0 indicates that the NAS SHOULD select a host to connect the
user to. Other values indicate the address the NAS SHOULD connect user to. Other values indicate the address the NAS SHOULD connect
the user to. the user to.
5.22. Framed-Route 5.22. Framed-Route
Description Description
This Attribute provides routing information to be configured for This Attribute provides routing information to be configured
the user on the NAS. It is used in the Access-Accept packet and for the user on the NAS. It is used in the Access-Accept
can appear multiple times. packet and can appear multiple times.
A summary of the Framed-Route Attribute format is shown below. The A summary of the Framed-Route Attribute format is shown below. The
fields are transmitted from left to right. fields are transmitted from left to right.
0 1 2 0 1 2
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-
| Type | Length | Text ... | Type | Length | Text ...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-
skipping to change at line 371 skipping to change at page 8, line 43
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 specification is easily extensible for new attribute types. It is the specification is easily extensible for new attribute types. It
therefore relatively simple to create new IPv6 specific attributes. is 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
are never implemented or advanced in the IETF standards process. They Proposed are never implemented or advanced in the IETF standards
therefore are often just proposed ideas that are presented to the process. They therefore are often just proposed ideas that are
Internet community. Sometimes flaws are exposed or they are one of many presented to the Internet community. Sometimes flaws are exposed or
competing solutions to problems. In these later cases, no discussion is they are one of many competing solutions to problems. In these later
presented as it would not serve the purpose of this discussion. cases, no discussion is 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 specification. 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 specification. 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 specification. 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 specification. 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 specification. There are no IPv4 dependencies in this specification.
5.006 RFC 1510 The Kerberos Network Authentication Service (V5) 5.006. RFC 1510 The Kerberos Network Authentication Service (V5)
Although this specification specifies optional use of host addresses, Although this specification specifies optional use of host
there are no specific requirements that the addresses be IPv4. The addresses, there are no specific requirements that the addresses
specification has no IPv4 dependencies, but implementations might be IPv4. The specification has no IPv4 dependencies, but
have issues. 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 specification. 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 specification. 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 specification. The operations There are no IPv4 dependencies in this specification. The
described operate on the entire IP packet without specifying that operations described operate on the entire IP packet without
the IP packet be IPv4 or IPv6. specifying that 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 specification. The operations There are no IPv4 dependencies in this specification. The
described operate on the entire IP packet without specifying that operations described operate on the entire IP packet without
the IP packet be IPv4 or IPv6. specifying that 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 specification. 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 specification. There are no IPv4 dependencies in this specification.
5.013 RFC 1928 SOCKS Protocol Version 5.013. RFC 1928 SOCKS Protocol Version
This specification is IPv6 aware and will function normally on either This specification is IPv6 aware and will function normally on
IPv4 and IPv6. either 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 specification. 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 specification. 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 specification. 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 specification. 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 specification. 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 specification. 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
specification. It is expected that a similar (or better) mechanism will specification. It is expected that a similar (or better)
be developed for RIPng. mechanism will 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 specification and has no This document defines an IP version independent specification and
IPv4 dependencies. has no 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 specification. 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 specification. 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 specification. 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 specification. 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 specification. 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 specification. 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 specification. 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 specification. 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
Option Signature Option
Although the specification enhancements have no IPv4 dependencies, it is Although the specification enhancements have no IPv4 dependencies,
an update to an IPv4 only routing specification. it is an update to an IPv4 only routing specification.
5.031 RFC 2401 Security Architecture for the Internet Protocol 5.031. RFC 2401 Security Architecture for the Internet Protocol
This specification 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 specification 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 specification. 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 specification. There are no IPv4 dependencies in this specification.
5.035 RFC 2405 The ESP DES-CBC Cipher Algorithm With Explicit IV 5.035. RFC 2405 The ESP DES-CBC Cipher Algorithm With Explicit IV
There are no IPv4 dependencies in this specification. 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 specification 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 specification 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 specification 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 specification. 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 specification. 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 specification. 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 specification. 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 specification. 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 specification. 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 specification. 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 specification. 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 specification. 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 specification. 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 specification. 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
address records. 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 specification. There are no IPv4 dependencies in this specification.
5.051 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
an ASN.1 specification as follows: with an ASN.1 specification as follows:
GeneralName ::= CHOICE { GeneralName ::= CHOICE {
otherName [0] INSTANCE OF OTHER-NAME, otherName [0] INSTANCE OF OTHER-NAME,
rfc822Name [1] IA5String, rfc822Name [1] IA5String,
dNSName [2] IA5String, dNSName [2] IA5String,
x400Address [3] EXPLICIT OR-ADDRESS.&Type, x400Address [3] EXPLICIT OR-ADDRESS.&Type,
directoryName [4] EXPLICIT Name, directoryName [4] EXPLICIT Name,
ediPartyName [5] EDIPartyName, ediPartyName [5] EDIPartyName,
uniformResourceIdentifier [6] IA5String, uniformResourceIdentifier [6] IA5String,
iPAddress [7] OCTET STRING, iPAddress [7] OCTET STRING,
registeredID [8] OBJECT IDENTIFIER registeredID [8] OBJECT IDENTIFIER
} }
uses a potential IPv4 only address. It goes on with the following uses a potential IPv4 only address. It goes on with the following
example: example:
Example 2: Assume that an X.509v3 certificate is issued to /CN=James Example 2: Assume that an X.509v3 certificate is issued to
Hacker/L=Basingstoke/O=Widget Inc/C=GB/ with Subject Alternate names /CN=James Hacker/L=Basingstoke/O=Widget Inc/C=GB/ with Subject
of (a) domain name widget.foo.example, (b) IPv4 address Alternate names of (a) domain name widget.foo.example,
10.251.13.201, and (c) string "James Hacker (b) IPv4 address 10.251.13.201, and (c) string "James Hacker
<hacker@mail.widget.foo.example>". Then the storage locations <hacker@mail.widget.foo.example>". Then the storage locations
recommended, in priority order, would be recommended, in priority order, would be
(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 -- so it seems this specification is IPv4 and IPv6 aware. aware -- so it seems this specification is IPv4 and IPv6 aware.
5.052 RFC 2539 Storage of Diffie-Hellman Keys in the Domain Name 5.052. RFC 2539 Storage of Diffie-Hellman Keys in the Domain
System (DNS) Name System (DNS)
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.053 RFC 2560 X.509 Internet Public Key Infrastructure Online 5.053. RFC 2560 X.509 Internet Public Key Infrastructure Online
Certificate Status Specification - OCSP Certificate Status Specification - OCSP
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.054 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 specification. There are no IPv4 dependencies in this specification.
5.055 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 specification. There are no IPv4 dependencies in this specification.
5.056 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 specification. There are no IPv4 dependencies in this specification.
5.057 RFC 2631 Diffie-Hellman Key Agreement Method 5.057. RFC 2631 Diffie-Hellman Key Agreement Method
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.058 RFC 2632 S/MIME Version 3 Certificate Handling 5.058. RFC 2632 S/MIME Version 3 Certificate Handling
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.059 RFC 2633 S/MIME Version 3 Message Specification 5.059. RFC 2633 S/MIME Version 3 Message Specification
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.060 RFC 2634 Enhanced Security Services for S/MIME 5.060. RFC 2634 Enhanced Security Services for S/MIME
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.061 RFC 2712 Addition of Kerberos Cipher Suites to Transport Layer 5.061. RFC 2712 Addition of Kerberos Cipher Suites to Transport
Security (TLS) Layer Security (TLS)
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.062 RFC 2743 Generic Security Service Application Program Interface 5.062. RFC 2743 Generic Security Service Application Program
Version 2 Update 1 Interface Version 2 Update 1
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.063 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 specification. There are no IPv4 dependencies in this specification.
5.064 RFC 2747 RSVP Cryptographic Authentication 5.064. RFC 2747 RSVP Cryptographic Authentication
This specification is both IPv4 and IPv6 aware and needs no changes. This specification is both IPv4 and IPv6 aware and needs no
changes.
5.065 RFC 2797 Certificate Management Messages over CMS 5.065. RFC 2797 Certificate Management Messages over CMS
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.066 RFC 2817 Upgrading to TLS Within HTTP/1.1 5.066. RFC 2817 Upgrading to TLS Within HTTP/1.1
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.067 RFC 2829 Authentication Methods for LDAP 5.067. RFC 2829 Authentication Methods for LDAP
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.068 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 specification. There are no IPv4 dependencies in this specification.
5.069 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 specification. There are no IPv4 dependencies in this specification.
5.070 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 specification. There are no IPv4 dependencies in this specification.
5.071 RFC 2847 LIPKEY - A Low Infrastructure Public Key Mechanism 5.071. RFC 2847 LIPKEY - A Low Infrastructure Public Key
Using SPKM Mechanism Using SPKM
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.072 RFC 2853 Generic Security Service API Version 2 : Java 5.072. RFC 2853 Generic Security Service API Version 2 :
Bindings Java 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 specification. dependencies in this specification.
5.073 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 specification. There are no IPv4 dependencies in this specification.
5.074 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 specification. There are no IPv4 dependencies in this specification.
5.075 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 specification. There are no IPv4 dependencies in this specification.
5.076 RFC 2931 DNS Request and Transaction Signatures 5.076. RFC 2931 DNS Request and Transaction
(SIG(0)s) Signatures (SIG(0)s)
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.077 RFC 2935 Internet Open Trading Protocol (IOTP) HTTP 5.077. RFC 2935 Internet Open Trading Protocol (IOTP)
Supplement HTTP Supplement
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.078 RFC 2941 Telnet Authentication Option 5.078. RFC 2941 Telnet Authentication Option
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.079 RFC 2942 Telnet Authentication: Kerberos Version 5 5.079. RFC 2942 Telnet Authentication: Kerberos Version 5
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.080 RFC 2943 TELNET Authentication Using DSA 5.080. RFC 2943 TELNET Authentication Using DSA
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.081 RFC 2944 Telnet Authentication: SRP 5.081. RFC 2944 Telnet Authentication: SRP
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.082 RFC 2945 The SRP Authentication and Key Exchange 5.082. RFC 2945 The SRP Authentication and Key
System Exchange System
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.083 RFC 2946 Telnet Data Encryption Option 5.083. RFC 2946 Telnet Data Encryption Option
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.084 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 specification. There are no IPv4 dependencies in this specification.
5.085 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 specification. There are no IPv4 dependencies in this specification.
5.086 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 specification. There are no IPv4 dependencies in this specification.
5.087 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 specification. There are no IPv4 dependencies in this specification.
5.088 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 specification. There are no IPv4 dependencies in this specification.
5.089 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 specification. There are no IPv4 dependencies in this specification.
5.090 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 specification. There are no IPv4 dependencies in this specification.
5.091 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.092 RFC 3039 Internet X.509 Public Key Infrastructure Qualified 5.092. RFC 3039 Internet X.509 Public Key Infrastructure
Certificates Profile Qualified Certificates Profile
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.093 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.094 RFC 3062 LDAP Password Modify Extended Operation 5.094. RFC 3062 LDAP Password Modify Extended Operation
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.095 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 specification. There are no IPv4 dependencies in this specification.
5.096 RFC 3097 RSVP Cryptographic Authentication -- Updated Message 5.096. RFC 3097 RSVP Cryptographic Authentication --
Type Value Updated Message Type Value
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.097 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
System (DNS) Name System (DNS)
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.098 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.099 RFC 3207 SMTP Service Extension for Secure SMTP over Transport 5.099. RFC 3207 SMTP Service Extension for Secure SMTP over
Layer Security Transport Layer Security
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.100 RFC 3275 (Extensible Markup Language) XML-Signature Syntax and 5.100. RFC 3275 (Extensible Markup Language) XML-Signature
Processing Syntax and Processing
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.101 RFC 3280 Internet X.509 Public Key Infrastructure Certificate and 5.101. RFC 3280 Internet X.509 Public Key Infrastructure
Certificate Revocation List (CRL) Profile Certificate and Certificate Revocation List (CRL) Profile
This specification is IPv4 and IPv6 aware. This specification is IPv4 and IPv6 aware.
5.102 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
implementation or usage on the Internet. They are often propriety in widescale implementation or usage on the Internet. They are often
nature or used in limited arenas. They are documented to the Internet propriety in nature or used in limited arenas. They are documented
community in order to allow potential interoperability or some other to the Internet community in order to allow potential
potential useful scenario. In a few cases they are presented as interoperability or some other potential useful scenario. In a few
alternatives to the mainstream solution to an acknowledged problem. cases they are presented as 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 specification. 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 specification. 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 specification. 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 specification. 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 specification. 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 specification assumes the use of IGMP and is therefore limited to This specification assumes the use of IGMP and is therefore
IPv4 multicast. It is assumed that a similar mechanism may be limited to IPv4 multicast. It is assumed that a similar mechanism
defined for IPv6 multicasting. may be 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 specification. 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 specification. 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
Trusted Entity. This certificate is included in the router PKLSA and a Trusted Entity. This certificate is included in the router
in the router configuration information. To change any of the values PKLSA and in the router configuration information. To change
in the certificate, a new certificate must be obtained from a TE. 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 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 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 | | Router Id |
+-+-+-+-+-+-+-+-*-+-+-+-+-+-+-+-*-+-+-+-+-+-+-+-*-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-*-+-+-+-+-+-+-+-*-+-+-+-+-+-+-+-*-+-+-+-+-+-+-+-+
| TE Id | TE Key Id | Rtr Key Id | Sig Alg | | TE Id | TE Key Id | Rtr Key Id | Sig Alg |
+-+-+-+-+-+-+-+-*-+-+-+-+-+-+-+-*-+-+-+-+-+-+-+-*-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-*-+-+-+-+-+-+-+-*-+-+-+-+-+-+-+-*-+-+-+-+-+-+-+-+
| Create Time | | Create Time |
+-+-+-+-+-+-+-+-*-+-+-+-+-+-+-+-*-+-+-+-+-+-+-+-*-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-*-+-+-+-+-+-+-+-*-+-+-+-+-+-+-+-*-+-+-+-+-+-+-+-+
skipping to change at line 964 skipping to change at page 21, line 36
| Address Mask | | Address Mask |
+-+-+-+-+-+-+-+-*-+-+-+-+-+-+-+-*-+-+-+-+-+-+-+-*-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-*-+-+-+-+-+-+-+-*-+-+-+-+-+-+-+-*-+-+-+-+-+-+-+-+
| IP Address/Address Mask for each Net Range ... / | IP Address/Address Mask for each Net Range ... /
| ... / | ... /
+-+-+-+-+-+-+-+-*-+-+-+-+-+-+-+-*-+-+-+-+-+-+-+-*-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-*-+-+-+-+-+-+-+-*-+-+-+-+-+-+-+-*-+-+-+-+-+-+-+-+
| Router Public Key | | Router Public Key |
+-+-+-+-+-+-+-+-*-+-+-+-+-+-+-+-*-+-+-+-+-+-+-+-*-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-*-+-+-+-+-+-+-+-*-+-+-+-+-+-+-+-*-+-+-+-+-+-+-+-+
| Certification / | Certification /
+-+-+-+-+-+-+-+-*-+-+-+-+-+-+-+-*-+-+-+-+-+-+-+-*-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-*-+-+-+-+-+-+-+-*-+-+-+-+-+-+-+-*-+-+-+-+-+-+-+-+
#NET RANGES The number of network ranges that follow. A network #NET RANGES The number of network ranges that follow. A
range is defined to be an IP Address and an Address network range is defined to be an IP Address
Mask. This list of ranges defines the addresses that and an Address Mask. This list of ranges
the Router is permitted to advertise in its Router defines the addresses that the Router is
Links LSA. Valid values are 0-255. If there are 0 permitted to advertise in its Router Links LSA.
ranges the router cannot advertise anything. This is Valid values are 0-255. If there are 0 ranges
not generally useful. One range with address=0 and the router cannot advertise anything. This is
mask=0 will allow a router to advertise any address. not generally useful. One range with address=0
and 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
Define a range of addresses that this router may router may advertise. Each is a 32 bit value.
advertise. Each is a 32 bit value. One range with One range with address=0 and mask=0 will allow
address=0 and mask=0 will allow a router to advertise 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 specification. 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 specification. 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 specification. 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 specification. 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 specification. 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 specification. 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 specification. 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 specification 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 specification. There are no IPv4 dependencies in this specification.
7.0 Summary of Results 7.0. Summary of Results
In the initial survey of RFCs 4 positives were identified out of a In the initial survey of RFCs 4 positives were identified out of a
total of 124, broken down as follows: total of 124, broken down as follows:
Standards 0 of 1 or 0.00% Standards: 0 out of 1 or 0.00%
Draft Standards 1 of 3 or 33.33% Draft Standards: 1 out of 3 or 33.33%
Proposed Standards 1 of 102 or 0.98% Proposed Standards: 1 out of 102 or 0.98%
Experimental RFCs 2 of 18 or 11.11% Experimental RFCs: 2 out 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 Mobile IPv4 Challenge Response Extension (RFC 3012) 7.3.2. Mobile IPv4 Challenge Response Extension (RFC 3012)
The problems are not being addressed and similar functions may The problems are not being addressed and similar functions may be
be needed in Mobile IPv6. needed in Mobile IPv6.
7.3.3 Authentication for DHCP Messages (RFC 3118) 7.3.3. Authentication for DHCP Messages (RFC 3118)
This problem has been fixed in RFC 3315, Dynamic Host Configuration This problem has been fixed in RFC 3315, Dynamic Host
Protocol for IPv6 (DHCPv6). Configuration 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 specification relies on IPv4 IGMP Multicast and a new specification This specification relies on IPv4 IGMP Multicast and a new
may be produced; however, the SMKD is not believed to be in use. specification may be produced; however, the SMKD is not believed
to be in use.
8.0 Security Consideration 7.4.2. OPSF with Digital Signatures (RFC 2154)
This memo examines the IPv6-readiness of specifications; this does not This specification is IPv4-only, and relies on an IPv4-only
have security considerations in itself. 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.
9.0 Acknowledgements 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 The authors would like to acknowledge the support of the Internet
Society in the research and production of this document. Society in the research and production of this document.
Additionally the author, Philip J. Nesser II, would like to thanks Additionally the author, Philip J. Nesser II, would like to thanks
his partner in all ways, Wendy M. Nesser. his partner in all ways, Wendy M. Nesser.
The editor, Andreas Bergstrom, would like to thank Pekka Savola The editor, Andreas Bergstrom, would like to thank Pekka Savola for
for guidance and collection of comments for the editing of this guidance and collection of comments for the editing of this document.
document.
10.0 References
10.1 Normative 10.0. Normative Reference
[1] Philip J. Nesser II, Andreas Bergstrom. "Introduction to the [1] Nesser, II, P. and A. Bergstrom, Editor, "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-05.txt IETF work in progress, RFC 3789, June 2004.
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
Phone: +1 425 481 4303 Phone: +1 425 481 4303
Fax: +1 425 48 Fax: +1 425 48
EMail: phil@nesser.com
Andreas Bergstrom (Editor) Andreas Bergstrom (Editor)
Ostfold University College Ostfold University College
Email: andreas.bergstrom@hiof.no Rute 503 Buer
Address: Rute 503 Buer
N-1766 Halden N-1766 Halden
Norway Norway
12.0 Intellectual Property Statement 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 The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights this document or the extent to which any license under such rights
might or might not be available; neither does it represent that it might or might not be available; nor does it represent that it has
has made any effort to identify any such rights. Information on the made any independent effort to identify any such rights. Information
IETF's procedures with respect to rights in standards-track and on the procedures with respect to rights in RFC documents can be
standards-related documentation can be found in BCP-11. Copies of found in BCP 78 and BCP 79.
claims of rights made available for publication and any assurances of
licenses to be made available, or the result of an attempt made to Copies of IPR disclosures made to the IETF Secretariat and any
obtain a general license or permission for the use of such assurances of licenses to be made available, or the result of an
proprietary rights by implementors or users of this specification can attempt made to obtain a general license or permission for the use of
be obtained from the IETF Secretariat. 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 The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights which may cover technology that may be required to practice rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF Executive this standard. Please address the information to the IETF at ietf-
Director. ipr@ietf.org.
13.0 Full Copyright Statement
Copyright (C) The Internet Society (2000). All Rights Reserved. Acknowledgement
This document and translations of it may be copied and furnished to Funding for the RFC Editor function is currently provided by the
others, and derivative works that comment on or otherwise explain it Internet Society.
or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this docu-
ment itself may not be modified in any way, such as by removing the
copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of develop-
ing Internet standards in which case the procedures for copyrights
defined in the Internet Standards process must be followed, or as
required to translate it into languages other than English. The lim-
ited permissions granted above are perpetual and will not be revoked
by the Internet Society or its successors or assigns. This document
and the information contained herein is provided on an "AS IS" basis
and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DIS-
CLAIMS 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.
 End of changes. 

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