Versions Compared

Key

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

Please use this page to record ideas that you would like to include in the 2024 REFEDS work plan. Copy and paste the template table below. Ideas don't need to be fully formed but the more scope we can get, the easier it will be to assess whether the idea should be taken forward. We look forward to all your ideas! 


Table of Contents
maxLevel3

Template

Title<title of your proposal here>
Description<description text here>
Proposer<your name here>
Resource requirements<money? effort? coordination? unicorns?>
+1's<for others to voice their support - add your name here>

Ideas

Titleupdate REFEDs specs to leverage OpenIDFederation
DescriptionThe OpenID Federation specification is gaining increased traction. The REFEDs specifications currently do not define how to express them in OpenID Federation. This working group will idenify issues with the current REEFDs specification wrt using OpenID Federation, it will propose changes to existing speficiation or popose new one if needed.

As an initial proposal the work could be cut up in 3 phases:
  • Investigate the REFEDs specs and identify potential places where the REFEDs specifications need to be updated
    This work has already been started in the GEANT Trust and Identity Incubator, though at the time of writing the document is not yet complete.
  • Propose changes to the REFEDs specifications to be discussed and within the REEFDs community
  • Specs with behavioral and trust rules. Several REFEDS specs do not only define a technical specification, but also take it account behavioral rules and trust aspects. It is proposed to engage with these specifications last, as these will need not only technical adoption of the specification but may also required changes to the description of the behaviours.
ProposerNiels van Dijk (SURF)
Resource requirementsStandard support tools for WG and meetings.
+1's<for others to voice their support - add your name here>


TitleeduID Operator Group
Description

A group of NREN's offer an IdP service that is not bound to a specific organisation, for example as an IdP of last resort and IdP for home organisations that don't manage their own. My suggestion is to create an operator group so that have a place to discuss and exchange ideas and operational guidelines.

A possible first outcome could be a position paper on how eduIDs perceive themselves (what unifies the eduID?)

ProposerPål Axelsson (Sunet) (addition by Maarten Kremers)
Resource requirementsTime for the group to convene and create a charter and thereafter mail list, slack channel, wiki space and meetings.
+1's

Maarten Kremers (SURF)

Marlies Rikken (SURF)

Peter Havekes (SURF)

Wolfgang Pempe (DFN)

Christoph Graf (Switch)

Laura Paglione


TitleMetadata about federations in metadata aggregates
DescriptionTo find information about federations today require that you go to each one of them you're interested to and manually gather the information or go to eduGAIN technical site and look for what is manually registered there. I suggest a working group that discuss and may define a metadata extension that include information and policy links plus contact information that is published in the federation metadata feed so that others easy can aggregate this for example in MET and the technical eduGAIN site. The solution should be federation technology agnostic with examples for both SAML and Openid technology federations.
ProposerPål Axelsson (Sunet)
Resource requirementsStandard support tools for WG and meetings.
+1's

Davide Vaghetti (GARR)

Wolfgang Pempe (DFN)

Albert Wu (InCommon)

John Scullen (Australian Access Federation)

Alex Stuart (UK federation)

Nicole Roy (InCommon)

Niels van Dijk (SURF and GEANT Incubator)

Björn Mattsson (Sunet)


TitleDefine a REFEDS profile for registering support for entity categories or frameworks in metadata 
DescriptionToday all working groups need to define if and how an entity shall indicate in metadata that they support a specific REFEDS specification. To make that more generic I suggest that we create a working group that define a REFEDS framework on how this should be done. Today REFEDS entity categories and SIRTFI have this defined in their specifications but it would be good to have specific profile on how to do ths for all REFEDS framworks, profiles and entity categories.
ProposerPål Axelsson (Sunet)
Resource requirementsStandard support tools for WG and meetings.
+1's

Davide Vaghetti (GARR)

Wolfgang Pempe (DFN)

Albert Wu (InCommon)

Björn Mattsson (Sunet)

David Walker (How does this relate to the SeamlessAccess trustinfo proposal below?)


TitleDefine a REFEDS profile for phishing-resistant multi-factor authentication
DescriptionWithin its chosen scope, the existing MFA profile is great, but that scope leaves some space when it states: "Protection against active man-in-the-middle attacks is out of scope of this Profile." . There are protocols in the wild which do provide phishing resistance (most prominently, WebAuthn/FIDO2), and those are rolled out progressively by many big players. These new phishing-resistant MFA methods are a new level in the game of authentication assurance, and it feels wrong to put something like "password+TOTP generator (susceptible to phishing)" and "biometrics+cryptographic keypair (w/channel binding and phishing resistant)" into the same bucket. Phishing-resistant MFA deserves being recognised as its own class of authentication assurance, with a distinct REFEDS profile.
ProposerStefan Winter (Restena)
Resource requirementsa large amount of copy&paste from the existing MFA profile, and discussions on the exact formulation in an incarnation of the MFA subgroup.
+1's

Christoph Graf (Switch)

Zacharias Törnblom (Sunet)


TitleSupporting Open Science Through Attributes
Description

Programs such as the US Government's Open Science initiative are likely to drive requirements for attributes beyond "researcher" and "member". Resource Providers will need additional information about a person’s qualifications in order to determine access to their services. This work item intends to

  1. Capture use cases for open access/open science in order to identify the various classes of problems that will need to be addressed
  2. Collate and compare existing community efforts that may be able to support these use cases and authorization decisions
  3. Make recommendations for how the identified problems could be addressed.
ProposerBenn Oshrin, Albert Wu, Alan Buxey
Resource requirementsMeetings. More Meetings.
+1'sLaura Paglione, Tom Barton, Ken Klingenstein, Peter Gietz (FIM4L)


TitleBrowser Changes, continued
DescriptionContinued to coordinate concerns about Browser Changes to mitigate third party cookies and navigational tracking, including "replacements" like FedCM and wallet space work
ProposerJudith Bush
Resource requirementsSlack Channel, individuals with ability to attend W3C community group and working group meetings, Confluence space. Occasional meeting.
+1'sHeather Flanagan, Scott Cantor, Nicole Roy, Gary Windham, Zacharias Törnblom


TitlePromote REFEDS for VC governance
DescriptionThe "verifable credentials world" is about to reinvent many things REFEDS has developed for the international academic interfederation world for years. This covers e.g. federation standards, attribute specs and governance structures to manage all of that. We should try to figure out how to carry over those achievements to the "verifiable credentials world".
ProposerChristoph Graf (Switch)
Resource requirementsGroup of willing to come up with ideas and to propose a set of actions
+1's

Heather Flanagan

Albert Wu (InCommon)

Pål Axelsson (Sunet)

Nicole Roy (InCommon)

Laura Paglione

Niels (SURF) [This might partially overlap with my proposal above to look at REFEDs specs in the context of OpenID Federation]


TitleStandardising Standards!
DescriptionThere are areas of REFEDS specification creation that could use improvements specifically:
  • to ensure that repeatables elements within specifications are standardised and worded in the same way for consistency and user support
  • to create a standard way of editing and managing changes to specifications within working groups (e.g github?)

This would help us step up as a standardisation body and give the sort of consistency seen in other areas.

ProposerNicole Harris
Resource requirements
+1's

Heather Flanagan

Albert Wu (InCommon)

Alex Stuart (UK federation)

John Scullen (Australian Access Federation)

Pål Axelsson (Sunet)

Laura Paglione


TitleFormalise SeamlessAccess trustinfo metadata as a REFEDS specification
DescriptionTrustinfo metadata has been developed by the SeamlessAccess team. A working document exists and code is in development (perhaps even deployed) in SeamlessAccess. This work item is to take the specification through the REFEDS standardization process, which should facilitate uptake by federation operators.
ProposerAlex Stuart
Resource requirementsA short-term working group, a consultation, a stable URI for the specification
+1's

Pål Axelsson (Sunet)

Zacharias Törnblom (Sunet)

Albert Wu (InCommon)

Björn Mattsson (Sunet)

David Walker


TitleA basic eduPerson/schac SD-JWT Verifiable Credentials schema
DescriptionThe working group will produce a specification for a basic SD-JWT verifiable credential representing a  person and their institutional affiliation based on the eduPerson and schac schema. Think of this as the basic student and/or employee "card" for the R&E wallet ecosystems.
ProposerLeif Johansson (SUNET) and Peter Leijnse (SURF)
Resource requirementsA relatively short-term group. The goal is to produce a straw man specification before Q3 2024. We will look for active engagement from EU, US and Asia as a minimum requirement for success.
+1'sPål Axelsson


TitleDefining user experience (UX) principles for FIM
DescriptionThis working group will produce principles and best practices to support better user experience (UX) across federations (for discovery services, access management tools, coherent terminology etc.). We aim to create a knowledge base of existing research, practical examples and existing implementations that can serve as best practices for implementers.   
ProposerFloris Fokkinga (SURF) and Marlies Rikken (SURF)
Resource requirements

Standard support (collaborative workspace and meetings)


+1's<for others to voice their support - add your name here>