All,
Paul asked what is PKIX doing for UTF-8.
Carlisle Adams is including the following text in the PKIX Certificate
Management Protocol I-D (aka PKIX Part 3) in which an OCTET STRING is used
to carry a UTF-8 string:
PKIFreeText ::= SEQUENCE {
languageTag PrintableString OPTIONAL, --RFC 1766 language tag
text OCTET STRING --carries a UTF-8 string
} -- the languageTag field may be used to indicate the language
-- of the text contained in the "text" field
There are no occurrences of "UTF" in the PKIX X.509 Certrificate and CRL
Profile (aka PKIX Part 1).
Therefore, I recommend that we leave ESS as is:
ESSPrivacyMark ::= CHOICE {
pString PrintableString (SIZE (1..ub-privacy-mark-length)),
utf8String OCTET STRING
-- If utf8String is used, the contents must be in UTF-8 [UTF8]
}
================================
John Pawling
jsp(_at_)jgvandyke(_dot_)com
J.G. Van Dyke & Associates, Inc.
================================
At 04:02 PM 2/16/98 -0800, Paul Hoffman / IMC wrote:
If this is the case, and UTF8String has UNIVERSAL 12 as its tag, I
recommend that we use that tag instead of OCTET STRING to package our
UTF8 strings. I don't know what PKIX is doing regarding this, but I
suspect that they should do the same thing.
Well, I just turned in the next ESS draft, and I coded it as OCTET STRING. I'm
happy to change it in the one after this, as long as we're doing exactly what
the PKIX people are. Carlisle, what are you going to do in PKIX part 3? Russ,
how about PKIX part 1?
--Paul Hoffman, Director
--Internet Mail Consortium