RFC 6433: Requirements for a Working Group Milestones Tool
In plain English — editorial summary, not part of the RFC
The IETF intends to provide a new tool to Working Group chairs and Area Directors for the creation and updating of milestones for Working Group charters. This document describes the requirements for the proposed new tool, and it is intended as input to a later activity for the design and development of such a tool. This document updates RFC 6292. This document is not an Internet Standards Track specification; it is published for informational purposes.
Document record
- Document ID
- RFC6433
- Published
- November 2011
- Authors
- P. Hoffman
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- gen
- Pages
- 7
- Also known as
- —
- Updates:
- RFC 6292
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6359Datatracker Extensions to Include IANA and RFC Editor Processing InformationCurrent
September 2011
- RFC 6293Requirements for Internet-Draft Tracking by the IETF Community in the DatatrackerCurrent
June 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 7979Response to the IANA Stewardship Transition Coordination Group (ICG) Request for Proposals on the IANA Protocol Parameters RegistriesCurrent
August 2016
- 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 4450Getting Rid of the Cruft: Report from an Experiment in Identifying and Reclassifying Obsolete Standards DocumentsCurrent
March 2006
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?