BGP Extension for SR-MPLS Entropy Label Position
draft-zhou-idr-bgp-srmpls-elp-02
|
Document |
Type |
|
Active Internet-Draft (individual)
|
|
Authors |
|
Liu Yao
,
Shaofu Peng
|
|
Last updated |
|
2021-02-22
|
|
Stream |
|
(None)
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
xml
pdf
htmlized (tools)
htmlized
bibtex
|
Stream |
Stream state |
|
(No stream defined) |
|
Consensus Boilerplate |
|
Unknown
|
|
RFC Editor Note |
|
(None)
|
IESG |
IESG state |
|
I-D Exists
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
IDR Working Group Yao. Liu
Internet-Draft Shaofu. Peng
Intended status: Standards Track ZTE Corp.
Expires: August 26, 2021 February 22, 2021
BGP Extension for SR-MPLS Entropy Label Position
draft-zhou-idr-bgp-srmpls-elp-02
Abstract
This document proposes extensions for BGP to indicate the entropy
label position in the SR-MPLS label stack when distributing SR Policy
candidate paths.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on August 26, 2021.
Copyright Notice
Copyright (c) 2021 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Liu & Peng Expires August 26, 2021 [Page 1]
Internet-Draft BGP Extension for ELP February 2021
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Conventions used in this document . . . . . . . . . . . . . . 3
2.1. Requirements Language . . . . . . . . . . . . . . . . . . 3
2.2. Terminology and Acronyms . . . . . . . . . . . . . . . . 3
3. Entropy Labels in SR-MPLS Scenario with a Controller . . . . 3
4. BGP Extensions . . . . . . . . . . . . . . . . . . . . . . . 4
5. Operations . . . . . . . . . . . . . . . . . . . . . . . . . 5
6. Security Considerations . . . . . . . . . . . . . . . . . . . 5
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 5
8.1. Normative References . . . . . . . . . . . . . . . . . . 5
8.2. Informative References . . . . . . . . . . . . . . . . . 6
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 7
1. Introduction
Segment Routing (SR) leverages the source routing paradigm. Segment
Routing can be instantiated on MPLS data plane which is referred to
as SR-MPLS [RFC8660]. SR-MPLS leverages the MPLS label stack to
construct the SR path.
Entropy labels (ELs) [RFC6790] are used in the MPLS data plane to
provide entropy for load-balancing. The idea behind the entropy
label is that the ingress router computes a hash based on several
fields from a given packet and places the result in an additional
label named "entropy label". Then, this entropy label can be used as
part of the hash keys used by an LSR. Using the entropy label as
part of the hash keys reduces the need for deep packet inspection in
the LSR while keeping a good level of entropy in the load-balancing.
[RFC8662] proposes to use entropy labels for SR-MPLS networks and
mutiple < ELI, EL> pairs may be inserted in the SR-MPLS label stack.
The ingress node may decide the number and position of the ELI/ELs
which need to be inserted into the label stack, that is termed as ELP
(Entropy Label Position). In some cases, centralized controllers are
used to perform the TE path computation for intra or inter-domain
scenarios, thus it is also the responsibility of the controller to
calculate ELP and inform it to the headend of the SR-TE path.
[I-D.ietf-idr-segment-routing-te-policy] defines the specific process
of how the controller/PCE in the SR network passes the path
calculation result of the SR-TE policy to the headend of the network
through BGP.
Liu & Peng Expires August 26, 2021 [Page 2]
Internet-Draft BGP Extension for ELP February 2021
This document proposes extensions for BGP to indicate the ELP in the
segment list when distribute SR Policy candidate paths using BGP for
Show full document text