-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Good questions all.
IMHO, Independent Stream at most. Or a simple blog post would do. :)
On 9/25/12 1:13 PM, Adrian Farrel wrote:
Hi, I don't understand the process for this document.
I read Russ's words, but I don't glean the meaning :-(
This document is in IETF last call for publication in the IETF
stream. Yet any comments received will not necessarily be taken on
board and the document will not be published as having IETF
consensus. Why does that feel like Independent Stream to me? And
why is an RFC needed simply to record the thoughts of one person?
Is the purpose of the Last Call simply to help the IESG make its
decision?
Thanks, Adrian (Who has yet to read the document, but feels that he
cannot make any useful comments since the content is the opinion of
one person and he has no idea whether the document correctly
reflects the opinion of that person.)
-----Original Message----- From: ietf-announce-bounces(_at_)ietf(_dot_)org
[mailto:ietf-announce- bounces(_at_)ietf(_dot_)org] On Behalf Of The IESG
Sent: 25 September 2012 15:41 To: IETF-Announce Subject: Last
Call: <draft-leiba-extended-doc-shepherd-00.txt> (Document
Shepherding Throughout a Document's Lifecycle) to Informational
RFC
The IESG has received a request from an individual submitter to
consider the following document: - 'Document Shepherding
Throughout a Document's Lifecycle'
<draft-leiba-extended-doc-shepherd-00.txt> as Informational RFC
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.
The IESG plans to make a decision in the next few weeks, and
solicits final comments on this action. Please send substantive
comments to the ietf(_at_)ietf(_dot_)org mailing lists by 2012-10-23.
Exceptionally, comments may be sent to iesg(_at_)ietf(_dot_)org instead. In
either case, please retain the beginning of the Subject line to
allow automated sorting.
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.
The file can be obtained via
http://datatracker.ietf.org/doc/draft-leiba-extended-doc-shepherd/
IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-leiba-extended-doc-shepherd/ballot/
No IPR declarations have been submitted directly on this I-D.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.18 (Darwin)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/
iEYEARECAAYFAlBiFA8ACgkQNL8k5A2w/vwtegCfZ76DaVQwi7r0UsLPUI2ftPBj
69EAnijKdGdaQ3a5b47uwApIx5DEgMxf
=fxRK
-----END PGP SIGNATURE-----