[Pce] I-D Action: draft-ietf-pce-pcep-l2-flowspec-04.txt
internet-drafts@ietf.org Tue, 04 July 2023 07:13 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 B4B7DC14CF1E; Tue, 4 Jul 2023 00:13:34 -0700 (PDT)
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: 11.3.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: pce@ietf.org
Message-ID: <168845481472.23180.14090096588143989708@ietfa.amsl.com>
Date: Tue, 04 Jul 2023 00:13:34 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/kNzX2GYGrQWPOT_zPbzFAm7P_1M>
Subject: [Pce] I-D Action: draft-ietf-pce-pcep-l2-flowspec-04.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, 04 Jul 2023 07:13:34 -0000
A New Internet-Draft is available from the on-line Internet-Drafts directories. This Internet-Draft 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 Filename : draft-ietf-pce-pcep-l2-flowspec-04.txt Pages : 14 Date : 2023-07-04 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-04 A diff from the previous version is available at: https://author-tools.ietf.org/iddiff?url2=draft-ietf-pce-pcep-l2-flowspec-04 Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts
- [Pce] I-D Action: draft-ietf-pce-pcep-l2-flowspec… internet-drafts