Re: [proto-team] PROTO template differences

Lars Eggert <lars.eggert@nokia.com> Thu, 19 April 2007 06:45 UTC

Return-path: <proto-team-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HeQOm-0006W2-Ul; Thu, 19 Apr 2007 02:45:44 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HeQOh-0005zI-KP; Thu, 19 Apr 2007 02:45:39 -0400
Received: from smtp.nokia.com ([131.228.20.172] helo=mgw-ext13.nokia.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HeQOg-0001UC-5R; Thu, 19 Apr 2007 02:45:39 -0400
Received: from esebh105.NOE.Nokia.com (esebh105.ntc.nokia.com [172.21.138.211]) by mgw-ext13.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id l3J6j1E4031386; Thu, 19 Apr 2007 09:45:36 +0300
Received: from esebh103.NOE.Nokia.com ([172.21.143.33]) by esebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 19 Apr 2007 09:45:13 +0300
Received: from mgw-int02.ntc.nokia.com ([172.21.143.97]) by esebh103.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.1830); Thu, 19 Apr 2007 09:45:12 +0300
Received: from [172.21.35.232] (esdhcp035232.research.nokia.com [172.21.35.232]) by mgw-int02.ntc.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id l3J6jAlC024134; Thu, 19 Apr 2007 09:45:10 +0300
In-Reply-To: <3E387C1C64088E499E7BF0E86B0E1BF7794225@NSF-BE-03.ad.nsf.gov>
References: <E1D5C12C-BB6A-422B-8C41-C570D9B97E97@nokia.com> <3E387C1C64088E499E7BF0E86B0E1BF7794225@NSF-BE-03.ad.nsf.gov>
Mime-Version: 1.0 (Apple Message framework v752.3)
Message-Id: <E05B6370-963B-4E91-874E-C69DD8CE0234@nokia.com>
From: Lars Eggert <lars.eggert@nokia.com>
Subject: Re: [proto-team] PROTO template differences
Date: Thu, 19 Apr 2007 09:44:54 +0300
To: "ext Mankin, Allison J" <amankin@nsf.gov>
X-Mailer: Apple Mail (2.752.3)
X-OriginalArrivalTime: 19 Apr 2007 06:45:12.0423 (UTC) FILETIME=[47A25770:01C7824E]
X-Nokia-AV: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 00e94c813bef7832af255170dca19e36
Cc: IESG IESG <iesg@ietf.org>, 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="===============1719254940=="
Errors-To: proto-team-bounces@ietf.org

On 2007-4-18, at 22:02, ext Mankin, Allison J wrote:
> In the revision of RFC 2434bis, there's a thought of announcing the
> appointment of any IANA
> Expert in the Document Announcement.  That question does not  
> capture the
> point, but I think this may be why it is there.

Ah. That wasn't clear to me from the text. Maybe replace it with "If  
the document requires IANA experts, insert 'The IANA Expert(s) for  
the registries in this document are <TO BE ADDED BY THE AD>.'" Or  
something like that.

Lars


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