[98178] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: ASN Name of the week

daemon@ATHENA.MIT.EDU (Stephen Wilcox)
Wed Jul 25 14:37:02 2007

Date: Wed, 25 Jul 2007 18:06:15 +0100
From: Stephen Wilcox <steve.wilcox@packetrade.com>
To: Carlos Friacas <cfriacas@fccn.pt>
Cc: "Tuc at T-B-O-H.NET" <ml@t-b-o-h.net>, NANOG list <nanog@nanog.org>
In-Reply-To: <Pine.LNX.4.64.0707251616350.13451@gauntlet.fccn.pt>
Errors-To: owner-nanog@merit.edu


On Wed, Jul 25, 2007 at 04:20:25PM +0100, Carlos Friacas wrote:
> 
> On Wed, 25 Jul 2007, Tuc at T-B-O-H.NET wrote:
> 
> >>Hi,
> >>
> >>ASNV6, no clue... but 32-bit ASN are already prepared, at least in
> >>the registry world.
> >>
> >	It was just a joke, since the AS is getting high up there
> >in the 2 byte range (2/3's of the available ones down I think) and
> >was implying that moving to 4 byte would be as fast/efficient/complete
> >as going to IPV6 (Not...)
> 
> That's actually something funny......
> We'll probably run out of v4 addresses sooner than 2 byte ASN, however, 
> globally it seems more pieces of the puzzle are in place for the latter 
> "revolution".

I doubt most routers are 4 byte ASN aware, but the difference is no 'revolution' is required as 4 byte is designed to cross silently across any 2 byte only routers without needing any upgrade by nature of BGPv4s flexibility 

Steve


home help back first fref pref prev next nref lref last post