Re: [xacml] Proposed Agenda - October 30

[Frank Siebenlist <franks@mcs.anl.gov>]

I'm sorry, but I won't be able to make tomorrow's call as I'm on the road.

After the discussions Polar, Simon and I had at the end of the F2F, I'm in the 
process of writing another note to describe the more formal approach that we 
could take to implement the delegation. I believe that the three of us we pretty 
much in agreement, and the most difficult thing seems to be the notation to use, 
so I reading up on what others have published about that...

I should be able to send it around before the focus group telcon of next 
Thursday, and it would be great if we could discuss it then.

Regards, Frank.


Hal Lockhart wrote:

> Date: Thursday, October 30, 2003
> Time: 10:00 AM EDT
> Tel: 512-225-3050 Access Code: 65998
> 
> Proposed Agenda:
> 
> 10:00-10:05 Roll Call and Agenda Review
> 10:05-10:10 Vote to accept minutes of October 16 concall
> 
> http://www.oasis-open.org/archives/xacml/200310/msg00047.html
> 
> 10:10-11:00 Discuss 2.0 Work in Progress (thanks to Anne for supplying the
> items)
> 
> 1. The following work items appear ready for a vote of approval.
>    Can we put them on the agenda for the 30 Oct meeting?
> 
>    Ready for vote:
>    22. time-in-range function
>    23. Use XQuery comparison functions for date, time, dateTime
>    28. Define "current time/date/dateTime" during policy evaluation
> 
>    Already approved:
>    7. ConditionReference
>    12. Environment Element in Target
> 
> 2. We need to assign a due date for WI #11. XACML Extension
>    Points, which needs a proposal.
> 
> 3. Are we ready to approve general proposal for #9. "Policies
>    referring to hierarchical entities" (i.e. all hierarchies must
>    be mapped to XML), and move status to "needs detailed
>    proposal"?
> 
> 4. Same for #42. "Requests asking for access to multiple elements
>    in a hierarchical resource"?  i.e. all requests for access to
>    multiple elements must express request using XML mapping?
> 
> 
> 5. Still open and have open issues, so perhaps time to discuss:
> 
>    18. Obligations in Rules
>        General proposal:
>        http://lists.oasis-open.org/archives/xacml/200305/msg00011.html
>    32. Standardize naming to specify rules for requestor's authz policy
>        http://lists.oasis-open.org/archives/xacml/200308/msg00008.html #4
>        http://lists.oasis-open.org/archives/xacml/200310/msg00035.html #32
>        http://lists.oasis-open.org/archives/xacml/200310/msg00042.html #32
>    34. porttype/operations to ask for required attributes
>        http://lists.oasis-open.org/archives/xacml/200308/msg00008.html #6
>        http://lists.oasis-open.org/archives/xacml/200310/msg00035.html #34
>        [this one not tied to 2.0, so perhaps lower priority]
>    36. Check for requester authorized to ask for authz decision
>        http://lists.oasis-open.org/archives/xacml/200310/msg00035.html #36
>    39. Make Status in the XACML Response optional
>        http://lists.oasis-open.org/archives/xacml/200310/msg00037.html #39
>        http://lists.oasis-open.org/archives/xacml/200310/msg00040.html
>    40. Define a SAML PolicyQuery and PolicyStatement
>        http://lists.oasis-open.org/archives/xacml/200310/msg00031.html
>        http://lists.oasis-open.org/archives/xacml/200310/msg00032.html
>        http://lists.oasis-open.org/archives/xacml/200310/msg00034.html
>        http://lists.oasis-open.org/archives/xacml/200310/msg00036.html
>        http://lists.oasis-open.org/archives/xacml/200310/msg00037.html #40
>    46. Status detail for missing attributes
>        http://lists.oasis-open.org/archives/xacml/200310/msg00076.html
>        http://lists.oasis-open.org/archives/xacml/200310/msg00077.html
> 
>    and the policy administration items:
>        http://lists.oasis-open.org/archives/xacml/200310/msg00084.html
>    29. Policy Authority Delegation
>        http://lists.oasis-open.org/archives/xacml/200310/msg00083.html
>    31. Attribute Issuer as Subject
>        http://lists.oasis-open.org/archives/xacml/200308/msg00008.html #3
>        http://lists.oasis-open.org/archives/xacml/200310/msg00035.html #31
>    38. Policies for the Administration of XACML Policies
>        http://lists.oasis-open.org/archives/xacml/200308/msg00050.html
>        http://lists.oasis-open.org/archives/xacml/200310/msg00037.html #38
>        http://lists.oasis-open.org/archives/xacml/200310/msg00054.html
> 
> 
> Following are awaiting action by champions (or others):
>     2. Location Information
>        Needs revised general proposal from Seth Proctor.
>    13. Optional Target Elements
>        Needs detailed proposal from Hal Lockhart.
>    27. Version number element or attribute in an XACML policy.
>        Needs detailed proposal from Seth Proctor.
>    33. XACML wsdl/porttype definition for <Req>/<Resp> exchange
>        Needs detailed proposal from Frank Siebenlist.
>    37. Multiple <AttributeValue> elements for single <Attribute> in Request
>        Needs detailed proposal from Rebekah Lepro.
>    41. General attribute classifications instead of Subject, Resource, ...
>        Needs proposal from Daniel Engovatov by 3 Nov 2003.
>    45. Fix AttributeAssignment example in Section 4.2.4.3 (Rule 3)
>        Needs detailed proposal from ???
> 
> Hal
> 
> 
> To unsubscribe from this mailing list (and be removed from the roster of the OASIS TC), go to http://www.oasis-open.org/apps/org/workgroup/xacml/members/leave_workgroup.php.
> 

-- 
Frank Siebenlist               franks@mcs.anl.gov
The Globus Alliance - Argonne National Laboratory