Convention for ITU-T Recommendations

[italobusi]

I am not sure if there is any convention in YANG modeling to use or not use "." in variable names. For example, in iana-if-type.yang it uses "identity ieee8023adLag" as opposed to "802.3". Maybe just removing ".", to make it like G652, G653.

Originally posted by @agva123 in #25 (comment)

• To be discussed during IETF-111 CCAMP WG presentation

[italobusi]

According to https://datatracker.ietf.org/doc/html/rfc8407#section-4.3.1:

Identifiers SHOULD follow a consistent naming pattern throughout the
module. Only lowercase letters, numbers, and dashes SHOULD be used
in identifier names. Uppercase characters, the period character, and
the underscore character MAY be used if the identifier represents a
well-known value that uses these characters. YANG does not permit
any other characters in YANG identifiers.

I think that RFC8407 allows using the . for ITU-T Recommendation numbers since it is a well-know value

[sergiobelotti]

April 11 weekly call:
Aihua: If it is not prohibit the usage of "." , we can use the "." also in YANG statements.

[sergiobelotti]

the last decision is that "If it is not prohibit the usage of "." , we can use the "." also in YANG statements.
RFC8407 allows using the "." for ITU-T Recommendation numbers since it is a well-know value (see above #26 (comment))