Re: [proto-team] Re: small issues with draft-ietf-proto-wgchair-doc-shepherding-07

Lars Eggert <lars.eggert@netlab.nec.de> Sat, 01 July 2006 09:35 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fwbt1-00053U-BB; Sat, 01 Jul 2006 05:35:35 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fwbsz-00053K-PK for proto-team@ietf.org; Sat, 01 Jul 2006 05:35:33 -0400
Received: from kyoto.netlab.nec.de ([195.37.70.21]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fwbsy-0008IH-7r for proto-team@ietf.org; Sat, 01 Jul 2006 05:35:33 -0400
Received: from lars.localhost (ip-80-226-8-137.vodafone-net.de [80.226.8.137]) by kyoto.netlab.nec.de (Postfix) with ESMTP id 8AB371BAC4D for <proto-team@ietf.org>; Sat, 1 Jul 2006 11:22:30 +0200 (CEST)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by lars.local (Postfix) with ESMTP id D012E131991 for <proto-team@ietf.org>; Sat, 1 Jul 2006 10:38:17 +0200 (CEST)
Mime-Version: 1.0 (Apple Message framework v752.2)
In-Reply-To: <44A2C2A1.5090307@levkowetz.com>
References: <35758337-E41C-4EFE-AABA-A10F499198BC@netlab.nec.de> <3EC69FA4-7F5E-49C7-AB64-DC25C99A60FE@netlab.nec.de> <44A2C2A1.5090307@levkowetz.com>
Message-Id: <90951F0D-0BAC-4F64-8230-F4BDCEED7920@netlab.nec.de>
Cc: proto-team@ietf.org
From: Lars Eggert <lars.eggert@netlab.nec.de>
Subject: Re: [proto-team] Re: small issues with draft-ietf-proto-wgchair-doc-shepherding-07
Date: Sat, 1 Jul 2006 10:38:15 +0200
X-Mailer: Apple Mail (2.752.2)
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 29dc808194f5fb921c09d0040806d6eb
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="===============1422089299=="
Errors-To: proto-team-bounces@ietf.org

Hi,

On Jun 28, 2006, at 19:55, Henrik Levkowetz wrote:
> 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.

I think it makes total sense that the shepherding process should  
continue all the way until publication. See below for a proposed  
wording change to the draft.

Another issue is that AFAIK the RFC Editor does not currently CC  
document shepherds on any email they send. (Usually, the chairs are  
the shepherds, so in practice that's not a big issue, but we do now  
allow secretaries to become shepherds.) We may want to explicitly  
instruct the RFC Editor to do so.

So, how about replacing this:

>    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.

with:

    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.

    Shepherding actions during post-approval highly depend on the  
specific
    document. Consequently, this document does not give detailed  
guidelines
    for the post-approval shepherding phase, other than noting that a
    document shepherd SHOULD generally treat post-approval requests  
from the
    IANA or the RFC Editor similarly to DISCUSS items raised during IESG
    evaluation (see Section 3.3).

Comments?

If we decide on this, we might also want to change the title to  
something like "Document Shepherding from Working Group Last Call to  
RFC Publication".

Lars
-- 
Lars Eggert                                     NEC Network Laboratories


_______________________________________________
proto-team mailing list
proto-team@ietf.org
https://www1.ietf.org/mailman/listinfo/proto-team