W3C home > Mailing lists > Public > w3c-ietf-xmldsig@w3.org > January to March 2002

RE: X509SubjectName and binary values

From: Gregor Karlinger <gregor.karlinger@iaik.at>
Date: Wed, 23 Jan 2002 09:36:33 +0100
To: "Herry" <herrykoh@yahoo.com>, <w3c-ietf-xmldsig@w3.org>
Message-ID: <LBEPJAONIMDADHFHAEAOIEONCMAA.gregor.karlinger@iaik.at>


> I am seeking some clarification on what is the current
> W3C RECOMMENDATION pertaining to the encoding. With
> your current proposed recommendation
> http://www.w3.org/TR/2001/PR-xmldsig-core-20010820/
> in sectin 4.4.4, it was mentioned :
> [...
> Escape all occurences of ASCII control characters
> (Unicode range \x00 - \x20) by replacing them with "\"
> followed by a two digit hex number showing its Unicode
> number. Since a XML document logically consists of
> characters, not octets, the resulting unicode string
> is finally encoded according to the character encoding
> used for producing the physical representation of the
> XML document.
> ...]
> which I take it to mean( please correct me if I am
> wrong) that for example, a (short) DName [CN=My Name]
> will translate, in the physical XML document, to
> [CN=My\20Name].
> However in the draft mentioned the mail below, the
> Unicode range was 'shortened' to (\x00 - \x1f) which
> excludes the space (with the exception of the trailing
> space)
> So if I have an application that needs to support W3C
> _proposed recommendation_, should the DName end up
> like [CN=My\20Name]?

If your application needs to support Proposed Rec, then
your example DName should be "My\20Name".

However it is likely that this will change in the Rec.
Please also follow the current discussion on clarifying
the encoding of DNames according to XMLDSIG [1],[2],[3],
[4] and its reflection in section of the current
working document [5].

[5] http://www.w3.org/Signature/Drafts/xmldsig-core


DI Gregor Karlinger
Phone +43 316 873 5541
Institute for Applied Information Processing and Communications
Received on Wednesday, 23 January 2002 03:37:24 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:21:37 UTC