PCEP Extensions for BIER-TE
draft-chen-pce-bier-06
|
| Document |
Type |
|
Active Internet-Draft (individual)
|
|
Last updated |
|
2019-11-03
|
|
Stream |
|
(None)
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
pdf
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)
|
Networking Working Group Ran. Chen
Internet-Draft Zheng. Zhang
Intended status: Standards Track ZTE Corporation
Expires: May 7, 2020 Senthil. Dhanaraj
Huawei
Fengwei. Qin
China Mobile
November 4, 2019
PCEP Extensions for BIER-TE
draft-chen-pce-bier-06
Abstract
Bit Index Explicit Replication (BIER)-TE shares architecture and
packet formats with BIER as described in [RFC8279]. BIER-TE forwards
and replicates packets based on a BitString in the packet header, but
every BitPosition of the BitString of a BIER-TE packet indicates one
or more adjacencies as described in [I-D.ietf-bier-te-arch].BIER-TE
Path can be derived from a Path Computation Element (PCE).
This document specifies extensions to the Path Computation Element
Protocol (PCEP) that allow a PCE to compute and initiate the path for
the BIER-TE.
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 May 7, 2020.
Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the
document authors. All rights reserved.
Chen, et al. Expires May 7, 2020 [Page 1]
Internet-Draft PCEP Ext for BIER-TE November 2019
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 . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Conventions used in this document . . . . . . . . . . . . . . 3
3. Overview of PCEP Operation in BIER Networks . . . . . . . . . 3
4. Object Formats . . . . . . . . . . . . . . . . . . . . . . . 3
4.1. The OPEN Object . . . . . . . . . . . . . . . . . . . . . 3
4.1.1. The BIER-TE PCE Capability sub-TLV . . . . . . . . . 3
4.2. The RP/SRP Object . . . . . . . . . . . . . . . . . . . . 4
4.3. END-POINTS object . . . . . . . . . . . . . . . . . . . . 4
4.4. ERO Object . . . . . . . . . . . . . . . . . . . . . . . 4
4.4.1. BIER-ERO Subobject . . . . . . . . . . . . . . . . . 5
4.4.2. BIER-ERO Processing . . . . . . . . . . . . . . . . . 6
5. Security Considerations . . . . . . . . . . . . . . . . . . . 6
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6
6.1. PCEP Objects . . . . . . . . . . . . . . . . . . . . . . 6
6.1.1. BIER-TE-PCE-CAPABILITY Sub-TLV Type Indicators . . . 7
6.1.2. New Path Setup Type . . . . . . . . . . . . . . . . . 7
6.1.3. BIER-ERO Subobject . . . . . . . . . . . . . . . . . 7
6.1.4. PCEP-Error Objects and Types . . . . . . . . . . . . 7
7. Normative references . . . . . . . . . . . . . . . . . . . . 8
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 9
1. Introduction
Bit Index Explicit Replication (BIER)-TE shares architecture and
packet formats with BIER as described in [RFC8279]. BIER-TE forwards
and replicates packets based on a BitString in the packet header, but
every BitPosition of the BitString of a BIER-TE packet indicates one
or more adjacencies as described in [I-D.ietf-bier-te-arch].BIER-TE
Path can be derived from a Path Computation Element (PCE).
[RFC8231] specifies a set of extensions to PCEP that allow a PCE to
compute and recommend network paths in compliance with [RFC4657] and
defines objects and TLVs for MPLS-TE LSPs.
This document uses a PCE for computing one or more BIER-TE paths
Show full document text