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

[Qin Wu <[e-mail]>]

Hi, Michael:
Quote text in section 4.1 of RFC9907,
"
   All published module names MUST be unique.  For a YANG module
   published in an RFC, this uniqueness is guaranteed by IANA
   (Section 14 of [RFC6020]).

   Example modules are non-normative and SHOULD be named with the prefix
   "example-".

   It is suggested that a stable module name prefix be selected that
   represents the entire organization.  All normative YANG modules
   published by the IETF MUST begin with the prefix "ietf-".  All IANA-
   maintained YANG modules MUST begin with the prefix "iana-".  Another
   standards organization, such as the IEEE, might use the prefix
   "ieee-" for all YANG modules.
"
For vendor specific module, I think the enterprise or organization-name should be used,
Similar to example modules, organization specific module.

Also see quoted text in section 5.3 of RFC7950
"
   XML namespaces for private modules are assigned by the organization
   owning the module without a central registry.  Namespace URIs MUST be
   chosen so they cannot collide with standard or other enterprise
   namespaces -- for example, by using the enterprise or organization
   name in the namespace.
"

Further see module tag RFC, section 2.2
"
2.2. Vendor Tags
A vendor tag is a tag that has the prefix "vendor:". These tags are defined by the vendor
 that implements the module and are not registered; however, it is RECOMMENDED that
 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).
"
It also indicate to use enterprise or organization name for vendor tags, same rule can be applied to modules.

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


Mahesh Jethanandani <[e-mail]> wrote:
    > Different vendors use different names/namespaces. See this folder for
    > how different vendors have named their modules.

I'm trying to resolve the question of uniqueness in RFC8366bis' "extensions"
registry.
Here is what I've written now:
https://github.com/anima-wg/voucher/commit/ada220e5#diff-f2a46f5f7515ce785de390697118abc6ef7052d42b52ddc672828dc7c09d0b02L1158-R1156

   Extension name strings for IETF process (standards track, experimental,
   IRTF) documents are single words, given by the YANG Module Name: They do
   not contain dots.

   For vendor proprietary extensions, (including ISE submissions), the
   resulting string still needs to be unique.  This can be done by
   making the YANG module unique, basing it on a fully-qualified domain
   name (FQDN) [RFC3696], such as "fuubar.example.com-mud-thing" rather
   than "fuubar-mud-thing"


--
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 **