PCE for BIER-TE Path
draft-chen-pce-bier-te-path-00
Network Working Group H. Chen
Internet-Draft M. McBride
Intended status: Standards Track Futurewei
Expires: August 25, 2021 A. Wang
China Telecom
G. Mishra
Verizon Inc.
Y. Liu
China Mobile
Y. Fan
Casa Systems
L. Liu
Fujitsu
X. Liu
Volta Networks
February 21, 2021
PCE for BIER-TE Path
draft-chen-pce-bier-te-path-00
Abstract
This document describes extensions to Path Computation Element (PCE)
communication Protocol (PCEP) for supporting Bit Index Explicit
Replication (BIER) Traffic Engineering (TE) paths.
Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119].
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."
Chen, et al. Expires August 25, 2021 [Page 1]
Internet-Draft PCE for BIER-TE Path February 2021
This Internet-Draft will expire on August 25, 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.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Terminologies . . . . . . . . . . . . . . . . . . . . . . 4
2. Overview of PCE for BIER-TE . . . . . . . . . . . . . . . . . 5
2.1. Example BIER-TE Topology with PCE . . . . . . . . . . . . 5
2.2. A Brief Flow of PCEP Messages for a BIER-TE Path . . . . 6
2.3. Procedures on Ingress . . . . . . . . . . . . . . . . . . 8
3. Extensions to PCEP . . . . . . . . . . . . . . . . . . . . . 9
3.1. BIER-TE Path Capability . . . . . . . . . . . . . . . . . 9
3.2. Extensions to SRP . . . . . . . . . . . . . . . . . . . . 10
3.2.1. SRP Object Flag Field . . . . . . . . . . . . . . . . 10
3.2.2. Multicast Traffic TLV . . . . . . . . . . . . . . . . 11
3.3. Ingress Node Object . . . . . . . . . . . . . . . . . . . 14
3.4. Objective Functions . . . . . . . . . . . . . . . . . . . 16
3.5. BIER-TE Path Subobject . . . . . . . . . . . . . . . . . 17
3.6. BIER-TE Path Subobject in ERO . . . . . . . . . . . . . . 18
3.7. BIER-TE Path Subobject in RRO . . . . . . . . . . . . . . 18
4. Procedures . . . . . . . . . . . . . . . . . . . . . . . . . 19
4.1. BIER-TE Path Creation . . . . . . . . . . . . . . . . . . 19
4.2. BIER-TE Path Update . . . . . . . . . . . . . . . . . . . 20
4.3. BIER-TE Path Deletion . . . . . . . . . . . . . . . . . . 20
5. The PCEP Messages . . . . . . . . . . . . . . . . . . . . . . 20
5.1. The PCRpt Message . . . . . . . . . . . . . . . . . . . . 20
5.2. The PCUpd Message . . . . . . . . . . . . . . . . . . . . 21
5.3. The PCInitiate Message . . . . . . . . . . . . . . . . . 21
Show full document text