Survey of IPv4 Addresses in Currently Deployed IETF Sub-IP Area Standards Track and Experimental Documents
RFC 3793
|
Document |
Type |
|
RFC - Informational
(June 2004; No errata)
|
|
Authors |
|
Philip Nesser
,
Andreas Bergstrom
|
|
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 3793 (Informational)
|
|
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: 3793 Nesser & Nesser Consulting
Category: Informational A. Bergstrom, Ed.
Ostfold University College
May 2004
Survey of IPv4 Addresses in Currently Deployed
IETF Sub-IP 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). All Rights Reserved.
Abstract
This document seeks to document all usage of IPv4 addresses in
currently deployed IETF Sub-IP 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. . . . . . . . . . . . . . . . . . . . . . . 3
6. Experimental RFCs . . . . . . . . . . . . . . . . . . . . . . . 3
7. Summary of Results. . . . . . . . . . . . . . . . . . . . . . . 4
7.01. Standards . . . . . . . . . . . . . . . . . . . . . . . . 4
7.02. Draft Standards . . . . . . . . . . . . . . . . . . . . . 4
7.03. Proposed Standards. . . . . . . . . . . . . . . . . . . . 4
7.04. Experimental RFCs . . . . . . . . . . . . . . . . . . . . 4
8. Security Considerations . . . . . . . . . . . . . . . . . . . . 4
9. Acknowledgements. . . . . . . . . . . . . . . . . . . . . . . . 4
Nesser II & Bergstrom Informational [Page 1]
RFC 3793 IPv4 Addresses in the IETF Sub-IP Area May 2004
10. Normative Reference . . . . . . . . . . . . . . . . . . . . . . 5
11. Authors' Addresses. . . . . . . . . . . . . . . . . . . . . . . 5
12. Full Copyright Statement. . . . . . . . . . . . . . . . . . . . 6
1. 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 & Management, Routing, Security, Sub-IP and Transport).
For a full introduction, please see the introduction [1].
2. Document Organization
The rest of the document sections are described below.
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. 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.
There are no full standards within the scope of this document.
4. 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.
There are no draft standards within the scope of this document.
Nesser II & Bergstrom Informational [Page 2]
RFC 3793 IPv4 Addresses in the IETF Sub-IP Area May 2004
5. Proposed Standards
Proposed Standards are introductory level documents. There are no
requirements for even a single implementation. In many cases
Proposed are never implemented or advanced in the IETF standards
process. They therefore are often just proposed ideas that are
Show full document text