ANNEX ISupplementary provisions
ANNEX I General requirements for driving licences which include a microchip The general requirements for driving licences including a microchip described in this Annex are based on international standards, in particular the ISO/IEC 18013-series standards. They cover: — the specifications for the microchip and the logical data structure on the microchip, — the specifications for harmonised and additional data to be stored, and — the specifications relating to data protection mechanisms for the digitally stored data on the microchip. I.1 ABBREVIATIONS Abbreviation Meaning AID Application Identifier BAP Basic Access Protection DG Data Group EAL 4+ Evaluation Assurance Level 4 Augmented EF Elementary File EFID Elementary File Identifier eMRTD Machine Readable Travel Documents ICC Integrated Circuit Card ISO International Standard Organisation LDS Logical Data Structure PICC Proximity Integrated Circuit Card PIX Proprietary Application Identifier Extension RID Registered Application Identifier SOd Document Security Object I.2 DATA STORED ON THE MICROCHIP I.2.1 Harmonised mandatory and optional driving licence data The microchip shall store the harmonised driving licence data specified in Annex I, Paragraph 3, to Directive 2006/126/EC. If a Member State decides to include in the driving licence data items marked as optional in Annex I, Paragraph 3, of Directive 2006/126/EC, these items shall be stored in the microchip. I.2.2 Additional data After consulting the Commission, Member States may store additional data, provided that it does not interfere in anyway with the implementation of Directive 2006/126/EC. Member States intending to introduce additional data shall provide the Commission with detailed information on the type of additional data and the reasons for storing such data on the microchip. The Commission shall examine this information and, where appropriate, deliver an opinion in the light of the requirements laid down in this Annex and after consultation of the Working Party established under Article 29 of Directive 95/46/EC. The Commission shall also indicate in its opinion, where appropriate, whether the additional data is to be stored in the EU driving licence application or in another application. I.3 MICROCHIP I.3.1 Storage medium type The storage medium for driving licence data shall be a microchip with a contact, contactless, or combined contact and contactless (dual) interface, as specified in Annex II, item 1 of this Regulation. I.3.2 Applications All data on a microchip shall be stored in applications. All applications on the microchip shall be identified by a unique code called Application Identifier (AID) as specified in Annex II, item 2. I.3.2.1 EU Driving Licence Application Mandatory and optional driving licence data shall be stored in the dedicated EU Driving Licence application. The AID for the EU Driving Licence application shall be: ‘ A0 00 00 04 56 45 44 4C 2D 30 31 ’, consisting of: — the Registered Application Identifier (RID) for the European Commission: ‘ A0 00 00 04 56 ’, — the Proprietary Application Identifier Extension (PIX) for the EU Driving Licence application: ‘ 45 44 4C 2D 30 31 ’ (EDL-01). Data shall be grouped in Data Groups (DGs) as part of a Logical Data Structure (LDS). DGs shall be stored as Elementary Files (EFs) in the EU Driving Licence application, and shall be protected in accordance with Annex II, item 3. I.3.2.2 Other Applications Other additional data shall be stored in one or more dedicated applications apart from the EU Driving Licence Application. Each such application shall be identified by a unique AID. I.4 LOGICAL DATA STRUCTURE OF THE EU DRIVING LICENCE APPLICATION I.4.1 Logical Data Structure Driving Licence Data shall be stored on the microchip in a Logical Data Structure (LDS) specified in Annex II, item 4. This paragraph specifies additional requirements for the mandatory, optional and additional DGs. Each DG shall be stored in one EF. The EFs to be used for the EU Driving Licence Application shall be identified with the Elementary File Identifiers (EFIDs) and Short EF identifiers as specified in Annex II, item 5. I.4.2 Mandatory Data Groups The mandatory and optional data elements shall be stored in the following DGs: — DG 1: all mandatory and optional data elements as printed on the document, except face image and signature image, — DG 5: image of the licence holder’s signature, — DG 6: image of the licence holder’s face. DG 1 data shall be structured as specified in paragraph I.6 of this Annex and as specified in Annex II, item 6. Data contained in other DGs shall be stored according to the specifications of Annex II as specified in Annex II, item 7. I.4.3 Additional Data Groups The additional data elements shall be stored in the following DGs: — DG 2: details on the licence holder, except for biometric data, — DG 3: details on issuing authority, — DG 4: portrait image, — DG 7: biometric data regarding fingerprint of the licence holder, — DG 8: biometric data regarding iris of the licence holder, — DG 11: other details, such as the full name of the holder in national characters. Data contained in these DGs shall be stored according to the specifications of Annex II, item 8. I.5 DATA PROTECTION MECHANISMS Appropriate mechanisms shall be used for the validation of authenticity and integrity of the microchip and data contained in it and for restricting access to driving licence data. Data on the microchip shall be protected according the specifications laid down in Annex II, item 3. This paragraph specifies additional requirements to be complied with. I.5.1 Authenticity Verification I.5.1.1 Mandatory Passive Authentication All DGs stored in the EU Driving Licence application shall be protected with passive authentication. Data related to passive authentication shall conform to the requirements specified in Annex II, item 9. I.5.1.2 Optional Active Authentication Optional Active Authentication mechanisms shall be applied to ensure that the original microchip has not been replaced. I.5.2 Access Restriction I.5.2.1 Mandatory Basic Access Protection The Basic Access Protection mechanism (BAP) shall be applied for all data in the EU Driving Licence application. In the interest of interoperability with existing systems such as that using Machine Readable Travel Documents (eMRTD) it is mandatory to use the one-line Machine Readable Zone (MRZ), as specified in Annex II, item 10. The K doc document key used to access the chip is generated from the one-line MRZ, which can be entered either manually or using an Optical Character Recognition (OCR) reader. The BAP 1 configuration defined for a one-line MRZ as specified in Annex II, item 10 shall be applied. I.5.2.2 Conditional Extended Access Control When more sensitive data are stored on the microchip, access to such data shall be restricted with additional measures. The Extended Access Control mechanisms shall comply with the specifications of Annex II, item 11. I.5.3 Public Key Infrastructure (PKI) for driving licences including a microchip The single contact point defined in Article 6 shall establish the necessary national arrangements for Public Key management, in accordance with Annex A of ISO standard 18013_3. I.6 DATA PRESENTATION I.6.1 Formatting of data in DG 1 Tag L Value Encoding M/O 61 V DG1 Data elements (nested) Tag L Value 5F 01 V Type approval number ans M 5F 02 V Constructed data object of demographic data elements M Tag L Value 5F 03 3 Issuing Member State a3 M 5F 04 V Surname(s) of the holder as M 5F 05 V Other name(s) of the holder as M 5F 06 4 Date of birth (ddmmyyyy) n8 M 5F 07 V Place of birth ans M 5F 08 3 Nationality a3 O 5F 09 1 Gender M/F/U O 5F 0A 4 Date of issue of the licence (ddmmyyyy) n8 M 5F 0B 4 Date of expiry of the licence (ddmmyyyy) n8 M 5F 0C V Issuing authority ans M 5F 0D V Administrative number (other than document number) ans O 5F 0E V Document number an M 5F 0F V Permanent place of residence, or postal address ans O 7F 63 V Constructed data object of categories of vehicles/restrictions/conditions M Tag L Value (coded as defined below) 02 1 Number of categories/restrictions/conditions N M 87 V Category/restriction/condition ans M 87 V Category/restriction/condition ans O … … … … … 87 V Category/restriction/condition ans O I.6.2 Logical record format The categories regarding vehicles, restrictions or conditions shall be compiled in a data object following the structure specified in the following table: Vehicle category code Date of issue Date of expiry Code Sign Value where: — vehicle category codes shall be presented as defined in Article 4 of Directive 2006/126/EC (such as AM, A1, A2, A, B1, B, etc.), — date of issue shall be presented in the format DDMMYYYY (day in two digits followed by month in two digits followed by year in four digits) for the vehicle category, — date of expiry shall be presented in the format DDMMYYYY (day in two digits followed by month in two digits followed by year in four digits) for the vehicle category, — code, sign and value refer to additional information or restrictions relating to the vehicle category or the driver.