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

This document describes test methods for determining the conformance of security crypto suites with the specifications given in ISO/IEC 29167‑19. This document contains conformance tests for all mandatory and 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 exclusively applicable in relation to RFID tags and interrogators defined in the ISO/IEC 18000 series using a reference to this document.

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
29-Aug-2018
Current Stage
6060 - International Standard published
Start Date
10-Aug-2018
Completion Date
30-Aug-2018
Ref Project

Buy Standard

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

Standards Content (sample)

INTERNATIONAL ISO/IEC
STANDARD 19823-19
First edition
2018-09
Information technology —
Conformance test methods for
security service crypto suites —
Part 19:
Crypto suite RAMON
Technologies de l'information — Méthodes d'essai de conformité pour
les suites cryptographiques des services de sécurité —
Partie 19: Suite cryptographique RAMON
Reference number
ISO/IEC 19823-19:2018(E)
ISO/IEC 2018
---------------------- Page: 1 ----------------------
ISO/IEC 19823-19:2018(E)
COPYRIGHT PROTECTED DOCUMENT
© ISO/IEC 2018

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 2018 – All rights reserved
---------------------- Page: 2 ----------------------
ISO/IEC 19823-19:2018(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 with respect to ISO/IEC 18000 parts ......................................................................................................... 2

5.1 Test requirements for ISO/IEC 18000-63 interrogators and tags .............................................................. 2

5.2 Test requirements for other parts of ISO/IEC 18000 ............................................................................................ 2

6 Test methods with respect to ISO/IEC 29167-19 interrogators and tags ..................................................3

6.1 Test map for optional features .................................................................................................................................................. 3

6.2 Crypto suite requirements ............................................................................................................................................................ 3

6.3 Test patterns ..........................................................................................................................................................................................12

Bibliography .............................................................................................................................................................................................................................17

© ISO/IEC 2018 – All rights reserved iii
---------------------- Page: 3 ----------------------
ISO/IEC 19823-19:2018(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.

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 2018 – All rights reserved
---------------------- Page: 4 ----------------------
ISO/IEC 19823-19:2018(E)
Introduction

ISO/IEC 29167 describes security as applicable for ISO/IEC 18000. The various parts of ISO/IEC 29167

describe crypto suites that are optional extensions to the ISO/IEC 18000 air interfaces.

ISO/IEC 19823 describes the conformance test methods for security service crypto suites. ISO/

IEC 19823 is related to ISO/IEC 18047, 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 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 RAMON crypto suite as standardized in ISO/

IEC 29167-19.

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

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

This document describes test methods for determining the conformance of security crypto suites with

the specifications given in ISO/IEC 29167-19.

This document contains conformance tests for all mandatory and 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 exclusively applicable in relation to RFID

tags and interrogators defined in the ISO/IEC 18000 series using a reference to this document.

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 18000-63:2015, 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-19:2016, Information technology — Automatic identification and data capture techniques —

Part 19: Crypto suite RAMON security services for air interface communications
3 Terms, definitions, symbols and abbreviated terms

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

ISO/IEC 19762 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 2018 – All rights reserved 1
---------------------- Page: 6 ----------------------
ISO/IEC 19823-19:2018(E)
4 Test methods
4.1 General

Clause 4 describes the general test methods for ISO/IEC 29167-19. As the parts of ISO/IEC 19823 are

always tested in relation to ISO/IEC 18047, 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. They may only be defined in ISO/IEC 19823 if

ISO/IEC 18047 does not define them, 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

Laboratory testing of one, or (if required for statistical reasons) multiple, products, processes or services

to ensure conformance. A laboratory 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 laboratory.
4.3 By design

Design parameters and/or theoretical analysis that 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 laboratory shall approve the technical analysis as being

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 with respect to ISO/IEC 18000 parts
5.1 Test requirements for ISO/IEC 18000-63 interrogators and tags

Interrogators and tags tested according this document shall be based on ISO/IEC 18000-63. Test

requirements for ISO/IEC 18000-63 interrogators and tags shall be as specified in ISO/IEC 18047-

6:2017, Clauses 4 and 5.

Before a DUT is tested according to this document, it shall meet the requirements of ISO/IEC 18047-

6:2017, Clause 8.
5.2 Test requirements for other parts of ISO/IEC 18000
Currently there are no test methods defined for other parts of ISO/IEC 18000.
2 © ISO/IEC 2018 – All rights reserved
---------------------- Page: 7 ----------------------
ISO/IEC 19823-19:2018(E)
6 Test methods with respect to ISO/IEC 29167-19 interrogators and tags
6.1 Test map for optional features

Interrogators and tags tested according this document shall be based on ISO/IEC 29167-19. 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 Table 2.
Table 1 — Test map for optional features
Mark items to be
Test
# Feature Additional requirement tested for
results
supplied product
1 Mutual authentication Shall be tested with the authenticate command
of the declared ISO/IEC 18000 part
2 Secure communication Shall be tested with the authenticate command
of the declared ISO/IEC 18000 part
3 Key update Shall be tested with the authenticate command
of the declared ISO/IEC 18000 part
4 Number of keys sup-
ported
5 Key length supported
by the tag

Table 2 lists all crypto suite requirements that shall be tested in dependence of the features of Table 1

as supported by the DUT.
6.2 Crypto suite requirements
Table 2 — Crypto suite requirements
Protocol M/O/
a,b
Item Requirement Applies to How to verify
a c
subclause PRM/CRM
1 6.2.1 The Interrogator shall com- M Interrogator By demonstration
pare its generated Interroga- using Test Pattern
tor challenge with the chal- 12 and Test Pattern
lenge it received from the Tag. 14
If the values match, the Tag is
identified.
2 6.2.1 If the Tag provides a signa- M Interrogator By design
ture along with the SID, the
Interrogator shall validate the
signature using the signature
verification key. If successful,
the Tag is authenticated.
3 6.5 The IID shall remain constant M Interrogator By design
during a session.
4 6.5 The SID of a Tag shall be set M Tag By design
during personalization and
shall remain constant through-
out the lifetime of the Tag.
5 6.5 The SID and the optional signa- M Tag By design
ture are secret information
and shall never be readable for
an unauthorized reader.
6 6.5 The SID shall never be sent in M Tag By design
plaintext.
© ISO/IEC 2018 – All rights reserved 3
---------------------- Page: 8 ----------------------
ISO/IEC 19823-19:2018(E)
Table 2 (continued)
Protocol M/O/
a,b
Item Requirement Applies to How to verify
a c
subclause PRM/CRM
7 6.5 The Tag shall not perform M Tag By design
signature generation or veri-
fication, nor shall it store the
corresponding keys.
8 6.5 The Tag shall store the SID M Tag By design
and the public key K for Tag
authentication in its memory.
9 6.5 The Tag shall store the SID O Tag By design
along with its signature in its
memory.
10 6.5 The memory locations storing M Tag By design
the SID and the secret keys
shall not be readable for any
Interrogator after having writ-
ten these values once during
production of the Tag.
11 6.5 The Interrogator shall have ac- M Interrogator By design
cess to the RAMON decryption
key K to be able to decrypt
the authentication message
sent by the Tag.
12 6.5 The Interrogator shall have ac- M Interrogator By design
cess to a list of valid SIDs; each
SID might have a signature
attached to it.
13 6.6 The length of the keys used for M Tag, Interro- By design
Tag identification shall be as gator
specified in Table 4.
14 6.6 The length of the keys used M Tag, Interro- By design
for mutual authentication and gator
secure communication shall be
as specified in Table 5.
15 8.1 A Tag shall support at least one M Tag By design
of two authentication protocol
modes, the partial result mode
or the complete result mode.
16 8.1 Interrogators shall support M Interrogator By demonstration
both protocol modes. using Test Pattern
12 and 13
17 8.1 The complete result mode shall M Interrogator, By design
require the capability of the Tag
interface standard to handle
long timeouts or to signalize
the interrogator that a tag is
still processing a command.
18 8.1 In partial result mode, a M Interrogator, By design
sequence of Authenticate com- Tag
mands shall be sent to the Tag
in order to complete the full
authentication protocol.
4 © ISO/IEC 2018 – All rights reserved
---------------------- Page: 9 ----------------------
ISO/IEC 19823-19:2018(E)
Table 2 (continued)
Protocol M/O/
a,b
Item Requirement Applies to How to verify
a c
subclause PRM/CRM
19 8.1 A Tag receiving a command M Tag By demonstration
with incorrect AuthMethod or using Test Pattern 3
Step fields shall respond either and Test Pattern 4
with an “insufficient privi-
leges” or an “other error” error
code. The crypto suite shall
transit to the Init state.
20 8.1 An Interrogator receiving a M Interrogator By design
Tag’s response with incorrect
AuthMethod or Step fields
shall reset the Tag and try to
restart the communication.
21 8.2 All Authenticate commands M Tag By demonstration
for Tag identification shall use using Test Pattern 1
AuthMethod = 11b in accord- or Test Pattern 2
ance with 10.3.
22 8.2.1 The crypto suite state transi- M Interrogator, By design
tions for Tag identification in Tag
partial result mode shall be as
specified in Figure 4.
23 8.2.2 The crypto suite state transi- M Interrogator, By design
tions for Tag identification in Tag
complete result mode shall be
as specified in Figure 5.
24 8.2.2 In case of failure during one of M Tag By design
the steps of the protocol, the
crypto suite transits to the
Init state.
25 10.1 The sequence of messages ex- M Interrogator, By design
changed for Tag identification Tag
in partial result mode shall be
as depicted in Figure 8.
26 10.1 The sequence of messages ex- M Interrogator, By design
changed for Tag identification Tag
in complete result mode shall
be as depicted in Figure 9.
27 10.1.1 In Step 1 of the partial result M Interrogator By design
mode, the Interrogator mes-
sage shall include a random
challenge to request the Tag to
send its identification data.
28 10.1.1 Upon reception of this mes- PRM Tag By design
sage, the Tag shall start calcu-
lating the response.
29 10.1.1 The first response of the Tag PRM Tag By design
shall be the total length of the
identification cryptogram.
30 10.1.1 In Step 2 of the partial result M Interrogator By design
mode, the Interrogator shall
retrieve the fragments of the
Tag’s identification crypto-
gram by chaining further
Authenticate commands and
responses.
© ISO/IEC 2018 – All rights reserved 5
---------------------- Page: 10 ----------------------
ISO/IEC 19823-19:2018(E)
Table 2 (continued)
Protocol M/O/
a,b
Item Requirement Applies to How to verify
a c
subclause PRM/CRM
31 10.1.2 In complete result mode, the M Interrogator By design
first and only Interrogator
message shall include a ran-
dom challenge.
32 10.1.2 The Tag shall transmit the CRM Tag By design
identification data to the read-
er and shall set the remaining
bytes to zero.
33 10.3.1 The coding of the Message M Interrogator By design
field for Tag Identification,
AuthMethod 3, Step 1 shall be
as specified in Table 7. This
message transmits the Inter-
rogator Challenge to the Tag.
34 10.3.1 KeySelect shall allow selecting M Interrogator By design
one key (K ) out of a number
of keys.
35 10.3.1 If only one key is supported, M Interrogator By design
KeySelect shall be 00h.
36 10.3.1 If the selected key is not availa- M Tag By demonstration
ble on the Tag, it shall respond using Test Pattern 5
with a “Not supported” error
code and transit to Init state.
37 10.3.1 MRead shall be set to “0000b” M Interrogator, By design
for Tag identification. Tag
38 10.3.1 An Interrogator shall set all M Interrogator By design
RFU bits of the message field
to “0”.
39 10.3.1 A Tag receiving a Message field M Tag By design
with RFU bits set other than
“0” shall respond with a “Not
supported” error code and
transit to Init state.
40 10.3.1 A Tag using partial result PRM Tag By design
mode shall require additional
commands to transmit the
partial result.
41 10.3.1 The coding of the Message field M Interrogator By design
in state TAM1.1 and TAM1.2
for AuthMethod 3, Step 2 shall
be as specified in Table 8.
42 10.3.1 An Interrogator shall set all M Interrogator By design
RFU bits of the message field
to “0”.
43 10.3.1 A Tag receiving a Message field PRM Tag By design
with RFU bits set other than
“0” shall respond with a “Not
supported” error code and
transit to Init state.
44 10.4 The Tag shall send a response M Tag By design
message to each Authenticate
command.
6 © ISO/IEC 2018 – All rights reserved
---------------------- Page: 11 ----------------------
ISO/IEC 19823-19:2018(E)
Table 2 (continued)
Protocol M/O/
a,b
Item Requirement Applies to How to verify
a c
subclause PRM/CRM
45 10.4.1.1 In partial result mode, the first PRM Tag By design
Tag response shall indicate the
overall length of response data
and shall not carry any bytes
of the response data itself.
46 10.4.1.1 The subsequent response PRM Tag By design
messages shall transmit frag-
ments of the response data in
consecutive order.
47 10.4.1.1 Each response message shall PRM Tag By design
indicate the remaining number
of bytes to be transmitted.
48 10.4.1.1 The coding of the Tag response PRM Tag By design
field for Tag Identification,
AuthMethod 3 Step 1, shall be
as defined in Table 11.
49 10.4.1.1 A Tag shall set all RFU bits of PRM Tag By design
the Tag Response field in step
1 to “0”.
50 10.4.1.1 An Interrogator receiving an M Interrogator By design
Authenticate Response field
with RFU bits set other than
“0” shall ignore the RFU bits
and try to continue communi-
cation with the Tag.
51 10.4.1.1 An Interrogator receiving a M Interrogator By design
response frame formatted
as shown in Table 11 shall
continue with Authenticate
commands for AuthMethod 3
with payload for Step 2.
52 10.4.1.1 The coding of the Tag response PRM Tag By design
field for Tag Identification,
AuthMethod 3, Step 2 shall be
as specified in Table 12.
53 10.4.1.1 If the Tag receives the first PRM Tag By demonstration
Authenticate command for Au- using Test Pattern 2
thMethod 3 Step 2, it shall pro-
cess the command, send the
response, transit from state
TAM1.1 into state TAM1.2 and
remain in TAM1.2 as long as
there are identification data
bytes remaining to be sent and
no error occurred.
54 10.4.1.1 The response data shall be cal- PRM Tag By design
culated in consecutive order.
55 10.4.1.1 The Tag shall indicate the PRM Tag By design
remaining number of bytes to
be fetched in the Remaining
Length field.
56 10.4.1.1 The Remaining Length en- PRM Tag By design
coded to 000h shall indicate
that this is the last fragment.
© ISO/IEC 2018 – All rights reserved 7
---------------------- Page: 12 ----------------------
ISO/IEC 19823-19:2018(E)
Table 2 (continued)
Protocol M/O/
a,b
Item Requirement Applies to How to verify
a c
subclause PRM/CRM
57 10.4.1.1 A Tag shall set all RFU bits of PRM Tag By design
the Tag Response field in step
2 to “0”.
58 10.4.1.1 An Interrogator receiving an M Interrogator By design
Authenticate Response field
with RFU bits set other than
“0” shall ignore the RFU bits
and try to continue communi-
cation with the Tag.
59 10.4.1.2 In complete result mode, the CRM Tag By demonstration
Tag shall transmit the whole using Test Pattern 1
response data in a single
response after it has finished
the calculation and transit to
state TAM1.3.
60 10.4.1.2 The format of the response CRM Tag By design
field for the complete result
mode shall be as specified in
Table 12.
61 10.4.1.2 In complete result mode, a Tag CRM Tag By design
shall set the Remaining Length
field to “000h” to indicate that
this is the only and complete
response.
62 10.4.1.2 The response data fragment M Tag By design
shall contain the complete
RAMON cryptogram, consist-
ing of 128 Byte.
63 10.4.3 A Tag that encounters an M Tag By design
error during the execution of a
cryptographic suite operation
shall send an error reply to the
Interrogator.
64 10.5 An Interrogator shall check the M Interrogator By design
Step and the Remaining Length
field in the Tags response to
determine between complete-
and partial response mode.
65 A Any combination of Start PRM Tag By design
States and Transitions for Tag
identification in partial result
mode not listed in Table A.1
shall result in an error and
consequently a transition to
the Init state.
66 A Any combination of Start CRM Tag By design
States and Transitions for
Tag identification in com-
plete result mode not listed
in Table A.2 shall result in an
error and consequently a tran-
sition to the Init state.
8 © ISO/IEC 2018 – All rights reserved
---------------------- Page: 13 ----------------------
ISO/IEC 19823-19:2018(E)
Table 2 (continued)
Protocol M/O/
a,b
Item Requirement Applies to How to verify
a c
subclause PRM/CRM
67 B A Tag that encounters an M Tag By design
error during the execution of a
cryptographic suite operation
shall send an error reply to the
Interrogator.
68 B The details of these error M Tag By design
replies shall be as defined in
the respective air interface
standards.
69 C.1 The RAMON authentication M Tag By design
cryptogram shall be composed
from the components specified
in Table C.1.
70 C.1 The SID, the signature and the M Tag By design
random filling bytes shall be
encoded as TLV structure to
facilitate the decomposition by
the interrogator.
71 C.1 The coding of TLV-fields in the M Tag By design
authentication message shall
be as specified in Table C.2.
72 C.1 If the optional signature is not M Tag By design
present, its TLV structure shall
be omitted completely.
73 C.1 A Random filling and a final M Tag By design
zero-byte shall be appended to
the authentication message to
yield a total size of 128 bytes.
74 C.1 If only two bytes are left for M Tag By design
the TLV coded random filling,
the coding shall be C8h 00h.
75 C.1 If only one byte is left for the M Tag By design
TLV coded random filling, the
coding shall be 00h.
76 C.1.2 The Tag shall insert additional O Tag By design
TLV-fields into the authentica-
tion message if the RAMON
encryption is used to read
out sensor data and/or other
dynamic information.
77 C.1.2 The coding of additional TLV- O Tag By design
fields shall be as specified in
Table C.5.
78 E.1 For the implementation of the M Interrogator, By design
RAMON crypto suite, an air in- Tag
terface protocol shall support
the required security com-
mands that this crypto suite
has implemented.
79 E.1 Security commands shall con- M Interrogator By design
tain a message field with pa-
rameters for the crypto suite.
© ISO/IEC 2018 – All rights reserved 9
---------------------- Page: 14 ----------------------
ISO/IEC 19823-19:2018(E)
Table 2 (continued)
Protocol M/O/
a,b
Item Requirement Applies to How to verify
a c
subclause PRM/CRM
80 E.1 A reply of a Tag contains a M Tag By design
response field with the data
returned by the crypto suite.
81 E.1 The Crypto Suite Identifier M Interrogator, By design
(CSI) for this crypto suite shall Tag
be defined as the 6-bit value
001001 and it is expanded to
the 8-bit value 09 .
82 E.1 This crypto suite shall support M Interrogator, By design
the security services which are Tag
defined in Table E.1.
83 E.5 A Crypto Suite supporting ISO/ M Interrogator, By design
IEC 18000-63 shall fulfil the Tag
protocol security command
requirements as defined in E.5.
84 E.5 For Tag Authentication, the M Interrogator, By demonstration
Authenticate command shall Tag using Test Pattern 1
be supported. or Test Pattern 2
85 E.5 For Tag Authentication, the O Interrogator, By demonstration
Challenge command may be Tag using Test Pattern 7
supported.
86 E.5 The execution time for an M Tag By demonstration
authentication shall be below using Test Pattern 1
1 minute. or Test Pattern 2
87 E.5 The Tag shall ignore com- M Tag By design
mands from an Interrogator
during execution of a crypto-
graphic operation.
88 E.5 The Tag shall support sending M Tag By demonstration
the contents of the response using Test Pattern 8
buffer in the reply to an ACK
command.
89 E.5 The Tag shall support sending M Tag By demonstration
the contents of the response using Test Pattern 6
buffer in the reply to a READ_
BUFFER command.
90 E.5 The tag may support a security O Tag By design
timeout following a crypto
error. The length of the time-
out shall be defined by the tag
manufacturer, depending on
the application profile.
...

Questions, Comments and Discussion

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