128.0.0.0/16 configured as martian: Please update your routers
[Apologies for duplicate emails] 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. We are exchanging the allocations that were already issued and for now we will (temporarily) stop using this specific /16. The RIPE NCC is working on this matter. For now, 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 Best regards, Ingrid Wijte Registration Services Assistant Manager RIPE NCC
On 13.10.2011 11:51, Ingrid Wijte wrote:
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.
We are exchanging the allocations that were already issued and for now we will (temporarily) stop using this specific /16.
The RIPE NCC is working on this matter. For now, 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
Keep in mind that martians settings are made per table in Junos, so if you have internet inside routing instance you may want to use this command under routing-instance since if you change those settings in inet.0 it won't affect other tables.
Ingrid, On Thu, 2011-10-13 at 09:51 +0200, Ingrid Wijte wrote:
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.
We are exchanging the allocations that were already issued and for now we will (temporarily) stop using this specific /16.
The RIPE NCC is working on this matter. For now, 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
Thanks for being proactive on this. I'm wondering though, does the RIPE NCC still do de-bogonizing? If so, did it simply miss this block? Or... ? Thanks, -- Shane
Hello, I inform you that all of juniper routers of FULLCOMPANY maintainer that communicate with Internet have been updated as you indicate. Best, Massimiliano Lalli ----- Original Message ----- From: "Ingrid Wijte" <ingrid@ripe.net> To: <routing-wg@ripe.net>; <ncc-announce@ripe.net> Sent: Thursday, October 13, 2011 9:51 AM Subject: [ncc-announce] 128.0.0.0/16 configured as martian: Please updateyour routers [Apologies for duplicate emails] 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. We are exchanging the allocations that were already issued and for now we will (temporarily) stop using this specific /16. The RIPE NCC is working on this matter. For now, 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 Best regards, Ingrid Wijte Registration Services Assistant Manager RIPE NCC Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks.
participants (4)
-
Ingrid Wijte
-
ripe-noc@telecomitalia.it
-
Shane Kerr
-
Tima Maryin