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: Minutes for 17 August 2017 TC Meeting


Time: 4:30 PM EDT (-0400 GMT)
Tel: 1-712-775-7031
Access Code: 620-103-760

Minutes for 17 August 2017 TC Meeting

I. Roll Call & Minutes

 attendees:
Steven Legg
Rich Levinson
Hal Lockhart
Bill Parducci


  bill: we have quorum

  Approve Minutes 20 July 2017
   https://lists.oasis-open.org/archives/xacml/201707/msg00010.html

  hal: any objections to unan approval: none heard
	minutes approved

II. Administrivia

   Errata Status
    TC admin announces XACML 3.0 Core Errata:
      https://lists.oasis-open.org/archives/xacml/201708/msg00001.html

   rich: Home page has been updated w approved errata links
     https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=xacml

   Updates to statements of use for Xacml 3.0 profiles:
    JSON profile:
     https://lists.oasis-open.org/archives/xacml/201707/msg00011.html
     https://lists.oasis-open.org/archives/xacml/201707/msg00014.html

  hal: some people have json impl but don't support the abbreviations
        - will make sure it's on the mailing list

  steven: did emc provide stmt of use for json profile?
  hal: will try to check; steven: that would give us 3

  steven: rest profile is problematic:
           example in profile is different from internet draft


III. Issues


   Is time-in-range conformant with time-equal?
    steven:
     https://lists.oasis-open.org/archives/xacml/201707/msg00015.html
    bill:
     https://lists.oasis-open.org/archives/xacml/201707/msg00016.html
    steven:
     https://lists.oasis-open.org/archives/xacml/201708/msg00000.html

   should work in different time zones: i.e. is the range local or ref'd remote
    i.e. does 10AM in Melbourne satisfy 9AM-5PM in NYC?

    time in range doc appears ambiguous; should be consistent w "time equals"

   hal: thinks it was intended to be ref'd to defining entity time zone.

   there's also a 52-hr range, which is confusing;

   hal: maybe what was agreed was not what actually it came out to be based
         on some specs defn of time.

   hal/steven: probably best approach is to add some new functions to fill the gaps

 next meeting: 4 weeks: 14-sep-17
  mtg adjourned: 4:55 PM





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