List of datasets
eduroam core service (to-do)
logs of ETLR servers
eduroam F-ticks
| Dataset description: |
Usage log messages for each international and national roaming authentication request. |
| 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. |
| Data source: | NROs Federation top level Radius servers. |
| 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. |
| Data transfer: |
F-ticks data are not transferred to any other party or system. |
| Data retention: | F-ticks data are kept permanently.  |
| Personal data processed: | 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 |
eduroam Database - NRO information
| Dataset description: | National Roaming Operator information. |
| Purpose of processing: | Data is used to feed the central data repository for eduroam service. It provides information about National Roaming Operators that participate in the eduroam service. The data is used for providing public available information about eduroam service, available at https://monitor.eduroam.org/. |
| Data source: | The eduroam database has been build as a central database with the mechanism that enables automatic data collection from (National) Roaming Operators - (N)ROs. (N)ROs should provide general data in the defined XML or JSON format. The data should be available at the specific, predefined URLs: http://www.eduroam.<tld>/general/<dataset-name>. |
| Data storage and access: | Data is 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. |
| Data transfer: | Data is not transferred to any other party or system. |
| Data retention: | Data is kept permanently. |
| Personal data processed: | Yes |
Dataset content
| Data item | Is personal data (DPO fills in) | Comment | |
|---|---|---|---|
| 1 | ROid - Unique identifier provided by the database operator during the RO registration | No | |
| 2 | country - two letter country code | No | |
| 3 | stage - 0=preproduction/test, 1=active | No | |
| 4 | org_name - (N)RO corporate name | No | |
| 5 | address_street - (N)RO address | No | |
| 6 | address_city - (N)RO address | No | |
| 7 | coordinates - longitude, latitude, altitude | No | |
| 8 | contact_name - (N)RO contact: name | Yes | If contact is person |
| 9 | contact_email - (N)RO contact: e-mail | Yes | If contact is person |
| 10 | contact_phone - (N)RO contact: phone no. | Yes | If contact is person |
| 11 | contact_type - 0=person, 1=service/department | No | |
| 12 | contact_privacy - 0=private, 1=public | No | |
| 13 | info_URL - (N)RO web page URL | No | |
| 14 | policy_URL - (N)RO Policy URL | No | |
| 15 | ts - date: last changed | No |
eduroam Database - Institution information
| Dataset description: | Institution information (IdP or SP) |
| Purpose of processing: | Data is used to feed the central data repository for eduroam service. It provides information about Institutions that participate in the eduroam service as IdPs and SPs. The data is used for providing public available information about eduroam service, available at https://monitor.eduroam.org/. |
| Data source: | The eduroam database has been build as a central database with the mechanism that enables automatic data collection from (National) Roaming Operators - (N)ROs. (N)ROs should provide general data in the defined XML or JSON format. The data should be available at the specific, predefined URLs: http://www.eduroam.<tld>/general/<dataset-name> |
| Data storage and access: | Data is 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. |
| Data transfer: | Data is not transferred to any other party or system. |
| Data retention: | Data is kept permanently. |
| Personal data processed: | Yes |
Dataset content
| 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 registration | No | |
| 3 | type - IdP, SP, IdP+SP | No | |
| 4 | stage - 0=preproduction/test, 1=active | No | |
| 5 | inst_realm - (only for IdP or IdP+SP) | No | |
| 6 | inst_name - institution’s corporate name | No | |
| 7 | address_street - institution’s address | No | |
| 8 | address_city - institution’s address: city | No | |
| 9 | coordinates - longitude, latitude, altitude of institution’s location | No | |
| 10 | inst_type - IEEE 802.11-2012, clause 8.4.1.34 Venue Info | No | |
| 11 | contact_name - institution’s contact: name | Yes | If contact is person |
| 12 | contact_email - institution’s contact: e-mail | Yes | If contact is person |
| 13 | contact_phone - institution’s 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 | info_URL - institution’s web page with the information related to the service | No | |
| 17 | policy_URL - institution’s Policy | No | |
| 18 | ts - date: last changed | No |
eduroam Database - Service Location information
| Dataset description: | Service Location information |
| Purpose of processing: | Data is used to feed the central data repository for eduroam service. It provides information about Service Locations that are provided in eduroam by participating SPs. The data is used for providing public available information about eduroam service, available at https://monitor.eduroam.org/. |
| Data source: | The eduroam database has been build as a central database with the mechanism that enables automatic data collection from (National) Roaming Operators - (N)ROs.(N)ROs should provide general data in the defined XML or JSON format. The data should be available at the specific, predefined URLs: http://www.eduroam.<tld>/general/<dataset-name>. |
| Data storage and access: | Data is 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. |
| Data transfer: | Data is not transferred to any other party or system. |
| Data retention: | Data is kept permanently. |
| Personal data processed: | Yes |
Dataset content
| 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: |
Dataset content
| Data item | Is personal data (DPO fills in) | |
|---|---|---|
| 1 | ||
| 2 | ||
| 3 |
Description of fields
The details of service related datasets (data collections) should be filled with a list of all kinds of data which is collected or processed by this service. The table should be filled by the Service Manager and afterwards reconciled with the GEANT Data Protection Officer in order to address GDPR requirements. One service often incorporates several datasets. <dataset_name> - name of dataset (collection of data processed in similar way). Dataset description: brief explanation of the kind of information or entities the dataset contains. Purpose of processing: what is purpose of data collecting and processing. Data source: what are source(s) of data - list of services, systems, applications, databases or similar source components, including user's input, from which data are being received. E.g. RIPE database, service ABC, organisation LDAP directory... Data storage and access: describe where the data are stored, backup-ed etc. and who has access to the data. Data transfer: list of other services, systems, applications, databases or similar destinations to which data are being sent. E.g. RIPE database, service ABC, GÉANT's database XYZ... Data retention: describe data retention policy ie. for how long data are stored before being deleted. E.g. 1 year, 2 years after contract ending, forever... Dataset content
|
| Document ID | |
|---|---|
| Version of document | |
| Date of approval | |
| Approved by | |
| Status (draft, approved, obsolete) | draft |
| Document owner (Service Manager?) | |
| Contact person | |
| Date of resubmission | |
| Intervall of resubmission | |
| Type of document (policy, procedure, Information) |