...
| Comment # | Document (Policy / MRPS) | Document line / reference | Proposed Change or Query | Proposer / Affiliation | Action / decision (to be filled in by candidate) |
|---|---|---|---|---|---|
| 1 | MRPS | section 4 | technical.edugain.org lists their Registration Authority as "urn:mace:rafiki.ke", but in the MRPS, they instead use the "http://Federation.org" example from the template which makes their intent unclear. If they intend to use MACE space, they should register it before going into production ;-). Or they should use https://rafiki.ke as a registrationAuthority. Either way, they should update the example in the MRPS. | Guy / SAFIRE | We have update updated the registrationAuthority to https://rafiki.ke and updated the MRPS example as well |
| 2 | MRPS | line 74 | Presumably RAFIKI checks a member'scanonical name matches registrant information shown in WHOIS, not DNS. | Alex Stuart / UK federation | We have amended the section to read " A member’s canonical name matches registrant information shown in public WHOIS records held by the DNS domain registrar." |
| 3 | MRPS | whole document | There is no mention of RAFIKI verifying the use of domain names in scopes. The eduGAIN profile requires this for entities exported to eduGAIN, so it might be useful to include reference to scopes in the MRPS. I note that one of the IdPs in the RAFIKI's metadata feed has no scopes. | Alex Stuart / UK federation | We request for further guidance/clarification on this |
...