Minutes
Attendees: Keith Wessel, Derek Eiler, Joanne Boomer, Mark Rank, Matt Porter, Steven Premeau, Krysten Stevens, Eric Goodman
Reps from other groups: David Bantz,
Staff: Johnny Lasker, David Walker, Albert Wu, Nicole Roy, Kevin Morooney
Regrets: Heather Flanagan, Judith Bush, Les LaCroix,
Scribes: Mark Rank / Joanne Boomer
- Intellectual Property Reminder - All Internet2 activities are governed by the Internet2 Intellectual Property Framework. - done
- Public Content Notice - TAC minutes are public documents. Please let the TAC and note taker know if you plan to discuss something of a sensitive nature. - done
- Call for scribe volunteers ( 2 per call) - recording / transcription available - done
- Missing one approval for the 12/13 minutes
- Agenda Bash + request for notable working and advisory group updates - none
- Status Updates - Q&A
- T&I - Johnny reports fed mgr delegation functions communicated
- InC Discovery service outage – was discussed by T&I, Nicole summarized the response
- CTAB - work plan was main topic: including operationalizing conformance to Baseline Expectations, additional standards/practices to increase trust & assurance & interoperability, NIST 800-63 rev 4 draft, assurance, follow up SIRTFI exercise; probably some joint CTAB/TAC/CACTI work
- Reminder - REFEDS MFA profile consultation on 1.1 draft - 15 Jan 2023
- T&I - Johnny reports fed mgr delegation functions communicated
- (20 min) Finalize 2022 Accomplishment Report
- Thanks all for summary - HECVAT section was added Thurs morning
- Still blank section for entityID creation and use – is there anything to be said? A call for vote was sent out. Silent consent was reached. Albert will capture decision and there is some internal work that needs to happen.
- Reminder (not final decision) – https://docs.google.com/document/d/1B9-OlMgtuik4G_hADLFkbWwcwZv1XIu0gtppqjyal9c/edit#heading=h.hks6tdf7r4t0
- There was discussion outside of the document – as much as there may be to want to limit to URL, disallowing other options is not practical
- Should we strike from report? No, Albert will suggest a “blurp”. TAC firmed up a position but no action.
- There was a thread of work for SP Middlethings. A couple of sentences - Mark will draft something. Tgt COB Friday.
- Was there a section on the Wallets in report — yes
- Get next sections in, and everyone read between now and next call. Please raise any comments/feedback in doc or via TAC-List
- (20 min) Finalize 2023 Work Plan
- At face-to-face we did talk about work plan and discussed handling a wide range of of items or focus on a few and try and complete.
- Flushing out items first and write up descriptions so we understand what it means before deciding if we will tackle or not.
- Federation Testing -
- This was copied from last year. There was discussion about putting a different spin on it for this year. Last year came from desire for participants to be able to measure whether their implementation is sufficient for interoperation. Tooling and testing implementation for adherence to interoperation standards.
- At end of last year there was interest in using the tooling and testing criteria but very few people volunteered to help create this criteria.
- Albert still believes this is important but do we have enough momentum and a body willing to flush out requirements and developing test cases. If we take on the work it will be to continue from last year and continue developing test cases.
- Keith - Do we need a high level TAC group? Albert - If there are parties to continue to work on this in a small group. Quick show of hands on indication of interest or table?
- Mark proposes tabling it as in the first half of the year there will be testing of other work (FedCM API from Google).
- Eric - assumption is that fed testing is directly related to the next work item, Adopt SAML Deployment profiles & Subject Identifiers.
- Albert - main value is to help those who are onboarding to verify their implementation configurations are working as expected. It’s less compliance for the sake of compliance but knowing your implementation is working. Place on how to make federation easier.
- Derek indicated the value of work, Nicole indicated there were probably resources that can be found.
- Reminder Working group is formal and has a chair and outcome (usually a report). Subgroup is information and outcome is more flexible. Will fill in some blanks and come back.
- Adopt SAML Deployment Profile & Subject Identifiers
- Progress last few year but is now aligned. Need nudge.
- Release value statement
- Some surveying of what low hanging
- Mark as chair
- Also want to use this work to drive revamp federation
- The Future of Federations and Digital Wallets
- Yes — need to move
- CACTI will also be talking about and also MACE-DIR responsibility.
- For TAC, more where is this going to be used
- Proposal is some joint work
- From face-to-face, CACTI was taking lead
- Strong Maybe – consult with Judith
- Middlethings?
- Air time during techex – probable table for 6mo
- Revisit next time.
- Anonymous, Pseudonymous, and Personalized Entity Categories - What does InCommon do with them?
- Needs to be fleshed out
- Might carry on with the subject identifiers
- Strong candidate - practical way to carry forward
- Keep scope controlled – have InC statement about them. Have guidance for early adopters
- Propose Time box this to the first 3 months
- NIST 800-63 Revision 4 Consultation - Review and Feedback
- (10 min)TAC liaisons to CTAB and CACTI, and TAC SME needs for 2023?
- Eric and Steve – are you ok continuing as liaisons
- Eric - happy to continue
- Steve - happy to continue
- Any concerns from the group – drop Keith feedback directly in the next few days.
- N.b., from Eric… feel free to send to me as well (if you’re happy with me continuing but there’s anything specific you’d like to see done differently!)
- Eric and Steve – are you ok continuing as liaisons
- Adjourned 2:01 ET