IETF Logo Mail Archive

Re: [Can] The name CAN

Dirk Trossen <dirk.trossen@huawei.com> Fri, 24 February 2023 15:27 UTC

Return-Path: <dirk.trossen@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 A0D57C14CF09 for <can@ietfa.amsl.com>; Fri, 24 Feb 2023 07:27:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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 o6aDQWMe3-wF for <can@ietfa.amsl.com>; Fri, 24 Feb 2023 07:27:35 -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 C0D59C14CEF9 for <can@ietf.org>; Fri, 24 Feb 2023 07:27:35 -0800 (PST)
Received: from lhrpeml500005.china.huawei.com (unknown [172.18.147.207]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4PNYcN0RNtz67D3d; Fri, 24 Feb 2023 23:25:24 +0800 (CST)
Received: from lhrpeml500003.china.huawei.com (7.191.162.67) by lhrpeml500005.china.huawei.com (7.191.163.240) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.17; Fri, 24 Feb 2023 15:27:32 +0000
Received: from lhrpeml500003.china.huawei.com ([7.191.162.67]) by lhrpeml500003.china.huawei.com ([7.191.162.67]) with mapi id 15.01.2507.017; Fri, 24 Feb 2023 15:27:32 +0000
From: Dirk Trossen <dirk.trossen@huawei.com>
To: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "can@ietf.org" <can@ietf.org>
Thread-Topic: [Can] The name CAN
Thread-Index: AdlIWK+WM35HVwzERaasLsGUAEafZAAC4+EA
Date: Fri, 24 Feb 2023 15:27:32 +0000
Message-ID: <6ecb44f52676429f97f57ae3e353e208@huawei.com>
References: <0e9501d94859$ceda4300$6c8ec900$@olddog.co.uk>
In-Reply-To: <0e9501d94859$ceda4300$6c8ec900$@olddog.co.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.45.151.215]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/can/76RK7SWUXeYr00Xd4BoXT7Z6_UQ>
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: Fri, 24 Feb 2023 15:27:39 -0000

Hi Adrian, all,

Problem with acronyms is the small space that three letters give you in a crowded area like Internet tech. 

Anyways, for the sake of possibly focusing the rather broad 'networking' word on the aspect of 'networking' that we may care most about, together with a possibly funny note, how about CATS: Compute-Aware Traffic Steering? 

Best,

Dirk

-----Original Message-----
From: Can <can-bounces@ietf.org> On Behalf Of Adrian Farrel
Sent: 24 February 2023 15:11
To: can@ietf.org
Subject: [Can] The name CAN

Hi,

I just received a comment that "CAN" is not a very helpful name. They pointed out that if you search online for "CAN networking" you mainly get "Controller Area Network".

I would say that "CAN IETF" hits our Datatracker page as the first hit.

Remembering RFC 5513, I think we would struggle for a different name. Certainly, "Service Aware Networking (SAN)" would be equally unhelpful. I am not recommending a change.

We really only have until the IESG meets on Thursday next week to make any change. So, if you have a strong opinion that we should change, please speak now and make a suggestion.

There is no need to comment if you think we should stay as we are, or if you don't care. Silence will not cause any changes 😊

Cheers,
Adrian

-- 
Can mailing list
Can@ietf.org
https://www.ietf.org/mailman/listinfo/can

v2.23.0 | Report a Bug | By Email