CTAB Call Tuesday May 17, 2022

 Attending

• David Bantz, University of Alaska (chair)  
  
• Jon Miner, University of Wisc - Madison (co-chair) 
  
• Pål Axelsson, SUNET    
  
• Richard Frovarp,  North Dakota State 
  
• Eric Goodman, UCOP - InCommon TAC Representative to CTAB  
  
• Andy Morgan, Oregon State University 
  
• Rick Wagner, UCSD 
  
• Chris Whalen, Research Data and Communication Technologies 
  
• Jule Ziegler,  Leibniz Supercomputing Centre  
  
• Robert Zybeck, Portland Community College  
  
• Johnny Lasker, Internet2  
  
• Kevin Morooney, Internet2   
  
• Ann West, Internet2   
  
• Albert Wu, Internet2 
  
• Emily Eisbruch, Internet2 
  

Regrets 

• Tom Barton, Internet2, ex-officio regrets
  
• Sarah Borland, University of Nebraska regrets
  
• Ercan Elibol, Florida Polytech Institute
  
• Meshna Koren, Elsevier
  
• Dave Robinson, Grinnell College in Iowa, InCommon Steering Rep, ex-officio
  

Discussion

• CTAB liaison to CACTI
  • Suggestion to have a CTAB liaison to CACTI  (Community Architecture Committee for Trust and Identity) and vice versa
    
  • CTAB and InCommon TAC have had liaisons to each other for several years,  but CTAB has never had a liaison relationship with CACTI  
    
  •   There are 3 committees related to InCommon Federation
    
    •           InCommon Steering
      
    •           InCommon TAC
      
    •            CTAB
      
  • CACTI - Top level architecture “steering” group.
    •   informs cross service/software work.  Grew out of the older “MACE” group. 
      
    • CACTI  meets biweekly on Tuesdays at 11am ET.
      
  • DECISION:
    • Thanks to Richard Frovarp who volunteered to be the CTAB Liaison to CACTI
      
    • Richard’s “term” as liaison to CACTI will be until the end of 2022.
      

Working Group Updates Process

• Streamlining regularly occurring working group updates - follow TAC’s convention to send updates via email? 
  
  • Example TAC notes with updates from WGs: https://spaces.at.internet2.edu/display/inctac/InCommon+TAC+Meeting+2022-03-10 
    
• Should liaisons put an update in the CTAB scribing doc, instead of having email updates or verbal updates?  
  
• DECISION:  liaisons will put updates into the CTAB scribing doc.
  
  

Working Group Updates

• InCommon TAC 
  
  • Discussion focused on Digital Wallets:
  •      digital format for claims about a person that are under the control of the person
    
  •       some implementations are based on block chain; unclear whether all are
    
    
  • Discussion about low level of engagement with Wallets and Federations workgroup 
    
  • Digital Wallets Working group will focus on what place the wallets technology have in the higher ed federation landscape/trust fabric.
    Draft charter: https://docs.google.com/document/d/1W_JXZrvgxGCMTdRbn5Ya5gh0LRgZGFcwtX2UVtr5iMk/edit#heading=h.4w7uimsy6s53
    
    
    
• REFEDS Assurance Working Group
  
  • Discussed relationship w OPENID Connect
    
  • OIDC profile for research and education sector
    
  • ACR and AMR claims used for authentication assurance
    
  • Proposal for new ASR claim for identity assurance
    

• REFEDs MFA Working SubGroup

• • Working the way thru new revised profile, hope for new draft in time for TNC.
    
  • MFA is a subgroup of the REFEDS Assurance Working Group
    
  • The profile should go through  the REFEDs Assurance Working Group
    
  • Looking forward to upcoming consultation
    
  • if you’d like to follow the MFA group’s progress, here is the document being edited: https://docs.google.com/document/d/1GGOVFLMZSUSlnDTg42yQlZaVz9LLX3CEUk1Cr0Qqh_o/edit#
    
    
• TLS  CTAB Working Group

• • Tom, Richard and Andy met on May 16, 2022.
    
  • Made new edits to the draft document. Draft is not yet polished
    
  • Addressing issues around resources required and workload.
    
  • Discussion around how to handle a substantial change in SSL labs grading
    
  • How to hand the “hump” of non compliant participants for BE v2
    
    

Quarterly Chairs meeting (Chairs of TAC, CACTI, CTAB, with Nicole Roy and Albert)

• Reflections from cross-committee chairs quarterly meeting  
  
  • Increased collaboration between CACTI and CTAB
    
• Discussed strategies for communicating  the value of multilateral InCommon federation.
  
• There are some issues around supporting Shib
  
• Important to understand federation in a more nuanced way
  
• Some participants, including some major research institutions, are moving towards a commercial solution
  
• Some orgs are maintaining federation for a few research services, such as NIH
  
• Based on a recent email thread, some orgs may move away from seeing InCommon as the solution for streamlined access to SaaS services.
  
• Hosted solutions for brokering new orgs into InCommon could be seen as a gift
  
• Kevin: what is the utility of multilateral? 
  • Publish metadata once, use it many times.
  • With SPs rising and falling within a short period of time, discovery can present a challenge and needs a solution like multilateralism.  
  • Sometimes bilateral SAML relationships are set up and they can be difficult to manage.
    
•  Perhaps we should start to highlight the org to org use case more than, in addition to, the enterprise use case. Need more data
  
• There is an opportunity, not just a threat from the current trends
  
• David: in addition to research projects, another use case requiring the same kind of multilateral infrastructure is for scholarship and journal access
  
• David will share his notes from this Chairs meeting with CTAB
  
• Please inform David if you would like to join a future Chairs meeting. 
  
  • Andy would like to join in the future.
    

InCommon Operations

• Looking at providing more data, including trend reports 
  

CTAB Work Plan

• AI: Review/endorse CTAB Work Plan on wiki before publishing. 
  
•    The CTAB work plan is not public yet. Please “sign off’ on this within 2 weeks
  
•     If Albert does not hear objections, this work plan will be opened up
  
  

InCommon Steering Update

• Kevin notes that In the InCommon Steering agenda there is an “around the horn” meeting for early or late fall.
• Going around all the advisory committees and asking them to share what they are doing.
• A review of all the committee work for Steering.

BE2 status update and next steps (Albert) (Did not discuss on this call)

Next CTAB call: Tuesday, May 31, 2022