Re: [Can] The name CAN

Lizhenbin <lizhenbin@huawei.com> Wed, 01 March 2023 14:39 UTC

Return-Path: <lizhenbin@huawei.com>
X-Original-To: can@ietfa.amsl.com
Delivered-To: can@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B94A6C14F5E0 for <can@ietfa.amsl.com>; Wed, 1 Mar 2023 06:39:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.197
X-Spam-Level:
X-Spam-Status: No, score=-4.197 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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 FMMLJeDV2NX2 for <can@ietfa.amsl.com>; Wed, 1 Mar 2023 06:39:40 -0800 (PST)
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 A6670C14EAA3 for <can@ietf.org>; Wed, 1 Mar 2023 06:39:39 -0800 (PST)
Received: from lhrpeml100004.china.huawei.com (unknown [172.18.147.226]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4PRcM26PWqz6J72S for <can@ietf.org>; Wed, 1 Mar 2023 22:39:26 +0800 (CST)
Received: from dggpemm500006.china.huawei.com (7.185.36.236) by lhrpeml100004.china.huawei.com (7.191.162.219) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.21; Wed, 1 Mar 2023 14:39:35 +0000
Received: from dggpemm500008.china.huawei.com (7.185.36.136) by dggpemm500006.china.huawei.com (7.185.36.236) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.21; Wed, 1 Mar 2023 22:39:33 +0800
Received: from dggpemm500008.china.huawei.com ([7.185.36.136]) by dggpemm500008.china.huawei.com ([7.185.36.136]) with mapi id 15.01.2507.021; Wed, 1 Mar 2023 22:39:33 +0800
From: Lizhenbin <lizhenbin@huawei.com>
To: "易昕昕(联通集团本部)" <yixx3@chinaunicom.cn>, Dirk Trossen <dirk.trossen=40huawei.com@dmarc.ietf.org>, Dhruv Dhody <dhruv.ietf@gmail.com>, Erik Kline <ek.ietf@gmail.com>
CC: John Scudder <jgs@juniper.net>, "adrian@olddog.co.uk" <adrian@olddog.co.uk>, can <can@ietf.org>
Thread-Topic: [Can] The name CAN
Thread-Index: AdlIWK+WM35HVwzERaasLsGUAEafZAAC4+EAAAF4JwAAAAfAAP//kfOAgAE1sYCAAuKUgIACMBUV//+wmUA=
Date: Wed, 01 Mar 2023 14:39:33 +0000
Message-ID: <cca24b41b88743e2a190cfa2156ac90a@huawei.com>
References: <0e9501d94859$ceda4300$6c8ec900$@olddog.co.uk>, <6ecb44f52676429f97f57ae3e353e208@huawei.com>, <87F334FF-B190-4FCD-9A49-7A9B002DADB8@juniper.net>, <C28573EA-F272-4EC8-B3E7-282D9B16FC24@juniper.net>, <CAMGpriXvzDEH4oQAd7gyoxdtLfvZBFCxk6T+oxXHX6-0zvOOhA@mail.gmail.com>, <CAB75xn5ZDNTv1ANdiAsZBnfpb--wWhwypNUdhCaRYXwbqQcsfQ@mail.gmail.com>, <ee32b11af37f4cfcb56b7a41801f1030@huawei.com> <202302281730236472617@chinaunicom.cn>+AF26A1166EAC15F9
In-Reply-To: <202302281730236472617@chinaunicom.cn>+AF26A1166EAC15F9
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [10.48.118.203]
Content-Type: multipart/related; boundary="_004_cca24b41b88743e2a190cfa2156ac90ahuaweicom_"; type="multipart/alternative"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/can/oJxXP1RaaBMKt7AUpnJ_3QTrUeo>
Subject: Re: [Can] The name CAN
X-BeenThere: can@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: CAN- Computing-Aware Networking <can.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/can>, <mailto:can-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/can/>
List-Post: <mailto:can@ietf.org>
List-Help: <mailto:can-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/can>, <mailto:can-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Mar 2023 14:39:41 -0000

Hi All,
If the name CAN need to change,  I prefer to the names of “CA” with “R” (such as CAR, CARP, CARN, or others). For the CAN work, it is necessary for the network to learn the compute status. After learning the compute status, there can be multiple usages beyond traffic steering, such as visibility of compute and network status for the purpose of fault detection or service provision. IMHO, the scope of the “Traffic Steering”  is a little too specific and it is better to keep some extensibility.


Best Regards,
Zhenbin



From: Can [mailto:can-bounces@ietf.org] On Behalf Of 易昕昕(联通集团本部)
Sent: Tuesday, February 28, 2023 5:30 PM
To: Dirk Trossen <dirk.trossen=40huawei.com@dmarc.ietf.org>; Dhruv Dhody <dhruv.ietf@gmail.com>; Erik Kline <ek.ietf@gmail.com>
Cc: John Scudder <jgs@juniper.net>; adrian@olddog.co.uk; can <can@ietf.org>
Subject: Re: [Can] The name CAN

I think CATS is a better choice, traffic steering should be mentioned. I wonder if it makes more sense to replace “Traffic Steering” by “Routing”, since the routing work is extremely necessary. As for CARP, “Protocol” can’t cover all of our work.
So we suggest two concepts as below:

  *   CARN: Computing Aware Routing Network
  *   CAR: Computing Aware Routing

     Thanks.

________________________________
Xinxin Yi

发件人: Dirk Trossen<mailto:dirk.trossen=40huawei.com@dmarc.ietf.org>
发送时间: 2023-02-27 16:06
收件人: Dhruv Dhody<mailto:dhruv.ietf@gmail.com>; Erik Kline<mailto:ek.ietf@gmail.com>
抄送: John Scudder<mailto:jgs@juniper.net>; adrian@olddog.co.uk<mailto:adrian@olddog.co.uk>; can@ietf.org<mailto:can@ietf.org>
主题: [警惕!外部邮件]Re: [Can] The name CAN
Yes, but we have multi-instance based decision at the heart of the traffic steering, so CATS makes sense [cid:_Foxmail.1@9a899d2c-8392-671e-570a-db0a7ab880ca]

From: Dhruv Dhody <dhruv.ietf@gmail.com<mailto:dhruv.ietf@gmail.com>>
Sent: 25 February 2023 13:03
To: Erik Kline <ek.ietf@gmail.com<mailto:ek.ietf@gmail.com>>
Cc: John Scudder <jgs@juniper.net<mailto:jgs@juniper.net>>; Dirk Trossen <dirk.trossen@huawei.com<mailto:dirk.trossen@huawei.com>>; adrian@olddog.co.uk<mailto:adrian@olddog.co.uk>; can@ietf.org<mailto:can@ietf.org>
Subject: Re: [Can] The name CAN

I like CATS! Both as a name of the proposed WG as well as the actual furry beast :)

BTW SEC also had CAT [1] way back!

Dhruv

[1] https://datatracker.ietf.org/wg/cat/about/

On Fri, Feb 24, 2023 at 11:05 PM Erik Kline <ek.ietf@gmail.com<mailto:ek.ietf@gmail.com>> wrote:
Whereas CAT[S]bus already has a non-colliding meaning<https://www.google.com/search?q=catbus&tbm=isch>.  =)

SEC has KITTEN, RTG can definitely have CATS.  (+1)

On Fri, Feb 24, 2023 at 8:08 AM John Scudder <jgs=40juniper.net@dmarc.ietf.org<mailto:40juniper.net@dmarc.ietf.org>> wrote:
I had meant to add, the collision with CANbus while not awful, isn’t exactly a desirable thing either.

—John
--
Can mailing list
Can@ietf.org<mailto:Can@ietf.org>
https://www.ietf.org/mailman/listinfo/can
--
Can mailing list
Can@ietf.org<mailto:Can@ietf.org>
https://www.ietf.org/mailman/listinfo/can
如果您错误接收了该邮件,请通过电子邮件立即通知我们。请回复邮件到 hqs-spmc@chinaunicom.cn,即可以退订此邮件。我们将立即将您的信息从我们的发送目录中删除<mailto:hqs-spmc@chinaunicom.cn,即可以退订此邮件。我们将立即将您的信息从我们的发送目录中删除>。 If you have received this email in error please notify us immediately by e-mail. Please reply to hqs-spmc@chinaunicom.cn<mailto:hqs-spmc@chinaunicom.cn> ,you can unsubscribe from this mail. We will immediately remove your information from send catalogue of our.