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

 


Help: OASIS Mailing Lists Help | MarkMail Help

cloudauthz message

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


Subject: 31 March 2014 TC Meeting Minutes


AnilSaldhana_RedHat: Agenda

1. Roll Call, Agenda Review and Meeting Minute Taker Nomination.
2. Approval of minutes

AnilSaldhana_RedHat: 3. Use Case Document public review comments

AnilSaldhana_RedHat: 4. Context Driven Entitlements document discussion

5. Other Business

6. Adjourn

anonymous morphed into Felix Gomez (NEC)

AnilSaldhana_RedHat: 1. Roll Call, Agenda Review and Meeting Minute Taker Nomination

AnilSaldhana_RedHat: Meeting Attendees   Spreadsheet
Company Name ascending Role
JPMorgan Chase Bank, N.A. Shaheen Abdul Jabbar Secretary
NEC Corporation Felix Gomez Marmol Member
Citrix Systems Andrew Innes Voting Member
Bank of America Radu Marian Chair
Red Hat Anil Saldhana Chair

AnilSaldhana_RedHat: Quorum: 4 /5 voting members (80%).  quorum achieved.

AnilSaldhana_RedHat: 2. Approval of minutes

AnilSaldhana_RedHat: 17 March 2014: https://lists.oasis-open.org/archives/cloudauthz/201403/msg00007.html

AnilSaldhana_RedHat: Andrew moves; Anil Seconds

AnilSaldhana_RedHat: Meeting minutes are approved.

AnilSaldhana_RedHat: 4. Context Driven Entitlements document discussion

AnilSaldhana_RedHat: https://www.oasis-open.org/committees/document.php?document_id=52632&wg_abbrev=cloudauthz

AnilSaldhana_RedHat: Shaheen: look at Trust Elevation Document where context has been defined.

Radu Marian (Bank of America): from trust elevation deck: "Context includes, but is not limited to, location, time, party, prior relationship, social relationship and source"

AnilSaldhana_RedHat: if you have other examples, please suggest.

AnilSaldhana_RedHat: radu:  healthcare and government example.

Radu Marian (Bank of America): had to drop - apologies

Andrew Innes (Citrix): Thought I had while listening to the descripion of the stock mobile app: why would someone use a standards-based entitlement protocol to represent the available stocks for trading, rather than just create a broker specific web service API that conveys that information? However someone on the call was listing a number of other reasons why it would be useful to have a generic standards-based representation (though I didn't catch them all). Could this motivation for using entitlements be captured in the introduction?

AnilSaldhana_RedHat: Comments Archive: https://lists.oasis-open.org/archives/cloudauthz-comment/201403/threads.html

AnilSaldhana_RedHat: 3. Use Case Document public review comments

AnilSaldhana_RedHat: Postponed to next call to allow for more comments to flow given comment end period is 26 April.

AnilSaldhana_RedHat: 5. Other Business

AnilSaldhana_RedHat: No meeting on April 14th as chair has to travel.


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