Versions Compared

Key

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

eduGAIN Steering Group Meeting

Thursday 30th April 2015 - 10:00 - 11:30 CEST (in your timezone)

9:30Arrival & "Can you hear me now?" via https://connect.sunet.se/edugain
10:00Welcome, Introductions & Agenda Agreement
10:15

Summary of Current Status

See http://edugain.org/technical/status.php

  • 32 Participating Members
  • Members that aren't participating (5)
    • Argentina - MATE
    • Australia - AAF
    • New Zealand - Tuakiri Identity Federation
    • Portugal - RCTSaai
    • Turkey - YETKIİM
10:30

New member questions, candidates and policy status

Candidates (4) with Policy & MRPS available

  • Armenia - AFIRE
  • Belarus - FEBAS
  • Georgia - GRENA Identity Federation (GIF)
  • Moldova - LEAF

Candidates (3)

  • India - INFED
  • Oman - Knowledge ID
  • Serbia - iAMRES

Known Federation Initiatives (11)

  • China - CARSI
  • Korea - KISTI ID Federation
  • Luxembourg - eduID
  • Malaysia - MyIFAM
  • Mexico - FENIX
  • Morocco - eduIDM
  • Peru - INCA
  • Russia - ФEDUrus AAI
  • Slovakia - safeID
  • South Africa - SAFIRE
  • Uruguay - RAUid

It is hoped that the situation regarding the above federations can be cleared up prion to the meeting so that it is know whether we are voting on their membership or providing additional feedback to the federation operators on their process.

Voting/objecting to progressing federations to membership status.

10:45

What is the value in a vote?

Discussion in light of the above assessment and discussion on the mailing list.

11:00

What does it mean to exchange metadata?

11:15

GN3plus is dead - GN4 is beginning - what does this mean for eduGAIN?

Summary of Harmonisation Task - Nicole Harris, GÉANT Association

-

Any other Business

Q1: Does "eduGAIN" want to take on a trust router/ABFAB protocol and what are the implications of doing so?

Q2: Will the eduGAIN SG govern and oversee trust router infrastructure usage and peering? Is eduGAIN-OT responsible for the infrastructure?

Q3: Is the supplied profile sufficient or is an eduGAIN Constitution change required? Timeframe? Who?


11:30

Summary, Actions and Close (or we're running over time).

...

ACTION20150430-02: NH to circulate the MRPS for comment.  

 6.  Any other Business - Moonshot

Moonshot Profile raised by Rhys Smith and the Questions posed by Chris Phillips (rephrased by Brook)

Q1: Does "eduGAIN" want to take on a trust router/ABFAB protocol and what are the implications of doing so? i.e. Does edugain want to represent different technology profile approaches within its strucuture? 

 - Introduing a new trust broker as different workflow from the MDS - currently not well structured to do this.  Would have to focus on this.  There are also implications about a trust model where the trust broker is not run by a central operational team. f there is more than one service, "mandatory" vs. "optional" becomes more complex; there can be profiles which are optional in the sense that you don't need to implement if you don't use a particular service, but which are mandatory if you do want to use that service. The SAML 2 metadata profile would be one of those, for example.

Q2: Will the eduGAIN SG govern and oversee trust router infrastructure usage and peering? Is eduGAIN-OT responsible for the infrastructure?

 - difficult if trust broker is distributed rather than centralised in the current edugain MDS model. 

Q3: s the supplied profile sufficient or is an eduGAIN Constitution change required? Timeframe? Who? 

 - The constitution would need changing as it is too tightly coupled to a SAML workflow.  Process does not mention the role of the MDS at all - this needs to be brought out more in the SAML profiles.  

Q4: This is an optional profile, right?
 
 - Would have to be - although mandatory vs optional becomes more complex.  

Q5.  Why is this not an eduroam profile? Is this different from adding RADIUS / eduroam profile to eduGAIN? 

 - not easy to fit in eduroam model - very different (e.g not a single service model).  

Q6.  What would be the consequences  for current eduGAIN members of Moonshot becoming part of the eduGAIN policy framework?

 - Need to seperate the two questions.  Current document is not a profile - it is too open ended so cannot be voted on now.  This is seperate from the question of whether we want to change eduGAIN constitution to allow it to be used for new approaches.  This needs to be started now.  As a community, we need to be convinced that there is a good reason to change this basic approach.  

ACTION20150430-03: Rhys / Brook / Nicole to work on an FAQ that looks at the issues involved in introducing an new technology profile to eduGAIN. 

7.  Any other Business - WAYF

7.1. WAYF have started publishing (proxy) IdPs to eduGAIN 3 now - 90 soon

7. 2. PHPH tool at https://phph.wayf.dk - screencast at https://youtu.be/Jv_xYdd1Hrs

7.3. Does anyone have a set of Ian style XSLT rules for eduGAIN md requirements ?

 - https://github.com/ukf/ukf-meta? but not upstream rules. 
 - edugain validator? other pre-flight check style approaches?

Action Summary:

ACTION20150430-01: Brook to move the current candidates forward to vote and then consider the proposed changes to the process with the OT and other relevant stakeholders. 

...