...
| Number | Name | Description | Status | Tools |
|---|---|---|---|---|
| 1 | policy | NRO has signed the appropriate version of the policy | MUST | OT checks in official archive |
| policy | NROs should appoint at least one representative to the eduroam SG | SHOULD | OT checks meeting participation | |
| policy | Scheduled maintenance work performed by the NRO within the respective federation should be announced two (2) days in advance through the SG mailing list. For unscheduled maintenance the announcement should preferably be made 24 hours in advance. A ticket on TTS should be opened by the respective NRO representative, and closed with a short comment on the performed action. | SHOULD | OT checks SG mailing list archive and TTS as well as outages in the FTLR connections from the monitoring systems | |
| policy | NROs should regularly report to the OT about the number and type of security incidents | SHOULD | OT cross-checks its archives with other security incident archives | |
| policy | Malfunction in a member federation should be announced through the SG mailing list. A ticket on the TTS should be opened by the respective NRO representative and closed with a short comment on the performed action | SHOULD | OT checks mailing list archives and possible other sources (including social media) regarding malfunction reports. | |
| policy | Participating federations are encouraged to check send VLAN attributes (Tunnel-Type, Tunnel-Medium-Type, Tunnel-Private-Group-ID) , and to investigate whether the sender is sending these attributes inadvertently or not, and then take appropriate action. | SHOULD (encouraged) | OT checks sent VLAN attributes and contact institutions directy to check if the NRO has been in contact regarding this. |
3b. Secondary Requirements and recommendations (MOL)
...