Re: [ekmi] Request ID or entire request in sksml response

[Anil Saldhana <Anil.Saldhana@redhat.com>]

The example of an email usage was just an illustration of possibilities 
of transport.  Inline answers:

Arshad Noor wrote:
> Interesting requirement, Anil.  This leads to more questions:
>
> 1) Should SKSML then be sent using SOAP over SMTP, or using just
>    S/MIME?
Are we not relying on ws-security? That will provide the message level 
security.
>
> 2) How should the SKS server respond under the following conditions?
>
>    a) When the mail message is unsigned spam;
>    b) When the mail message is signed spam;
>    c) When the mail message is legitimate SKSML, but signed with
>       an invalid certificate?
What if it is a controlled environment?
> 3) Are there other transports we should be considering besides HTTP
>    and SMTP?
Why tie the spec to any transport?

I do not understand what difficulties arise in sending some id about the 
request back in the response :).  I am just looking at usage in an 
asynchronous manner such as Async WS.
http://java.sun.com/blueprints/webservices/using/webservbp3.html

>
>
> Arshad
>
> Anil Saldhana wrote:
>> Hi Arshad,
>>  at least two use cases come into my mind.
>>
>> a) In enterprise software, typically transport is the variant.  So I 
>> should be able to send sksml requests via smtp for example. :) With 
>> JMS for example, I may
>> get a response later and the only thing that I will have is either 
>> the request id or the optional request element.
>>
>> b) With clients in low bandwidth and tough terrain, such as hand held 
>> devices, you cannot always rely on synchronous communication.
>>
>> I would at least like to have the request id sent back from the 
>> response. That should be sufficient for clients.
>>
>> Regards,
>> Anil
>>
>> Arshad Noor wrote:
>>> Hi Anil,
>>>
>>> Can you provide a business scenario where this is necessary and
>>> where synchronous communication with the SKS server does not
>>> address the problem.  Thanks.
>>>
>>> Arshad
>>>
>>> Anil Saldhana wrote:
>>>> Hi all,
>>>>  I would like to open the discussion to the use case of 
>>>> asynchronous/batch requests for keys.  This will require that we 
>>>> need to return a request id or the entire request (which can be an 
>>>> optional element) in the response.
>>>>
>>>> Regards,
>>>> Anil