Last Call: <draft-ietf-pce-segment-routing-14.txt> (PCEP Extensions for Segment Routing) to Proposed Standard

The IESG <iesg-secretary@ietf.org> Mon, 15 October 2018 18:58 UTC

Return-Path: <iesg-secretary@ietf.org>
X-Original-To: ietf-announce@ietf.org
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id E0162124C04; Mon, 15 Oct 2018 11:58:43 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: Last Call: <draft-ietf-pce-segment-routing-14.txt> (PCEP Extensions for Segment Routing) to Proposed Standard
X-Test-IDTracker: no
X-IETF-IDTracker: 6.87.0
Auto-Submitted: auto-generated
Precedence: bulk
CC: dhruv.ietf@gmail.com, db3546@att.com, Dhruv Dhody <dhruv.ietf@gmail.com>, pce@ietf.org, pce-chairs@ietf.org, draft-ietf-pce-segment-routing@ietf.org
Reply-To: ietf@ietf.org
Sender: iesg-secretary@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Reply-To: ietf@ietf.org
Message-ID: <153962992384.18790.6604030692402632855.idtracker@ietfa.amsl.com>
Date: Mon, 15 Oct 2018 11:58:43 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/qlNmQjnkJO8NfmbKycd9e0Lqxa4>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Oct 2018 18:58:44 -0000

The IESG has received a request from the Path Computation Element WG (pce) to
consider the following document: - 'PCEP Extensions for Segment Routing'
  <draft-ietf-pce-segment-routing-14.txt> as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2018-10-29. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the beginning of
the Subject line to allow automated sorting.

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





The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-pce-segment-routing/

IESG discussion can be tracked via
https://datatracker.ietf.org/doc/draft-ietf-pce-segment-routing/ballot/


No IPR declarations have been submitted directly on this I-D.