Survey of IPv4 Addresses in Currently Deployed IETF Application Area Standards Track and Experimental Documents
RFC 3795
|
| Document |
Type |
|
RFC - Informational
(June 2004; No errata)
|
|
Last updated |
|
2013-03-02
|
|
Stream |
|
IETF
|
|
Formats |
|
plain text
pdf
html
bibtex
|
| Stream |
WG state
|
|
(None)
|
|
Document shepherd |
|
No shepherd assigned
|
| IESG |
IESG state |
|
RFC 3795 (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 R. Sofia
Request for Comments: 3795 P. Nesser, II
Category: Informational Nesser & Nesser Consulting
June 2004
Survey of IPv4 Addresses in Currently Deployed
IETF Application 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 describes IPv4 addressing dependencies in an attempt to
clarify the necessary steps in re-designing and re-implementing
specifications to become network address independent, or at least, to
dually support IPv4 and IPv6. This transition requires several
interim steps, one of them being the evolution of current IPv4
dependent specifications to a format independent of the type of IP
addressing schema used. Hence, it is hoped that specifications will
be re-designed and re-implemented to become network address
independent, or at least to dually support IPv4 and IPv6.
To achieve that step, it is necessary to survey and document all IPv4
dependencies experienced by current standards (Full, Draft, and
Proposed) as well as Experimental RFCs. Hence, this document
describes IPv4 addressing dependencies that deployed IETF Application
Area documented Standards may experience.
Sofia & Nesser II Informational [Page 1]
RFC 3895 IPv4 Addresses in the IETF Application Area June 2004
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Document Organization. . . . . . . . . . . . . . . . . . . . . 2
3. Full Standards . . . . . . . . . . . . . . . . . . . . . . . . 3
4. Draft Standards. . . . . . . . . . . . . . . . . . . . . . . . 5
5. Proposed Standards . . . . . . . . . . . . . . . . . . . . . . 10
6. Experimental RFCs. . . . . . . . . . . . . . . . . . . . . . . 34
7. Summary of Results . . . . . . . . . . . . . . . . . . . . . . 45
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 47
9. Security Considerations. . . . . . . . . . . . . . . . . . . . 48
10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 48
10.1. Normative References. . . . . . . . . . . . . . . . . . 48
10.2. Informative References. . . . . . . . . . . . . . . . . 48
11. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 49
12. Full Copyright Statement . . . . . . . . . . . . . . . . . . . 50
1. Introduction
The exhaustive documentation of IPv4 addresses usage in currently
deployed IETF documented standards has now been broken into seven
documents conforming to current IETF main areas, i.e., Applications,
Internet, Operations and Management, Routing, Sub-IP, and Transport.
A general overview of the documentation, as well as followed
methodology and historical perspective can be found in [1]. This
document represents one of the seven blocks, and its scope is limited
to surveying possible IPv4 dependencies in IETF Application Area
documented Standards.
2. Document Organization
The remainder sections are organized as follows. Sections 3, 4, 5,
and 6 describe, respectively, the raw analysis of Internet Standards
[2]:
Full, Draft, and Proposed Standards, and Experimental RFCs. For each
section, standards are analysed by their RFC number, in sequential
order, i.e., from RFC 1 to RFC 3200. Exceptions to this are some
RFCs above RFC 3200. They have been included, given that they
obsoleted RFCs within the range 1-3200. Also, the comments presented
for each RFC are raw in their nature, i.e., each RFC is simply
analysed in terms of possible IPv4 addressing dependencies. Finally,
Section 7 presents a global overview of the data described in the
previous sections, and suggests possible future steps.
Sofia & Nesser II Informational [Page 2]
RFC 3895 IPv4 Addresses in the IETF Application Area June 2004
3. Full Standards
Internet Full Standards have attained the highest level of maturity
on the standards track process. They are commonly referred to as
"Standards", and represent fully technical mature specifications that
are widely implemented and used throughout the Internet.
3.1. RFC854: Telnet Protocol Specifications
Show full document text