[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [dss] CMS
Trevor, Either ... urn:oasis:names:tc:dss:1.0:result:NotSupported (probably with a message) ... or Verify them reporting first error encountered or success Further to this, Return options not supported when multiple signatures are present should also issue the above urn (i.e. ReturnSignerIdentity, ReturnSigningTime), also with a message Ed -----Original Message----- From: Trevor Perrin [mailto:trevp@trevp.net] Sent: April 21, 2004 6:36 AM To: Ed Shallow Subject: RE: [dss] CMS >[Trevor] >In your proposal, the client sends a SignedData. When a SignedData >contains multiple SignerInfos (co-signatures or counter-signatures), >what does the server do? Hi Ed - actually, if you could answer the above question (to me or on list, whichever), I'll send out a summary of both CMS approaches and request other opinions (or send out the summary yourself). I think we've reduced this issue to 2 clear, reasonable proposals (and good for us for doing that!), so we might as well put it to a vote. Trevor
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]