ABCDEFGHIJKLMNOPQRSTUVWXYZ
1
IDTaskPriorityEstimated time requiredTarget StartTarget FinishStatusPersonnelDependenciesNotes
2
1Survey
3
1.1Survey results in and survey closedMarchend MarchDONEKarl Meyer, DavideKarl has the results in raw format, will tidy up and send
4
1.2Analysis of resultsend MarchMid AprilLATEDavide, Maarten, Karl
5
1.3Write summary report of results and key findingsMid AprilEnd AprilSPEED UP!Davide
6
1.4Send summary report to REFEDSEnd AprilEnd AprilSPEED UP!MaartenWith a "thank you to everyone who responded to the survey" + thanks on the feedback on the questions
7
8
2EC Deliverable for BCPTo be a single document, pulling together work already done
9
2.1 Create overview and use cases1.2https://docs.google.com/document/d/1_wfL3EmcSxQZzGutv2n3W_Kzxv1Xidu5gO_Jld0ypXY/edit#heading=h.2xalqapb1gls (needs to be updated so not specific to SWITCH).

Chapter on information from survey results.

Chapter on potential solutions.
10
2.1.1Overview of current eduKEEP architecturesMid MarchEnd AprilSPEED UP!Davide, Maarten, Rolf
11
2.1.2Use cases - or why eduKEEP concepts are actually useful in use case A, B, and C. Specifically note the SWITCH case as this will be the one pilotedEnd MarchEnd MayWORK IN PROGRESSHerve', Constantin, RolfRolf will be away for 2 weeks in April but will give it his best effort.
Add use cases to this document (in a new section):
https://docs.google.com/document/d/1_wfL3EmcSxQZzGutv2n3W_Kzxv1Xidu5gO_Jld0ypXY/edit#heading=h.phby8irkvdny
12
2.2 Develop reference technical architecture2.1https://docs.google.com/presentation/d/1DaJ6LQs3Pk49QGIY60cKWLhprN4_opKBCY24hQY3z3k/edit#slide=id.p
13
2.2.1 Finalize the draft technical architecturesStart MayMid JuneTO BE STARTEDAt least 2
14
2.2.2 Central IdP technical architectureMid JuneMid JulyTO BE STARTEDRolf2.2.1Get in contact with Rolf if someone wants to help
15
2.2.3 Account Linking/Proxy technical architectureMid JuneMid JulyTO BE STARTEDDavide2.2.1Is this one still really needed? I'd say yes (Rolf). To my understanding, we don't develop one single reference architecture, but rather 4 possible approaches (eduPASS, eduTEAMS, Swiss edu-ID, Swedish edu-ID), which we will compare.
16
2.3 Develop policy/legal framework2.2.1
17
2.3.1Review SWITCH user-driven federated identity policyMid JuneEnd JuneWORK IN PROGRESSRolf, Constantin, MihályWhat topics does a "federated identity policy" cover exactly?
18
2.3.2Draft generic policy based on SWITCH policyStart JulyEnd AugustTO BE STARTEDRolf, Constantin, Mihály
19
2.3.3Ask for policy reviewing by "Experts" in the community and/or legal counselling service in GEANTStart SeptemberMid SeptemberTO BE STARTEDMaarten
20
2.4 Recommendations for interfederation2.2.1, 2.3To be drafted
21
2.4.1Review eduGAIN policyMid JulyEnd AugustTO BE STARTEDPLAN A: Maarten ask Peter Schober if he's interestedWith help from Brook/Ioannis/Lukas?
22
2.4.2Summarise policy changes required of eduGAIN and any other changes to eduGAIN (e.g. constitution and other docs?). Write into Deliverable document the collation of all potential changes a federation or eduGAIN should consider, some of which will not apply to individual federations and/or eduGAINStart SeptemberMid SeptemberTO BE STARTEDPLAN A: Maarten ask Peter Schober if he's interested
23
2.5
Glossary ("user-centric"; "user-driven"; "org-centric" etc)
Start AprilEnd AprilTO BE STARTEDRolfTo be updated throughout deliverable writing
24
2.6Best Practice for User Centric Federated IdentityEnd October 2017EC Deliverable
To be written as a concluding chapter to the above, and the whole lot to be presented as the milestone doc to the EC (first iteration of the Best Practices)
25
2.6.1Write concluding chapter summarising work done and what the recommended best currrent practices areMid AugustMid SeptemberTO BE STARTEDDavide, HerveAll participants to help review and make suggestions
26
2.6.2Send to Tech Authors for editorial checkMid SeptemberEnd SeptemberTO BE STARTEDMaartenLet them know it's coming in August
27
2.6.3Send to QASPAR reviewersStart OcotberMid OctoberTO BE STARTEDMaartenLet them know it's coming in August
28
2.6.4Address any comments3rd week October4th week OctoberTO BE STARTEDDavide, Maarten
29
2.6.5Deliverable submitted to ECEnd October TO BE STARTEDMaarten
30
31
3PilotingStart June 2017End August 20182.2, 2.1.22-3 federations, 1-2 services. Find participants before summer 2017. BCP is what is being piloted, not a central service
32
3.1Use output of 2.2 combined with 2.1.2 (SWITCH use case) to produce an overview of what the pilot will do, and specify KPIsMid JuneEnd JuneTO BE STARTEDa KPI can be two or three iterations of the BCP, another one can be pilot at least three use cases from 2.1.2,
33
3.2Call for expressions of interest with service providers for SWITCH use case pilotStart JulyStart SeptemberTO BE STARTED
34
3.3Formal start date of pilot (make sure SPs know)Start October 2017TO BE STARTEDWe could have a F2F kickoff meeting attached to GÉANT Project Symposium 2017 (https://eventr.geant.org/events/2564)
35
3.4Monthly catch up meetings for feedback and progressTO BE STARTED
36
3.5Formally close the pilot with a debrief/wash up VCTO BE STARTED
37
3.6Produce a review of outcomesTO BE STARTED
38
39
40
M9.8 User Centric Federated Identity Business Case3.7EC Milestone. TBD - is this a GEANT PLM deliverable or a "marketing' generic business case for why feds should adopt user-driven? Recommend the latter and based on pilot experience
41
Lightweight CBA on why the BCP should be followed, using outcome of PilotTO BE STARTED
42
Adapt exisitng template to use relevant sectionsTO BE STARTED
43
Draft text TO BE STARTED
44
Send to Tech Authors to reviewTO BE STARTED
45
Send to QASPAR(?)TO BE STARTED
46
Published TO BE STARTED
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100