RE: XACMl TC Chapter revision - Ironman

["Simon Y. Blackwell" <sblackwell@psoom.com>]

My sense is that this is not being dropped, it is just that we are focusing
on the first section of the charter. Of course, leaving this unsaid doesn't
help much! Thanks for bring it up.

> -----Original Message-----
> From: Pilz, Gilbert [mailto:gpilz@jamcracker.com]
> Sent: Wednesday, June 27, 2001 9:36 AM
> To: 'xacml@lists.oasis-open.org'
> Subject: RE: XACMl TC Chapter revision - Ironman
> 
> 
> An issue that was raised at the SAML F2F #3 is that the wording about
> XACML's relationship to SAML seems to have been dropped. Specifically:
> 
> +-----------------------------
> To ensure work is not duplicated and standards adoption is as 
> simple as
> possible, XACML shall adopt as baseline documents the work 
> products of the
> Security Services TC including but not limited to a Domain Model and
> Glossary. Furthermore, Use Cases and Requirements documents will share
> content that is common through normative references. The 
> XACML TC shall keep
> its work consistent with the work of the Security Services TC 
> by requesting
> enhancements to, modifications of, and cross-references from Security
> Services TC documents through a formal liaison with the 
> Security Services
> TC. This liaison will include the regular sharing of 
> deliverables and status
> reports during teleconferences or at face-to-face meetings.
> +-----------------------------
> 
> As one of the liaisons between SAML and XACML this naturally 
> concerns me . .
> .
> 
> - gil
> 
> -----Original Message-----
> From: Simon Y. Blackwell [mailto:sblackwell@psoom.com]
> Sent: Wednesday, June 27, 2001 9:06 AM
> To: 'xacml@lists.oasis-open.org'
> Subject: FW: XACMl TC Chapter revision - Ironman
> 
> 
> I am reposting this since it will again be a topic of 
> discussion on the
> con-call. Let's try and put it to bed. If you have any 
> suggested changes or
> concerns, please post them to the list today.
> 
> -----Original Message-----
> From: Damodaran, Suresh [mailto:Suresh_Damodaran@stercomm.com]
> Sent: Thursday, June 14, 2001 1:20 PM
> To: 'xacml@lists.oasis-open.org'
> Subject: XACMl TC Chapter revision - Ironman
> 
> 
> 
> Here is the version that we worked on in the con-call.
> The scope part and beyond are still under work.
> 
> -Suresh
> --------------------------------------------------------------
> --------------
> -
> Product of TC
> XACML TC will define a core XML schema for representing 
> authorization and
> entitlement policies, also called XACML.
> 
> Policy Target
> The target of a policy (hereafter referred to as "target") 
> can be any object
> that can be referenced using XML.
> 
> Protocols and bindings
> XACML TC will identify bindings
> to existing protocols (e.g., XPath, LDAP), and define new 
> protocols, if
> necessary, as means of accessing and communicating the policies.
> 
> Scope
> XACML is expected to address fine grained control of 
> authorized activities,
> the effect of characteristics of the access requestor, the 
> protocol over
> which the request is made, authorization based on classes of 
> activities, and
> content introspection (i.e. authorization based on both the 
> requestor and
> potentially attribute values within the target where the values of the
> attributes may not be known to the policy writer). XACML is 
> also expected to
> suggest a policy authorization model to guide implementers of the
> authorization mechanism.
> 
> Extensibility
> XACML core schema is extensible for as yet unknown features
> 
> Interoperability
> 
> XACML TC will define interoperability of XACML core schema
> with other standards
> 
> 
> 
> -----------------------------------------------------www.sterc
omm.com-------
------------------------------------------------------
Suresh Damodaran, Ph.D.					Sterling Commerce, a
SBC Company
Senior Software Architect					750 W. John
Carpenter Freeway
469-524-2676 (O) 						Irving, TX
75039-2505