[Pce] RFC 10066 on Path Computation Element Communication Protocol (PCEP) Extensions for Signaling Multipath Information
rfc-editor@rfc-editor.org Mon, 26 October 2026 19:22 UTC
Received: by mx.ietf.org (Postfix) id 9B12446; Mon, 26 Oct 2026 19:22:55 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rfc-editor.org; s=mail; t=1793042575; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=MnvfEVh+sBUCLSjuE3q2z06w1ngQDRmQNotzcqioSA0=; b=kqMqdi4aN/SKTlvcbvh4DuSOtfSUshRwRgRyTqbiw15bkuJFc0El5YA3v8wFFsmVnP8Buc 9CyG9OgNrfHQuyLWLnmXKWRHGSR6O+NqtAD0pxFfyfbu95EAHymmRDLkQih/Eq6OvlH3LS 5XhQW1ThrR+mghPEUQ3NLYrP2l/pLMA=
Authentication-Results: ORIGINATING; auth=pass smtp.auth=mail2@ietf.org smtp.mailfrom=rfc-editor@rfc-editor.org
Received: from celery-6b6df56bcb-cbt58 (gaia.k8s.ietf.org [4.156.85.76]) by mail2.ietf.org (Postfix) with ESMTP id 61F4E13B1C823; Mon, 26 Oct 2026 12:22:55 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: rfc-editor@rfc-editor.org
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Date: Mon, 26 Oct 2026 19:22:55 -0000
message-id: <179304257524.10.125732995214886341@rfc-editor.org>
Message-ID-Hash: QXZEBFH47RWS4CQ73PSIOK67PK3RWQ4D
X-Message-ID-Hash: QXZEBFH47RWS4CQ73PSIOK67PK3RWQ4D
X-MailFrom: rfc-editor@rfc-editor.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; header-match-pce.ietf.org-0; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: drafts-update-ref@iana.org, pce@ietf.org, rfc-editor@rfc-editor.org
X-Mailman-Version: 3.3.10
Precedence: list
Subject: [Pce] RFC 10066 on Path Computation Element Communication Protocol (PCEP) Extensions for Signaling Multipath Information
List-Id: Path Computation Element <pce.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/wrkO8A6JiL--Z_WzUyidZaAN94Y>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Owner: <mailto:pce-owner@ietf.org>
List-Post: <mailto:pce@ietf.org>
List-Subscribe: <mailto:pce-join@ietf.org>
List-Unsubscribe: <mailto:pce-leave@ietf.org>
A new Request for Comments is now available in online RFC libraries.
RFC 10066
Title: Path Computation Element Communication Protocol (PCEP)
Extensions for Signaling Multipath Information
Author: M. Koldychev, Ed.,
S. Sidor, Ed.
Status: Proposed Standard
Stream: IETF
Date: October 2026
Mailbox: mkoldych@ciena.com,
ssidor@cisco.com
Pages: 29
I-D Tag: draft-ietf-pce-multipath-29
URL: https://www.rfc-editor.org/info/rfc10066
DOI: 10.17487/RFC10066
This document defines Path Computation Element Communication Protocol (PCEP) extensions to signal multipath information, associating multiple forwarding paths with a single PCEP Label Switched Path (LSP) to allow load balancing and redundancy across diverse paths. The extensions are generic and applicable to both stateless and stateful PCEP and are designed to be reusable for future path types. Their primary application is Segment Routing Policy (SR Policy), where a Candidate Path can contain multiple segment lists: current PCEP extensions for SR Policy only allow signaling of a single segment list per Candidate Path. These extensions enable multipath capabilities such as weighted or equal-cost load balancing across paths.
This document is a product of the Path Computation Element Working Group of the IETF.
STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and
suggestions for improvements. 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/series/rfc-download/
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