CACTI call of Oct. 2, 2018

Attending

Members

  • Chris Phillips, CANARIE    (chair)  
  • Tom Barton, U Chicago   
  • Rob Carter, Duke   
  • Nathan Dors, U Washington   
  • Jill Gemmill, Clemson   
  • Ann Harding, SWITCH/GEANT  
  • Karen Herrington, Virginia Tech   
  • Todd Higgins, Franklin & Marshall College 
  • Christos Kanellopoulos, GEANT  
  • Les LaCroix, Carleton College     

Internet2 

  • Ann West 
  • Emily Eisbruch
  • David Walker 

Regrets

  • Warren Anderson, University of Wisconsin-Milwaukee /LIGO 
  • Tom Jordan, U Wisc - Madison     
  • Steve Zoppi ,  Internet2
  • Kevin Morooney,  Internet2 

Discussion

 FIM4R Recommendations Review 

  • FIM4R Assessment public coordination page: CACTI-Discuss-Topic-Internet2 FIM4R Assessment
  •  The team has done more prioritization  of the feedback recommendations since our last CACTI call.    
    • Priority Recommendation : Support Collaboration as a Service 
  •  Within edugain, there is a minimum implementation for an IDP. There can be profiles to indicate a better level of readiness for federation.  Best common practices.   
  • Suggestion to leverage the CTAB work around Baseline Expectations (BE) 
  • Support adding both R&S for higher ed IDPs and SIRTFI to BE
  • Best to avoid another tagging scheme.
  • Regarding the recommendation around CILogon, we may want to be sure we are looking at the whole class of services.
  • Globus  Online  is another option. https://www.globus.org/
    • Globus Online relies on CILOGON. But would be worth having discussions with Globus
    • Globus is based on OAuth and Globus is developing OAuth and OIDC standards
  • eduTeams https://www.geant.org/Innovation/eduteams
  • Sometimes it’s necessary to choose a service to support. 
  • We should continue to keep an eye out for critical efforts
  • AnnH: Campus IDP work on federation has been less successful than on the eduroam side
  • IdP as a service may be complex. Need to give campus control
    • InCommon TAC is looking at IDP as a service
  •  IDP as a service is a good idea, this can help bridge the gap around R&S adoption
  • There was consensus that the team (Jill, Karen, ChrisP, etc)  is on the right track with the FIM4R response work. Will develop another draft for TechEx. 


OIDC R&E WG update   

  • OIDF R&E WG has been accepted by OIDF… what’s next? Things are moving along at a good pace 
  • https://openid.net/wg/rande/ 
  • Oct 1, 2018 - planning meeting yesterday 
  • Oct 15 - REFEDS
  • Oct 16-19 - TechEx
  • Oct 19 - OIDC WG chair/leads bonus session
  • Milestone: alignment between OIDF R&E, REFEDS OIDCre, and InCommon OIDC-OAuth; people with needs/interest know where to go. 
  • Oct 22 - OIDF meeting (before IIW) 
  • Oct 23-25 - IIW https://www.internetidentityworkshop.com/ 
  • OIDF R&E WG - most work driven via mailing list; bi-weekly calls alternating between times friendly to EU and Asia Pacific. 
  • Need to do more training and learning around OIDC 
  • Question:  How are we handling communications with REFEDs? 
  • Answer: there was good representation on the Oct 1 planning call including many Europeans 
  • ChrisP: At TechEx in Orlando, we hope to move the needle on communication and clarification on where to go for particular topics and how people can get connected 
  • ChrisP is informing the edugain Steering group 


EduPerson transition 

  • No course change, proceeding as planned. 
  • REFEDs steering will vote within a few days on the eduPerson transition


TechEx in Orlando 

    • open CACTI meeting at TechEx in Orlando (Thursday, Oct 18 at lunch 10/18/18 12:10PM-01:30PM )  
    • https://meetings.internet2.edu/2018-technology-exchange/detail/100052 
    • Proposed Agenda for open meeting. 
        1. FIM4R assessment  
        2. Outreach and engaging research platforms open discussion
          1. Continue the conversation on how to expand our reach to benefit other areas such as Pacific Research Platform and other efforts.
        3. An update on state/next steps of Sunset for MACE-DIR

  • Community Updates
    • Jill: Food for thought:  IDP as a service  -- we would have benefited from having this years ago
    • For CIOs, budget and resources are an issue, but the IDP as a service would be a huge benefit