Minutes

Attending: Joanne Boomer, Matthew Brookover, Judith Bush, Matthew Economou, Heather Flanagan, Eric Goodman, Les LaCroix, Matt Porter, Steven Premeau, Mark Rank, Keith Wessel

With (Also Starring): David Bantz, IJ Kim, Johnny Lasker, Nicole Roy, David Walker, Ann West, Albert Wu, Steve Zoppi

Status Updates

• International, SeamlessAccess, and Browser Updates

• Federation 2.0

• CTAB Update
• Federation Testing Working Group
• T&I Update
  • Johnny Lasker: A new release of the Federation Manager is expected next Wednesday with eduroam-related updates.
  • Steve Zoppi: There has been recent discussion about Internet2 underwriting priorities for software projects. The following guide decisions for the coming year:
    1. Community Education and Adoption
    2. Leverage/Sustainability
    3. Documentation Clarity, Consistency and Organization
    4. Succession / Augmentation / Advancement of IAM Community
    5. Feature / Functionality Heuristics (assessing the degree of use of each available feature/function)
    6. Determinism in Software Requirements Fulfillment/Delivery
    7. Solution interoperability with Commercial, Off-the-Shelf (COTS) offerings.
  • Ann West: The IdPaaS proposal has been approved by Steering. The idea is to add a lightweight layer on top of the Catalyst Program. There will be more information coming; we may have an agenda item on this next month.

2021 TAC Accomplishments

• Everyone please review 2021 TAC Accomplishments before the end of next week. If there are no unresolved issues by then, it will be declared final and published.

Liaisons to committees

• Thanks to Eric for continuing as our CTAB liaison, Matthew for his past service as the CACTI liaison, and Steven for his future work as the next CACTI liaison.

Finalize InCommon Discovery Futures Recommendations

• Mark has resolved all comments, adding one suggestion to complete the incomplete sentence at the end of the main body of the document.
• There were no objections from the TAC members to the document.
• Ann will review the document and offer suggestions she may have. Once final, she will deliver it to Steering.
• Albert will clean up the draft, adding page numbers, date, list of authors, etc. He will also find a home for it in the federation library to ensure that it's discoverable by searches.

Finalize 2022 Work Plan

• 2022 TAC Work Plan was discussed and updated per that discussion. Highlights include:
  • There are many issues (communication strategy, change management, etc.) surrounding a rollout of likely recommendations from the Deployment Profile and Subject Identifier activities.
  • The Subject Identifier work will start with a level set by Albert as an agenda item next month. Following that, a subset of TAC members will propose a path forward, perhaps including chartering a new working group.
  • Heather solicited comments on the draft charter for the digital wallets group at https://docs.google.com/document/d/1W_JXZrvgxGCMTdRbn5Ya5gh0LRgZGFcwtX2UVtr5iMk/edit#
  • It was decided to drop the suggested "Roadmap to seamless R&E integration/interoperation" activity for 2022.

Next Call February 10, 2022

EMail Updates

International, SeamlessAccess, and Browser Updates

International Update
REFEDS

• The R&S Working Group continues its efforts to harmonize the Anonymous Authorization and Pseudonymous Authorization entity categories with the Personalized Entity Category. Included in this effort is a first draft of Federated Authorization Best Practices. The working group is looking for feedback on that article via the rands@lists.refeds.org mailing list.
• Mark Rank (Cirrus Identity) has joined the REFEDS Schema Editorial Board. The SEB is kicking off a new subcommittee on defining an attribute for pronoun choice; anyone interested in chairing this group should contact Heather Flanagan. People interested in joining should sign up to the mailing list

Conferences

• TNC22 is still on target for an in-person conference in Trieste, Italy, from 14-17 June. The program committee has chosen the main sessions; reviews of lightning talks will be next on their list. Expect further announcements regarding the final program in a few weeks.
• Identiverse is also on target for an in-person conference in Denver, Colorado, from 20-23 June. The program has not been announced, but the quality of the conference in past years is quite high.

SeamlessAccess
The product roadmap is always available to the public: https://seamlessaccess.org/services/

The organization is planning on a webinar in March, focusing on the UI/UX feedback from various SeamlessAccess Integrators.

Browser Interactions
Heather Flanagan, along with Jason Griffey (NISO) and Tim Lloyd (LibLynx), has recorded a session called "Access Apocalypse: Be Prepared for Anything" for the upcoming NISO+ conference. The session is scheduled to air on 17 February 2022; while the session itself was recorded, Q&A will be live.

The FedID CG is working on its first Community Group Report, collecting the problem statement, terminology, use cases, and potential solutions in one document. The chairs hope to have publishable draft ready before the end of Q1 2022.

Federation 2.0

The Federation 2.0 has had its final edits in response to the consultancy period and will be in REFED’s hands in time for the late February meeting of REFEDS Steering.

CTAB Update

CTAB Update for TAC

The working group/liaison updates actually accounted for a reasonable amount of time on the call this week. The more notable items covered:

• Status of the SIRTFI Exercise WG (closing in on a schedule for the exercises)
• R&S 2.0 updates (related to the Anonymous/Pseudonymous/Personalized data bundles)
• NIH activities updates

There was the normal BE2 compliance review. Work moves along well, though there are of course sticking points/organizations.

Finally the 2022 CTAB work plan was discussed.

• One of CTAB’s largest focuses is “scaling interoperability”. This includes:
• Encouraging heightened trust and assurance to promote interoperability
• Discouraging one to one linking, promote federation
• There were other areas of focus (identity assurance, mfa, etc) but the area most relevant to TAC in my mind was related to interop and large commercial IdPs
• This discussion ended up overlapping with the work done by the IdPaaS workgroup TAC initiated.
• We talked a bit about this and Mary McKee has been brought out of “TAC Retirement” to talk with CTAB about the workgroup’s outputs.
• As part of the conversation Ann mentioned some ongoing work within InCommon in support of furthering some of the IdPaaS recommendations (that I was unaware of), which made me think maybe we should have a status update in TAC as well.

Federation Testing Working Group

Colleagues,

InCommon’s TAC wishes to develop a testing infrastructure that can help InCommon participants validate their inter-operational readiness.

A call for working group members went out in the usual channels and there was little interest. I write to you all specifically as your interest in the profile may also lend some sympathy to this effort. Perhaps you missed the earlier calls? Or, you may not be prepared to serve on a working group, but you might be interested in helping define some of the testing behaviors for specific elements of the profile.

The InCommon TAC has had a small team review the deployment profile and classify the requirements into requirements that are (1) currently expected of participants, t(2) hat are important to guide participants into following, and (3) some that need more time for InCommon to be prepared to expect participants to fully comply (*cough* logout *cough*).  That team also classified whether behavior could be controlled by the federation metadata manager, tested, or if the behavior would be left for community members to report to InCommon.

This review means that where the working group charter  --  https://spaces.at.internet2.edu/display/fedtestwg/Federation+Test+Environment+Working+Group+Charter – says “Develop the testable Deployment Profile requirements into specific, implementable testing criteria” we already have a prioritized list of the requirements that we believe could be reasonably tested by InCommon.

Perhaps you might have enough time to

1. Sign up for the mailing list so if there’s something targeted you can help with, you will hear about it
1. Join the Federation Testing WG Mailing List. Email incommonsympa@incommon.org with the subject line:
   Subscribe fedtestwg [Firstname] [Lastname] 
2. Let us know when you could be available for a meeting to kick off this work the week of Feb 7^th  https://doodle.com/poll/dfvnygtn2s46regn
3. Be a co-chair of the group? Let me know!

Thanks,

Judith Bush