CTAB Call Tuesday May 16, 2023


  • Warren Anderson, LIGO
  • Pål Axelsson, SUNET
  • David Bantz, University of Alaska (chair)
  • Tom Barton, Internet2, ex-officio 
  • Ercan Elibol, Florida Polytechnic University 
  • Eric Goodman, UCOP - InCommon TAC Representative to CTAB 
  • Mike Grady, Unicon
  • Johnny Lasker, Internet2
  • Kyle Lewis,  Research Data and Communication Technologies
  • Jon Miner, University of Wisc - Madison (co-chair) 
  • Andrew Scott, Internet2 
  • Andy Morgan, Oregon State University
  • Kevin Morooney, Internet2
  • Albert Wu, Internet2  


  • Matt Eisenberg, NIAID 
  • Richard Frovarp,  North Dakota State
  • Scott Green, Eastern Washington U 
  • Meshna Koren, Elsevier 
  • Rick Wagner, UCSD 
  • Ann West, Internet2
  • Emily Eisbruch, Independent, scribe


Federation Readiness

    • CTAB Workplan InCommon CTAB 2023 Work Plan,
      • see  item 4. Framing the next chapter of federation maturity
    • What are the use cases in which we would like to see greater maturity?
      • have that be the starting point for this work item
    • Work on definition of problems or needs rather than “solutions” 
    • CTAB should take the lead;
      • other groups, including InCommon TAC, may do some of the work
    • need to think about how will the progress be measured?
    • CTAB eventually may want to create charter for a working group on Federation Readiness
    • Good first step - mine previous documented work in
      CIC “cookbook”
      https://wiki.refeds.org/display/FBP/Cloud+Services+Cookbook and likely other repositories (SWAMID)

    • “Prepare for 800-63-4” Federation Assurance Level (FAL) baseline (Tom B)
      • create a FALx baseline
    • New entities seek “check-list” of what they need to do
      • CTAB may want to pivot from compliance driven aspects for Baseline
      • there is a desire for an interface to promote home organization discovery 
      • perhaps provide levels of work in specific areas
    • “Where does general IAM maturity overlap InCommon style federation" maturity? (EG)
    • Articulate unstated assumptions (conventions) experienced practitioners make that remain unknown to newbies (AW, MG) - e.g., on R&S
    • CTAB should present a clear set of preferences, including around qualifying for R&S
      • Don't need to lock everything down, but provide suggested guidelines
    • How to scale up local trust to global infrastructure(?) (PA, TB)
    • There may be advantages to considering Trust separately from Interoperability
      • Trust is hard
      • Interoperability grammar can be specified 
    • When to use an MFA profile? When to use attributes, such as eduPerson?
    • (Andy’s summary) - Maybe InCommon should focus on eduPerson schema only, and stop encouraging vendors to participate for “convenience”.  More strict requirement to use our higher-ed standards
    • NEXT STEP: “Mural” white-board session at next CTAB meeting

Working Group updates

    • InCommon TAC
    • InCommon CACTI - no report
      • Proposed update mostly complete. Expected to go out for comment “soon”
    • SIRTFI Exercise Working Group (Kyle)
      • Survey on what community would like for such training opportunitues going out 1 June
      • IAM Online ‘How to Sirtfi” presentation planned 19 July
    • REFEDS Assurance (Kyle)
      • (short presentation update to CTAB on RAF 2.0 is ready)

    • Community Exchange Highlights (Albert and Kevin)
    • Albert: IDP as a Service Pilot is starting

Next CTAB Call: Tuesday, May 30, 2023

  • No labels