OASIS eXtensible Access Control Markup Language (XACML) TC

I. Roll Call Voting Members Hal Lockhart (Chair) Bill Parducci (Co-Chair, minutes) Paul Tyson Doron Grinstein Remon Sinnema Gregory Neven Franz-Stefan Preiss Jan Herrmann John Tolbert Members David Chadwick David Choy John Mike Davis Quorum met: (57% per Kavi) I. Roll Call & Approve Minutes: 21 April 2011 TC Meeting: APPROVED unanimously II. Administrivia F2F Information Will be held in Lexington, MA at the Boeing facility 28th, 29th,30th June John Tolbert to publish logistics information Webinar Erik, Doron and Hal will be presenting. Contents being worked on now. III. Issues BTG David, is in the process of splitting document into a SAML Profile and XACML profile. He is a bit unclear as to what is needed in XACML profile based upon Paul's comments on the list. Hal offered that a Profile may created or an artifact on non-normative document track. Greg noted that he is awaiting feedback from the SAML group on the proposal made to that group. David summarized the current discussion into 4 basic topics: 1. Use existing components in a standard way (general approval) 2. Should be a BTG state attribute (general approval) 3. BTG response from PDP? User knows if has BTG privilege. (open) 4. Should there be an Obligation or special BTG response management? (open) Mike suggested that state need to broadened to be more generic than BTG. Hal offered that a generalize dynamic state manager that could be used for notification, etc. The current mechanisms outlined are Obligation/Advice and Missing Information. Mike suggested that the case of the request spanning organizations is fundamentally different than than an internal solution. He suggested that BTG capabilities be indicated upon initial interface with the PEP. Bill suggested that BTG doesn't have context until a Deny has been issued. Hal contrasted the flow diagrams posted to the list by Paul and David--PDP and PEP manages the BTG state. Paul intended that the PDP return a Deny with Advice. Doron offered that an Advice on a Deny would allow for a simple Profile that would be reasonably interoperable. David noted that an Obligation was used in the proposal for XACML v2 compliance. meeting adjourned.

Hi Bill there are missing headings in the minutes as follows David On 28/04/2011 19:19, Bill Parducci wrote: > > I. Roll Call > Voting Members > Hal Lockhart (Chair) > Bill Parducci (Co-Chair, minutes) > Paul Tyson > Doron Grinstein > Remon Sinnema > Gregory Neven > Franz-Stefan Preiss > Jan Herrmann > John Tolbert > > Members > David Chadwick > David Choy > John Mike Davis > > Quorum met: (57% per Kavi) > > I. Roll Call& Approve Minutes: > 21 April 2011 TC Meeting: > APPROVED unanimously > > II. Administrivia > > F2F Information > Will be held in Lexington, MA at the Boeing facility > 28th, 29th,30th June > John Tolbert to publish logistics information > > Webinar > Erik, Doron and Hal will be presenting. Contents being worked on now. > > III. Issues > BTG - delete Attribute predicate profile for SAML and XACML > David,- delete Greg is in the process of splitting document into a SAML Profile > and XACML profile. He is a bit unclear as to what is needed in XACML > profile based upon Paul's comments on the list. Hal offered that a > Profile may created or an artifact on non-normative document track. > Greg noted that he is awaiting feedback from the SAML group on the > proposal made to that group. BTG > > David summarized the current discussion into 4 basic topics: > 1. Use existing components in a standard way (general approval) > 2. Should be a BTG state attribute (general approval) > > 3. BTG response from PDP? User knows if has BTG privilege. (open) > 4. Should there be an Obligation or special BTG response management? > (open) > > Mike suggested that state need to broadened to be more generic than > BTG. Hal offered that a generalize dynamic state manager that could > be used for notification, etc. > > The current mechanisms outlined are Obligation/Advice and Missing > Information. > > Mike suggested that the case of the request spanning organizations > is fundamentally different than than an internal solution. He > suggested that BTG capabilities be indicated upon initial interface > with the PEP. Bill suggested that BTG doesn't have context until a > Deny has been issued. > > Hal contrasted the flow diagrams posted to the list by Paul and > David--PDP and PEP manages the BTG state. Paul intended that the PDP > return a Deny with Advice. > > Doron offered that an Advice on a Deny would allow for a simple > Profile that would be reasonably interoperable. David noted that an > Obligation was used in the proposal for XACML v2 compliance. > > meeting adjourned. > > --------------------------------------------------------------------- > To unsubscribe from this mail list, you must leave the OASIS TC that > generates this mail. Follow this link to all your TCs in OASIS at: > https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php > > -- ***************************************************************** David W. Chadwick, BSc PhD Professor of Information Systems Security School of Computing, University of Kent, Canterbury, CT2 7NF Skype Name: davidwchadwick Tel: +44 1227 82 3221 Fax +44 1227 762 811 Mobile: +44 77 96 44 7184 Email: D.W.Chadwick@kent.ac.uk Home Page: http://www.cs.kent.ac.uk/people/staff/dwc8/index.html Research Web site: http://www.cs.kent.ac.uk/research/groups/iss/index.html Entrust key validation string: MLJ9-DU5T-HV8J PGP Key ID is 0xBC238DE5 *****************************************************************