Hiding Transit-only Networks in OSPF
draft-yang-ospf-hiding-01
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Yi Yang , Alvaro Retana , Abhay Roy | ||
| Last updated | 2011-05-23 | ||
| Replaced by | draft-ietf-ospf-prefix-hiding | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-ospf-prefix-hiding | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
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 LSAs but 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 minimize remote attack vulnerability.
Authors
Yi Yang
Alvaro Retana
Abhay Roy
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)