Minutes 11 September TC Meeting

[Bill Parducci <bill@parducci.net>]

1. Roll Call
    Hal Lockhart (minutes)
    Bill Parducci (Co-chair, minutes)
    Erik Rissanen
    Anthony Nadalin
    Rich Levinson
    Hal Lockhart
    Anil Saldhana
    John Tolbert
    Duane DeCouteau (non-voting)

    Quorum reached 7 of 9 (77%)


2. Administrivia
    Vote on minutes postponed to next meeting due to late posting
    to list.

3. Issues

   Open Issues on list
    http://lists.oasis-open.org/archives/xacml/200809/msg00000.html

    The TC has no objections to those Issues Erik suggests should be
    considered No Action.

    The TC has no objections to the Proposed Actions Erik presented on
    the list.

    Identifier conflict – the TC has chosen to resolve this by using:
    urn:oasis:names:tc:xacml:1.0:subject:authentication-method

    String comparison - the general consensus is this issue requires
    more consideration. A possible source is XQuery's implementation.

    Multiply function arguments - The TC agrees that 0 or 1 argument
    will not be supported. The TC also agrees that Add and Multiply
    arguments will BOTH allow multiple arguments in v3. V2 will not
    be updated. The identifier will remain the same in V3.

    Interger overflow - The TC agreed that interger overflow during
    upon type conversion should be handled as an Indeterminate result.

    Rule combining algorithms - The TC will create simpler text
    description to describe combining algorithms as suggested on the
    list. The pseudo code will be listed as non-normative.

   Issue 72 SAML:Where should passed-in policies be inserted

    Hal noted that the spec currently says that there is a top level
    combining algorithm in an implied policy set. The TC decided that
    the provided policies shall be inserted in the presented order
    at the top of this policy set. Hal took an action item to propose
    text which would include more explicit wording on the TLP set.

   Issue 75: Defining an interface for closely coupled PEP/PDP
    This will not be considered part of the core schema, rather it
    will be addressed via a Profile. This is not on the V3 critical
    path.

   Issue 66: Missing attributes may be underspecified
    This will discussed further on the list and will be taken up
    on the next call.

meeting adjourned.