...
| Comment # | Document (Policy / MRPS) | Document line / reference | Proposed Change or Query | Proposer / Affiliation | Action / decision (to be filled in by candidate) |
|---|---|---|---|---|---|
| 1 | Policy | 46-49 | "Exceptionally, end users are also deemed to be end users of other federations with whom AMRES makes interfederation". Is "exceptional" to signify the expectation that there will be fewer end users through interfederation than AMRES end users, or do you have a process for granting an exception? | Alex Stuart (UK federation) | |
| 2 | MRPS | 30 and 39 | Line 30 defines an entity without reference to any protocol. The restriction in line 39 to a policy of registering only SAML entities will reduce the agility of the federation if iAMRES wishes to use other protocols. I suggest that the word "SAML" is removed from line 39. | Alex Stuart (UK federation) | |
| 3 | MRPS | 49-43 | It is good that iAMRES explicitly includes the publishing policy regards eduGAIN. It would be better if the policy for importing entities from eduGAIN were also listed. This would provide guidance for AMRES Users, and would inform interfederation partners wishing to use services from AMRES Identity Federation Users or AMRES Identity Federation Partners. | Alex Stuart (UK federation) | |
| 4 | MRPS | 57-62 | This is only a subset of the namespaces that are used in eduGAIN today. I suggest that this list is removed from the MRPS and maintained on the AMRES technical website. | Alex Stuart (UK federation) | |
| 5 | MRPS | 77-78 | This item refers to domains in entityIDs. There is no corresponding item about AMRES verifying the scopes in metadata of Identity Providers (although this is explicitly in the eduGAIN SAML profile, which would apply to entities exported to eduGAIN). | Alex Stuart (UK federation) | |
| 6 | MRPS | 82 | I understand the general intention of this item, but AMRES verifying endpoint reachability isn't technically equivalent to the reachability for End Users. | Alex Stuart (UK federation) |
...