RFC 9168 on Path Computation Element Communication Protocol (PCEP) Extension for Flow Specification

rfc-editor@rfc-editor.org Fri, 14 January 2022 19:53 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A3A1E3A07D8; Fri, 14 Jan 2022 11:53:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YcjXkmHcuwGa; Fri, 14 Jan 2022 11:53:04 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 63BB33A07CD; Fri, 14 Jan 2022 11:53:03 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 499) id 09B2520EBD3; Fri, 14 Jan 2022 11:53:02 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 9168 on Path Computation Element Communication Protocol (PCEP) Extension for Flow Specification
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, pce@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20220114195302.09B2520EBD3@rfc-editor.org>
Date: Fri, 14 Jan 2022 11:53:02 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/MJtoQPFU5m0dMv2pWTi-xuutY3s>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
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: Fri, 14 Jan 2022 19:53:13 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 9168

        Title:      Path Computation Element Communication Protocol 
                    (PCEP) Extension for Flow Specification 
        Author:     D. Dhody,
                    A. Farrel,
                    Z. Li
        Status:     Standards Track
        Stream:     IETF
        Date:       January 2022
        Mailbox:    dhruv.ietf@gmail.com,
                    adrian@olddog.co.uk,
                    lizhenbin@huawei.com
        Pages:      29
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-pce-pcep-flowspec-13.txt

        URL:        https://www.rfc-editor.org/info/rfc9168

        DOI:        10.17487/RFC9168

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.

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 Path Computation Client (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.

This document is a product of the Path Computation Element Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC