[Idr] Re: Fw: New Version Notification for draft-zhang-idr-portid-ec-00.txt
zhang.zheng@zte.com.cn Tue, 03 March 2026 09:34 UTC
Return-Path: <zhang.zheng@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 61C85C350669 for <idr@mail2.ietf.org>; Tue, 3 Mar 2026 01:34:57 -0800 (PST)
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 XNcB_kdl2YGQ for <idr@mail2.ietf.org>; Tue, 3 Mar 2026 01:34:56 -0800 (PST)
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 C4156C350662 for <idr@ietf.org>; Tue, 3 Mar 2026 01:34:55 -0800 (PST)
Received: from mse-fl1.zte.com.cn (unknown [10.5.228.132]) (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 4fQ9ck6w9gz5BNS0; Tue, 03 Mar 2026 17:34:46 +0800 (CST)
Received: from njy2app03.zte.com.cn ([10.40.13.14]) by mse-fl1.zte.com.cn with SMTP id 6239YfBt073170; Tue, 3 Mar 2026 17:34:41 +0800 (+08) (envelope-from zhang.zheng@zte.com.cn)
Received: from mapi (njb2app07[null]) by mapi (Zmail) with MAPI id mid203; Tue, 3 Mar 2026 17:34:43 +0800 (CST)
X-Zmail-TransId: 2aff69a6ab33e5f-cacc3
X-Mailer: Zmail v1.0
Message-ID: <20260303173443700Hgd9DtsisZrWfJha7gCMQ@zte.com.cn>
In-Reply-To: <CAPF+HwUdfYPa=R5AHDPT6nGkG=KVTS7v6aFhwCDB9qg=muvHqw@mail.gmail.com>
References: CAPF+HwU80Fm3zxmfcVe0-CYLfhBz+MCE36GRFwbrcD1bK77FuQ@mail.gmail.com,20260303084828712hk61hGnE5cz6OPRzagFj9@zte.com.cn,CAPF+HwUdfYPa=R5AHDPT6nGkG=KVTS7v6aFhwCDB9qg=muvHqw@mail.gmail.com
Date: Tue, 03 Mar 2026 17:34:43 +0800
Mime-Version: 1.0
From: zhang.zheng@zte.com.cn
To: donatas.abraitis@gmail.com
Content-Type: multipart/mixed; boundary="=====_001_next====="
X-MAIL: mse-fl1.zte.com.cn 6239YfBt073170
X-TLS: YES
X-SPF-DOMAIN: zte.com.cn
X-ENVELOPE-SENDER: zhang.zheng@zte.com.cn
X-SPF: None
X-SOURCE-IP: 10.5.228.132 unknown Tue, 03 Mar 2026 17:34:46 +0800
X-Fangmail-Anti-Spam-Filtered: true
X-Fangmail-MID-QID: 69A6AB36.001/4fQ9ck6w9gz5BNS0
Message-ID-Hash: JRS76KYSSQOIIJ6246UUWSNJUBYJUVAS
X-Message-ID-Hash: JRS76KYSSQOIIJ6246UUWSNJUBYJUVAS
X-MailFrom: zhang.zheng@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
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Idr] Re: Fw: New Version Notification for draft-zhang-idr-portid-ec-00.txt
List-Id: Inter-Domain Routing <idr.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/ePXid2Oe0tRQLQhFqQID_8u3jXo>
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 Donatas, Got it. Those are not solving the same problem. Best regards, Sandy Original From: DonatasAbraitis <donatas.abraitis@gmail.com> To: 张征00007940; Cc: idr@ietf.org <idr@ietf.org>; Date: 2026年03月03日 15:17 Subject: Re: [Idr] Fw: New Version Notification for draft-zhang-idr-portid-ec-00.txt I was referring to https://datatracker.ietf.org/doc/html/draft-acee-idr-lldp-peer-discovery. On Tue, Mar 3, 2026 at 2:48 AM <zhang.zheng@zte.com.cn> wrote: Hi Donatas, Thank you for your information. I'm not sure if the existing work you mentioned refers to this draft: https://datatracker.ietf.org/doc/html/draft-filsfils-rtgwg-lightweight-host-routing-00. If I understand correctly, this draft addresses information advertising between the Server and Leaf switches. draft-zhang-idr-portid-ec is different; it's used to advertise the interface between the Server and Leaf switches (via the Spine). The purpose, as you stated, is to resolve last-hop congestion. Cases where the Server and Leaf switches are not directly connected are not currently within the scope of this draft. If this solution were to be used, creating a tunnel between the Server and Leaf switches might be necessary. Best regards, Sandy Original From: DonatasAbraitis <donatas.abraitis@gmail.com> To: 张征00007940; Cc: idr@ietf.org <idr@ietf.org>; Date: 2026年03月03日 00:41 Subject: Re: [Idr] Fw: New Version Notification for draft-zhang-idr-portid-ec-00.txt * We already have a draft for carrying LLDP information in BGP. Wouldn't that be better to continue the work? * What happens if the server is not directly connected to the leaf? * I'm still concerned, what problem is trying to solve here? Congestion or what? On Mon, Mar 2, 2026 at 11:24 AM <zhang.zheng@zte.com.cn> wrote: Hi, This draft tries to address the issue of requiring the advertising of the connection interface between Leaf switches and servers in some implementations when deploying BGP in data centers used for AI computing. If you have experience in this deployment and implementation, or are interested in this topic, please feel free to provide suggestions and feedback. Thank you very much. Best regards, Sandy Original From: internet-drafts@ietf.org <internet-drafts@ietf.org> To: 袁冬宇10335620;Junye Zhang <zhangjunye@chinamobile.com>;张征00007940; Date: 2026年02月28日 22:03 Subject: New Version Notification for draft-zhang-idr-portid-ec-00.txt A new version of Internet-Draft draft-zhang-idr-portid-ec-00.txt has been successfully submitted by Zheng Zhang and posted to the IETF repository. Name: draft-zhang-idr-portid-ec Revision: 00 Title: BGP PORT EC for AIDC Date: 2026-02-28 Group: Individual Submission Pages: 7 URL: https://www.ietf.org/archive/id/draft-zhang-idr-portid-ec-00.txt Status: https://datatracker.ietf.org/doc/draft-zhang-idr-portid-ec/ HTML: https://www.ietf.org/archive/id/draft-zhang-idr-portid-ec-00.html HTMLized: https://datatracker.ietf.org/doc/html/draft-zhang-idr-portid-ec Abstract: This document introduces a new BGP extended community attribute for use in AI computing, which announces the port ID between Leaf switches and servers as preparation for sending large-scale traffic before initiating AI tasks. The IETF Secretariat _______________________________________________ Idr mailing list -- idr@ietf.org To unsubscribe send an email to idr-leave@ietf.org -- Donatas -- Donatas
- [Idr] Fw: New Version Notification for draft-zhan… zhang.zheng
- [Idr] Re: Fw: New Version Notification for draft-… Donatas Abraitis
- [Idr] Re: Fw: New Version Notification for draft-… zhang.zheng
- [Idr] Re: Fw: New Version Notification for draft-… Donatas Abraitis
- [Idr] Re: Fw: New Version Notification for draft-… zhang.zheng
- [Idr] Re: Fw: New Version Notification for draft-… Jeffrey Haas
- [Idr] Re: Fw: New Version Notification for draft-… zhang.zheng
- [Idr] Re: Fw: New Version Notification for draft-… Robert Raszuk
- [Idr] Re: Fw: New Version Notification for draft-… zhang.zheng