RFC 3789: Introduction to the Survey of IPv4 Addresses in Currently Deployed IETF Standards Track and Experimental Documents
In plain English — editorial summary, not part of the RFC
This document is a general overview and introduction to the v6ops IETF workgroup project of documenting all usage of IPv4 addresses in IETF standards track and experimental RFCs. It is broken into seven documents conforming to the current IETF areas. It also describes the methodology used during documentation, which types of RFCs have been documented, and provides a concatenated summary of results. This memo provides information for the Internet community.
Document record
- Document ID
- RFC3789
- Published
- June 2004
- Authors
- P. Nesser, II; A. Bergstrom
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- ops
- Pages
- 10
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3790Survey of IPv4 Addresses in Currently Deployed IETF Internet Area Standards Track and Experimental DocumentsCurrent
June 2004
- RFC 3791Survey of IPv4 Addresses in Currently Deployed IETF Routing Area Standards Track and Experimental DocumentsCurrent
June 2004
- RFC 3792Survey of IPv4 Addresses in Currently Deployed IETF Security Area Standards Track and Experimental DocumentsCurrent
June 2004
- RFC 3793Survey of IPv4 Addresses in Currently Deployed IETF Sub-IP Area Standards Track and Experimental DocumentsCurrent
June 2004
- RFC 3794Survey of IPv4 Addresses in Currently Deployed IETF Transport Area Standards Track and Experimental DocumentsCurrent
June 2004
- RFC 3795Survey of IPv4 Addresses in Currently Deployed IETF Application Area Standards Track and Experimental DocumentsCurrent
June 2004
- RFC 3796Survey of IPv4 Addresses in Currently Deployed IETF Operations & Management Area Standards Track and Experimental DocumentsCurrent
June 2004
- RFC 3763One-way Active Measurement Protocol (OWAMP) RequirementsCurrent
April 2004
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?