W3C home > Mailing lists > Public > w3c-ietf-xmldsig@w3.org > April to June 2001

RE: DName encoding (was:KeyName white space)

From: Joseph M. Reagle Jr. <reagle@w3.org>
Date: Wed, 20 Jun 2001 14:23:43 -0400
Message-Id: <4.3.2.7.2.20010620131624.00ba0e28@localhost>
To: "Gregor Karlinger" <gregor.karlinger@iaik.at>
Cc: <w3c-ietf-xmldsig@w3.org>
Ok, done.

[
        http://www.w3.org/Signature/Drafts/xmldsig-core/Overview.html
        $Revision: 1.83 $ on $Date: 2001/06/14 18:17:33 $
]

At 09:09 6/20/2001, Gregor Karlinger wrote:
>Joseph,
>
>I have just read the text you have added to the current draft, and I
>would like to propose the following changes:
>
>   1. Change the first sentence to:
>
>        "Also, strings in DNames (X509IssuerSerial, X509SubjectName,
>         and KeyName if appropriate) should be encoded as follows:"
>
>      This is because the encoding does not apply to the whole DName,
>      but only to string values within a DName.
>
>   2. Escaping of ASCII control characters should happen by replacing
>      them with "\" (instead of "\x" in the current draft - this
>      is an error adopted from my proposal text) followed by ...
>
>Liebe Gruesse/Regards,
>---------------------------------------------------------------
>DI Gregor Karlinger
>mailto:gregor.karlinger@iaik.at
>http://www.iaik.at
>Phone +43 316 873 5541
>Institute for Applied Information Processing and Communications
>Austria
>---------------------------------------------------------------
>
>
> > -----Original Message-----
> > From: w3c-ietf-xmldsig-request@w3.org
> > [mailto:w3c-ietf-xmldsig-request@w3.org]On Behalf Of Joseph M. Reagle
> > Jr.
> > Sent: Wednesday, June 13, 2001 7:58 PM
> > To: Donald E. Eastlake 3rd
> > Cc: w3c-ietf-xmldsig@w3.org
> > Subject: Re: DName encoding (was:KeyName white space)
> >
> >
> > At 07:59 6/13/2001, Donald E. Eastlake 3rd wrote:
> > >It is a specification for the encoding of X.500 Distinguished Names
> > >(DName) as such.
> >
> > Ok, represented at the end of section 4.4.4. We could add a
> > schema datatype
> > but given that RFC2253 encoding is "should" and these are further
> > specified
> > as guidelines over that, the present approach is probably the lightest.
> >
> > [
> >          $Revision: 1.81 $ on $Date: 2001/06/13 17:55:14 $
> >
> > http://www.w3.org/Signature/Drafts/xmldsig-core/Overview.html#sec-X509Data
> > ]
> >
> > --
> > Joseph Reagle Jr.                 http://www.w3.org/People/Reagle/
> > W3C Policy Analyst                mailto:reagle@w3.org
> > IETF/W3C XML-Signature Co-Chair   http://www.w3.org/Signature
> > W3C XML Encryption Chair          http://www.w3.org/Encryption/2001/
> >
> >
> >


--
Joseph Reagle Jr.                 http://www.w3.org/People/Reagle/
W3C Policy Analyst                mailto:reagle@w3.org
IETF/W3C XML-Signature Co-Chair   http://www.w3.org/Signature
W3C XML Encryption Chair          http://www.w3.org/Encryption/2001/
Received on Wednesday, 20 June 2001 14:23:48 GMT

This archive was generated by hypermail 2.2.0 + w3c-0.29 : Thursday, 13 January 2005 12:10:13 GMT