RFC 6359: Datatracker Extensions to Include IANA and RFC Editor Processing Information
In plain English — editorial summary, not part of the RFC
This document captures the requirements for integrating IANA and RFC Editor state information into the Datatracker to provide the community with a unified tool to track the status of their document as it progresses from Internet-Draft (I-D) version -00 to RFC. Extending the Datatracker to hold document data from I-D version -00 to RFC allows for increased automation between the Datatracker, IANA, and RFC Editor, thus reducing manual labor, processing errors, and potential delay. Therefore, this document also describes the requirements to make such automation possible. This document is not an Internet Standards Track specification; it is published for informational purposes.
Document record
- Document ID
- RFC6359
- Published
- September 2011
- Authors
- S. Ginoza; M. Cotton; A. Morris
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- gen
- Pages
- 18
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6293Requirements for Internet-Draft Tracking by the IETF Community in the DatatrackerCurrent
June 2011
- RFC 6292Requirements for a Working Group Charter ToolUpdated
June 2011
- RFC 6433Requirements for a Working Group Milestones ToolCurrent
November 2011
- RFC 5378Rights Contributors Provide to the IETF TrustCurrent
November 2008
- RFC 5377Advice to the Trustees of the IETF Trust on Rights to Be Granted in IETF DocumentsObsoleted
November 2008
- RFC 4879Clarification of the Third Party Disclosure Procedure in RFC 3979Obsoleted
April 2007
- RFC 4748RFC 3978 Update to Recognize the IETF TrustObsoleted
October 2006
- RFC 7979Response to the IANA Stewardship Transition Coordination Group (ICG) Request for Proposals on the IANA Protocol Parameters RegistriesCurrent
August 2016
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?