Attending  

Warren Anderson, LIGO 
Pål Axelsson, SUNET 
David Bantz, University of Alaska (chair)    
Tom Barton, Internet2, ex-officio
Gabor Eszes, Univ of Virginia (rep from CACTI)   
Richard Frovarp,  North Dakota State  
Mike Grady, Unicon   
Johnny Lasker, Internet2
Kyle Lewis,  Research Data and Communication Technologies 
Ryan McDaniel, University of Alaska Anchorage    
Jon Miner, University of Wisc - Madison (vice chair)   
Kevin Morooney, Internet2  
Emily Eisbruch, Independent

Regrets

Ercan Elibol, Florida Polytechnic University 
Matt Eisenberg, NIAID 
Scott Green, Eastern Washington University
Christopher Keith, Brown University 
Andrew Scott, Internet2
Rick Wagner, UCSD
Ann West, Internet2 
Kathy Wright, Clemson, (InCommon TAC rep to CTAB )   
Albert Wu, Internet2     

Discussion

  • Intellectual Property Reminder  - All Internet2 activities are governed by the  Internet2 Intellectual Property Framework.
  • Public Content Notice  - CTAB minutes are public documents. Please let the CTAB and note taker know if you plan to discuss something of a sensitive nature.


Working Group Updates

  • CACTI – largely a meeting of briefings and presentations from leaders of efforts in Internet2, and how CACTI can fit into these efforts in the future.
    • Recap of SIRTFI exercise by Andrew Scott
    • Discussion of Certificate Service Redesign by Sara Jeanes
    • Near-final comments on finalizing charter for Next-Generation Credential Trust Framework WG
      • Will be public soon
    • Futures2: IAM Architecture Blueprinting, and CACTI’s role, by Nicole Roy and Steve Zoppi

  • eduRoam Advisory Committee (has been under CACTI but charter is changing)
    • This group could benefit from having liaisons to other InCommon advisory groups
    • There is some overlap with CTAB
    • We can put out the call to see who on CTAB would like to be a liaison, but wait to talk to eAC chair (Brett Bieber)
       
  • InCommon TAC
    • Expectation to use MDQ was discussed

  • SIRTFI
    • Nothing Significant to Report (NSTR): continuing on track for Phase 0 practice exercise with working group in June

REFEDS Assurance Framework 2.0: Risk Comparison to NIST SP 800-63-3 IAL2

    • A statement from NIST for this report was requested and this was agreed to  yesterday (by Ryan Galluzzo)
    • Perhaps the statement will talk about methodology 
    • Establishes InCommons value to services operating within federal agencies
    • Should be part of InCommon Federation expectations
    • Public Comment Period for Rev 4 of NIST SP 800-63 expected to start around end of June 2024. Will emphasize the need for risk based security management.
    • Hoping to engender profiles of NIST SP 800-63 for various communities 
    • Perhaps after updated RAF guidance, next task for CTAB could be a higher ed profile for meeting NIST SP 800-63
    • New CTAB sponsored working group
      • Need a working group to look at RAF implementation guidance
      • This is on the CTAB work plan https://spaces.at.internet2.edu/display/ctab/ctab-2024-work-plan
        • Work plan item: CTAB24-1: Update REFEDS Assurance Framework Implementation Guidance for InCommon Participants
      • CTAB agrees to spinning up the working group
      • Kyle will work on spinning up the working group, including a call for community participation 
      • See process here 


InCommon Futures 2 topics

  • Kevin’s Futures 2 update


2. Kevin’s requests to suspend advisory committee elections (turnover) this year.

      • Hoping for greater administrative efficiency
      • Kevin flywheels InCommon steering
        •  12 hours per year
        •   We spend at least 2 of those 12 hours talking about next year’s roster
        •   Hope to get some of that time back
      • Hoping for cognitive continuity as we work on implementing InCommon Futures 2
      • Base CAMP is coming up, we need to set correct expectations on whether there will be open advisory committee slots

    • 3. Need to change target of advisory committees from InCommon to InCommon AND to the army of people who need it 


  • Key Activities coming out of the InCommon Futures2 Report:
    • Activity 1: Communicating the Value Differently
      • Relates to dissemination of knowledge 
      • This is already happening
      • InCommon working with Internet2 community engagement team  
      • We (InCommon) needs to think and speak about ourselves differently

    • Activity 2: Provide Foundational IAM Guidance to the Community
      • Shift in attention in the toolkit context : Shift a bit away from doing and towards advising 
      • Emphasize guidance documents


    • Activity 3: Navigating Demographic Changes
      • Higher Ed institutions want to collaborate to deal with changes
      • Need friction-free environment for students dealing with many course management systems
    • Activity 4: Increase Collaboration across Higher Ed, Research and Federal Agencies

    •  Activity 5: Refresh Community Engagement Approach (deferred until later in the year) 


  • DISCUSSION
    • Question: is there a risk of clashing with Educause as we move forward with InCommon Futures2?
    • Kevin: I am interfacing a lot with Educause
    • Yes, there could be some “collisions”
    • Educause is focusing in the decision support space
    • Worth looking at the Educause strategic plan 
    • https://er.educause.edu/articles/2023/10/introducing-the-new-educause-strategic-plan
    • Educause is not engaged in the work around technical issues such as NIST standards, etc. 

    • Question: Re the question of “Are these InCommon Advisory groups the correct ones ?”
    • Which parts of the items in the slides are a call to action to the InCommon Advisory groups?
    • Kevin: we don’t know yet, this will evolve

    • Other comments:
    •  Breakdown of the goals of the Futures2 report into an action plan with 5 activity areas is helpful 
    • When IAM Team staff members change in InCommon member organizations should we know about this so we can do a better job of training (providing knowledge and context) to new people?


Planning for 2024 Technology Exchange in December 9-12 in Boston


Next CTAB call: Tuesday, May 28, 2024

 

  • No labels