[Pce] Last Call: <draft-ietf-pce-multipath-25.txt> (Path Computation Element Communication Protocol (PCEP) Extensions for Signaling Multipath Information) to Proposed Standard
The IESG <iesg-secretary@ietf.org> Wed, 20 May 2026 18:08 UTC
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: pce@ietf.org
Delivered-To: pce@mail2.ietf.org
Received: from [10.244.8.101] (unknown [4.156.85.76]) by mail2.ietf.org (Postfix) with ESMTP id 52A72F1C345D; Wed, 20 May 2026 11:08:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1779300508; bh=N2K/t6goarHxemtqMjTUMMSTIVPPBV+dPivJ1mNsFQ0=; h=From:To:Subject:CC:Reply-To:Date; b=OKTmTk/DXM21QszOhlugdfk2gtWGTkdB+3CEWCs8Zf8HYG9CrxUDzYx2305dPn6yc E8rg6+p7ObJ1pBF5kqCiqoN2PBrzem0QE+Pe6qysCdYlsQZxMePB51JD9bWvScIFbK J5tehgZyLogG/n3o4DIaafb6NN5Bu0jzDhn7ox6Q=
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 12.65.0
Auto-Submitted: auto-generated
Precedence: bulk
Sender: iesg-secretary@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-ID: <177930050826.107758.359875717736573079@dt-datatracker-7688897f84-hmm7m>
Date: Wed, 20 May 2026 11:08:28 -0700
Message-ID-Hash: L2YBHKQAHCTEQAQCD3BDQRI7EV77LR64
X-Message-ID-Hash: L2YBHKQAHCTEQAQCD3BDQRI7EV77LR64
X-MailFrom: iesg-secretary@ietf.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-pce.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: draft-ietf-pce-multipath@ietf.org, pce-chairs@ietf.org, pce@ietf.org
X-Mailman-Version: 3.3.9rc6
Reply-To: last-call@ietf.org
Subject: [Pce] Last Call: <draft-ietf-pce-multipath-25.txt> (Path Computation Element Communication Protocol (PCEP) Extensions for Signaling Multipath Information) to Proposed Standard
List-Id: Path Computation Element <pce.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/3gan30Y4QaXIwWY9WXuataqohlw>
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>
The IESG has received a request from the Path Computation Element WG (pce) to consider the following document: - 'Path Computation Element Communication Protocol (PCEP) Extensions for Signaling Multipath Information' <draft-ietf-pce-multipath-25.txt> as Proposed Standard The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the last-call@ietf.org mailing lists by 2026-06-03. Exceptionally, comments may be sent to iesg@ietf.org instead. In either case, please retain the beginning of the Subject line to allow automated sorting. Abstract A Segment Routing (SR) Policy Candidate Path can contain multiple Segment Lists, allowing for load-balancing and redundancy across diverse paths. However, current PCEP extensions for SR Policy only allow signaling of a single Segment List per Candidate Path. This document defines PCEP extensions to encode multiple Segment Lists within an SR Policy Candidate Path, enabling multipath capabilities such as weighted or equal-cost load-balancing across Segment Lists. These extensions are designed to be generic and reusable for future path types beyond SR Policy, and are applicable to both stateless and stateful PCEP. The file can be obtained via https://datatracker.ietf.org/doc/draft-ietf-pce-multipath/ The following IPR Declarations may be related to this I-D: https://datatracker.ietf.org/ipr/6144/ https://datatracker.ietf.org/ipr/4833/ https://datatracker.ietf.org/ipr/5762/