Information technology -- Conformance test methods for security service crypto suites

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é

General Information

Status
Published
Publication Date
20-May-2019
Current Stage
6060 - International Standard published
Start Date
27-Apr-2019
Completion Date
21-May-2019
Ref Project

Buy Standard

Standard
ISO/IEC 19823-21:2019 - Information technology -- Conformance test methods for security service crypto suites
English language
20 pages
sale 15% off
Preview
sale 15% off
Preview

Standards Content (sample)

INTERNATIONAL ISO/IEC
STANDARD 19823-21
First edition
2019-05
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
Reference number
ISO/IEC 19823-21:2019(E)
ISO/IEC 2019
---------------------- Page: 1 ----------------------
ISO/IEC 19823-21:2019(E)
COPYRIGHT PROTECTED DOCUMENT
© ISO/IEC 2019

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
Fax: +41 22 749 09 47
Email: copyright@iso.org
Website: www.iso.org
Published in Switzerland
ii © ISO/IEC 2019 – All rights reserved
---------------------- Page: 2 ----------------------
ISO/IEC 19823-21:2019(E)
Contents Page

Foreword ........................................................................................................................................................................................................................................iv

Introduction ..................................................................................................................................................................................................................................v

1 Scope ................................................................................................................................................................................................................................. 1

2 Normative references ...................................................................................................................................................................................... 1

3 Terms, definitions, symbols and abbreviated terms ....................................................................................................... 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 with respect 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:2018, Clauses 1 to 8 and

Annexes A to C ........................................................................................................................................... ......................... 3

6.2.3 Crypto suite requirements of ISO/IEC 29167-21:2018, Clauses 9 to 12

and Annex E.......................................................................................................................................................................... 3

6.3 Test patterns ..........................................................................................................................................................................................13

6.3.1 General...................................................................................................................................................................................13

6.3.2 Test_Pattern 1 ..................................................................................................................................................................14

6.3.3 Test_Pattern 2 ..................................................................................................................................................................14

6.3.4 Test_Pattern 3 ..................................................................................................................................................................15

6.3.5 Test_Pattern 4 ..................................................................................................................................................................15

6.3.6 Test_Pattern 5 ..................................................................................................................................................................16

6.3.7 Test_Pattern 6 ..................................................................................................................................................................16

6.3.8 Test_Pattern 7 ..................................................................................................................................................................17

6.3.9 Test_Pattern 8 ..................................................................................................................................................................17

6.3.10 Test_Pattern 9 ..................................................................................................................................................................18

6.3.11 Test_Pattern 10 ...............................................................................................................................................................18

6.3.12 Test_Pattern 11 ...............................................................................................................................................................19

Bibliography .............................................................................................................................................................................................................................20

© ISO/IEC 2019 – All rights reserved iii
---------------------- Page: 3 ----------------------
ISO/IEC 19823-21:2019(E)
Foreword

ISO (the International Organization for Standardization) and IEC (the International Electrotechnical

Commission) form the specialized system for worldwide standardization. National bodies that

are members of ISO or IEC participate in the development of International Standards through

technical committees established by the respective organization to deal with particular fields of

technical activity. ISO and IEC technical committees collaborate in fields of mutual interest. Other

international organizations, governmental and non-governmental, in liaison with ISO and IEC, also

take part in the work.

The procedures used to develop this document and those intended for its further maintenance are

described in the ISO/IEC Directives, Part 1. In particular, the different approval criteria needed for

the different types of document should be noted. This document was drafted in accordance with the

editorial rules of the ISO/IEC Directives, Part 2 (see www .iso .org/directives).

Attention is drawn to the possibility that some of the elements of this document may be the subject

of patent rights. ISO and IEC shall not be held responsible for identifying any or all such patent

rights. Details of any patent rights identified during the development of the document will be in the

Introduction and/or on the ISO list of patent declarations received (see www .iso .org/patents) or the

IEC list of patent declarations received (see http: //patents .iec .ch).

Any trade name used in this document is information given for the convenience of users and does not

constitute an endorsement.

For an explanation of the voluntary nature of standards, the meaning of ISO specific terms and

expressions related to conformity assessment, as well as information about ISO's adherence to the

World Trade Organization (WTO) principles in the Technical Barriers to Trade (TBT) see www .iso

.org/iso/foreword .html.

This document was prepared by Joint Technical Committee ISO/IEC JTC 1, Information technology,

Subcommittee SC 31, Automatic identification and data capture techniques.
A list of all parts in the ISO/IEC 19823 series can be found on the ISO website.

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.
iv © ISO/IEC 2019 – All rights reserved
---------------------- Page: 4 ----------------------
ISO/IEC 19823-21:2019(E)
Introduction

The ISO/IEC 29167 series describes security services as applicable for the ISO/IEC 18000 series. The

various parts of ISO/IEC 29167 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 ISO/IEC 29167 is related to ISO/IEC 18000.

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 ISO/IEC 18000 or ISO/IEC 29167, all related parts of ISO/IEC 18047 and

ISO/IEC 19823 apply.

NOTE 1 The conformance test requirements of ISO/IEC 18000-6, ISO/IEC 18000-61, ISO/IEC 18000-62, ISO/

IEC 18000-63, ISO/IEC 18000-64 are currently all in ISO/IEC 18047-6.

This document describes the test methods for the SIMON crypto suite as standardized in ISO/

IEC 29167-21.

NOTE 2 Test methods for interrogator and tag performance are covered by ISO/IEC 18046 (all parts).

© ISO/IEC 2019 – All rights reserved v
---------------------- Page: 5 ----------------------
INTERNATIONAL STANDARD ISO/IEC 19823-21:2019(E)
Information technology — Conformance test methods for
security service crypto suites —
Part 21:
Crypto suite SIMON
1 Scope

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.

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 960 MHz Type C

ISO/IEC 18047-6:2017, Information technology — Radio frequency identification device conformance test

methods — Part 6: Test methods for air interface communications at 860 MHz to 960 MHz

ISO/IEC 19762, Information technology — Automatic identification and data capture (AIDC) techniques —

Harmonized vocabulary

ISO/IEC 29167-21:2018, Information technology — Automatic identification and data capture

techniques — Part 21: Crypto suite SIMON security services for air interface communications

3 Terms, definitions, symbols and abbreviated terms

For the purposes of this document, the terms, definitions, symbols and abbreviated terms given in ISO/

IEC 19762 and in ISO/IEC 29167-21 apply.

ISO and IEC maintain terminological databases for use in standardization at the following addresses:

— ISO Online browsing platform: available at https: //www .iso .org/obp
— IEC Electropedia: available at http: //www .electropedia .org/
© ISO/IEC 2019 – All rights reserved 1
---------------------- Page: 6 ----------------------
ISO/IEC 19823-21:2019(E)
4 Test methods
4.1 General

This document describes test methods for ISO/IEC 29167-21. As parts of ISO/IEC 19823 are always

tested in relation to ISO/IEC 18047, duplication of information requirements and specifications is meant

to be avoided.

Clause 5 defines elements that are covered in the respective part of ISO/IEC 18047.

Clause 6 defines elements that are not covered by ISO/IEC 18047 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 verification of design parameters and/or theoretical analysis is

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 requirements of ISO/IEC 18047-6:2017, Clauses 4

and 5 shall be fulfilled.

Before a DUT is tested according to this document, it shall successfully pass ISO/IEC 18047-6:2017,

Clause 7.
6 Test methods with respect 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.
2 © ISO/IEC 2019 – All rights reserved
---------------------- Page: 7 ----------------------
ISO/IEC 19823-21:2019(E)
Table 1 — Test map for optional features
To be tested for
Test
# Feature Additional requirement supplied prod-
results
uct?
Shall be tested with the Authenticate command of
1 TA
ISO/IEC 18000-63
Shall be tested with the Authenticate command of
2 IA
ISO/IEC 18000-63
Shall be tested with the Authenticate command of
3 MA
ISO/IEC 18000-63
Secure Communi- Shall be tested with the SecureComm command of
cation ISO/IEC 18000-63
6.2 Crypto suite requirements
6.2.1 General
This clause refers to the requirements of ISO/IEC 29167-21.

6.2.2 Crypto suite requirements of ISO/IEC 29167-21:2018, Clauses 1 to 8 and Annexes A to C

All the requirements of ISO/IEC 29167-21:2018, Clauses 1 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:2018, Clauses 9 to 12 and Annex E

The requirements of ISO/IEC 29167-21:2018, 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 for ISO/IEC 29167-21
Protocol
a b
Item Requirement MO Applies to How verified
subclause
The Interrogator shall generate a random Inter-

1 9.3.2 rogator challenge (IChallenge-b/k) that is carried M Interrogator By design

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
2 9.3.3 receipt of the message with valid parameters, M Tag By design
the 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
3 9.3.3 value of Step is different, the Tag shall return a M Tag Test_Pattern 2
"Not Supported" error.
The Tag shall check if the RFU is "00 ". If the
4 9.3.3 value of RFU is different, the Tag shall return a M Tag Test_Pattern 2
"Not Supported" error.
All clause, subclause and table references are to ISO/IEC 29167-21.

M: mandatory; items marked with "M" are mandatory and shall be tested for all devices.

O: optional; items marked with “O” are optional and shall be tested only for devices that support the feature that is indicated

by the requirement.
© ISO/IEC 2019 – All rights reserved 3
---------------------- Page: 8 ----------------------
ISO/IEC 19823-21:2019(E)
Table 2 (continued)
Protocol
a b
Item Requirement MO Applies to How verified
subclause
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.
The Tag shall check whether the values of Block-
Size and KeySize are supported by Key.KeyID and
6 9.3.3 that Key.KeyID is authorized for use in Tag authen- M Tag By design
tication. 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 Support-
ed" error.
Assuming that the TAM1 message is successful-
8 9.3.3 ly parsed by the Tag, the Tag shall prepare the M Tag By design
TAM1 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 Interro-
11 9.3.4 M Tag By design
gator.
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
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
14 9.4.3 of the message with valid parameters, the Tag O Tag By design
shall 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
15 9.4.3 O Tag By design
AuthMethod, then the Tag shall return a "Not
Supported" error condition.
All clause, subclause and table references are to ISO/IEC 29167-21.

M: mandatory; items marked with "M" are mandatory and shall be tested for all devices.

O: optional; items marked with “O” are optional and shall be tested only for devices that support the feature that is indicated

by the requirement.
4 © ISO/IEC 2019 – All rights reserved
---------------------- Page: 9 ----------------------
ISO/IEC 19823-21:2019(E)
Table 2 (continued)
Protocol
a b
Item Requirement MO Applies to How verified
subclause
The Tag shall check if the Step is "00 ". If the
16 9.4.3 value of Step is different, the Tag shall return a O Tag Test_Pattern 3
"Not Supported" error.
The Tag shall check if the RFU is "00 ". If the
17 9.4.3 value of RFU is different, the Tag shall return a O Tag Test_Pattern 3
"Not 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.
The Tag shall check whether the values of
BlockSize and KeySize are supported by Key.
KeyID and that Key.KeyID is authorized for use
19 9.4.3 O Tag By design
in Interrogator 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
TChallenge-b/k of length t bits, where t is deter-
22 9.4.4 O Tag By design
mined by the parameter set, and shall send this
to the Interrogator.
The Interrogator shall construct the IAM2
23 9.4.5 O Interrogator By design
message.
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
25 9.4.7 O Tag By design
when 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
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 "01 ". If the
27 9.4.7 value of Step is different, the Tag shall return a O Tag Test_Pattern 5
"Not 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 ).
All clause, subclause and table references are to ISO/IEC 29167-21.

M: mandatory; items marked with "M" are mandatory and shall be tested for all devices.

O: optional; items marked with “O” are optional and shall be tested only for devices that support the feature that is indicated

by the requirement.
© ISO/IEC 2019 – All rights reserved 5
---------------------- Page: 10 ----------------------
ISO/IEC 19823-21:2019(E)
Table 2 (continued)
Protocol
a b
Item Requirement MO Applies to How verified
subclause
The Tag shall check that S[t-1:0] = TChal-
30 9.4.7 O Tag By design
lenge-b/k.
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

33 9.4.9 if the returned value of TStatus is 0 , then the O Interrogator By design

Interrogator shall abandon the cryptographic
protocol.
The Interrogator shall generate a random Inter-

34 9.5.2 rogator challenge (IChallenge-b/k) that is carried O Interrogator By design

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
36 9.5.3 of the message with valid parameters, the Tag O Tag By design
shall 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
38 9.5.3 value of Step is different, the Tag shall return a O Tag Test_Pattern 7
"Not Supported" error.
The Tag shall check if the RFU is "00 ". If the
39 9.5.3 value of RFU is different, the Tag shall return a O Tag Test_Pattern 7
"Not 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 TCh-
43 9.5.3 O Tag By design
allenge-b/k.
All clause, subclause and table references are to ISO/IEC 29167-21.

M: mandatory; items marked with "M" are mandatory and shall be tested for all devices.

O: optional; items marked with “O” are optional and shall be tested only for devices that support the feature that is indicated

by the requirement.
6 © ISO/IEC 2019 – All rights reserved
---------------------- Page: 11 ----------------------
ISO/IEC 19823-21:2019(E)
Table 2 (continued)
Protocol
a b
Item Requirement MO Applies to How verified
subclause
The Tag shall construct a b-bit string by concat-
enating 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: 2 t -b+c] ‖
IChallenge-b/k ).
After receiving MAM1 Response, the Interro-
gator shall use Key.KeyID to compute the b-bit
string T where:
46 9.5.5 T = SIMON-b/k-DEC ( Key.KeyID, TRespon- O Interrogator By design
se[b-1:0] ).
1. The Interrogator shall check that T[t-1:0] =
IChallenge-b/k.
If the cryptographic protocol has not been aban-
doned, 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 Section
10 will be used after mutual authentication is
completed. Otherwise, the Interrogator shall set
SecureComm = 0000 .
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 AuthMeth-
49 9.5.7 O Tag By design
od, then the Tag shall return a "Not Supported"
error condition.
The Tag shall check if the Step is "01 ". If the
50 9.5.7 value of Step is different, the Tag shall return a O Tag Test_Pattern 9
"Not 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 O Tag Test_Pattern 9
"Not Supported" error.
All clause, subclause and table references are to ISO/IEC 29167-21.

M: mandatory; items marked with "M" are mandatory and shall be tested for all devices.

O: optional; items marked with “O” are optional and shall be tested only for devices that support the feature that is indicated

by the requirement.
© ISO/IEC 2019 – All rights reserved 7
---------------------- Page: 12 ----------------------
ISO/IEC 19823-21:2019(E)
Table 2 (continued)
Protocol
a b
Item Requirement MO Applies to How verified
subclause
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-
52 9.5.7 O Tag Test_Pattern 10
t-c-1:0] ‖ T[b-c-1:t] ‖
TResponse[2t+c-b-1:0] ).
The Tag shall check if S[t-1:0] =
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.