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

RE: Processing model for ds:Reference/@Type

From: Gregor Karlinger <gregor.karlinger@iaik.at>
Date: Sat, 13 Oct 2001 00:54:46 +0200
To: "Christian Geuer-Pollmann" <geuer-pollmann@nue.et-inf.uni-siegen.de>, <w3c-ietf-xmldsig@w3.org>
Message-ID: <LBEPJAONIMDADHFHAEAOIELGCJAA.gregor.karlinger@iaik.at>
Christian,

see last sentence of section 4.3.3.1: "The type attribute is advisory. 
No validation of the type information is required by this specification."

/Gregor

> -----Original Message-----
> From: w3c-ietf-xmldsig-request@w3.org
> [mailto:w3c-ietf-xmldsig-request@w3.org]On Behalf Of Christian
> Geuer-Pollmann
> Sent: Tuesday, October 09, 2001 7:13 PM
> To: w3c-ietf-xmldsig@w3.org
> Subject: Processing model for ds:Reference/@Type
> 
> 
> Hi all,
> 
> The Type attribute of a ds:Reference can contain the Type of a Reference 
> like
> 
> Type="http://www.w3.org/2000/09/xmldsig#Object"
> 
> or
> 
> Type="http://www.w3.org/2000/09/xmldsig#Manifest"
> 
> . Does there exist a proposed processing model how verification 
> is done on 
> that? From what I see,  there exist two different ways:
> 
> 1: I ignore this type information and do only core validation: 
> SignatureValue and the SignedInfo
> 
> 2: I try to follow and verify all nested Manifests (if 
> Type="&ds;Manifest").
> 
> But what processing should happen if the Type is #Reference or #Object?
> 
> 
> Christian
> 
> 
> 
Received on Friday, 12 October 2001 18:54:48 GMT

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