Re: [netmod] A review of draft-ietf-netmod-node-tags

Qin Wu <bill.wu@huawei.com> Thu, 20 January 2022 12:01 UTC

Return-Path: <bill.wu@huawei.com>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 176EF3A0A19; Thu, 20 Jan 2022 04:01:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kbqvBhx2DKFc; Thu, 20 Jan 2022 04:01:50 -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 536253A0A07; Thu, 20 Jan 2022 04:01:50 -0800 (PST)
Received: from fraeml737-chm.china.huawei.com (unknown [172.18.147.207]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4Jfh1m0DRjz67yk2; Thu, 20 Jan 2022 20:01:32 +0800 (CST)
Received: from canpemm100008.china.huawei.com (7.192.104.152) by fraeml737-chm.china.huawei.com (10.206.15.218) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2308.21; Thu, 20 Jan 2022 13:01:46 +0100
Received: from canpemm500005.china.huawei.com (7.192.104.229) by canpemm100008.china.huawei.com (7.192.104.152) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2308.21; Thu, 20 Jan 2022 20:01:44 +0800
Received: from canpemm500005.china.huawei.com ([7.192.104.229]) by canpemm500005.china.huawei.com ([7.192.104.229]) with mapi id 15.01.2308.021; Thu, 20 Jan 2022 20:01:44 +0800
From: Qin Wu <bill.wu@huawei.com>
To: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "draft-ietf-netmod-node-tags@ietf.org" <draft-ietf-netmod-node-tags@ietf.org>
CC: "netmod@ietf.org" <netmod@ietf.org>
Thread-Topic: A review of draft-ietf-netmod-node-tags
Thread-Index: AdgN9X0oe0CTHnA6Q46lvYK40nArXA==
Date: Thu, 20 Jan 2022 12:01:44 +0000
Message-ID: <130e9f5191454d538fdcae6cba9cdaae@huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.136.100.16]
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/Cy-KhkrHcm_2ErqXIxipaAQGNqE>
Subject: Re: [netmod] A review of draft-ietf-netmod-node-tags
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: NETMOD WG list <netmod.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netmod>, <mailto:netmod-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netmod/>
List-Post: <mailto:netmod@ietf.org>
List-Help: <mailto:netmod-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netmod>, <mailto:netmod-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Jan 2022 12:01:55 -0000

Hi, Adrian:
>-----邮件原件-----
>发件人: Adrian Farrel [mailto:adrian@olddog.co.uk] 
>发送时间: 2022年1月19日 22:29
>收件人: Qin Wu <bill.wu@huawei.com>; draft-ietf-netmod-node-tags@ietf.org
>抄送: netmod@ietf.org
>主题: RE: A review of draft-ietf-netmod-node-tags

>Hi again, Qin.

>Just closing on the one remaining point.

>Adrian

>>>There is some contradiction between and within sections 4.3 and 4.4
>>>
>>>1. If a user tag is defined as any tag that has the prefix "user:"
>>>   how can you then say that users are not required to use the "user:"
>>>   prefix? That would mean that a user tag is any tag that does or
>>>   does not have the prefix "user:"
>> [Qin Wu] Correct.
>>>2. If any tag not starting with "ietf:", "vendor:", or "user:" is 
>>>   reserved, how can a user create a tag that doesn't start with
>>>   "user:"?
>> [Qin Wu] :I understand your concern, but my understanding on reserved 
>> tag,
>upon such reserved tag is allocated, it should start with "xxx:",
>>         Therefore such reserved tag can not be seen as user tag. It 
>> seems
>unlikely there is contraction if my understanding is correct.
>>         Correct me if I am wrong.
>>
>> [AF] Ah, I missed the point!

>>A user tag is:
>>- any tag with the prefix "user" 
>>or
>>- any tag that has no prefix at all

>>Thus, and for the avoidance of confusion, the colon (":") when it 
>>appears
>for the first time, is always assumed to be the separator between a prefix and the rest of the tag. And so, when a user tag does not have a prefix, it MUST NOT contain a colon. 
> [Qin Wu] Your understanding is correct, if you think I should add some text to make this more clear, I am happy to do so.

>Maybe just a sentence. I know that my confusion is not indicative of the state of the average reader, but maybe there are others who would be just as confused.

[Qin Wu] Okay, I will add a sentence in section 3.4. Thank for all these good suggestions.