W3C home > Mailing lists > Public > w3c-ietf-xmldsig@w3.org > July to September 2000

Re: <X509Name>CN=Kent</X509Name>

From: Joseph M. Reagle Jr. <reagle@w3.org>
Date: Tue, 11 Jul 2000 08:13:47 -0400
Message-Id: <3.0.5.32.20000711081347.00a7dcb0@localhost>
To: TAMURA Kent <kent@trl.ibm.co.jp>
Cc: "IETF/W3C XML-DSig WG" <w3c-ietf-xmldsig@w3.org>, Brian LaMacchia <bal@microsoft.com>
At 15:42 7/11/00 +0900, TAMURA Kent wrote:
 >> I wanted to point out that the examples you sent me (and Petteri
confirmed)
 >> for the forthcoming Signature specification include an <X509Name> element
 >> that is not part of the schema. Do you mean X509SubjectName?
 >
 >Yes, it should be X509SubjectName.  I modify our generation code.

However, in that case Brian's latest content model [1] precludes the ability
to use a SubjectName and Cert within one X509Data. Consequently, I've
removed the SubjectName so the spec has valid examples -- and leave it to
you and Brian to resolve what you want for the content model.

[1] http://lists.w3.org/Archives/Public/w3c-ietf-xmldsig/2000AprJun/0277.html

This change means that an individual X509Data clause may be one of:
a) a collection of X509IssuerSerial, X509SKI and X509SubjectName elements,
b) exactly one X509Certificate element, or
c) exactly one X509CRL


_________________________________________________________
Joseph Reagle Jr.   
W3C Policy Analyst                mailto:reagle@w3.org
IETF/W3C XML-Signature Co-Chair   http://www.w3.org/People/Reagle/
Received on Tuesday, 11 July 2000 08:14:16 GMT

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