ISO/IEC 18013-3:2017/Amd 1:2022
(Amendment)Information technology — Personal identification — ISO-compliant driving licence — Part 3: Access control, authentication and integrity validation — Amendment 1: PACE protocol
Information technology — Personal identification — ISO-compliant driving licence — Part 3: Access control, authentication and integrity validation — Amendment 1: PACE protocol
Technologies de l'information — Identification des personnes — Permis de conduire conforme à l'ISO — Partie 3: Contrôle d'accès, authentification et validation d'intégrité — Amendement 1: Protocole de PAC
General Information
Relations
Buy Standard
Standards Content (Sample)
INTERNATIONAL ISO/IEC
STANDARD 18013-3
Second edition
2017-04
AMENDMENT 1
2022-01
Information technology — Personal
identification — ISO-compliant driving
licence —
Part 3:
Access control, authentication and
integrity validation
AMENDMENT 1: PACE protocol
Technologies de l'information — Identification des personnes —
Permis de conduire conforme à l'ISO —
Partie 3: Contrôle d'accès, authentification et validation d'intégrité
AMENDEMENT 1: Protocole de PAC
Reference number
ISO/IEC 18013-3:2017/Amd. 1:2022(E)
© ISO/IEC 2022
---------------------- Page: 1 ----------------------
ISO/IEC 18013-3:2017/Amd. 1:2022(E)
COPYRIGHT PROTECTED DOCUMENT
© ISO/IEC 2022
All rights reserved. Unless otherwise specified, or required in the context of its implementation, no part of this publication may
be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting on
the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address below
or ISO’s member body in the country of the requester.
ISO copyright office
CP 401 • Ch. de Blandonnet 8
CH-1214 Vernier, Geneva
Phone: +41 22 749 01 11
Email: copyright@iso.org
Website: www.iso.org
Published in Switzerland
ii
© ISO/IEC 2022 – All rights reserved
---------------------- Page: 2 ----------------------
ISO/IEC 18013-3:2017/Amd. 1:2022(E)
Foreword
ISO (the International Organization for Standardization) and IEC (the International Electrotechnical
Commission) form the specialized system for worldwide standardization. National bodies that are
members of ISO or IEC participate in the development of International Standards through technical
committees established by the respective organization to deal with particular fields of technical
activity. ISO and IEC technical committees collaborate in fields of mutual interest. Other international
organizations, governmental and non-governmental, in liaison with ISO and IEC, also take part in the
work.
The procedures used to develop this document and those intended for its further maintenance
are described in the ISO/IEC Directives, Part 1. In particular, the different approval criteria
needed for the different types of document should be noted. This document was drafted in
accordance with the editorial rules of the ISO/IEC Directives, Part 2 (see www.iso.org/directives or
www.iec.ch/members_experts/refdocs).
Attention is drawn to the possibility that some of the elements of this document may be the subject
of patent rights. ISO and IEC shall not be held responsible for identifying any or all such patent
rights. Details of any patent rights identified during the development of the document will be in the
Introduction and/or on the ISO list of patent declarations received (see www.iso.org/patents) or the IEC
list of patent declarations received (see patents.iec.ch).
Any trade name used in this document is information given for the convenience of users and does not
constitute an endorsement.
For an explanation of the voluntary nature of standards, the meaning of ISO specific terms and
expressions related to conformity assessment, as well as information about ISO's adherence to
the World Trade Organization (WTO) principles in the Technical Barriers to Trade (TBT) see
www.iso.org/iso/foreword.html. In the IEC, see www.iec.ch/understanding-standards.
This document was prepared by Joint Technical Committee ISO/IEC JTC 1, Information technology, SC 17,
Cards and security devices for personal identification.
A list of all parts in the ISO/IEC 18013 series can be found on the ISO and IEC websites.
Any feedback or questions on this document should be directed to the user’s national standards
body. A complete listing of these bodies can be found at www.iso.org/members.html and
www.iec.ch/national-committees.
iii
© ISO/IEC 2022 – All rights reserved
---------------------- Page: 3 ----------------------
ISO/IEC 18013-3:2017/Amd. 1:2022(E)
Information technology — Personal identification — ISO-
compliant driving licence —
Part 3:
Access control, authentication and integrity validation
AMENDMENT 1: PACE protocol
Page 2, Clause 2
Replace:
ICAO Technical Report — Supplemental Access Control for Machine Readable Travel Documents, v1.01,
2010 [TR-PACE]
with:
ICAO Doc 9303-10, Machine Readable Travel Documents, Seventh Edition, 2015, Part 10: Logical Data
Structure (LDS) for Storage of Biometrics and Other Data in the Contactless Integrated Circuit (IC)
ICAO Doc 9303-11, Machine Readable Travel Documents, Seventh Edition, 2015, Part 11: Security
Mechanisms for MRTDs
Page 4, 3.10
Delete Note 1 to entry and designate the existing "Note 2 to entry" as "Note 1 to entry".
1
© ISO/IEC 2022 – All rights reserved
---------------------- Page: 4 ----------------------
ISO/IEC 18013-3:2017/Amd. 1:2022(E)
Page 31, 8.4.4.1
Replace Table 10 with:
Table 10 — Non-match alert parameters
Name, Fixed (F) or
Variable (V),
Field format/length/type Example
Mandatory (M) or
Optional (O)
SAI_referencestring, V, M Byte 1: An input string of ABC4DEF con-
tained in the SAI_referencestring
— ‘00’ if the input string follows;
field will be coded as ‘00 41 42 43
34 44 45 46’, where ‘41 42 43 34
— ‘01’ if a reference to where the input string
44 45 46’ is the encoded form of
can be obtained follows.
ABC4DEF.
Subsequent bytes:
If the licence number is used as the
— If byte 1 = ‘00’, the input string follows
input string, this will be coded as
from byte 2 (inclusive). The input
‘01 01 08’.
string is encoded in accordance with
ISO/IEC 8859-1:1998;
If the 16th data element of Data
Group 12 is used as the input
— If byte 1 = ‘01’, the reference to the
parameter, the input string will be
field that contains the input string is
coded as ‘01 12 16’.
constructed as aabb where aa is the data
group and bb is the sequence number of
the referenced data element, with aabb
encoded as unsigned BCD.
SAI_inputmethod, V, O Byte 1: SAI standard and input method. The If the licence number is used as the
four most significant bits (upper nibble) of input string (i.e. a SAI is construct-
byte 1 can take on any of the following values: ed around the existing licence
number field on the IDL), the value
— ‘0x’ if the input string is based on an
of SAI_inputmethod will be ‘00’.
existing field;
If, in addition, the input string is
— ‘1x’ if the input string is based on a
printed in OCR-B font, the input
dedicated field;
string will be ‘00 01’, or alternative-
ly ‘00 01 00’.
— ‘2x’ if the input string is stored in a
barcode; If, in addition, the SAI is located on
the portrait side of the IDL, with
— ‘4x’ if the input string is based on IDL MRZ.
the top left corner of the SAI at 29
mm from the left edge of the card
The four least significant bits (lower nibble) of
and 24 mm from the bottom edge
byte 1 denotes the input method, and can take
of the card, and the right bottom
on any of the following values:
corner of the SAI at 59 mm from
— ‘x0’ if the input string is intended for
the left edge of the card and 14 mm
manual input;
from the bottom edge of the card,
the input string will be ‘00 01 00 00
— ‘x1’ if the input string is intended for OCR
29 24 59 14’.
interpretation;
— ‘x2’ if the input string is stored as a
barcode.
Byte 2: Barcode standard. If the first byte is of
the form ‘x2’, byte 2 is mandatory, taking on
any of the following values:
2
© ISO/IEC 2022 – All rights reserved
---------------------- Page: 5 ----------------------
ISO/IEC 18013-3:2017/Amd. 1:2022(E)
Table 10 (continued)
Name, Fixed (F) or
Variable (V),
Field format/length/type Example
Mandatory (M) or
Optional (O)
— ‘00’ for PDF417;
— ‘01’ for Code 39 (ISO/IEC 16388);
— ‘02’ for Code 128 (ISO/IEC 15417);
— ‘03’ for data matrix (ISO/IEC 16022);
— ‘FE’ for other barcode standards not
provided for above.
If the first byte is not of the form ‘x2’, byte 2 is
optional. If present, it shall have the
following value:
— ‘FF’ for no barcode.
Byte 2 is also mandatory if Bytes 3 to 7 are
present.
Bytes 3 to 7: Position of the SAI, expressed
as ‘aa bb cc dd ee’, where ‘aa’ is the side of the
card on which the SAI appears (‘00’ for por-
trait side, and ‘01’ for non-portrait side), ‘bb cc’
is the top left corner of the SAI (where ‘bb’ is
the distance from the left edge of the IDL and
‘cc’ is the distance from the bottom edge of the
card), and ‘dd ee’ is the bottom right corner
of the SAI (where ‘dd’ is the distance from the
left edge of the IDL and ‘ee’ is the distance
from the bottom edge of the card), with all dis-
tances measured in millimetres, and encoded
as BCD.
The bytes are progressively mandatory, i.e.
SAI_inputmethod can consist only of byte 1, or
only of bytes 1 and 2, or of bytes 1 to 7.
Page 35, 8.7.3
Delete the NOTE and insert the following sentence at the end of this subclause:
The chip access procedure shall be in accordance with ICAO Doc 9303-11:2015, 4.2. The SecurityInfos
shall be in accordance with ICAO Doc 9303-10:2015, 5.3.1 and ICAO Doc 9303-11:2015, 9.2.8.
Page 39, 10.4
Insert the following NOTE at the end of this subclause:
NOTE '6F' is nested within DO '7E' when used as file control information template for
ISO/IEC 18013 (all parts).
3
© ISO/IEC 2022 – All rights reserved
---------------------- Page: 6 ----------------------
ISO/IEC 18013-3:2017/Amd. 1:2022(E)
Page 40, 10.5
Replace the NOTE with:
NOTE See ICAO Doc 9303-11:2015, 9.2.8.
Page 40, 10.6
Replace the NOTE with:
NOTE See ICAO Doc 9303-10:2015, 5.3.1.
Page 67, C.1
Replace the second paragraph with:
PACE is specified in ICAO Doc 9303-11:2015, 4.4.1 to 4.4.5. Specification defined in ICAO Doc 9303-
11:2015, 9.1, 9.2 and 9.4 to 9.8 applicable to PACE also apply for IDL in respect of the limitations
defined in C.2.1.
Replace the third paragraph with:
After PACE, AES and 3DES shall be applied in Secure Messaging as specified in ICAO Doc 9303-
11:2015, 9.8.
Replace NOTE 2 with:
NOTE 2 According to ICAO Doc 9303-11:2015, padding is always performed by the secure
messaging layer, so that the underlying message authentication code does not need to perform any
internal padding.
Page 67, C.2
Replace the entire subclause with:
C.2 Changes to ICAO Doc 9303-11
C.2.1 General
This subclause describes the changes that apply to ICAO Doc 9303-11:2015, 4.4.1 to 4.4.5 to support
access to the IDL application using PACE.
Only ECDH generic mapping shall be used.
For eMRTD Application, read Driving Licence Application.
For eMRTD, read IDL.
For eMRTD chip or MRTD chip, read SIC.
For MRZ, read input string.
For password, read input string.
4
© ISO/IEC 2022 – All rights reserved
---------------------- Page: 7 ----------------------
ISO/IEC 18013-3:2017/Amd. 1:2022(E)
C.2.2 Key derivation function
The key derivation function for PACE is specified in ICAO Doc 9303-11:2015, 9.7.3. This document
replaces the encoding of passwords with "f (π) = input string".
C.3
Add the following new subclause after C.2:
C.3 Worked example
C.3.1 General
This subclause provides a worked example for PACE. Not all steps are explicitly shown. As a precondition,
the MF is selected.
C.3.2 Read PACEInfo
1. Select EF.CardAccess (file identifier = '01 1C')
Unprotected command APDU
CLA INS P1 P2 Lc Command data field
'00' 'A4' '02' '0C' '02' '01 1C'
Unprotected response APDU
SW1-SW2
'90 00'
2. Read EF.CardAccess
Read the first 8 bytes of EF.CardAccess.
Unprotected command APDU
CLA INS P1 P2 Le
'00' 'B0' '00' '00' '08'
Unprotected response APDU
Response data field SW1-SW2
resp_data '90 00'
resp_data = '31 14 30 12 06 0A 04 00'
Read the rest of EF.CardAccess.
5
© ISO/IEC 2022 – All rights reserved
---------------------- Page: 8 ----------------------
ISO/IEC 18013-3:2017/Amd. 1:2022(E)
Unprotected command APDU
CLA INS P1 P2 Le
'00' 'B0' '00' '08' '0E'
Unprotected response APDU
Response data field SW1-SW2
resp_data '90 00'
resp_data = '7F 00 07 02 02 04 02 02 02 01 02 02 01 0C'
Hex string of EF.CardAccess is '31 14 30 12 06 0A 04 00 7F 00 07 02 02 04 02 02 02 01 02 02 01 0C'
Content of EF.CardAccess in this worked example is described in Table C.1.
Table C.1 — Example content of EF.CardAccess
Tag Length Value Note
‘31’ ‘14’ SET data object SecurityInfos
Tag Length Value
‘30’ ‘12’ SEQUENCE data object PACEInfo
Tag Length Value
‘04 00 7F 00 OID id-PACE-ECDH-
‘06’ ‘0A’ 07 02 02 04 GM-AES-CBC-
02 02’ CMAC-128
‘02’ ‘01’ ‘02’ Version 2
a
‘02’ ‘01’ ‘0C’ 1
a
This value indicates NIST P-256 standard domain parameters.
The BER-TLV structure of public key data object is specified in ICAO Doc 9303-11:2015, 9.4. For
convenience, an ASN.1 encoding of the NIST P-256 standard domain parameters is given in
Table C.2.
6
© ISO/IEC 2022 – All rights reserved
---------------------- Page: 9 ----------------------
ISO/IEC 18013-3:2017/Amd. 1:2022(E)
Table C.2 — NIST P-256
...
INTERNATIONAL ISO/IEC
STANDARD 18013-3
Second edition
2017-04
AMENDMENT 1
Second edition
Information technology — Personal
identification — ISO-compliant driving
licence —
Part 3:
Access control, authentication and
integrity validation
AMENDMENT 1: PACE protocol
Partie 3: Contrôle d'accès, authentification et validation d'intégrité
AMENDEMENT 1: Titre manque
PROOF/ÉPREUVE
Reference number
ISO/IEC 18013-3/Amd. 1:2021(E)
© ISO/IEC 2021
---------------------- Page: 1 ----------------------
ISO/IEC 18013-3/Amd. 1:2021(E)
COPYRIGHT PROTECTED DOCUMENT
© ISO/IEC 2021
All rights reserved. Unless otherwise specified, or required in the context of its implementation, no part of this publication may
be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting on
the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address below
or ISO’s member body in the country of the requester.
ISO copyright office
CP 401 • Ch. de Blandonnet 8
CH-1214 Vernier, Geneva
Phone: +41 22 749 01 11
Email: copyright@iso.org
Website: www.iso.org
Published in Switzerland
ii
PROOF/ÉPREUVE © ISO/IEC 2021 – All rights reserved
---------------------- Page: 2 ----------------------
ISO/IEC 18013-3/Amd. 1:2021(E)
Foreword
ISO (the International Organization for Standardization) and IEC (the International Electrotechnical
Commission) form the specialized system for worldwide standardization. National bodies that are
members of ISO or IEC participate in the development of International Standards through technical
committees established by the respective organization to deal with particular fields of technical
activity. ISO and IEC technical committees collaborate in fields of mutual interest. Other international
organizations, governmental and non-governmental, in liaison with ISO and IEC, also take part in the
work.
The procedures used to develop this document and those intended for its further maintenance
are described in the ISO/IEC Directives, Part 1. In particular, the different approval criteria
needed for the different types of document should be noted. This document was drafted in
accordance with the editorial rules of the ISO/IEC Directives, Part 2 (see www.iso.org/directives or
www.iec.ch/members_experts/refdocs).
Attention is drawn to the possibility that some of the elements of this document may be the subject
of patent rights. ISO and IEC shall not be held responsible for identifying any or all such patent
rights. Details of any patent rights identified during the development of the document will be in the
Introduction and/or on the ISO list of patent declarations received (see www.iso.org/patents) or the IEC
list of patent declarations received (see patents.iec.ch).
Any trade name used in this document is information given for the convenience of users and does not
constitute an endorsement.
For an explanation of the voluntary nature of standards, the meaning of ISO specific terms and
expressions related to conformity assessment, as well as information about ISO's adherence to
the World Trade Organization (WTO) principles in the Technical Barriers to Trade (TBT) see
www.iso.org/iso/foreword.html. In the IEC, see www.iec.ch/understanding-standards.
This document was prepared by Joint Technical Committee ISO/IEC JTC 1, Information technology, SC 17,
Cards and security devices for personal identification.
A list of all parts in the ISO/IEC 18013 series can be found on the ISO and IEC websites.
Any feedback or questions on this document should be directed to the user’s national standards
body. A complete listing of these bodies can be found at www.iso.org/members.html and
www.iec.ch/national-committees.
iii
© ISO/IEC 2021 – All rights reserved PROOF/ÉPREUVE
---------------------- Page: 3 ----------------------
ISO/IEC 18013-3/Amd. 1:2021(E)
Information technology — Personal identification — ISO-
compliant driving licence —
Part 3:
Access control, authentication and integrity validation
AMENDMENT 1: PACE protocol
Page 2, Clause 2
Replace:
ICAO Technical Report — Supplemental Access Control for Machine Readable Travel Documents,
v1.01, 2010 [TR-PACE]
with:
ICAO Doc 9303-10, Machine Readable Travel Documents, Seventh Edition, 2015, Part 10: Logical
Data Structure (LDS) for Storage of Biometrics and Other Data in the Contactless Integrated Circuit
(IC)
ICAO Doc 9303-11, Machine Readable Travel Documents, Seventh Edition, 2015, Part 11: Security
Mechanisms for MRTDs
Page 4, 3.10
Delete Note 1 to entry and designate the existing "Note 2 to entry" as "Note 1 to entry".
1
© ISO/IEC 2021 – All rights reserved PROOF/ÉPREUVE
---------------------- Page: 4 ----------------------
ISO/IEC 18013-3/Amd. 1:2021(E)
Page 31, 8.4.4.1
Replace Table 10 with:
Table 10 — Non-match alert parameters
Name, Fixed (F) or
Variable (V),
Field format/length/type Example
Mandatory (M) or
Optional (O)
SAI_referencestring, V, M Byte 1: An input string of ABC4DEF con-
tained in the SAI_referencestring
— ‘00’ if the input string follows;
field will be coded as ‘00 41 42 43
34 44 45 46’, where ‘41 42 43 34
— ‘01’ if a reference to where the input string
44 45 46’ is the encoded form of
can be obtained follows.
ABC4DEF.
Subsequent bytes:
If the licence number is used as the
— If byte 1 = ‘00’, the input string follows
input string, this will be coded as
from byte 2 (inclusive). The input
‘01 01 08’.
string is encoded in accordance with
ISO/IEC 8859-1:1998;
If the 16th data element of Data
Group 12 is used as the input
— If byte 1 = ‘01’, the reference to the
parameter, the input string will be
field that contains the input string is
coded as ‘01 12 16’.
constructed as aabb where aa is the data
group and bb is the sequence number of
the referenced data element, with aabb
encoded as unsigned BCD.
SAI_inputmethod, V, O Byte 1: SAI standard and input method. The If the licence number is used as the
four most significant bits (upper nibble) of input string (i.e. a SAI is construct-
byte 1 can take on any of the following values: ed around the existing licence
number field on the IDL), the value
— ‘0x’ if the input string is based on an
of SAI_inputmethod will be ‘00’.
existing field;
If, in addition, the input string is
— ‘1x’ if the input string is based on a
printed in OCR-B font, the input
dedicated field;
string will be ‘00 01’, or alternative-
ly ‘00 01 00’.
— ‘2x’ if the input string is stored in a
barcode; If, in addition, the SAI is located on
the portrait side of the IDL, with
— ‘4x’ if the input string is based on IDL MRZ.
the top left corner of the SAI at 29
mm from the left edge of the card
The four least significant bits (lower nibble) of
and 24 mm from the bottom edge
byte 1 denotes the input method, and can take
of the card, and the right bottom
on any of the following values:
corner of the SAI at 59 mm from
— ‘x0’ if the input string is intended for
the left edge of the card and 14 mm
manual input;
from the bottom edge of the card,
the input string will be ‘00 01 00 00
— ‘x1’ if the input string is intended for OCR
29 24 59 14’.
interpretation;
— ‘x2’ if the input string is stored as a
barcode.
Byte 2: Barcode standard. If the first byte is of
the form ‘x2’, byte 2 is mandatory, taking on
any of the following values:
2
PROOF/ÉPREUVE © ISO/IEC 2021 – All rights reserved
---------------------- Page: 5 ----------------------
ISO/IEC 18013-3/Amd. 1:2021(E)
Table 10 (continued)
Name, Fixed (F) or
Variable (V),
Field format/length/type Example
Mandatory (M) or
Optional (O)
— ‘00’ for PDF417;
— ‘01’ for Code 39 (ISO/IEC 16388);
— ‘02’ for Code 128 (ISO/IEC 15417);
— ‘03’ for data matrix (ISO/IEC 16022);
— ‘FE’ for other barcode standards not
provided for above.
If the first byte is not of the form ‘x2’, byte 2 is
optional. If present, it shall have the
following value:
— ‘FF’ for no barcode.
Byte 2 is also mandatory if Bytes 3 to 7 are
present.
Bytes 3 to 7: Position of the SAI, expressed
as ‘aa bb cc dd ee’, where ‘aa’ is the side of the
card on which the SAI appears (‘00’ for por-
trait side, and ‘01’ for non-portrait side), ‘bb cc’
is the top left corner of the SAI (where ‘bb’ is
the distance from the left edge of the IDL and
‘cc’ is the distance from the bottom edge of the
card), and ‘dd ee’ is the bottom right corner
of the SAI (where ‘dd’ is the distance from the
left edge of the IDL and ‘ee’ is the distance
from the bottom edge of the card), with all
distances measured in millimetres, and encod-
ed as BCD.
The bytes are progressively mandatory, i.e.
SAI_inputmethod can consist only of byte 1, or
only of bytes 1 and 2, or of bytes 1 to 7.
Page 35, 8.7.3
Delete the NOTE and insert the following sentence at the end of this subclause:
The chip access procedure shall be in accordance with ICAO Doc 9303-11:2015, 4.2. The SecurityInfos
shall be in accordance with ICAO Doc 9303-10:2015, 5.3.1 and ICAO Doc 9303-11:2015, 9.2.8.
Page 39, 10.4
Insert the following NOTE at the end of this subclause:
NOTE '6F' is nested within DO '7E' when used as file control information template for
ISO/IEC 18013 (all parts).
3
© ISO/IEC 2021 – All rights reserved PROOF/ÉPREUVE
---------------------- Page: 6 ----------------------
ISO/IEC 18013-3/Amd. 1:2021(E)
Page 40, 10.5
Replace the NOTE with:
NOTE See ICAO Doc 9303-11:2015, 9.2.8.
Page 40, 10.6
Replace the NOTE with:
NOTE See ICAO Doc 9303-10:2015, 5.3.1.
Page 67, C.1
Replace the second paragraph with:
PACE is specified in ICAO Doc 9303-11:2015, 4.4.1 to 4.4.5. Specification defined in ICAO Doc 9303-
11:2015, 9.1, 9.2 and 9.4 to 9.8 applicable to PACE also apply for IDL in respect of the limitations
defined in C.2.1.
Replace the third paragraph with:
After PACE, AES and 3DES shall be applied in Secure Messaging as specified in ICAO Doc 9303-
11:2015, 9.8.
Replace NOTE 2 with:
NOTE 2 According to ICAO Doc 9303-11, padding is always performed by the secure messaging
layer, so that the underlying message authentication code does not need to perform any internal
padding.
Page 67, C.2
Replace the entire subclause with:
C.2 Changes to ICAO Doc 9303-11
C.2.1 General
This subclause describes the changes that apply to ICAO Doc 9303-11:2015, 4.4.1 to 4.4.5 to support
access to the IDL application using PACE.
Only ECDH generic mapping shall be used.
For eMRTD Application, read Driving Licence Application.
For eMRTD, read IDL.
For eMRTD chip or MRTD chip, read SIC.
For MRZ, read input string.
For password, read input string.
C.2.2 Key derivation function
4
PROOF/ÉPREUVE © ISO/IEC 2021 – All rights reserved
---------------------- Page: 7 ----------------------
ISO/IEC 18013-3/Amd. 1:2021(E)
The key derivation function for PACE is specified in ICAO Doc 9303-11:2015, 9.7.3. This document
replaces the encoding of passwords with "f (π) = input string".
C.3
Add the following new subclause after C.2:
C.3 Worked example
C.3.1 General
This subclause provides a worked example for PACE. Not all steps are explicitly shown. As a precondition,
the MF is selected.
C.3.2 Read PACEInfo
1. Select EF.CardAccess (file identifier = '01 1C')
Unprotected command APDU
CLA INS P1 P2 Lc Command data field
'00' 'A4' '02' '0C' '02' '01 1C'
Unprotected response APDU
SW1-SW2
'90 00'
2. Read EF.CardAccess
Read the first 8 bytes of EF.CardAccess.
Unprotected command APDU
CLA INS P1 P2 Le
'00' 'B0' '00' '00' '08'
Unprotected response APDU
Response data field SW1-SW2
resp_data '90 00'
resp_data = '31 14 30 12 06 0A 04 00'
Read the rest of EF.CardAccess.
Unprotected command APDU
CLA INS P1 P2 Le
'00' 'B0' '00' '08' '0E'
5
© ISO/IEC 2021 – All rights reserved PROOF/ÉPREUVE
---------------------- Page: 8 ----------------------
ISO/IEC 18013-3/Amd. 1:2021(E)
Unprotected response APDU
Response data field SW1-SW2
resp_data '90 00'
resp_data = '7F 00 07 02 02 04 02 02 02 01 02 02 01 0C'
Hex string of EF.CardAccess is '31 14 30 12 06 0A 04 00 7F 00 07 02 02 04 02 02 02 01 02 02 01 0C'
Content of EF.CardAccess in this worked example is described in Table C.1.
Table C.1 — Example content of EF.CardAccess
Tag Length Value Note
SecurityInfos
‘31’ ‘14’ SET data object
Tag Length Value
‘30’ ‘12’ SEQUENCE data object PACEInfo
Tag Length Value
‘04 00 7F 00 OID id-PACE-ECDH-
‘06’ ‘0A’ 07 02 02 04 GM-AES-CBC-
02 02’ CMAC-128
‘02’ ‘01’ ‘02’ Version 2
a
‘02’ ‘01’ ‘0C’ 1
a
This value indicates NIST P-256 standard domain parameters.
The BER-TLV structure of public key data object is specified in ICAO Doc 9303-11:2015, 9.4. For
convenience, an ASN.1 encoding of the NIST P-256 standard domain parameters is given in
Table C.2.
6
PROOF/ÉPREUVE © ISO/IEC 2021 – All rights reserved
---------------------- Page: 9 ----------------------
ISO/IEC 18013-3/Amd. 1:2021(E)
Table C.2 — NIST P-256 standard domain parameters
T L V Note
‘30’ ’81EC’ SEQUENCE data objec
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.