OSPF Reverse Metric
draft-ketant-ospf-reverse-metric-00
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Ketan Talaulikar , Peter Psenak , Hugh Johnston | ||
| Last updated | 2018-09-02 (Latest revision 2018-03-01) | ||
| Replaced by | draft-ketant-lsr-ospf-reverse-metric | ||
| 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-ketant-lsr-ospf-reverse-metric | |
| 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
This document specifies the extensions to OSPF that enables a router to signal to its neighbor the metric that the neighbor should use towards itself using link-local advertisement between them. The signalling of this reverse metric, to be used on link(s) towards itself, allows a router to influence the amount of traffic flowing towards itself and in certain use-cases enables routers to maintain symmetric metric on both sides of a link between them.
Authors
Ketan Talaulikar
Peter Psenak
Hugh Johnston
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)