[118011] in North American Network Operators' Group
Re: 109/8 - not a BOGON
daemon@ATHENA.MIT.EDU (Leo Vegoda)
Fri Oct 9 08:09:27 2009
From: Leo Vegoda <leo.vegoda@icann.org>
To: Matthew Walster <matthew@walster.org>, "nanog@nanog.org" <nanog@nanog.org>
Date: Fri, 9 Oct 2009 05:08:35 -0700
In-Reply-To: <c2af1d7d0910090422i6a1cdb17q305406457ee0ecd7@mail.gmail.com>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
On 09/10/2009 4:22, "Matthew Walster" <matthew@walster.org> wrote:
> A customer of mine is reporting that there are a large number of addresse=
s
> he can not reach with his addresses in the 109/8 range. This was
> declassified as a BOGON and assigned by IANA to RIPE in January 2009.
>=20
> If you have a manually updated BOGON list, can I please ask that you revi=
ew
> it and update it as soon as possible please? His addresses in 89/8 and 83=
/8
> work just fine, hence this presumption of BOGON filtering.
This might be a good moment to list all the /8s allocated so far this year.
046/8 RIPE NCC 2009-09 whois.ripe.net ALLOCATED
002/8 RIPE NCC 2009-09 whois.ripe.net ALLOCATED
182/8 APNIC 2009-08 whois.apnic.net ALLOCATED
175/8 APNIC 2009-08 whois.apnic.net ALLOCATED
183/8 APNIC 2009-04 whois.apnic.net ALLOCATED
180/8 APNIC 2009-04 whois.apnic.net ALLOCATED
178/8 RIPE NCC 2009-01 whois.ripe.net ALLOCATED
109/8 RIPE NCC 2009-01 whois.ripe.net ALLOCATED
Also, I'd like to mention that if you ever want to check your filters
against the registry, we have made the columns sortable. It's now nice and
easy to identify newly allocated /8s.
http://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xml
Regards,
Leo Vegoda
