BSI 14/30275432 DC:2014 Edition
$13.70
BS ISO/IEC 29167-10. Information technology. Automatic identification and data capture techniques. Part 10. Crypto suite AES-128 security services for air interface communications
Published By | Publication Date | Number of Pages |
BSI | 2014 | 35 |
PDF Catalog
PDF Pages | PDF Title |
---|---|
7 | Foreword Part 1: Security services for RFID air interfaces |
8 | Introduction |
9 | 1 Scope 2 Conformance 2.1 Air interface protocol specific information 2.2 Interrogator conformance and obligations 2.3 Tag conformance and obligations |
10 | 3 Normative references 4 Terms and definitions 4.1 AES-CBC-ENC(IV, key, data) AES data encryption (forward operation) in CBC mode of input data ‘data’, using initialization vector IV and 128 bit cryptographic key ‘key’ 4.2 AES-ECB-ENC(key, data) AES data encryption (forward operation) in ECB mode of input data ‘data’, using 128 bit cryptographic key ‘key’ 4.3 AES-CMAC-96(key, data) CMAC generation using AES in forward operation with 128 bit cryptographic key ‘key’ of input data ‘data’, truncating the result by using only the 96 most significant bits from the 128-bit CMAC code 4.4 Bit String Ordered sequence of 0’s and 1’s 4.5 Block Cipher 4.6 Block Size Number of bits in an input (or output) block of the block cipher |
11 | 4.7 Cryptographic Key 4.8 CMAC Cipher-based MAC algorithm based on a symmetric key block cipher. See MAC method 5 in [1] for a normative reference 4.9 Command (Message) Data that Interrogator sends to Tag with “Message” as parameter 4.10 D Number of additional 128-bit blocks with custom data that may be added to the Tag authentication response 4.11 Data Block (Block) Sequence of bits whose length is the block size of the block cipher 4.12 Initialization Vector Data block that some modes of operation require as an additional initial input 4.13 Input Block Data that is an input to either the forward cipher function or the inverse cipher function of the block cipher algorithm 4.14 Key String of bits used by a cryptographic algorithm to transform plain text into cipher text or vice versa or to produce a message authentication code 4.15 KeyID Numerical designator for a single key 4.16 Key[KeyID].ENC_key Key that shall be used for encryption 4.17 Key[KeyID].MAC_key Key that may be used for cryptographic integrity protection 4.18 MAC_key Variable that shall contain the key that will be used for cryptographic integrity protection 4.19 Memory Profile Start pointer within the Tag’s memory for addressing custom data block 4.20 Message Part of the Command that is defined by the crypto suite |
12 | 4.21 Mode of Operation (Mode) Algorithm for the cryptographic transformation of data that features a symmetric key block cipher algorithm 4.22 Output Block Data that is an output of either the forward cipher function or the inverse cipher function of the block cipher algorithm 4.23 Plaintext Usable data that is formatted as input to a mode 4.24 Reply (Response) Data that Tag returns to the Interrogator with “Response” as parameter 4.25 Response Part of the Reply (stored or sent) that is defined by the crypto suite 4.26 Word Bit string comprised of 16 bits. 5 Symbols and abbreviated terms 5.1 Symbols 5.2 Abbreviated terms |
13 | 6 Introduction of the AES-128 crypto suite 7 Parameter definitions Table 1 — Definition of AES-128 crypto suite parameters |
14 | 8 Crypto Suite state Diagram Figure 1 — Crypto suite Tag state diagram 9 Initialization and resetting 10 Authentication 10.1 Introduction Table 2 —message and response functions 10.2 Message and Response formatting |
15 | If AuthMethod = “00b” the Tag shall parse Message as described in section 10.3 10.3 Tag authentication (Method “00” = TAM) Figure 2 – Tag authentication If CustomData = “0b” the Tag shall parse the TAM1 Message as described in section 10.3.1 If CustomData = “1b” the Tag shall parse the TAM2 Message as described in section 10.3.4 10.3.1 TAM1 Message |
16 | Table 3 — TAM1 Message format 10.3.2 TAM1 Response Table 4 — Response if optional fields have not been used 10.3.3 Final Interrogator processing TAM1 10.3.4 TAM2 Message |
17 | Table 5 — Supported modes of operation for ProtMode |
18 | Table 6 — TAM2 Message format |
19 | 10.3.5 TAM2 Response 10.3.5.1 Response if ProtMode = “0000b”: Plaintext Table 7 — Response if ProtMode = “0000b”: Plain text 10.3.5.2 Response if ProtMode = “0001b”: CBC encipherment only |
20 | Table 8 — Response if ProtMode = “0001b”: CBC encipherment only 10.3.5.3 Response if ProtMode = “0010b”: CMAC message authentication only Table 9 — Response if ProtMode = “0010b”: CMAC message authentication only 10.3.5.4 Response if ProtMode = “0011b”: CBC encipherment with CMAC message authentication |
21 | Table 10 — Response if ProtMode = “0011b”: CBC encipherment with CMAC message authentication 10.3.6 Final Interrogator processing TAM2 11 Communication 12 Key Table |
22 | Table 11 — Link of MPI bits with memory profiles Table 12 — Key Management Table |
23 | Annex A (normative) Crypto Suite State transition tables Table A.1 — Crypto Suite State transition table |
24 | Annex B (normative) Error conditions and error handling Table B.1 — Error conditions |
25 | Annex C (normative) Cipher description |
26 | Annex D (informative) Test vectors D.1 References for AES test vectors D.1.1 Test vectors for the AES algorithm D.1.2 online AES calculator |
27 | Annex E (normative) Protocol specific information E.1 General Figure E.1— Message exchange for Tag authentication E.1.1 Supported Security Services Table E.1 — Security Services |
28 | E.2 Security Services for ISO/IEC 18000-3 mode 1 E.3 Security Services for ISO/IEC 18000-3 mode 3 E.4 Security Services for ISO/IEC 18000-63 E.4.1 ISO/IEC 18000-63 Protocol Commands |
29 | E.4.2 Security commands in ISO/IEC 18000-63 E.4.3 Implementation of crypto suite error conditions in ISO/IEC 18000-63 Table E.2 — Implementation of crypto suite error conditions as Tag error codes E.4.4 Key Properties E.4.5 Memory profiles Table E.3 — Description of ISO/IEC 18000-63 specific memory profiles for Profile |
30 | E.4.6 Interaction with Untraceability feature |
31 | Annex F (Informative) Examples F.1 General F.2 Assumed content of the Tag’s Key Management Table and memory profile F.2.1 Content of Key Management Table F.2.2 Memory profile configuration |
32 | F.3 Example for TAM1 Table F.3 — Example TAM1 Message Table F.4 — TAM1 Response F.4 Examples for TAM2 F.4.1 Example 1 Table F.5 — TAM2 Message – example 1 |
33 | Table F.6 — TAM2 Response – example 1 F.4.2 Example 2 Table F.7 — TAM2 Message – example 2 Table F.8 — TAM2 Response – example 2 |
34 | F.4.3 Example 3 |
35 | Bibliography |