H-bit Support for OSPFv2
draft-ietf-ospf-ospfv2-hbit-00
| Document | Type |
This is an older version of an Internet-Draft that was ultimately published as RFC 8770.
Expired & archived
|
|
|---|---|---|---|
| Authors | Keyur Patel , Padma Pillay-Esnault , Manish Bhardwaj , Serpil Bayraktar | ||
| Last updated | 2016-04-20 (Latest revision 2015-10-18) | ||
| Replaces | draft-keyupate-ospf-ospfv2-hbit | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Formats | |||
| Reviews |
TSVART Last Call review
(of
-10)
by Kyle Rose
Ready with Nits
|
||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| 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
OSPFv3 defines an option field for router-LSAs known as a R-bit in RFC5340. If the R-bit is clear, an OSPFv3 router can participate in OSPF topology distribution without acting as a forwarder to forward the transit traffic. In such cases, an OSPF router would only accept traffic intended for local delivery. This draft defines R-bit functionality for OSPFv2 defined in RFC2328.
Authors
Keyur Patel
Padma Pillay-Esnault
Manish Bhardwaj
Serpil Bayraktar
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)