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] Use-cases and requirements - observations


At 09:32 AM 7/9/2003 -0400, Tim Moses wrote:

>Trevor - It sounds like we are in agreement.  I don't object to having a
>service interface that "allows" clients to control the plethora of choices.
>I merely want to provide adequate support for those that can't.
>
>The main lesson from GSS_API is that the interface must allow the client to
>stipulate who the intended recipient is.  It's pointless signing a message
>in conformance with one's own policy, if it does not conform with the policy
>of the recipient.  So, the service has to know who the message is intended
>for.  I am thinking of B2B Web-services in which there is a single
>Web-service end-point or WSDL port.  This would not require wild-carding.

Under 3.4 Signing Requirements, how about adding an "Intended Audience" 
section, where the client can optionally pass in a list of names of whom 
the message is targeted to?

Trevor



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