ISO/IEC 19823-10:2017
(Main)Information technology — Conformance test methods for security service crypto suites — Part 10: Crypto suite AES-128
Information technology — Conformance test methods for security service crypto suites — Part 10: Crypto suite AES-128
ISO/IEC 19823-10:2017 describes test methods for determining the conformance of security crypto suites defined in ISO/IEC 29167‑10. ISO/IEC 19823-10:2017 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 intended to be applied exclusively related to RFID tags and interrogators defined in the ISO/IEC 18000 series using ISO/IEC 29167‑10.
Technologies de l'information — Méthodes d'essai de conformité pour les suites cryptographiques des services de sécurité — Partie 10: Suite cryptographique AES-128
General Information
Relations
Standards Content (Sample)
INTERNATIONAL ISO/IEC
STANDARD 19823-10
First edition
2017-11
Information technology —
Conformance test methods for
security service crypto suites —
Part 10:
Crypto suite AES-128
Technologies de l'information — Méthodes d'essai de conformité pour
les suites cryptographiques des services de sécurité —
Partie 10: Suite cryptographique AES-128
Reference number
ISO/IEC 19823-10:2017(E)
©
ISO/IEC 2017
---------------------- Page: 1 ----------------------
ISO/IEC 19823-10:2017(E)
COPYRIGHT PROTECTED DOCUMENT
© ISO/IEC 2017, Published in Switzerland
All rights reserved. Unless otherwise specified, 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
Ch. de Blandonnet 8 • CP 401
CH-1214 Vernier, Geneva, Switzerland
Tel. +41 22 749 01 11
Fax +41 22 749 09 47
copyright@iso.org
www.iso.org
ii © ISO/IEC 2017 – All rights reserved
---------------------- Page: 2 ----------------------
ISO/IEC 19823-10:2017(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 methods in respect to the ISO/IEC 18000 parts . 2
5.1 Test requirements for ISO/IEC 18000-3 interrogators and tags . 2
5.2 Test requirements for ISO/IEC 18000-63 interrogators and tags . 3
6 Test methods in respect to the ISO/IEC 29167-10 interrogators and tags .3
6.1 Test map for optional features . 3
6.2 Additional parameters required as input for the test . 3
6.3 Crypto suite requirements . 4
6.3.1 Crypto suite requirements of ISO/IEC 29167‑10:2015, Clauses 1 to 6 . 4
6.3.2 Crypto suite requirements of ISO/IEC 29167‑10:2015, Clauses 7 to 12. 4
6.3.3 Crypto suite requirements of ISO/IEC 29167‑10:2015, Annex A . .15
6.3.4 Crypto suite requirements of ISO/IEC 29167‑10:2015, Annex E .16
6.4 Test patterns .19
6.4.1 Test patterns for ISO/IEC 18000-3 mode 1 .19
6.4.2 Test patterns for ISO/IEC 18000-3 mode 3 .19
6.4.3 Test patterns for ISO/IEC 18000-63 .19
Bibliography .23
© ISO/IEC 2017 – All rights reserved iii
---------------------- Page: 3 ----------------------
ISO/IEC 19823-10:2017(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. In the field of information technology, ISO and IEC have established a joint technical committee,
ISO/IEC JTC 1.
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).
Any trade name used in this document is information given for the convenience of users and does not
constitute an endorsement.
For an explanation on 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 the following
URL: www.iso.org/iso/foreword.html.
This document was prepared by 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 19823 series can be found on the ISO website.
iv © ISO/IEC 2017 – All rights reserved
---------------------- Page: 4 ----------------------
ISO/IEC 19823-10:2017(E)
Introduction
The ISO/IEC 29167 series of standards describes security services as applicable for the
ISO/IEC 18000 series of standards. The various parts of ISO/IEC 29167 describe crypto suites that are
optional extensions to the ISO/IEC 18000 series air interfaces.
The ISO/IEC 19823 series of standards describes the conformance test methods for security service
crypto suites. The ISO/IEC 19823 series is related to the ISO/IEC 18047 series of standards, 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, then 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 AES‑128 crypto suite as standardized in
ISO/IEC 29167-10
NOTE 2 Test methods for interrogator and tag performance are covered by the multiple parts of ISO/IEC 18046.
© ISO/IEC 2017 – All rights reserved v
---------------------- Page: 5 ----------------------
INTERNATIONAL STANDARD ISO/IEC 19823-10:2017(E)
Information technology — Conformance test methods for
security service crypto suites —
Part 10:
Crypto suite AES-128
1 Scope
This document describes test methods for determining the conformance of security crypto suites
defined in ISO/IEC 29167‑10.
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 intended to be applied exclusively related to
RFID tags and interrogators defined in the ISO/IEC 18000 series using ISO/IEC 29167‑10.
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 18047-3:2011, Information technology — Radio frequency identification device conformance test
methods — Part 3: Test methods for air interface communications at 13,56 MHz
ISO/IEC 18047-6:2012, 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 (all parts), Information technology — Automatic identification and data capture (AIDC)
techniques — Harmonized vocabulary
ISO/IEC 29167-10:2015, Information technology — Automatic identification and data capture
techniques — Part 10: Crypto suite AES-128 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‑
10 apply.
ISO and IEC maintain terminological databases for use in standardization at the following addresses:
— IEC Electropedia: available at https://www.electropedia.org/
— ISO Online browsing platform: available at https://www.iso.org/obp
© ISO/IEC 2017 – All rights reserved 1
---------------------- Page: 6 ----------------------
ISO/IEC 19823-10:2017(E)
3.2 Symbols
For the purposes of this document, the symbols given in ISO/IEC 19762 apply.
3.3 Abbreviated terms
For the purposes of this document, the abbreviated terms given in ISO/IEC 19762 apply.
4 Test methods
4.1 General
This clause describes the general test methods for ISO/IEC 29167-10. As the parts of ISO/IEC 19823 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 assumed to be covered in the respective ISO/IEC 18047 part and
therefore, shall not be addressed in an ISO/IEC 19823 part. Only if ISO/IEC 18047 does not define
them, then they may be defined in ISO/IEC 19823, although a revision of ISO/IEC 18047 should be the
preferred option.
Clause 6 defines elements that are not expected to be covered by ISO/IEC 18047 and therefore, shall be
addressed in the respective ISO/IEC 19823 part.
4.2 By demonstration
“By demonstration” means laboratory testing of one or, if required for statistical reasons, multiple
products, processes or services to ensure compliance.
A test laboratory that meets 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 by this
document. The detailed test plan is at the discretion of the test laboratory.
4.3 By design
“By design” means design parameters and/or theoretical analysis that ensure compliance. A vendor
submitting a component or system for compliance testing 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 respect to the ISO/IEC 18000 parts
5.1 Test requirements for ISO/IEC 18000-3 interrogators and tags
The following mandatory requirements and applicable optional requirements of ISO/IEC 18047‑3:2011
shall be fulfilled:
— 5.2 Default conditions applicable to the test methods
2 © ISO/IEC 2017 – All rights reserved
---------------------- Page: 7 ----------------------
ISO/IEC 19823-10:2017(E)
Before a DUT is tested according to this document, it shall successfully pass the following prerequisite
from ISO/IEC 18047-3:2011:
— 5.3 Conformance tests for ISO/IEC 18000-3 Mode 1
5.2 Test requirements for ISO/IEC 18000-63 interrogators and tags
The following mandatory requirements and applicable optional requirements of ISO/IEC 18047‑6:2012
shall be fulfilled:
— 3.4 Default conditions applicable to the test methods
— Clause 4 Set up of test equipment
Before a DUT is tested according to this document, it shall successfully pass the following prerequisite
from ISO/IEC 18047-6:2012:
— Clause 7 Conformance tests for ISO/IEC 18000-63
6 Test methods in respect to the ISO/IEC 29167-10 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 7.3.
Table 1 — Test map for optional features
Mark items
to be tested
# Feature Additional requirements Test results
for supplied
product
1 TAM2 Shall be tested with the Authenticate com-
mand of the declared ISO/IEC 18000 part
1.1 Memory profiles and MPI Shall be tested with the Authenticate com-
mand of the declared memory profiles and
every key
MAX_Profiles=Number of memory profiles
MAX_KeyID=Number of keys supported
1.2 ProtMode=0000 Shall be tested with the Authenticate com-
b
mand of the declared ISO/IEC 18000 part
1.3 ProtMode=0001 Shall be tested with the Authenticate com-
b
mand of the declared ISO/IEC 18000 part
1.4 ProtMode=0010 Shall be tested with the Authenticate com-
b
mand of the declared ISO/IEC 18000 part
1.5 ProtMode=0011 Shall be tested with the Authenticate com-
b
mand of the declared ISO/IEC 18000 part
Table 3 lists all crypto suite requirements that shall be tested in dependence of the features of Table 1
as supported by the DUT. Items marked with M are mandatory and shall be tested for each DUT.
6.2 Additional parameters required as input for the test
Table 2 lists all additional test parameters of this crypto suite.
© ISO/IEC 2017 – All rights reserved 3
---------------------- Page: 8 ----------------------
ISO/IEC 19823-10:2017(E)
Table 2 — Additional test parameters
# Feature Additional requirement Value
1 Maximum BlockSize Shall be provided in order to ensure that only test results for
supported parameters are taking into consideration.
6.3 Crypto suite requirements
This clause contains all requirements of ISO/IEC 29167-10.
6.3.1 Crypto suite requirements of ISO/IEC 29167-10:2015, Clauses 1 to 6
All the requirements of ISO/IEC 29167‑10:2015, Clauses 1 to 6 are mandatory, inherently by design only.
6.3.2 Crypto suite requirements of ISO/IEC 29167-10:2015, Clauses 7 to 12
Table 3 contains all requirements of ISO/IEC 29167-10:2015, Clauses 7 to 12.
The column MO (Mandatory/Optional) has the following content:
— 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.
Table 3 — Crypto suite requirements
Protocol
Item Requirement MO Applies to How verified
subclause
0010 7 MAC_key[127:0] Variable O Interroga- By design
that shall contain the key that tor
will be used for cryptograph- Tag
ic integrity protection.
0020 8 A transition to Initial state M Tag By design
shall also cause a reset of all
variables used by the crypto
suite.
0030 9 Implementations of this M Tag By design
crypto suite shall ensure that
all memory used for interme-
diate results is cleared after
each operation (message-re-
sponse pair) and after reset.
4 © ISO/IEC 2017 – All rights reserved
---------------------- Page: 9 ----------------------
ISO/IEC 19823-10:2017(E)
Table 3 (continued)
Protocol
Item Requirement MO Applies to How verified
subclause
0040 10.2 The crypto suite shall parse M Tag By demonstration using test pat-
the Messages and process the terns for ISO/IEC 18000-3 mode 1
data based on the value of Au-
This subclause is reserved to
thMethod, which is the first
define the test patterns for ISO/
parameter of all Messages.
IEC 18000-3 mode 1.
Test patterns for ISO/
IEC 18000-3 mode 3
This subclause is reserved to
define the test patterns for ISO/
IEC 18000-3 mode 3.
Test patterns for ISO/
IEC 18000-63
This subclause defines the test
patterns for ISO/IEC 18000-63.
That document also contains the
descriptions of the terms used in
the test patterns.
Miller2 stands for "Miller Subcar-
rier Sequence M=2"
Miller4 stands for "Miller Subcar-
rier Sequence M=4"
Test pattern 1
0050 10.2 The following sections of M Tag By demonstration using test
this document describe the patterns for ISO/IEC 18000-33
formatting of Message and mode 1
Response for Tag Authenti-
This subclause is reserved to
cation. AuthMethod shall be
define the test patterns for ISO/
“00 ” for Tag Authentication.
b
IEC 18000-3 mode 1.
Test patterns for ISO/
IEC 18000-3 mode 3
This subclause is reserved to
define the test patterns for ISO/
IEC 18000-3 mode 3.
Test patterns for ISO/
IEC 18000-63
This subclause defines the test
patterns for ISO/IEC 18000-63.
That document also contains the
descriptions of the terms used in
the test patterns.
Miller2 stands for "Miller Subcar-
rier Sequence M=2"
Miller4 stands for "Miller Subcar-
rier Sequence M=4"
Test pattern 1
© ISO/IEC 2017 – All rights reserved 5
---------------------- Page: 10 ----------------------
ISO/IEC 19823-10:2017(E)
Table 3 (continued)
Protocol
Item Requirement MO Applies to How verified
subclause
0060 10.2 If AuthMethod=“00 ” the M Tag By demonstration using test pat-
b
Tag shall parse Message as terns for ISO/IEC 18000-3 mode 1
described in 10.3.
This subclause is reserved to
define the test patterns for ISO/
IEC 18000-3 mode 1.
Test patterns for ISO/
IEC 18000-3 mode 3
This subclause is reserved to
define the test patterns for ISO/
IEC 18000-3 mode 3.
Test patterns for ISO/
IEC 18000-63
This subclause defines the test
patterns for ISO/IEC 18000-63.
That document also contains the
descriptions of the terms used in
the test patterns.
Miller2 stands for "Miller Subcar-
rier Sequence M=2"
Miller4 stands for "Miller Subcar-
rier Sequence M=4"
Test pattern 1
0070 10.2 If AuthMethod=“01 ”, “10 ” M Tag By demonstration using
b b
or “11 ” then the Tag shall re- Test pattern 2
b
turn a “Not Supported” error
condition and shall transition
to the Initial state.
0080 10.3 The functionality shall be M Tag By design
implemented by means of a
challenge-response exchange.
Tag authentication only shall
be implemented in TAM1 and
Tag authentication with the
addition of custom data shall
be implemented as TAM2 (see
Figure 2).
0090 10.3 The crypto suite shall parse M Tag By demonstration using
the TAM Messages and pro- Test pattern 3
cess the data based on the
value of CustomData, which is
the second parameter of both
TAM Messages. The Messages
for Tag Authentication with-
out and with custom data
shall be distinguished by Cus-
tomData. CustomData shall
be “0 ” for Tag Authentication
b
without custom data and “1 ”
b
for Tag Authentication with
custom data.
0100 10.3 If CustomData=“0 ” the Tag M Tag By demonstration using
b
shall parse the TAM1 Mes- Test pattern 3
sage as described in 10.3.2.
6 © ISO/IEC 2017 – All rights reserved
---------------------- Page: 11 ----------------------
ISO/IEC 19823-10:2017(E)
Table 3 (continued)
Protocol
Item Requirement MO Applies to How verified
subclause
0110 10.3 If CustomData=“1 ” the Tag O-1 Tag By demonstration using
b
shall parse the TAM2 Mes- Test pattern 4
sage as described in 10.3.4.
0120 10.3.2 For Tag authentication the In- M Interroga- By demonstration using Test pat-
terrogator shall generate an tor tern 1 twice with different values
80-bit random TAM1 Interro- Tag of KeyID and checking that the
gator challenge and include response contains the appropri-
that in the TAM1 message. ate MAC in both cases.
The TAM1 message shall also
include the reference KeyID
to select an encryption key
in the Key Management Table
(see Clause 12).
— KeyID: defines the key
that shall be used for TAM1.
0130 10.3.2 The Tag shall accept this M Tag By demonstration sending two
message in any state. If the different TAM1 messages, one
parameters of the message after each other, without waiting
are valid, then the Tag shall for the response to the first
transition to the Initial state; TAM1 message. Check if the
thereby aborting any cryp- response to the second TAM1
tographic protocol that has message is correct.
not yet been completed.
0140 10.3.2 If the length of the TAM1 mes- M Tag By demonstration using a se-
sage <> 96 bits then the Tag quence of Test pattern 1, with
shall return an “Other Error” different values for IChallenge_
error condition and shall TAM1.
transition to the Initial state.
First time IChallenge_TAM1 shall
be “D53600FAA9B4C1965CC3 ”
h
and the response shall be accord-
ing to Test pattern 1.
Second time IChallenge_TAM1
shall be “D53600FAA9B4C1965C”
(88 bits) and the response shall
be “Other Error”.
Third time IChal-
lenge_TAM1 shall be
“D53600FAA9B4C1965CCFF ”
h
(104 bits) and the response shall
be “Other Error”.
0150 10.3.2 If TAM1_RFU <> “00000 ” M Tag By demonstration using a se-
b
then the Tag shall return a quence of Test pattern 1, with two
“Not Supported” error con- different values for TAM1_RFU.
dition and shall transition to
First time TAM1_RFU shall be
the Initial state.
“0x00000 ” and the response
b
shall be according to Test pat-
tern 1.
Second time TAM1_RFU shall
be “0x00001 ” and the response
b
shall be “Other Error”.
© ISO/IEC 2017 – All rights reserved 7
---------------------- Page: 12 ----------------------
ISO/IEC 19823-10:2017(E)
Table 3 (continued)
Protocol
Item Requirement MO Applies to How verified
subclause
0160 10.3.2 If the Tag does not support M Tag By demonstration using
key[KeyID].ENC_key then it Test pattern 5
shall return a “Not Support-
ed” error condition and shall
transition to the Initial state.
0170 10.3.3 If all verifications are M Tag By demonstration using
successful, then the Tag Test pattern 3
shall generate the random
data TRnd_TAM1 (32 bits)
and encrypt the challenge
IChallenge_TAM1 of the In-
terrogator using Key[KeyID].
ENC_key, after first prefixing
the constant C_TAM1 (16
bits) and the random data
TRnd_TAM1.
0180 10.3.2 After returning the TAM1 M Tag By demonstration using Test pat-
Response (TResponse) the tern 1 twice and verifying two
Tag shall remain in the Ini- correct responses.
tial state.
0190 10.3.4 The Interrogator (or the M Interrogator By demonstration using
external application con- Test pattern 3
trolling the Interrogator)
decrypts the TAM1 Response
(TResponse) and shall
verify whether: C_TAM1 and
IChallenge_TAM1 have the
correct value. If the values
are correct, then the Tag can
be considered as authentic.
0200 10.3.5 TAM2 shall be used for Tag O-1.1 Interroga- By design
Authentication if the Tag tor Tag
needs to return part of its
memory as custom data that
may be protected (protection
of integrity and authenticity)
and/or encrypted (confi-
dentiality protection) with
the Tag authentication. The
TAM2 message shall also
include the reference KeyID
to select an encryption key
in the Key Management Table
(see Clause 12). If protection
of integrity and authenticity
of the data is requested, the
selected key shall also con-
tain a MAC key.
0210 10.3.5 A Tag that supports TAM2 O-1.1 Tag By design
shall define at least one and
at most 16 memory profiles.
All supported addresses or
pointers for the memory
profiles shall be specified in
Annex E.
8 © ISO/IEC 2017 – All rights reserved
---------------------- Page: 13 ----------------------
ISO/IEC 19823-10:2017(E)
Table 3 (continued)
Protocol
Item Requirement MO Applies to How verified
subclause
0220 10.3.5 The memory profiles may also O-1.1 Tag By design
be linked to a key in the Key
Management Table that shall
be used for the encryption
process to protect the data.
0230 10.3.5 Custom data is specified as a O-1.1 Tag By design
number (1 to 16) of consecu-
tive 64‑bit blocks in the Tag's
memory. The custom data
block shall be defined by the
parameters Profile, Offset
and BlockCount.
0240 10.3.5 Profile shall select one of the O-1.1 Tag By design
memory profiles that are
supported by the Tag.
0250 10.3.5 BlockCount specifies the 4‑bit O-1.1 Tag By design
number of 64-bit custom
data blocks that need to be
returned from the offset posi-
tion onwards. Minimum value
is “0000 ”, corresponding to
b
one single 64-bit block. Maxi-
mum binary value is “1111 ”,
b
or decimal 15, corresponds
to a maximum number of 16
64-bit blocks of custom data
that shall be returned. If the
number of returned bits of the
custom data is not a multiple
of 128, then padding with
zeroes shall be applied to the
least significant bits of the
last block that has a non-zero
block size of less than 128
bits. The Interrogator shall
maintain the value of Block-
Count for use as part of the
MAC verification process. The
Tag manufacturer shall speci-
fy the number of custom data
blocks that can be returned.
0260 10.3.5 ProtMode specifies the mode O-1.1 Tag By design
of operation that shall be
used for the encipherment
and/or protection of the
custom data. Table 5 defines
the mode of operation for en-
cipherment algorithms and/
or message authentication
algorithms for the (optional)
protection (authentication
and/or encipherment) of
custom data.
© ISO/IEC 2017 – All rights reserved 9
---------------------- Page: 14 ----------------------
ISO/IEC 19823-10:2017(E)
Table 3 (continued)
Protocol
Item Requirement MO Applies to How verified
subclause
0270 10.3.5 Tags shall implement at least O-1.1 Tag By design
one of the modes of operation
as defined by Table 5 for each
of the memory profiles that
the Tag supports.
0280 10.3.5 The Interrogator shall gener- O-1.1 Interroga- By design
ate an 80-bit random TAM2 tor
Interrogator challenge in the Tag
following TAM2 message and
include several fields indicat-
ing additional options for the
authentication protocol.
0290 10.3.5 — ProtMode: 4-bit value to O-1.1 Tag By design
select the mode of operation
that shall be used to process
the custom data
0300 10.3.5 The Tag shall accept this O-1.1 Tag By design
message in any state. If the
parameters of the message
are valid, then the Tag shall
transition to the Initial state;
thereby aborting any cryp-
tographic protocol that has
not yet been completed.
0310 10.3.5 If the length of the TAM2 mes- O-1.1 Tag By demonstration using a se-
sage <> 120 bits, then the Tag quence of Test pattern 4, with
shall return an “Other Error” different values for IChallenge_
error condition and shall TAM2.
transition to the Initial state.
First time IChallenge_TAM2 shall
be “D53600FAA9B4C1965CC3 ”
h
and the response shall be accord-
ing to Test pattern 4.
Second time IChal-
lenge_TAM2 shall be
“D53600FAA9B4C1965C ” (88
h
bits) and the response shall be
“Other Error”.
Third time IChal-
lenge_TAM2 shall be
“D53600FAA9B4C1965CCFF ”
h
(104 bits) and the response shall
be “Other Error”.
0320 10.3.5 If TAM2_RFU <> “00000 ” O-1.1 Tag By demonstration using a se-
b
then the Tag shall
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.