Hi, The IANA IPv4 registry has been updated to reflect the allocation of two /8 IPv4 blocks to APNIC in January 2010: 1/8 and 27/8. You can find the IANA IPv4 registry at: http://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xml http://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xml http://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.txt Please update your filters as appropriate. The IANA free pool contains 24 unallocated unicast IPv4 /8s. Regards, Leo Vegoda Number Resources Manager, IANA ICANN
On 22/01/2010, at 12:36 PM, Leo Vegoda wrote:
Hi,
The IANA IPv4 registry has been updated to reflect the allocation of two /8 IPv4 blocks to APNIC in January 2010: 1/8 and 27/8. You can find the IANA IPv4 registry at:
1/8 is going to be interesting. I would like 1.2.3/24 please.
Nathan Ward wrote:
On 22/01/2010, at 12:36 PM, Leo Vegoda wrote:
Hi,
The IANA IPv4 registry has been updated to reflect the allocation of two /8 IPv4 blocks to APNIC in January 2010: 1/8 and 27/8. You can find the IANA IPv4 registry at:
1/8 is going to be interesting.
Interesting? It's going to be absolutely fantastically hilarious! But only for those of us who don't commonly talk with people whe end up assigned addresses in 1/15 and 1.2/16, and probably the rest of 1/8. Has APNIC done any reachability analysis on these prefixes yet? (advertising a /24 out of it and seeing how long it takes for various places on the Internet to see the prefix?)
On 22/01/2010, at 12:48 PM, Perry Lorier wrote:
Nathan Ward wrote:
On 22/01/2010, at 12:36 PM, Leo Vegoda wrote:
Hi,
The IANA IPv4 registry has been updated to reflect the allocation of two /8 IPv4 blocks to APNIC in January 2010: 1/8 and 27/8. You can find the IANA IPv4 registry at:
1/8 is going to be interesting.
Interesting? It's going to be absolutely fantastically hilarious! But only for those of us who don't commonly talk with people whe end up assigned addresses in 1/15 and 1.2/16, and probably the rest of 1/8.
Has APNIC done any reachability analysis on these prefixes yet? (advertising a /24 out of it and seeing how long it takes for various places on the Internet to see the prefix?)
Apparently Leo looked in to 1/8 a bit: http://www.cisco.com/web/about/ac123/ac147/archived_issues/ipj_10-3/103_awkw...
On 21 Jan 2010, at 3:54, Nathan Ward wrote: [...]
The IANA IPv4 registry has been updated to reflect the allocation of two /8 IPv4 blocks to APNIC in January 2010: 1/8 and 27/8. You can find the IANA IPv4 registry at:
1/8 is going to be interesting.
Interesting? It's going to be absolutely fantastically hilarious! But only for those of us who don't commonly talk with people whe end up assigned addresses in 1/15 and 1.2/16, and probably the rest of 1/8.
Has APNIC done any reachability analysis on these prefixes yet? (advertising a /24 out of it and seeing how long it takes for various places on the Internet to see the prefix?)
Apparently Leo looked in to 1/8 a bit: http://www.cisco.com/web/about/ac123/ac147/archived_issues/ipj_10-3/103_awkw...
That article was really meant to forewarn people that all the unallocated IPv4 address space is going to be allocated. The actual research ICANN sponsored was done by Duane Wessels, not me. He presented it at a DNS OARC meeting and details are available on the web site at: https://www.dns-oarc.net/files/dnsops-2008/Wessels-Unused-space.pdf Regards, Leo
On Fri, 2010-01-22 at 12:41 +1300, Nathan Ward wrote:
On 22/01/2010, at 12:36 PM, Leo Vegoda wrote:
Hi,
The IANA IPv4 registry has been updated to reflect the allocation of two /8 IPv4 blocks to APNIC in January 2010: 1/8 and 27/8. You can find the IANA IPv4 registry at:
1/8 is going to be interesting.
I would like 1.2.3/24 please.
This was my immediate reaction upon seeing the allocation notice as well 8^) AusNOG has been pretty busy with people worrying about those unfortunate souls using 1/8 internally, including apparently such highlights as McDonalds' free wi-fi across .au -- -Michael Fincham System Administrator, Unleash www.unleash.co.nz Phone: 0800 750 250 DDI: 03 978 1223 Mobile: 027 666 4482
On 22/01/2010, at 12:49 PM, Michael Fincham wrote:
On Fri, 2010-01-22 at 12:41 +1300, Nathan Ward wrote:
I would like 1.2.3/24 please.
This was my immediate reaction upon seeing the allocation notice as well 8^)
I'm very pleased I'm not the only one who thought this. JSR -- John S Russell Big Geek. Doing Geek Stuff.
On 22/01/2010, at 10:11 AM, Nathan Ward wrote:
On 22/01/2010, at 12:36 PM, Leo Vegoda wrote:
Hi,
The IANA IPv4 registry has been updated to reflect the allocation of two /8 IPv4 blocks to APNIC in January 2010: 1/8 and 27/8. You can find the IANA IPv4 registry at:
1/8 is going to be interesting.
I would like 1.2.3/24 please.
Setup some DNS on 1.1.1.1 and undermine the Google DNS conspiracy. :-) MMC
1/8 is going to be interesting.
I would like 1.2.3/24 please.
Setup some DNS on 1.1.1.1 and undermine the Google DNS conspiracy.
Presumably much traffic sent to 1.1.1.1 will end up hitting filters, more specifics, or just internal routing well before it hits your DNS servers, hence the problem. It would be interesting for someone to get allocated ranges containing 1.1.1.1 and 1.2.3.4 and do some scamper reachability analysis on these ranges (mjl?), and/or something similar to RIPE's debogon[1] project [1]: http://www.ris.ripe.net/debogon/
Presumably much traffic sent to 1.1.1.1 will end up hitting filters, more specifics, or just internal routing well before it hits your DNS servers, hence the problem. It would be interesting for someone to get allocated ranges containing 1.1.1.1 and 1.2.3.4 and do some scamper reachability analysis on these ranges (mjl?), and/or something similar to RIPE's debogon[1] project
http://tr.meta.net.nz/datexplore.php/2010-01-22_15:11_1.1.1.1?openas=,AS9901... As of today, this is what TR sees when tracerouting to 1.1.1.1 from various places around the Internet. The BGP feed I get given has a default route in it[1] which shows it inside TELSTRA-NZTRANSIT-AS, which is obviously wrong, don't blame them for my buggy tools :) Interestingly you can see that a couple of places manage to successfully reach 1.1.1.1 (!). [1]: I'm aware that these are easily filterable in cisco/juniper/whatever, however I'm using my own bgp collector I wrote by hand and haven't gotten to adding that feature yet.
participants (6)
-
John Russell -
Leo Vegoda -
Matthew Moyle-Croft -
Michael Fincham -
Nathan Ward -
Perry Lorier