On 01/07/2022 07:33, Martin J. Dürst wrote:
Hello Tom, others,
On 2022-06-30 20:31, tom petch wrote:
Second, the 'NOTE' seems at variance with RFC5646 in that the RFC
specifies that they are case insensitive. YANG is in most respects a
lower case language and it has the concept of canonical form so my
understanding of RFC5646 is that the canonical form, in any YANG
context, would be lower case, which is not what the appendix says (not
that the appendix explicitly considers YANG but I expect tusers of
this I-D will).
I agree with what Carsten said (in a later mail): that for core-problem,
and also for CBOR in general, we are in the right spot.
Although the wording in
https://datatracker.ietf.org/doc/html/rfc5646#section-2.1.1 (pointed to
by Randy) is different, in some way it would be appropriate to call
capitalizations such zh-US-Latn-pinyin (Chinese as used in the US,
written in Latin script according to the pinyin Romanization) the
"canonical form" according to RFC 5654.
The question for YANG would be whether to force lower case, whether to
allow free case (as RFC 5646 does), or whether to force the above
capitalization. I do not know enough about the YANG ecosystem to be able
to give advice. But what YANG does definitely should not affect other
formats and protocols.
Yes, YANG needs to do what is right for YANG and not put back pressure
on other specifications. If and when there is a proposal for a YANG
type for language tags, I will push for the lower case ie as Carsten says
"So I would have used [a-z]{1,8}(-[a-z0-9]{1,8})* instead of
[a-zA-Z]{1,8}(-[a-zA-Z0-9]{1,8})* as the regexp for a language tag."
but I see that as one for the NETMOD WG perhaps with input from art if
some want mixed case:-( YANG can be a but flaky when it comes to string
comparisons. Some places it insists on lower case (e.g. 'true'
'false'), others it does not. It does have canonical forms but does not
do Unicode normalisation and does allow a very wide range of characters.
So the I-D looks ok.
Tom Petch
Regards, Martin.
.
--
last-call mailing list
last-call@xxxxxxxx
https://www.ietf.org/mailman/listinfo/last-call
