pktcMtaDevRealmName
"Randy Presuhn" <[email protected]>
| Newsgroups | gmane.ietf.ipcdn |
|---|---|
| Message-ID | <009001c50358$7a9026c0$7f1afea9@oemcomputer> |
Hi - I think the use of SnmpAdminString for pktcMtaDevRealmName might need some more thought. The language about "all capitals" and search operations using upper-case ASCII doesn't mesh too well with SnmpAdminString. Whether it makes any sense at all will depend on whether Kerberos will ever permit realm names which are not upper-case ASCII. For several writing systems, there is no upper-case/lower-case distinction. Chinese, Thai, Cambodian, and Japanese are just a few examples. Even for languages written with the Roman alphabet, there are problems. German "?" (which supposedly cannot be capitalized, and > should be transformed to "SS") is a classic example. > > If they're trying to future-proof things, they should take a > careful look at > http://www.unicode.org/versions/Unicode4.0.0/ch05.pdf#G21180 > as well as http://www.unicode.org/reports/tr15/, since they > really should > nail down which normalization form as well. (Actually, the choice of > normalization form is something we should have done in the definition > of SnmpAdminString, but no one else wanted to touch the issue then.) > > My advice, not knowing what the future of Kerberos will be and how it > will handle comparison of non-ascii realm names, is to just make this > object a DisplayString, and to spell out exactly what > characters are permitted. > > Randy