[147338] in North American Network Operators' Group
[ncc-announce] 128.0.0.0/16 configured as martians in some routers
daemon@ATHENA.MIT.EDU (Alex Le Heux)
Wed Dec 7 11:12:04 2011
From: Alex Le Heux <alexlh@ripe.net>
Date: Mon, 5 Dec 2011 16:20:27 +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>, SANOG List <sanog@sanog.org>,
ncc-announce@ripe.net,
Address Policy Working Group <address-policy-wg@ripe.net>,
AfNOG List <afnog@afnog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
Dear Colleagues,
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.
All allocations that were already issued have been exchanged and for now =
we will hold this space in quarantine.
We urge everyone to change the default behaviour of their Juniper =
routers:
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
128.0.0.0/16 has been added to the RIPE NCC's Debogonising Project:
http://www.ris.ripe.net/debogon/
To facilitate testing, the following prefixes are being announced:
prefix pinagble address
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
Best regards,
Alex Le Heux
Policy Implementation Co-ordinator
RIPE NCC=
