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

Compare with Current View Page History

« Previous Version 3 Next »

The approach to prioritise use cases was discussed on 5 Feb 2026 and the principles are copied below.

Context

As the community of NRENs within the GEANT community, we have been involved in «identity stuff» for decades. One of the most visible services it produced is eduGAIN. That is where we come from.

The most important stakeholders we do this for are:

  • Students
  • Researchers
  • University administration

Our specific focus in our GEANT collaboration was generally speaking:

  • Making local stuff interwork – often interfederating national federations
  • Setting standards for this to work sustainably – with a specific focus on the international research and education community 
  • Establish collaboration channels and governance structures – mostly through the GÉANT organisation and projects
  • Emphasis on Europe, but reaching out to other regions for global interoperability – where possible with similarly scoped regional players

Scope

Let’s narrow down the wallet use cases we would like to work on:

  • We are not pushing wallets for the sake of the wallets, but only care for wallets as long as they are doing interesting stuff for us
  • To create focus, let us concentrate on the X most interesting ones, where 3 < X < 10

Proposed prioritisation principles

Some criteria for prioritisation of wallet use cases:

  • Comprehensibility: We want to go for use cases that are not «too academic», but easily understandable for most
    • Nothing that needs lots of explications and community insights
  • Benefit: We can easily describe the added benefit with respect to existing solutions we have in place or easy to grasp benefits for problem statements we did not address so far
    • We should not go for marginal gains, but rather for major steps
    • We do not want to compete with existing solutions, but enable new stuff
  • Legitimation: We want to go for use cases we have an estalished position and can easily «claim territory» in some way
    • It should be apparent that our community has experience and a role in this use case
    • It should be clear that we are needed here, we do not need to explain our raison d’être
  • Product or governance vision: It should be a use case where there is some future role in running it for us on GÉANT/NREN level
    • We do not focus on paving the way for others, but primarily for ourselves
    • We are not doing research but shaping our own future

Existing collections of use cases

Use cases used in GN5-1: https://wiki.geant.org/x/WgeLKg

Use case collection of GN5-2: https://wiki.geant.org/x/OwHbRg


  • No labels