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

internet-drafts@ietf.org Tue, 26 December 2023 05:34 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 4DA3AC14F683; Mon, 25 Dec 2023 21:34:49 -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: 12.1.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: pce@ietf.org
Message-ID: <170356888929.47362.15135569534917195072@ietfa.amsl.com>
Date: Mon, 25 Dec 2023 21:34:49 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/5fwUojFwpqwm17dZlnuk3i7nfNo>
Subject: [Pce] I-D Action: draft-ietf-pce-pcep-l2-flowspec-05.txt
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.39
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: Tue, 26 Dec 2023 05:34:49 -0000

Internet-Draft draft-ietf-pce-pcep-l2-flowspec-05.txt is now available. It is
a work item of the Path Computation Element (PCE) WG of the IETF.

   Title:   PCEP Extension for Layer 2 (L2) Flow Specification
   Authors: Dhruv Dhody
            Adrian Farrel
            Zhenbin Li
   Name:    draft-ietf-pce-pcep-l2-flowspec-05.txt
   Pages:   14
   Dates:   2023-12-25

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

The IETF datatracker status page for this Internet-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-05

A diff from the previous version is available at:
https://author-tools.ietf.org/iddiff?url2=draft-ietf-pce-pcep-l2-flowspec-05

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