PCE Controlled ID Space
draft-li-pce-controlled-id-space-06
|
| Document |
Type |
|
Active Internet-Draft (individual)
|
|
Last updated |
|
2020-07-06
|
|
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)
|
Network Working Group C. Li
Internet-Draft M. Chen
Intended status: Experimental Huawei Technologies
Expires: January 7, 2021 A. Wang
China Telecom
W. Cheng
China Mobile
C. Zhou
Cisco System
July 6, 2020
PCE Controlled ID Space
draft-li-pce-controlled-id-space-06
Abstract
The Path Computation Element Communication Protocol (PCEP) provides
mechanisms for Path Computation Elements (PCEs) to perform path
computations in response to Path Computation Clients (PCCs) requests.
The Stateful PCE extensions allow stateful control of Multiprotocol
Label Switching (MPLS) Traffic Engineering (TE) Label Switched Paths
(LSPs) using PCEP. Furthermore, PCEP can be used for computing paths
in SR networks.
Stateful PCE provide active control of MPLS-TE LSPs via PCEP, for a
model where the PCC delegates control over one or more locally
configured LSPs to the PCE. Further, stateful PCE could also create
and delete PCE-initiated LSPs itself. A PCE-based central controller
(PCECC) simplify the processing of a distributed control plane by
integrating with elements of Software-Defined Networking (SDN).
In some use cases, such as PCECC or Binding Segment Identifier (SID)
for Segment Routing (SR), there are requirements for a stateful PCE
to make allocation of labels, SIDs, etc. These use cases require PCE
aware of various identifier spaces where to make allocations on
behalf of PCC. This document describes a mechanism for PCC to inform
the PCE of the identifier space under its control via PCEP. The
identifier could be MPLS label, SID or any other to-be-defined
identifier to be allocated by a PCE.
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
Li, et al. Expires January 7, 2021 [Page 1]
Internet-Draft PCE Controlled ID Space July 2020
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 January 7, 2021.
Copyright Notice
Copyright (c) 2020 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.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.1. Requirements Language . . . . . . . . . . . . . . . . . . 4
3. Use cases . . . . . . . . . . . . . . . . . . . . . . . . . . 4
3.1. PCE-based Central Control . . . . . . . . . . . . . . . . 4
3.1.1. PCECC for MPLS/SR-MPLS . . . . . . . . . . . . . . . 4
3.1.2. PCECC for SRv6 . . . . . . . . . . . . . . . . . . . 5
3.2. Binding SID Allocation . . . . . . . . . . . . . . . . . 5
4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 5
5. Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
5.1. Open Object . . . . . . . . . . . . . . . . . . . . . . . 7
5.1.1. LABEL-CONTROL-SPACE TLV . . . . . . . . . . . . . . . 7
5.1.2. FUNCT-ID-CONTROL-SPACE TLV . . . . . . . . . . . . . 8
6. Other Considerations . . . . . . . . . . . . . . . . . . . . 10
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11
8. Security Considerations . . . . . . . . . . . . . . . . . . . 11
Show full document text