draft-ietf-lsr-ospf-reverse-metric-00.txt   draft-ietf-lsr-ospf-reverse-metric-01.txt 
Link State Routing K. Talaulikar Link State Routing K. Talaulikar
Internet-Draft P. Psenak Internet-Draft P. Psenak
Intended status: Standards Track Cisco Systems, Inc. Intended status: Standards Track Cisco Systems, Inc.
Expires: July 9, 2020 H. Johnston Expires: December 31, 2020 H. Johnston
AT&T Labs AT&T Labs
January 6, 2020 June 29, 2020
OSPF Reverse Metric OSPF Reverse Metric
draft-ietf-lsr-ospf-reverse-metric-00 draft-ietf-lsr-ospf-reverse-metric-01
Abstract Abstract
This document specifies the extensions to OSPF that enables a router This document specifies the extensions to OSPF that enables a router
to signal to its neighbor the metric that the neighbor should use to signal to its neighbor the metric that the neighbor should use
towards itself using link-local advertisement between them. The towards itself using link-local advertisement between them. The
signalling of this reverse metric, to be used on link(s) towards signalling of this reverse metric, to be used on link(s) towards
itself, allows a router to influence the amount of traffic flowing itself, allows a router to influence the amount of traffic flowing
towards itself and in certain use-cases enables routers to maintain towards itself and in certain use-cases enables routers to maintain
symmetric metric on both sides of a link between them. symmetric metric on both sides of a link between them.
Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP
14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on July 9, 2020. This Internet-Draft will expire on December 31, 2020.
Copyright Notice Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the Copyright (c) 2020 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3
2. Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.1. Symmetrical Metric Based on Reference Bandwidth . . . . . 3 2.1. Symmetrical Metric Based on Reference Bandwidth . . . . . 3
2.2. Adaptive Metric Signaling . . . . . . . . . . . . . . . . 4 2.2. Adaptive Metric Signaling . . . . . . . . . . . . . . . . 4
3. Solution . . . . . . . . . . . . . . . . . . . . . . . . . . 5 3. Solution . . . . . . . . . . . . . . . . . . . . . . . . . . 5
4. LLS Reverse Metric TLV . . . . . . . . . . . . . . . . . . . 6 4. LLS Reverse Metric TLV . . . . . . . . . . . . . . . . . . . 6
5. LLS Reverse TE Metric TLV . . . . . . . . . . . . . . . . . . 6 5. LLS Reverse TE Metric TLV . . . . . . . . . . . . . . . . . . 6
6. Procedures . . . . . . . . . . . . . . . . . . . . . . . . . 7 6. Procedures . . . . . . . . . . . . . . . . . . . . . . . . . 7
7. Backward Compatibility . . . . . . . . . . . . . . . . . . . 9 7. Backward Compatibility . . . . . . . . . . . . . . . . . . . 9
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
9. Security Considerations . . . . . . . . . . . . . . . . . . . 9 9. Security Considerations . . . . . . . . . . . . . . . . . . . 9
skipping to change at page 3, line 22 skipping to change at page 3, line 13
using this value which results in the desired change in traffic using this value which results in the desired change in traffic
distribution that R1 wanted to achieve towards itself over the link distribution that R1 wanted to achieve towards itself over the link
from R2. from R2.
This document proposes an extension to OSPF link-local signaling This document proposes an extension to OSPF link-local signaling
(LLS) [RFC5613] for signalling the OSPF reverse metric using the LLS (LLS) [RFC5613] for signalling the OSPF reverse metric using the LLS
Reverse Metric TLV in Section 4, the reverse Traffic Engineering (TE) Reverse Metric TLV in Section 4, the reverse Traffic Engineering (TE)
metric [RFC3630] using the LLS Reverse TE Metric TLV in Section 5 and metric [RFC3630] using the LLS Reverse TE Metric TLV in Section 5 and
describes the related procedures in section Section 6. describes the related procedures in section Section 6.
1.1. Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP
14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here.
2. Use Cases 2. Use Cases
This section describes certain use-cases that OSPF reverse metric This section describes certain use-cases that OSPF reverse metric
helps to address. The usage of OSPF reverse metric need not be helps to address. The usage of OSPF reverse metric need not be
limited to these cases and is intended to be a generic mechanism. limited to these cases and is intended to be a generic mechanism.
2.1. Symmetrical Metric Based on Reference Bandwidth 2.1. Symmetrical Metric Based on Reference Bandwidth
Certain OSPF implementations and deployments deduce the metric of Certain OSPF implementations and deployments deduce the metric of
links based on their bandwidth using a reference bandwidth. The OSPF links based on their bandwidth using a reference bandwidth. The OSPF
 End of changes. 7 change blocks. 
12 lines changed or deleted 13 lines changed or added

This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/