RFC 4714: Requirements for IETF Technical Publication Service
In plain English — editorial summary, not part of the RFC
The work of the IETF is to discuss, develop, and disseminate technical specifications to support the Internet's operation. Technical publication is the process by which that output is disseminated to the community at large. As such, it is important to understand the requirements on the publication process. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4714
- Published
- October 2006
- Authors
- A. Mankin; S. Hayes
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- —
- Pages
- 24
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3797Publicly Verifiable Nominations Committee (NomCom) Random SelectionCurrent
June 2004
- RFC 4691Guidelines for Acting as an IETF Liaison to Another OrganizationCurrent
October 2006
- RFC 4089IAB and IESG Recommendation for IETF Administrative RestructuringCurrent
May 2005
- RFC 3975OMA-IETF Standardization CollaborationCurrent
February 2005
- RFC 3677IETF ISOC Board of Trustee Appointment ProceduresCurrent
December 2003
- RFC 3536Terminology Used in Internationalization in the IETFObsoleted
May 2003
- RFC 3305Report from the Joint W3C/IETF URI Planning Interest Group: Uniform Resource Identifiers (URIs), URLs, and Uniform Resource Names (URNs): Clarifications and RecommendationsCurrent
August 2002
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?