AW: [xacml] Proposed Agenda for 9 September 2010 TC Meeting

["Jan Herrmann" <herrmanj@in.tum.de>]

dear all,
just a quick questions before the telco.
Is there a reason why the core spec recommends/?constrains implementations
that obligations have to be fulfilled in the pep and not in the ctx handler.
best regards
jan

 
> -----Ursprüngliche Nachricht-----
> Von: Rich.Levinson [mailto:rich.levinson@oracle.com]
> Gesendet: Donnerstag, 9. September 2010 06:41
> An: xacml
> Betreff: [xacml] Proposed Agenda for 9 September 2010 TC Meeting
> 
> Proposed Agenda for 9 September 2010 TC Meeting:
> 
> Time: 13:00 EDT
> Tel: 513-241-0892 Access Code: 65998
> 
> 13:00 - 13:05 Roll Call & Approve Minutes:
> Roll Call:
> 
> Approve Minutes:
> 12 Aug 2010 TC Meeting:
>   http://lists.oasis-open.org/archives/xacml/201008/msg00006.html
> 
> 13:05-13:10
> Administrivia:
>     Identity Management 2010
>     Worldwide Identity Solutions for Online Security, Privacy and Trust
>     27-28 September, Washington, DC  USA
>     http://events.oasis-open.org/home/IDM/2010
>  see emails:
>   http://lists.oasis-open.org/archives/xacml/201008/msg00007.html
>   http://lists.oasis-open.org/archives/xacml/201009/msg00000.html
> 
> 13:10-14:00
> 
> XACML v3 Status:
>   Next steps:
>      All 8 specs are CS, we were going to check that TC-Admin
> 	did the necessary updates.
>      To move to OASIS Specification need 3 members to confirm
> 	they are using specs in conformance w the clauses
> 	in each spec.
> 	 - the core and profiles can proceed independently in general,
> 	    assuming no dependencies.
> 
> 
> Export and IPC specs:
>   TC Admin issues were addressed, ballots were issued:
> 	Both ballots approved doc as a Committee Specification:
> 		vote on each was: 9-0-0
> 
> New Issues:
> A paper about extending XACML to specify quantified risk adaptive access
> control
>  http://lists.oasis-open.org/archives/xacml/201008/msg00008.html
> 
> Old Issues
> User is asking why:
>  "'3.1 Nodes in an XML document' requiring that not only
>    should one include a resource-id of type xpath-expression for the node
>    that is the resource for the access decision but also its parent and
>    all ancestors. Why is this required by the spec? Why is it necessary."
> 
>  This should already be addressed in 3.0 hier profile;
>    should we consider updating the 2.0 hier profile w errata?
> 
> 
> 
> ---------------------------------------------------------------------
> 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