[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: 2.0 Work Item List, v1.37
Colleagues, An updated XACML 2.0 Work Item Index is attached. I believe the STATUS line of each item reflects the current status with respect to XACML 2.0, including decisions taken at today's 22 Jan 2004 TC meeting. Please let me know if any corrections are needed. Actions needed: 7. ConditionReference Please review the proposed schema changes in http://lists.oasis-open.org/archives/xacml/200401/msg00035.html and get comments to the list as soon as possible. Accepted in general, but still need exact schema and text changes. 11. XACML Extension Points Please review the proposed schema extension points in http://lists.oasis-open.org/archives/xacml/200401/msg00046.html and get comments to the list as soon as possible. This proposal needs discussion and vote. 13. Optional Target Elements We approved making Target elements and Targets optional, but then Polar raised objections. We need to see brief examples so members can determine what is needed for consistent semantics and simplicity of policy construction. 18. Obligations in Rules Michiharu's proposal in http://lists.oasis-open.org/archives/xacml/200305/msg00011.html lists some open issues. These need to be reviewed prior to the 5 Feb 04 meeting and resolved then, if possible. 23. Use XQuery comparison functions for date, time, dateTime Waiting for XML Schema group to decide time type semantics. 31. Attribute Issuer as Subject Need brief explanation from Frank as to how this would enable an administrative policies extension or profile. 32. Standardize naming to specify rules for requestor's authz policy Do we really think we will do something for XACML 2.0 on this? Can it be addressed in a separate profile document? 36. Check for requester authorized to ask for authz decision Do we really think we will do something for XACML 2.0 on this? Can it be addressed in a separate profile document? 37. Multiple <AttributeValue> elements for single <Attribute> in Request Rebekah is still reviewing handling of Attribute and AttributeValue in current draft. Report expected by 5 Feb 2004. 38. Policies for the Administration of XACML Policies Is this same as 29? Wouldn't it be addressed as part of the proposed "Administration Policy Profile"? 42. Requests asking for access to multiple elements in a hierarchical resource Some lingering issues raised by Simon on associating semantics with the upward/downward elements in a resource hierarchy: http://lists.oasis-open.org/archives/xacml/200401/msg00047.html [Simon add'l issues] http://lists.oasis-open.org/archives/xacml/200401/msg00048.html [Michiharu to Simon] 45. Fix AttributeAssignment example in Section 4.2.4.3 (Rule 3) Review fix in Section 4.2.4.3 (Rule 3) in current draft. Do we have to vote to accept it? 46. Status detail for missing attributes Awaiting "missing attribute" schema from Seth. 51. Clarify obligations: "fulfill" vs. "understand" Awaiting detailed proposal from Michiharu that will provide text clarifying the issues raised. 52. New section explaining not backwards compatible and listing changes Awaiting detailed proposal from Bill. 55. Converge SAML and XACML Attribute schema definitions We continue to track SAML. Anne to respond to SAML request for history of our decision to use explicit URI Datatype attributes. 58. Standard hierarchy schemas Awaiting hierarchical file system schema proposal from Anne. 59. Define standard "role" subject attribute Needs discussion and vote. 60. Define standard "purpose" attributes Needs discussion and vote. Anne -- Anne H. Anderson Email: Anne.Anderson@Sun.COM Sun Microsystems Laboratories 1 Network Drive,UBUR02-311 Tel: 781/442-0928 Burlington, MA 01803-0902 USA Fax: 781/442-1692
Title: XACML 2.0 Work Items
Version: 1.37
Updated: 04/01/22 (yy/mm/dd)
TEMPLATE FOR PROPOSALS:
http://lists.oasis-open.org/archives/xacml/200308/msg00028.html
CURRENT 2.0 DRAFT:
http://www.oasis-open.org/apps/org/workgroup/xacml/download.php/5127/oasis-xacml-2_0-wd-05.zip
THIS WORK ITEM INDEX INCLUDES E-MAILS UP THROUGH:
http://lists.oasis-open.org/archives/xacml/200401/msg00050.html
and reflects decisions taken at XACML TC meeting 22 Jan 2004.
1. Grid Requirements
Any XACML changes needed to satisfy Grid requirements
TYPE: New functionality
STATUS: Abstract. Related: #2,3,4,16,17,29,30,31,32,33,34,35,36,37
PROPOSAL: Abstract
CHAMPION: Frank Siebenlist
2. Location Information
Way to pass information needed to configure a PDP and its
context and policy handlers/finders in order to evaluate a
policy.
Examples of such information are:
o where to find various Attributes, and what they are keyed off
o where Attribute Authorities to be used are located
o where to find function, combining algorithm, data-type,
Attribute parsing code
Such information might be embedded in
a. an XACML Request
b. an XACML policy
c. a third document type
TYPE: New functionality. Could be separate profile if #11 accepted.
STATUS: Open issues. Waiting for revised proposal from Seth. Related: #1,24.
PROPOSAL:
http://lists.oasis-open.org/archives/xacml/200310/msg00022.html
CHAMPION: Seth Proctor
3. Multiple Actions per Request
Support Requests containing multiple Actions. Response could
either say "All permitted/denied" or could include a separate
decision for each.
TYPE: New functionality
STATUS: Closed for 2.0: no proposal submitted by 20 Oct 2003. Related: #1.
PROPOSAL:
CHAMPION: Frank Siebenlist
4. Multiple Resources per Request
Support Requests containing multiple Resources. Response
could either say "All permitted/denied" or could include a
separate decision for each.
TYPE: New functionality
STATUS: Closed for 2.0: no proposal submitted by 20 Oct 2003. Related: #1.
PROPOSAL:
CHAMPION: Frank Siebenlist
5. Privacy Requirements
Any XACML changes needed to satisfy Privacy requirements.
TYPE: New functionality
STATUS: Closed for XACML 2.0. Abstract. Related: <none>
PROPOSAL: ABSTRACT
CHAMPION: ?
6. Domain-specific identifiers
Define a set of domain-specific identifiers based on
application usage of XACML.
TYPE: New functionality
STATUS: Closed for 2.0: no proposal submitted by 20 Oct 2003.
PROPOSAL:
CHAMPION: Michiharu Kudo
7. ConditionReference
Allow a Rule to contain a ConditionReference element as an
alternative to a Condition element. The ConditionReference
would identify a Condition element specified elsewhere. This
allows a single Condition to be re-used in Rules under
different Targets. An optional ConditionId attribute would be
added to the Condition element to support this.
TYPE: Simplicity of policy construction.
STATUS: Detailed proposal below accepted in general 22 Jan
2004 with exception that VariableId should be #string, not
#anyURI. This will go into Draft 6, with understanding that
changes can still be made. Still needs text description for
the spec. Final vote still needed.
PROPOSAL:
http://lists.oasis-open.org/archives/xacml/200304/msg00039.html [use cases]
http://lists.oasis-open.org/archives/xacml/200312/msg00045.html [Michiharu:summary]
http://lists.oasis-open.org/archives/xacml/200401/msg00022.html [Bill: summary]
http://lists.oasis-open.org/archives/xacml/200401/msg00035.html [Michiharu:detailed]
CHAMPION: Michiharu Kudo
8. RuleIdReference
Define RuleIdReference analogous to PolicyIdReference and
PolicySetIdReference.
TYPE: Simplicity of policy construction
STATUS: Closed for 2.0 20 Oct 2003. Can do this now with a Policy
containing a single Rule. Related #19.
PROPOSAL:
http://lists.oasis-open.org/archives/xacml/200305/msg00004.html
CHAMPION: Anne Anderson (on behalf of ebXML)
9. Policies referring to hierarchical resources
How to express policies that apply to a hierarchy of
resources. E.g. "Frank can read any file under directory
/X/Y".
TYPE: New functionality
STATUS: CURRENT proposal below accepted for 2.0 8 Jan 2004.
PROPOSALS:
OLD: http://lists.oasis-open.org/archives/xacml/200304/msg00057.html
OLD: http://lists.oasis-open.org/archives/xacml/200305/msg00009.html
CURRENT: http://lists.oasis-open.org/archives/xacml/200310/msg00078.html
http://lists.oasis-open.org/archives/xacml/200312/msg00050.html [need std hier. schema]
http://lists.oasis-open.org/archives/xacml/200312/msg00059.html [Anne to Rob Grzywinski]
CHAMPION: Simon Godik
10. Parameters for Combining Algorithms
Support an element or attribute in a PolicySet, Policy, or Rule
that provides parameters to be used by a Combining Algorithm
that is combining the PolicySet, Policy, or Rule.
TYPE: New functionality
STATUS: Closed for 2.0 21 Oct 2003. Will do this via extension points #11.
PROPOSAL:
OLD: http://lists.oasis-open.org/archives/xacml/200305/msg00014.html
CURRENT: http://lists.oasis-open.org/archives/xacml/200310/msg00079.html
CHAMPION: Michiharu Kudo
11. XACML Extension Points
Define schema extension points for XACML. This work item
might solve the requirements driving several other work items.
Used as solution for #10. See
http://lists.oasis-open.org/archives/xacml/200310/msg00098.html
for information that may be relevant on extension points.
TYPE: New functionality
STATUS: Open. Need discussion and vote on proposal below.
PROPOSAL:
http://lists.oasis-open.org/archives/xacml/200401/msg00046.html
CHAMPION: Simon Godik and Michiharu Kudo.
12. Environment Element in Target
Allow the Target Element to include an Environment element,
just as it now includes Subject, Resource, and Action
elements.
TYPE: New functionality
STATUS: Accepted for 2.0 on 8 Jan 2004. In 2.0 draft.
PROPOSAL:
http://lists.oasis-open.org/archives/xacml/200305/msg00012.html
CHAMPION: Michiharu Kudo
13. Optional Target Elements
Make Subjects, Resources, Actions elements optional in a
Target. Missing element has same semantics as <Any.../> Make
Target itself optional. Missing element has same semantics as
a Target containing <AnySubject/>, <AnyResource/>,
<AnyAction/>. <Any...> dropped. Environment elements to be
treated same as Subject, Resource, Action as far as omitted
elements are concerned.
TYPE: Simplicity of policy construction
STATUS: Open issues. In 2.0 draft 05 Section 5.5.
PROPOSAL:
http://lists.oasis-open.org/archives/xacml/200310/msg00038.html
Polar has objected that semantics are not consistent.
CHAMPION: Hal Lockhart
14. Signature envelope requirements
Any new XACML work items to meet requirements for signature
envelopes around an XACML schema instance, such as including
an XACML Policy or Request in a signed SAML Assertion.
TYPE: New functionality
STATUS: Closed for XACML 2.0. Abstract. Related: <none>
PROPOSAL: ABSTRACT
CHAMPION: ?
15. Encrypted XACML schema instance requirements
Any new XACML work items to meet requirements for encrypted
XACML Policy or Context schema instances.
TYPE: New functionality
STATUS: Closed for XACML 2.0. Abstract. Related: <none>
PROPOSAL: ABSTRACT
CHAMPION: ?
16. XACML Policy in SAML Response Conditions
Profile uses of XACML Policy instances as a syntax for
specifying Conditions in a SAML Response.
TYPE: SAML Profile
STATUS: Closed for XACML 2.0: no proposal by 20 Oct 2003.
PROPOSAL:
CHAMPION: Frank Siebenlist
17. XACML Policy in SAML Request Conditions
Profile use of SAML Conditions element as a way for a PEP to
pass an XACML Policy to be used by the PDP in evaluating the
Request.
TYPE: SAML Profile
STATUS: Closed for XACML 2.0: no proposal by 20 Oct 2003.
PROPOSAL:
CHAMPION: Frank Siebenlist
18. Obligations in Rules
Allow Rule to contain Obligations.
TYPE: Simplicity of policy construction
STATUS: Open issues. To be discussed 5 Feb 04.
PROPOSAL:
http://lists.oasis-open.org/archives/xacml/200305/msg00011.html
CHAMPION: Michiharu Kudo
19. Rule as lowest administrative unit
Allow a Rule to be the lowest administrative unit for XACML.
Probably required to support RuleIdReference.
TYPE: New functionality
STATUS: Closed for 2.0 20 Oct 2003. No proposal. Related #8.
PROPOSAL:
CHAMPION: Michiharu Kudo
20. Non-normative XACML interpretation guide
Rationale, examples, possible implementation models; general
information that would help XACML users know the intent of the
XACML TC for the use of XACML elements.
TYPE: New document not tied to XACML 2.0.
STATUS: Needs proposal. Not part of 2.0.
PROPOSAL:
CHAMPION: ?
21. Non-normative XACML Primer
Primer for XACML usage.
TYPE: New document not tied to XACML 2.0.
STATUS: Needs proposal. Not part of 2.0.
PROPOSAL:
CHAMPION: ?
22. time-in-range function
Provide a function for comparing that a time of day is between
two other times of day.
TYPE: Erratum fix
STATUS: Approved in general 30 Oct 2003. In 2.0 draft.
PROPOSAL:
http://lists.oasis-open.org/archives/xacml/200309/msg00005.html
CHAMPION: Seth Proctor
23. Use XQuery comparison functions for date, time, dateTime
Allow date, time, and dateTime functions to handle comparing a
value with no time zone with a value with a time zone.
TYPE: Erratum fix
STATUS: Approved in general 30 Oct 2003. 8 Jan 2004: Seth to
consult on new XML Schema time values.
PROPOSAL:
http://lists.oasis-open.org/archives/xacml/200307/msg00044.html
http://lists.oasis-open.org/archives/xacml/200312/msg00061.html [Status update]
CHAMPION: Seth Proctor
24. Define a schema for function declarations
Define a schema for declaring the signature of a function.
Probably needed with #2 if #2 includes finding parsing and
evaluation code for new FunctionIds.
TYPE: New functionality
STATUS: Closed for 2.0: no proposal by 20 Oct 2003. Related: #2.
PROPOSAL:
CHAMPION: Daniel Engovatov
25. Function for comparing file system pathnames.
Define a function for specifying and comparing file system
pathnames used in resource-id. Possibly new DataType also.
TYPE: New functionality
STATUS: Closed for 2.0: handle per #9 proposal.
PROPOSAL:
http://lists.oasis-open.org/archives/xacml/200309/msg00088.html
CHAMPION: Anne Anderson
26. Define policy reduction (partial evaluation) of a policy
Define a process for reducing a policy based on known
information, leaving only the unresolved predicates. The
reduced policy is returned along with the context with which
the reduction was done.
TYPE: New functionality
STATUS: Closed for 2.0 20 Oct 2003. Use case requirement
satisfied using a different model.
PROPOSAL:
http://lists.oasis-open.org/archives/xacml/200310/msg00080.html
CHAMPION: Frank Siebenlist
27. Version number element or attribute in an XACML policy.
Some way of indicating the version of a policy having a
particular XACML policy id, and a way of placing version
constraints on a policy reference.
TYPE: New functionality
STATUS: Accepted for 2.0 8 Jan 2004. In 05 draft.
PROPOSAL:
http://lists.oasis-open.org/archives/xacml/200312/msg00062.html [Seth]
http://lists.oasis-open.org/archives/xacml/200312/msg00067.html [Tim]
CHAMPION: Seth Proctor
28. Define "current time/date/dateTime" during policy evaluation
Specify whether time/date/dateTime are constant over a
policy evaluation. Proposal is that it be constant.
TYPE: Erratum fix
STATUS: Approved in general 30 Oct 2003. In 2.0 draft.
PROPOSAL:
http://lists.oasis-open.org/archives/xacml/200308/msg00006.html
http://lists.oasis-open.org/archives/xacml/200310/msg00035.html #28
CHAMPION: Seth Proctor
29. Policy Authority Delegation
The ability to express in a policy rule that a certain
authorization authority is allowed to administer access
control policy for a certain target: i.e. way to say "Frank is
trusted to issue policies for resource X". If the PDP trusts
the policy rule that states this, then the PDP would also
trust policies issued by Frank for resource X.
TYPE: Administration Policy Profile
STATUS: Open issues. Related: #1,29,31,35,38.
PROPOSAL:
http://lists.oasis-open.org/archives/xacml/200308/msg00008.html #1
http://lists.oasis-open.org/archives/xacml/200310/msg00035.html #29
http://lists.oasis-open.org/archives/xacml/200310/msg00042.html #29
http://lists.oasis-open.org/archives/xacml/200310/msg00046.html
http://lists.oasis-open.org/archives/xacml/200310/msg00053.html
http://lists.oasis-open.org/archives/xacml/200310/msg00054.html
http://lists.oasis-open.org/archives/xacml/200310/msg00060.html
http://lists.oasis-open.org/archives/xacml/200310/msg00061.html
http://lists.oasis-open.org/archives/xacml/200310/msg00062.html
http://lists.oasis-open.org/archives/xacml/200310/msg00063.html
http://lists.oasis-open.org/archives/xacml/200311/msg00022.html [Frank:Haskell model]
http://lists.oasis-open.org/archives/xacml/200311/msg00030.html [schema changes]
http://lists.oasis-open.org/archives/xacml/200311/msg00032.html [Tim:summary]
http://lists.oasis-open.org/archives/xacml/200311/msg00034.html [Bill:weird case]
http://lists.oasis-open.org/archives/xacml/200311/msg00036.html
http://lists.oasis-open.org/archives/xacml/200312/msg00009.html [Polar:Abadi calculus]
http://lists.oasis-open.org/archives/xacml/200312/msg00015.html [Use cases]
http://lists.oasis-open.org/archives/xacml/200312/msg00019.html [Von Welch,resp]
http://lists.oasis-open.org/archives/xacml/200312/msg00022.html [Polar to Frank]
http://lists.oasis-open.org/archives/xacml/200312/msg00025.html [Frank to Polar]
CHAMPION: Frank Siebenlist
30. Passing of explicit policy in the Authorization Decision Query
This is the same as #17, except that it is more general
(i.e. policy from PEP not necessarily passed in SAML
Conditions), and also explicitly states that the authority to
specify the policy to use has been delegated to the PEP.
TYPE: SAML Profile
STATUS: Closed for 2.0 21 Oct 2003. See #17. Solve by making
remote PAP accessible to the local PDP. Possibly related: #29,38.
PROPOSAL:
http://lists.oasis-open.org/archives/xacml/200308/msg00008.html #2
http://lists.oasis-open.org/archives/xacml/200310/msg00035.html #30
CHAMPION: Frank Siebenlist
31. Attribute Issuer as Subject
The current attribute issuer type is a string. This
restriction doesn't allow one to easily point at an issuer as
Subject, and it doesn't allow for any path validation that
goes more than one level deep. By allowing an attribute issuer
of type subject, one could cater for more complex use-cases
that involve policy delegation.
TYPE: New functionality
STATUS: Open issues. Related: #1,29,31,35,38.
PROPOSAL:
http://lists.oasis-open.org/archives/xacml/200308/msg00008.html #3
http://lists.oasis-open.org/archives/xacml/200310/msg00035.html #31
CHAMPION: Frank Siebenlist
32. Standardize naming to specify rules for requestor's authz policy
In a setting where a requester invokes certain operations of a
service provider, the convention for the target of the service
provider's policy is well defined: subject=requester,
resource=service-provider, and action=operation. However,
when we consider the policy evaluation on the requester's side
to check whether an invocation on the service provider is
allowed according to the requester's policy, then is it less
clear. It is almost a mirror case, but if we take a
convention where the "resource" is the one protected by the
policy, the we should equate subject=service-provider and
resource=requester with the same action=operation.
Unfortunately, if we also have to consider the possibility
that the service-provider can invoke an equivalent operation
on the requester, then we need an additional way to
discriminate between these cases. Maybe we can label the
action with a category of "out-bound" (?).
TYPE: New functionality. Separate profile?
STATUS: Open issues. Related: #1,29,31,35,38.
PROPOSAL:
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
CHAMPION: Frank Siebenlist
33. XACML wsdl/porttype definition for <Req>/<Resp> exchange
Abstract the decision request and response messages between
the context handler and the PDP into a wsdl/porttype
definition.
TYPE: WSDL Profile
STATUS: Needs detailed proposal. Related: #1. Not part of 2.0.
PROPOSAL:
http://lists.oasis-open.org/archives/xacml/200308/msg00008.html #5
http://lists.oasis-open.org/archives/xacml/200310/msg00035.html #33
CHAMPION: Frank Siebenlist
34. porttype/operations to ask for required attributes
Allow a requester to query the resource's authorization policy
for the required attributes for a Target such that it "knows"
which one are missing and would have to be retrieved and
presented with any request.
TYPE: WSDL Profile
STATUS: Open issues. Related: #1. Not part of 2.0.
PROPOSAL:
http://lists.oasis-open.org/archives/xacml/200308/msg00008.html #6
http://lists.oasis-open.org/archives/xacml/200310/msg00035.html #34
CHAMPION: Frank Siebenlist
35. Policy on revealing missing attributes
The returning of the missing attribute info is sensitive
information and should itself be subject to policy.
TYPE: New functionality
STATUS: Closed for 2.0 21 Oct 2003. Related: #1,29,31,35,38.
Can be solved using existing XACML policies.
PROPOSAL:
OLD: http://lists.oasis-open.org/archives/xacml/200308/msg00008.html #7
CURRENT: http://lists.oasis-open.org/archives/xacml/200310/msg00081.html
CHAMPION: Frank Siebenlist
36. Check for requester authorized to ask for authz decision
Proposes that the PDP have a formally defined access control
mechanism to "downstream PDPs".
The PDP should check whether the upstream PDP requester,
i.e. subject associated with the context handler, is allowed
to ask for the authorization decision. We need to be able to
state this in a policy statement, and describe the correct
operating procedure.
TYPE: New functionality. Separate profile?
STATUS: Open issues. Related: #1,29,30,31,35,38.
PROPOSAL:
http://lists.oasis-open.org/archives/xacml/200310/msg00035.html #36
http://lists.oasis-open.org/archives/xacml/200310/msg00074.html #36 on 20 Oct 2003
CHAMPION: Frank Siebenlist
37. Multiple <AttributeValue> elements for single <Attribute> in Request
Allow
<Attribute DataType="Y" ID=X>
<AttributeValue DataType="Y">A</AttributeValue>
<AttributeValue DataType="Y">B</AttributeValue>
<AttributeValue DataType="Y">C</AttributeValue>
</Attribute>
as syntactic shorthand for
<Attribute DataType="Y" ID=X>
<AttributeValue DataType="Y">A</AttributeValue>
</Attribute>
<Attribute DataType="Y" ID=X>
<AttributeValue DataType="Y">B</AttributeValue>
</Attribute>
<Attribute DataType="Y" ID=X>
<AttributeValue DataType="Y">C</AttributeValue>
</Attribute>
This makes it easier to convert SAML Attributes into XACML
Attributes, and is consistent with the way XPath treats the
same set of AttributeValues.
TYPE: Simplicity of Request construction
STATUS: Approved as "OK idea" at 21 Oct 2003 F2F. In 2.0 draft
05. Related: #1.
PROPOSAL:
http://lists.oasis-open.org/archives/xacml/200310/msg00037.html #37
http://lists.oasis-open.org/archives/xacml/200401/msg00019.html [Rebekah - Q's]
http://lists.oasis-open.org/archives/xacml/200401/msg00023.html [Rebekah; 04 draft]
http://lists.oasis-open.org/archives/xacml/200401/msg00024.html [Rebekah; 04 draft]
http://lists.oasis-open.org/archives/xacml/200401/msg00041.html [Tim to Rebekah]
http://lists.oasis-open.org/archives/xacml/200401/msg00042.html [Rebekah to Tim]
CHAMPION: Rebekah Lepro
38. Policies for the Administration of XACML Policies
XACML defines a language to express policies about access to
resources. But it is also desirable to create policies about
the creation, modification and deletion of XACML policies. In
a sense XACML already allows this, since XACML policies are
agnostic to the semantics of the resources being
protected. However, it is very desirable for administrative
policies to specify not the "name" of policies being
administered, but their "content."
TYPE: New functionality. Administration Policy Profile?
STATUS: Open issues. Related: #1,29,31,35,38. Same as #29?
PROPOSAL:
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
CHAMPION: Hal Lockhart
39. Make Status in the XACML Response optional
Makes it possible to allow Status for Indeterminate situations
to be conveyed in the protocol envelope (such as SAML
DecisionStatement) rather than in the XACML Response for cases
where that is more appropriate. Avoids having redundant and
possibly inconsistent Status fields when XACML Response is
carried in some envelope that also has a Status.
TYPE: New functionality
STATUS: Accepted in general for 2.0 30 Oct 2003. In 2.0 draft.
PROPOSAL:
http://lists.oasis-open.org/archives/xacml/200310/msg00037.html #39
http://lists.oasis-open.org/archives/xacml/200310/msg00040.html
CHAMPION: Hal Lockhart
40. Define a SAML PolicyQuery and PolicyStatement
Define syntax for SAML that will allow a Query for one or more
Policy or PolicySet instances with specified Policy[Set]Ids or
with copy of a Request Context that need to be matched, and
will return the requested instances in a PolicyStatement in a
SAML Assertion.
TYPE: XACML Profile for Using SAML
STATUS: Related to #48.
PROPOSAL:
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
CHAMPION: Hal Lockhart
41. General attribute classifications instead of Subject, Resource, ...
Instead of using the fixed attribute classifications
"Subject", "Resource", "Action", and "Environment", allow
arbitrary attribute classifications to be used, each
identified by a URN and associated with a profile that
explains its use and semantics.
TYPE: New functionality.
STATUS: Closed for 2.0 8 Jan 2004, although could be
considered for future version. Related: #2,24.
PROPOSAL:
CHAMPION: Daniel Engovatov
42. Requests asking for access to multiple elements in a hierarchical resource
How to express requests that ask for access to multiple
elements in a hierarchical resource, i.e. "Does Frank have
access to all elements under /X/Y?".
XACML currently defines a standard Resource AttributeId
"urn:oasis:names:tc:xacml:1.0:resource:scope" that can be used
to express whether a request applies to "Immediate",
"Children", or "Descendents". XACML also currently defines a
way to include an XML document in a <ResourceContent> element
as part of a Request. This is sufficient if all hierarchies
are assumed to be XML documents and if the document itself is
always included in <ResourceContent> when multiple decisions
are requested.
What is missing is a way of handling hierarchical resources
that are not XML documents, such as file system directories.
To handle other types of hierarchies, it will be necessary to
identify what type of hierarchy the resource is and, in a
related profile, what syntax is to be used in expressing and
referring to nodes and elements in hierarchies of that type.
Proposal 200310/msg00078.html proposes to solve this by
requiring all hierarchical resources to be represented and
referenced as XML instances using XPath expressions. If this
is accepted, then the specification needs to state this
explicitly.
TYPE: New functionality.
STATUS: Accepted in general for 2.0 30 Oct 2003. Needs to
be explained in specification in non-normative Hierarchical
Resources section. Resolution is: supply resource hierarchy
in XML representation in <ResourceContent>.
Related: #9,25,42.
PROPOSAL:
http://lists.oasis-open.org/archives/xacml/200310/msg00078.html
http://lists.oasis-open.org/archives/xacml/200310/msg00082.html
http://lists.oasis-open.org/archives/xacml/200401/msg00047.html [Simon add'l issues]
http://lists.oasis-open.org/archives/xacml/200401/msg00048.html [Michiharu to Simon]
CHAMPION: Simon Godik
43. Examine interactions between approved work items
As part of the editorial process, a check is needed to ensure
that there are no unexpected problematic interactions between
approved work items.
TYPE: Editorial
STATUS: Open issues
PROPOSAL: ?
CHAMPION: ?
44. Fix examples in the XACML Specification
Review & correct all examples before the 2.0 release.
TYPE: Editorial
STATUS: Abstract. Related: #45.
PROPOSAL: Abstract
CHAMPION:
45. Fix AttributeAssignment example in Section 4.2.4.3 (Rule 3)
In this example, AttributeAssignments contain
AttributeSelectors and AttributeDesignators. While this isn't
illegal, the example implies something about the specification
that isn't true (ie, that the PDP will interpret the contents
of assignments).
TYPE: Editorial
STATUS: In 2.0 draft. Related: #44.
PROPOSAL:
http://lists.oasis-open.org/archives/xacml/200310/msg00064.html
http://lists.oasis-open.org/archives/xacml/200310/msg00067.html
http://lists.oasis-open.org/archives/xacml/200310/msg00068.html
http://lists.oasis-open.org/archives/xacml/200310/msg00069.html
http://lists.oasis-open.org/archives/xacml/200311/msg00009.html
CHAMPION: Michiharu Kudo
46. Status detail for missing attributes
In 6.15 there is an explanation for what detail to include
with the missing-attribute status code: Attributes specify one
or more missing values, and if an AttributeValue is included,
then this specifies an acceptable value. If no AttributeValue
is included, then the PDP is specifying the identifier and
datatype only. Sounds good.
The problem is that the Attribute type is
<xs:element ref="xacml-context:AttributeValue"/>
This means that it's not valid to have an Attribute with no
AttributeValue. So, it's not possible for the PDP to specify a
missing attribute without specifying at least one acceptable
value (note that even an empty AttributeValue tag, which is
still legal, is still technically a value). PDPs need a way
to specify missing attributes without providing acceptable
values.
TYPE: Erratum
STATUS: Need to define a new "missing attribute" schema
element that can return attribute meta-data (with or without
Attribute Value information) for this. Accepted in general
30 Oct 2003.
PROPOSAL:
http://lists.oasis-open.org/archives/xacml/200310/msg00076.html
http://lists.oasis-open.org/archives/xacml/200310/msg00077.html
CHAMPION: Seth Proctor
47. New SAML Authorization Decision Query/Response using XACML
TYPE: XACML Profile for Using SAML
STATUS: SAML accepts XACML/OGSA proposal in general (link),
but says XACML should define a SAML extension using the
SAML namespace. We need to verify that SAML 2.0 changes
do not invalidate our proposal. Only Sun(?), Oblix, and
Entrust seem to use the SAML 1.0 version, so will be
deprecated in SAML 2.0.
PROPOSAL: (find link)
CHAMPION: Anne Anderson and Hal Lockhart
48. PAP Interface to a PDP/PRP
Define an interface to a PDP or PRP (Policy Repository Point)
from a PAP for pushing and/or managing policies.
TYPE: XACML Interface Definitions Specification
STATUS: Related to #38,40. Requirements spec needed.
PROPOSAL:
CHAMPION: Tim Moses
49. Improve example showing how obligations work
The example in Section 4.2.4.3 is somewhat misleading and has
caused confusion among XACML users. See PROPOSAL for specific
points.
TYPE: Erratum
STATUS: Closed. Same as #45.
CHAMPION: Michiharu Kudo
50. Fix obligations erratum: fulfilled by PDP
Lines 2077-2078 in the 1.1 specification say "The
<Obligations> element SHALL contain a set of obligations that
MUST be fulfilled by the PDP in conjunction with the
authorization decision."
"PDP" should be "PEP".
TYPE: Erratum
STATUS: Accepted for 2.0 8 Jan 2004.
PROPOSAL: http://lists.oasis-open.org/archives/xacml/200311/msg00060.html
CHAMPION: Anne Anderson
51. Clarify obligations: "fulfill" vs. "understand"
Lines:1768-1770,2731-2733,2756-2757,2859-2862,3060-3062
Intermixed uses of "fulfill" and "understand" with respect to
obligations semantics is confusing. For example, "what is the
recommended action for an obligation that is understood yet is
unable to be fulfilled?"
TYPE: Erratum
STATUS: Awaiting detailed proposal.
PROPOSAL: http://lists.oasis-open.org/archives/xacml/200311/msg00059.html
CHAMPION: Michiharu Kudo
52. New section explaining not backwards compatible and listing changes
The XACML 2.0 specification should have a new section that
explains 2.0 is not backwards compatible with 1.0 or 1.1, and
listing the changes made between 1.0 (and/or 1.1) and 2.0.
TYPE: Editorial
STATUS: Awaiting detailed proposal.
PROPOSAL:
CHAMPION: Bill Parducci
53. Drop <Function> element
I believe its purpose can be served by the <Apply> element
when the FunctionId attribute identifies one of the bag
functions. We already allow a similar special case in the
<Condition> element, which is an <Apply> element whose
FunctionId attribute must identify a function whose return
type is boolean.
As currently structured, the bag function does not "enclose"
the attributes or functions to which it applies.
If we require the use of the <Apply> element instead, the bag
function can enclose the attributes or functions to which it
applies. See lines [a477] to [a491] in draft 3.
TYPE: Simplicity
STATUS: Closed for 2.0. Tim will add additional clarify text
to the description of <Function> explaining how and why it is
used.
PROPOSAL:
http://lists.oasis-open.org/archives/xacml/200312/msg00063.html [Tim]
http://lists.oasis-open.org/archives/xacml/200312/msg00064.html [Daniel]
http://lists.oasis-open.org/archives/xacml/200312/msg00065.html [Polar to Tim]
CHAMPION: Tim Moses
54. Is resource-id required?
First issue: V1.1 Section 6.3 schema fragment says resource
must have 0 or more attributes, but text that follows says
there must be one and only one instance of the "resource-id"
attribute (implying one or more attributes, exactly one of
which must be "resource-id"). These two should be made
consistent. [Tim]
Second issue: Why do we require "resource-id"? Some policies
may depend only on the security label of the resource, only on
the host machine where the resource is located, or some other
attribute of the resource, but may not care about the actual
"resource-id" at all. [Anne]
TYPE: Simplicity and erratum fix
STATUS: Voted to make resource-id optional 8 Jan 2004.
PROPOSAL:
http://lists.oasis-open.org/archives/xacml/200401/msg00000.html [Tim]
http://lists.oasis-open.org/archives/xacml/200401/msg00001.html [Anne]
http://lists.oasis-open.org/archives/xacml/200401/msg00002.html [Seth to Anne]
http://lists.oasis-open.org/archives/xacml/200401/msg00003.html [Bill to Tim]
http://lists.oasis-open.org/archives/xacml/200401/msg00004.html [Anne]
http://lists.oasis-open.org/archives/xacml/200401/msg00005.html [Daniel to Anne]
http://lists.oasis-open.org/archives/xacml/200401/msg00006.html [Satoshi to Anne]
http://lists.oasis-open.org/archives/xacml/200401/msg00007.html [Daniel to Satoshi]
http://lists.oasis-open.org/archives/xacml/200401/msg00008.html [Satoshi to Daniel]
http://lists.oasis-open.org/archives/xacml/200401/msg00009.html [Daniel to Satoshi]
http://lists.oasis-open.org/archives/xacml/200401/msg00010.html [Satoshi to Daniel]
http://lists.oasis-open.org/archives/xacml/200401/msg00011.html [Daniel to Satoshi]
http://lists.oasis-open.org/archives/xacml/200401/msg00012.html [Satoshi]
http://lists.oasis-open.org/archives/xacml/200401/msg00013.html [Daniel to Satoshi]
http://lists.oasis-open.org/archives/xacml/200401/msg00014.html [Satoshi to Daniel]
http://lists.oasis-open.org/archives/xacml/200401/msg00015.html [Daniel to Satoshi]
http://lists.oasis-open.org/archives/xacml/200401/msg00016.html [Satoshi to Seth]
http://lists.oasis-open.org/archives/xacml/200401/msg00017.html [Tim]
CHAMPION: Tim Moses and Anne Anderson
55. Converge SAML and XACML Attribute schema definitions
TYPE: Interoperability. Some of this could go into an XACML SAML Profile.
STATUS: Open. Still under discussion. SAML has not frozen
their 2.0 Attribute definition.
PROPOSAL:
http://www.oasis-open.org/apps/org/workgroup/security/download.php/4884/draft-sstc-attribute-02.pdf [Rebekah SAML proposal]
http://lists.oasis-open.org/archives/xacml/200401/msg00031.html [Anne - draft answer to SAML]
http://lists.oasis-open.org/archives/xacml/200401/msg00032.html [Anne]
http://lists.oasis-open.org/archives/xacml/200401/msg00034.html [Scott Cantor]
http://lists.oasis-open.org/archives/xacml/200401/msg00039.html [SAML/XACML mtg]
CHAMPION: Rebekah Lepro
56. Should Request Context be optional (non-normative)
Use of the Request Context should be non-normative, so long as
policy evaluation is consistent with the behavior given a
Request Context.
TYPE: Erratum fix
STATUS: Accepted for 2.0 8 Jan 2004. Detailed text below
accepted 22 Jan 2004.
PROPOSAL:
http://lists.oasis-open.org/archives/xacml/200401/msg00037.html [detailed text]
CHAMPION: Hal Lockhart
57. Make Environment element optional in Request Context
TYPE: Simplicity
STATUS: Closed for 2.0 8 Jan 2004. Leave as is: minOccurs="1".
58. Standard hierarchy schemas
Given resolution to hierarchical resources in WI#9, there
needs to be a standard schema for certain common hierarchies
such as UFS.
TYPE: Interoperability. Could be separate profile.
STATUS: Open
PROPOSAL:
CHAMPION: Anne Anderson (for UFS and WFS)
59. Define standard "role" subject attribute
Add following to Appendix B.5 "Subject attributes":
This identifier indicates a role associated with the subject.
Values of this attribute SHOULD be of type
"http://www.w3.org/2001/XMLSchema#anyURI";;.
urn:oasis:names:tc:xacml:2.0:subject:role
TYPE: Interoperability.
STATUS: Detailed proposal available
PROPOSAL:
http://lists.oasis-open.org/archives/xacml/200401/msg00038.html
CHAMPION: Anne Anderson
60. Define standard "purpose" attributes
In order to deal with certain regulatory requirements, it
would be useful to have a standard "purpose" attribute for
resource and for action.
urn:oasis:names:tc:xacml:2.0:resource:purpose
urn:oasis:names:tc:xacml:2.0:action:purpose
We could also define a standard rule that requires the
resource purpose to include the action purpose. This would
enforce the requirement that data resources only be used for
the purposes for which they were collected.
TYPE: Interoperability
STATUS: Open.
PROPOSAL: See above.
CHAMPION: Tim Moses
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]