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:[email protected]] 发送时间: 2022年5月26日 1:05 收件人: yuchaode <[email protected]> 抄送: Juergen Schoenwaelder <[email protected]>; [email protected]; [email protected]; Fatai Zhang <[email protected]>; Zhenghaomian <[email protected]>; liuzhoulong <[email protected]>; Chenchunhui (C) <[email protected]> 主题: 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.
_______________________________________________ netmod mailing list [email protected] https://www.ietf.org/mailman/listinfo/netmod
