[F1ANNEX II U.K. PART II OF THE REGISTRATION CERTIFICATE (1)
Textual Amendments
I. This part may be implemented in either of two formats: as a paper document or as a smart card. The characteristics of the paper document version are specified in Chapter II and those of the smart card version in Chapter III. U.K.
II. Specifications of Part II of the registration certificate in paper format U.K.
II.1. The overall dimensions of the registration certificate shall not be greater than an A4 format (210 × 297 mm) or a folder of A4 format. U.K.
II.2. The paper used for part II of the registration certificate shall be made secure against forgery by using at least two of the following techniques: U.K.
graphics,
watermark,
fluorescent fibres, or
fluorescent imprints.
Member States are free to introduce additional security features.
II.3. Part II of the registration certificate may consist of several pages. Member States shall determine the number of pages in accordance with the information contained in the document and its layout. U.K.
II.4. The first page of Part II of the registration certificate shall contain U.K.
the name of the Member State issuing Part II of the registration certificate,
[F2the distinguishing mark of the Member State issuing Part II of the registration certificate, namely:
B:
Belgium
CZ:
Czech Republic
DK:
Denmark
D:
Germany
EST:
Estonia
GR:
Greece
E:
Spain
F:
France
IRL:
Ireland
I:
Italy
CY:
Cyprus
LV:
Latvia
LT:
Lithuania
L:
Luxembourg
H:
Hungary
M:
Malta
NL:
Netherlands
A:
Austria
PL:
Poland
P:
Portugal
SLO:
Slovenia
SK:
Slovakia
FIN:
Finland
S:
Sweden
UK:
United Kingdom,]
the name of the competent authority,
the words ‘ Part II of the Registration Certificate ’ , printed in large type in the language or languages of the Member States issuing the registration certificate; they shall also appear, after a suitable space, in small type, in the other languages of the European Community,
the words ‘ European Community ’ , printed in the language or languages of the Member State issuing Part II of the registration certificate,
the number of the document.
Textual Amendments
F2 Substituted by Treaty between the Kingdom of Belgium, the Kingdom of Denmark, the Federal Republic of Germany, the Hellenic Republic, the Kingdom of Spain, the French Republic, Ireland, the Italian Republic, the Grand Duchy of Luxembourg, the Kingdom of the Netherlands, the Republic of Austria, the Portuguese Republic, the Republic of Finland, the Kingdom of Sweden, the United Kingdom of Great Britain and Northern Ireland (Member States of the European Union) and the Czech Republic, the Republic of Estonia, the Republic of Cyprus, the Republic of Latvia, the Republic of Lithuania, the Republic of Hungary, the Republic of Malta, the Republic of Poland, the Republic of Slovenia, the Slovak Republic, concerning the accession of the Czech Republic, the Republic of Estonia, the Republic of Cyprus, the Republic of Latvia, the Republic of Lithuania, the Republic of Hungary, the Republic of Malta, the Republic of Poland, the Republic of Slovenia and the Slovak Republic to the European Union.
II.5. Part II of the Registration Certificate shall also contain the following data, preceded by the corresponding harmonised Community codes: U.K.
registration number
date of the first registration of the vehicle
vehicle:
make,
type,
variant (if available)
version (if available)
commercial description(s)
vehicle identification number
type-approval number (if available)
II.6. Part II of the registration certificate may, moreover, contain the following data, preceded by the corresponding harmonised Community codes: U.K.
personal data
owner of the vehicle,
surname(s) or business name,
other name(s) or initial(s) (where appropriate),
address in the Member State of registration, on the date of issue of the document,
natural or legal person who may use the vehicle by virtue of a legal right other than that of ownership,
surname(s) or business name,
other name(s) or initial(s) (where appropriate),
address in the Member State of registration, on the date of issue of the document
where a change in the personal data given in point II.6, code C.2 and/or point II.6, code C.3 does not give rise to the issue of a new Part II of the Registration Certificate, the new personal data corresponding to these points may be included under codes (C.5) or (C.6); they are broken down in accordance with point II.6, code C.2 and point II.6, code C.3.
vehicle category.
II.7. Member States may include additional information in Part II of the registration certificate; in particular, they may add between brackets to the identification codes, as laid down under points II.5 and II.6, additional national codes. U.K.
III. Specifications of Part II of the Registration Certificate in smart card format (Alternative to the specimen in paper format described in Chapter II) U.K.
III.1. Card format and data legible with the eye U.K.
Being a microprocessor card, the chip card shall be designed in accordance with the standards mentioned in Chapter III.5.
Printed on the front and back of the card shall be at least the data specified in Chapters II.4 and II.5; these data shall be legible with the eye (minimum character height: 6 points) and printed on as follows. (Examples of possible lay-outs are presented in Figure 2 at the end of this section)
A. Basic imprint U.K.
The basic data shall contain the following:
Front U.K.
To the right of the chip location:
in the language(s) of the Member State issuing the Registration Certificate
the words ‘ European Community ’ ,
the name of the Member State issuing the Registration Certificate,
the words ‘ Part II of the Registration Certificate ’ printed in large type,
another (e.g. previous national) designation of the equivalent document (optional),
the name of the competent authority (alternatively, also in the form of a personalisation imprint as per Letter B),
the unambiguous consecutive number of the document as used within the Member State (alternatively, also in the form of a personalisation imprint as per Letter B).
Above the chip location:
the distinguishing mark of the Member State issuing the Registration Certificate, white in a blue rectangle and surrounded by twelve yellow stars:
BBelgium
[F3BGBulgaria]
DKDenmark
DGermany
GRGreece
ESpain
FFrance
[F4HRCroatia]
IRLIreland
IItaly
LLuxembourg
NLThe Netherlands
AAustria
PPortugal
[F3RORomania]
FINFinland
SSweden
UKUnited Kingdom
Member States might consider adding, at the lower edge in small type and in their national language(s), the note: ‘ This document should be kept in a safe place outside the vehicle. ’
The basic colour of the card is red (Pantone 194); alternatively, a red-to-white transition is possible.
A symbol representing a wheel (see proposed lay-out) shall be printed within the printing area in the bottom left corner of the card front.
In other respects, the provisions of Chapter III.13 shall apply.
B. Personalisation imprint U.K.
The personalisation imprint shall contain the following information:
Front U.K.
the name of the competent authority — see also Letter Aa).
the name of the authority issuing the Registration Certificate (optional).
the unambiguous consecutive number of the document as used within the Member State — see also Letter Aa).
The following data from Chapter II.5; according to Chapter II.7, individual national codes may be added to the preceding harmonised Community codes.
| Code | Reference |
|---|---|
| A | registration number (official licence number) |
| B | date of first registration of the vehicle |
Back U.K.
The back shall bear at least the remaining data specified in Chapter II.5; according to Chapter II.7, individual national codes may be added to the preceding harmonised community codes.
In detail, these data are:
| Code | Reference |
|---|---|
| Vehicle data (in consideration of the notes in Chapter II.5) | |
| D.1 | make |
| D.2 | type (variant/version, where appropriate) |
| D.3 | commercial description(s) |
| E | vehicle identification number |
| K | type-approval number (if available) |
Optionally, additional data from II.6 (with the harmonised codes) and II.7 may be added on the back of the card.
C. Physical security features of the smart card U.K.
The threats to the physical security of documents are:
Production of false cards: creating a new object which bears great resemblance to the document, either by making it from scratch or by copying an original document.
Material alteration: changing a property of an original document, e.g. modifying some of the data printed on the document.
The material used for Part II of the registration certificate shall be made secure against forgery by using at least three of the following techniques:
microprinting,
guilloche printing*,
iridescent printing,
laser engraving,
ultraviolet fluorescent ink,
inks with viewing angle — dependent colour*,
inks with temperature — dependent colour*,
custom holograms*,
variable laser images,
optical variable images.
Member States are free to introduce additional security features.
As a basis, the techniques indicated with an asterisk are to be preferred as they enable the law enforcement officers to check the validity of the card without any special means.
III.2. Data storage and protection U.K.
Preceded by the harmonised common codes (where appropriate, in connection with the individual codes of the Member States according to Chapter II.7), the following data shall or may be additionally stored on the card surface bearing the legible information as per Chapter III.1:
Data as per Chapters II.4 and II.5
All data specified in Chapters II.4 and II.5 shall be mandatorily stored on the card.
Other data as per Chapter II.6
Moreover, the Member States are free to store more data as per Chapter II.6, to the necessary extent.
Other data as per Chapter II.7
Optionally, further vehicle-related data of general interest may be stored on the card.
The data from the Letters A and B is stored in two corresponding files with transparent structure (see ISO/IEC 7816-4). The Member States may specify the storage of data from Letter C according their requirements.
There are no read restrictions on these files.
Write access to these files shall be restricted to the national competent authorities (and their authorised Agencies) in the Member State issuing the smart card.
Write access is permitted only after an asymmetric authentication with session key exchange for protecting the session between the vehicle registration card and a Security Module (e.g. a Security Module Card) of the national competent authorities (or their authorised Agencies). Thereby Card Verifiable certificates according to ISO/IEC 7816-8 are exchanged before the authentication process. The Card Verifiable certificates contain the corresponding public keys to be retrieved and to be used in the following authentication process. These certificates are signed by the national competent authorities and contain an authorisation object (certificate holder authorisation) according to ISO/IEC 7816-9 in order to encode role specific authorisation to the card. This role authorisation is related to the national competent authority (e.g. to update a data field).
The corresponding public keys of the national competent authority are stored as trust anchor (root public key) in the card.
The specification of the files and commands needed for the authentication process and the writing process is under responsibility of the Member States. The security assurance has to be approved by Common Criteria Evaluation according to EAL4+. The augmentations are as follows: 1. AVA_MSU.3 Analysis and testing for insecure states; 2. AVA_VLA.4 Highly resistant.
Verification data for authenticity of registration data
The issuing authority calculates its electronic signature about the complete data of a file containing the data of the Letter A or B and stores it in a related file. These signatures allow the authenticity of the stored data to be verified. The cards shall store the following data:
electronic signature of registration data related to Letter A,
electronic signature of registration data related to Letter B.
For verification of these electronic signatures the card shall store:
certificates of the issuing authority calculating the signatures about the data of Letters A, B.
Electronic signatures and the certificates shall be readable without restriction. Write access to electronic signatures and certificates shall be restricted to the national competent authorities.
III.3. Interface U.K.
External contacts should be used for interfacing. A combination of external contacts with a transponder is optional.
III.4. Storage capacity of the card U.K.
The card shall have sufficient capacity to store the data mentioned in Chapter III.2.
III.5. Standards U.K.
The chip card and reading devices used shall comply with the following standards:
:
Standards for identification cards (plastic cards): Physical characteristics,
:
Physical characteristics of chip cards, dimensions and location of contacts,
:
Electrical characteristics of contacts, transmission protocols,
:
Communication contents, chip card data structure, safety architecture, access mechanisms,
:
Structure of application identifiers, selection and execution of application identifiers, registration procedure for application identifiers (numbering system),
:
Inter-industry data elements for interchange,
:
Integrated circuit(s) cards with contacts — Security related inter-industry commands,
:
Integrated circuit(s) cards with contacts — Enhanced inter-industry commands,
III.6. Technical characteristics and transmission protocols U.K.
The format shall be ID-1 (normal size, see ISO/IEC 7810).
The card shall support transmission protocol T = 1 in compliance with ISO/IEC 7816-3. Additionally other transmission protocols may be supported, e.g. T=0, USB or contactless protocols. For bit transmission the ‘ direct convention ’ shall be applied (see ISO/IEC 7816-3).
A. Supply voltage, programming voltage U.K.
The card shall work with Vcc = 3V (+/0.3V) or with Vcc = 5V (+/0.5V). The card shall not require a programming voltage at pin C6.
B. Answer to reset U.K.
The Information Field Size Card byte shall be presented at the ATR in character TA3. This value shall be at least ‘ 80h ’ (=128 bytes).
C. Protocol parameter selection U.K.
The support of protocol parameter selection (PPS) according to ISO/IEC 7816-3 is mandatory. It is used for selecting T=1, if T=0 is additionally present in the card, and to negotiate the Fi/Di parameters for achieving higher transmission rates.
D. Transmission protocol T = 1 U.K.
The support of chaining is mandatory.
The following simplifications are allowed:
NAD Byte: not used (NAD should be set to ‘ 00 ’ ),
S-Block ABORT: not used,
S-Block VPP state error: not used.
The information field size device (IFSD) shall be indicated from the IFD immediately after ATR, i.e. the IFD shall transmit the S-block IFS request after ATR and the card shall send back S-block IFS. The recommended value for IFSD is 254 bytes.
III.7. Temperature range U.K.
The registration certificate in smart card format shall properly function under all climatic conditions usually prevailing in the territories of the community and at least in the temperature range specified in ISO 7810. The cards shall be capable of operating correctly in the humidity range 10 % to 90 %.
III.8. Physical lifetime U.K.
If used in accordance with the environmental and electricity-related specifications, the card must function properly for a period of ten years. The material of the card must be chosen in such a way that this lifetime is ensured.
III.9. Electrical characteristics U.K.
During operation, the cards shall conform to Directive 95/54/EC, related to electromagnetic compatibility, and shall be protected against electrostatic discharges.
III.10. File structure U.K.
Table 1 lists the mandatory elementary files (EF) of the application DF (see ISO/IEC 7816-4) DF.Registration. All these files have a transparent structure. The access requirements are described in Chapter III.2. The file sizes are specified by the Member States according their requirements.
Table 4
| Filename | File Identifier | Description |
|---|---|---|
| EF.Registration_A | ‘ D001 ’ | Registration data according to the Chapters II.4 and II.5 |
| EF.Signature_A | ‘ E001 ’ | Electronic Signature about complete data content of EF.Registration_A |
| EF.C.IA_A.DS | ‘ C001 ’ | X.509v3 Certificate of the issuing authority calculating the signatures for EF.Signature_A |
| EF.Registration_B | ‘ D011 ’ | Registration data according Chapter II.6 |
| EF.Signature_B | ‘ E011 ’ | Electronic Signature about complete data content of EF.Registration_B |
| EF.C.IA_B.DS | ‘ C011 ’ | X.509v3 Certificate of the issuing authority calculating the signatures for EF.Signature_B |
III.11. Data structure U.K.
The stored certificates are in the X.509v3 format according ISO/IEC 9594-8.
The electronic signatures are stored transparent.
The registration data is stored as BER-TLV data objects (see ISO/IEC 7816-4) in the corresponding elementary files. The value fields are coded as ASCII character as defined by ISO/IEC 8824-1, the values ‘ C0 ’ - ‘ FF ’ are defined by ISO/IEC 8859-1 (Latin1 character set) or ISO/IEC 8859-7 (Greek character set) or ISO/IEC 8859-5 (Cyrillic character set). The format of dates is YYYYMMDD.
Table 2 lists the Tags identifying the data objects corresponding to the registration data of Chapter II.4 and II.5 together with additional data from Chapter III.1. Unless otherwise stated, the data objects listed in Table 2 are mandatory. Optional data objects may be omitted. The column of the Tag indicates the level of nesting.
Table 5
| Tag | Description | |||
|---|---|---|---|---|
| ‘ 78 ’ | Compatible tag allocation authority, nesting object ‘ 4F ’ (see ISO/IEC 7816-4 and ISO/IEC 7816-6) | |||
| ‘ 4F ’ | Application identifier (see ISO/IEC 7816-4) | |||
| ‘ 73 ’ | Inter-industry template (see ISO/IEC 7816-4 and ISO/IEC 7816-6) corresponding to mandatory data of the registration certificate Part 2, nesting all following objects | |||
| ‘ 80 ’ | Version of tag definition | |||
| ‘ 9F33 ’ | Name of the Member State issuing the registration certificate Part 2 | |||
| ‘ 9F34 ’ | Another (e.g. previous national) designation of the equivalent document (optional) | |||
| ‘ 9F35 ’ | Name of the competent authority | |||
| ‘ 9F36 ’ | Name of the authority issuing the registration certificate (optional) | |||
| ‘ 9F37 ’ | Character set used: ‘00’ : ISO/IEC 8859-1 (Latin1 character set) ‘01’ : ISO/IEC 8859-5 (Cyrillic character set) ‘02’ : ISO/IEC 8859-7 (Greek character set) | |||
| ‘ 9F38 ’ | Unambiguous consecutive number of the document as used within the Member State | |||
| ‘ 81 ’ | Registration number | |||
| ‘ 82 ’ | Date of first registration | |||
| ‘ A3 ’ | Vehicle, nesting objects ‘ 87 ’ , ‘ 88 ’ and ‘ 89 ’ | |||
| ‘ 87 ’ | Vehicle make | |||
| ‘ 88 ’ | Vehicle type | |||
| ‘ 89 ’ | Vehicle commercial descriptions | |||
| ‘ 8A ’ | Vehicle identification number | |||
| ‘ 8F ’ | Type approval number | |||
Table 6 lists the Tags identifying the data objects corresponding to the registration data of Chapter II.6. The data objects listed in Table 6 are optional.
Table 6
| Tag | Description | |||
|---|---|---|---|---|
| ‘ 78 ’ | Compatible tag allocation authority, nesting object ‘ 4F ’ (see ISO/IEC 7816-4 and ISO/IEC 7816-6) | |||
| ‘ 4F ’ | Application identifier (see ISO/IEC 7816-4) | |||
| ‘ 74 ’ | Inter-industry template (see ISO/IEC 7816-4 and ISO/IEC 7816-6) corresponding to optional data of the registration certificate Part 1, Chapter II.6, nesting all following objects | |||
| ‘ 80 ’ | Version of tag definition | |||
| ‘ A1 ’ | Personal data nesting objects ‘ A7 ’ , ‘ A8 ’ and ‘ A9 ’ | |||
| ‘ A7 ’ | Vehicle owner nesting objects ‘ 83 ’ , ‘ 84 ’ and ‘ 85 ’ | |||
| ‘ 83 ’ | Surname or business name | |||
| ‘ 84 ’ | Other names or initials (optional) | |||
| ‘ 85 ’ | Address in the Member State | |||
| ‘ A8 ’ | Second vehicle owner nesting objects ‘ 83 ’ , ‘ 84 ’ and ‘ 85 ’ | |||
| … | ||||
| ‘ A9 ’ | Person who may use the vehicle by virtue of legal right other than ownership nesting objects ‘ 83 ’ , ‘ 84 ’ , and ‘ 85 ’ | |||
| … | ||||
| ‘ 98 ’ | Vehicle category | |||
Structure and format of the data according Chapter II.7 are specified by the Member States.
III.12. Reading the registration data U.K.
A. Application selection U.K.
The Application ‘ Vehicle Registration ’ shall be selectable by a SELECT DF (by name, see ISO/IEC 7816-4) with its Application identifier (AID). The AID value is requested from a laboratory selected by the European Commission.
B. Reading data from files U.K.
The files corresponding to Chapter II, letters A, B and D, shall be selectable by SELECT (see ISO/IEC 7816-4) with the command parameters P1 set to ‘ 02 ’ , P2 set to ‘ 04 ’ and the command data field containing the file identifier (see Chapter X, Table 1). The returned FCP template contains the file size which can be useful for reading these files.
These files shall be readable with READ BINARY (see ISO/IEC 7816-4) with an absent command data field and L e set to the length of the expected data, using a short L e .
C. Verification of data authenticity U.K.
To verify the authenticity of the stored registration data, the corresponding electronic signature may be verified. This means that besides the registration data also the corresponding electronic signature may be read from the registration card.
The public key for signature verification can be retrieved by reading the corresponding issuing authority certificate from the registration card. Certificates contain the public key and the identity of the corresponding authority. The signature verification may be performed by another system than the registration card.
The Member States are free in retrieving the public keys and certificates for verifying the issuing authority certificate.
III.13. Special provisions U.K.
Irrespective of the other provisions herein, the Member States, after notifying the European Commission, may add colours, marks or symbols. In addition, for certain data of Chapter III.2 Letter C, the Member States may allow XML format and may allow access via TCP/IP. Member States may, with the agreement of the European Commission, add other applications for which no harmonised rules or documents exist yet at EU level (e.g. roadworthiness certificate), on the vehicle registration card to realise additional vehicle related services.]
[F1This Annex is concerned only with Registration Certificates consisting of Parts I and II.]