Code | Work Item | Type | Due | Dependencies | Comment |
---|
1 | Task Management | Subtask | | | |
| Quarterly reports | EC Deliverable | M4, M7, M13, M16, M19, M25, M28, M31 | | We need to provide info to NA1 c6 weeks before those due dates |
1.1 | eduGAIN policy review | | | | |
1.1.1 | Review text of GDRP | | M4-M6 | | Get input from Andrew C |
| Review Federation interpretations of impact on their local and eduGAIN systems | | M6-M8 | | |
| Develop statements and recommendations for stakeholders | | M8-12 | | |
| M9.2 Assessment of DP Legislation Implications | EC Milestone | M8 | | Does not need full TA review |
1.1.2 | International CoCo Development | | Ongoing | | Dependencies - GDRP, Privacy Shield. Cross-ref with REFEDs |
1.2 | eduGAIN Metadata and Attribute Release Management | | | | Devs not available til Sept/Oct, prob not full speed until Jan |
| Federation Operational Practice Statement | | 29/07/2016 | Brook | |
| Check dev implications with Tomasz | | Sept | | |
| Outreach for Attribute Release Takeup (CoCo, R&S) | | Ongoing | | Review after one year |
| KPI monitoring & effectiveness monitoring for attribute release | | M1 - set up KPI graphs from eduGAIN DB | | |
| | | M6, M18, M30 effectiveness check | | See if this can be automated with Lukas's tools |
| Improved audit test/tools (e.g.Fedlab test adoption in eduGAIN) | | Y2/Y3 | | OT will finish integraton of Lukas's tools |
| Best practice metadata management - MDS Aggregation Practice Statement [MAPS] | | 29/07/2016 | Brook | |
| Scalable metadata release tools | | Y2, Y3 | | |
| Market analysis of developments improving metadata exchange peformance | | Y2, Y3 | | |
| Monitoring & statistics | | M5-M22 | | Not expllicitly mentioned but needed and can fit in the rubric 'metadata performance' |
| Prepare monitoring spec - data required, reports required, import spec, engineering specs | | M5 | | |
| Prototype with H&S - max 2 federations | | M8 | | Also acts as learning/induction tool for the developers |
| Pre-pilot version - inc. partial data from mesh fedederation | | M14 | | |
| Pilot (provisional) M16-M22 | | M18-M22 | | |
| Attribute translation tools at Federation level - enhance FaaS | | Y3 | | |
| Update eduGAIN CBA | | M8, M20, M32 | T0 Brook | Suggest to do this 1x per year rather than for each increment in this subtask unless the investments needed are big |
1.3 | Supporting Services for Campus Identity Providers | | | | |
1.3.1 | Design Phase | | M1-M6 | | Marco |
| D9.1 Market Analysis for Supporting Services for Campus Identity Providers | EC Del | M8 | | Marco |
| Include info on TIER | | | | |
| Create CBA or update FaaS CBA | | M6 | | |
| CBA Approval | | M8 | | |
| Technical Design | | M6-M12 | | marco & Janusz |
| Prototype | | M18-M20 | | Marco Janusz |
1.3.2 | Pilot | | M20-M28 | | Marco |
1.3.3 | Transition to Production | | M30 | | Marco |
1.4 | eduGAIN Incident Management platform integration | | | | |
1.4.1 | Design Phase | | | | |
| Identify impact on eduGAIN central infrastructure e.g. EC monitoring reqs, audit reqs. | | M1 | T0 Brook | |
| Prepare BCP for adoption of Sirtfi by Good eduGAIN Citizens | | M12 | | Provide provisional suggestions first then use surfnet & switch pilots to provide final |
| Update eduGAIN CBA | | | T0 Brook | |
| Design Tooling | | M18 | | Check federation experience first |
1.4.2 | Pilot | | M1-M18 | | We may want to split piloting central support and NREN takeup |
| Support takeup by NRENs | | Ongoing | | |
| M9.4 SIRTFI Pilot Report | EC Milestone | M20 | | |
1.4.3 | Transition to production | | M18-M20 | | Need to define what production means for this since implementation is not our scope |
TBC | eduSAFE | | | | |