ISO/IEC 19823-16

Information technology — Conformance test methods for security service crypto suites — Part 16: Crypto suite ECDSA-ECDH

This document describes test methods for determining the conformance of security crypto suites defined in ISO/IEC 29167-16. This document contains conformance tests for all mandatory and applicable optional functions. The conformance parameters are the following: — parameters that apply directly affecting system functionality and inter-operability; — protocol including commands and replies; — nominal values and tolerances. Unless otherwise specified, the tests in this document are to be applied exclusively to RFID tags and interrogators defined in the ISO/IEC 18000 series using ISO/IEC 29167-16.

Technologies de l'information — Méthodes d'essai de conformité pour les suites cryptographiques des services de sécurité — Partie 16: Suite cryptographique ECDSA-ECDH

General Information

• Status: Not Published
• ICS: 35.030 - IT Security
• Technical Committee: ISO/IEC JTC 1/SC 31 - Automatic identification and data capture techniques
• Drafting Committee: ISO/IEC JTC 1/SC 31/WG 4 - Radio communications
• Current Stage: 6000 - International Standard under publication
• Start Date: 13-Dec-2025
• Completion Date: 13-Dec-2025

Relations

• Revises: ISO/IEC 19823-16:2020 - Information technology — Conformance test methods for security service crypto suites — Part 16: Crypto suite ECDSA-ECDH security services for air interface communications
• Effective Date: 03-Feb-2024

Standards Content (Sample)

FINAL DRAFT
International
Standard
ISO/IEC
FDIS
19823-16
ISO/IEC JTC 1/SC 31
Information technology —
Secretariat: ANSI
Conformance test methods for
Voting begins on:
security service crypto suites —
2025-10-17
Part 16:
Voting terminates on:
2025-12-12
Crypto suite ECDSA-ECDH
RECIPIENTS OF THIS DRAFT ARE INVITED TO SUBMIT,
WITH THEIR COMMENTS, NOTIFICATION OF ANY
RELEVANT PATENT RIGHTS OF WHICH THEY ARE AWARE
AND TO PROVIDE SUPPOR TING DOCUMENTATION.
IN ADDITION TO THEIR EVALUATION AS
BEING ACCEPTABLE FOR INDUSTRIAL, TECHNO­
LOGICAL, COMMERCIAL AND USER PURPOSES, DRAFT
INTERNATIONAL STANDARDS MAY ON OCCASION HAVE
TO BE CONSIDERED IN THE LIGHT OF THEIR POTENTIAL
TO BECOME STAN DARDS TO WHICH REFERENCE MAY BE
MADE IN NATIONAL REGULATIONS.
Reference number
ISO/IEC FDIS 19823­16:2025(en) © ISO/IEC 2025

FINAL DRAFT
ISO/IEC FDIS 19823-16:2025(en)
International
Standard
ISO/IEC
FDIS
19823-16
ISO/IEC JTC 1/SC 31
Information technology —
Secretariat: ANSI
Conformance test methods for
Voting begins on:
security service crypto suites —
Part 16:
Voting terminates on:
Crypto suite ECDSA-ECDH
RECIPIENTS OF THIS DRAFT ARE INVITED TO SUBMIT,
WITH THEIR COMMENTS, NOTIFICATION OF ANY
RELEVANT PATENT RIGHTS OF WHICH THEY ARE AWARE
AND TO PROVIDE SUPPOR TING DOCUMENTATION.
© ISO/IEC 2025
IN ADDITION TO THEIR EVALUATION AS
All rights reserved. Unless otherwise specified, or required in the context of its implementation, no part of this publication may
BEING ACCEPTABLE FOR INDUSTRIAL, TECHNO­
LOGICAL, COMMERCIAL AND USER PURPOSES, DRAFT
be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting on
INTERNATIONAL STANDARDS MAY ON OCCASION HAVE
the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address below
TO BE CONSIDERED IN THE LIGHT OF THEIR POTENTIAL
or ISO’s member body in the country of the requester.
TO BECOME STAN DARDS TO WHICH REFERENCE MAY BE
MADE IN NATIONAL REGULATIONS.
ISO copyright office
CP 401 • Ch. de Blandonnet 8
CH-1214 Vernier, Geneva
Phone: [phone]
Email: [e-mail]
Website: www.iso.org
Published in Switzerland Reference number
ISO/IEC FDIS 19823­16:2025(en) © ISO/IEC 2025

© ISO/IEC 2025 – All rights reserved
ii
ISO/IEC FDIS 19823-16:2025(en)
Contents Page
Foreword .iv
Introduction .v
1 Scope . 1
2 Normative references . 1
3 Terms, definitions, symbols and abbreviated terms . 1
3.1 Terms and definitions .1
3.2 Symbols .1
3.3 Abbreviated terms .2
4 Test methods . 2
4.1 General .2
4.2 By demonstration .2
4.3 By design .3
5 Test methods related to ISO/IEC 18000-4:2018, MODE 4 . 3
5.1 Default items applicable to the test methods .3
5.1.1 General .3
5.1.2 Test environment .3
5.1.3 Pre-conditioning .3
5.1.4 Default tolerance .3
5.1.5 Total measurement uncertainty .3
5.2 Test setup and measurement equipment .3
5.2.1 Test setup for interrogator testing .4
5.2.2 Test setup for tag testing .4
5.2.3 Test equipment .4
6 Test methods related to ISO/IEC 29167-16 interrogators and tags . 5
6.1 Test map for optional features .5
6.2 Crypto suite requirements .5
6.2.1 General .5
6.2.2 Crypto suite requirements of ISO/IEC 29167-16:2022, Clauses 1 to 6 .5
6.2.3 Crypto suite requirements of ISO/IEC 29167-16:2022, Clauses 7 to 11 .5
6.2.4 Crypto suite requirements of ISO/IEC 29167-16:2022, Annex A .10
6.2.5 Crypto suite requirements of ISO/IEC 29167-16:2022, Annex E .10
6.3 Test patterns for ISO/IEC 18000-4:2018, MODE 4 . 12
6.3.1 General . 12
6.3.2 Test pattern 1 utilizing ISO/IEC 18000-4:2018, 9.3.3 . 12
6.3.3 Test pattern 2 utilizing ISO/IEC 18000-4:2018, 9.3.3 . 13
6.3.4 Test pattern 3 utilizing ISO/IEC 18000-4:2018, 9.3.3 .14
6.3.5 Test pattern 4 utilizing ISO/IEC 18000-4:2018, 9.3.3 .14
6.3.6 Test pattern 5 utilizing ISO/IEC 18000-4:2018, 9.3.3 .14
6.3.7 Test pattern 6 utilizing ISO/IEC 18000-4:2018, 9.3.3 . 15
6.3.8 Test pattern 7 utilizing ISO/IEC 18000-4:2018, 9.3.3 . 15
6.3.9 Test pattern 8 utilizing ISO/IEC 18000-4:2018, 9.3.3 . 15
6.3.10 Test pattern 9 utilizing ISO/IEC 18000-4:2018, 9.3.3 . 15
6.3.11 Test pattern 10 utilizing ISO/IEC 18000-4:2018, 9.3.3 .16
Annex A (informative) Test parameters example . 17
Bibliography .21

© ISO/IEC 2025 – All rights reserved
iii
ISO/IEC FDIS 19823-16:2025(en)
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).
ISO and IEC draw attention to the possibility that the implementation of this document may involve the
use of (a) patent(s). ISO and IEC take no position concerning the evidence, validity or applicability of any
claimed patent rights in respect thereof. As of the date of publication of this document, ISO and IEC had
received notice of (a) patent(s) which may be required to implement this document. However, implementers
are cautioned that this may not represent the latest information, which may be obtained from the patent
database available at www.iso.org/patents and https://patents.iec.ch. ISO and IEC shall not be held
responsible for identifying any or all such patent rights.
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,
Subcommittee SC 31, Automatic identification and data capture techniques.
This second edition cancels and replaces the first edition (ISO/IEC 19823-16:2020), which has been
technically revised.
The main changes are as follows:
— command codes have been technically revised, “01h” revised to “80h” in 6.3;
— the normative reference to “ISO/IEC 29167-16:2015” has been updated and the normative reference to
“ISO/IEC 29167-15:2022” has been removed.
A list of all parts in the ISO/IEC 19823 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.

© ISO/IEC 2025 – All rights reserved
iv
ISO/IEC FDIS 19823-16:2025(en)
Introduction
The ISO/IEC 29167 series describes security services that are applicable for the ISO/IEC 18000 series.
The various parts of the ISO/IEC 29167 series describe crypto suites that are optional extensions to the
ISO/IEC 18000 series air interfaces.
The ISO/IEC 19823 series describes the conformance test methods for security service crypto suites. It is
related to the ISO/IEC 18047 series, which describes the radio frequency identification device conformance
test methods, in the same way as the ISO/IEC 29167 series is related to the ISO/IEC 18000 series. These
relations mean that, for a product that is claimed to be compliant to a pair of ISO/IEC 18000-n and
ISO/IEC 29167-m, the test methods of ISO/IEC 18047-n and ISO/IEC 19823-m apply. If a product supports
more than one part of the ISO/IEC 18000 series or the ISO/IEC 29167 series, all related parts of the
ISO/IEC 18047 series and the ISO/IEC 19823 series apply.
This document describes the test methods for the elliptic curve digital signature algorithm-elliptic curve
Diffie-Hellman (ECDSA-ECDH) crypto suite as standardized in ISO/IEC 29167-16.
The conformance parameters are the following:
— parameters that apply directly affecting system functionality and inter-operability;
— protocol including commands and replies;
— nominal values and tolerances.

© ISO/IEC 2025 – All rights reserved
v
FINAL DRAFT International Standard ISO/IEC FDIS 19823-16:2025(en)
Information technology — Conformance test methods for
security service crypto suites —
Part 16:
Crypto suite ECDSA-ECDH
1 Scope
This document describes the test methods for determining the conformance of security crypto suites
defined in ISO/IEC 29167-16.
This document contains conformance tests for all mandatory and applicable optional functions.
Unless otherwise specified, the tests in this document are only applicable to radio frequency identification
(RFID) tags and interrogators defined in the ISO/IEC 18000 series using ISO/IEC 29167-16.
2 Normative references
The following documents are referred to in the text in such a way that some or all of their content constitutes
requirements of this document. For dated references, only the edition cited applies. For undated references,
the latest edition of the referenced document (including any amendments) applies.
ISO/IEC 17025, General requirements for the competence of testing and calibration laboratories
ISO/IEC 18000-4:2018, Information technology — Radio frequency identification for item management — Part
4: Parameters for air interface communications at 2,45 GHz
ISO/IEC 19762, Information technology — Automatic identification and data capture (AIDC) techniques —
Vocabulary
ISO/IEC 29167-16:2022, Information technology — Automatic identification and data capture techniques —
Part 16: Crypto suite ECDSA-ECDH security services for air interface communications
3 Terms, definitions, symbols and abbreviated terms
3.1 Terms and definitions
For the purposes of this document, the terms and definitions given in ISO/IEC 19762 and ISO/IEC 29167-16 apply.
ISO and IEC maintain terminology databases for use in standardization at the following addresses:
— ISO Online browsing platform: available at https:// www .iso .org/ obp
— IEC Electropedia: available at https:// www .electropedia .org/
3.2 Symbols
For the purposes of this document, the symbols given in ISO/IEC 19762 apply.

© ISO/IEC 2025 – All rights reserved
ISO/IEC FDIS 19823-16:2025(en)
3.3 Abbreviated terms
For the purposes of this document, the abbreviated terms given in ISO/IEC 19762 and the following apply.
DBPSK differential binary phase shift keying
ECDH elliptic curve Diffie-Hellman
ECDHP ECDH parameter
ECDSA elliptic curve digital signature algorithm
MAC message authentication code
MAM mutual authentication message
MIC message integrity code
O-QPSK offset quadrature phase shift keying
RN random number
SEK session encryption key
SIK session integrity check key
TPK temporary public key
TRAIS tag and reader air interface security
TRAIS-P TRAIS based on public key cryptography
TTP trusted third party
TTPID identifier of TTP
4 Test methods
4.1 General
This document describes the general test methods for ISO/IEC 29167-16. As the parts of the ISO/IEC 19823
series are always tested in relation with the ISO/IEC 18047 series, a duplication of information requirements
and specifications should be avoided.
Clause 5 defines elements that are covered in the respective part of the ISO/IEC 19823 series.
Clause 6 defines elements that are not covered by the ISO/IEC 18047 series and are therefore addressed in
this document.
4.2 By demonstration
"By demonstration" means that laboratory testing of one or, if required for statistical reasons, multiple
products, processes, or services to ensure conformance.
A test laboratory meeting the requirements of ISO/IEC 17025 shall be selected for the performance of the
indicated testing to ensure conformance of the component or system.
For protocol requirements that are verified by demonstration, the test conditions are specified by this
document. The detailed test plan is at the discretion of the test laboratory.

© ISO/IEC 2025 – All rights reserved
ISO/IEC FDIS 19823-16:2025(en)
4.3 By design
"By design" means that either design parameters or theoretical analyses, or both, ensure conformance. A
vendor submitting a component or system for conformancetesting shall provide the necessary technical
information, in the form of a technical memorandum or similar. A test laboratory shall issue a test certificate
indicating whether the technical analysis was sufficient to ensure conformance of the component or system.
For protocol requirements that are verified by design, the method of technical analysis is at the discretion
of the submitting vendor and is not specified by this document. In general, the technical analysis shall have
sufficient rigor and technical depth to convince a test engineer knowledgeable of the protocol that the
particular requirement has been met.
5 Test methods related to ISO/IEC 18000-4:2018, MODE 4
5.1 Default items applicable to the test methods
5.1.1 General
The requirements and recommendations in 5.1 shall be fulfilled.
5.1.2 Test environment
Unless otherwise specified, testing shall take place in an environment of temperature 23 °C ± 3 °C
(73 °F ± 5 °F) and relative humidity of 40 % to 60 %.
5.1.3 Pre-conditioning
Where pre-conditioning is required by the test method, the tags and interrogators to be tested shall be
conditioned to the test environment for an appropriate period of time before testing.
5.1.4 Default tolerance
Unless otherwise specified, a default tolerance of ±5 % shall be applied to the quantity values given to
specify the characteristics of the test equipment (e.g. linear dimensions) and the test method procedures
(e.g. test equipment adjustments).
5.1.5 Total measurement uncertainty
The total measurement uncertainty for each quantity determined by these test methods shall be stated in
the test report.
NOTE 1 Basic information is given in Reference [5].
NOTE 2 The default items applicable to the test methods defined in 5.1 are detailed in ISO/IEC TR 18047-4.
5.2 Test setup and measurement equipment
This subclause defines the test setup and measurement equipment for verifying the operation of a tag or an
interrogator according to ISO/IEC 18000-4:2018, MODE 4.
Test results shall not be influenced by the setup method of the test.
Test setups include:
— test setup for interrogator testing (see 5.2.1),
— test setup for tag testing (see 5.2.2),
— test equipment (see 5.2.3).
© ISO/IEC 2025 – All rights reserved
ISO/IEC FDIS 19823-16:2025(en)
These are described in the following subclauses.
5.2.1 Test setup for interrogator testing
An interrogator with integral antenna(e) shall be equipped with temporary antenna connector(s), or else
coupling device(s) [i.e. sense antenna(e)] shall be used to connect to the test equipment.
A sense antenna shall not affect test results. Appropriate distances (e.g. 30 cm), antenna sizes and types (e.g.
patch antenna) and antenna polarization (i.e. circular polarization) shall be used. The antenna configuration
and distance shall be included in the test report.
To set up an interrogator with the appropriate test pattern and operational modes, one of two methods shall
be used (combinations are also be possible):
a) an implemented test mode,
b) a tag for initializing the appropriate operational mode.
The air interface parameter in a test mode shall behave in the same way as the air interface parameter
during normal usage.
Unless otherwise stated, for all tests, the frequency of the reference carrier shall conform to
ISO/IEC 18000-4:2018, 9.3.1. The output power shall be set to maximum (both carriers switched on).
5.2.2 Test setup for tag testing
A tag with integral antenna(e) shall be equipped with temporary antenna connector(s), or else suitable
coupling device(s) [i.e. antenna(e)] shall be used to connect to the test equipment.
A sense antenna shall not affect test results. Appropriate distances (e.g. 30 cm), antenna sizes and types
(e.g. patch antenna), as well as antenna polarization (i.e. circular polarization) shall be used. The antenna
configuration and distance shall be included in the test report.
To set up a tag with the appropriate test pattern and operational modes, one of two methods shall be used
(combinations shall also be possible):
a) an implemented test mode,
b) an interrogator for initializing the appropriate operational mode.
Unless otherwise stated, for all tests, the frequency of the reference carrier shall conform to
ISO/IEC 18000-4:2018, 9.3.1.
5.2.3 Test equipment
All tests shall be performed using commercial test equipment. In addition to the measurement devices
described in the following subclauses, appropriate devices such as power supplies, splitters, combiners and
cables shall be used.
The reference point for all measurements shall be either (temporary) antenna connector(s), or appropriate
coupling device(s). The reference point shall be documented in the test report.
5.2.3.1 Spectrum analyser
A spectrum analyser with the capability of digital demodulating and with vector signal analysis capability
shall be used. Appropriate trigger functionality shall be either implemented in the spectrum analyser or
generated externally with additional measurement devices.

© ISO/IEC 2025 – All rights reserved
ISO/IEC FDIS 19823-16:2025(en)
5.2.3.2 Signal generator
A signal generator for the 2,45 GHz band shall be used to generate an interrogator output signal for testing
tags. The signal level for the tests shall be within the operational range of the receiver input of the tag. The
input level shall be specified by the tag manufacturer and shall be documented in the test report.
5.2.3.3 Logic analyser
A logic analyser shall be used for verification of the correct data. Therefore, the analyser shall be capable of
storage of sequent samples in 0,5 s.
6 Test methods related to ISO/IEC 29167-16 interrogators and tags
6.1 Test map for optional features
Table 1 lists all optional features of the crypto suite defined by Tag and Reader Air Interface Security
(TRAIS) based on Public key cryptography (TRAIS-P) and shall be used as a template for reporting the test
results. Furthermore, Table 1 shall be used in reference to the test requirements in 6.2.
Table 1 — Test map for optional features
Item Mark items to be tested
Feature Additional requirement Test results
no. for supplied product
1 Mutual Authentication Shall be tested with the Authenticate
without TTP involved command of the relevant part of the
ISO/IEC 18000 series.
2 Mutual Authentication Shall be tested with the Authenticate
with TTP involved command of the relevant part of the
ISO/IEC 18000 series.
3 Authenticate communi- Shall be tested with the AuthComm
cation command of the relevant part of the
ISO/IEC 18000 series.
4 Secure communication Shall be tested with the SecureComm
command of the relevant part of the
ISO/IEC 18000 series.
Table 2 to Table 5 lists all crypto suite requirements that shall be tested in dependence of the features of
Table 1 as supported by the device under test. Items marked with M are mandatory and shall be tested for
each device under test.
6.2 Crypto suite requirements
6.2.1 General
Subclause 6.2 refers to the requirements of ISO/IEC 29167-21.
6.2.2 Crypto suite requirements of ISO/IEC 29167-16:2022, Clauses 1 to 6
All of the requirements of ISO/IEC 29167-16:2022, Clauses 5 to 6 shall be followed.
6.2.3 Crypto suite requirements of ISO/IEC 29167-16:2022, Clauses 7 to 11
Table 2 contains all of the requirements of ISO/IEC 29167-16:2022, Clauses 7 to 11.

© ISO/IEC 2025 – All rights reserved
ISO/IEC FDIS 19823-16:2025(en)
Table 2 — Crypto suite requirements of ISO/IEC 29167-16:2022, Clauses 7 to 11
Item Protocol
Requirement M/O Applies to Verification method
a
no. subclause
1 7.1 ECDHP: M Interrogator/ By design
Tag
ECDH parameter, consisting of parameter
ID, parameter length and parameter content
three parts, where the parameter ID shall be
8 bits; parameter shall be 16 bits in length and
indicate the number of bytes in the parameter
content. The values of ECDH parameter:
1) 01 : The field value shall be denoted by
h
OIDs. The Length subfield indicates the
number of octets of OIDs. The values of
Content subfield are the content of OIDs.
2)  Other: All other values are RFU.
2 7.1 MK[127:0] M Interrogator/ By design
Tag
Master key
3 7.1 MIC [255:0] M Tag By design
t
Message integrity code generated by the tag,
the length shall be 256 bits.
4 7.1 RN [63:0] M Tag By design
t
64-bit random number generated by the tag
5 7.1 Sig [383:0] M Tag By design
t
Digital signature generated by the tag. The
length shall be 384 bits.
6 7.1 TPK [391:0] M Tag By design
t
Temporary public key generated by tag, the
length shall be 392 bits.
7 7.1 X [391:0] M Tag By design
t
Temporary private key generated by tag and
used for ECDH exchange.
8 7.1 MIC [255:0] M Interrogator By design
i
Message integrity code generated by the inter-
rogator, the length shall be 256 bits.
9 7.1 RN [63:0] M Interrogator By design
i
64-bit random number generated by theinter-
rogator.
10 7.1 Sig [383:0] M Interrogator By design
i
Digital signature generated by the interroga-
tor. The length shall be 384 bits.
11 7.1 TPK [391:0] M Interrogator By design
i
Temporary public key generated by interroga-
tor, the length shall be 392 bits.
12 7.1 X [391:0] M Interrogator By design
i
Temporary private key generated by interroga-
tor and used for ECDH exchange.
13 7.2 Cert Type shall be 4 bits, Value shall be: M Interrogator/ By design
Tag
© ISO/IEC 2025 – All rights reserved
ISO/IEC FDIS 19823-16:2025(en)
TTaabbllee 22 ((ccoonnttiinnueuedd))
Item Protocol
Requirement M/O Applies to Verification method
a
no. subclause
a) 0000:Value subfield contains X.509
certificate of Interrogator, Cert ;
i
b) 0001:Value subfield contains X.509
certificate of Tag, Cert ;
t
c) 0010:Value subfield contains X.509
certificate of TTP, Cert ;
ttp
d) Other: All other values are RFU.
14 8 A transition to Ready state shall also cause a M Tag By design
reset of all variables used by the crypto suite.
15 9 Implementations of this crypto suite shall M Tag By design
ensure that all memory used for intermediate
results is cleared after each operation (mes-
sage-response pair) and after reset.
16 10.2.1 The crypto suite shall parse the Messages and M Interrogator By demonstration
process the data based on the value of CSI, using test patterns
which is the first parameter of all commands. 3,4,7 and 8
17 10.2.2 The FN shall be 8 bits. M Interrogator By demonstration
using test patterns
3,4,7 and 8
18 10.2.2 The IID shall be 64 bits. M Interrogator By demonstration
using test patterns
3,4,7 and 8
19 10.2.2 The following sections of this document de- M Interrogator By demonstration
scribe the formatting of Message and Response using test patterns
for authentication. AuthType shall be "00". 3,4,7 and 8
20 10.2.2 In MAM1.1 Message, AuthStep shall be "000". M Interrogator By demonstration
using test patterns
3,4,7 and 8
21 10.2.2 If TTP not to be involved, TTPID shall be "0000 M Interrogator By demonstration
0000", or using test patterns
3,4,7 and 8
If TTP to be involved, TTPID shall be "0000
0001".
22 10.2.2 ECDH parameter shall be 01 . M Interrogator By demonstration
h
using test patterns
3,4,7 and 8
23 10.2.3 The FN shall be 8 bits. M Tag By demonstration
using test patterns
1,2,5 and 6
24 10.2.3 TheTID shall be 64 bits. M Tag By demonstration
using test patterns
1,2,5 and 6
25 10.2.3 TTPID is the same as the one in the MAM1.1 M Tag By demonstration
Message. using test patterns
1,2,5 and 6
26 10.2.3 ECDH parameter shall
...

ISO/IEC DISFDIS 19823-16:2024(en)
ISO/IEC JTC 1/SC 31
Secretariat: ANSI
Date: 2024-07-222025-08-18
Information technology — Conformance test methods for security
service crypto suites — —
Part 16:
Crypto suite ECDSA-ECDH
Technologies de l' information — [Conformance test methods for security service crypto suites] —
Partie 16: [Crypto suite ECDSA-ECDH security services for air interface communications]

FDIS stage
2 © ISO 2023 – All rights reserved

ISO/IEC FDIS 19823-16:2025(en)
© ISO/IEC 20242025
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'sISO’s member body in the country of the requester.
ISO Copyright Officecopyright office
CP 401 • Ch. de Blandonnet 8
CH-1214 Vernier, Geneva
Phone: + 41 22 749 01 11
Email: E-mail: [e-mail]
Website: www.iso.org
Published in Switzerland.
© ISO/IEC 2025 – All rights reserved
iii
ISO/IEC FDIS 19823-16:2025(en)
Contents
Foreword . v
Introduction . vi
1 Scope . 1
2 Normative references . 1
3 Terms, definitions, symbols and abbreviated terms . 1
3.1 Terms and definitions . 1
3.2 Symbols . 1
3.3 Abbreviated terms . 2
4 Test methods . 2
4.1 General. 2
4.2 By demonstration . 2
4.3 By design . 3
5 Test methods related to ISO/IEC 18000-4:2018, MODE 4 . 3
5.1 Default items applicable to the test methods . 3
5.2 Test setup and measurement equipment . 3
6 Test methods related to ISO/IEC 29167-16 interrogators and tags . 5
6.1 Test map for optional features . 5
6.2 Crypto suite requirements . 5
6.3 Test patterns for ISO/IEC 18000-4:2018, MODE 4 . 13
Annex A (informative) Test parameters example . 18
Bibliography . 23

© ISO/IEC 2025 – All rights reserved
iv
ISO/IEC FDIS 19823-16:2025(en)
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).
ISO and IEC draw attention to the possibility that the implementation of this document may involve the use of
(a) patent(s). ISO and IEC take no position concerning the evidence, validity or applicability of any claimed
patent rights in respect thereof. As of the date of publication of this document, ISO and IEC had received notice
of (a) patent(s) which may be required to implement this document. However, implementers are cautioned
that this may not represent the latest information, which may be obtained from the patent database available
at www.iso.org/patents and https://patents.iec.ch. ISO and IEC shall not be held responsible for identifying
any or all such patent rights.
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,
Subcommittee SC 31, Automatic identification and data capture techniques.
This second edition cancels and replaces the first edition (ISO/IEC 19823-16:2020), which has been
technically revised.
The main changes are as follows:
— — command codes have been technically revised, “01h” revised to “80h” in 6.3;;
— — the normative references havereference to “ISO/IEC 29167-16:2015” has been updated and the
normative reference to “ISO/IEC 29167-15:2022” has been removed.
A list of all parts in the ISO/IEC 19823 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.
© ISO/IEC 2025 – All rights reserved
v
ISO/IEC FDIS 19823-16:2025(en)
Introduction
The ISO/IEC 29167 series describes security services asthat are applicable for the ISO/IEC 18000 series. The
various parts of the ISO/IEC 29167 series describe crypto suites that are optional extensions to the
ISO/IEC 18000 series air interfaces.
The ISO/IEC 19823 series describes the conformance test methods for security service crypto suites. It is
related to the ISO/IEC 18047 series, which describes the radio frequency identification device conformance
test methods, in the same way as the ISO/IEC 29167 series is related to the ISO/IEC 18000 series. These
relations mean that, for a product that is claimed to conformbe compliant to a pair of documents from the
ISO/IEC 18000 series-n and the ISO/IEC 29167 series-m, the test methods of the ISO/IEC 18047 series-n and
the ISO/IEC 19823 series-m apply. If a product supports more than one part of the ISO/IEC 18000 series or
the ISO/IEC 29167 series, all related parts of the ISO/IEC 18047 series and the ISO/IEC 19823 series apply.
This document describes the test methods for the elliptic curve digital signature algorithm-elliptic curve
Diffie-Hellman (ECDSA-ECDH) crypto suite as standardized in ISO/IEC 29167-16. The changes to the current
edition are the following:
— — command codes have been technically revised, “01h” revised to “80h” in subclause 6.3;
— — normative references have been updated, “ISO/IEC 29167-16:2015” updated to “ISO/IEC 29167-
15:2022”.
The conformance parameters are the following:
— — parameters that apply directly affecting system functionality and inter-operability;
— — protocol including commands and replies;
— — nominal values and tolerances.
© ISO/IEC 2025 – All rights reserved
vi
ISO/IEC FDIS 19823-16:2025(en)
Information technology — Conformance test methods for security
service crypto suites —
Part 16:
Crypto suite ECDSA-ECDH security services for air interface
communications
1 Scope
This document describes the test methods for determining the conformance of security crypto suites defined
in ISO/IEC 29167-16.
This document contains conformance tests for all mandatory and applicable optional functions.
Unless otherwise specified, the tests in this document are only applicable to RFIDradio frequency
identification (RFID) tags and interrogators defined in the ISO/IEC 18000 series using ISO/IEC 29167-16.
2 Normative references
The following documents are referred to in the text in such a way that some or all of their content constitutes
requirements of this document. For dated references, only the edition cited applies. For undated references,
the latest edition of the referenced document (including any amendments) applies.
ISO/IEC 17025, General requirements for the competence of testing and calibration laboratories
ISO/IEC 18000--4:2018, Information technology — Radio frequency identification for item management — Part
4: Parameters for air interface communications at 2,45 GHz
ISO/IEC 19762, Information technology — Automatic identification and data capture (AIDC) techniques —
Harmonized vocabularyVocabulary
ISO/IEC 29167--16:2022, Information technology — Automatic identification and data capture techniques —
Part 16: Crypto suite ECDSA-ECDH security services for air interface communications
3 Terms, definitions, symbols and abbreviated terms
3.1 Terms and definitions
For the purposes of this document, the terms and definitions given in ISO/IEC 19762 and ISO/IEC 29167-16
apply.
ISO and IEC maintain terminology databases for use in standardization at the following addresses:
— — ISO Online browsing platform: available at https://www.iso.org/obp
— — IEC Electropedia: available at https://www.electropedia.org/
3.2 Symbols
For the purposes of this document, the symbols given in ISO/IEC 19762 apply.
© ISO/IEC 2025 – All rights reserved
ISO/IEC FDIS 19823-16:2025(en)
3.3 Abbreviated terms
For the purposes of this document, the abbreviated terms given in ISO/IEC 19762 and the following apply.
DBPSK differential binary phase shift keying
ECDH elliptic curve Diffie-Hellman
ECDHP ECDH parameter
ECDSA elliptic curve digital signature algorithm
MAC message authentication code
MAM mutual authentication message
MIC message integrity code
O-QPSK offset quadrature phase shift keying
RN random number
SEK session encryption key
SIK session integrity check key
TPK temporary public key
TRAIS tag and reader air interface security
TRAIS-P TRAIS based on public key cryptography
TTP trusted third party
TTPID identifier of TTP
4 Test methods
4.1 General
This document describes the general test methods for ISO/IEC 29167-16. As the parts of the ISO/IEC 19823
series are always tested in relation with the ISO/IEC 18047 series, a duplication of information requirements
and specifications should be avoided.
5Clause 5 defines elements that are covered in the respective part of the ISO/IEC 19823 series.
6Clause 6 defines elements that are not covered by the ISO/IEC 18047 series and are therefore addressed in
this document.
4.2 By demonstration
"By demonstration" means that laboratory testing of one or, if required for statistical reasons, multiple
products, processes, or services to ensure conformance.
A test laboratory meeting the requirements of ISO/IEC 17025 shall be selected for the performance of the
indicated testing to ensure conformance of the component or system.
For protocol requirements that are verified by demonstration, the test conditions are specified by this
document. The detailed test plan is at the discretion of the test laboratory.
© ISO/IEC 2025 – All rights reserved
ISO/IEC FDIS 19823-16:2025(en)
4.3 By design
"By design" means that either design parameters and/or theoretical analyses that, or both, ensure
conformance. A vendor submitting a component or system for compliance testingconformancetesting shall
provide the necessary technical information, in the form of a technical memorandum or similar. A test
laboratory shall issue a test certificate indicating whether the technical analysis was sufficient to ensure
conformance of the component or system.
For protocol requirements that are verified by design, the method of technical analysis is at the discretion of
the submitting vendor and is not specified by this document. In general, the technical analysis shall have
sufficient rigor and technical depth to convince a test engineer knowledgeable of the protocol that the
particular requirement has been met.
5 Test methods in respectrelated to ISO/IEC 18000-4:2018, ModeMODE 4
5.1 Default items applicable to the test methods
5.1.1 General
The following requirements and applicable optional requirementsrecommendations in 5.1 shall be fulfilled.
5.1.15.1.2 Test environment
Unless otherwise specified, testing shall take place in an environment of temperature 23 °C ± 3 °C
(73 °F ± 5 °F) and relative humidity of 40 % to 60 %.
5.1.25.1.3 Pre-conditioning
Where pre-conditioning is required by the test method, the tags and interrogators to be tested shall be
conditioned to the test environment for an appropriate period of time before testing.
5.1.35.1.4 Default tolerance
Unless otherwise specified, a default tolerance of ±5 % shall be applied to the quantity values given to specify
the characteristics of the test equipment (e.g. linear dimensions) and the test method procedures (e.g. test
equipment adjustments).
5.1.45.1.5 Total measurement uncertainty
The total measurement uncertainty for each quantity determined by these test methods shall be stated in the
test report.
NOTE 1 Basic information is given in Reference [0“ISO Guide to the Expression of Uncertainty in Measurement”, ISBN
92-67-10188-9, 1993.].
NOTE 2 The default items applicable to the test methods defined in 5.15.1 is given are detailed in ISO/IEC TR 18047-
4.
5.2 Test setup and measurement equipment
This subclause defines the test setup and measurement equipment for verifying the operation of a tag or an
interrogator according to ISO/IEC 18000-4:2018, ModeMODE 4.
Test results shall not be influenced by the setup method of the test.
Test setups include:
© ISO/IEC 2025 – All rights reserved
ISO/IEC FDIS 19823-16:2025(en)
— — test setup for interrogator testing (see 5.2.15.2.1),),
— — test setup for tag testing (see 5.2.25.2.2),),
— — test equipment (see 5.2.35.2.3).).
These are described in the following subclauses.
5.2.1 Test setup for interrogator testing
An interrogator with integral antenna(e) shall be equipped with temporary antenna connector(s), or else
coupling device(s) [i.e. sense antenna(e)] shall be used to connect to the test equipment.
A sense antenna shall not affect test results. Appropriate distances (e.g. 30 cm), antenna sizes and types (e.g.
patch antenna) and antenna polarization (i.e. circular polarization) shall be used. The antenna configuration
and distance shall be included in the test report.
To set up an interrogator with the appropriate test pattern and operational modes, one of two methods shall
be used (combinations shallare also be possible):
a) a) an implemented test mode,
b) b) a tag for initializing the appropriate operational mode.
The air interface parameter in a test mode shall behave in the same way as the air interface parameter during
normal usage.
Unless otherwise stated, for all tests, the frequency of the reference carrier shall conform to ISO/IEC 18000-
4:2018, 9.3.1. The output power shall be set to maximum (both carriers switched on).
5.2.2 Test setup for tag testing
A tag with integral antenna(e) shall be equipped with temporary antenna connector(s), or else suitable
coupling device(s) [i.e. antenna(e)] shall be used to connect to the test equipment.
A sense antenna shall not affect test results. Appropriate distances (e.g. 30 cm), antenna sizes and types (e.g.
patch antenna), as well as antenna polarization (i.e. circular polarization) shall be used. The antenna
configuration and distance shall be included in the test report.
To set up a tag with the appropriate test pattern and operational modes, one of two methods shall be used
(combinations shall also be possible):
a) a) an implemented test mode,
b) b) an interrogator for initializing the appropriate operational mode.
Unless otherwise stated, for all tests, the frequency of the reference carrier shall conform to ISO/IEC 18000-
4:2018, 9.3.1.
5.2.3 Test equipment
All tests shall be performed using commercial test equipment. In addition to the measurement devices
described in the following subclauses, appropriate devices such as power supplies, splitters, combiners and
cables shall be used.
© ISO/IEC 2025 – All rights reserved
ISO/IEC FDIS 19823-16:2025(en)
The reference point for all measurements shall be either (temporary) antenna connector(s), or appropriate
coupling device(s). The reference point shall be documented in the test report.
5.2.3.1 Spectrum analyser
A spectrum analyser with the capability of digital demodulating and with vector signal analysis capability shall
be used. Appropriate trigger functionality shall be either implemented in the spectrum analyser or generated
externally with additional measurement devices.
5.2.3.2 Signal generator
A signal generator for the 2.,45 GHz band shall be used to generate an interrogator output signal for testing
tags. The signal level for the tests shall be within the operational range of the receiver input of the tag. The
input level shall be specified by the tag manufacturer and shall be documented in the test report.
5.2.3.3 Logic analyser
A logic analyser shall be used for verification of the correct data. Therefore, the analyser shall be capable of
storage of sequent samples in 0.,5 seconds.
6 Test methods in respectrelated to ISO/IEC 29167-16 interrogators and tags
6.1 Test map for optional features
Table 1Table 1 lists all optional features of the crypto suite defined by Tag and Reader Air Interface Security
(TRAIS) based on Public key cryptography (TRAIS-P) and shall be used as a template for reporting the test
results. Furthermore, Table 1Table 1 shall be used in reference to the test requirements in 6.26.2.
Table 1 — Test map for optional features
Item Mark items to be tested
Feature Additional requirement Test results
no. for supplied product
1 Mutual Authentication Shall be tested with the Authenticate
without TTP involved command of the relevant part of the
ISO/IEC 18000 series.
2 Mutual Authentication Shall be tested with the Authenticate
with TTP involved command of the relevant part of the
ISO/IEC 18000 series.
3 Authenticate Shall be tested with the AuthComm
communication command of the relevant part of the
ISO/IEC 18000 series.
Shall be tested with the SecureComm
4 Secure communication
command of the relevant part ofISOof
the ISO/IEC 18000 series.
Table 2Table 2 to Table 5Table 5 lists all crypto suite requirements that shall be tested in depending on
dependence of the features of Table 1Table 1 as supported by the device under test. Items marked with M are
mandatory and shall be tested for each device under test.
6.2 Crypto suite requirements
6.2.1 General
This subclause contains all of Subclause 6.2 refers to the requirements of ISO/IEC 29167-16.21.
© ISO/IEC 2025 – All rights reserved
ISO/IEC FDIS 19823-16:2025(en)
6.2.2 Crypto suite requirements of ISO/IEC 29167-16:2022, Clauses 1 to 6
All of the requirements of ISO/IEC 29167-16:2022, Clauses 1to 6 are mandatory, inherently by design only5
to 6 shall be followed.
6.2.3 Crypto suite requirements of ISO/IEC 29167-16:2022, Clauses 7 to 11
Table 2Table 2 contains all of the requirements of ISO/IEC 29167-16:2022, Clauses 7 to 11.
Table 2 — Crypto suite requirements of ISO/IEC 29167-16:2022, Clauses 7 to 11
Protocol
Item
subclausesub Requirement M/O Applies to Verification method
no.
a
clause
1 7.1 ECDHP: M Interrogator/Ta By design
g
ECDH parameter, consisting of parameter ID,
parameter length and parameter content three
parts, where the parameter ID shall be 8 bits;
parameter shall be 16 bits in length and indicate
the number of bytes in the parameter content.
The values of ECDH parameter:
1) 1)  01h: The field value shall be denoted by
OIDs. The Length subfield indicates the
number of octets of OIDs. The values of
Content subfield are the content of OIDs.
2)  Other: All other values are RFU.
2 7.1 MK[127:0] M Interrogator/ By design
Tag
Master key
3 7.1 MIC [255:0] M Tag By design
t
Message integrity code generated by the tag, the
length shall be 256 bits.
4 7.1 RN [63:0] M Tag By design
t
64-bit random number generated by the tag
5 7.1 Sigt[383:0] M Tag By design
Digital signature generated by the tag. The
length shall be 384 bits.
6 7.1 TPKt[391:0] M Tag By design
Temporary public key generated by tag, the
length shall be 392 bits.
7 7.1 X [391:0] M Tag By design
t
Temporary private key generated by tag and
used for ECDH exchange.
8 7.1 MIC [255:0] M Interrogator By design
i
Message integrity code generated by the
interrogator, the length shall be 256 bits.
9 7.1 RNi[63:0] M Interrogator By design
64-bit random number generated by
theinterrogator.
10 7.1 Sig [383:0] M Interrogator By design
i
© ISO/IEC 2025 – All rights reserved
ISO/IEC FDIS 19823-16:2025(en)
Protocol
Item
subclausesub Requirement M/O Applies to Verification method
no.
a
clause
Digital signature generated by the interrogator.
The length shall be 384 bits.
11 7.1 TPKi[391:0] M Interrogator By design
Temporary public key generated by
interrogator, the length shall be 392 bits.
12 7.1 X [391:0] M Interrogator By design
i
Temporary private key generated by
interrogator and used for ECDH exchange.
13 7.2 Cert Type shall be 4 bits, Value shall be: M Interrogator/ By design
Tag
a) a) 0000:Value subfield contains

X.509 certificate of Interrogator, Certi;
b) b) 0001:Value subfield contains
X.509 certificate of Tag, Cert ;
t
c) c) 0010:Value subfield contains
X.509 certificate of TTP, Certttp;
d) d) Other: All other values are RFU.
14 8 A transition to Ready state shall also cause a M Tag By design
reset of all variables used by the crypto suite.
15 9 Implementations of this crypto suite shall ensure M Tag By design
that all memory used for intermediate results is
cleared after each operation (message-response
pair) and after reset.
16 10.2.1 The crypto suite shall parse the Messages and M Interrogator By demonstration
process the data based on the value of CSI, which using Testtest
is the first parameter of all commands. patterns 3,4,7 and 8
17 10.2.2 The FN shall be 8 bits. M Interrogator By demonstration
using Testtest
patterns 3,4,7 and 8
18 10.2.2 The IID shall be 64 bits. M Interrogator By demonstration
using Testtest
patterns 3,4,7 and 8
19 10.2.2 The following sections of this document describe M Interrogator By demonstration
the formatting of Message and Response for using Testtest
authentication. AuthType shall be "00". patterns 3,4,7 and 8
By demonstration
20 10.2.2 In MAM1.1 Message, AuthStep shall be "000". M Interrogator
using Testtest
patterns 3,4,7 and 8
21 10.2.2 If TTP not to be involved, TTPID shall be "0000 M Interrogator By demonstration
0000", or using Testtest
patterns 3,4,7 and 8
If TTP to be involved, TTPID shall be "0000
0001".
© ISO/IEC 2025 – All rights reserved
ISO/IEC FDIS 19823-16:2025(en)
Protocol
Item
subclausesub Requirement M/O Applies to Verification method
no.
a
clause
22 10.2.2 ECDH parameter shall be 01h. M Interrogator By demonstration
using Testtest
patterns 3,4,7 and 8
23 10.2.3 The FN shall be 8 bits. M Tag By demonstration
using Testtest
patterns 1,2,5 and 6
24 10.2.3 TheTID shall be 64 bits. M Tag By demonstration
using Testtest
patterns 1,2,5 and 6
25 10.2.3 TTPID is the same as the one in the MAM1.1 M Tag By demonstration
Message. using Testtest
patterns 1,2,5 and 6
26 10.2.3 ECDH parameter shall be 01h. M Tag By demonstration
using Testtest
patterns 1,2,5 and 6
27 10.2.4 The FN shall be 8 bits. M Interrogator By demonstration
using Testtest
patterns 4 and 8
28 10.2.4 The following sections of this document describe M Interrogator By demonstration
the formatting of Message and Response for using Testtest
authentication. AuthType shall be "00". patterns 4 and 8
29 10.2.4 In MAM1.2 Message, AuthStep shall be "001". M Interrogator By demonstration
using Testtest
patterns 4 and 8
30 10.2.4 AuthRes: This field shall be present if TTPID = O Interrogator By demonstration
"0000 0001" in MAM1.1 Message; otherwise, using Testtest
this field is not present. patterns 4 and 8
31 10.2.5 The FN shall be 8 bits. M Tag By demonstration
using Testtest
patterns 2 and 6
32 10.3.1 The tag should have ECC-based private key St M Interrogator/ By design
and the related certificate Cert . The interrogator
t
Tag
shall have ECC-based private key S and the
i
related certificate Certi.
33 10.3.1 For the implementation of this crypto suite an M Interrogator/ By design
air interface protocol shall support security
Tag
commands that allow the exchange of data
between the interrogator and the tag that has
this crypto suite implemented. The security
command contains a message with parameters
for the crypto suite. The reply of the tag contains
a response with the data that is returned by the
crypto suite.
Authenticate (MAM1.1 Message) and MAM 1.1
Response, Authenticate (MAM1.2 Message) and
MAM 1.2 Response shall be implemented(See
ISO/IEC 29167-16:2022, Figure 3).
© ISO/IEC 2025 – All rights reserved
ISO/IEC FDIS 19823-16:2025(en)
Protocol
Item
subclausesub Requirement M/O Applies to Verification method
no.
a
clause
34 10.3.2 Transmits command Authenticate (MAM1.1 M Interrogator By demonstration
Message) to the tag (See ISO/IEC 29167- using Testtest
16:2022, Table 4). patterns 3,4,7 and 8
35 10.3.2 If TTPID in Authenticate (MAM1.1 Message) is O Tag By design
not "0000 0000" or "0000 0001", the
authentication failed. The tag shall remain in the
Ready state.
36 10.3.2 Transmits MAM1.1Response to the M Tag By design
interrogator(See ISO/IEC 29167-16:2022,
Table 5).
37 10.3.2 Sigt = ECDSA M Tag By design
(S ,TID||IID||Cert ||TTPID||RN ||TPK ||ECDHP).
t t t t
38 10.3.2 After returning the MAM1.1 Response, the tag M Tag By design
shall remain in the Authenticate state.
Check whether the values of TTPID and ECDHP
39 10.3.2 M Interrogator By design
in MAM1.1 Response are equal to the values of
TTPID and ECDHP in Authenticate (MAM1.1
Message). If not, the authentication failed.
40 10.3.2 Use Qt extracted from certificate Certt to verify M Interrogator By design
Sigt. If failed, the authentication failed.
41 10.3.2 Generates Xi and TPKi, uses Xi and TPKt to M Interrogator By design
perform the ECDH computation, gets
(X •TPK ) , computes KD-HMAC-
i t abscissa
SHA256((X •TPK ) , RN ||RN ) to generate a
i t abscissa t i
128 bits MK.
42 10.3.2 Computes KD-HMAC-SHA256 (MK, M Interrogat
...