CTAB Wed March 13, 2019


  • Brett Bieber, University of Nebraska 
  • David Bantz, University of Alaska, acting chair for this call
  • Rachana Ananthakrishnan, Globus, University of Chicago
  • Tom Barton, University Chicago and Internet2
  • Brad Christ, Eastern Washington University 
  • Eric Goodman, UCOP - TAC Representative to CTAB 
  • John Hover, Brookhaven National Lab 
  • Adam Lewenberg , Stanford 
  • Jon Miner, University of Wisc - Madison 
  • John Pfeifer, University of Maryland  
  • Chris Whalen, Research Data and Communication Technologies  
  • Albert Wu, Internet2
  • Emily Eisbruch, Internet2   


  • Mary Catherine Martinez, InnoSoft (chair)  
  • Chris Hable, U of Michigan
  • Ann West, Internet2

Action Items from this call

  • AI Albert will report back to Dean on the discussion around the BE survey
  • AI Albert will prepare a template report for reporting to Steering on orgs not meeting Baseline as of March 14, 2019


 2019 Internet2 Global Summit 

Final call on BE Survey feedback 

    •  There was discussion of audience for  the planned survey and it was suggested that most likely the InCommon participants list is the right audience
    • Three different possible purposes for the survey, to determine:
      • 1. How did Baseline Expectations go 
      • 2. In what direction should Baseline Expectations  go from here? 
        • (we are working on Strawman CTAB Roadmap and can get feedback)
      • 3. What about Assurance program (bronze and silver)
    • Currently , the survey covers 1. only. 
    • Decision, keep the survey as is, but engage the community going forward on the roadmap plans
    • AI Albert will report back to Dean on the discussion around the BE survey

Updated immediate CTAB work plan with security focus (error URL, SIRTFI) 

Work Package Theme -- Protect Collaboration Resources / Manage Risk

    Proposed Key Activities

  • All InCommon participants must meet SIRTFI

  • All InCommon IDPs must publish error URL

  • All InCommon participants must operate current, supported software

  • Discussion
    • Is running Shib required?  
    • No, but must be a supported software,  
    • Note, an organization can’t declare SIRTFI  and have unsupported software
    • Vulnerabilities of certain XML libraries has been an issue
    • Browser standards
    • CTAB will need to be prepared to address many questions.
    • Error URL is more straightforward than the other two

Refine “semantics” of upcoming BE requirements? (David) (10 min)

E.g., A what should a error URL really be for? 

         B  Parallel to work from Deployment Profile WG?
Deferred this item for this week due to need to work on docket

  • Dispute Docket Close Out (Albert) (20 min):

    1. Steering Overview doc delivered on March 11, 2019
    2. MC and Ann have shared updates/context with Steering so Steering is expecting next steps. 
    3. Albert reminded orgs under extension as of March 12, 2019
      Several SPs are responding today
    4. Time to prepare the final Steering review list
    5. Report to Steering should expand on these for each org that is not yet in compliance with Baseline Expectations.  
      1. Org status and relationship to InCommon  
      2. Nature of non-compliance 
      3. Contact history
      4. Recommended action

  • Albert will be careful to differentiate between a campus and its SPs that may be out of compliance (we will not identify an organization as out of compliance per se)
  • For recommended action, if staff is changing and they need more time, we need to give them more time.  
  • Consensus:  bilateral agreement SPs that are out of compliance must removed from InCommon metadata despite the fact they don’t really federate (no exception based just on an SP being “bilateral”)
  • It can be hard to know if an SP is bilateral or federated

  • Q: are there some orgs on the docket that we have not yet done enough work to contact?
  • Albert will do another manual check to review that all orgs have been reached out to.
  • Albert: there a handful of orgs that have not yet paid their InCommon dues, we may have  NOT reached out to those
  • There are 58 orgs that have not met BE to date.
  • Decision:  send out one more email to those orgs not yet meeting BE saying, by this date we are forwarding your org to InCommon Steering and by this date your entities may be removed from metadata.
  • In report to Steering,   the contact history will be included 
  • If Steering members want more background that can be provided
  • AI Albert will prepare a template report

Next CTAB Call: Wed. March 27, 2019

  • No labels