[from the REN-news mailing list]
As of the 1st of January, all the Region Internet Registries (RIR's),I suppose this is a bit like the USG jump-starting DNSSEC by requiring it be present for the .gov TLD. But only a little bit, because in this case the pressure on the vendors is going to be coming from annoyed customers.
that being, AfriNIC, APNIC, LACNIC, RIPE and ARIN have adopted a policy which allocates 32bit ASN's by default
...
[A]lmost no networking equipment out there
currently supports these.
...
This means that should you get a 32bit ASN instead of a 16bit ASN, it
will not be useable to peer with or announce to the TENET network or
most other networks at this point.
And since there's no backwards-compatibility built-in (no fall-back number), Metcalfe's Law works against one here: everyone you need to peer with also needs updated equipment and/or software.
1 comment:
Hi There,
Your blog entry here isnt *quite* correct, if you want to peer with someone with a 32bit ASN, you are right, you and they will both need hardware that supports 32bit ASN's (unless you use a very dirty hack explained below). However, if someone on the internet is announcing routes with a 32bit ASN further upstream, you will still receive their prefix's and see a path, just not the 32bit path. In this particular case, all 32bit ASN's will be mapped to 23456 (making identification of upstream originator impossible, which REALLY sucks). As stated, the really dirty hack would be to get the guy you were peering with from your 32bit ASN to his 16bit ASN to mark you as coming from AS23456... but seriously... don't do that.
There is some backwards compatibility... but not for the purpose who gets a 32bit ASN and actually has to implement it himself!
Post a Comment