[netmod] 答复: A question about YANG identifier design

yuchaode <yuchaode@huawei.com> Thu, 26 May 2022 03:12 UTC

Return-Path: <yuchaode@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 AAA9FC3B01E6 for <netmod@ietfa.amsl.com>; Wed, 25 May 2022 20:12:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.896
X-Spam-Level:
X-Spam-Status: No, score=-6.896 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, 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 gWIs-98FHL-f for <netmod@ietfa.amsl.com>; Wed, 25 May 2022 20:12:07 -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 9CBB3C3A9171 for <netmod@ietf.org>; Wed, 25 May 2022 20:12:07 -0700 (PDT)
Received: from fraeml711-chm.china.huawei.com (unknown [172.18.147.207]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4L7tDw5G05z67DpL; Thu, 26 May 2022 11:08:48 +0800 (CST)
Received: from canpemm500004.china.huawei.com (7.192.104.92) by fraeml711-chm.china.huawei.com (10.206.15.60) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.24; Thu, 26 May 2022 05:12:01 +0200
Received: from canpemm500002.china.huawei.com (7.192.104.244) by canpemm500004.china.huawei.com (7.192.104.92) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.24; Thu, 26 May 2022 11:12:00 +0800
Received: from canpemm500002.china.huawei.com ([7.192.104.244]) by canpemm500002.china.huawei.com ([7.192.104.244]) with mapi id 15.01.2375.024; Thu, 26 May 2022 11:12:00 +0800
From: yuchaode <yuchaode@huawei.com>
To: 'Kent Watsen' <kent+ietf@watsen.net>
CC: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>, "netmod@ietf.org" <netmod@ietf.org>, Fatai Zhang <zhangfatai@huawei.com>, Zhenghaomian <zhenghaomian@huawei.com>, liuzhoulong <liuzhoulong@huawei.com>, "Chenchunhui (C)" <chenchunhui@huawei.com>
Thread-Topic: [netmod] A question about YANG identifier design
Thread-Index: AQHYcFmVFv9Qp7L1cEidXDA4QdN0Nq0weVlg
Date: Thu, 26 May 2022 03:12:00 +0000
Message-ID: <e4a2925caf354fe98100576ddd621c79@huawei.com>
References: <de9b838f10a448c9991d0a381d426716@huawei.com> <20220524101546.cfzkzi55dsutfyic@anna> <f97fd7815d8147a680798dd5159f0594@huawei.com> <20220525072213.udkoy7lejf2qk2iq@anna> <c85dc299766941f7b3749c1572c6ccb3@huawei.com> <20220525081828.kwpbiw43ck4wizw2@anna> <9af6251a5fbe4c338bace6cccece1cde@huawei.com> <20220525083544.ymzco56byey5zt4w@anna> <86c348fb32b14dda97644c8893057588@huawei.com> <01000180fc2d869d-8284af4c-ba30-4e21-9824-d99d03f260f3-000000@email.amazonses.com>
In-Reply-To: <01000180fc2d869d-8284af4c-ba30-4e21-9824-d99d03f260f3-000000@email.amazonses.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.117.175.195]
Content-Type: multipart/alternative; boundary="_000_e4a2925caf354fe98100576ddd621c79huaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/lISwYsSjTpz0kjICk7s_dV-PDTc>
Subject: [netmod] 答复: A question about YANG identifier design
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.34
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, 26 May 2022 03:12:12 -0000

Thanks Kent,

I think the common understanding with me for the benefit of string format is that string format is generic and easy for implementation. But I am still confused how can this URI string can help to correlate identifiers across systems. Could you help to provide some more detail information?

B.R.
Chaode

发件人: Kent Watsen [mailto:kent+ietf@watsen.net]
发送时间: 2022年5月26日 1:05
收件人: yuchaode <yuchaode@huawei.com>
抄送: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>; netmod@ietf.org; netconf@ietf.org; Fatai Zhang <zhangfatai@huawei.com>; Zhenghaomian <zhenghaomian@huawei.com>; liuzhoulong <liuzhoulong@huawei.com>; Chenchunhui (C) <chenchunhui@huawei.com>
主题: Re: [netmod] A question about YANG identifier design


Thank you all the same for your comments!
And I also find peaple who are designing YANG module in IETF don’t like to use uuid. They prefer to use a string for identifier. String type is generic and easy for implementation but there is not a good way to make it global unique and easy for reference.

It's notable that RFC 8345 uses URIs, the reasoning for doing so is described in Section 4.4.11.<https://datatracker.ietf.org/doc/html/rfc8345#section-4.4.11> Identifiers of String or URI Type.

PS: though the draft says that all the identifiers are URIs, all the examples in the draft use simple strings.  AFAICT, none of the examples in that draft would pass validation.

K.