[111679] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

New IPv4 blocks allocated to RIPE NCC

daemon@ATHENA.MIT.EDU (Alex Le Heux)
Tue Feb 10 11:07:45 2009

From: Alex Le Heux <alexlh@ripe.net>
To: Address Policy WG <address-policy-wg@ripe.net>,
	Routing WG <routing-wg@ripe.net>, NANOG <nanog@merit.edu>,
	SANOG List <sanog@sanog.org>, uknof@lists.uknof.org.uk
Date: Tue, 10 Feb 2009 17:07:27 +0100
Errors-To: nanog-bounces@nanog.org

[Apologies for duplicate mails]

Dear Colleagues,

The RIPE NCC received the IPv4 address ranges 109/8 and 178/8 from the
IANA in January 2009. We will begin allocating from these ranges in the
near future.

The minimum allocation size from these two /8s has been set at /21.

You may wish to adjust any filters you have in place accordingly.

More information on the IP space administered by the RIPE NCC
can be found at:

https://www.ripe.net/ripe/docs/ripe-ncc-managed-address-space.html

Please also note that several "pilot" prefixes are being announced from
each /8. These prefixes are:

178.0.0.0/16, pingable 178.0.0.1
178.1.0.0/21, pingable 178.1.0.1
178.1.24.0/24, pingable 178.1.24.1
109.0.0.0/16, pingable 109.0.0.1
109.1.0.0/21, pingable 109.1.0.1
109.1.24.0/24, pingable 109.1.24.1

They all originate in AS12654.

More information on this "pilot" activity is available in the
document "De-Bogonising New Address Blocks", which can be found at:

http://www.ripe.net/ripe/docs/ripe-351.html

Best regards,

Alex Le Heux
RIPE NCC
Policy Implementation Co-ordinator

home help back first fref pref prev next nref lref last post