[netmod] Re: vendor proprietary YANG modules: how are they named?

[Qin Wu <[e-mail]>]

-----邮件原件-----
发件人: Michael Richardson [mailto:[e-mail]] 
发送时间: 2026年8月11日 3:32
收件人: Qin Wu <[e-mail]>
抄送: Mahesh Jethanandani <[e-mail]>; netmod <[e-mail]>
主题: Re: [netmod] Re: vendor proprietary YANG modules: how are they named?


Qin Wu <[e-mail]> wrote:
    > For vendor specific module, I think the enterprise or organization-name should be used,
    > Similar to example modules, organization specific module.

Can you give me an example?
The YANG module name: "example.org-bgp-obscure-types" seems valid.
The only caveat is maybe org.example-obscure-types would be a better convention.

[Qin Wu] The typical example is enterprise or organization-name following by product-name or platform-name and/or network function or network feature name,
Or enterprise or organization-name following directly with network function or network feature name
e.g., Cisco-IOS-XR-8000-fib-platform-cfg.yang, huawei-bgp-mvpn-deviations-NE8000.yang

Also based on identifiers rule in section 4.3 of RFC9907,
"
   All YANG identifiers in published modules MUST be between 1 and 64
   characters in length.
"
I think this rule should also be applied to module name.

    > the vendor include extra identification in the tag to avoid collisions, such as using the
    > enterprise or organization name following the "vendor:" prefix (e.g.,
    > vendor:example.com:vendor-defined-classifier).

I'm not sure how this relates to the YANG module name, as this seems to be about the XML name, right?

[Qin Wu] You are correct.
--
Michael Richardson <[e-mail]>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide

**       My working hours and your working hours may be different.         **
** Please do not feel obligated to reply outside your normal working hours **