Guidelines for
...
expressing affiliation information
...
across infrastructures
Summary
This document describes the semantics associated with the use of the affiliation attributes eduPersonAffiliation and/or eduPersonScopedAffiliation when these are asserted by an Infrastructure Proxy when communiting to connected service providers and other Infrastructure Proxies.
...
Hi Nicolas Liampotis: I think SPs will be doing scope checking anyway (you cannot prevent it, as anywhere else that is considered best if not the only acceptable practice. Since also SPs will likely serve multiple Proxies as well as independent customers, they will get different scoped and can never ultimately trust any of the single proxies. Which implies that, if we write something else here for eP(S)A that being the scope of the Proxy in all cases, things will start breaking in 'interesting' ways. So so keep consistency in the ecosystem, ePSA must be scoped to the proxy, QED 
. Meanwhile, we did define freshness to be scoped to the Infrastructure Proxy (which may use any kind of business logic to derive but, but that's out of scope for both this and the assurance doc, which is why I need this doc at least with rough consensus. Otherwise there will be too many dangling references in AARC-G021 ... Cheers, DavidG.
Links
Working docs
Google doc: https://docs.google.com/document/d/1o6uLlUW59F61mdImPGMCAwBR4KH4lfQIaLMfaqhOW3Q
Final PDF
To be published
Meetings schedule and Minutes
| Date | Location | Agenda | Minutes |
|---|---|---|---|
| YYYY-MM-DD HH-MM TIME-COORDINATES (UTC/CEST/...) | link to webconf platform/room | IMPORTANT insert link to PUBLIC PAGE | IMPORTANT insert link to PUBLIC PAGE |
...