PCEP Extensions for Segment Routing leveraging the IPv6 data plane
draft-ietf-pce-segment-routing-ipv6-00
PCE Working Group M. Negi
Internet-Draft C. Li
Intended status: Standards Track Huawei Technologies
Expires: September 11, 2019 S. Sivabalan
Cisco Systems
P. Kaladharan
RtBrick Inc
March 10, 2019
PCEP Extensions for Segment Routing leveraging the IPv6 data plane
draft-ietf-pce-segment-routing-ipv6-00
Abstract
The Source Packet Routing in Networking (SPRING) architecture
describes how Segment Routing (SR) can be used to steer packets
through an IPv6 or MPLS network using the source routing paradigm.
Segment Routing (SR) enables any head-end node to select any path
without relying on a hop-by-hop signaling technique (e.g., LDP or
RSVP-TE).
It depends only on "segments" that are advertised by Link- State
IGPs. A Segment Routed Path can be derived from a variety of
mechanisms, including an IGP Shortest Path Tree (SPT), explicit
configuration, or a Path Computation Element (PCE).
Since, Segment Routing can be applied to both MPLS and IPv6
forwarding plane, a PCE should be able to compute SR-Path for both
MPLS and IPv6 forwarding plane. This draft describes the extensions
required for Segment Routing support for IPv6 data plane in Path
Computation Element communication Protocol (PCEP).
Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP
14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here.
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
Negi, et al. Expires September 11, 2019 [Page 1]
Internet-Draft PCEP Extensions for SRv6 March 2019
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 September 11, 2019.
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
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Overview of PCEP Operation in SRv6 Networks . . . . . . . . . 5
3.1. Operation Overview . . . . . . . . . . . . . . . . . . . 6
3.2. SRv6-Specific PCEP Message Extensions . . . . . . . . . . 6
3.3. Object Formats . . . . . . . . . . . . . . . . . . . . . 6
3.3.1. The OPEN Object . . . . . . . . . . . . . . . . . . . 6
3.3.1.1. The SRv6 PCE Capability sub-TLV . . . . . . . . . 6
3.3.1.2. Exchanging the SRv6 Capability . . . . . . . . . 8
3.3.2. The RP/SRP Object . . . . . . . . . . . . . . . . . . 9
3.3.3. ERO Object . . . . . . . . . . . . . . . . . . . . . 9
3.3.3.1. SR-ERO Subobject . . . . . . . . . . . . . . . . 10
3.3.3.2. ERO Processing . . . . . . . . . . . . . . . . . 12
3.3.4. RRO Object . . . . . . . . . . . . . . . . . . . . . 13
3.3.4.1. SR-RRO Subobject . . . . . . . . . . . . . . . . 13
3.4. Security Considerations . . . . . . . . . . . . . . . . . 14
3.5. IANA Considerations . . . . . . . . . . . . . . . . . . . 14
3.5.1. PCEP Objects . . . . . . . . . . . . . . . . . . . . 14
3.5.1.1. ERROR Objects . . . . . . . . . . . . . . . . . . 14
3.5.1.2. TLV Type Indicators . . . . . . . . . . . . . . . 14
Show full document text