Re: [proto-team] Re: Submission of update to document in IESG Eval

Allison Mankin <mankin@psg.com> Mon, 23 October 2006 16:37 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gc2nb-0002Yj-9w; Mon, 23 Oct 2006 12:37:15 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gc2nZ-0002NJ-FH for proto-team@ietf.org; Mon, 23 Oct 2006 12:37:13 -0400
Received: from psg.com ([147.28.0.62]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gc2nY-0001EQ-40 for proto-team@ietf.org; Mon, 23 Oct 2006 12:37:13 -0400
Received: from localhost ([127.0.0.1] helo=psg.com) by psg.com with esmtp (Exim 4.63 (FreeBSD)) (envelope-from <mankin@psg.com>) id 1Gc2nV-000M5j-B3; Mon, 23 Oct 2006 16:37:09 +0000
To: Brian E Carpenter <brc@zurich.ibm.com>
Subject: Re: [proto-team] Re: Submission of update to document in IESG Eval
Date: Mon, 23 Oct 2006 09:37:09 -0700
From: Allison Mankin <mankin@psg.com>
X-Spam-Score: -4.4 (----)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
Cc: proto-team@ietf.org
X-BeenThere: proto-team@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: mankin@psg.com
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
Message-Id: <E1Gc2nb-0002Yj-9w@megatron.ietf.org>

Brian,

The document mainly differs from -07 in adding Sections 4 and 5,
about shepherding the IANA processing and shepherding the
document in the RFC Editor.

Note: I did not include errata shepherding  because this
 seems not to be clear yet - errata can be found forever -
 I hesitated to assume the Document Shepherd could still be
 attached at arbitrary times after RFC publication.  Someone
 is thinking about errata verification since the WGs know
 best, and this sort of question?  We might want to add
 an explicit disclaimer about errata shepherding as a
 Note to the RFC Editor text.  


I see now that I did not add mentions of the new sections
in the paragraph that starts "The remainder of this document 
is organised as follows" - so if you don't want one more revision,
I may ask to give you that as a Note to the RFC Editor.

Other mods:

 - Fixed the number references to questions in the Document Shepherd
   Write-Up

A few updates to ensure a bit more specificity of text which is
already there.  In a WG document, I would not be happy with the
editor, but I think this was ok/constructive (of course :).
See diffs when we get to the tools.ietf.org page.

I added to the Document Shepherd Write-Up questions about
IANA a question about whether there's been action on
any designated Expert.

Under the Document Announcement Write-Up in Section 1, I had
a formatting problem when I tried to simply add a line before
the listing of the Document Shepherd and the Responsible
Area Director, so I resorted to giving that its own heading,
"Personnel".  



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