Process Experiment: Document Shepherding Throughout a Document's Lifecycle
draft-leiba-extended-doc-shepherd-02
| Document | Type | Expired Internet-Draft (individual in gen area) | |
|---|---|---|---|
| Author | Barry Leiba | ||
| Last updated | 2014-01-11 (Latest revision 2013-07-10) | ||
| Stream | Internet Engineering Task Force (IETF) | ||
| Formats |
Expired & archived
plain text
xml
htmlized
pdfized
bibtex
|
||
| Reviews |
GENART Telechat review
(of
-06)
Not Ready
GENART Last Call review
Ready
|
||
| Stream | WG state | (None) | |
| Document shepherd | Allison Mankin | ||
| IESG | IESG state | Expired (IESG: Dead) | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | Benoît Claise | ||
| Send notices to | barryleiba@computer.org, allison.mankin@gmail.com |
https://www.ietf.org/archive/id/draft-leiba-extended-doc-shepherd-02.txt
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 in many situations to begin shepherding when there's a call for adoption as a working group document. This document extends RFC 4858, describing how that extended shepherding function might work and what tasks might be involved throughout the document's lifecycle, and suggesting how Working Group Chairs might choose to implement extended shepherding.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)