AS Numbers from a common 32-bit pool.
are y'all ready for this gift? --bill Begin forwarded message:
From: "Ernest - (AfriNIC)" <ernest@afrinic.net> Date: December 20, 2010 3:16:42 PST To: announce@afrinic.net Subject: [AfriNIC-announce] AfriNIC to assign AS Numbers from a common 32-bit pool.
Dear Colleagues,
According to the "IANA Policy for Allocation of ASN Blocks to the Regional Internet Registries (RIRs)" - http://www.afrinic.net/docs/policies/AFPUB-2008-ASN-001.htm , IANA will cease to make any distinction between 16 and 32-bit only ASN blocks on 31 December 2010 when making allocations to RIRs.
After this date, the RIRs will assign AS Numbers from an undifferentiated 32-bit ASN allocation pool.
Consequently, for any entity requesting an ASN, AfriNIC will cease to present the ability to opt for a 16- or 32-bit ASN, and will start issuing ASNs from a common 32-bit pool.
We therefore urge all IP network operators to ensure that their routing infrastructure is 32-bit ASN compatible.
Kind regards,
Ernest Byaruhanga.
_______________________________________________ announce mailing list announce@afrinic.net https://lists.afrinic.net/mailman/listinfo.cgi/announce
I'm kinda fearing this in South Africa, as we have a few large incumbents who aren't really driving -NG versions of protocols. They also have a "prove to us it's broken, and we may look at it in a few months' time"-attitude towards it. :O So 32-bit ASNs and IPv6 equally aren't really being driven, apart from by a few key Academic players. Just my ZAR 0.02 -H. On 2010/12/20 14:43, bill manning wrote:
are y'all ready for this gift?
--bill
Begin forwarded message:
From: "Ernest - (AfriNIC)"<ernest@afrinic.net> Date: December 20, 2010 3:16:42 PST To: announce@afrinic.net Subject: [AfriNIC-announce] AfriNIC to assign AS Numbers from a common 32-bit pool.
Dear Colleagues,
According to the "IANA Policy for Allocation of ASN Blocks to the Regional Internet Registries (RIRs)" - http://www.afrinic.net/docs/policies/AFPUB-2008-ASN-001.htm , IANA will cease to make any distinction between 16 and 32-bit only ASN blocks on 31 December 2010 when making allocations to RIRs.
After this date, the RIRs will assign AS Numbers from an undifferentiated 32-bit ASN allocation pool.
Consequently, for any entity requesting an ASN, AfriNIC will cease to present the ability to opt for a 16- or 32-bit ASN, and will start issuing ASNs from a common 32-bit pool.
We therefore urge all IP network operators to ensure that their routing infrastructure is 32-bit ASN compatible.
Kind regards,
Ernest Byaruhanga.
_______________________________________________ announce mailing list announce@afrinic.net https://lists.afrinic.net/mailman/listinfo.cgi/announce
On Mon, Dec 20, 2010 at 02:49:49PM +0200, Heinrich Strauss wrote:
I'm kinda fearing this in South Africa, as we have a few large incumbents who aren't really driving -NG versions of protocols.
They also have a "prove to us it's broken, and we may look at it in a few months' time"-attitude towards it. :O
That would be why 32-bit ASNs have been "requestable" for the last couple of years(?); you could have been prodding providers with "it doesn't work, fix it" for a while now. - Matt -- "For once, Microsoft wasn't exaggerating when they named it the 'Jet Engine' -- your data's the seagull." -- Chris Adams
On Dec 20, 2010, at 10:15 PM, Matthew Palmer wrote:
On Mon, Dec 20, 2010 at 02:49:49PM +0200, Heinrich Strauss wrote:
I'm kinda fearing this in South Africa, as we have a few large incumbents who aren't really driving -NG versions of protocols.
They also have a "prove to us it's broken, and we may look at it in a few months' time"-attitude towards it. :O
That would be why 32-bit ASNs have been "requestable" for the last couple of years(?); you could have been prodding providers with "it doesn't work, fix it" for a while now.
- Matt
-- "For once, Microsoft wasn't exaggerating when they named it the 'Jet Engine' -- your data's the seagull." -- Chris Adams
I'll point out that there really isn't any alternative at this point. This approach will issue 16-bit compatible ASNs as long as they last. Once they're gone, it's not like there was some new 16-bit compatible alternative. Owen
On 2010/12/21 08:15, Matthew Palmer wrote:
That would be why 32-bit ASNs have been "requestable" for the last couple of years(?); you could have been prodding providers with "it doesn't work, fix it" for a while now.
- Matt
Although I realise that, the problem in South Africa is that we essentially still have a Telecoms Monopoly: The local loop belongs to Telkom SA who also competes with ISPs in providing Internet access to clients, so growth in the ISP sector is stunted. There are only really a handful of other NSPs who service ISPs and those ISPs still have no access to the networking segment from Datacenter to DSLAM. The major hope in .ZA is the unbundling of the local loop around 2012. Until then, there's no real end in sight (apart from mobile access, which is being stunted in many senses by the Communications Authority). ISPs just don't have that kind of prodding power in this country yet :( And the bad news is that I hear our incumbent Telecoms operator is expanding further up the continent, so that their legacy of incompetence may remain for a while. But we will continue pushing for these (legacy-)new technologies. :) One day we will prevail! :P -H.
On 12/21/2010 4:57 AM, Heinrich Strauss wrote:
Although I realise that, the problem in South Africa is that we essentially still have a Telecoms Monopoly: The local loop belongs to Telkom SA who also competes with ISPs in providing Internet access to clients, so growth in the ISP sector is stunted. There are only really a handful of other NSPs who service ISPs and those ISPs still have no access to the networking segment from Datacenter to DSLAM.
There was always similar issues in .ZW as well (when it was marginally more stable). Jack
participants (5)
-
bill manning -
Heinrich Strauss -
Jack Bates -
Matthew Palmer -
Owen DeLong