draft-ietf-ospf-mpls-elc-11.txt   draft-ietf-ospf-mpls-elc-12.txt 
OSPF Working Group X. Xu OSPF Working Group X. Xu
Internet-Draft Alibaba Inc Internet-Draft Alibaba Inc
Intended status: Standards Track S. Kini Intended status: Standards Track S. Kini
Expires: April 23, 2020 Expires: April 27, 2020
P. Psenak P. Psenak
C. Filsfils C. Filsfils
S. Litkowski S. Litkowski
Cisco Systems, Inc. Cisco Systems, Inc.
M. Bocci M. Bocci
Nokia Nokia
October 21, 2019 October 25, 2019
Signaling Entropy Label Capability and Entropy Readable Label-stack Signaling Entropy Label Capability and Entropy Readable Label-stack
Depth Using OSPF Depth Using OSPF
draft-ietf-ospf-mpls-elc-11 draft-ietf-ospf-mpls-elc-12
Abstract Abstract
Multiprotocol Label Switching (MPLS) has defined a mechanism to load- Multiprotocol Label Switching (MPLS) has defined a mechanism to load-
balance traffic flows using Entropy Labels (EL). An ingress Label balance traffic flows using Entropy Labels (EL). An ingress Label
Switching Router (LSR) cannot insert ELs for packets going into a Switching Router (LSR) cannot insert ELs for packets going into a
given tunnel unless an egress LSR has indicated via signaling that it given tunnel unless an egress LSR has indicated via signaling that it
has the capability to process ELs, referred to as Entropy Label has the capability to process ELs, referred to as Entropy Label
Capability (ELC), on that tunnel. In addition, it would be useful Capability (ELC), on that tunnel. In addition, it would be useful
for ingress LSRs to know each LSR's capability of reading the maximum for ingress LSRs to know each LSR's capability of reading the maximum
label stack depth and performing EL-based load-balancing, referred to label stack depth and performing EL-based load-balancing, referred to
as Entropy Readable Label Depth (ERLD). This document defines a as Entropy Readable Label Depth (ERLD). This document defines a
mechanism to signal these two capabilities using OSPF and OSPFv3. mechanism to signal these two capabilities using OSPF and OSPFv3.
These mechanism is particularly useful in the environment where These mechanism is particularly useful in the environment where
Segment Routing (SR) is used, where label advertisements are done via Segment Routing (SR) is used, where label advertisements are done via
protocols like OSPF and OSPFv3. protocols like OSPF and OSPFv3.
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
[BCP14] [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 April 27, 2020.
This Internet-Draft will expire on April 23, 2020.
Copyright Notice Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2019 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
skipping to change at page 3, line 28 skipping to change at page 3, line 21
[I-D.ietf-mpls-spring-entropy-label] may be used by ingress LSRs to [I-D.ietf-mpls-spring-entropy-label] may be used by ingress LSRs to
determine the position of the EL label in the stack, and whether it's determine the position of the EL label in the stack, and whether it's
necessary to insert multiple ELs at different positions in the label necessary to insert multiple ELs at different positions in the label
stack. stack.
2. Terminology 2. Terminology
This document makes use of the terms defined in [RFC6790], [RFC7770] This document makes use of the terms defined in [RFC6790], [RFC7770]
and [I-D.ietf-mpls-spring-entropy-label]. and [I-D.ietf-mpls-spring-entropy-label].
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
[BCP14] [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here.
3. Advertising ELC Using OSPF 3. Advertising ELC Using OSPF
Even though ELC is a property of the node, in some cases it is Even though ELC is a property of the node, in some cases it is
advantageous to associate and advertise the ELC with the prefix. In advantageous to associate and advertise the ELC with the prefix. In
multi-area networks, routers may not know the identity of the prefix multi-area networks, routers may not know the identity of the prefix
originator in a remote area, or may not know the capabilities of such originator in a remote area, or may not know the capabilities of such
originator. Similarly, in a multi domain network, the identity of originator. Similarly, in a multi domain network, the identity of
the prefix originator and its capabilities may not be known to the the prefix originator and its capabilities may not be known to the
ingress LSR. ingress LSR.
skipping to change at page 6, line 44 skipping to change at page 6, line 44
(work in progress), June 2019. (work in progress), June 2019.
[I-D.ietf-idr-bgp-ls-segment-routing-msd] [I-D.ietf-idr-bgp-ls-segment-routing-msd]
Tantsura, J., Chunduri, U., Talaulikar, K., Mirsky, G., Tantsura, J., Chunduri, U., Talaulikar, K., Mirsky, G.,
and N. Triantafillis, "Signaling MSD (Maximum SID Depth) and N. Triantafillis, "Signaling MSD (Maximum SID Depth)
using Border Gateway Protocol Link-State", draft-ietf-idr- using Border Gateway Protocol Link-State", draft-ietf-idr-
bgp-ls-segment-routing-msd-09 (work in progress), October bgp-ls-segment-routing-msd-09 (work in progress), October
2019. 2019.
[I-D.ietf-isis-mpls-elc] [I-D.ietf-isis-mpls-elc]
Xu, X., Kini, S., Psenak, P., Filsfils, C., and S. Xu, X., Kini, S., Psenak, P., Filsfils, C., Litkowski, S.,
Litkowski, "Signaling Entropy Label Capability and Entropy and M. Bocci, "Signaling Entropy Label Capability and
Readable Label Depth Using IS-IS", draft-ietf-isis-mpls- Entropy Readable Label Depth Using IS-IS", draft-ietf-
elc-09 (work in progress), October 2019. isis-mpls-elc-10 (work in progress), October 2019.
[I-D.ietf-mpls-spring-entropy-label] [I-D.ietf-mpls-spring-entropy-label]
Kini, S., Kompella, K., Sivabalan, S., Litkowski, S., Kini, S., Kompella, K., Sivabalan, S., Litkowski, S.,
Shakir, R., and J. Tantsura, "Entropy label for SPRING Shakir, R., and J. Tantsura, "Entropy label for SPRING
tunnels", draft-ietf-mpls-spring-entropy-label-12 (work in tunnels", draft-ietf-mpls-spring-entropy-label-12 (work in
progress), July 2018. progress), July 2018.
[I-D.ietf-spring-segment-routing-mpls] [I-D.ietf-spring-segment-routing-mpls]
Bashandy, A., Filsfils, C., Previdi, S., Decraene, B., Bashandy, A., Filsfils, C., Previdi, S., Decraene, B.,
Litkowski, S., and R. Shakir, "Segment Routing with MPLS Litkowski, S., and R. Shakir, "Segment Routing with MPLS
 End of changes. 7 change blocks. 
17 lines changed or deleted 14 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/