Last Call: <draft-ietf-pce-pcep-flowspec-09.txt> (PCEP Extension for Flow Specification) to Proposed Standard
The IESG <iesg-secretary@ietf.org> Mon, 22 June 2020 20:53 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 D578B3A1195; Mon, 22 Jun 2020 13:53:07 -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-pcep-flowspec-09.txt> (PCEP Extension for Flow Specification) to Proposed Standard
X-Test-IDTracker: no
X-IETF-IDTracker: 7.3.2
Auto-Submitted: auto-generated
Precedence: bulk
CC: pce-chairs@ietf.org, db3546@att.com, pce@ietf.org, draft-ietf-pce-pcep-flowspec@ietf.org, Julien Meuric <julien.meuric@orange.com>, julien.meuric@orange.com
Reply-To: last-call@ietf.org
Sender: iesg-secretary@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-ID: <159285918728.15849.17315250353555891619@ietfa.amsl.com>
Date: Mon, 22 Jun 2020 13:53:07 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/hj3wQvZWB3lja7VT4oJICTCiO5M>
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, 22 Jun 2020 20:53:08 -0000
The IESG has received a request from the Path Computation Element WG (pce) to consider the following document: - 'PCEP Extension for Flow Specification' <draft-ietf-pce-pcep-flowspec-09.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 last-call@ietf.org mailing lists by 2020-07-06. 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 The Path Computation Element (PCE) is a functional component capable of selecting paths through a traffic engineering network. These paths may be supplied in response to requests for computation, or may be unsolicited instructions issued by the PCE to network elements. Both approaches use the PCE Communication Protocol (PCEP) to convey the details of the computed path. Traffic flows may be categorized and described using "Flow Specifications". RFC XXXX defines the Flow Specification and describes how Flow Specification Components are used to describe traffic flows. RFC XXXX also defines how Flow Specifications may be distributed in BGP to allow specific traffic flows to be associated with routes. This document specifies a set of extensions to PCEP to support dissemination of Flow Specifications. This allows a PCE to indicate what traffic should be placed on each path that it is aware of. RFC Editor Note: Please replace XXXX in the Abstract with the RFC number assigned to draft-ietf-idr-rfc5575bis when it is published. Please remove this note. The file can be obtained via https://datatracker.ietf.org/doc/draft-ietf-pce-pcep-flowspec/ The following IPR Declarations may be related to this I-D: https://datatracker.ietf.org/ipr/3840/