"Valery Smyslov" <smyslov.i...@gmail.com> writes:
Hi William,
Hi Valery,
I would also add that if this field is left, then the issues
with its language must be addressed.
In particular, a compliance with BCP18 is needed.
It just comes up to my mind that the “string” type is widely used in
YANG modules. But I didn’t see any with a language indictor. I wonder
how YANG modules handle this issue.
I don’t know. Perhaps those strings are not transferred on
the wire and are not presented to end user.
I do know. Language is not specified, the strings are sent over the wire, they
are presented to the user, and it's working just fine. Thank you for the
obvious example of why we don't need to argue/rat-hole over this anymore. :)
Thanks,
Chris.
BCP18 (RFC 2277) states in Section 4.2:
Protocols that transfer text MUST provide for carrying information
about the language of that text.
Protocols SHOULD also provide for carrying information about the
language of names, where appropriate.
and in Section 4.4:
Protocols where users have text presented to them in response to
user
actions MUST provide for support of multiple languages.
Regards,
Valery.
Regards & Thanks！
Wei PAN (潘伟)
_______________________________________________
IPsec mailing list -- ipsec@ietf.org
To unsubscribe send an email to ipsec-le...@ietf.org
_______________________________________________
IPsec mailing list -- ipsec@ietf.org
To unsubscribe send an email to ipsec-le...@ietf.org
