Survey of IPv4 Addresses in Currently Deployed IETF Security Area Standards Track and Experimental Documents
RFC 3792
Document | Type | RFC - Informational (June 2004; No errata) | |
---|---|---|---|
Authors | Andreas Bergstrom , Philip Nesser | ||
Last updated | 2013-03-02 | ||
Stream | IETF | ||
Formats | plain text html pdf htmlized bibtex | ||
Stream | WG state | (None) | |
Document shepherd | No shepherd assigned | ||
IESG | IESG state | RFC 3792 (Informational) | |
Action Holders |
(None)
|
||
Consensus Boilerplate | Unknown | ||
Telechat date | |||
Responsible AD | Bert Wijnen | ||
Send notices to | <pekkas@netcore.fi>, <Jonne.Soininen@nokia.com>,<bob@thefinks.com> |
Network Working Group P. Nesser, II Request for Comments: 3792 Nesser & Nesser Consulting Category: Informational A. Bergstrom, Ed. Ostfold University College June 2004 Survey of IPv4 Addresses in Currently Deployed IETF Security Area Standards Track and Experimental Documents Status of this Memo This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. Copyright Notice Copyright (C) The Internet Society (2004). Abstract This document seeks to document all usage of IPv4 addresses in currently deployed IETF Security Area documented standards. In order 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 evolution of current protocols that have IPv4 dependencies. It is hoped that these protocols (and their implementations) will be redesigned to be network address independent, but failing that will at least dually support IPv4 and IPv6. To this end, all Standards (Full, Draft, and Proposed) as well as Experimental RFCs will be surveyed and any dependencies will be documented. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2 2. Document Organisation. . . . . . . . . . . . . . . . . . . . . 2 3. Full Standards . . . . . . . . . . . . . . . . . . . . . . . . 2 4. Draft Standards. . . . . . . . . . . . . . . . . . . . . . . . 2 5. Proposed Standards . . . . . . . . . . . . . . . . . . . . . . 8 6. Experimental RFCs. . . . . . . . . . . . . . . . . . . . . . . 20 7. Summary of Results . . . . . . . . . . . . . . . . . . . . . . 22 7.1. Standards. . . . . . . . . . . . . . . . . . . . . . . . 23 7.2. Draft Standards. . . . . . . . . . . . . . . . . . . . . 23 7.3. Proposed Standards . . . . . . . . . . . . . . . . . . . 23 7.4. Experimental RFCs. . . . . . . . . . . . . . . . . . . . 23 8. Security Considerations. . . . . . . . . . . . . . . . . . . . 24 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 24 Nesser II & Bergstrom Informational [Page 1] RFC 3792 IPv4 Addresses in the IETF Security Area June 2004 10. Normative Reference. . . . . . . . . . . . . . . . . . . . . . 24 11. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 24 12. Full Copyright Statement . . . . . . . . . . . . . . . . . . . 25 1.0. Introduction 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 in a manageable form, it has been broken into 7 documents conforming to the current IETF areas (Application, Internet, Operations and Management, Routing, Security, Sub-IP, and Transport). For a full introduction, please see the introduction [1]. 2.0. Document Organization Sections 3, 4, 5, and 6 each describe the raw analysis of Full, Draft, and Proposed Standards, and Experimental RFCs. Each RFC is discussed in its turn starting with RFC 1 and ending with (around) RFC 3100. The comments for each RFC are "raw" in nature. That is, each RFC is discussed in a vacuum and problems or issues discussed do 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 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. 3.0. Full Standards Full Internet Standards (most commonly simply referred to as "Standards") are fully mature protocol specification that are widely implemented and used throughout the Internet. 3.1. RFC 2289 A One-Time Password System There are no IPv4 dependencies in this specification. 4.0. Draft Standards Draft Standards represent the penultimate standard level in the IETF. A protocol can only achieve draft standard when there are multiple, independent, interoperable implementations. Draft Standards are usually quite mature and widely used. Nesser II & Bergstrom Informational [Page 2] RFC 3792 IPv4 Addresses in the IETF Security Area June 2004 4.1. RFC 1864 The Content-MD5 Header Field There are no IPv4 dependencies in this specification. 4.2. RFC 2617 HTTP Authentication: Basic and Digest Access Authentication Section 3.2.1 The WWW-Authenticate Response Header include he following text: (Note: including the IP address of the client in the nonce would appear to offer the server the ability to limit the reuseShow full document text