[proto-team] Re: Russ's Discuss on the doc shepherding draft

Brian E Carpenter <brc@zurich.ibm.com> Tue, 21 November 2006 08:08 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GmQft-0006KL-9l; Tue, 21 Nov 2006 03:08:13 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GmQfr-0006K2-PT; Tue, 21 Nov 2006 03:08:11 -0500
Received: from mtagate1.de.ibm.com ([195.212.29.150]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GmQfq-00072Y-4U; Tue, 21 Nov 2006 03:08:11 -0500
Received: from d12nrmr1607.megacenter.de.ibm.com (d12nrmr1607.megacenter.de.ibm.com [9.149.167.49]) by mtagate1.de.ibm.com (8.13.8/8.13.8) with ESMTP id kAL889WH264160; Tue, 21 Nov 2006 08:08:09 GMT
Received: from d12av01.megacenter.de.ibm.com (d12av01.megacenter.de.ibm.com [9.149.165.212]) by d12nrmr1607.megacenter.de.ibm.com (8.13.6/8.13.6/NCO v8.1.1) with ESMTP id kAL8BZAB2552016; Tue, 21 Nov 2006 09:11:35 +0100
Received: from d12av01.megacenter.de.ibm.com (loopback [127.0.0.1]) by d12av01.megacenter.de.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id kAL888er021473; Tue, 21 Nov 2006 09:08:08 +0100
Received: from sihl.zurich.ibm.com (sihl.zurich.ibm.com [9.4.16.232]) by d12av01.megacenter.de.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id kAL888D4021467; Tue, 21 Nov 2006 09:08:08 +0100
Received: from zurich.ibm.com ([9.4.210.199]) by sihl.zurich.ibm.com (AIX4.3/8.9.3p2/8.9.3) with ESMTP id JAA43490; Tue, 21 Nov 2006 09:08:06 +0100
Message-ID: <4562B3E7.3050901@zurich.ibm.com>
Date: Tue, 21 Nov 2006 09:08:07 +0100
From: Brian E Carpenter <brc@zurich.ibm.com>
Organization: IBM
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en, fr, de
MIME-Version: 1.0
To: Allison Mankin <mankin@psg.com>
References: <E1GmJMp-0002gL-LQ@megatron.ietf.org>
In-Reply-To: <E1GmJMp-0002gL-LQ@megatron.ietf.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5011df3e2a27abcc044eaa15befcaa87
Cc: Russ Housley <housley@vigilsec.com>, iesg@ietf.org, proto-team@ietf.org
Subject: [proto-team] Re: Russ's Discuss on the doc shepherding draft
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>
Errors-To: proto-team-bounces@ietf.org

There is a feeling that we should convert the I-D checklist
into an ION shortly - but that doesn't affect the principle,
although it would change the exact URL.

In fact I would rather the template to be in Additional IESG
Information than in the IETF Chair material. That's where IONs will
live anyway, and we will have versioning support.

Try
http://www.ietf.org/IESG/content/Doc-Writeup.txt
for now. Is that the right material? (txt is so much easier to maintain
than html.)

BTW, shouldn't the Personnel section include:

Are there existing IANA Experts, or do they need to be appointed?

     Brian


Allison Mankin wrote:
> Russ,
> 
> Thanks for the good suggestion of where to put the template.
> When we put up the template (shortly, I hope), I want to
> emulate ID-checklist and include the contact info of
> the maintainer(s) and some view of how it is updated.
> 
> How does the following language strike you for clearing
> your DISCUSS?  (The URL is a parallel to ID-checklist).
> 
> Section 3.1
> 
> OLD:
> There are two parts to this task.  First, the Document Shepherd 
> answers questions (1.a) to (1.i) below to give the Responsible Area
> Director insight into the working group process that applied to
> this document.
> 
> NEW:
> There are two parts to this task, the "Document Shepherd Write-Up" 
> and the "Document Announcement Write-Up".  The Document Shepherd 
> Write-Up consists of a template of questions to give the Responsible
> Area Director insight into the working group process that applied 
> to the document.  The template is maintained on the web, in similar 
> fashion to the ID-checklist called out in (1.g) below.  The template
> at the time of this writing is published here.  The current Write-Up
> template is maintained by the IETF at http://www.ietf.org/Doc-Writeup.html
> (and a link to it is provided among IETF WG Chair resources).
> 
> 
> Allison
> 
> 
>>Date:    Fri, 17 Nov 2006 20:09:29 EST
>>To:      mankin@psg.com,housley@vigilsec.ietf.org
>>cc:      iesg@ietf.org,proto-team@ietf.org
>>From:    Russ Housley <housley@vigilsec.com>
>>Subject: Re: Russ's Discuss on the doc shepherding draft
>>
>>
>>Allison:
>>
>>I do not want you to add any words to the template now.  We have been 
>>using the current template very effectively.  I just expect that it 
>>will need to be changed at some point, for RFC 4107 or for something 
>>else.  The real point of my DISCUSS is that I do not want to change 
>>an RFC in order to change the template.
>>
>>I think the same directory where we have ID-Checklist makes sense.
>>
>>Russ
>>
>>At 06:02 PM 11/17/2006, Allison Mankin wrote:
>>
>>
>>>Russ,
>>>
>>>I think it makes sense to add those words to the Write-Up about checking
>>>that RFC 4107 concerns are handled, because we have asked this to be
>>>an explicit matter in protocols.  I don't think will always be
>>>a question in the Write-Up from similar BCPs, even though that BCP might
>>>incur review requirements:  but maybe I'm wrong.  Maybe on the web we'll
>>>need a Write-Up with pull down menus (answer all the questions that
>>>apply :).
>>>
>>>"The initial Document Write-Up is included here, but changes are
>>>expected over time"
>>>
>>>We intended to do this with a web-based one.  I've been the block
>>>for launching the web content, I'm afraid, though I also want input
>>>for the right place for the page, that's one of my issues.
>>>
>>>Where will it be intuitive to look for the updated Write-Up, if you're
>>>a shepherd?  What do you think?
>>>
>>>Allison
>>
> 

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