ISO/IEC 18013-5:2021(E) - Amendment 1 Draft 8 - Changes and discussion notes

Aug 31, 2026

Upload by Mason

Draft amendment text for ISO/IEC 18013-5:2021(E) covering personal identification via ISO-compliant mobile driving licence (mDL) applications. Summarizes proposed changes arising from the previous WG10 meeting, including negotiated handover, reader authentication for multiple document requests, revocation mechanisms and related certificate profile topics, MSO validity versus DS certificate verification requirements, and updates to device and cryptographic expectations such as updated x509 COSE requirements and transport security parameters. Notes items that are still under discussion or not yet included, plus editorial-only updates and scope boundaries for reader business-logic verification.

LanguageEnglish

CategoryForms

FormatDOCX

Pages172

Reading Time1 h 0 min

AccessFree to download

Foreword

Introduction

1 Scope

2 Normative references

3 Terms and definitions

4 Abbreviated terms

5 Conformance requirement

6 mDL overview

6.1 Interfaces

6.2 Functional requirements

6.3 Technical requirements

7 mDL data model

7.1 mDL document type and namespace

7.2 mDL data

8 Transaction

8.1 Encoding of data structures and data elements

8.2 Device engagement

8.3 Data retrieval

9 Security mechanisms

ISO/IEC TC JTC1/SC 17 Date: 20241-081009-032429 ISO/IEC 18013-5:2021(E) Secretariat: BSI Personal identification — ISO-compliant driving licence — Part 5: Mobile driving licence (mDL) application Identification des personnes — Permis de conduire conforme à l'ISO —Partie 5: Application pour permis de conduire sur dispositif mobile (mDL) This is the draft 381 for the amendment 1 changes based on the discussions from the last WG10 meeting. All changes still need to be discussed and validated by the group. See the notes for items that still require input or comments. Changes in the document include:Not yet included in this draft but discussed : SessionEstablishement for negotiated handover Reader Authentication for multiple doc requests Revocation mechanism, including certificate profile MSO validity vs DS certificate verification requirements Criticality info in the request PSM info element DeviceSigned updated proposal Updated x509 cose requirements Remove BrainpoolP320r1 from Table b.7 and b.8 Agreed TLS 1.3 requirements L2CAP message size Still under discussion : Consider specifying an optional revocation mechanisms Consider clarifying options for when age_over_nn are not available Support sending the SessionEstablishment message during NFC handover Agreed but not yet included in this draft : Negotiated handover example Variety of purely editioral items, mostly typos. Not yet included in this draft and not yet discussed :To discuss : Variety of purely editioral items, mostly typos.. Add clarification that verifying business logic is an important responsibility of the mDL reader but requirements for that are out of scope for this document. Negotiated handover example Clarification of QR handover direction in QR presentment section Clarify that for each type only one RetrievalOptions array shall be present in 8.2.2.1 BLE multiplexing info BLE unsubscribe requirement BLE message size vs MTU sizeNot yet discussed : Server retrieval elements presence in table 5 Ensure that all information necessary to setup the L2CAP info is present (besides the PSM) Agreed to look at this, could relate to PSM encoding Contents Page TOC \o "2-3" \h \z \t "Heading 1;1;ANNEX;1;ANNEXN;1;ANNEXZ;1;na2;1;na3;1;na4;1;na5;1;na6;1;Title;1;SECTION HEADER;1;HEADING(Nonumber);1;ANNEX_title;1;Base_Heading;1;Front Head;1;AMEND Terms Heading;1;AMEND Heading 1 Unnumbered;1;Biblio Title;1;Foreword Title;1;Intro Title;1" HYPERLINK \l "_Toc82007396" Foreword PAGEREF _Toc82007396 \h iv HYPERLINK \l "_Toc82007397" Introduction PAGEREF _Toc82007397 \h v HYPERLINK \l "_Toc82007398" 1 Scope PAGEREF _Toc82007398 \h 1 HYPERLINK \l "_Toc82007399" 2 Normative references PAGEREF _Toc82007399 \h 1 HYPERLINK \l "_Toc82007400" 3 Terms and definitions PAGEREF _Toc82007400 \h 3 HYPERLINK \l "_Toc82007401" 4 Abbreviated terms PAGEREF _Toc82007401 \h 5 HYPERLINK \l "_Toc82007402" 5 Conformance requirement PAGEREF _Toc82007402 \h 6 HYPERLINK \l "_Toc82007403" 6 mDL overview PAGEREF _Toc82007403 \h 7 HYPERLINK \l "_Toc82007404" 6.1 Interfaces PAGEREF _Toc82007404 \h 7 HYPERLINK \l "_Toc82007405" 6.2 Functional requirements PAGEREF _Toc82007405 \h 7 HYPERLINK \l "_Toc82007406" 6.3 Technical requirements PAGEREF _Toc82007406 \h 8 HYPERLINK \l "_Toc82007407" 6.3.1 Data model PAGEREF _Toc82007407 \h 8 HYPERLINK \l "_Toc82007408" 6.3.2 Data exchange PAGEREF _Toc82007408 \h 9 HYPERLINK \l "_Toc82007409" 6.3.3 Security mechanisms PAGEREF _Toc82007409 \h 13 HYPERLINK \l "_Toc82007410" 7 mDL data model PAGEREF _Toc82007410 \h 15 HYPERLINK \l "_Toc82007411" 7.1 mDL document type and namespace PAGEREF _Toc82007411 \h 15 HYPERLINK \l "_Toc82007412" 7.2 mDL data PAGEREF _Toc82007412 \h 16 HYPERLINK \l "_Toc82007413" 7.2.1 Overview PAGEREF _Toc82007413 \h 16 HYPERLINK \l "_Toc82007414" 7.2.2 Portrait of mDL holder PAGEREF _Toc82007414 \h 20 HYP

FAQs

What is this document’s purpose regarding ISO/IEC 18013-5:2021(E)?

It is a draft for Amendment 1 changes to ISO/IEC 18013-5:2021(E), based on outcomes of the last WG10 meeting, and it lists items that still require discussion and validation.

Which change topics are mentioned as discussed but not yet included in the draft?

The notes mention negotiated handover establishment, reader authentication for multiple document requests, revocation mechanisms (including certificate profile), MSO validity versus DS certificate verification requirements, and updates to device-signed and related COSE and security requirements.

What items are still under discussion or only planned for later inclusion?

The document lists optional revocation mechanisms, clarifications for cases where age attributes are not available, support for SessionEstablishment during NFC handover, negotiated handover examples, QR handover direction clarifications, BLE multiplexing and unsubscribe requirements, and relationships between BLE message size and MTU size.

Aug 31, 2026

Upload by Mason