Re: [proto-team] Re: Revision of shepherding draft for the deadline

Lars Eggert <lars.eggert@netlab.nec.de> Tue, 07 March 2006 10:23 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FGZLs-0001La-Fv; Tue, 07 Mar 2006 05:23:36 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FGZLq-0001G3-SN for proto-team@ietf.org; Tue, 07 Mar 2006 05:23:34 -0500
Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129] helo=chiedprmail1.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FGYF0-0002Cb-4j for proto-team@ietf.org; Tue, 07 Mar 2006 04:12:26 -0500
Received: from kyoto.netlab.nec.de ([195.37.70.21]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1FGY3W-00056c-9O for proto-team@ietf.org; Tue, 07 Mar 2006 04:00:37 -0500
Received: from lars.local (unknown [195.37.70.134]) by kyoto.netlab.nec.de (Postfix) with ESMTP id B3CAE1BAC4D for <proto-team@ietf.org>; Tue, 7 Mar 2006 10:01:10 +0100 (CET)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by lars.local (Postfix) with ESMTP id AD2317740E9 for <proto-team@ietf.org>; Tue, 7 Mar 2006 10:00:27 +0100 (CET)
Mime-Version: 1.0 (Apple Message framework v746.2)
In-Reply-To: <20060306145315.GA9388@1-4-5.net>
References: <951b596b0603051848s13ac0f1bm5af9ed74345dcb0a@mail.gmail.com> <20060306145315.GA9388@1-4-5.net>
Message-Id: <F03F98D9-E919-482B-A07F-D8D3FE4FAA1D@netlab.nec.de>
Cc: proto-team@ietf.org
From: Lars Eggert <lars.eggert@netlab.nec.de>
Subject: Re: [proto-team] Re: Revision of shepherding draft for the deadline
Date: Tue, 7 Mar 2006 10:00:21 +0100
X-Mailer: Apple Mail (2.746.2)
X-Spam-Score: -2.5 (--)
X-Scan-Signature: 6ffdee8af20de249c24731d8414917d3
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="===============0995156675=="
Errors-To: proto-team-bounces@ietf.org

Hi,

On Mar 6, 2006, at 15:53, David Meyer wrote:
>         I've read it over a few times and I like it. Others?

read it and agree, it's in good shape overall. I only have some minor  
comments:

(1) If RFC2119 language is applicable to a process document (and I'm  
not sure that it is), some parts of the document could use some  
RFC2119-ization. Example in Section 3.1: change "it is the task of  
the Shepherding WG Chair to do a document write-up" to "the  
Shepherding WG Chair MUST do a document write-up".

(2) The intro briefly notes that chairs can appoint secretaries as  
shepherds, but the process description in Section 3 never picks this  
up. A brief paragraph on what steps this involves may be good. We may  
also want to change terminology from "Shepherding WG Chair" to simply  
"Shepherd" or something similar for that reason.

Nits:

URL in Section 3.1 point 1.g should become a reference

typo in Section 3.1 point 1.h: s/publicatioin/publication/

same paragraph has some duplication: "as described in BCP 97, RFC  
3967 RFC 3967 [RFC3967]"

Section 3.1, last paragraph: not sure if IESG secretary email address  
should be hardcoded here - maybe just say "to the AD and the IESG  
secretary?"

Lars

PS: Aaron has used the PROTO process in DCCP in the past. We've  
dropped the ball a bit on this when Tom and me took over, but we're  
going to start to use PROTO again with draft-ietf-dccp-tfrc-voip-05,  
which has just passed WGLC.
-- 
Lars Eggert                                     NEC Network Laboratories


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