PCEP Extensions for Segment Routing leveraging the IPv6 data plane
draft-negi-pce-segment-routing-ipv6-04

Document Type Replaced Internet-Draft (pce WG)
Last updated 2019-03-08 (latest revision 2019-02-06)
Replaced by draft-ietf-pce-segment-routing-ipv6
Stream IETF
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream WG state Adopted by a WG
Document shepherd No shepherd assigned
IESG IESG state Replaced by draft-ietf-pce-segment-routing-ipv6
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-negi-pce-segment-routing-ipv6-04.txt

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).

Authors

Mahendra Negi (mahendrasingh@huawei.com)
Cheng Li (chengli13@huawei.com)
Siva Sivabalan (msiva@cisco.com)
Prejeeth Kaladharan (prejeeth@rtbrick.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)