RFC 9603 on Path Computation Element Communication Protocol (PCEP) Extensions for IPv6 Segment Routing

rfc-editor@rfc-editor.org Mon, 29 July 2024 20:51 UTC

Return-Path: <wwwrun@rfcpa.rfc-editor.org>
X-Original-To: ietf-announce@ietf.org
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from rfcpa.rfc-editor.org (unknown [167.172.21.234]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1BD20C14F748; Mon, 29 Jul 2024 13:51:22 -0700 (PDT)
Received: by rfcpa.rfc-editor.org (Postfix, from userid 461) id 81B567FA69; Mon, 29 Jul 2024 13:51:21 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 9603 on Path Computation Element Communication Protocol (PCEP) Extensions for IPv6 Segment Routing
From: rfc-editor@rfc-editor.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20240729205121.81B567FA69@rfcpa.rfc-editor.org>
Date: Mon, 29 Jul 2024 13:51:21 -0700
Message-ID-Hash: UX5ZEBHG7WY2W6TXGAXXTH2M25SYCLGD
X-Message-ID-Hash: UX5ZEBHG7WY2W6TXGAXXTH2M25SYCLGD
X-MailFrom: wwwrun@rfcpa.rfc-editor.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ietf-announce.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, pce@ietf.org
X-Mailman-Version: 3.3.9rc4
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/ymV4ZXwvMnb1wO64wBIHB5dT9_0>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Owner: <mailto:ietf-announce-owner@ietf.org>
List-Post: <mailto:ietf-announce@ietf.org>
List-Subscribe: <mailto:ietf-announce-join@ietf.org>
List-Unsubscribe: <mailto:ietf-announce-leave@ietf.org>

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

        
        RFC 9603

        Title:      Path Computation Element Communication Protocol (PCEP)
                    Extensions for IPv6 Segment Routing 
        Author:     C. Li, Ed.,
                    P. Kaladharan,
                    S. Sivabalan,
                    M. Koldychev,
                    Y. Zhu
        Status:     Standards Track
        Stream:     IETF
        Date:       July 2024
        Mailbox:    c.l@huawei.com,
                    prejeeth@rtbrick.com,
                    msiva282@gmail.com,
                    mkoldych@cisco.com,
                    zhuyq8@chinatelecom.cn
        Pages:      23
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-pce-segment-routing-ipv6-25.txt

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

        DOI:        10.17487/RFC9603

Segment Routing (SR) can be used to steer packets through a network
using the IPv6 or MPLS data plane, employing the source routing
paradigm.

An SR Path can be derived from a variety of mechanisms, including an
IGP Shortest Path Tree (SPT), explicit configuration, or a Path
Computation Element (PCE).

Since SR can be applied to both MPLS and IPv6 data planes, a PCE
should be able to compute an SR Path for both MPLS and IPv6 data
planes. The Path Computation Element Communication Protocol (PCEP)
extension and mechanisms to support SR-MPLS have been defined. This
document outlines the necessary extensions to support SR for the IPv6
data plane within PCEP.

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