Re: The IESG Approved the Expansion of the AS Number Registry

David Conrad <drc@virtualized.org> Thu, 30 November 2006 11:04 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gpjis-0004RT-VZ; Thu, 30 Nov 2006 06:04:58 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gpjir-0004R3-7A for ietf@ietf.org; Thu, 30 Nov 2006 06:04:57 -0500
Received: from ns.virtualized.org ([204.152.189.134] helo=mail.virtualized.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gpjin-00030K-7V for ietf@ietf.org; Thu, 30 Nov 2006 06:04:57 -0500
Received: from terminus.local (ns.virtualized.org [204.152.189.134]) by mail.virtualized.org (8.12.9p1/8.12.9) with ESMTP id kAUB0FrG002163; Thu, 30 Nov 2006 03:00:38 -0800 (PST) (envelope-from drc@virtualized.org)
Received: from [127.0.0.1] by terminus.local (PGP Universal service); Thu, 30 Nov 2006 03:04:37 -0800
X-PGP-Universal: processed; by terminus.local on Thu, 30 Nov 2006 03:04:37 -0800
In-Reply-To: <Pine.LNX.4.62.0611291243330.21560@sokol.elan.net>
References: <OFD0267ABF.3F66D904-ON80257235.003D0E82-80257235.003DF739@btradianz.com> <456D8B5D.9010206@ripe.net> <04643DE6-2102-4BE8-B4B6-0BCD810B50FC@ca.afilias.info> <Pine.LNX.4.62.0611290853390.27374@sokol.elan.net> <223ECFD0-A4AF-414A-9E72-660491F5499B@ca.afilias.info> <Pine.LNX.4.62.0611291243330.21560@sokol.elan.net>
Mime-Version: 1.0 (Apple Message framework v752.3)
Message-Id: <67375E78-0F93-40A1-8B6E-9B11CAC1457D@virtualized.org>
From: David Conrad <drc@virtualized.org>
Date: Thu, 30 Nov 2006 03:04:05 -0800
To: "william(at)elan.net" <william@elan.net>
X-Mailer: Apple Mail (2.752.3)
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Cc: Henk Uijterwaal <henk@ripe.net>, ietf@ietf.org
Subject: Re: The IESG Approved the Expansion of the AS Number Registry
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>
Errors-To: ietf-bounces@ietf.org

Hi,

On Nov 29, 2006, at 12:52 PM, william(at)elan.net wrote:
>>> I did not see any consensus on that issue when it was brought to  
>>> NANOG-m.
>> Interesting. I didn't notice any support for separating the 32-bit  
>> quantity into two sections, but I remember many people decrying  
>> the need for any separator at all.
> I'd have to look at archive but I was not left with impression that  
> people were against it rather they were noting changes that would  
> have to be made.

Obviously, 32-bit ASNs are 32 bit binary values and could be  
represented in an infinite number of ways. IANA has chosen to use the  
textual convention documented in draft-michaelson-4byte-as- 
representation-02 for the expansion of the ASN registry found at  
http://www.iana.org/assignments/as-numbers since, as that draft  
mentions:

    This notation has been informally adopted by at least one vendor,  
and
    used consistently in presentations in the Regional Internet Registry
    (RIR) community towards the deployment of 4-byte AS numbers.

Rgds,
-drc


_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf