This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[address-policy-wg] 2014-03 Review Period extended until 19 May 2015 (Remove Multihoming Requirement for AS Number Assignments)
- Previous message (by thread): [address-policy-wg] 2014-03 Review Period extended until 19 May 2015 (Remove Multihoming Requirement for AS Number Assignments)
- Next message (by thread): [address-policy-wg] 2015-03 New Policy Proposal (Assessment Criteria for IPv6 Initial Allocation Size)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
David Huberman
David.Huberman at microsoft.com
Wed May 20 19:15:11 CEST 2015
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 at space.net] > Sent: Tuesday, May 19, 2015 11:45 AM > To: David Huberman > Cc: address-policy-wg at 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
- Previous message (by thread): [address-policy-wg] 2014-03 Review Period extended until 19 May 2015 (Remove Multihoming Requirement for AS Number Assignments)
- Next message (by thread): [address-policy-wg] 2015-03 New Policy Proposal (Assessment Criteria for IPv6 Initial Allocation Size)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]