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

internet-drafts@ietf.org Sun, 06 March 2022 14:21 UTC

Return-Path: <internet-drafts@ietf.org>
X-Original-To: pce@ietf.org
Delivered-To: pce@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 1A1483A0B9B; Sun, 6 Mar 2022 06:21:08 -0800 (PST)
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
X-Test-IDTracker: no
X-IETF-IDTracker: 7.46.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: pce@ietf.org
Message-ID: <164657646804.27631.16143565558321897429@ietfa.amsl.com>
Date: Sun, 06 Mar 2022 06:21:08 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/4Elec5oplWtLXb2tQduBYBbUR_g>
Subject: [Pce] I-D Action: draft-ietf-pce-pcep-l2-flowspec-01.txt
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Path Computation Element <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 06 Mar 2022 14:21:09 -0000

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 L2 Flow Specification
        Authors         : Dhruv Dhody
                          Adrian Farrel
                          Zhenbin Li
	Filename        : draft-ietf-pce-pcep-l2-flowspec-01.txt
	Pages           : 13
	Date            : 2022-03-06

Abstract:
   The Path Computation Element (PCE) is a functional component capable
   of selecting paths through a traffic engineering (TE) 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 8955 defines the Flow Specification and
   describes how Flow Specification components are used to describe
   traffic flows.  RFC 8955 also defines how Flow Specifications may be
   distributed in BGP to allow specific traffic flows to be associated
   with routes.

   RFC 9168 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 extends the support for
   Ethernet Layer 2 (L2) and Layer 2 Virtual Private Network (L2VPN)
   traffic filtering rules either by themselves or in conjunction with
   L3 flowspecs.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-pce-pcep-l2-flowspec/

There is also an htmlized version available at:
https://datatracker.ietf.org/doc/html/draft-ietf-pce-pcep-l2-flowspec-01

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


Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts