< draft-leiba-extended-doc-shepherd-00.txt   draft-leiba-extended-doc-shepherd-01.txt >
Network Working Group B. Leiba Network Working Group B. Leiba
Internet-Draft Huawei Technologies Internet-Draft Huawei Technologies
Intended status: Informational August 2, 2012 Intended status: Informational November 4, 2012
Expires: February 3, 2013 Expires: May 8, 2013
Document Shepherding Throughout a Document's Lifecycle Document Shepherding Throughout a Document's Lifecycle
draft-leiba-extended-doc-shepherd-00 draft-leiba-extended-doc-shepherd-01
Abstract Abstract
RFC 4858 talks about "Document Shepherding from Working Group Last RFC 4858 talks about "Document Shepherding from Working Group Last
Call to Publication". There's a significant part of a document's Call to Publication". There's a significant part of a document's
life that happens before working group last call, starting, really, life that happens before working group last call, starting, really,
at the time a working group begins discussing a version of the idea 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 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 helpful to begin shepherding when there's a call for adoption as a
working group document, and this document gives one Area Director's working group document, and this document gives one Area Director's
skipping to change at page 1, line 38 skipping to change at page 1, line 38
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on February 3, 2013. This Internet-Draft will expire on May 8, 2013.
Copyright Notice Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the Copyright (c) 2012 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Notational Conventions . . . . . . . . . . . . . . . . . . . 3 1.1. Notational Conventions . . . . . . . . . . . . . . . . . . . 4
2. The Document Shepherd as a "Function" . . . . . . . . . . . 5 2. The Document Shepherd as a "Function" . . . . . . . . . . . 5
3. Stages in a Document's Lifecycle . . . . . . . . . . . . . . 6 3. Stages in a Document's Lifecycle . . . . . . . . . . . . . . 6
3.1. Stage: Call for Adoption . . . . . . . . . . . . . . . . . . 6 3.1. Stage: Call for Adoption . . . . . . . . . . . . . . . . . . 6
3.2. Stage: Working Group Document . . . . . . . . . . . . . . . 8 3.2. Stage: Working Group Document . . . . . . . . . . . . . . . 8
3.3. Stage: Working Group Last Call . . . . . . . . . . . . . . . 10 3.3. Stage: Working Group Last Call . . . . . . . . . . . . . . . 10
3.4. Stage: Shepherd Writeup Underway . . . . . . . . . . . . . . 11 3.4. Stage: Shepherd Writeup Underway . . . . . . . . . . . . . . 11
3.5. Stage: AD Review . . . . . . . . . . . . . . . . . . . . . . 13 3.5. Stage: AD Review . . . . . . . . . . . . . . . . . . . . . . 13
3.6. Stage: IETF Last Call . . . . . . . . . . . . . . . . . . . 14 3.6. Stage: IETF Last Call . . . . . . . . . . . . . . . . . . . 14
skipping to change at page 3, line 49 skipping to change at page 3, line 49
tasks earlier in a document's life, and possibly delegating Document tasks earlier in a document's life, and possibly delegating Document
Shepherd tasks to a Shepherd who is neither a Chair nor the Working Shepherd tasks to a Shepherd who is neither a Chair nor the Working
Group Secretary (consistent with the IESG Statement on Document Group Secretary (consistent with the IESG Statement on Document
Shepherds [Stmt]). Shepherds [Stmt]).
By providing summaries in each section of the tasks expected at that By providing summaries in each section of the tasks expected at that
stage in the document's lifecycle, I hope to make this an easy stage in the document's lifecycle, I hope to make this an easy
reference and checklist for Working Group Chairs and Document reference and checklist for Working Group Chairs and Document
Shepherds. Shepherds.
I also want to stress that the specific mechanism suggested here will
not be suitable for all working groups, all management models, and
all situations. While I think that it's still a good idea to have
the stages laid out and the tasks at each stage identified, not all
working groups will benefit from having a single document shepherd
designated at the start. Indeed, when a document is legitimately
years in the making, personnel may come and go and changes will be
necessary. A particular working group might be working only on one
document at a time, with all tasks shared between the chairs.
For these and other reasons, the suggestions herein are meant to be
adapted to specific situations to retain the underlying objective of
maintaining progress through active involvement.
1.1. Notational Conventions 1.1. Notational Conventions
Because this document is specifically one individual's thoughts on Because this document is specifically one individual's thoughts on
this matter, it's worth pointing out that the document makes no this matter, it's worth pointing out that the document makes no
process changes and there is no normative language here. process changes and there is no normative language here.
I use Initial Capitals in some terms, such as "Document Shepherd", to I use Initial Capitals in some terms, such as "Document Shepherd", to
indicate that those terms represent formal roles in the management indicate that those terms represent formal roles in the management
model I'm describing. model I'm describing.
skipping to change at page 21, line 10 skipping to change at page 22, line 5
here is anything different to what should be happening already. here is anything different to what should be happening already.
Setting it out as clear tasks and a set of stages in the document's Setting it out as clear tasks and a set of stages in the document's
lifecycle will make it easier to recognize what needs to be done lifecycle will make it easier to recognize what needs to be done
when, and to handle delegation when the Chairs choose to delegate. when, and to handle delegation when the Chairs choose to delegate.
5. Security Considerations 5. Security Considerations
This document describes an individual's suggestion about IETF This document describes an individual's suggestion about IETF
process, and is entirely unrelated to security in any way. process, and is entirely unrelated to security in any way.
[The RFC Editor is asked to remove either this section or this
paragraph, depending upon publication policy.]
6. IANA Considerations 6. IANA Considerations
No IANA actions are requested by this document, and the RFC Editor is No IANA actions are requested by this document, and the RFC Editor is
asked to remove this section before publication. asked to remove this section before publication.
7. References 7. References
7.1. Normative References 7.1. Normative References
[RFC2418] Bradner, S., "IETF Working Group Guidelines and [RFC2418] Bradner, S., "IETF Working Group Guidelines and
 End of changes. 6 change blocks. 
8 lines changed or deleted 19 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/