IETF Logo Mail Archive

[Idr] Re: [BGP-LS] draft-ietf-idr-bgp-ls-sr-epe-over-l2bundle-02 - WG LC (5/11/2026 to 5/31/2026) - 3 week WG LC

liu.yao71@zte.com.cn Wed, 13 May 2026 01:14 UTC

Return-Path: <liu.yao71@zte.com.cn>
X-Original-To: idr@mail2.ietf.org
Delivered-To: idr@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 24108ED6F6C4; Tue, 12 May 2026 18:14:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1778634897; bh=u2ITUK1oxs36OiPpk11eSTODVk2faTYDAN5YF+6MYKg=; h=In-Reply-To:References:Date:From:To:Cc:Subject; b=Auw17vuzbnW7G0Y9ig5/B/cll9O2Ju56nllMXPMLKnnW8vOvvtFNEhbN/cZW+vcY5 E+93ZqerTasmrauq72I/iIXXp1qnuEnXm0zGCzbtApwplZ2kPMI+1BQrmvnAAr+Ddx rXxNl8EnCDrOsEOw+amjdGEQo2TS0TCBG4Uxh0zs=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gddDqaMJ_kZy; Tue, 12 May 2026 18:14:56 -0700 (PDT)
Received: from mxhk.zte.com.cn (mxhk.zte.com.cn [160.30.148.34]) (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 mail2.ietf.org (Postfix) with ESMTPS id 34CECED6F6BC; Tue, 12 May 2026 18:14:55 -0700 (PDT)
Received: from mse-fl2.zte.com.cn (unknown [10.5.228.133]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange x25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mxhk.zte.com.cn (FangMail) with ESMTPS id 4gFb996Z4nz5B11R; Wed, 13 May 2026 09:14:53 +0800 (CST)
Received: from njy2app01.zte.com.cn ([10.40.12.136]) by mse-fl2.zte.com.cn with SMTP id 64D1ElgN054623; Wed, 13 May 2026 09:14:47 +0800 (+08) (envelope-from liu.yao71@zte.com.cn)
Received: from mapi (njy2app08[null]) by mapi (Zmail) with MAPI id mid203; Wed, 13 May 2026 09:14:48 +0800 (CST)
X-Zmail-TransId: 2b006a03d088122-a31ab
X-Mailer: Zmail v1.0
Message-ID: <20260513091448315lLaqsspgbzcBQUVCnT2sF@zte.com.cn>
In-Reply-To: <DM8PR08MB7413D38E716D1CA540EFCA89B3382@DM8PR08MB7413.namprd08.prod.outlook.com>
References: DM8PR08MB7413D38E716D1CA540EFCA89B3382@DM8PR08MB7413.namprd08.prod.outlook.com
Date: Wed, 13 May 2026 09:14:48 +0800
Mime-Version: 1.0
From: liu.yao71@zte.com.cn
To: shares@ndzh.com
Content-Type: multipart/mixed; boundary="=====_001_next====="
X-MAIL: mse-fl2.zte.com.cn 64D1ElgN054623
X-TLS: YES
X-SPF-DOMAIN: zte.com.cn
X-ENVELOPE-SENDER: liu.yao71@zte.com.cn
X-SPF: None
X-SOURCE-IP: 10.5.228.133 unknown Wed, 13 May 2026 09:14:53 +0800
X-Fangmail-Anti-Spam-Filtered: true
X-Fangmail-MID-QID: 6A03D08D.000/4gFb996Z4nz5B11R
Message-ID-Hash: UAQ4F4SZPDSXHY7G2QWWBJIWJXJUAKCV
X-Message-ID-Hash: UAQ4F4SZPDSXHY7G2QWWBJIWJXJUAKCV
X-MailFrom: liu.yao71@zte.com.cn
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, spring@ietf.org, pce-chairs@ietf.org, srv6ops-chairs@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Idr] Re: [BGP-LS] draft-ietf-idr-bgp-ls-sr-epe-over-l2bundle-02 - WG LC (5/11/2026 to 5/31/2026) - 3 week WG LC
List-Id: Inter-Domain Routing <idr.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/FwvpnKnNIGpUh7i26XJrgMaNTsA>
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>

Hi, 

I support the publication of this document. 
It enables traffic steering over individual L2 bundle member links, thereby enhancing SR-TE capabilities. 

Regards,
Yao





Original


From: SusanHares <shares@ndzh.com>
To: idr <idr@ietf.org>;spring <spring@ietf.org>;
Cc: pce-chairs <pce-chairs@ietf.org>;srv6ops-chairs@ietf.org <srv6ops-chairs@ietf.org>;
Date: 2026年05月11日 20:35
Subject: [Idr] [BGP-LS] draft-ietf-idr-bgp-ls-sr-epe-over-l2bundle-02 - WG LC (5/11/2026 to 5/31/2026) - 3 week WG LC

_______________________________________________
Idr mailing list -- idr@ietf.org
To unsubscribe send an email to idr-leave@ietf.org
 

This begins a 3-week WG LC for draft-ietf-idr-bgp-ls-sr-epe-over-l2bundle-02.txt (5/11 to 5/31/2026).  
 
This document describes how BGP-LS can support Segment Routing BGP Egress Peer Engineering by updating 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 draft is being cross-posted to Spring to confirm that this draft aligns with Spring’s goals for SR-EPE.  If you believe this does not represent Spring’s plan for SR-EPE over L2 Bundled links, please reply to this email.  The PCE and srv6ops chairs have been copied in case they wish to inform their WGs.
 
The authors of this draft should reply to this email with an IPR statement regarding this document.  
 
The IDR WG LC should consider: 
 
1) Is this BGP-LS addition technically correct? 
2) Is this document ready for publication? 
3) Will it aid the deployment of BGP SR EPE in networks? 
 
Cheerily, Sue Hares

v2.46.0 | Report a Bug | By Email | System Status