Document Shepherding Throughout a Document's Lifecycle
draft-leiba-extended-doc-shepherd-01
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
|---|---|---|---|
| Author | Barry Leiba | ||
| Last updated | 2013-05-10 (Latest revision 2012-11-06) | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Formats | |||
| Reviews | |||
| Stream | WG state | (None) | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired (IESG: Dead) | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | Russ Housley | ||
| Send notices to | barryleiba@computer.org, "Murray S. Kucherawy" <superuser@gmail.com> |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
RFC 4858 talks about "Document Shepherding from Working Group Last Call to Publication". There's a significant part of a document's life that happens before working group last call, starting, really, at the time a working group begins discussing a version of the idea that's been posted as an individual draft. It seems reasonable and helpful to begin shepherding when there's a call for adoption as a working group document, and this document gives one Area Director's view of how that extended shepherding function might work, and what tasks might be involved throughout the document's lifecycle.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)