H-bit Support for OSPFv2
draft-keyupate-ospf-ospfv2-hbit-01
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Keyur Patel , Padma Pillay-Esnault , Manish Bhardwaj , Serpil Bayraktar | ||
| Last updated | 2019-09-19 (Latest revision 2015-05-21) | ||
| Replaces | draft-pillay-esnault-ospf-rbit | ||
| Replaced by | RFC 8770 | ||
| 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-ospfv2-hbit | |
| 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 [RFC5340] defines an option field for router-LSAs known as a R-bit. 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.)