...
| Title | Attribute Authority Metadata policy development for eduGAIN |
|---|---|
| Description | While for IdPs and SPs eduGAIN metadata requirements are well described, no such requirements exist for AAs. We have however already 5 of these entities in eduGAIN. It would also be a good idea to consider/define what it would mean for an AA to claim CoCo, R&S and Sirtifi support |
| Proposer | Niels van Dijk |
| Resource requirements |
|
| +1's | Constantin Sclifos, RENAM Nick Roy, InCommon SURFnet Rhys Smith, UKf: I think AAs will become more important as we move forward, and there is a gap here in policy that needs thinking about. Wolfgang Pempe, DFN |
eScience
...
requirements driven activities
| TitleNon fed ops/eduroam driven activities | Placehoder to include (and potentially continue) some of AARC work |
|---|---|
| Description | I would like to have a placeholder to include work that my be triggered by the revisited list of FIM4R requirements, as well as by AARC. Furthermore, I'd also like to include in this box liaisons with EOSC hub concerning their T&I architecture developments and adoption/support of FIM technologies. This item cannot and should not be more specific than this at this point in time. |
| Proposer | Licia Florio |
| Resource requirements | Coordination work, resources |
| +1's | <for others to voice their support - add your name here> |
...
| Title | eduTEAMS enhancements |
|---|---|
| Description | eduTEAMS work is progressing; there are different options for deploying eduTEAMS. This work item looks at the requirements for eduTEAMS . And there when used by eScience collaborations. There will be lessons learned after the pilot with the life science community. I propose we have a placeholder so work on this does not go off radar during the planning. |
| Proposer | Licia Florio |
| Resource requirements | Effort mostly |
| +1's | <for others to voice their support - add your name here> |
...