[147202] in North American Network Operators' Group
Re: 128.0.0.0/16 configured as martians in some routers
daemon@ATHENA.MIT.EDU (Alex Le Heux)
Mon Dec 5 12:44:52 2011
In-Reply-To: <2DDABC15-3D2A-4044-B65D-A83FFB9E145F@ripe.net>
From: Alex Le Heux <alexlh@ripe.net>
Date: Mon, 5 Dec 2011 16:48:39 +0100
To: Routing WG <routing-wg@ripe.net>
Cc: lacnog@lacnic.net, PacNOG List <pacnog@pacnog.org>, nanog@nanog.org,
menog@menog.net, UKNOF List <uknof@uknof.org.uk>, AfNOG List <afnog@afnog.org>,
ncc-announce@ripe.net,
Address Policy Working Group <address-policy-wg@ripe.net>,
SANOG List <sanog@sanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
Dear Colleagues,
The correct prefix and pingable address list for the Debogonising =
Project is:
prefix pinagble address
128.0.0.0/21 128.0.0.1
128.0.24.0/24 128.0.24.1
Our apologies for the oversight.
Best regards,
Alex Le Heux
Policy Implementation Co-ordinator
RIPE NCC
On Dec 5, 2011, at 16:20, Alex Le Heux wrote:
> Dear Colleagues,
>=20
> The RIPE NCC is aware that 128.0.0.0/16 is configured as a martian by =
default in (some) Juniper OS, even though RFC 5735 and RFC3330 outline =
that this /16 should no longer be reserved as specialised address space.
>=20
> All allocations that were already issued have been exchanged and for =
now we will hold this space in quarantine.
>=20
> We urge everyone to change the default behaviour of their Juniper =
routers:
>=20
> set routing-options martians 128.0.0.0/16 orlonger allow
> set routing-options martians 191.255.0.0/16 orlonger allow
> set routing-options martians 223.255.255.0/24 exact allow
>=20
> 128.0.0.0/16 has been added to the RIPE NCC's Debogonising Project:
>=20
> http://www.ris.ripe.net/debogon/
>=20
> To facilitate testing, the following prefixes are being announced:
>=20
> prefix pinagble address
>=20
> 128.0.0.0/16 128.0.0.1
> 128.0.8.0/21 128.0.8.1
> 128.0.24.0/24 128.0.24.1
>=20
> Best regards,
>=20
> Alex Le Heux
> Policy Implementation Co-ordinator
> RIPE NCC
