Re: X509SubjectName and binary values

On Thursday 13 September 2001 06:14, merlin wrote:
> Hi Christian,
> I would summarize our encoding (assuming the changes recently
> discussed on the list) as:
>
> Translation from RFC 2253 -> XMLDSIG:
>
> . UTF-8 decode the string.
> . Encode characters < ' ' as "\XY".
> . Replace any trailing "\ " in the full dname with "\20".
>
> Translation from XMLDSIG -> RFC 2253:
>
> . Replace any trailing "\20" with "\ ".
> . Replace any "\XY" with the corresponding character.
> . UTF-8 encode the string.
>
> Broadly, this is RFC 2253 without the UTF-8 encoding step,
> with all characters < ' ' encoded as "\XY" and any trailing
> "\ " in the full dname replaced with "\20".

Given no objection to my summary/proposal [1], I've moved the escape of 
whitespace to those only occuring at the end of DNAME as you proposed:

[ 
http://www.w3.org/Signature/Drafts/xmldsig-core/#sec-X509Data
$Revision: 1.123 $ on $Date: 2001/09/14 16:55:21 $
...
     * Escape all occurrences of ASCII control characters (Unicode range
       \x00 - \x [INS: 1f :INS] ) by replacing them with "\" followed by
       a two digit hex number showing its Unicode number.
     * [INS: Escape any trailing white space by replacing "\ " with
       "\20". :INS]
]

[1] 
http://lists.w3.org/Archives/Public/w3c-ietf-xmldsig/2001JulSep/0217.html

> To be honest, I would be cautious about the text that we have
> in XMLDSIG; it duplicates material from RFC 2253 and may lose
> clarity in so doing.

If you'd like to an improvement, please do!