Action Items from June 9

(AI) Steve Carmody will coordinate the TAC work list presentation requested by Steering for Steering’s July 11 meeting.

(AI) TAC will provide a written reaction to the InCommon projects/sequencing list, which can then be shared and consulted as the process continues.

(AI) Trust/Identity staff will develop a companion document to the projects/sequencing list, to discuss strategic direction and how the projects/sequencing fit with that direction.

(AI) Steve Carmody will identify those topics on the TAC  work plan ready for working group development and contact potential working group chairs.

Minutes

Attending: Scott Cantor, Jim Jokl, Keith Hazelton, Janemarie Duh, Mark Scheible, Steve Carmody, Tom Mitchell, Walter Hoehn, Kim Milford, Chris Misra, Michael Gettes

With: Dean Woodbeck, Nick Roy, David Walker, Ian Young, Tom Scavo, IJ Kim, Ann West

Action Items

(AI) Chris Misra will draft language for the FOPP, which will then be vetted by TAC and ultimately recommended to Steering

(AI) Steve will incorporate the proposed changes to the “TAC Response to Priority Planning” and send the revised document to TAC no later than June 27 for comment. The document will be finalized after the close of business on June 29 and will be sent to Kevin Morooney for consideration.

(AI) Steve will contact TAC members about draft charters for items on the TAC Work Plan in time for the July 7 TAC call.

Minutes from June 9 meeting approved

Ops Update

IdPv3 upgrade communication

Per-entity Metadata Working Group

Scott Koranda (with LIGO hat) has agreed to chair and InCommon will fund David Walker to flywheel. Will include direct outreach to those we think will be interested in this effort (including those outside of the US). Also, Rhys Smith (UK federation) will have a per-entity metadata service operational in August. He has offered to discuss this with the working group.

TNC Recap (Nick)

Incident Response Processes

TAC has discussed this over the last three meetings. There is a need for InCommon to have the latitude to take action in light of a serious security lapse or breach, but what sort of behavior would trigger a reaction? There is a need to have a statement in place in the FOPP, but also more specific documentation in the wiki. There are also questions about the governance process that would be in place for such a response.

(AI) Chris Misra will draft language for the FOPP, which will then be vetted by TAC and ultimately recommended to Steering. Ann mentioned that the AAC has a similar process that TAC might leverage for this.

New TAC Members for 2017

Given the experience of bringing on new TAC members last year, it is time to begin thinking about a process to have new members on board by January 1, 2017. Roughly one-third of the TAC seats are up for either renewal or filling.

There was also discussion about election of officers. It seems unreasonable to onboard new members, then immediately ask them to vote for a chair. The suggestion is to bring on new members on January 1, then select officers on or about July 1. TAC will discuss this process after Labor Day.

Priority planning

There was a discussion about the document that comprises the TAC response to the trust and identity sequencing list. There seems to be consensus on this document after discussion via email.

(AI) Steve will incorporate the proposed changes and send the revised document to TAC no later than June 27 for comment. The document will be finalized after the close of business on June 29 and will be sent to Kevin Morooney for consideration.

TAC Work List

There was discussion about a couple of items on the TAC Work List.

  1. Deployment Profile - Walter provided an explanation of the “deployment profile” item. These are items that were identified by the Federation Interoperability Working Group as part of its deliberations, but were not addressed at that time. Walter drafted a proposed charter for this follow-on working group: https://spaces.at.internet2.edu/x/6oLmBQ
  2. Compliance - Ann described the business problem this is meant to solve - that the basic requirements for setting up an IdP or SP are not clear. Documentation is also not clear on what IdPs and SPs need to support. The idea is that there would also be a way to test IdPs and SPs on basic operability and evolve that over time to include other requirements. 


(AI) Steve will be contacting TAC members about specific items on the work plan to ask them to draft charters in time for the July 7 TAC call.

Next Meeting - Thurs., July 7, 2016

1:00pm ET | 12:00pm CT | 11:00am MT | 10:00am PT