RE: Internet Draft rfc1888bis
"Pandey, Arun" <pandey.arun@hp.com> Tue, 15 March 2005 05:35 UTC
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA10659 for <ipv6-web-archive@ietf.org>; Tue, 15 Mar 2005 00:35:58 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DB4mW-00032T-6z for ipv6-web-archive@ietf.org; Tue, 15 Mar 2005 00:39:52 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DB4dE-0002co-6S; Tue, 15 Mar 2005 00:30:16 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DB4dC-0002cj-3U for ipv6@megatron.ietf.org; Tue, 15 Mar 2005 00:30:14 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA10258 for <ipv6@ietf.org>; Tue, 15 Mar 2005 00:30:10 -0500 (EST)
Received: from mailout.zma.compaq.com ([161.114.64.105] helo=zmamail05.zma.compaq.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DB4gw-0002nf-FH for ipv6@ietf.org; Tue, 15 Mar 2005 00:34:07 -0500
Received: from tayexg11.americas.cpqcorp.net (tayexg11.americas.cpqcorp.net [16.103.130.186]) by zmamail05.zma.compaq.com (Postfix) with ESMTP id 79CFFCE30; Tue, 15 Mar 2005 00:30:03 -0500 (EST)
Received: from tayexc17.americas.cpqcorp.net ([16.103.130.15]) by tayexg11.americas.cpqcorp.net with Microsoft SMTPSVC(6.0.3790.211); Tue, 15 Mar 2005 00:30:02 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 15 Mar 2005 00:30:01 -0500
Message-ID: <A1FEAC5922FD9442A5832B08A2CA645B0716DAD6@tayexc17.americas.cpqcorp.net>
Thread-Topic: Internet Draft rfc1888bis
Thread-Index: AcUo3hfDYd+gYqTbThqPFGBIdc+KcgAPy6Xg
From: "Pandey, Arun" <pandey.arun@hp.com>
To: Eric.Gray@Marconi.com, John.Rutemiller@Marconi.com, swallow@cisco.com
X-OriginalArrivalTime: 15 Mar 2005 05:30:02.0948 (UTC) FILETIME=[09C45040:01C52920]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15
Content-Transfer-Encoding: quoted-printable
Cc: ipv6@ietf.org
Subject: RE: Internet Draft rfc1888bis
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
Sender: ipv6-bounces@ietf.org
Errors-To: ipv6-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f60d0f7806b0c40781eee6b9cd0b2135
Content-Transfer-Encoding: quoted-printable
Hi John, Eric and George, As discussed with John and others more than a couple of months back, I have worked to put the distinct requirements of X.500 for Internet Code Point (ICP) for encoding an IPv6 address in an NSAP Address in another draft. I had submitted this draft to IETF Dec-05. This draft can be accessed via : http://www.ietf.org/internet-drafts/draft-pandey-osidirectory-ipv6-nsapa-format-00.txt Please do review the same. Ideally the new format specified for X.500 in the above draft (with suitable comments incorporated) would be good to be considered for inclusion in rfc1888bis. Best Regards Arun Pandey -----Original Message----- From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org]On Behalf Of Gray, Eric Sent: Tuesday, March 15, 2005 3:02 AM To: 'ipv6@ietf.org' Subject: Internet Draft rfc1888bis Folks, The Internet Area Directors asked me to announce this ID to the IPv6 Working Group. Please do not be misled by the title, it is not an attempt to resurrect RFC 1888 in its entirety. The ID represents an extraction of section 6 of RFC 1888 - which defines an Internet Code Point (ICP) for encoding an IPv6 address in an NSAP Address - as well as adding an Internet Code Point for a similar encoding of IPv4 addresses. The draft also defines a process for further assignments from the IANA controlled NSAP Address space that begins with an Address Format and Identifier (AFI) of 0x35. As such, the ID re-asserts a previously defined way to use IPv6 addresses and extends this definition to include a similar use of IPv4 addresses. It does not attempt to define or modify the general use of these IPv6 and IPv4 addresses and does not affect IP addressing architecture in general. The draft is 10 pages long and is available at: http://www.ietf.org/internet-drafts/draft-gray-rfc1888bis-00.txt The draft was available prior to last week's meeting, but was not discussed because of: 1) insufficient notice to the WG Chair and Area Directors and 2) insufficient time during the WG meeting. -- Eric Gray -------------------------------------------------------------------- IETF IPv6 working group mailing list ipv6@ietf.org Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6 -------------------------------------------------------------------- -------------------------------------------------------------------- IETF IPv6 working group mailing list ipv6@ietf.org Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
- Internet Draft rfc1888bis Gray, Eric
- RE: Internet Draft rfc1888bis Pandey, Arun