MHonArc v2.5.0b2 -->

















xacml message






[Date Prev]
 | [Thread Prev]
 | [Thread Next]
 | [Date Next]

--

[Date Index]
 | [Thread Index]
 | [List Home]








Subject: Re: [xacml] another small time/date issue




From: Bill Parducci <bill.parducci@overxeer.com>
To: xacml@lists.oasis-open.org
Date: Fri, 15 Aug 2003 07:44:34 -0700






this is my point. the only 'requirement' that we need be concerned with 
is the set of subject/action/resource inputs for a specfic decision. as 
i poisted in my first note, this does not exclude the [pXp] introducing 
attributes in a multistep process. XACML simply doesn't address how this 
is done (the point that i *think* you are trying to make ;o), it treats 
each decision as a unique transaction.

b

Daniel Engovatov wrote:
> To clarify myself:  yes, in most cases it is the PDP that will "provide"
> this attributes.  But as we where discussing for quite a while now - I
> do not think it is feasible to put exact requirement on exactly how it
> is done.
> The fact that it is a single block on Figure 1 does not mean it must be
> implemented as a monolithic piece in any sense.
> 
> Could you suggest an example of a clarification?  Maybe it would be
> easier for me to understand why it is a problem then.
> 
> Thank you.
> 
> Daniel.









References:

RE: RE: [xacml] another small time/date issue
From: "Daniel Engovatov" <dengovatov@bea.com>






[Date Prev]
 | [Thread Prev]
 | [Thread Next]
 | [Date Next]

--

[Date Index]
 | [Thread Index]
 | [List Home]