[Idr] 答复: [RTGWG & IDR] Discussing the Open Scheduled fabric of AI Network
Aijun Wang <wangaijun@tsinghua.org.cn> Fri, 05 July 2024 03:00 UTC
Return-Path: <wangaijun@tsinghua.org.cn>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 93815C1D4A70; Thu, 4 Jul 2024 20:00:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.905
X-Spam-Level:
X-Spam-Status: No, score=-6.905 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GiDoAJnGYcU0; Thu, 4 Jul 2024 20:00:25 -0700 (PDT)
Received: from mail-m49198.qiye.163.com (mail-m49198.qiye.163.com [45.254.49.198]) (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 ietfa.amsl.com (Postfix) with ESMTPS id A4C15C1CAF4A; Thu, 4 Jul 2024 20:00:23 -0700 (PDT)
Received: from LAPTOP09T7970K (unknown [219.142.69.75]) by smtp.qiye.163.com (Hmail) with ESMTPA id DD12E7E01C5; Fri, 5 Jul 2024 11:00:14 +0800 (CST)
From: Aijun Wang <wangaijun@tsinghua.org.cn>
To: '霍朋飞' <huopengfei=40bytedance.com@dmarc.ietf.org>, idr@ietf.org, rtgwg@ietf.org
References: <CA++4kv88HEKoA2Mvwh0nUyM-uyR97UhDh=w9jOGVfMjASdnw8w@mail.gmail.com>
In-Reply-To: <CA++4kv88HEKoA2Mvwh0nUyM-uyR97UhDh=w9jOGVfMjASdnw8w@mail.gmail.com>
Date: Fri, 05 Jul 2024 11:00:14 +0800
Message-ID: <000501dace87$75a315e0$60e941a0$@tsinghua.org.cn>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0006_01DACECA.83C76750"
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQIR1ITPc6GYbMskLLmLageatLZx17F5XtqQ
Content-Language: zh-cn
X-HM-Spam-Status: e1kfGhgUHx5ZQUpXWQgPGg8OCBgUHx5ZQUlOS1dZFg8aDwILHllBWSg2Ly tZV1koWUFKTEtLSjdXWS1ZQUlXWQ8JGhUIEh9ZQVlCGkweVktDHkofSE8fQxkaGFYeHw5VEwETFh oSFyQUDg9ZV1kYEgtZQVlJSkJVSk9JVU1CVUxOWVdZFhoPEhUdFFlBWU9LSFVKS0lPT09IVUpLS1 VKQktLWQY+
X-HM-Tid: 0a9080d5d22903a2kunmdd12e7e01c5
X-HM-MType: 10
X-HM-Sender-Digest: e1kMHhlZQR0aFwgeV1kSHx4VD1lBWUc6NjI6Kjo5LjNDTlZKDhNNFiI4 Dw0KFD9VSlVKTElLSk9DT0pOTExOVTMWGhIXVQwaFRwaEhEOFTsPCBIVHBMOGlUUCRxVGBVFWVdZ EgtZQVlJSkJVSk9JVU1CVUxOWVdZCAFZQUlISEtDNwY+
Message-ID-Hash: LO4FMF4KR3KEL55FBAO7X7YEOJXJMX2W
X-Message-ID-Hash: LO4FMF4KR3KEL55FBAO7X7YEOJXJMX2W
X-MailFrom: wangaijun@tsinghua.org.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
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [Idr] 答复: [RTGWG & IDR] Discussing the Open Scheduled fabric of AI Network
List-Id: Inter-Domain Routing <idr.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/DP-zEYDUv2C114UD9U9UsuoGep0>
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, Pengfei: After reading your proposals, I have the following questions: 1. In your osf-framework, how you assure the sorting, fragmentation or aggregation of packet of one flow at the Ingress/Egress device does not lead to forwarding latency(also large required memory storage on these devices)? 2. For your congestion control proposal(credit-based flow control), what’s the difference from the traditional RSVP technology? 3. For your rapid link failure switchover in OSF, the main point is that the involvement of OSF-MS component that act as the central control point. Is it right? Where is the OSF-MS component in your architecture that described in section https://datatracker.ietf.org/doc/html/draft-hcl-rtgwg-osf-framework-00#section-2.2 4. And, in https://datatracker.ietf.org/doc/html/draft-hcl-rtgwg-osf-framework-00#section-3, the document states that OSF-MS components can also operate in a distributed process mode, or a hybrid mode, how do you achieve the rapid link failure switchover as AI applications required in these two modes? Best Regards Aijun Wang China Telecom 发件人: forwardingalgorithm@ietf.org [mailto:forwardingalgorithm@ietf.org] 代表 霍朋飞 发送时间: 2024年6月30日 12:57 收件人: idr@ietf.org; rtgwg@ietf.org 主题: [Idr] [RTGWG & IDR] Discussing the Open Scheduled fabric of AI Network Hi Wg, Link: <https://datatracker.ietf.org/doc/html/draft-hcl-rtgwg-ai-network-problem-00> https://datatracker.ietf.org/doc/html/draft-hcl-rtgwg-ai-network-problem-00 <https://datatracker.ietf.org/doc/html/draft-hcl-rtgwg-osf-framework-00> https://datatracker.ietf.org/doc/html/draft-hcl-rtgwg-osf-framework-00 <https://datatracker.ietf.org/doc/html/draft-hcl-idr-extend-tunnel-egress-point-00> https://datatracker.ietf.org/doc/html/draft-hcl-idr-extend-tunnel-egress-point-00 These documents describe the main disturbances caused by AI applications to the network and propose solutions based on open schedulable network architecture developed to address these issues. It primarily focuses on the following aspects: 1. Open Scheduled Fabric An open network architecture that resolves hash issues through dynamic scheduling based on network measurements. 2. Bgp Extension for Tunnel Egress Point A method for implementing the OSF network architecture involves using BGP uniformly in the control plane, extending the data plane as a new tunnel encapsulation, and providing the necessary control information transmission for the data plane. 3. Extending the BGP protocol to carry Tunnel Egress Point information within the community attribute. We welcome any comments and discussions. Thank you! Thanks, Pengfei