Skip to main content

Hiding Transit-Only Networks in OSPF
RFC 6860

Revision differences

Document history

Date By Action
2022-08-12
Alvaro Retana This document now replaces draft-yang-ospf-hiding instead of None
2020-01-21
(System) Received changes through RFC Editor sync (added Verified Errata tag)
2018-12-20
(System)
Received changes through RFC Editor sync (changed abstract to 'A transit-only network is defined as a network connecting routers only. In OSPF, transit-only networks are …
Received changes through RFC Editor sync (changed abstract to 'A transit-only network is defined as a network connecting routers only. In OSPF, transit-only networks are usually configured with routable IP addresses, which are advertised in Link State Advertisements (LSAs) but are not needed for data traffic. In addition, remote attacks can be launched against routers by sending packets to these transit-only networks. This document presents a mechanism to hide transit-only networks to speed up network convergence and reduce vulnerability to remote attacks.

In the context of this document, 'hiding' implies that the prefixes are not installed in the routing tables on OSPF routers. In some cases, IP addresses may still be visible when using OSPFv2.

This document updates RFCs 2328 and 5340. [STANDARDS-TRACK]')
2016-11-30
(System) Closed request for Telechat review by GENART with state 'Unknown'
2015-10-14
(System) Notify list changed from ospf-chairs@ietf.org, draft-ietf-ospf-prefix-hiding@ietf.org to (None)
2013-01-18
(System) RFC published