Re: Last Call: 'Internet Code Point Assignments' to Proposed Standard
Brian E Carpenter <brc@zurich.ibm.com> Fri, 12 August 2005 12:43 UTC
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1E3Ysh-0005X0-DR; Fri, 12 Aug 2005 08:43:27 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1E3Ysf-0005Vy-3t; Fri, 12 Aug 2005 08:43:25 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA19537; Fri, 12 Aug 2005 08:43:21 -0400 (EDT)
Received: from mtagate3.uk.ibm.com ([195.212.29.136]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1E3ZR9-0007wb-1O; Fri, 12 Aug 2005 09:19:03 -0400
Received: from d06nrmr1407.portsmouth.uk.ibm.com (d06nrmr1407.portsmouth.uk.ibm.com [9.149.38.185]) by mtagate3.uk.ibm.com (8.12.10/8.12.10) with ESMTP id j7CChWXR345360; Fri, 12 Aug 2005 13:43:32 +0100
Received: from d06av02.portsmouth.uk.ibm.com (d06av02.portsmouth.uk.ibm.com [9.149.37.228]) by d06nrmr1407.portsmouth.uk.ibm.com (8.12.10/NCO/VERS6.7) with ESMTP id j7CChDCf197826; Fri, 12 Aug 2005 13:43:13 +0100
Received: from d06av02.portsmouth.uk.ibm.com (loopback [127.0.0.1]) by d06av02.portsmouth.uk.ibm.com (8.12.11/8.13.3) with ESMTP id j7CChCji014550; Fri, 12 Aug 2005 13:43:12 +0100
Received: from mail-gw3.hursley.ibm.com (mail-gw3.hursley.ibm.com [9.20.131.251]) by d06av02.portsmouth.uk.ibm.com (8.12.11/8.12.11) with ESMTP id j7CChC1N014545; Fri, 12 Aug 2005 13:43:12 +0100
Received: from [9.20.136.27] (helo=sp15en17.hursley.ibm.com) by mail-gw3.hursley.ibm.com with esmtp (Exim 4.50) id 1E3YsS-00019u-Lt; Fri, 12 Aug 2005 13:43:12 +0100
Received: from zurich.ibm.com (sig-9-146-217-20.de.ibm.com [9.146.217.20]) by sp15en17.hursley.ibm.com (AIX5.1/8.11.6p2/8.11.0) with SMTP id j7CChCo113774; Fri, 12 Aug 2005 13:43:12 +0100
Message-ID: <42FC995C.5000309@zurich.ibm.com>
Date: Fri, 12 Aug 2005 14:43:08 +0200
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: ietf@ietf.org
References: <E1E2vaU-0005nH-S9@newodin.ietf.org> <Pine.LNX.4.61.0508102255560.15537@netcore.fi>
In-Reply-To: <Pine.LNX.4.61.0508102255560.15537@netcore.fi>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 31247fb3be228bb596db9127becad0bc
Content-Transfer-Encoding: 7bit
Cc: swallow@cisco.com, Eric.Gray@Marconi.com, iesg@ietf.org, John.Rutemiller@Marconi.com
Subject: Re: Last Call: 'Internet Code Point Assignments' to Proposed Standard
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
Commenting as an individual (and as the culprit for RFC 1888 and RFC 4048): Pekka Savola wrote: > On Wed, 10 Aug 2005, The IESG wrote: > >> The IESG has received a request from an individual submitter to >> consider the >> following document: >> >> - 'Internet Code Point Assignments ' >> <draft-gray-rfc1888bis-01.txt> as a Proposed Standard >> >> The IESG plans to make a decision in the next few weeks, and solicits >> final comments on this action. Please send any comments to the >> iesg@ietf.org or ietf@ietf.org mailing lists by 2005-09-07. >> >> The file can be obtained via >> http://www.ietf.org/internet-drafts/draft-gray-rfc1888bis-01.txt > > > The title is inappropriately generic. I agree. Suggest Internet Code Point Assignments for NSAP Addresses > Given RFC 4048, is there sufficient evidence that this would be useful to the operational (or any other) community ? My understanding is that the ATM world needs this. > (Being more explicit on this draft's relationship to RFC 1888 and 4048 would not hurt in general.) Slightly agree, see below. 1. Introduction ... The means RFC 1888 defined for encoding NSAP addresses in IPv6 address format, was heavily annotated with warnings and limitations that apply should this encoding be used. Possibly as a result, these encodings are not used and appear never to have been used in any IPv6 deployment. In addition, section 6 contains minor errors. As a result of these various considerations, an Internet Draft [BC] has been submitted recommending that RFC 1888 be made historical. The last sentence, and the reference, is out of date. Suggest: As a result of these various considerations, RFC 1888 has been obsoleted and declared Historic by RFC 4048 [ref RFC 4048]. 2. IANA Considerations ... Remaining decimal values '2' through '9999' SHOULD be assigned on an IETF consensus basis, with IANA consent. I don't understand "with IANA consent." Also SHOULD seems ambiguous. Suggest: Remaining decimal values '2' through '9999' MUST be assigned on an IETF Consensus basis [ref RFC 2434]. but I wonder whether Expert Review wouldn't be sufficient? Do we really need to trouble the whole IETF for this? 4. Security Considerations Security issues are not specifically addressed in this document, as the NSAP encoding of IPv4 and IPv6 addresses is compatible with the corresponding security mechanisms of RFC 1825 [1825]. I'd prefer to be told that this document doesn't directly affect the security of the Internet, if that is the case. Also, RFC 1825 is obsolete - the current document is RFC 2401. Brian _______________________________________________ Ietf mailing list Ietf@ietf.org https://www1.ietf.org/mailman/listinfo/ietf
- Re: Last Call: 'Internet Code Point Assignments' … Pekka Savola
- Re: Last Call: 'Internet Code Point Assignments' … Brian E Carpenter
- Re: Last Call: 'Internet Code Point Assignments' … Pekka Savola
- Re: Last Call: 'Internet Code Point Assignments' … Alexey Melnikov