RFC 7221: Handling of Internet-Drafts by IETF Working Groups
In plain English — editorial summary, not part of the RFC
The productive output of an IETF working group is documents, as mandated by the working group's charter. When a working group is ready to develop a particular document, the most common mechanism is for it to "adopt" an existing document as a starting point. The document that a working group adopts and then develops further is based on initial input at varying levels of maturity. An initial working group draft might be a document already in wide use, or it might be a blank sheet, wholly created by the working group, or it might represent any level of maturity in between. This document discusses how a working group typically handles the formal documents that it targets for publication.
Document record
- Document ID
- RFC7221
- Published
- April 2014
- Authors
- A. Farrel; D. Crocker
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- —
- Pages
- 14
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3844IETF Problem Resolution ProcessCurrent
August 2004
- RFC 3774IETF Problem StatementCurrent
May 2004
- RFC 7749The "xml2rfc" Version 2 VocabularyObsoleted
February 2016
- RFC 7282On Consensus and Humming in the IETFCurrent
June 2014
- RFC 8088How to Write an RTP Payload FormatUpdated
May 2017
- RFC 8789IETF Stream Documents Require IETF Rough ConsensusCurrent
June 2020
- RFC 8874Working Group GitHub Usage GuidanceCurrent
August 2020
- RFC 5434Considerations for Having a Successful Birds-of-a-Feather (BOF) SessionCurrent
February 2009
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?