[Pce] I-D Action: draft-ietf-pce-pcep-flowspec-12.txt

internet-drafts@ietf.org Sat, 31 October 2020 04:53 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Cc: pce@ietf.org
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: pce@ietf.org
Message-ID: <160411999809.3549.14880758702724070191@ietfa.amsl.com>
Date: Fri, 30 Oct 2020 21:53:18 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/vQkcP1OuB_xdWmlvNKefDRVmN2M>
Subject: [Pce] I-D Action: draft-ietf-pce-pcep-flowspec-12.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Path Computation Element WG of the IETF.

        Title           : PCEP Extension for Flow Specification
        Authors         : Dhruv Dhody
                          Adrian Farrel
                          Zhenbin Li
	Filename        : draft-ietf-pce-pcep-flowspec-12.txt
	Pages           : 37
	Date            : 2020-10-30

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

   The extensions defined in this document include the creation, update,
   and withdrawal of Flow Specifications via PCEP, and can be applied to
   tunnels initiated by the PCE or to tunnels where control is delegated
   to the PCE by the PCC.  Furthermore, a PCC requesting a new path can
   include Flow Specifications in the request to indicate the purpose of
   the tunnel allowing the PCE to factor this into the path computation.

   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 IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-pce-pcep-flowspec/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-pce-pcep-flowspec-12
https://datatracker.ietf.org/doc/html/draft-ietf-pce-pcep-flowspec-12

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-pce-pcep-flowspec-12


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.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

[Pce] I-D Action: draft-ietf-pce-pcep-flowspec-12… internet-drafts