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: Core protocol: is the <Status> element the status of what has been validated ?



Concerning the verification protocol, I would like that our protocol clearly 
distinguishes in the validation response between two different aspects:

1. Whether the server could successfully process or not the request, arriving
to a result on which it could report the client. 

2. Whether the signature the client sent to verify is valid or not.


After reading the core protocol document in its section 2.5, it seems to me
as if
the <Status> element does NOT REPORT ON THE STATUS OF WHAT THE
SERVER WAS REQUESTED TO VERIFY, BUT ON THE STATUS THE SERVER
HAS REACHED AFTER trying to process that request, and in fact there is no such
code like valid or invalid ....

I propose to define in the VerifyResponse two elements:

1. Result. This element would substitute the current Status. It would
indicate the
global result of the processing, namely, whether the server has
successfully processed
or not the request of the client.

2. A Report element that would contain an Status element indicating whether
the signature was or not valid, and a number of optional StatusMessages
that could 
give more information on how the server has concluded that the signature is
or not
valid.

Juan Carlos.


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