Child pages
  • 2015 Work Plan Preparation

Versions Compared


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



Fed Ops Security Incident Response

DescriptionMost federations have wording in their federation policy to support incident response but this tends to be a few words committing the Op, IdP and SP to work together on issues.  There is no developed idea of the workflow for incident reporting and it is difficult for SPs to understand the process across different federations or contact multiple federations.   REFEDS should define a common process and workflow descriptions for federations and support a lightweight model for supporting incident reporting and discussion - possibly via the FOG list or an XMPP type approach.  As discussed at ACAMP.
ProposerNicole on behalf of ACAMP session.
Resource requirementsREFEDS Coordinator time, buy in from federations, possibly some small infrastructure support requirements.
+1'sTom Barton, Wendy Petersen (CAF), Dave Kelsey, Scott Koranda, Romain Wartel, Michal Prochazka, Ann West, Heather Flanagan, Lukas Hämmerle, Jean-François Guezou
ConsensusProceed - keep lightweight.

Global FedLab

DescriptionLots of useful tools have been produced as part of FedLab - as seen in Roland's excellent presentation in Indianapolis.  There have also been other tools developed across the community to monitor and check information - such as MET, Code of Conduct monitor, Lukas's domain-checking tool for edugain, SMEV etc. etc.  Some of FedLab will be moved to production as part of the GN4 project under the Identity and Harmonisation Task, but this will only address specific GEANT Project use cases.  A pilot should be undertaken by REFEDS to look at global requirements and the best set of tools for our community.  In the longterm this may merge back with GEANT service offerings but it makes sense to run a pilot under REFEDS to address all possible features.
ProposerLicia Florio, Nicole Harris, Roland Hedberg
Resource requirementsFunding for hosting and coordinating testing and decisions around useful tools.  Development effort can be provided via GN4.
+1'sTom Barton

EduGAIN Global incident handling/support framework


As national federations continue to join eduGAIN the problem of supporting users across federation boundaries will increase. When a user has an issue attempting to access services provided in another federation how it will be resolved in this global federation of federations. Issues the end user may experience include;

  • Understanding where the cause of the problem is;
  • Language barriers;
  • Service providers unaware that their services is available in other federations;
  • Services providers unwilling to provide support to users in other federations;
  • Global scale and time zone difference challenges

The development of a global incident handling/support framework. This framework would build on each federation’s user support strategies and seek ongoing support of the framework from federation through a memorandum of understanding.

ProposerTerry Smith (AAF) and Sat Mandri (Tuakiri)
Resource requirements

1) Development of a service oriented approach eduGAIN Global Support Framework to provide seamless user experience, including:

i. Capability to log support request from anywhere (eduGAIN Support Zendesk)

ii. Incident Management process for National Federation on eduGAIN

iii. Incident Management process for Service Providers (Institutional, National, and International SPs)

2) A program of work to ingest (1) above into all national federations participating in eduGAIN.

Development and documentation of the framework Marketing of the framework and buy in for federations

Risk and Issues

eduGAIN to publish a register for participating members to log and manage Risk and Issues

+1'sHeath Marks (AAF), Wendy Petersen (CAF)
ConsensusThis is an edugain operational issue and some of the info is being looked at - e.g. helpdesk functionality in GN4.  Not for REFEDS.