OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

dss message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [dss] UPU Electronic PostMark user case scenarios


Trevor,
Sorry for the delay in my reply: Monday and Tuesday were holidays
in Barcelona... See below
>>
>You mean add, to the Request message, an indication that the input 
>signature should be verified before it is counter-signed?
>
>I'm not sure we need that - we've already talked about how different types 
>of DSS services might do different things to the signature request before 
>signing it (such as archiving it, passing it to a human for review, 
>validating it in various ways, etc..).  I don't think it's the client's job 
>to request these operations - the service will know what it needs to do, 
>based on whether it's an EPM service, or an eNotary service, or whatever.
>
>Maybe we can mention in "3.4.4 Signature Policy" that whether the server 
>archives, and how it validates, the request, might be other aspects 
>controlled by the Signature Policy the client selects.  Then the client 
>could have some control over them, but we don't need to explicitly add 
>elements for this.  I'd just like to avoid complicating the client/server 
>interface with too many options.
>
>Trevor 
>
Well, I understand your point: depending of the kind of service,
the server will do one thing or the other.... And certainly, we can add
the kind of text you propose in section 3.4.4....

Juan Carlos.


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]