PCEP Procedures and Protocol Extensions for Using PCE as a Central Controller (PCECC) for SRv6
draft-dhody-pce-pcep-extension-pce-controller-srv6-02
|
| Document |
Type |
|
Active Internet-Draft (individual)
|
|
Last updated |
|
2019-08-22
|
|
Stream |
|
(None)
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
xml
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)
|
PCE Working Group M. Negi
Internet-Draft Z. Li
Intended status: Standards Track X. Geng
Expires: February 23, 2020 Huawei Technologies
August 22, 2019
PCEP Procedures and Protocol Extensions for Using PCE as a Central
Controller (PCECC) for SRv6
draft-dhody-pce-pcep-extension-pce-controller-srv6-02
Abstract
The Path Computation Element (PCE) is a core component of Software-
Defined Networking (SDN) systems. It can compute optimal paths for
traffic across a network and can also update the paths to reflect
changes in the network or traffic demands.
PCE was developed to derive paths for MPLS Label Switched Paths
(LSPs), which are supplied to the head end of the LSP using the Path
Computation Element Communication Protocol (PCEP). But SDN has a
broader applicability than signaled (G)MPLS traffic-engineered (TE)
networks, and the PCE may be used to determine paths in a range of
use cases. PCEP has been proposed as a control protocol for use in
these environments to allow the PCE to be fully enabled as a central
controller.
A PCE-based central controller (PCECC) can simplify the processing of
a distributed control plane by blending it with elements of SDN and
without necessarily completely replacing it. This document specifies
the procedures and PCEP protocol extensions when a PCE-based
controller is also responsible for configuring the forwarding actions
on the routers for Segment Routing in IPv6 (SRv6), in addition to
computing the SRv6 paths for packet flows and telling the edge
routers what instructions to attach to packets as they enter the
network.
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/.
Negi, et al. Expires February 23, 2020 [Page 1]
Internet-Draft PCECC-SRv6 August 2019
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 February 23, 2020.
Copyright Notice
Copyright (c) 2019 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. Requirements Language . . . . . . . . . . . . . . . . . . 5
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5
3. PCECC SRv6 . . . . . . . . . . . . . . . . . . . . . . . . . 5
4. PCEP Requirements . . . . . . . . . . . . . . . . . . . . . . 6
5. Procedures for Using the PCE as the Central Controller
(PCECC) in SRv6 . . . . . . . . . . . . . . . . . . . . . . . 6
5.1. Stateful PCE Model . . . . . . . . . . . . . . . . . . . 6
5.2. New Functions . . . . . . . . . . . . . . . . . . . . . . 6
5.3. PCECC Capability Advertisement . . . . . . . . . . . . . 7
5.4. PCEP session IP address and TEDB Router ID . . . . . . . 7
5.5. SRv6 Path Operations . . . . . . . . . . . . . . . . . . 7
5.5.1. PCECC Segment Routing in IPv6 (SRv6) . . . . . . . . 7
5.5.1.1. PCECC SRv6 Node/Prefix SID allocation . . . . . . 7
5.5.1.2. PCECC SRv6 Adjacency SID allocation . . . . . . . 8
5.5.1.3. Redundant PCEs . . . . . . . . . . . . . . . . . 9
5.5.1.4. Re Delegation and Cleanup . . . . . . . . . . . . 9
5.5.1.5. Synchronization of SRv6 SID Allocations . . . . . 9
6. PCEP messages . . . . . . . . . . . . . . . . . . . . . . . . 9
7. PCEP Objects . . . . . . . . . . . . . . . . . . . . . . . . 9
7.1. OPEN Object . . . . . . . . . . . . . . . . . . . . . . . 9
Show full document text