...
Table of Contents maxLevel 1 style none
eduroam
...
eduroam core service (to-do)
logs of ETLR servers (contain IPaddress, MAC address, outer-identity, CUI, ON, ...)
eduroam F-ticks
| GEANT central ops | NROs | |
| Dataset description: | Data needed for eduroam authentication for end usersUsage log messages for each international and national roaming authentication request. | Usage log messages for each international and national roaming authentication request coming from IdPs belonging to that NRO. |
| Purpose of processing: |
Log data provides basic statistical information about service usage. It provides statistics about the number of logins for national and international roaming. The data is used for generation of usage statistics that are publicly available at https://monitor.eduroam.org and for reporting to EC and other stakeholders. | Log data provides basic statistical information about the service usage. It provides statistics about the number of logins for national and international roaming. The data is sent to the GEANT central operations as requested by the eduroam service definition. Depending on the NRO practices, the data can processed by the NRO for creating usage statistics. |
| Data source: | NROs Federation top level Radius servers.IdPs and SPs can optionally send | F-ticks data as wellare generated by the data from RADIUS authentication requests or responses sent by the IdP, and that transverses the NROs Federation top level Radius servers. This happens in the event when a user access eduroam at a visited SP location and authenticates. |
| Data storage and access: | F-ticks data are stored in the SQL database that is operated in the infrastructure provided by CARNet. The raw data is accessible only by the personnel of eduroam operations team. | Depending on the NRO practices, data can be kept and stored by NRO as well. |
| Data transfer: |
F-ticks data are not transferred to any other party or system. | F-ticks data are sent to the eduroam core operations. |
| Data retention: | F-ticks data are kept permanently.  | Depends on the NRO practices if they keep a copy and for how long. |
| Personal data processed: | Yes | Yes |
Dataset content
| Data item | Is personal data (DPO fills in) | |
|---|---|---|
| 1 | REALM - As in users EPPN used for the authentication (for example “@education.lu”) - contains the user’s country of origin and the institution of origin | No ? |
| 2 | Calling-Station-Id - User’s device MAC address | No ? |
| 3 | Viscountry - ISO country code of the NRO that generated the log message | No ? |
| 4 | Visinst - Identifier of visited institution i.e. operator-name RADIUS attribute | No ? |
| 5 | Result - Authentication outcome: OK / FAIL | No ? |
...
| Data item | Is personal data (DPO fills in) | Comment | |
|---|---|---|---|
| 1 | instid - provided by the NRO | No | |
| 2 | ROid - Unique identifier provided by the database operator during the RO | No | |
| 3 | locationid - provided by the NRO | No | |
| 4 | coordinates - longitude, latitude, altitude | No | |
| 5 | stage - 0=preproduction/test, 1=active | No | |
| 6 | type - 0=single spot; 1=area; 2=mobile | No | |
| 7 | loc_name - location’s name | No | |
| 8 | address_street - location’s address | No | |
| 9 | address_city - location’s address: city | No | |
| 10 | location_type - IEEE 802.11-2012, clause 8.4.1.34 Venue Info | No | |
| 11 | contact_name - on site contact: name | Yes | If contact is person |
| 12 | contact_email - on site contact: e-mail | Yes | If contact is person |
| 13 | contact_phone - on site contact: phone no. | Yes | If contact is person |
| 14 | contact_type - 0=person, 1=service/department | No | |
| 15 | contact_privacy - 0=private, 1=public | No | |
| 16 | SSID - SSID used | No | |
| 17 | enc_level - supported encryption levels | No | |
| 18 | AP_no - number of APs | No | |
| 19 | wired_no - number of enabled sockets for wired access | No | |
| 20 | tag - specific characteristic(s): port_restrict, transp_proxy, IPv6, NAT, HS2.0 | No | |
| 21 | availability - 0=default, 1=physical access restrictions | No | |
| 22 | operation_hours - If service is not available 24 hours per day | No | |
| 23 | info_URL - info page with additional info in case of any restrictions | No | |
| 24 | ts - date: last changed | No |
eduroam CAT (todo)
| Dataset description: | |||
| Purpose of processing: | |||
| Data source: | |||
| Data storage and access: | Data transfer: | Data retention: | Personal data processed: |
eduroam NRO
eduroam F-ticks
| : |
Usage log messages for each international and national roaming authentication request.
Log data provides basic statistical information about the service usage. It provides statistics about the number of logins for national and international roaming. The data is sent to the GEANT central operations as requested by the eduroam service definition. Depending on the NRO practices, the data can processed by the NRO for creating usage statistics.
| Data |
Depending on the NRO practices, data can be kept and stored by NRO as well.
| transfer: |
| Data retention: |
| Personal data processed: |
Dataset content
Provided in the eduroam core operations section.
...
Dataset content
| Data item | Is personal data (DPO fills in) | |
|---|---|---|
| 1 | ||
| 2 | ||
| 3 |
...