Re: [address-policy-wg] 2014-03 Review Period extended until 19 May 2015 (Remove Multihoming Requirement for AS Number Assignments)
Some data from the ARIN region, courtesy of Richard Jimmerson of ARIN: For the last several years ARIN has been registering AS numbers by issuing the lowest AS number we have in inventory to approved organizations. We ask those organizations if they would be willing to accept an AS number higher in the number range, and outside of the range that previously made up the 2-byte only AS number space. In 2014 we found that nearly 27% of the organizations approved for an AS number elected to receive a 4-byte AS number rather than take the lowest AS number in our inventory. Several organizations unwilling to receive a 4-byte AS number have indicated to ARIN that their transit providers strongly state a preference that their customers use AS numbers from the traditional 2-byte AS number range. More recently, because of a lack of 2-byte AS numbers in the ARIN inventory, the AS number assignments we make are 4-byte AS numbers and outside of the range that previously made up the 2-byte only AS number space. For those organizations who come back to ARIN specifically stating a preference for a 2-byte AS number, we may be able to continue satisfying their requests using AS numbers that have recently been added to the ARIN AS number inventory through returns or revocations. Very recently ARIN received a new assignment of AS numbers from the IANA. Roughly 90 of those were from the 2-byte range. In 2014 there were 12 organizations that elected to receive a 4-byte AS number and later came back to ARIN to exchange it for a 2-byte AS number. Each of these organizations stated issues with their transit providers either unwilling or unable to accept the use of a 4-byte AS number by a customer. 2014 total AS numbers issued: 1,579 2014 4-byte AS numbers issued: 416 2014 2-byte AS numbers issued: 1,163 David R Huberman Principal, Global IP Addressing Microsoft Corporation
On Tue, May 19, 2015 at 6:32 PM, David Huberman < David.Huberman@microsoft.com> wrote:
In 2014 there were 12 organizations that elected to receive a 4-byte AS number and later came back to ARIN to exchange it for a 2-byte AS number. Each of these organizations stated issues with their transit providers either unwilling or unable to accept the use of a 4-byte AS number by a customer.
It's seems as if the transit providers are mentioned a bit too frequently here. Does anyone have any information about how long it would take to get transit providers 4-byte-ready? -- Jan
On Tue, May 19, 2015 at 06:55:54PM +0200, Jan Ingvoldstad wrote:
It's seems as if the transit providers are mentioned a bit too frequently here.
Does anyone have any information about how long it would take to get transit providers 4-byte-ready?
AFAIK, it's not so much a problem with the providers but with vendor support for 4-byte communities. rgds, Sascha Luck
Hi, On Tue, May 19, 2015 at 04:32:42PM +0000, David Huberman wrote:
Each of these organizations stated issues with their transit providers either unwilling or unable to accept the use of a 4-byte AS number by a customer.
I can see that transit providers might not be able to use 4-byte AS for their own network (because communities in <AS>:<action> notation just do not work then), but transit providers refusing customers with 4-byte ASNs in, what, 2014, is so totally lame... Thanks, David, for the update, though! Gert Doering -- proud holder of AS3.3 (AS196611 nowadays, far less pretty) -- have you enabled IPv6 on something today...? SpaceNet AG Vorstand: Sebastian v. Bomhard Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann D-80807 Muenchen HRB: 136055 (AG Muenchen) Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279
Per ARIN's statistics, there were 416 4-byte ASNs issued in CY2014. 12 were returned to ARIN as non-useable. That means that here, on May 20 2015, we should see most of the 404 4-byte ASNs registered in some copy of the DFZ. So let's see! Methodology: - I downloaded 'delegated-arin-extended-latest', today's extended file - I found exactly 421 4-byte ASNs with a registration date in 2014. - I hopped on a Microsoft router and did: show route advertising-protocol bgp [our IP address] aspath-regex ".*(65536-4294967295).*" Interestingly, we found 39,293 prefixes announced or transiting 4-byte ASNs. That's a lot more than expected. - I then looked for all 421 registered 4-byte ASNs from CY2014 in the routing table. Results: 289 4-byte ASNs were found in my company's copy of the DFZ (69%) 132 4-byte ASNs were NOT found (31%) David R Huberman Principal, Global IP Addressing Microsoft Corporation
-----Original Message----- From: Gert Doering [mailto:gert@space.net] Sent: Tuesday, May 19, 2015 11:45 AM To: David Huberman Cc: address-policy-wg@ripe.net Subject: Re: [address-policy-wg] 2014-03 Review Period extended until 19 May 2015 (Remove Multihoming Requirement for AS Number Assignments)
Hi,
On Tue, May 19, 2015 at 04:32:42PM +0000, David Huberman wrote:
Each of these organizations stated issues with their transit providers either unwilling or unable to accept the use of a 4-byte AS number by a customer.
I can see that transit providers might not be able to use 4-byte AS for their own network (because communities in <AS>:<action> notation just do not work then), but transit providers refusing customers with 4-byte ASNs in, what, 2014, is so totally lame...
Thanks, David, for the update, though!
Gert Doering -- proud holder of AS3.3 (AS196611 nowadays, far less pretty) -- have you enabled IPv6 on something today...?
SpaceNet AG Vorstand: Sebastian v. Bomhard Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann D-80807 Muenchen HRB: 136055 (AG Muenchen) Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279
participants (4)
-
David Huberman -
Gert Doering -
Jan Ingvoldstad -
Sascha Luck [ml]