[pim] Re: LLM?
zhang.zheng@zte.com.cn Tue, 22 July 2025 12:51 UTC
Return-Path: <zhang.zheng@zte.com.cn>
X-Original-To: pim@mail2.ietf.org
Delivered-To: pim@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 55E76486A4F3 for <pim@mail2.ietf.org>; Tue, 22 Jul 2025 05:51:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.884
X-Spam-Level:
X-Spam-Status: No, score=-1.884 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, 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 F5aIfUz_T6cE for <pim@mail2.ietf.org>; Tue, 22 Jul 2025 05:51:21 -0700 (PDT)
Received: from mxhk.zte.com.cn (mxhk.zte.com.cn [160.30.148.35]) (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 93CE6486A4E6 for <pim@ietf.org>; Tue, 22 Jul 2025 05:51:19 -0700 (PDT)
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 4bmcZn6Wgrz8Xs6N; Tue, 22 Jul 2025 20:51:13 +0800 (CST)
Received: from njy2app03.zte.com.cn ([10.40.13.14]) by mse-fl1.zte.com.cn with SMTP id 56MCpBLi074873; Tue, 22 Jul 2025 20:51:11 +0800 (+08) (envelope-from zhang.zheng@zte.com.cn)
Received: from mapi (njb2app06[null]) by mapi (Zmail) with MAPI id mid203; Tue, 22 Jul 2025 20:51:14 +0800 (CST)
Date: Tue, 22 Jul 2025 20:51:14 +0800
X-Zmail-TransId: 2afe687f8942ffffffffc9e-a4678
X-Mailer: Zmail v1.0
Message-ID: <20250722205114379f4T_vro3Bf2WkhXJeQ6zi@zte.com.cn>
In-Reply-To: <F756716F-F4BD-4B09-A58B-47950B341CB0@gmail.com>
References: 20250722052619582w_F7ySFpsL4OtzJ-ZSBrH@zte.com.cn,F756716F-F4BD-4B09-A58B-47950B341CB0@gmail.com
Mime-Version: 1.0
From: zhang.zheng@zte.com.cn
To: jefftant.ietf@gmail.com
Content-Type: multipart/mixed; boundary="=====_001_next====="
X-MAIL: mse-fl1.zte.com.cn 56MCpBLi074873
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, 22 Jul 2025 20:51:13 +0800
X-Fangmail-Anti-Spam-Filtered: true
X-Fangmail-MID-QID: 687F8941.002/4bmcZn6Wgrz8Xs6N
Message-ID-Hash: WKPLXUBQ3DMLKQRWGUQFHW2O4GEQKX6Z
X-Message-ID-Hash: WKPLXUBQ3DMLKQRWGUQFHW2O4GEQKX6Z
X-MailFrom: zhang.zheng@zte.com.cn
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-pim.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: James.A.Stevens=40collins.com@dmarc.ietf.org, pim@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [pim] Re: LLM?
List-Id: Protocol Independent Multicast <pim.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/pim/R4qNKwUHvnOmsADZUMubcSZChio>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pim>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Owner: <mailto:pim-owner@ietf.org>
List-Post: <mailto:pim@ietf.org>
List-Subscribe: <mailto:pim-join@ietf.org>
List-Unsubscribe: <mailto:pim-leave@ietf.org>
Hi Jeff, Yes. You are right! We focus more on the sparse mode, such as MoE. Sandy 发自我的zMail Original From:jefftant.ietf<jefftant.ietf@gmail.com> To:张征00007940; Cc:James.A.Stevens=40collins.com@dmarc.ietf.org;pim<pim@ietf.org>; Date:2025-07-22 14:43:52 Subject:Re: [pim] Re: LLM? Sandy, Perhaps you should be more specific, there are LLMs that are based on dense transformers architecture where multicast on not really applicable. Cheers, Jeff On Jul 21, 2025, at 23:27, zhang.zheng@zte.com.cn wrote: Yes. Large language model. Sandy _______________________________________________ pim mailing list -- pim@ietf.org To unsubscribe send an email to pim-leave@ietf.org From:Stevens,Jim<James.A.Stevens=40collins.com@dmarc.ietf.org> To:pim<pim@ietf.org>; Date:2025-07-21 16:43:30 Subject:[pim] Re: LLM? _______________________________________________ pim mailing list -- pim@ietf.org To unsubscribe send an email to pim-leave@ietf.org Date: Fri, 18 Jul 2025 18:10:43 +0800 (CST) From: <zhang.zheng@zte.com.cn> Subject: [pim] Invitation to the "Multicast in LLM" side meeting (Tuesday July 22, 9:45 - 11:00 in room El Escorial) To: <pim@ietf.org> Hi, If you are familiar with LLM, or are interested in network layer multicast, and want to use network layer multicast to assist in implementing LLM's multicast operations, please come to the side meeting to discuss. What do you mean by LLM? · Large Language Model AI? (my assumption, but want to double check) · Low Latency Messaging? · Or? Thanks, Sandy
- [pim] Re: LLM? Stevens, Jim
- [pim] Re: LLM? zhang.zheng
- [pim] Re: LLM? zhang.zheng
- [pim] Re: LLM? Jeff Tantsura