[Idr] I-D Action: draft-ietf-idr-bgp-ls-sr-epe-over-l2bundle-00.txt
internet-drafts@ietf.org Wed, 30 July 2025 13:16 UTC
Return-Path: <internet-drafts@ietf.org>
X-Original-To: idr@ietf.org
Delivered-To: idr@mail2.ietf.org
Received: from [10.244.4.86] (unknown [104.131.183.230]) by mail2.ietf.org (Postfix) with ESMTP id 7FEF14D4C3CC; Wed, 30 Jul 2025 06:16:17 -0700 (PDT)
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.44.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <175388137736.238556.16449838986517858082@dt-datatracker-5bd446d5fd-c47nq>
Date: Wed, 30 Jul 2025 06:16:17 -0700
Message-ID-Hash: GGX25RSF7JO5WQCSASRAGUWC54MAX4JY
X-Message-ID-Hash: GGX25RSF7JO5WQCSASRAGUWC54MAX4JY
X-MailFrom: internet-drafts@ietf.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-idr.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: idr@ietf.org
X-Mailman-Version: 3.3.9rc6
Reply-To: idr@ietf.org
Subject: [Idr] I-D Action: draft-ietf-idr-bgp-ls-sr-epe-over-l2bundle-00.txt
List-Id: Inter-Domain Routing <idr.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/-i_Qnq83b0njQmrr5Jju56qbuQA>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Owner: <mailto:idr-owner@ietf.org>
List-Post: <mailto:idr@ietf.org>
List-Subscribe: <mailto:idr-join@ietf.org>
List-Unsubscribe: <mailto:idr-leave@ietf.org>
Internet-Draft draft-ietf-idr-bgp-ls-sr-epe-over-l2bundle-00.txt is now
available. It is a work item of the Inter-Domain Routing (IDR) WG of the IETF.
Title: Members
Authors: Changwang Lin
Zhenqiang Li
Ran Pang
Ketan Talaulikar
Ran Chen
Name: draft-ietf-idr-bgp-ls-sr-epe-over-l2bundle-00.txt
Pages: 13
Dates: 2025-07-30
Abstract:
There are deployments where the Layer 3 interface on which a BGP peer
session is established is a Layer 2 interface bundle. In order to
allow BGP-EPE to control traffic flows on individual member links of
the underlying Layer 2 bundle, BGP Peering SIDs need to be allocated
to individual bundle member links, and advertisement of such BGP
Peering SIDs in BGP-LS is required. This document describes how to
support Segment Routing BGP Egress Peer Engineering over Layer 2
bundle members. This document updates RFC9085 to allow the L2 Bundle
Member Attributes TLV to be added to the BGP-LS Attribute associated
with the Link NLRI of BGP peering link. This document updates
RFC9085 and RFC9086 to allow the PeerAdj SID TLV to be included as a
sub-TLV of the L2 Bundle Member Attributes TLV.
The IETF datatracker status page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-idr-bgp-ls-sr-epe-over-l2bundle/
There is also an HTMLized version available at:
https://datatracker.ietf.org/doc/html/draft-ietf-idr-bgp-ls-sr-epe-over-l2bundle-00
Internet-Drafts are also available by rsync at:
rsync.ietf.org::internet-drafts
- [Idr] I-D Action: draft-ietf-idr-bgp-ls-sr-epe-ov… internet-drafts