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

Henk Uijterwaal <henk@ripe.net> Wed, 29 November 2006 13:30 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GpPW9-0006ZB-Of; Wed, 29 Nov 2006 08:30:29 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GpPW7-0006Z6-VI for ietf@ietf.org; Wed, 29 Nov 2006 08:30:27 -0500
Received: from postman.ripe.net ([193.0.0.199]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GpPW4-0002P8-LA for ietf@ietf.org; Wed, 29 Nov 2006 08:30:27 -0500
Received: by postman.ripe.net (Postfix, from userid 4008) id E79D124127; Wed, 29 Nov 2006 14:30:19 +0100 (CET)
Received: from herring.ripe.net (herring.ripe.net [193.0.1.203]) by postman.ripe.net (Postfix) with ESMTP id E53EC240B7; Wed, 29 Nov 2006 14:30:18 +0100 (CET)
Received: from [127.0.0.1] (chimp.ripe.net [193.0.1.199]) by herring.ripe.net (Postfix) with ESMTP id 365382F5A2; Wed, 29 Nov 2006 14:30:18 +0100 (CET)
Message-ID: <456D8B5D.9010206@ripe.net>
Date: Wed, 29 Nov 2006 14:30:05 +0100
From: Henk Uijterwaal <henk@ripe.net>
Organization: RIPE NCC
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To: Michael.Dillon@btradianz.com
References: <OFD0267ABF.3F66D904-ON80257235.003D0E82-80257235.003DF739@btradianz.com>
In-Reply-To: <OFD0267ABF.3F66D904-ON80257235.003D0E82-80257235.003DF739@btradianz.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-RIPE-Spam-Level:
X-RIPE-Spam-Tests: ALL_TRUSTED,BAYES_00
X-RIPE-Spam-Status: N 0.039059 / -4.4
X-RIPE-Signature: b6d0d2742ba101ca9457d8cd2f11df79
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe
Cc: ietf@ietf.org
Subject: Re: Fwd: 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

Michael.Dillon@btradianz.com wrote:

>> Until all software understands the bigger numbers, people
>> will want to continue using the 16-bit ones.
> 
> The IESG message talked about numbers from 65536 to some
> big number. Here suddenly, we see a reference to some
> number of bits.
> 
>> Meanwhile, to encourage the migration to 4-byte ASNs, the RIRs have
> 
> Now there is a reference to some number of bytes. What is going
> on here?

I think we're mixing up the number of bits reserved and the decimal
representation.  So far, 16 bits were used, or 2 bytes, the extensions
use 32 bits on the wire.  16 bits can be used for an unsigned decimal
number up to 65536, so it does make some sense to use that instead
of a string of 0's and 1's.

> On the NANOG list it has already been pointed out that a lot
> of network management software cannot handle such notation and
> in some cases, 1.0 could be interpreted as the IP address 
> 1.0.0.0. It has been confirmed that one widely used PERL 
> library interprets x.y as IP address x.0.0.y.

I think this is a bug.

> Because of this I think it would be useful for the IETF
> to publish a draft defining the notation for AS numbers
> so that we can either keep it simple or, if a new notation
> is to be used, then publicly state the issues of software 
> which needs to be changed. Such a draft should really come
> from the WG which extended the AS number in the first 
> place.

There is:

   Canonical Textual Representation of 4-byte AS Numbers
   draft-michaelson-4byte-as-representation-02

describing the format of ASN32 and

   RPSL extensions for 32 bit AS Numbers
   draft-uijterwaal-rpsl-4byteas-ext-01.txt

describing what has to be changed in RPSL based tools for ASN32.  For
the latter draft, there is no good place in the IETF right now, but I
do welcome comments.

Henk

------------------------------------------------------------------------------
Henk Uijterwaal                           Email: henk.uijterwaal(at)ripe.net
RIPE Network Coordination Centre          http://www.amsterdamned.org/~henk
P.O.Box 10096          Singel 258         Phone: +31.20.5354414
1001 EB Amsterdam      1016 AB Amsterdam  Fax: +31.20.5354445
The Netherlands        The Netherlands    Mobile: +31.6.55861746
------------------------------------------------------------------------------

# Lawyer: "Now sir, I'm sure you are an intelligent and honest man--"
# Witness: "Thank you. If I weren't under oath, I'd return the compliment."


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