[147246] in North American Network Operators' Group
Re: 128.0.0.0/16 configured as martians in some routers
daemon@ATHENA.MIT.EDU (Joel jaeggli)
Tue Dec 6 11:05:21 2011
Date: Tue, 06 Dec 2011 08:04:01 -0800
From: Joel jaeggli <joelja@bogus.com>
To: Florian Weimer <fweimer@bfk.de>
In-Reply-To: <82zkf6t76h.fsf@mid.bfk.de>
Cc: Alex Le Heux <alexlh@ripe.net>, nanog@nanog.org
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
On 12/6/11 00:50 , Florian Weimer wrote:
> * Alex Le Heux:
>
>> 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.
>
> Would someone please clarify the impact? Will it result in a blackhole,
> or will the entire announcement be suppressed? I suspect the latter,
> given what we see and what Chris Adams has reported.
http://www.juniper.net/techpubs/en_US/junos10.2/topics/usage-guidelines/routing-configuring-martian-addresses.html
