Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. This work area is going to be political and needs to work closely with various other groups including AARC, JRA3, Enabling Users and FIM4R - will probably need someone to travel and be available at all of these events.
    1. Primary requirement: feedback on discussions at the AARC kick-off and building relationships with that workpackage. 
  2. Need to talk extensively with campuses - work with federations to identify user groups to have discussions with.  NH has already started asking for these.
    1. Develop basic set of questions to ask around assurance schemes and achievability / expense of development. Overall aim is to look at the cost and impact of adopting assurance schemes on IdP organisations. 
    2. Road-test the idea of a step-up assurance service - separate vetting undertaken for small groups run as a separate service.  
  3. Compare back results of the above with original FIM4Paper requirements.
  4. Lack of Identity Management Practice Statements (IMPS) could be a problem.  Most federations claim require them from IdPs but do not enforce them.  Should this be addressed?  Have a look at the REFEDS work on this.

  5. Federations such as InCommon, SWAMID, HAKA and WAYF may have existing information on the cost of implementing assurance, we should ask them to contribute.   Also ask out on the REFEDS list if anyone has any information on cost of implementation.  Kantara?

  6.  End goal is some sort of cost-analysis – is it cost effective for campuses to adopt assurance practices?  We’d like to compare this to AARC proposals but it is unlikely that will develop quickly enough so we can use the Kantara profiles as a starting point. 

Deliverables

  • Report on approaches to implementing assurance requirements across federations. LoA service architecture options and capabilities analysis (report).