RFC 2648: A URN Namespace for IETF Documents
In plain English — editorial summary, not part of the RFC
This document proposes the "ietf" namespace, which consists of the RFC family of documents (RFCs, STDs, FYIs, and BCPs) developed by the IETF and published by the RFC Editor and the minutes of working groups (WG) and birds of a feather (BOF) meetings that occur during IETF conferences. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2648
- Published
- August 1999
- Authors
- R. Moats
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- app
- Pages
- 30
- Also known as
- —
Topics
Referenced by
2 later RFCs formally update or obsolete part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2438Advancement of MIB specifications on the IETF Standards TrackCurrent
October 1998
- RFC 3005IETF Discussion List CharterObsoleted
November 2000
- RFC 3160The Tao of IETF - A Novice's Guide to the Internet Engineering Task ForceObsoleted
August 2001
- RFC 3184IETF Guidelines for ConductObsoleted
October 2001
- RFC 2031IETF-ISOC relationshipObsoleted
October 1996
- RFC 2028The Organizations Involved in the IETF Standards ProcessObsoleted
October 1996
- RFC 2611URN Namespace Definition MechanismsObsoleted
June 1999
- RFC 2436Collaboration between ISOC/IETF and ITU-TObsoleted
October 1998
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?