...
| Title | Focus on VOs |
|---|---|
| Description | VOs straddle national Feds and we handle them in an ad hoc (at best!) fashion. What practices should the interfed community adopt to support their Fed/Interfed needs? Deliverables might include strawman recommended practices to national Feds and roles & responsibilities that together would define a consistent service presented to VOs. The purpose would be to inform ourselves of what it might actually take to operationalize such a service. Could build on the VO Assessment activity proposed by Heather above. |
| Proposer | Tom Barton |
| Resource requirements | A few working group members to interview principals from several VOs or other organizations that support them or otherwise are knowledgeable about needs from a VO perspective (eg, Center for Trustworthy Scientific Cyberinfrastructure). A few Fed Ops to mull this over from an operational perspective. Someone to edit a resulting doc. |
| +1's | Romain Wartel, Michal Prochazka, Scott Koranda |
| Title | Privacy and interfed |
|---|---|
| Description | Is the CoCo on track? What barriers are there to its adoption? Purpose is to determine what issues a communications campaign should address to improve uptake. |
| Proposer | Tom Barton |
| Resource requirements | Working Group would conduct interviews with a selection of prospective CoCo adopting sites, blend with CoCo knowledgeable expert and a communications person to arrive at an enumeration of concerns to be addressed. Perhaps a dozen Working Group conference calls and list support. Support for a small number of group interviews. |
| +1's | Mikael Linden (the GEANT CoCo flywheel) |
| Title | Focus on R&S adoption |
|---|---|
| Description | What is needed to jump start R&S programs in more national Feds? Produce recommendations, possibly including training, template processes and communication materials, live exchanges between Feds with established practices and others getting ready to dig into it. |
| Proposer | Ann West (communicated by Tom Barton, as version history will attest) |
| Resource requirements | Working Group with representation from a couple of national Feds already doing R&S with a couple not quite there yet. Maybe 6 conference calls and list support. Could lead to a further event programming activity. |
| +1's | Scott Koranda |
| Title | EduGAIN Global incident handling/support framework |
|---|---|
| Description | 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;
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. |
| Proposer | Terry 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's | Heath Marks (AAF) |
...
| Title | Attribute authorities and group membership/role information |
|---|---|
| Description | Attribute authorities become interesting in VO world, where IdPs are not able to satisfy SP needs on additional attributes about the users especially group membership/roles. The main problem is when one SP wants to accept users from different VOs which use different attribute authorities. There is no common standard for representing group name/role in the attribute having VOs identification into account (just group name can lead to collision among different VOs). Some examples how group names are used by current group mgmt systems:
Protocols which work with groups and theirs requirements on the group name:
|
| Proposer | Michal Prochazka |
| Resource requirements | Several conference calls should be enough for setting up the working group and produce recommendation on nameing schema for groups including VO identification. |
| +1's | Scott Koranda |