W3C home > Mailing lists > Public > public-xmlsec-maintwg@w3.org > May 2007

Re: Get test case for E01 / DName Issues

From: Sean Mullan <Sean.Mullan@Sun.COM>
Date: Wed, 30 May 2007 13:30:24 -0400
To: Ed Simon <edsimon@xmlsec.com>
Cc: public-xmlsec-maintwg@w3.org
Message-id: <465DB4B0.2000501@sun.com>

Ed Simon wrote:
> I've re-reviewed the material and think I agree with Thomas. However, I do
> have a suggested rewrite of the text:
> 
> <section>
> <heading>DName Encoding</heading>
> <p>Except for DName AttributeValues that have a string representation,
> DNames (X509IssuerSerial,X509SubjectName, and KeyName if appropriate) should
> be encoded in accordance with RFC2253 [LDAP-DN]. DName AttributeValues that
> have a string representation should be encoded in accordance with RFC2253
> [LDAP-DN] with the following exceptions:</p>
> <ul>
> <li>Escape any trailing white space by replacing "\ " with "\20".</li>
> <li>Escape all occurrences of ASCII control characters (Unicode range \x00 -
> \x1f) by replacing them with "\" followed by a two digit hex number showing
> its Unicode number.</li>
> </ul>
> </section>
> <<<
> 
> In the above, I have removed the discussion of XML escaping and such -- that
> to me is just the fundamentals of XML. Personally, I would recommend
> applications use CDATA sections around DNames and MgmtData.

But wouldn't that require a change to the DTD, since DN Strings are 
currently specified as PCDATA?

--Sean
Received on Wednesday, 30 May 2007 17:31:13 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:22:00 GMT