Skip to main content

Process Experiment: Document Shepherding Throughout a Document's Lifecycle
draft-leiba-extended-doc-shepherd-03

Approval announcement
Draft of message to be sent after approval:

Announcement

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: RFC Editor <rfc-editor@rfc-editor.org>
Subject: Document Action: 'Document Shepherding Throughout a Document's Lifecycle' to Informational RFC (draft-leiba-extended-doc-shepherd-00.txt)

The IESG has approved the following document:
- 'Document Shepherding Throughout a Document's Lifecycle'
  (draft-leiba-extended-doc-shepherd-00.txt) as Informational RFC

This document has been reviewed in the IETF but is not the product of an
IETF Working Group.

The IESG contact person is Russ Housley.

A URL of this Internet Draft is:
http://datatracker.ietf.org/doc/draft-leiba-extended-doc-shepherd/


Ballot Text

Technical Summary

  This document is the author's opinion of how the document shepherding
  function described in RFC 4858 can be extended through the full life
  of a document, providing a single person (a working group chair or
  someone who works under the delegation and supervision of a chair) who
  is responsible for keeping discussion and development of the document
  moving, and avoiding deadlocks and stalling.  This document proposes
  no formal change and, as one person's opinion, is presented as an
  Informational document.

Working Group Summary

  This document is not the product of any IETF WG.

Document Quality

  The author posted a note about this document to the IETF discussion
  list, and he asked for comments.  No comments were posted to the list,
  but there was one private comment suggesting that the name of the
  function be changed from "document shepherd", to avoid confusion with
  the function presented in RFC 4858, which has been formally adopted.
  The author disagrees with this change; he explicitly wants to view
  this as a broadening of the document shepherd function.  The author's
  use of the same name is quite intentional.

Personnel

  Russ Housley is the responsible AD.

  Murray S. Kucherawy is the document shepherd.

Note to Reviewers

  The author is documenting his own opinion, and he is presenting that
  opinion to the community for consideration.  The author is not
  proposing any formal change, but he is interested in community
  comments.  Since this is the authors opinions, changes to the document
  based on received comments be at the author's discretion.  As a
  result, the finished document will not claim to reflect IETF community
  consensus.

RFC Editor Note