RE: [dss] Compound operation Verify & Sign

["Edward Shallow" <ed.shallow@rogers.com>]

Nick and Co,

   The last suggested position I remember getting consensus on was that the
request for the secondary or ancilliary operation should be expressed in the
"Options" or "ProcessingOptions" structure as it was then called.

   So in your example below, the principle operation is the "Verify". The
client requestor must express their desire through use of (for example) an
"AddContentTimeStamp" option or something similar.

   This may necessitate additonal "Outputs" but the protocol is nicely able
to handle that.

   As it pertains to the EPM, we have need for several such compound
operations, but we will use our profile extension to express them. I also
remember discussing that additional and/or optional "outputs" and "results"
would be expressed by the requestor as "options".

   I'll dig up the references if you wish.

Ed

-----Original Message-----
From: Nick Pope [mailto:pope@secstan.com] 
Sent: October 24, 2003 4:28 AM
To: OASIS DSS TC
Subject: [dss] Compound operation Verify & Sign

Following the discussion on the <Status> element brings to mind the
discussion we had a few meetings ago on compound (or what Ed called stacked)
operations and particularly the ability to support a VerifyAndSign operation
where a counter signature is applied based on whether the original signature
is valid.

I believe that such an operation is important in a number of use cases, for
example, notarisation services.

This was brought up at the F2F meeting and was included in the requirements
document (3.9).  My recollection of the discussion on 22 Sept is that the
only compound operation that was needed would be VerifyAndSign, although I
see no record of it in the minutes.

How do we envisage VerifyAndSign being supported in the DSS protocol?  Is
there a way of combining the two request / response structures, or do we
need to define a specific structure which is this combined operation?

Nick



To unsubscribe from this mailing list (and be removed from the roster of the
OASIS TC), go to
http://www.oasis-open.org/apps/org/workgroup/dss/members/leave_workgroup.php
.