[provision] Minutes of the October 11 meeting of the OASIS PSTC

["Daniel A. Perry" <Daniel.Perry@skyworthttg.com>]

Minutes of the October 11th meeting of the OASIS PSTC.

Meeting Date: 	October 11th, 2010
Meeting Time: 	2PM Eastern
Location:		Tel=866.434.5269  Meeting Number=9406791
Duration: 		Approximately 50 minutes
Chairs:		Richard Sand, Gary Cole
Recording Secretary:	Dan Perry

Attendees:

Tom Zeller (Internet2)
Anil John (JHU-APL)
Chi Wu (JHU-APL)
Gary Cole (Oracle)
Marco Fanti (Oracle)
Hal Lockhart (Oracle)
Kent Spaulding (Oracle)
Dan Perry (Skyworth TTG)
Richard Sand (Skyworth TTG)
Karsten Huneycutt (UNC-Chapel Hill)

Several voting members from recent meetings were unable to attend:
Dale Olds (Novell)
Anil Saldhana (Redhat)
Prateek Mishra (Oracle)
Darren Rolls (SailPoint)

In addition, several non-voting members from previous meetings were
unable to attend:
James Bryce Clark (OASIS)
Robin Cover (OASIS)
Mary McRae (OASIS)
Chris Obremski (JHU-APL)
Todd Clayton (Skyworth TTG)


Agenda:
1) Roll Call and Agenda Review
2) Approval of Sep 27th Meeting Minutes
3) Discuss the PSTC charter
4) Discuss Use Cases
5) AOB


1) Roll Call and Agenda Review:
- Richard took roll.
- Quorum was achieved (10 voting members present).
- Voting status changes: none.


2) Approval of Sep 27th Meeting Minutes:
- Richard Sand moves to approve the 9/27 minutes.
- No objections.


3) PSTC Charter
- Richard Sand asks the group if we are close to having a clarified
charter, and if we are ready to vote on the revised charter in the
near-future.
- Gary Cole: Agrees that the current draft of the charter looks good.
- Richard Sand: Suggests making the next meeting (on 10/25) a deadline
for comments on the charter.
- Gary Cole: Agrees that the deadline should be next meeting.
- Hal Lockhart: Mentions the we are doing a charter update to clarify
the existing charter. Also notes that the approval of the clarified
charter requires a ballot run by TC admin.
- Richard Sand: Will polish up draft charter to and send list for a last
review.  Next meeting we will take a committee vote on whether to put
charter to ballot.
- Gary Cole: Agrees


4) Use Cases

- Richard Sand: Suggests coming up with a bullet list of what use cases
"could be".  That bullet list can then be handed out to interested
members so they can complete writing up those cases.
- Gary Cole: Thinks that sort of an approach might be interesting.   
- Richard Sand: Elaborates that he would like to use a list of use case
to help get things moving.
- Gary Cole: Asks to see more detail. Was expecting that people already
had use cases in mind to illustrate the short comings of SPML.
- Richard: Reiterates earlier point, looking to use the bullet list to
draw out people's interests in SPML as a tool. 


- Richard Sand: Moves on to discuss higher-level IDM functions in SPML.
SPML is very focused on lower level CRUD operations. Possible higher
level functions that come to mind are password resets & role management.
- Anil John: Asks for details on what exactly are these higher level
functions.  Asks if they are they included in the existing SPML 2.0
standard.  Also asks if these functions are implemented in other
standards like SAML.
- Richard Sand: Clarifies that we haven't got the point to decide
whether we need to extend the current SPML standard or not.  Wanted to
explore using higher level functions to make implementing use cases
easier.  These higher level functions seem to be really useful for
service providers being able to stand up very atomic operations for the
services they provide and not just provide lower-level operations.
- Gary Cole: Asks for specific examples as to "what" can't be done with
the current SPML standard.
- Richard Sand: States that he's trying to point out the differences
between what the current SPML standard can technically do and what the
standard can do "well".
- Hal Lockhart: As background, there are several things that can be done
with submitted use cases by TC.   One is to declare use cases
out-of-scope for the particular TC.  Another is to use concepts like
profiling to come up with a way to handle the use case.   A final way to
handle a use case is to add support for that case to the existing spec.
Going back to the specific conversation at hand - at this point the most
important thing to do right now is to capture enough detail in the uses
for the TC to make such a decision in the future.
- Richard Sand: Agrees with Hal's comment.   States that his main point
is that SPML lacks some of the higher-level features to make it function
smoothly.
- Gary Cole:  States that he is trying to keep "conclusions from being
drawn before the argument is made".  He is looking forward to see
proposed use cases.
- Richard Sand: Will have use cases out to the list for review by the
next meeting (on 10/25).


5) AOB
- Richard Sand: Asks if there is any other business.
  (No Responses)
- Gary Cole moves to adjourn the meeting.


** Next meeting: Monday, October 25, 2PM Eastern Time (UTC-05:00)
Eastern Time (US & Canada). **



Dan Perry
239 Kings Highway East | Haddonfield | New Jersey 08033 | USA
Mobile: +1 609 721 2219 | Office: +1 856 795 1722 | Fax: +1 856 795 1733