← Prev in month ← Prev in thread
Next in thread → Next in month →

Minutes of XACML TC Meeting 29 March 2007

From
Bill Parducci
Date
2007-04-12T14:50:00+00:00
ID
Thread
Minutes of XACML TC Meeting 29 March 2007
Minutes of XACML TC Meeting 29 March 2007

1  Roll Call & Minutes

Attendees

Hal Lockhart (Co-chair)

Bill Parducci (Co-chair, minutes)

Anthony Nadalin

Ron Williams

Argyn Kuketayev

Rich Levinson

Prateek Mishra

Anil Saldhana

Erik Rissanen

Anne Anderson

Seth Proctor

David Staggs

Quorum achieved (76% per Kavi)

Approval of Minutes

29 March TC meeting minutes

APPROVED: UNANIMOUS CONSENT

  2  Administrivia

Oasis Symposium

Next week Oasis will be holding its Symposium in San Diego, Hal

asked if there were any concerns about his representing XACML at the

event during the "Lightning Round". None were voiced.

ITU

XACML has been adopted as ITU-T X.1142.

InterOp

Rich reviewed the status of the InterOp preparations and interest by

various organizations. Rich has been collecting input from

participants, has received comments from several. Vordel submitted

comments, but not confirmed as an InterOp participant. No Profiles

identified yet. Rich is targeting Tuesday for delivery of the next

version of the proposed test cases.

3
Issues

Obligations

Bill noted that a request for Use Cases has been posted to the list

and that a number of scenarios have been submitted. Hal said that he

will be providing some Use Cases soon. Tony says IBM products not

yet using Obligations, but may in the future. Bill is planning

on having a first cut at a proposal by the next TC meeting. Two

models are currently being considered: predefined bucket vs. model

with number of attributes for Obligation Categories.

Matching Identifiers

Anne discussed feedback from her request for requirements.

Push/Pull Protocol

Hal described his work on a Policy distribution protocol. This work

is based upon the following premises:

* datetime + PolicyID forms a unique identifier for each Policy

* Central store knows what Policies every PDP should have

* PDP knows what it has, so matching may occur at either end

* protocol is stateless

PUSH
PULL

----------------

Central Sync  |
|
|

|
|
|

----------------

Remote Sync
|
|
|

|
|
|

----------------

Consideration: Policies are updated during provisioning

(distribution of consistent set)

meeting adjourned
← Prev in month ← Prev in thread
Next in thread → Next in month →