Re: [proto-team] Re: small issues with draft-ietf-proto-wgchair-doc-shepherding-07
Henrik Levkowetz <henrik@levkowetz.com> Wed, 28 June 2006 17:55 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
by megatron.ietf.org with esmtp (Exim 4.43)
id 1FveGV-0005zi-Eg; Wed, 28 Jun 2006 13:55:51 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
by megatron.ietf.org with esmtp (Exim 4.43) id 1FveGU-0005zd-4s
for proto-team@ietf.org; Wed, 28 Jun 2006 13:55:50 -0400
Received: from av10-1-sn2.hy.skanova.net ([81.228.8.181])
by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FveGR-00027W-M6
for proto-team@ietf.org; Wed, 28 Jun 2006 13:55:50 -0400
Received: by av10-1-sn2.hy.skanova.net (Postfix, from userid 502)
id CA37D38421; Wed, 28 Jun 2006 19:55:46 +0200 (CEST)
Received: from smtp4-2-sn2.hy.skanova.net (smtp4-2-sn2.hy.skanova.net
[81.228.8.93]) by av10-1-sn2.hy.skanova.net (Postfix) with ESMTP
id B89D038032; Wed, 28 Jun 2006 19:55:46 +0200 (CEST)
Received: from shiraz.levkowetz.com (81-232-110-214-no16.tbcn.telia.com
[81.232.110.214])
by smtp4-2-sn2.hy.skanova.net (Postfix) with ESMTP id 7E0D837E44;
Wed, 28 Jun 2006 19:55:46 +0200 (CEST)
Received: from localhost ([127.0.0.1])
by shiraz.levkowetz.com with esmtp (Exim 4.62)
(envelope-from <henrik@levkowetz.com>)
id 1FveGP-0004Zp-Rz; Wed, 28 Jun 2006 19:55:45 +0200
Message-ID: <44A2C2A1.5090307@levkowetz.com>
Date: Wed, 28 Jun 2006 19:55:45 +0200
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Thunderbird 1.5.0.4 (Macintosh/20060530)
MIME-Version: 1.0
To: Lars Eggert <lars.eggert@netlab.nec.de>
Subject: Re: [proto-team] Re: small issues
with draft-ietf-proto-wgchair-doc-shepherding-07
References: <35758337-E41C-4EFE-AABA-A10F499198BC@netlab.nec.de>
<3EC69FA4-7F5E-49C7-AB64-DC25C99A60FE@netlab.nec.de>
In-Reply-To: <3EC69FA4-7F5E-49C7-AB64-DC25C99A60FE@netlab.nec.de>
X-Enigmail-Version: 0.94.0.0
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Scanned: No (on shiraz.levkowetz.com);
SAEximRunCond expanded to false
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 0fa76816851382eb71b0a882ccdc29ac
Cc: proto-team@ietf.org
X-BeenThere: proto-team@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Process and Tools Team <proto-team.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/proto-team>,
<mailto:proto-team-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:proto-team@ietf.org>
List-Help: <mailto:proto-team-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/proto-team>,
<mailto:proto-team-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0501036055=="
Errors-To: proto-team-bounces@ietf.org
Hi Lars, on 2006-06-28 18:23 Lars Eggert said the following: > Hi, > > I just realized that there is another inconsistency in -07: The title > is "Document Shepherding from Working Group Last Call to IESG > Approval", but we have some text in there that says: > > A Document Shepherd's responsibilities include: [...] > > o Following up on IANA and RFC Editor requests in the post-approval > shepherding of the document. > > and further down: > > Consequently, the document shepherding process includes follow-up > work during all document-processing stages after Working Group Last > Call, i.e., during AD Evaluation of a document, during IESG > evaluation, and during post-approval processing by IANA and the RFC > Editor. > > Since the rest of the text doesn't talk about how to deal with the > IANA and the RFC Editor, I propose to remove the bullet and change > the other paragraph to: > > Consequently, the document shepherding process includes follow-up > work during all document-processing stages after Working Group Last > Call until IESG approval of the document. > > Comments? I think it's right that this document describes shepherding from WG last call to IESG approval. However, that being the subject of this draft doesn't necessarily mean that the shepherding process stops there -- only that this document doesn't describe more... I think that it's been the intention that a document shepherd keeps shepherding the document all the way to published document (other PROTO and/or IESG members will chime in with protests or agreements here, I'm sure) so we should either not change the paragraphs you quote above, or clarify them in a slightly different manner. If we first can establish whether we agree on the shepherding process continuing beyond the IESG approval, I'm sure we can propose some alternative text for the paragraphs above. It'd be good to have an explicit agreement first, though. Regards, Henrik
_______________________________________________ proto-team mailing list proto-team@ietf.org https://www1.ietf.org/mailman/listinfo/proto-team
- [proto-team] small issues with draft-ietf-proto-w… Lars Eggert
- Re: [proto-team] small issues with draft-ietf-pro… Henrik Levkowetz
- Re: [proto-team] small issues with draft-ietf-pro… Lars Eggert
- [proto-team] Re: small issues with draft-ietf-pro… Lars Eggert
- Re: [proto-team] Re: small issues with draft-ietf… Henrik Levkowetz
- Re: [proto-team] Re: small issues with draft-ietf… Lars Eggert
- Re: [proto-team] Re: small issues with draft-ietf… Henrik Levkowetz
- Re: [proto-team] Re: small issues with draft-ietf… Lars Eggert