OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

xacml message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

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

On Tue, 2003-08-12 at 12:33, Daniel Engovatov wrote:
> But then we have the same issue with any other attribute that is part of
> the "context" - does it remain static for the duration of evaluation?
> I am not sure that we can place a requirement on the information source
> to remain static, nor a requirement on PDP to "cache" the data somehow.
> I understood that it is the implementation choice how the relevant bits
> of data are computed in PIP and retrieved - I remember that we
> explicitly left this open...

I'm not sure that we do have the same problem. The spec calls out the
current date/time attributes, and explicitly says that unlike other
attributes, these must be handled in a unique way:

  "So, unlike most other attributes, their semantics are not transparent
   to the PDP."  (10.2.5)

Based on this, I don't think a clarification about the current date/time
attributes has any effect on any other attributes in the system. All I'm
worried about is that since there's no language explaining how current
values must be provided, it leaves different implementations open to
different models.


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]