Versions Compared

Key

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

Participants


Name

Organisation

Infrastructure / Project / Community Represented

Member Status

Here

Christos Kanellopoulos

GEANT

GEANT, AARC

Chair

Y

Rudolf Dimper

EOSC-A

EOSC-A

Member

Y

Wolfgang Pempe

DFN

DFN-AAI, NFDI

Member

Y

Lukas Vojacek

IT4I

HPC, EOSC - ENTRUST

Member

Y

Jonas Söderberg

Uppsala University

SciLifeLab NBIS

Member

Y

David Groep

Nikhef & Maastricht University

AARC

Member

Y

Peter Balcirak

CESNET

AARC, LSAAI, e-INFRA CZ

Member

Y

Marina Adomeit

SUNET

SUNET, AARC, GEANT, PUHURI

Member

Y

Tomasz Kuczyński

PSNC

PIONIER.Id, GEANT

Member

Y

Berk Balci 

CERN

WLCG

Member

Y

Francesco Giacomini

INFN

AARC-TREE, WLCG

Member

Y

Marcus Hardt

KIT

AARC / HIFIS / NFDI

Member

Y

Logan Ayliffe

SURF

SURF Research Access Management

Member

Y

Jean-François Perrin

ESRF

ESRF, PaN Community

Member

Y

Ivan Kanakarakis

SUNET


Member

Y

Eisaku Sakane

NII

HPCI / GakuNin

Observer

Y

Tom Dack

STFC

SKA, IRIS

Member

Y

Davide Vaghetti

GARR

GARR, GEANT (eduGAIN)

Member

Y

János Mohácsi

KIFÜ

KIFÜ, AARC TREE, GÉANT

Member

Y

Nicolas Liampotis

GRNET

AARC

Member

Y

Klaas Wierenga

GEANT

GEANT

Member

Y

Licia Florio

NORDUnet

NORDUnet, EOSC, AARC TREE

Member

Y

Hussein Sherief

AASCTC

AAScTCloud on work (observer)

Observer

Y

Agenda

...

/ Notes

Introduction to the EOSC AAI Working Group

  • The meeting marks the beginning of the EOSC AAI Working Group, which is part of the Technical and Semantic Interoperability Task Force under the EOSC Association.
  • This group continues the work of the previous EOSC AAI Task Force (2021 - 2023).
  • Support from AARC (Authentication and Authorisation for Research and Collaboration) helps reach a wider community.

Membership and Participation Rules

  • Membership includes official members of the Technical and Semantic Interoperability Task Force and contributors from the wider EOSC stakeholder community.
  • International participation is welcomed, with non-European participants marked as observers.
  • Participants who miss five consecutive meetings will not be considered active contributors and will not be added as contributors to the outputs of the WG

Focus on Practical Implementation

  • The EOSC Association emphasises the need for practical, pragmatic approaches to EOSC implementation.
  • The focus should be on creating clear, concise guidelines for newcomers and infrastructures joining the EOSC Federation.
  • The group aims to produce shorter, more practical documents rather than extensive theoretical work.

Requirements and Architecture Profiling Activities

  • The group will focus on understanding requirements and addressing them, rather than creating new standards.
  • Work involves pushing standardisation requirements to international efforts in AARC and profiling how to apply standards within the EOSC Federation.
  • Syncing with recent developments in the EOSC EU node is crucial.

Timeline and Milestones

  • The group aims to update the EOSC architecture, targeting a new version by the end of 2025.
  • Engagement with stakeholders and identification of new use case requirements is a priority, leveraging ongoing work in AARC-TREE.
  • By Q1 2025, the group aims to have a clear understanding of the current status quo within EOSC and open issues/requirements.
  • By the end of Q4 2025, the group will address identified gaps and issues in a time-boxed manner.
  • In Q1 2026, the group will conduct another round of information gathering and requirement updates.
  • By the end of 2026, the group will finalise their work and update the EOSC architecture.

Meeting Logistics and Communication

  • Bi-weekly calls will be held initially, with the frequency to be reassessed after six months.
  • A mailing list has been set up for communication between meetings.
  • Meeting documents will remain closed to the public initially, with minutes published on a wiki page after acceptance at the next meeting.
  • This approach balances openness with the need for a safe environment for discussion and addresses potential sensitivities around information sharing.

Actions