IETF Logo Mail Archive

Re: [Dyncast] [Can] Scope and suggested charter statement for Computing Aware Networking(CAN)

"Shihang(Vincent)" <shihang9@huawei.com> Mon, 31 October 2022 03:28 UTC

Return-Path: <shihang9@huawei.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 9FE64C14F749; Sun, 30 Oct 2022 20:28:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.907
X-Spam-Level:
X-Spam-Status: No, score=-6.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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 FX4GfPxLrq-b; Sun, 30 Oct 2022 20:28:48 -0700 (PDT)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 88D55C14F722; Sun, 30 Oct 2022 20:28:48 -0700 (PDT)
Received: from fraeml736-chm.china.huawei.com (unknown [172.18.147.200]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4N0z8h2chSz686KW; Mon, 31 Oct 2022 11:26:44 +0800 (CST)
Received: from kwepemi500022.china.huawei.com (7.221.188.64) by fraeml736-chm.china.huawei.com (10.206.15.217) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.31; Mon, 31 Oct 2022 04:28:45 +0100
Received: from kwepemi500020.china.huawei.com (7.221.188.8) by kwepemi500022.china.huawei.com (7.221.188.64) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.31; Mon, 31 Oct 2022 11:28:43 +0800
Received: from kwepemi500020.china.huawei.com ([7.221.188.8]) by kwepemi500020.china.huawei.com ([7.221.188.8]) with mapi id 15.01.2375.031; Mon, 31 Oct 2022 11:28:43 +0800
From: "Shihang(Vincent)" <shihang9@huawei.com>
To: Peng Liu <liupengyjy@chinamobile.com>, can <can@ietf.org>, dyncast <dyncast@ietf.org>, 张佳兴 <zhangjiaxing20g@ict.ac.cn>
Thread-Topic: [Can] Scope and suggested charter statement for Computing Aware Networking(CAN)
Thread-Index: AQHY65yJqnuNFbpIpkCYrcJZqNkQMK4n05lQ
Date: Mon, 31 Oct 2022 03:28:43 +0000
Message-ID: <7a51d84597fb4a4c999e598211ba6576@huawei.com>
References: <DB841E37-3092-4D3B-B59C-75611627D316@futurewei.com>, <2a876605.4069.18423cfaa99.Coremail.zhangjiaxing20g@ict.ac.cn> <20221029214925550849399@chinamobile.com>
In-Reply-To: <20221029214925550849399@chinamobile.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.112.41.128]
Content-Type: multipart/alternative; boundary="_000_7a51d84597fb4a4c999e598211ba6576huaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/dyncast/IfhGRWG19P4LIhMGLZ7Y8_rf5qA>
Subject: Re: [Dyncast] [Can] Scope and suggested charter statement for Computing Aware Networking(CAN)
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: Mon, 31 Oct 2022 03:28:53 -0000

Hi Peng,

Thanks for your work.
1 comment below:


> CAN allows ingress nodes to consider computing-related resource

> conditions in routing decisions. As such, the CAN WG may develop an

> informational document, or create a design team, to define use cases,

> gap analysis, requirements, characterization of the computing-related

> resources, and how those conditions impact the ingress nodes routing decision process.

Do we need to put the “create design team” in charter? I assume every WG is free to create the design team as it see fit.

Best,
Hang Shi

From: Can <can-bounces@ietf.org> On Behalf Of Peng Liu
Sent: Saturday, October 29, 2022 9:49 PM
To: can <can@ietf.org>; dyncast <dyncast@ietf.org>; 张佳兴 <zhangjiaxing20g@ict.ac.cn>
Subject: [Can] Scope and suggested charter statement for Computing Aware Networking(CAN)

Hi Jason, All,

Thanks for mentioning that. The suggested scope and charter statement for CAN could be found at https://github.com/CAN-IETF/CAN-BoF-ietf115/blob/main/README.md. It described the overview of CAN, motivations , use cases, brief gap analysis, technical directions, work items and milestones. We would like to invite all the people who are interested in this work to review and comments on it.

BTW, the updated problem statement&usecase, gap analysis&requirements drafts could be found at https://datatracker.ietf.org/wg/can/documents/. Any comments on the drafts are also welcome.

Regards,
Peng
________________________________
liupengyjy@chinamobile.com<mailto:liupengyjy@chinamobile.com>

v2.23.0 | Report a Bug | By Email