IETF Logo Mail Archive

Re: [Can] The name CAN

"易昕昕(联通集团本部)" <yixx3@chinaunicom.cn> Tue, 28 February 2023 09:30 UTC

Return-Path: <yixx3@chinaunicom.cn>
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 8091DC15154D for <can@ietfa.amsl.com>; Tue, 28 Feb 2023 01:30:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.317
X-Spam-Level:
X-Spam-Status: No, score=-6.317 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, INVALID_MSGID=0.568, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=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 EEocKZAv5_AB for <can@ietfa.amsl.com>; Tue, 28 Feb 2023 01:30:38 -0800 (PST)
Received: from senda.mailex.chinaunicom.cn (senda.mailex.chinaunicom.cn [123.138.59.136]) (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 3DE35C14CE44 for <can@ietf.org>; Tue, 28 Feb 2023 01:30:32 -0800 (PST)
Received: from M10-XA-MLCEN02.MailSrv.cnc.intra (unknown [10.236.3.198]) by senda.mailex.chinaunicom.cn (SkyGuard) with ESMTPS id 4PQsZm0Qjfz3JrCx for <can@ietf.org>; Tue, 28 Feb 2023 17:32:00 +0800 (CST)
Received: from smtpbg.qq.com (10.237.2.94) by M10-XA-MLCEN02.MailSrv.cnc.intra (10.236.3.198) with Microsoft SMTP Server id 15.0.1497.42; Tue, 28 Feb 2023 17:30:26 +0800
X-QQ-mid: Ymail-xx24b003-t1677576624tk5
Received: from yixx-PC (unknown [10.2.108.70]) by smtp.qq.com (ESMTP) with id ; Tue, 28 Feb 2023 17:30:23 +0800 (CST)
X-QQ-SSF: 00900000000000C0I510000A0000000
X-QQ-GoodBg: 0
From: "易昕昕(联通集团本部)" <yixx3@chinaunicom.cn>
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" <adrian@olddog.co.uk>, can <can@ietf.org>
Date: Tue, 28 Feb 2023 17:30:24 +0800
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>
X-Priority: 3
X-Has-Attach: no
X-Mailer: Foxmail 7.2.23.119[cn]
MIME-Version: 1.0
Message-ID: <202302281730236472617@chinaunicom.cn>
Content-Type: multipart/related; boundary="----=_001_NextPart542030143008_=----"
X-QQ-SENDSIZE: 520
Feedback-ID: Ymail-xx:chinaunicom.cn:mail-xx:mail-xx24b003-zhyw42w
Archived-At: <https://mailarchive.ietf.org/arch/msg/can/GMjznPJU8BkhhtE-xZaIk55dMfY>
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: Tue, 28 Feb 2023 09:30:40 -0000

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>
Sent: 25 February 2023 13:03
To: Erik Kline <ek.ietf@gmail.com>
Cc: John Scudder <jgs@juniper.net>; Dirk Trossen <dirk.trossen@huawei.com>; adrian@olddog.co.uk; 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，即可以退订此邮件。我们将立即将您的信息从我们的发送目录中删除。 If you have received this email in error please notify us immediately by e-mail. Please reply to hqs-spmc@chinaunicom.cn ,you can unsubscribe from this mail. We will immediately remove your information from send catalogue of our.

v2.23.0 | Report a Bug | By Email