IS-IS Routing with Reverse Metric
RFC 8500
Revision differences
Document history
| Date | By | Action |
|---|---|---|
|
2019-08-19
|
Gunter Van de Velde | Assignment of request for Last Call review by OPSDIR to Tina Tsou was marked no-response |
|
2019-06-04
|
Alvaro Retana | Downref to RFC 5443 approved by Last Call for draft-ietf-isis-reverse-metric-17 |
|
2019-03-01
|
(System) | IANA registries were updated to include RFC8500 |
|
2019-02-28
|
(System) | Received changes through RFC Editor sync (created alias RFC 8500, changed abstract to 'This document describes a mechanism to allow IS-IS routing to quickly … Received changes through RFC Editor sync (created alias RFC 8500, changed abstract to 'This document describes a mechanism to allow IS-IS routing to quickly and accurately shift traffic away from either a point-to-point or multi-access LAN interface during network maintenance or other operational events. This is accomplished by signaling adjacent IS-IS neighbors with a higher reverse metric, i.e., the metric towards the signaling IS-IS router.', changed standardization level to Proposed Standard, changed state to RFC, added RFC published event at 2019-02-28, changed IESG state to RFC Published) |
|
2019-02-28
|
(System) | RFC published |