ISO/IEC 19823-21
(Main)Information technology — Conformance test methods for security service crypto suites — Part 21: Crypto suite SIMON
Information technology — Conformance test methods for security service crypto suites — Part 21: Crypto suite SIMON
This document describes methods for determining conformance to the security crypto suite defined in ISO/IEC 29167‑21. This document contains conformance tests for all mandatory 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 intended to be applied exclusively to RFID tags and interrogators defined in the ISO/IEC 18000 series using ISO/IEC 29167‑21.
Technologies de l'information — Méthodes d'essai de conformité pour les suites cryptographiques des services de sécurité — Partie 21: Suite cryptographique SIMON
General Information
Relations
Standards Content (Sample)
FINAL DRAFT
International
Standard
ISO/IEC
FDIS
19823-21
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 21:
Voting terminates on:
2025-12-12
Crypto suite SIMON
Technologies de l'information — Méthodes d'essai de conformité
pour les suites cryptographiques des services de sécurité —
Partie 21: Suite cryptographique SIMON
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 1982321:2025(en) © ISO/IEC 2025
FINAL DRAFT
ISO/IEC FDIS 19823-21:2025(en)
International
Standard
ISO/IEC
FDIS
19823-21
ISO/IEC JTC 1/SC 31
Information technology —
Secretariat: ANSI
Conformance test methods for
Voting begins on:
security service crypto suites —
Part 21:
Voting terminates on:
Crypto suite SIMON
Technologies de l'information — Méthodes d'essai de conformité
pour les suites cryptographiques des services de sécurité —
Partie 21: Suite cryptographique SIMON
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: +41 22 749 01 11
Email: copyright@iso.org
Website: www.iso.org
Published in Switzerland Reference number
ISO/IEC FDIS 1982321:2025(en) © ISO/IEC 2025
© ISO/IEC 2025 – All rights reserved
ii
ISO/IEC FDIS 19823-21:2025(en)
Contents Page
Foreword .iv
Introduction .v
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 1
4 Test methods . 2
4.1 General .2
4.2 By demonstration .2
4.3 By design .2
5 Test requirements for ISO/IEC 18000-63 interrogators and tags . 2
6 Test methods related to ISO/IEC 29167-21 interrogators and tags . 2
6.1 Test map for optional features .2
6.2 Crypto suite requirements .3
6.2.1 General .3
6.2.2 Crypto suite requirements of ISO/IEC 29167-21:2025, Clauses 4 to 8 and
Annexes A to C .3
6.2.3 Crypto suite requirements of ISO/IEC 29167-21:2025, Clauses 9 to 12 and
Annex E .3
6.3 Test patterns . . 12
6.3.1 General . 12
6.3.2 Test Pattern 1 . 12
6.3.3 Test Pattern 2 . 12
6.3.4 Test Pattern 3 . 13
6.3.5 TestPattern 4 . 13
6.3.6 Test Pattern 5 .14
6.3.7 Test Pattern 6 .14
6.3.8 Test Pattern 7 . 15
6.3.9 Test Pattern 8 . 15
6.3.10 Test Pattern 9 .16
6.3.11 TestPattern 10 .16
6.3.12 Test Pattern 11 .17
Bibliography .18
© ISO/IEC 2025 – All rights reserved
iii
ISO/IEC FDIS 19823-21: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-21:2019), which has been
technically revised.
The main change is as follows: test items have been updated to reflect changes to the over-the-air protocol.
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-21: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 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 conform to a pair 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.
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.
NOTE 1 ISO/IEC 18047-6 contains the conformance test requirements of ISO/IEC 18000-6, ISO/IEC 18000-61,
ISO/IEC 18000-62, ISO/IEC 18000-63 and ISO/IEC 18000-64.
NOTE 2 Test methods for interrogator and tag performance are covered by the ISO/IEC 18046 series.
© ISO/IEC 2025 – All rights reserved
v
FINAL DRAFT International Standard ISO/IEC FDIS 19823-21:2025(en)
Information technology — Conformance test methods for
security service crypto suites —
Part 21:
Crypto suite SIMON
1 Scope
This document describes the methods to determine conformance to the security crypto suite defined in
ISO/IEC 29167-21.
This document contains conformance tests for all mandatory 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-21.
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-63, Information technology — Radio frequency identification for item management — Part 63:
Parameters for air interface communications at 860 MHz to 930 MHz Type C
ISO/IEC 18047-6, Information technology — Radio frequency identification device conformance test methods
— Part 6: Test methods for air interface communications at 860 MHz to 930 MHz
ISO/IEC 19762, Information technology — Automatic identification and data capture (AIDC) techniques —
Vocabulary
ISO/IEC 29167-21, Information technology — Automatic identification and data capture techniques — Part 21:
Crypto suite SIMON security services for air interface communications
3 Terms and definitions
For the purposes of this document, the terms and definitions given in ISO/IEC 19762 and in ISO/IEC 29167-21
and the following 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/
© ISO/IEC 2025 – All rights reserved
ISO/IEC FDIS 19823-21:2025(en)
4 Test methods
4.1 General
This document describes the test methods for ISO/IEC 29167-21. As parts of the ISO/IEC 19823 series
are always tested in relation to the ISO/IEC 18047 series, duplication of information requirements and
specifications is meant to be avoided.
Clause 5 defines elements that are covered in the respective part of the ISO/IEC 18047 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
If tests are labelled “by demonstration”, then laboratory testing of one or (if required for statistical reasons)
multiple products, processes or services is required to ensure conformance. A test laboratory that meets the
requirements of ISO/IEC 17025 shall perform the indicated testing to ensure conformance of the component
or system.
For protocol requirements that are verified by demonstration, the test conditions are specified in this
document. The detailed test plan is left to the discretion of the test laboratory.
4.3 By design
If tests are labelled “by design”, then either the verification of design parameters or theoretical analysis, or
both, are used to ensure conformance. A vendor submitting a component or system for conformance testing
shall provide the necessary technical information, in the form of a technical memorandum or similar. A
test laboratory shall issue a test report 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 requirements for ISO/IEC 18000-63 interrogators and tags
The requirements and recommendations of ISO/IEC 18047-6:2017, Clauses 4 and 5 shall be fulfilled.
Before a device under test is tested according to this document, it shall successfully pass ISO/IEC 18047-6:2017,
Clause 7.
6 Test methods related to ISO/IEC 29167-21 interrogators and tags
6.1 Test map for optional features
Table 1 lists all optional features of this crypto suite and shall be used as a template to report the test results.
Furthermore, it is used to refer to the test requirements in 6.2.
© ISO/IEC 2025 – All rights reserved
ISO/IEC FDIS 19823-21:2025(en)
Table 1 — Test map for optional features
Item To be tested for Test
Feature Additional requirement
no. supplied product? results
Shall be tested with the Authenticate command of
1 Tag Authentication
ISO/IEC 18000-63
Interrogator Shall be tested with the Authenticate command of
Authentication ISO/IEC 18000-63
Mutual Shall be tested with the Authenticate command of
Authentication ISO/IEC 18000-63
Secure Shall be tested with the SecureComm command of
Communication ISO/IEC 18000-63
6.2 Crypto suite requirements
6.2.1 General
This subclause refers to the requirements of ISO/IEC 29167-21.
6.2.2 Crypto suite requirements of ISO/IEC 29167-21:2025, Clauses 4 to 8 and Annexes A to C
All the requirements of ISO/IEC 29167-21:2025, Clauses 4 to 8 and Annexes A to C shall be met and
conformance shall be verified by design only.
6.2.3 Crypto suite requirements of ISO/IEC 29167-21:2025, Clauses 9 to 12 and Annex E
The requirements of ISO/IEC 29167-21:2025, Clauses 9 to 12 and Annex E listed in Table 2 shall be met. This
document shall be read in conjunction with ISO/IEC 29167-21 to provide a full explanation of the terms used.
Table 2 — Crypto suite requirements of ISO/IEC 29167-21:2025, Clauses 9 to 12 and Annex E
Item Protocol Verified
Requirements M/O Applies to
a
no. subclause method
The Interrogator shall generate a random Interro-
1 9.3.2 gator challenge (IChallenge-b/k) that is carried in M Interrogator By design
the TAM1 message.
The Tag shall accept the TAM1 message at any
time (unless occupied by internal processing
and not capable of receiving messages), i.e. upon
2 9.3.3 receipt of the message with valid parameters, the M Tag By design
Tag shall abort any cryptographic protocol that
has not yet been completed and shall remain in
the Initial state.
The Tag shall check if the Step is "00 ". If the value
3 9.3.3 of Step is different, the Tag shall return a "Not M Tag Test Pattern 2
Supported" error.
The Tag shall check if the RFU is "00 ". If the value
4 9.3.3 of RFU is different, the Tag shall return a "Not M Tag Test Pattern 2
Supported" error.
The Tag shall check whether the values of Block-
Size and KeySize are supported by the Tag. If at
5 9.3.3 M Tag By design
least one of these checks is failed, the Tag shall
return a "Not Supported" error.
© ISO/IEC 2025 – All rights reserved
ISO/IEC FDIS 19823-21:2025(en)
TTabablele 2 2 ((ccoonnttiinnueuedd))
Item Protocol Verified
Requirements M/O Applies to
a
no. subclause method
The Tag shall check whether the values of Block-
Size and KeySize are supported by Key.KeyID
and that Key.KeyID is authorized for use in Tag
6 9.3.3 M Tag By design
authentication. If either or both of these checks
is failed, the Tag shall return a "Not Supported"
error.
The Tag shall check whether the parameter set
PS is supported. If the parameter set PS is not
7 9.3.3 M Tag Test Pattern 2
supported, the Tag shall return a "Not Supported"
error.
Assuming that the TAM1 message is successfully
8 9.3.3 parsed by the Tag, the Tag shall prepare the TAM1 M Tag By design
response.
The Tag shall generate a random salt TRnd-b/k of
9 9.3.4 length r bits were r is given for the parameter set M Tag By design
in Table 4.
The Tag shall use Key.KeyID and SIMON encryp-
tion to form a b-bit string TResponse such that:
10 9.3.4 M Tag Test Pattern 1
TResponse = SIMON-b/k-ENC ( Key.KeyID, C_TAM-
b/k ‖ TRnd-b/k ‖ IChallenge-b/k )
The Tag shall return TResponse to the Interroga-
11 9.3.4 M Tag By design
tor.
After receiving TAM1 response, the Interrogator
shall use Key.KeyID to compute the b-bit string S
where:
12 9.3.5 M Interrogator By design
S = SIMON-b/k-DEC ( Key.KeyID, TResponse ).
The Interrogator shall check that S[t-1:0] = IChal-
lenge-b/k.
The Interrogator shall send an initial message
IAM1 to the Tag prompting the Tag to start a chal-
lenge-response exchange.
13 9.4.2 O Interrogator By design
The Interrogator shall also indicate the variant of
SIMON to be used.
The Tag shall accept this message at any time
(unless occupied by internal processing and not
capable of receiving messages), i.e. upon receipt of
14 9.4.3 the message with valid parameters, the Tag shall O Tag By design
abort any cryptographic protocol that has not yet
been completed and shall remain in the Initial
state.
If Interrogator authentication is not supported on
the Tag, i.e. if "01 " is not a valid value for Auth-
15 9.4.3 O Tag By design
Method, then the Tag shall return a "Not Support-
ed" error condition.
The Tag shall check if the Step is "00 ". If the value
16 9.4.3 of Step is different, the Tag shall return a "Not O Tag Test Pattern 3
Supported" error.
The Tag shall check if the RFU is "00 ". If the value
17 9.4.3 of RFU is different, the Tag shall return a "Not O Tag Test Pattern 3
Supported" error.
The Tag shall check whether the values of Block-
Size and KeySize are supported by the Tag. If at
18 9.4.3 O Tag By design
least one of these checks is failed, the Tag shall
return a "Not Supported" error.
© ISO/IEC 2025 – All rights reserved
ISO/IEC FDIS 19823-21:2025(en)
TTabablele 2 2 ((ccoonnttiinnueuedd))
Item Protocol Verified
Requirements M/O Applies to
a
no. subclause method
The Tag shall check whether the values of Block-
Size and KeySize are supported by Key.KeyID and
that Key.KeyID is authorized for use in Interroga-
19 9.4.3 O Tag By design
tor authentication. If at least one of these checks
is failed, the Tag shall return a "Not Supported"
error.
The Tag shall check whether the value of param-
20 9.4.3 eter set PS is supported by the Tag. If not, the Tag O Tag Test Pattern 3
shall return a "Not Supported" error.
If the IAM1 message is successfully parsed by the
21 9.4.3 O Tag By design
Tag, the Tag shall calculate the IAM1 response.
The Tag shall generate a random challenge TCh-
allenge-b/k of length t bits, where t is determined
22 9.4.4 O Tag By design
by the parameter set, and shall send this to the
Interrogator.
The Interrogator shall construct the IAM2 mes-
23 9.4.5 O Interrogator By design
sage.
The Interrogator shall form a b-bit string IRe-
sponse such that:
IResponse = SIMON-b/k-DEC ( Key.KeyID, C_IAM-
24 9.4.6 O Interrogator Test Pattern 4
b/k ‖ IRnd-b/k ‖ TChallenge-b/k ).
The Interrogator shall send IResponse to the Tag
as part of the IAM2 message; see Table 10.
The Tag shall only accept the IAM2 message when
25 9.4.7 O Tag By design
the cryptographic engine is in state PA1.
If Interrogator authentication is not supported on
the Tag, i.e. if "01 " is not a valid value for Auth-
26 9.4.7 O Tag By design
Method, then the Tag shall return a "Not Support-
ed" error condition.
The Tag shall check if the Step is "01 ". If the value
27 9.4.7 of Step is different, the Tag shall return a "Not O Tag Test Pattern 5
Supported" error.
The Tag shall check if the RFU is "0000 ". If the
28 9.4.7 value of RFU is different, the Tag shall return a O Tag Test Pattern 5
"Not Supported" error.
The Tag shall use Key.KeyID to compute the b-bit
string S where:
29 9.4.7 O Tag By design
S = SIMON-b/k-ENC ( Key.KeyID, IResponse ).
30 9.4.7 The Tag shall check that S[t-1:0] = TChallenge-b/k. O Tag By design
31 9.4.7 The Tag shall prepare IAM2 response. O Tag By design
The Tag shall return the value of TStatus to the
32 9.4.8 O Tag Test Pattern 6
Interrogator.
If, under conditions laid out in the over-the-air
protocol, there is no response from the Tag or if
33 9.4.9 O Interrogator By design
the returned value of TStatus is 0 , then the Inter-
rogator shall abandon the cryptographic protocol.
The Interrogator shall generate a random Interro-
34 9.5.2 gator challenge (IChallenge-b/k) that is carried in O Interrogator By design
the MAM1 message.
The Interrogator shall indicate the variant of
35 9.5.2 O Interrogator By design
SIMON to be used.
© ISO/IEC 2025 – All rights reserved
ISO/IEC FDIS 19823-21:2025(en)
TTabablele 2 2 ((ccoonnttiinnueuedd))
Item Protocol Verified
Requirements M/O Applies to
a
no. subclause method
The Tag shall accept MAM1 message at any time
(unless occupied by internal processing and not
capable of receiving messages), i.e. upon receipt of
36 9.5.3 the message with valid parameters, the Tag shall O Tag By design
abort any cryptographic protocol that has not yet
been completed and shall remain in the Initial
state.
If Mutual authentication is not supported on the
Tag, i.e. if "10 " is not a valid value for AuthMeth-
37 9.5.3 O Tag By design
od, then the Tag shall return a "Not Supported"
error condition.
The Tag shall check if the Step is "00 ". If the value
38 9.5.3 of Step is different, the Tag shall return a "Not O Tag Test Pattern 7
Supported" error.
The Tag shall check if the RFU is "00 ". If the value
39 9.5.3 of RFU is different, the Tag shall return a "Not O Tag Test Pattern 7
Supported" error.
The Tag shall check whether the values of Block-
Size and KeySize are supported by the Tag. If at
40 9.5.3 O Tag By design
least one of these checks is failed, the Tag shall
return a "Not Supported" error.
The Tag shall check whether the values of Block-
Size and KeySize are supported by Key.KeyID and
that Key.KeyID is authorized for use in Interro-
41 9.5.3 O Tag By design
gator-Tag mutual authentication. If at least one of
these checks is failed, the Tag shall return a "Not
Supported" error.
The Tag shall check whether the value of param-
42 9.5.3 eter set PS is supported by the Tag. If not, the Tag O Tag By design
shall return a "Not Supported" error.
The Tag shall generate a random challenge TChal-
43 9.5.3 O Tag By design
lenge-b/k.
The Tag shall construct a b-bit string by concate-
nating C_MAM-b/k with the (b-t-c) most signif-
44 9.5.3 O Tag By design
icant bits of TChallenge-b/k and the entirety of
IChallenge-b/k.
The Tag shall use Key.KeyID to compute the b-bit
string S where:
45 9.5.3 S = SIMON-b/k-ENC ( Key.KeyID, C_MAM-b/k ‖ O Tag Test Pattern 8
TChallenge-b/k [t-1:2t-b+c] ‖
IChallenge-b/k ).
After receiving MAM1 Response, the Interrogator
shall use Key.KeyID to compute the b-bit string T
where:
46 9.5.5 T = SIMON-b/k-DEC ( Key.KeyID, TResponse[b-1:0] O Interrogator By design
).
1. The Interrogator shall check that T[t-1:0] =
IChallenge-b/k.
© ISO/IEC 2025 – All rights reserved
ISO/IEC FDIS 19823-21:2025(en)
TTabablele 2 2 ((ccoonnttiinnueuedd))
Item Protocol Verified
Requirements M/O Applies to
a
no. subclause method
If the cryptographic protocol has not been aban-
doned, the Interrogator shall form a b-bit string
IResponse depending on the par
...
ISO/IEC DISFDIS 19823-21:2024(en)
ISO/IEC JTC 1/SC 31
Secretariat: ANSI
Date: 2024-07-222025-10-03
Information technology — Conformance test methods for security
service crypto suites —
Part 21:
Crypto suite SIMON
Technologies de l'information — Méthodes d'essai de conformité pour les suites cryptographiques des services
de sécurité— Partie 21: Suite cryptographique SIMON —
Partie 21: Suite cryptographique SIMON
FDIS stage
ISO/IEC FDIS 19823-21: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’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
EmailE-mail: copyright@iso.org
Website: www.iso.org
Published in Switzerland
© ISO/IEC 2025 – All rights reserved
ii
ISO/IEC FDIS 19823-21:2025(en)
Contents
Foreword. iv
Introduction . v
1 Scope. 1
2 Normative references. 1
3 Terms and definitions . 1
4 Test methods. 2
4.1 General . 2
4.2 By demonstration . 2
4.3 By design . 2
5 Test requirements for ISO/IEC 18000-63 interrogators and tags. 2
6 Test methods related to ISO/IEC 29167-21 interrogators and tags. 2
6.1 Test map for optional features . 2
6.2 Crypto suite requirements . 3
6.3 Test patterns . 15
Bibliography . 23
© ISO/IEC 2025 – All rights reserved
iii
ISO/IEC FDIS 19823-21: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-21:2019), which has been
technically revised.
The main changes arechange is as follows:
— Test test items have been updated to reflect changes to the over-the-air protocol.
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-21: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 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 compliantconform 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.
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.
NOTE 1 ISO/IEC 18047--6 contains the conformance test requirements of ISO/IEC 18000--6, ISO/IEC 18000--61,
ISO/IEC 18000--62, ISO/IEC 18000--63, and ISO/IEC 18000--64.
NOTE 2 Test methods for interrogator and tag performance are covered by the ISO/IEC 18046 series.
© ISO/IEC 2025 – All rights reserved
v
ISO/IEC FDIS 19823-21:2025(en)
Information technology — Conformance test methods for security
service crypto suites —
Part 21:
Crypto suite SIMON
1 Scope
This document describes the methods to determine conformance to the security crypto suite defined in
ISO/IEC 29167--21.
This document contains conformance tests for all mandatory functions.
Unless otherwise specified, the tests in this document are intendedonly applicable to be applied exclusively to
radio frequency identification (RFID) tags and interrogators defined in the ISO/IEC 18000 series using
ISO/IEC 29167--21.
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--63, Information technology — Radio frequency identification for item management — Part 63:
Parameters for air interface communications at 860 MHz to 930 MHz Type C
ISO/IEC 18047--6, Information technology — Radio frequency identification device conformance test methods
— Part 6: Test methods for air interface communications at 860 MHz to 930 MHz
ISO/IEC 19762, Information technology — Automatic identification and data capture (AIDC) techniques —
Harmonized vocabulary — Vocabulary
ISO/IEC 29167--21, Information technology — Automatic identification and data capture techniques — Part
21: Crypto suite SIMON security services for air interface communications
3 Terms, and definitions, symbols and abbreviated terms
For the purposes of this document, the terms and definitions given in ISO/IEC 19762 and in ISO/IEC 29167-
21 and the following 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/
© ISO/IEC 2025 – All rights reserved
ISO/IEC FDIS 19823-21:2025(en)
4 Test methods
4.1 General
This document describes the test methods for ISO/IEC 29167--21. As parts of the ISO/IEC 19823 series are
always tested in relation to the ISO/IEC 18047 series, duplication of information requirements and
specifications is meant to be avoided.
5Clause 5 defines elements that are covered in the respective part of the ISO/IEC 18047 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
If tests are labelled “by demonstration””, then laboratory testing of one or (if required for statistical reasons)
multiple products, processes or services is required to ensure conformance. A test laboratory that meets the
requirements of ISO/IEC 17025 shall perform the indicated testing to ensure conformance of the component
or system.
For protocol requirements that are verified by demonstration, the test conditions are specified in this
document. The detailed test plan is left to the discretion of the test laboratory.
4.3 By design
If tests are labelled “by design””, then either the verification of design parameters and/or theoretical analysis
is, or both, are used to ensure conformance. A vendor submitting a component or system for conformance
testing shall provide the necessary technical information, in the form of a technical memorandum or similar.
A test laboratory shall issue a test report 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 requirements for ISO/IEC 18000-63 interrogators and tags
The mandatory requirements and applicable optional requirementsrecommendations of ISO/IEC 18047--
6:2017, Clauses 4 and 5 shall be fulfilled.
Before a device under test is tested according to this document, it shall successfully pass ISO/IEC 18047--
6:2017, Clause 7.
6 Test methods with respectrelated to ISO/IEC 29167--21 interrogators and tags
6.1 Test map for optional features
Table 1Table 1 lists all optional features of this crypto suite and shall be used as a template to report the test
results. Furthermore, it is used to refer to the test requirements in 6.26.2.
© ISO/IEC 2025 – All rights reserved
ISO/IEC FDIS 19823-21:2025(en)
Table 1 — Test map for optional features
#Ite
To be tested for Test
m
Feature Additional requirement
supplied product? results
no.
Tag Shall be tested with the Authenticate command of
Authentication ISO/IEC 18000-63
Interrogator Shall be tested with the Authenticate command of
Authentication ISO/IEC 18000-63
Mutual Shall be tested with the Authenticate command of
Authentication ISO/IEC 18000-63
Secure Shall be tested with the SecureComm command of
Communication ISO/IEC 18000-63
6.2 Crypto suite requirements
6.2.1 General
This subclause refers to the requirements of ISO/IEC 29167--21.
6.2.2 Crypto suite requirements of ISO/IEC 29167--21:20182025, Clauses 14 to 8 and Annexes A
to C
All the requirements of ISO/IEC 29167--21:20182025, Clauses 14 to 8 and Annexes A to C shall be met and
conformance shall be verified by design only.
6.2.3 Crypto suite requirements of ISO/IEC 29167--21:20182025, Clauses 9 to 12 and Annex E
The requirements of ISO/IEC 29167-21:20182025, Clauses 9 to 12 and Annex E listed in Table 2Table 2 shall
be met. This document shall be read in conjunction with ISO/IEC 29167-21 to provide a full explanation of the
terms used.
Table 2 — Crypto suite requirements forof ISO/IEC 29167--21:2025, Clauses 9 to 12 and Annex E
Protocol
subclause of
Item Verified
ISO/IEC 2916 Requirements of ISO/IEC 29167-21: 2025 MOM/O Applies to
no. method
7-
a
21subclause
The Interrogator shall generate a random
1 9.3.2 Interrogator challenge (IChallenge-b/k) that is M Interrogator By design
carried in the TAM1 message.
The Tag shall accept the TAM1 message at any time
(unless occupied by internal processing and not
capable of receiving messages), i.e. upon receipt of
2 9.3.3 the message with valid parameters, the Tag shall M Tag By design
abort any cryptographic protocol that has not yet
been completed and shall remain in the Initial
state.
The Tag shall check if the Step is "00 ". If the value
of Step is different, the Tag shall return a "Not
3 9.3.3 M Tag Test _Pattern 2
Supported" error.
© ISO/IEC 2025 – All rights reserved
ISO/IEC FDIS 19823-21:2025(en)
Protocol
subclause of
Item Verified
ISO/IEC 2916 Requirements of ISO/IEC 29167-21: 2025 MOM/O Applies to
no. method
7-
a
21subclause
The Tag shall check if the RFU is "00 ". If the value
4 9.3.3 of RFU is different, the Tag shall return a "Not M Tag Test _Pattern 2
Supported" error.
The Tag shall check whether the values of BlockSize
and KeySize are supported by the Tag. If at least
5 9.3.3 M Tag By design
one of these checks is failed, the Tag shall return a
"Not Supported" error.
The Tag shall check whether the values of BlockSize
and KeySize are supported by Key.KeyID and that
Key.KeyID is authorized for use in Tag
6 9.3.3 M Tag By design
authentication. If either or both of these checks is
failed, the Tag shall return a "Not Supported" error.
The Tag shall check whether the parameter set PS
is supported. If the parameter set PS is not
7 9.3.3 M Tag Test _Pattern 2
supported, the Tag shall return a "Not Supported"
error.
Assuming that the TAM1 message is successfully
8 9.3.3 parsed by the Tag, the Tag shall prepare the TAM1 M Tag By design
response.
The Tag shall generate a random salt TRnd-b/k of
length r bits were r is given for the parameter set in
9 9.3.4 M Tag By design
Table 4.
The Tag shall use Key.KeyID and SIMON encryption
to form a b-bit string TResponse such that:
10 9.3.4 M Tag Test _Pattern 1
TResponse = SIMON-b/k-ENC ( Key.KeyID, C_TAM-
b/k ‖ TRnd-b/k ‖ IChallenge-b/k )
11 9.3.4 The Tag shall return TResponse to the Interrogator. M Tag By design
After receiving TAM1 response, the Interrogator
shall use Key.KeyID to compute the b-bit string S
where:
12 9.3.5 M Interrogator By design
S = SIMON-b/k-DEC ( Key.KeyID, TResponse ).
The Interrogator shall check that S[t-1:0] =
IChallenge-b/k.
The Interrogator shall send an initial message IAM1
to the Tag prompting the Tag to start a challenge-
response exchange.
13 9.4.2 O Interrogator By design
The Interrogator shall also indicate the variant of
SIMON to be used.
The Tag shall accept this message at any time
(unless occupied by internal processing and not
capable of receiving messages), i.e. upon receipt of
14 9.4.3 the message with valid parameters, the Tag shall O Tag By design
abort any cryptographic protocol that has not yet
been completed and shall remain in the Initial
state.
If Interrogator authentication is not supported on
15 9.4.3 O Tag By design
the Tag, i.e. if "012" is not a valid value for
© ISO/IEC 2025 – All rights reserved
ISO/IEC FDIS 19823-21:2025(en)
Protocol
subclause of
Item Verified
ISO/IEC 2916 Requirements of ISO/IEC 29167-21: 2025 MOM/O Applies to
no. method
7-
a
21subclause
AuthMethod, then the Tag shall return a "Not
Supported" error condition.
The Tag shall check if the Step is "002". If the value
16 9.4.3 of Step is different, the Tag shall return a "Not O Tag Test _Pattern 3
Supported" error.
The Tag shall check if the RFU is "002". If the value
of RFU is different, the Tag shall return a "Not
17 9.4.3 O Tag Test _Pattern 3
Supported" error.
The Tag shall check whether the values of BlockSize
and KeySize are supported by the Tag. If at least
18 9.4.3 O Tag By design
one of these checks is failed, the Tag shall return a
"Not Supported" error.
The Tag shall check whether the values of BlockSize
and KeySize are supported by Key.KeyID and that
19 9.4.3 Key.KeyID is authorized for use in Interrogator O Tag By design
authentication. If at least one of these checks is
failed, the Tag shall return a "Not Supported" error.
The Tag shall check whether the value of parameter
20 9.4.3 set PS is supported by the Tag. If not, the Tag shall O Tag Test _Pattern 3
return a "Not Supported" error.
If the IAM1 message is successfully parsed by the
21 9.4.3 O Tag By design
Tag, the Tag shall calculate the IAM1 response.
The Tag shall generate a random challenge
TChallenge-b/k of length t bits, where t is
22 9.4.4 O Tag By design
determined by the parameter set, and shall send
this to the Interrogator.
23 9.4.5 The Interrogator shall construct the IAM2 message. O Interrogator By design
The Interrogator shall form a b-bit string IResponse
such that:
IResponse = SIMON-b/k-DEC ( Key.KeyID, C_IAM-
24 9.4.6 O Interrogator Test _Pattern 4
b/k ‖ IRnd-b/k ‖ TChallenge-b/k ).
The Interrogator shall send IResponse to the Tag as
part of the IAM2 message; see Table 10.
The Tag shall only accept the IAM2 message when
25 9.4.7 O Tag By design
the cryptographic engine is in state PA1.
If Interrogator authentication is not supported on
the Tag, i.e. if "012" is not a valid value for
26 9.4.7 O Tag By design
AuthMethod, then the Tag shall return a "Not
Supported" error condition.
The Tag shall check if the Step is "012". If the value
27 9.4.7 of Step is different, the Tag shall return a "Not O Tag Test _Pattern 5
Supported" error.
The Tag shall check if the RFU is "00002". If the
value of RFU is different, the Tag shall return a "Not
28 9.4.7 O Tag Test _Pattern 5
Supported" error.
© ISO/IEC 2025 – All rights reserved
ISO/IEC FDIS 19823-21:2025(en)
Protocol
subclause of
Item Verified
ISO/IEC 2916 Requirements of ISO/IEC 29167-21: 2025 MOM/O Applies to
no. method
7-
a
21subclause
The Tag shall use Key.KeyID to compute the b-bit
string S where:
29 9.4.7 O Tag By design
S = SIMON-b/k-ENC ( Key.KeyID, IResponse ).
30 9.4.7 The Tag shall check that S[t-1:0] = TChallenge-b/k. O Tag By design
31 9.4.7 The Tag shall prepare IAM2 response. O Tag By design
The Tag shall return the value of TStatus to the
32 9.4.8 O Tag Test _Pattern 6
Interrogator.
If, under conditions laid out in the over-the-air
protocol, there is no response from the Tag or if the
33 9.4.9 returned value of TStatus is 0 , then the O Interrogator By design
Interrogator shall abandon the cryptographic
protocol.
The Interrogator shall generate a random
34 9.5.2 Interrogator challenge (IChallenge-b/k) that is O Interrogator By design
carried in the MAM1 message.
The Interrogator shall indicate the variant of
35 9.5.2 O Interrogator By design
SIMON to be used.
The Tag shall accept MAM1 message at any time
(unless occupied by internal processing and not
capable of receiving messages), i.e. upon receipt of
36 9.5.3 the message with valid parameters, the Tag shall O Tag By design
abort any cryptographic protocol that has not yet
been completed and shall remain in the Initial
state.
If Mutual authentication is not supported on the
Tag, i.e. if "10 " is not a valid value for AuthMethod,
37 9.5.3 O Tag By design
then the Tag shall return a "Not Supported" error
condition.
The Tag shall check if the Step is "00 ". If the value
38 9.5.3 of Step is different, the Tag shall return a "Not O Tag Test _Pattern 7
Supported" error.
The Tag shall check if the RFU is "00 ". If the value
39 9.5.3 of RFU is different, the Tag shall return a "Not O Tag Test _Pattern 7
Supported" error.
The Tag shall check whether the values of BlockSize
and KeySize are supported by the Tag. If at least
40 9.5.3 O Tag By design
one of these checks is failed, the Tag shall return a
"Not Supported" error.
The Tag shall check whether the values of BlockSize
and KeySize are supported by Key.KeyID and that
Key.KeyID is authorized for use in Interrogator-Tag
41 9.5.3 O Tag By design
mutual authentication. If at least one of these
checks is failed, the Tag shall return a "Not
Supported" error.
© ISO/IEC 2025 – All rights reserved
ISO/IEC FDIS 19823-21:2025(en)
Protocol
subclause of
Item Verified
ISO/IEC 2916 Requirements of ISO/IEC 29167-21: 2025 MOM/O Applies to
no. method
7-
a
21subclause
The Tag shall check whether the value of parameter
42 9.5.3 set PS is supported by the Tag. If not, the Tag shall O Tag By design
return a "Not Supported" error.
The Tag shall generate a random challenge
43 9.5.3 O Tag By design
TChallenge-b/k.
The Tag shall construct a b-bit string by
concatenating C_MAM-b/k with the (b-t-c) most
44 9.5.3 O Tag By design
significant bits of TChallenge-b/k and the entirety
of IChallenge-b/k.
The Tag shall use Key.KeyID to compute the b-bit
string S where:
45 9.5.3 S = SIMON-b/k-ENC ( Key.KeyID, C_MAM-b/k ‖ O Tag Test _Pattern 8
TChallenge-b/k [t-1:2t-b+c] ‖
IChallenge-b/k ).
After receiving MAM1 Response, the Interrogator
shall use Key.KeyID to compute the b-bit string T
where:
46 9.5.5 T = SIMON-b/k-DEC ( Key.KeyID, TResponse[b-1:0] O Interrogator By design
).
1. The Interrogator shall check that T[t-1:0] =
IChallenge-b/k.
If the cryptographic protocol has not been
abandoned, the Interrogator shall form a b-bit
string IResponse depending on the parameter set
PS as follows:
1. If PS = 00 then IResponse is equal to
SIMON-b/k-DEC ( Key.KeyID, C_MAM-b/k ‖ T[b-t-c-
1:0] ‖ T[b-c-1:t] ‖
TResponse[2t+c-1:b] ).
47 9.5.6 O Interrogator By design
2. If PS = 01 then IResponse is equal to T[b-c:t].
The Interrogator shall set SecureComm = 0001 if
secure communications as described in
SectionClause 10 will beis used after mutual
authentication is completed. Otherwise, the
Interrogator shall set SecureComm = 00002.
The Interrogator shall send IResponse and the
value of SecureComm to the Tag as part of the
MAM2 message.
The Tag shall only accept this message when the
48 9.5.7 O Tag By design
cryptographic engine is in the state PA2.
If Mutual authentication is not supported on the
Tag, i.e. if "10 " is not a valid value for AuthMethod,
49 9.5.7 O Tag By design
then the Tag shall return a "Not Supported" error
condition.
© ISO/IEC 2025 – All rights reserved
ISO/IEC FDIS 19823-21:2025(en)
Protocol
subclause of
Item Verified
ISO/IEC 2916 Requirements of ISO/IEC 29167-21: 2025 MOM/O Applies to
no. method
7-
a
21subclause
The Tag shall check if the Step is "01 ". If the value
50 9.5.7 of Step is different, the Tag shall return a "Not O Tag Test _Pattern 9
Supported" error.
The Tag shall check if the RFU is "0000 ". If the
51 9.5.7 value of RFU is different, the Tag shall return a "Not O Tag Test _Pattern 9
Supported" error.
If PS = 00 then the Tag computes the b-bit string S
= SIMON-b/k-ENC ( Key.KeyID, IResponse ).
SIMON-b/k-DEC ( Key.KeyID, C_MAM-b/k ‖ T[b-t-c-
52 9.5.7 O Tag Test _Pattern 10
1:0] ‖ T[b-c-1:t] ‖
TResponse[2t+c-b-1:0] ).
The Tag shall check if S[t-1:0] = TChallenge-b/k.
If PS = 012, then the Tag shall check whether S =
53 9.5.7 O Tag Test _Pattern 10
TChallenge-b/k.
If TStatus = 12 and SecureComm = 1h, the Tag shall
generate a random string N . The Tag shall further
T
54 9.5.7 O Tag Test _Pattern 10
indicate using KeyID which key shall be used for
the subsequent secure communication session.
If, under conditions laid out in the over-the-air
protocol, there is no response from the Tag or if the
returned value of TStatus is 0 then the
55 9.5.9 2 O Interrogator By design
Interrogator shall abandon the cryptographic
protocol.
If the response is encapsulated, then it shall be
encapsulated as described in this crypto suite. A
56 10.1 O Tag By design
Tag shall only encapsulate the response to an
encapsulated command.
If a secure communication session is required, the
57 10.2 session shall be launched by the Interrogator after O Interrogator By design
a successful mutual authentication.
SEC shall only be used after mutual authentication
Interrogator
has been established and it guarantees either the
58 10.3.1 O By design
confidentiality and/or authenticity of the payload P
Tag
being encapsulated, or both.
To send a command as an encapsulated payload P,
the Interrogator shall perform the following steps:
a) The Interrogator shall verify that TStatus is 1 .
If not, the Interrogator shall abandon the
encapsulation process.
b) The Interrogator shall identify the key
59 10.3.2 Key.KeyID to be used. O Interrogator By design
c) The Interrogator shall construct the initial
value of the (b-16)-bit string N as N = N ‖
T
TChallenge.
© ISO/IEC 2025 – All rights reserved
ISO/IEC FDIS 19823-21:2025(en)
Protocol
subclause of
Item Verified
ISO/IEC 2916 Requirements of ISO/IEC 29167-21: 2025 MOM/O Applies to
no. method
7-
a
21subclause
d) The Interrogator shall choose the length
T_Length for the authentication token T.
e) The Interrogator shall specify if the payload is
authenticated or both encrypted and
authenticated. If authentication without
encryption is required, then the Interrogator
shall set Enc = 0. If both encryption and
authentication are required, then the
Interrogator shall set Enc = 1.
1. The Interrogator shall verify that TStatus is 1 .
If not, the Interrogator shall abandon the
encapsulation process.
2. The Interrogator shall identify the key
Key.KeyID to be used.
3. The Interrogator shall construct the initial
value of the (b-16)-bit string N as N = N ‖
T
TChallenge.
4. The Interrogator shall choose the length
T_Length for the authentication token T.
5. The Interrogator shall specify if the payload is
authenticated or both encrypted and
authenticated. If authentication without
encryption is required, then the Interrogator
shall set Enc = 0. If both encryption and
authentication are required, then the
Interrogator shall set Enc = 1.
59 10.3.2 O Interrogator By design
f) 6. The Interrogator shall specify if the
payload parameters should be protected. If
parameter protection is required, then the
Interrogator shall set Protect = 1. If parameter
protection is not required, then the
Interrogator shall set Protect = 0.
g) 7. The Interrogator shall specify
whether the Tag response is to be in the clear,
authenticated, or encrypted and authenticated.
8. The Interrogator shall construct a string X
where |X| = 0 or |X| = 8. If Protect = 0 then X =
∅. If Protect = 1 then X = Response ‖ Enc ‖
Protect ‖ 002.
9. The Interro
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.
Loading comments...