ICANN/GNSO GNSO Email List Archives

[ga]


<<< Chronological Index >>>    <<< Thread Index >>>

[Fwd: Re: [Fwd: [ga] question regarding number allocations]]

  • To: ga@xxxxxxxxxxxxxx
  • Subject: [Fwd: Re: [Fwd: [ga] question regarding number allocations]]
  • From: "GNSO.SECRETARIAT@xxxxxxxxxxxxxx" <gnso.secretariat@xxxxxxxxxxxxxx>
  • Date: Fri, 25 Jan 2008 21:14:17 +0100


Forwarded from Leo Vegoda, Manager, Number Resources - IANA

Sujet: [ga] question regarding number allocations
Date: Fri, 25 Jan 2008 23:11:18 +0900
De: Andrew McMeikan <andrewm@xxxxxxxxxxxx>
Pour :: ga@xxxxxxxxxxxxxx
Références: <4798690C.90405@xxxxxxxxxxxxxx>


Hi, just a bit of a de-lurk.  Hello to those who remember me.

Just looking at http://www.potaroo.net/tools/asns/

and I was wondering if anyone can let me know where I can read up on
what actions are underway specifically about AS number exhaustion.  I
could find several doom and gloom things, but a distinct lack of 'this
is how quick the solution will be in place'

The current status is that a new 32-bit (4-byte) number space was created.
It contains four billion AS Numbers. The first allocations from this new
number space were made to the RIRs in 2006 and can be seen at the bottom of
the page in the IANA AS Number registry at:

http://www.iana.org/assignments/as-numbers

All five RIR communities set policies for the introduction of the new,
larger AS Number space. The timelines they set are:

    *   From 1 January 2007 the [RIRs] will process applications that
specifically request 4-byte only AS Numbers and assign such AS Numbers as
requested by the applicant. In the absence of any specific request for a
4-byte only AS Number, a 2-byte only AS Number will be assigned by the RIPE
NCC.
    * From 1 January 2009 the [RIRs] will process applications that
specifically request 2-byte only AS Numbers and assign such AS Numbers as
requested by the applicant. In the absence of any specific request for a
2-byte only AS Number, a 4-byte only AS Number will be assigned by the RIPE
NCC.
    * From 1 January 2010 the [RIRs] will cease to make any distinction
between 2-byte only AS Numbers and 4-byte only AS Numbers, and will operate
AS Number assignments from an undifferentiated 4- byte AS Number allocation
pool.

The good news from the IETF and ISP worlds is that networks with 16-bit AS
Numbers do not need to upgrade to support the new 32-bit numbers. When they
talk to an AS numbered from the 32-bit space they will see the 32-bit AS as
AS23456, the transition AS Number. Things should still work OK and routing
should not break.

I was recently pointed at this web site that tracks vendor support for the
new AS Numbers:

http://www.swissix.ch/asn32/doku.php

There is still some work going on to decide on the 'right' way to represent
the new 32-bit AS Numbers. George Michaelson's latest draft on the subject
can be found at:

http://tools.ietf.org/id/draft-michaelson-4byte-as-representation-05.txt

I hope this is helpful.

Kind regards,

Leo Vegoda
Manager, Number Resources - IANA



--
Glen de Saint Géry
GNSO Secretariat - ICANN
gnso.secretariat[at]gnso.icann.org
http://gnso.icann.org



<<< Chronological Index >>>    <<< Thread Index >>>