Relax rules for identityref representation without a prefix

[abierman]

Problem

There are several YANG modules that have must/when XPath that compares an identityref leaf to a string literal.

          uses terminal-otn-protocol-top {
              when "config/logical-channel-type = 'PROT_OTN'" {
              description
                "Include the OTN protocol data only when the
                 channel is using OTN framing.";
            }
        }

The strict rules in the RFC (sec 9.10) say that the identity (e.g. PROT_OTN) MUST be defined in the current module.

This is often not done.

• It is not enforced by all tools
• The same unprefixed string literal does not mean the same thing in a NETCONF message
• Servers usually accept unprefixed strings to match against all known identities.

Solution

• Change sec 9.10.3 to allow a 'must' or when' expression to treat an unprefixed identity string to be checked in the default module as defined, but if not found, then can be found in any imported module

[schoenw]

What happens if the string matches multiple definitions?

If we allow leaving out prefixes in situations where there is no ambiguity, should we not do this systematically and not just in when/must expressions? Having to remember where I am allowed to leave out prefixes and where not may make it harder to write proper YANG. (I do not know whether any good language servers exist for YANG but tools like that can also take care of getting the details straight.)

[schoenw]

I guess we did insist on unambiguous identifiers to prevent situations where an update of an imported module suddenly causes name clashes in importing modules. So it is a question of convenience vs. robustness; if you don't like surprises, better use fully qualified names.

[abierman]

Agree to close this issue. Leaving out the prefix is a common issue. In general we should make YANG easier to use. This would change the meaning of a missing prefix.

Close: complexity: medium, bc: low, importance: low