-- draft --
1. Purpose
goal is to evaluate the service level, recognise excellence and identify possible weak spots all in order to maintain and improve the over quality of the service
2. Rules & Process
once a year - initial audit (2 months) + audit for those who failed (1 month)
requirements and recommendations = norms = MUST, SHOULD, MAY
audit marks:
- NRO passes: all MUSTs obeyed
- NRO is good: all MUSTs + all SHOULDs obeyed
- NRO is excellent: all MUSTs + all SHOULDs + all MAYs
audit results:
- rewards and sanctions
audit tools:
- self assesment
- automatic via monitoring tools
- manual assessment by the OT / audit team
audit process:
- initiated by the eduroam OT
- NRO admins fill in the web form (monitor.eduroam.org/audit)
- OT provides data via manual audit or monitoring tools
- OT publishes final results (only final mark per NRO is publicly available
3a. Requirements and recommendations
| Number | Name | Description | Status | Tools |
|---|---|---|---|---|
| 1 | policy (Ch 6) | NRO has signed the appropriate version of the policy | MUST | OT checks in official archive |
| policy (before Ch 6) | NROs should appoint at least one representative to the eduroam SG | SHOULD | OT checks meeting participation | |
| policy (before Ch 6) | 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 (before Ch 6) | 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 (before Ch 6) | 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 (before Ch 6) | 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. | |
| policy (Ch 6) | Violation of the Policy declaration MUST be reported to the OT, and MUST be presented to the SG and escalated to the NRENPC in serious cases. | MUST | Check forums and social media etc and cross-check with OT and SG mailing list archives & meeting minutes. |
3b. Secondary Requirements and recommendations (MOL)
| Number | Name | Description | Status | Tools |
|---|---|---|---|---|
| 1. | Physical signage | NRO advises member organisations to deploy physical signage in areas where eduroam is available (e.g. to assist visitors with medical prosthetics) | Should | Evidence: copy of documentation/web page |
4. References
eduroam Compliance Statement https://www.eduroam.org/support/eduroam_Compliance_Statement.pdf
European Confederation eduroam policy https://www.eduroam.org/wp-content/uploads/2016/05/GN3-12-194_eduroam-policy-for-signing_ver2-4_1_18052012.pdf
eduroam Service Definition https://www.eduroam.org/wp-content/uploads/2016/05/GN3-12-192_eduroam-policy-service-definition_ver28_26072012.pdf