Versions Compared


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


TitleService Catalogue in a Federated world

What if we had common specifications on services exposed to eduGAIN that would allow us to build a service catalogue ? 

We could consider having a first level catalogue, of services offered by NRENs. Then expand this to federation members.

Which requirements would be needed to have such catalogue ? and what are the benefits and risks related to that.

ProposerAnass CHABLI 
Resource requirements

Federation Operators, Service Operators, technical experience, team worked already on the eduGAIN Service Catalogue.


Alex Stuart Mario Reale Casper Dreef Guy Halse Albert Wu Adam Snook 

Comment from SURF: possibly first enhance MET to showcase the (meta)data instead on investing time on this topic 


TitleEnsure MET is maintained

MET ( is widely used. However the issues list is not being addressed and there are frequently operational issues with the service.

Proposal is to first facilitate the community of MET users to articulate their requirements for a MET service (including but not limited to issues on GitHub) and present some potential ways forward.

The REFEDS White Paper "Service Catalogues in a Federated Context" includes a proposal to consolidate the MET and eduGAIN metadata catalogues so this proposed work item may overlap with Anass CHABLI 's proposal for the work item above.

Resource requirementsA short-term WG in the first instance

Matthew Slowe Matt Huckson Nicole Roy Alex Perez Mendez Adam Snook 

+1 from SURF on maintenance, in our view budget is the primary required resource for hiring a maintainer