Subject: [Pce] FW: New Version Notification for draft-ietf-pce-segment-routing-16.txt

From: Jonathan Hardwick <[email-masked]>
Date: Mon, 4 Mar 2019 12:37:40 +0000

This version makes two changes:
- moves the section on backwards compatibility to an appendix
- adds a new NAI type for an IPv6 adjacency over a link that uses only link-local addresses (as motivated by draft-ietf-spring-segment-routing-policy).

Cheers
Jon

-----Original Message-----
From: [email-masked] <[email-masked]> 
Sent: Monday, 4 March, 2019 12:34 PM
To: Wim Henderickx <[email-masked]>; Siva Sivabalan <[email-masked]>; Jonathan Hardwick <[email-masked]>; Jonathan Hardwick <[email-masked]>; Jeff Tantsura <[email-masked]>; Clarence Filsfils <[email-masked]>
Subject: New Version Notification for draft-ietf-pce-segment-routing-16.txt

NOTE: Message is from an external sender

A new version of I-D, draft-ietf-pce-segment-routing-16.txt
has been successfully submitted by Jon Hardwick and posted to the IETF repository.

Name:           draft-ietf-pce-segment-routing
Revision:       16
Title:          PCEP Extensions for Segment Routing
Document date:  2019-03-04
Group:          pce
Pages:          33
URL:            https://www.ietf.org/internet-drafts/draft-ietf-pce-segment-routing-16.txt
Status:         https://datatracker.ietf.org/doc/draft-ietf-pce-segment-routing/
Htmlized:       https://tools.ietf.org/html/draft-ietf-pce-segment-routing-16
Htmlized:       https://datatracker.ietf.org/doc/html/draft-ietf-pce-segment-routing
Diff:           https://www.ietf.org/rfcdiff?url2=draft-ietf-pce-segment-routing-16

Abstract:
   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 Interior Gateway Protocols (IGPs).  A Segment Routing Path can
   be derived from a variety of mechanisms, including an IGP Shortest
   Path Tree (SPT), explicit configuration, or a Path Computation
   Element (PCE).  This document specifies extensions to the Path
   Computation Element Communication Protocol (PCEP) that allow a
   stateful PCE to compute and initiate Traffic Engineering (TE) paths,
   as well as a PCC to request a path subject to certain constraints and
   optimization criteria in SR networks.

Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat