You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 10 Next »

This consultation opens on Thursday 23rd June 2022 at 18:00 CEST and closes on Thursday 21st July at 18:00 CEST

Background

The eduGAIN Futures Group was established with the following goals:

  1. To review the REFEDS Baseline Expectations document and make proposals for changes to eduGAIN to support the baseline.  
  2. To identify key issues with current eduGAIN service provision and make recommendations for improvements (e.g. support mechanisms for CoCo and R&S, lack of service offer to Service Providers, technology support for OIDC etc). 
  3. To review the governance model for eduGAIN and make recommendations for improvements.
  4. To cross-reference proposals with other working groups and the eduGAIN service teams.  

Out of scope:

  • Direct policy revision - this work will be carried out based on the recommendations of this group.

Full information about the group can be found at: eduGAIN Futures Working Group Charter. 

Overview

The eduGAIN Futures Working Group met on a two-weekly cycle since its inception to produce a set of recommendations for the eduGAIN Steering Group and the eduGAIN Service Team.  A draft white paper has been produced and is now shared with the wider FIM community for consultation and comment.


The document for the consultation is available as a pdf attachment.  All comments should be added to the changelog below or sent directly to: edugain-discuss@lists.geant.org.  Comments posted to other lists will not be included in the consultation review.

Change Log


comment #Line/Reference #Proposed Change or QueryProposer / AffiliationAction / Decision (please leave blank)
1NAInclude names and organizations of contributing authors and editor(s)Nicole Roy
2144Does this mean that all participatings federations would have to switch to an opt-out policy? Our (DFN-AAI) constituency wouldn't accept that, I'm afraid... (currently, 314 out of 374 IdPs are exposed to eduGAIN - after all).Wolfgang Pempe
3144I see here a possible conflict with Baseline Expectations FO1 and FO3, especially in terms of filtering out untrustworthy entities from the eduGAIN downstream metadata. Currently, this only applies to SAML1-only-entities, but the next step will be to remove SPs without a Privacy Statement URL. If the Steering Group were to ban such a thing, we'd have a problem...Wolfgang Pempe

























  • No labels