[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: FW: [dss] wd-42 errors and typos
Ed and All DSS, Those comments which are considered to be editorial in nature have been incorporated in CD release4 as agreed at the last meeting. Those points which have a technical impact will have to be addressed in a new release of the CD, having discussed these in the DSS TC. The outstanding issues to be addressed as follows: Incorporation of signature timestamp in XML signatures: > 22) line 1070: "The present document does not establish a unique solution. > It is a matter of server policy to decide how to incorporate signature > timestamps in the XML signatures rendered to its clients" > > This phrase should either be reworded or removed as it will create > inter-operability anomalies across core implementations. Enveloped XML signatures in non XML documents. > > 25) line 1223-1226: "In the case of a non-XML input document, or when > > these child elements are omitted, then the server places the signature > > in the input document in accordance with procedures defined in a > > profile or as part of the server policy." > > > > I believe we should reject non-XML Documents as default core > > processing when Enveloped signatures are requested. > Clarification of treatment of RefURI within dss:SignedReferences > > 30) line 1324-1325: have no idea what this is supposed to mean ??? <dss:VerificationTime> and its relationship with claimed SigningTime and Signature timestamp. > > 39) line 1656: "instead of the current time" implies that the DSS > > implementation always uses the current time by default. What if > > "SigningTime" is present in the signature ? This optional input > > element needs to be re-written to reflect questions fielded from the > > public review. & > > 40) line 1747: a note should be made that qualifies the 3rd party's > > ability to attest to the SigningTime (i.e. only content Timestamps > > applied before signature creation should result in the > > ThirdPartyTimestamp boolean being turned on, since a signature > > Timestamp may be applied months after > > SigningTime.) All the other comments are considered to be editorial in nature and incorporated in the CDr4 version of the core as indicated in the attached document Nick Pope
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]