RFC 2551: The Roman Standards Process -- Revision III
In plain English — editorial summary, not part of the RFC
This memo documents the process used by the Roman community for the standardization of protocols and procedures. It defines the stages in the standardization process, the requirements for moving a document between stages and the types of documents used during this process. It also addresses the intellectual property rights and copyright issues associated with the standards process.
Document record
- Document ID
- RFC2551
- Published
- April 1999
- Authors
- S. Bradner
- Status
- INFORMATIONAL
- Stream
- INDEPENDENT
- Area
- —
- Pages
- 37
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2550Y10K and BeyondCurrent
April 1999
- RFC 2549IP over Avian Carriers with Quality of ServiceCurrent
April 1999
- RFC 1149Standard for the transmission of IP datagrams on avian carriersUpdated
April 1990
- RFC 2100The Naming of HostsCurrent
April 1997
- RFC 2450Proposed TLA and NLA Assignment RuleCurrent
December 1998
- RFC 2418IETF Working Group Guidelines and ProceduresUpdated
September 1998
- RFC 2357IETF Criteria for Evaluating Reliable Multicast Transport and Application ProtocolsCurrent
June 1998
- RFC 2768Network Policy and Services: A Report of a Workshop on MiddlewareCurrent
February 2000
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?