RE: [ws-sx] Issue 66: Security Policy Usecases

["Ashok Malhotra" <ashok.malhotra@oracle.com>]

Tony:
We sent out the usecases for two reasons.

First, security policy is complex and these usecases will give people
a bunch of standard policies that they can just pickup and use or templates 
they can modify.

Second, looking thru these usecases will identify holes and bugs in the spec.
You mail and the earlier mail from Anand Mani that I forwarded have started
this process.  This is great!  We will end up with a much better spec.

All the best, Ashok
 

> -----Original Message-----
> From: Tony Gullotta [mailto:tony.gullotta@soa.com] 
> Sent: Monday, June 19, 2006 2:35 PM
> To: Ashok Malhotra; ws-sx@lists.oasis-open.org
> Cc: Prateek Mishra; Mischkinsky,Jeff
> Subject: RE: [ws-sx] Issue 66: Security Policy Usecases
> 
> Ashok,
> 
> Thanks for taking up this task. In 2.1.3 you state there is 
> no way to indicate the supporting token must be encrypted. 
> However there is a way to indicate the supporting token must 
> be signed. Are you identifying that as a shortcoming in the spec? 
> 
> Tony 
> 
> -----Original Message-----
> From: Ashok Malhotra [mailto:ashok.malhotra@oracle.com]
> Sent: Thursday, June 15, 2006 11:13 AM
> To: ws-sx@lists.oasis-open.org
> Cc: Prateek Mishra; Mischkinsky,Jeff
> Subject: [ws-sx] Issue 66: Security Policy Usecases
> 
> I'm attaching a document with a number of what we feel are 
> typical Security Policy usecases along with sample Policies.
> 
> The first thing to do is to discuss whether we need more or 
> less usecases.
> My guess is we need more but we also don't need a 100 page document.
> 
> Then we need to decide where this fits along with the other 
> WS-SX deliverables.
> 
> All the best, Ashok
>  
> 
>