[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

128.0.0.0/16 configured as martians in some routers

Subject: 128.0.0.0/16 configured as martians in some routers
From: fweimer at bfk.de (Florian Weimer)
Date: Tue, 06 Dec 2011 08:50:46 +0000
In-reply-to: <[email protected]> (Alex Le Heux's message of "Mon, 5 Dec 2011 16:20:27 +0100")
References: <[email protected]>

* 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.

-- 
Florian Weimer                <fweimer at bfk.de>
BFK edv-consulting GmbH       http://www.bfk.de/
Kriegsstra?e 100              tel: +49-721-96201-1
D-76133 Karlsruhe             fax: +49-721-96201-99

Follow-Ups:
- 128.0.0.0/16 configured as martians in some routers
  - From: mtinka at globaltransit.net (Mark Tinka)
- 128.0.0.0/16 configured as martians in some routers
  - From: joelja at bogus.com (Joel jaeggli)

References:
- 128.0.0.0/16 configured as martians in some routers
  - From: alexlh at ripe.net (Alex Le Heux)

Prev by Date: On Working Remotely
Next by Date: 128.0.0.0/16 configured as martians in some routers
Previous by thread: [ncc-announce] 128.0.0.0/16 configured as martians in some routers
Next by thread: 128.0.0.0/16 configured as martians in some routers
Index(es):
- Date
- Thread