[Dyncast] Computing-Aware Network (CAN) mailing list
Peng Liu <liupengyjy@chinamobile.com> Fri, 14 October 2022 08:32 UTC
Return-Path: <liupengyjy@chinamobile.com>
X-Original-To: dyncast@ietfa.amsl.com
Delivered-To: dyncast@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 155B8C14CE31; Fri, 14 Oct 2022 01:32:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.893
X-Spam-Level:
X-Spam-Status: No, score=-1.893 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_FONT_FACE_BAD=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham 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 1TcpoEuJEL8k; Fri, 14 Oct 2022 01:32:25 -0700 (PDT)
Received: from cmccmta2.chinamobile.com (cmccmta2.chinamobile.com [221.176.66.80]) by ietfa.amsl.com (Postfix) with ESMTP id D414CC1522C0; Fri, 14 Oct 2022 01:32:20 -0700 (PDT)
X-RM-TagInfo: emlType=0
X-RM-SPAM-FLAG: 00000000
Received: from spf.mail.chinamobile.com (unknown[172.16.121.99]) by rmmx-syy-dmz-app08-12008 (RichMail) with SMTP id 2ee863491e907c9-f2546; Fri, 14 Oct 2022 16:32:19 +0800 (CST)
X-RM-TRANSID: 2ee863491e907c9-f2546
X-RM-TagInfo: emlType=0
X-RM-SPAM-FLAG: 00000000
Received: from CMCC-LP (unknown[10.2.53.125]) by rmsmtp-syy-appsvrnew10-12035 (RichMail) with SMTP id 2f0363491e91d68-9be17; Fri, 14 Oct 2022 16:32:18 +0800 (CST)
X-RM-TRANSID: 2f0363491e91d68-9be17
Date: Fri, 14 Oct 2022 16:37:56 +0800
From: Peng Liu <liupengyjy@chinamobile.com>
To: can <can@ietf.org>, dyncast <dyncast@ietf.org>
Cc: rtgwg <rtgwg@ietf.org>
X-Priority: 3
X-GUID: C348C016-3773-4D38-93F8-2AF8C5FDB0E8
X-Has-Attach: no
X-Mailer: Foxmail 7.2.21.453[cn]
Mime-Version: 1.0
Message-ID: <2022101416375635458125@chinamobile.com>
Content-Type: multipart/alternative; boundary="----=_001_NextPart314018532501_=----"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dyncast/cre8pzJK7hyVc31-t-ZyWdaP2H0>
Subject: [Dyncast] Computing-Aware Network (CAN) mailing list
X-BeenThere: dyncast@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Dynamic Anycast <dyncast.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dyncast>, <mailto:dyncast-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dyncast/>
List-Post: <mailto:dyncast@ietf.org>
List-Help: <mailto:dyncast-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dyncast>, <mailto:dyncast-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Oct 2022 08:32:29 -0000
Dear All, Thank you for supporting the dyncast work. We have cooperated on dyncast for several years, and reached some consensus on the problem space and use cases. We had a CAN(Wider space than Dyncast) BoF at IETF 113, and now we will have the second CAN BOF (WG-forming) in IETF 115. Through long discussion in emails and meetings, the CAN work is focusing on discussing the use cases, gap analysis, requirements, etc, of how the traditional routing decision processes on ingress nodes are influenced by the edge data centers' computing-related resource metrics. The work items may include characterization of the computing resources metrics, distribution of the metrics, and potential usage of the metrics. Till now, we do not pre-assume any solution has been selected, and it is still open for discussion. Therefore in the next CAN BOF, we will focus on the topics of use case, gap analysis, and then discuss the charter directly without discussing solutions since it is too early now. Because people are talking about CAN not limited to the dyncast solution (even exclude dyncast in this stage), it may be better to apply for a new mailing list of CAN. So we applied for it and hope you can subscribe the new mailing list as well: https://www.ietf.org/mailman/listinfo/can. In order to smoothly moving from dyncast to CAN, we encourage people to send emails to CAN mailing list and dyncast mailing list simultaneously when discussing related topics in the following days or months. We also cc rtgwg considering if there is someone interested in the CAN work but have not subscribe the dyncast mailing list. Thank you for your contributions, wish to see more contributions to CAN. Regards, CAN proponents liupengyjy@chinamobile.com