Page History

TAC Meeting 2016-05-12

Thursday, May 12, 2016
1:00pm ET | 12:00pm CT | 11:00am MT | 10:00am PT

Dial-in Information

+1-734-615-7474 (preferred) (use this number unless you pay for long distance)
+1-866-411-0013 (US and Canada) (use this number if you pay for long distance)

Access Code: 0139713#

eDial: http://edial.internet2.edu/call/0139713

SIP: sip:session_0139713@edial.internet2.edu

If you are on a phone lacking a mute button, you can mute your phone via eDial by pressing ##1. To unmute, press ##1 again.

Agenda

...

...

Minutes

...

1. Review carryover action items below

2. Acceptance of minutes from TAC Meeting 2016-04-28

3. Planning for Face-to-Face at Global Summit/Work Plan 2016

   1. Background documents:
      1. See Ann's prioritization request (thread): https://lists.incommon.org/sympa/arc/tac/2016-05/msg00057.html (includes planning process suggestion re: how ORCID does this) (original note pasted below)
      2. Previous TAC Work Items spreadsheet (DRAFT 1)
         
      3. InCommon 2016 Interim Priority Setting Spreadsheet - TAC View
      4. Task Spreadsheet - DRAFT 2
         
         1. A subgroup had developed a presentation on TAC Work items for yesterday's (cancelled) webinar. DRAFT 2 represents a re-ordering and structuring of the items from DRAFT 1. Items that weren't really defined in DRAFT 1 were omitted.
   2. Action Items: 
      1. All: Before this call, review items in DRAFT 2, preparation for the next two items
      2. Develop list of bulleted desired outcomes (specific tasks)  from each of the work items
      3. TAC members decide who will write up a project description / proto-charter for each
4. (your agenda item here)

Ann's Note:

We had an important meeting last week with three cios/one architect to talk about trust and identity and our analysis of the resources needed to address the external requirements/requests and internal support and development needs. It was illuminating, to say the least.

 We’ll be continuing this conversation at the global summit, engaging a broader group there, but the urgency to move faster and increase sustainability and trust is palpable. Internally, we’re working on better planning so we don’t commit to doing something we can’t follow through on. That’s producing things like the draft documents that Nick sent you last week, and reading between those lines, you can see what the resources are. 

 So this is a request, really a plea, to help us provide two major things: codify at least for now, what practices organizations must support AND help us look towards the federation of the future. Below are three-ish things you can push to make this happen.

...

• Gold Star  Program – While the AAC is working on identitying some simple statements that we can use to make stepwise progress towards replacing the POP (Tom B is TAC rep on that committee), I request that the TAC continue working on my request from last year (that yielded the fed interop profile) to provide clarity on required vs recommended practices. 
  • Rationale: 1) InCommon Central is hearing two diverging opinions: BE flexible on what we require to enable organizations to support their business needs versus BE more definitive on what’s required and hold participants to that standard to enable increased collective trust and progress towards easing interoperability. The TAC is in a perfect spot to lead that community discussion and determine the appetite for conformance vs flexibility. 2) Anecdotally, it’s not clear what our practices are. Jim B, for instance, said he sends links to 9 different wiki pages to those looking to set up new VOs. 3) New diverse participant mix needs clear guidance on what to do. They don’t have time for experimentation. See #2. 
• OIDC – Participant requirements and use cases for OIDC .
  • Rationale: We’re getting “When you support OIDC…” push from members of the community, but I don’t see a list of use cases and analysis behind the participant vs federation requirements. There are multiple gaps in federation support and I’m not understanding the trade offs here vs methodologies to support other non-web needs. Again, the TAC as the community architecture group for InCommon is in a perfect spot to engage the community on the use cases and gaps. 
• MDQ – Participant side of MDQ and ramifications on idPs and Sps as well their requirements for the service. 
  • Rationale: One reason eduGAIN worked so well is that we had  clear documentation for participants and worked with you extensively to understand their needs. The TAC is well suited to engaging the community to understand the impact on the participants regarding MDQ and help us design processes and documentation for them and advocate with software projects (if needed) to support specific features. 
• Membership – Finally, given this the first year under the new charter, remember the TAC must solicit and on-board new members this fall. This takes more time than you think.

Process

As we did last year, the TAC and InC Central priorities should be interleaved and presented along with AAC to Steering for their review. We’ll talk about our list at the TAC meeting next week. As you move forward in your ideas, remember you did this last year and you could start with the items on the list that aren’t yet finished:  https://docs.google.com/document/d/190rL7-K5X1ez0fNOacmz9IfoarbGrHj7YDPtVSbnFdw/edit 

On a recent call with Jim B, I learned about ORCID’s community planning process which I believe is spot on and where InCommon (and Trust and Identity) needs to go. See: http://support.orcid.org/forums/175591-orcid-ideas-forum From my point of view, this provides the transparency into how to submit ideas, get initial feedback about it’s popularity across the participants, prioritize, execute and report out. Excellent stuff. 

Informational Items

1. REFEDS Entity Category and Attribute Call
   Monday, May 23, 2016
   15:30–16:30 CEST (9:30–10:30 EDT)
   (wiki page forthcoming) 
2. Scott Cantor reports that a 32-bit Shibboleth IdP he runs can no longer get enough heap allocation to successfully load InCommon metadata as of the week of 5/2
3. There will be an informal TAC discussion about stance on end-of-life software in the federation at Global Summit - 3-4 p.m. on the 7th floor, we'll meet in front of the Grand Ballroom.  Nick will take notes and report out to those who won't be able to attend.
4. TAC example version of the internal planning process/document that Internet2 T&I is working through now: https://docs.google.com/spreadsheets/d/1oaJwB15TAeBbfNaXnhIHdOFMVgHaD9Y1OcNT4znYWT0/edit#gid=0  (see email from Nick on 5/2 for more detail: https://lists.incommon.org/sympa/arc/tac/2016-05/msg00003.html)

Carryover Action Items

1. Paul Caskey will take charge of the goal “Making Federation Easier”

2. Steven Carmody and Michael Gettes will develop a short white paper to document the requirements and goals related to attribute release.

3. Ann West will develop a service-level agreement concerning the IdP of Last Resort for Leif Johansson and UnitedID

4. Steve Zoppi, Steve Carmody, and Paul Caskey will come back to TAC in two weeks with a proposal concerning "making Shib easier;" specifically about how to leverage work already done through TIER to attract schools and individuals willing to commit to development help.

5. Tom Scavo will run a comparison of the 47 SAML1-only SPs in the InCommon with the SAML1-only SPs currently in eduGAIN metadata.

6. Steve Carmody will follow up with spinning up documentation around Duo deployment best practices, may be homed in MFA interop WG

Minutes

Attending: Keith Hazelton, Michael Gettes, Walter Hoehn, Steve Carmody, Janemarie Duh, Tom Mitchell, Scott Cantor, Tom Barton, Mark Scheible, Albert Wu

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

Minutes from April 28 meeting

...

Approved

Face-to-Face Planning

There was a discussion about the goals and topics for the TAC face-to-face at the Internet2 Global Summit.

...

Ann encouraged a broader view of “ops” than just the technical work. When thinking about eduGAIN, for example, our transition was hugely successful and, once started, took just four months. However, it consumed a lot of time and work not only for the technical implementation, but for communication and education and legal. We received high marks from the community on the transition and the communication stream, but that took a lot of time. We are now looking at the Steward program, per-entity metadata, POP replacement, and SIRTFY; all of which would require a communications plan and effort.

Next meeting

Tuesday, May 17, F2F at Internet2 Global Summit, 9-11 am CT

Remote participation is available.

734-615-7474, or

866-411-0013

Access code is 0193652#

Global Summit

TAC will meet at the Global Summit (the meeting is scheduled for Tues, May 17, 9-11 am, at the Chicago Downtown Marriott.

Next meeting after Global Summit

Thursday, May 26, 1 pm ET