HRAC decision object locality constrained?

[Konstantin Beznosov <beznosov@baptisthealth.net>]

We discussed during last conference call the issue of having QoP as one more
factor in making authorization decisions.

We decided to stay away from including QoP into the list of parameters for
access_allowed method. The decision had 2 rationales:

1. Not everyone will need it
2. QoP can be obtained via Current provided that the HRAC decision object is
locality constrained (LC).

Here is the question: Why should we impose the restriction of the HRAC decision
object to be LC?

As far as I understand, making an interface is considered to be a last resort.
If my understanding is true, then we want to have better than just "because of
QoP" justification of making the decision interface to be LC. 

Any thoughts?

Konstantin


----------------
Broadcast message to hrac-rfp from Konstantin Beznosov <beznosov@baptisthealth.net>.
Go to http://cadse.cs.fiu.edu/omg/hrac-rfp to browse the mail list archive.