[Pce] I-D Action: draft-ietf-pce-multipath-25.txt
internet-drafts@ietf.org Wed, 13 May 2026 08:52 UTC
Return-Path: <internet-drafts@ietf.org>
X-Original-To: pce@ietf.org
Delivered-To: pce@mail2.ietf.org
Received: from [10.244.6.166] (unknown [4.156.85.76]) by mail2.ietf.org (Postfix) with ESMTP id 10CFEEDA1446; Wed, 13 May 2026 01:52:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1778662322; bh=KjeyMEVD8hpuA5/oV+T5Axpt+5Ievak7IbVhE1YYMD4=; h=From:To:Cc:Subject:Reply-To:Date; b=KlrO0SqbE+oQyWT05CL2Icx4GKMQIRkxYlIpJNwliR4nPsfWoOe2tB1rWFxktE/DB Jk/4/Nw60GJ5DRlAMAFT9EMapiuFmo3IH2NAT3mZYL5nWwAKFfEahju4Pd/edb81i5 NzscPjoqS2Z0HAJNzXcvBGGYRbWzYlGBgnho45ac=
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
X-Test-IDTracker: no
X-IETF-IDTracker: 12.64.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <177866232198.1090814.1949042583308517580@dt-datatracker-54557f87b8-lnrkh>
Date: Wed, 13 May 2026 01:52:02 -0700
Message-ID-Hash: RVLCGX4OQZWON6LEXI6IRVQUVSY32CL3
X-Message-ID-Hash: RVLCGX4OQZWON6LEXI6IRVQUVSY32CL3
X-MailFrom: internet-drafts@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: pce@ietf.org
X-Mailman-Version: 3.3.9rc6
Reply-To: pce@ietf.org
Subject: [Pce] I-D Action: draft-ietf-pce-multipath-25.txt
List-Id: Path Computation Element <pce.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/9KESwsnfSjmQc5Jf0mIDc8G42z4>
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>
Internet-Draft draft-ietf-pce-multipath-25.txt is now available. It is a work
item of the Path Computation Element (PCE) WG of the IETF.
Title: Path Computation Element Communication Protocol (PCEP) Extensions for Signaling Multipath Information
Authors: Mike Koldychev
Samuel Sidor
Name: draft-ietf-pce-multipath-25.txt
Pages: 32
Dates: 2026-05-13
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 IETF datatracker status page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-pce-multipath/
There is also an HTML version available at:
https://www.ietf.org/archive/id/draft-ietf-pce-multipath-25.html
A diff from the previous version is available at:
https://author-tools.ietf.org/iddiff?url2=draft-ietf-pce-multipath-25
Internet-Drafts are also available by rsync at:
rsync.ietf.org::internet-drafts
- [Pce] I-D Action: draft-ietf-pce-multipath-25.txt internet-drafts