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
Nesser II & Bergstrom Informational [Page 1]
RFC 3793 IPv4 Addresses in the IETF Sub-IP Area May 2004
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).
2. Document Organization
The rest of the document sections are described below.
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.
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.
Nesser II & Bergstrom Informational [Page 2]
RFC 3793 IPv4 Addresses in the IETF Sub-IP Area May 2004 5. Proposed StandardsProposed 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 presented to the Internet community. Sometimes flaws are exposed or they are one of many competing solutions to problems. In these later cases, no discussion is presented as it would not serve the purpose of this discussion.
6. Experimental RFCs
Experimental RFCs typically define protocols that do not have widescale implementation or usage on the Internet. They are often propriety in nature or used in limited arenas. They are documented to the Internet community in order to allow potential interoperability or some other potential useful scenario. In a few cases they are presented as alternatives to the mainstream solution to an acknowledged problem. 6.01. RFC 3063 MPLS Loop Prevention Mechanism
Nesser II & Bergstrom Informational [Page 3]
RFC 3793 IPv4 Addresses in the IETF Sub-IP Area May 2004
There are no IPv4 dependencies in this specification.
7. Summary of Results
In the initial survey of RFCs 0 positives were identified out of a total of 7, broken down as follows:
8. Security Considerations
This memo examines the IPv6-readiness of specifications; this does not have security considerations in itself.
9. Acknowledgements
The authors would like to acknowledge the support of the Internet Society in the research and production of this document. Additionally the author, Philip J. Nesser II, would like to thank his partner in all ways, Wendy M. Nesser.
Nesser II & Bergstrom Informational [Page 4]
RFC 3793 IPv4 Addresses in the IETF Sub-IP Area May 2004
The editor, Andreas Bergstrom, would like to thank Pekka Savola for guidance and collection of comments for the editing of this document.
10. Normative Reference
[1] Nesser, II, P. and A. Bergstrom, Editor, "Introduction to the
11. Authors' Addresses
Please contact the authors with any questions, comments or suggestions at:
Nesser II & Bergstrom Informational [Page 5]
RFC 3793 IPv4 Addresses in the IETF Sub-IP Area May 2004 12. Full Copyright StatementCopyright (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.
