----------------- Event Title: Bi-weekly PSTC meeting Date: Monday, 21 May 2012, 02:00pm - 03:00pm ET Description

1-866-682-4770 conference: 1938387 passcode: 123456 View Details :
http://www.oasis-open.org/apps/org/workgroup/provision/event.php?event_id=30864

This meeting counts towards voter eligibility.

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

Agenda

1) Call Roll.

2) Approve minutes from April 23 meeting.

3) SCIM Strategy (Prateek Mishra / Gary Cole)     - Outlook for convergence     - Implications for PSTC

4) AOB

Minutes

Chair: Gary Cole

Attendees: Gary Cole (Oracle) Marco Fanti (Oracle) Karsten Huneycutt (UNC-Chapel Hill) Prateek Mishra (Oracle)

1) Call Roll: - Gary took roll. - Quorum *was* achieved (4 of 6 voting members attended) - Voting status changes: None. 

2) Approve minutes from April 23 meeting. - No one objected to approving the minutes as posted in the calendar-event.

3) SCIM Strategy (Prateek Mishra / Gary Cole)     - Outlook for convergence     - Implications for PSTC

Gary recapped the events since the PSTC restarted: SPMLv3 -> Use-Cases ->
RESTPML -> SCIM -> What's Missing? -> Why Do You Need That? - Movement for a new version of SPML led to an effort to clarify use-cases for
enhancements. - Writing use-cases revealed that V2 already addresses most needs.  Some
require adjustments, but most require only examples. - Excitement at SCIM's RESTful style of interaction led to a proposal for
RESTPML.  Excitement at standard-schema led to a proposal for SIMPLEST. - Marketing traction and excitement at the simplicity of SCIM led people to ask
whether SCIM replaces SPML.  - Some participants analyzed gaps between SPML and SCIM.  Most notably,
Phil Hunt proposed extending SCIM to support multiple targets. - Some contributors to SCIM don't understand the need for targeting or
other extensions, don't want anything to delay ratification of SCIM 1.0.

Gary believes that this brings us almost full-circle, back to (the need for)
Use-Cases: - Enterprises, App-Vendors and IDM Vendors want to know what's missing and
why it's needed.  We need to develop the Use-Cases. - Use-Cases underlay every feature and function in SPMLv2.  They were in
discussions and in emails, but were not delivered as part of the standard. - OASIS rules have changed.  TCs now may deliver such ancillary documents
as Committee Notes. - Gary asks whether participants agree that developing use-cases is important.

Prateek agrees that use-cases would be valuable:   -- SCIM is currently defined narrowly, very focused and unlikely to
change scope without a push.   -- Customers are confused because the name and the marketing seem to
indicate that SCIM will meet all their needs.   -- Cloud seen as fundamentally different and easier.  Anyone who
disagrees "just doesn't get it."   -- Need use-cases to clarify how identity-management will work for
enterprises using clouds.

Karsten asks: What is the goal of such use-cases? - The first use-cases we wrote were to justify possible extensions/corrections
to SPMLv2. - Then we got focused on the RESTful binding for SPML and the SIMPLEST
data-model.

Gary replies that the goal of development use-cases for enterprise IDM seems
two-fold: - To justify convergence (i.e., to justify extensions to SCIM) if the IETF WG
is interested. - To justify divergence (i.e., to justify RESTPML or some "wrapper"
to SCIM) if the IETF WG is not interested.

Karsten pointed out the need for other work within the scope of existing SPML,
e.g.,: - Formal errata document exists, but is not widely known, is not easy to find,
might need some updates. - Formalized SOAP binding would be valuable to those who deploy the existing
standard.

Prateek commented again in support of the need for use-cases: - Most SPML deployments were within the enterprise (often baked into IDM
products). - Deployments within the enterprise often did not cross formal administrative
boundaries. - Within an enterprise, administrative boundaries can be bent or broken more
easily than premise-to-cloud or cloud-to-cloud.

Gary promised to post to the list a draft of use-cases (business-functions,
topologies) that explain the scope of SPMLv2: - Brevity and clarity will be very important; will need help from
committee-members. - Draft may be abstract (in the interest of brevity); will need help to add
concrete examples wherever this helps.

4) AOB: None.

Owner: Gary Cole Group: OASIS Provisioning Services TC

Sharing: This event is shared with the OASIS Open (General Membership), and
General Public groups.

Public Event Link: http://www.oasis-open.org/committees/event.php?event_id=30864

BEGIN:VCALENDAR CALSCALE:GREGORIAN METHOD:PUBLISH VERSION:2.0 PRODID:-//Kavi Corporation//NONSGML Kavi Groups//EN X-MS-OLK-FORCEINSPECTOROPEN:TRUE BEGIN:VTIMEZONE TZID:America/New_York BEGIN:STANDARD DTSTART:20001029T020000 RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10;UNTIL=20061029T060000Z TZNAME:EST TZOFFSETFROM:-0400 TZOFFSETTO:-0500 END:STANDARD BEGIN:STANDARD DTSTART:20071104T020000 RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=11 TZNAME:EST TZOFFSETFROM:-0400 TZOFFSETTO:-0500 END:STANDARD BEGIN:DAYLIGHT DTSTART:20000402T020000 RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=4;UNTIL=20060402T070000Z TZNAME:EDT TZOFFSETFROM:-0500 TZOFFSETTO:-0400 END:DAYLIGHT BEGIN:DAYLIGHT DTSTART:20070311T020000 RRULE:FREQ=YEARLY;BYDAY=2SU;BYMONTH=3 TZNAME:EDT TZOFFSETFROM:-0500 TZOFFSETTO:-0400 END:DAYLIGHT END:VTIMEZONE BEGIN:VEVENT CATEGORIES:MEETING STATUS:CONFIRMED TRANSP:OPAQUE DTSTAMP:20120521T000000Z DTSTART;VALUE=DATE-TIME;TZID=America/New_York:20120521T140000 DTEND;VALUE=DATE-TIME;TZID=America/New_York:20120521T150000 SEQUENCE:504 SUMMARY:Bi-weekly PSTC meeting DESCRIPTION:\n 1-866-682-4770 conference: 1938387 passcode: 123456\n\nAgenda: \n 1) Call Roll.\n\n 2) Approve minutes from April 23 meeting.\n\n 3) SCIM Strategy (Prateek Mishra / Gary Cole)\n - Outlook for convergence\n - Implications for PSTC\n\n 4) AOB\nGroup: OASIS Provisioning Services TC\nCreator: Gary Cole URL:http://www.oasis-open.org/apps/org/workgroup/provision/event.php?event_id=30864 UID:http://www.oasis-open.org/apps/org/workgroup/provision/event.php?event_id=30864 BEGIN:VALARM ACTION:DISPLAY DESCRIPTION:REMINDER TRIGGER;RELATED=START:-PT00H15M00S END:VALARM END:VEVENT END:VCALENDAR