[147336] in North American Network Operators' Group
Re: 128.0.0.0/16 configured as martians in some routers
daemon@ATHENA.MIT.EDU (David Swafford)
Wed Dec 7 11:11:39 2011
In-Reply-To: <2DDABC15-3D2A-4044-B65D-A83FFB9E145F@ripe.net>
Date: Tue, 6 Dec 2011 06:16:10 -0500
From: David Swafford <david@davidswafford.com>
To: Alex Le Heux <alexlh@ripe.net>
Cc: lacnog@lacnic.net, PacNOG List <pacnog@pacnog.org>, nanog@nanog.org,
Routing WG <routing-wg@ripe.net>, 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
Hi Alex,
In Dayton, Ohio, US, we are not seeing any 128... routes from TWTC (AS 4323=
).
In St. Louis, Ohio, US, we are seeing the 128.0.0.0/21 via Level 3 (AS 3356=
).
David Swafford,
Sr. Network Engineer, CareSource
On Mon, Dec 5, 2011 at 10:20 AM, Alex Le Heux <alexlh@ripe.net> wrote:
> Dear Colleagues,
>
> The RIPE NCC is aware that 128.0.0.0/16 is configured as a martian by def=
ault in (some) Juniper OS, even though RFC 5735 and RFC3330 outline that th=
is /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 =A0pinagble address
>
> 128.0.0.0/16 =A0 =A0128.0.0.1
> 128.0.8.0/21 =A0 =A0128.0.8.1
> 128.0.24.0/24 =A0 128.0.24.1
>
> Best regards,
>
> Alex Le Heux
> Policy Implementation Co-ordinator
> RIPE NCC
