Re: [proto-team] revision of draft-ietf-proto-wgchair-doc-shepherding attached

Henrik Levkowetz <henrik@levkowetz.com> Fri, 09 June 2006 14:28 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fohyf-0007iZ-G5; Fri, 09 Jun 2006 10:28:45 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fohye-0007co-Ch for proto-team@ietf.org; Fri, 09 Jun 2006 10:28:44 -0400
Received: from av7-1-sn3.vrr.skanova.net ([81.228.9.181]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fohyc-0004PU-Uq for proto-team@ietf.org; Fri, 09 Jun 2006 10:28:44 -0400
Received: by av7-1-sn3.vrr.skanova.net (Postfix, from userid 502) id 892AF37F1D; Fri, 9 Jun 2006 16:03:01 +0200 (CEST)
Received: from smtp3-2-sn3.vrr.skanova.net (smtp3-2-sn3.vrr.skanova.net [81.228.9.102]) by av7-1-sn3.vrr.skanova.net (Postfix) with ESMTP id 7822537EC4; Fri, 9 Jun 2006 16:03:01 +0200 (CEST)
Received: from shiraz.levkowetz.com (81-232-110-214-no16.tbcn.telia.com [81.232.110.214]) by smtp3-2-sn3.vrr.skanova.net (Postfix) with ESMTP id C1D3E37E43; Fri, 9 Jun 2006 16:28:41 +0200 (CEST)
Received: from localhost ([127.0.0.1]) by shiraz.levkowetz.com with esmtp (Exim 4.62) (envelope-from <henrik@levkowetz.com>) id 1FohyZ-0001x6-Vo; Fri, 09 Jun 2006 16:28:41 +0200
Message-ID: <44898597.9000705@levkowetz.com>
Date: Fri, 09 Jun 2006 16:28:39 +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] revision of draft-ietf-proto-wgchair-doc-shepherding attached
References: <D27342A1-3CD2-483F-B031-37690568B927@netlab.nec.de> <20060607140952.GA2437@1-4-5.net> <6FF50059-B88A-44C3-B586-63B6A040F7FD@netlab.nec.de> <448879B6.9040703@levkowetz.com> <C60A11A6-029B-45CC-B54D-6C7E7177F6A2@netlab.nec.de> <5C7CABE4-58DE-4DAD-ADF6-436504E50A61@netlab.nec.de>
In-Reply-To: <5C7CABE4-58DE-4DAD-ADF6-436504E50A61@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: b5d20af10c334b36874c0264b10f59f1
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="===============0596073115=="
Errors-To: proto-team-bounces@ietf.org

Hi Lars,

  I'm of course biased, having suggested the changes, but I find that
to me it seems that the document reads much more smoothly now.  Maybe
that's the reason why I found more stuff...

on 2006-06-09 15:09 Lars Eggert said the following:
> On Jun 9, 2006, at 9:15, Lars Eggert wrote:
>> Agree with all of them, will make the edits.
> 
> Revision with Henrik's suggestions attached.

Minor fix:

Section 3.1, paragraph 7:

>    (1.d)  Does the Document Shepherd have any specific concerns or
>           issues with this document that the Responsible Area Director
>           and/or the IESG should be aware of?  For example, perhaps you
>           he or she is uncomfortable with certain parts of the document,
>           or has concerns whether there really is a need for it.  In any
>           event, if those issues have been discussed in the WG and the
>           WG has indicated that it still wishes to advance the document,
>           detail those concerns here.

	s/perhaps you he or she/perhaps he or she/

Larger issue:

Section 3.1, paragraph 11:

>    (1.i)  For Standards Track and BCP documents, the IESG approval
>           announcement includes a write-up.  Please provide such a
>           write-up.  Recent examples can be found in the "Action"
>           announcements for approved documents.  The approval
>           announcement contains the following sections:

One question for clarification: In the current revision, the "Document
Shepherd Write-up" seems to be defined as what's covered under 1.i, and
presumably the "Document Shepherd Questionnaire" is the whole of the
(1.a)..(1.i) set of questions.  It seems to me that in some places the
document mentions the Document Shepherd Write-up where intention is to
talk about talk about both questionaire and (1.i) write-up; for instance
here:

>    The Document Shepherd MUST send the Document Shepherd Write-Up to the
>    Responsible Area Director and iesg-secretary@ietf.org together with
>    the request to publish the document.  The Document Shepherd SHOULD
>    also send the write-up, minus any discussion of possible appeals, to
>    the working group mailing list.

I seem to remember that during the original discussions, we sometimes
(mostly?) referred to the whole questionnaire as the write-up.  Whatever
we call them, it would be good to have clear and separate terms for the
(1.i) writeup and for the questionnaire, and make sure that where the
document now mentions the write-up, it is verified (and if needed corrected)
so it correctly indicates (1.i) write-up or questionnaire.  It may be that
most places where the document now mentions 'Write-up' the whole
questionnaire is meant - if we define the 'Write-up' as being the whole
questionnaire, we should have a different term for the (1.i) write-up.


Regards,

	Henrik

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