Process Experiment: Document Shepherding Throughout a Document's Lifecycle
draft-leiba-extended-doc-shepherd-03
Document | Type |
Expired Internet-Draft
(individual in gen area)
Expired & archived
|
|
---|---|---|---|
Author | Barry Leiba | ||
Last updated | 2015-10-14 (Latest revision 2014-05-16) | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Intended RFC status | Informational | ||
Formats | |||
Reviews | |||
Stream | WG state | (None) | |
Document shepherd | Murray Kucherawy | ||
Shepherd write-up | Show Last changed 2014-10-22 | ||
IESG | IESG state | Expired (IESG: Dead) | |
Action Holders |
(None)
|
||
Consensus boilerplate | Unknown | ||
Telechat date | (None) | ||
Responsible AD | Benoît Claise | ||
Send notices to | allison.mankin@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 at the time that a working group begins discussing a version of the idea that's been posted as an individual draft. This document extends RFC 4858, discussing the potential for extending shepherding and what tasks might be involved throughout a working group document's lifecycle, from start to finish.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)