[147238] in North American Network Operators' Group
Re: 128.0.0.0/16 configured as martians in some routers
daemon@ATHENA.MIT.EDU (Florian Weimer)
Tue Dec 6 03:51:54 2011
From: Florian Weimer <fweimer@bfk.de>
To: Alex Le Heux <alexlh@ripe.net>
Date: Tue, 06 Dec 2011 08:50:46 +0000
In-Reply-To: <2DDABC15-3D2A-4044-B65D-A83FFB9E145F@ripe.net> (Alex Le Heux's
message of "Mon, 5 Dec 2011 16:20:27 +0100")
Cc: nanog@nanog.org
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
* 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.
--=20
Florian Weimer <fweimer@bfk.de>
BFK edv-consulting GmbH http://www.bfk.de/
Kriegsstra=DFe 100 tel: +49-721-96201-1
D-76133 Karlsruhe fax: +49-721-96201-99
