Handling and Adoption of Internet-Drafts by IETF Working Groups
draft-carpenter-gendispatch-rfc7221bis-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Adrian Farrel , Dave Crocker , Brian E. Carpenter , Fernando Gont , Michael Richardson | ||
| Last updated | 2021-05-02 (Latest revision 2020-10-29) | ||
| Replaces | draft-carpenter-gendispatch-draft-adoption | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
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.
Authors
Adrian Farrel
Dave Crocker
Brian E. Carpenter
Fernando Gont
Michael Richardson
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)