| PDF Pages<\/th>\n | PDF Title<\/th>\n<\/tr>\n | ||||||
|---|---|---|---|---|---|---|---|
| 6<\/td>\n | Foreword \uf0be Part 1: Air Interface for security services and file management for RFID architecture \uf0be Part 10: Air Interface for security services crypto suite AES128 \uf0be Part 11: Air Interface for security services crypto suite PRESENT-80 \uf0be Part 12: Air Interface for security services crypto suite ECC-DH \uf0be Part 13: Air Interface for security services crypto suite Grain-128A \uf0be Part 14: Air Interface for security services crypto suite AES-OFB \uf0be Part 15: Air Interface for security services crypto suite XOR \uf0be Part 16: Air Interface for security services crypto suite ECDSA-ECDH \uf0be Part 17: Air Interface for security services crypto suite Crypto GPS \uf0be Part 19: Air Interface for security services crypto suite RAMON <\/td>\n<\/tr>\n | ||||||
| 7<\/td>\n | Introduction <\/td>\n<\/tr>\n | ||||||
| 9<\/td>\n | 1 Scope 2 Conformance 2.1 Claiming conformance 2.2 Interrogator conformance and obligations 2.3 Tag conformance and obligations <\/td>\n<\/tr>\n | ||||||
| 10<\/td>\n | 3 Normative references 4 Terms and definitions 4.1 Terms and definitions 4.1.1 Command (Message) Command that Interrogator sends to Tag with “Message” as parameter <\/td>\n<\/tr>\n | ||||||
| 11<\/td>\n | 4.1.2 Message Part of the Command that is defined by the CS 4.1.3 Reply (Response) Reply that Tag returns to the Interrogator with “Response” as parameter 4.1.4 Response Part of the Reply (stored or sent) that is defined by the CS 4.2 Symbols 4.3 Abbreviated terms <\/td>\n<\/tr>\n | ||||||
| 12<\/td>\n | 5 Cipher introduction 6 Parameter definitions <\/td>\n<\/tr>\n | ||||||
| 13<\/td>\n | 7 State diagram <\/td>\n<\/tr>\n | ||||||
| 14<\/td>\n | Figure 1 \u2014 State diagram 8 Authentication Figure 2 \u2014 Mutual authentication with key agreement Figure 3 \u2014 Protocol flows between TTP and interrogator 8.1 Command 8.1.1 Authenticate command <\/td>\n<\/tr>\n | ||||||
| 15<\/td>\n | 8.1.2 Authenticate(MAM1.1 Message) <\/td>\n<\/tr>\n | ||||||
| 16<\/td>\n | 8.1.3 MAM1.1 Response 8.1.4 Authenticate(MAM1.2 Message) <\/td>\n<\/tr>\n | ||||||
| 17<\/td>\n | 8.1.5 MAM1.2 Response <\/td>\n<\/tr>\n | ||||||
| 18<\/td>\n | 8.1.6 Authenticate_EX 8.1.7 Authenticate_EX Response <\/td>\n<\/tr>\n | ||||||
| 19<\/td>\n | 8.2 Authentication procedure 8.2.1 Protocol requirements 8.2.2 Procedure <\/td>\n<\/tr>\n | ||||||
| 21<\/td>\n | a) When the interrogator received the MAM 1.1 Response (the optional field TTPID presents), it should send the Authenticate_EX command to the TTP, including the information of TID,IID,TTPID,RNt and RNi. b) After receiving the Authenticate_EX command, the TTP shall verify the tag and interrogator certificate (See IETF RFC 3280 for the certificates status verification) and send the Authenticate_EX Response to the interrogator,including the information… c) When the interrogator received the Authenticate_EX Response from the TTP, it should check the tag validity by RNt, TID and the authentication results of the tag RESt. If the verification is failed, ignore the response and the authentication proced… d) After receiving the Authenticate(MAM 1.2 Message), the tag should check the interrogator validity by RNi, IID and the authentication results of the interrogator RESi. If the verification is failed, ignore the response and the authentication procedu… 9 Authenticate Communication Figure 4 \u2013 Authenticate communication <\/td>\n<\/tr>\n | ||||||
| 22<\/td>\n | 10 Secure Communication Figure 5 \u2013 Secure communication <\/td>\n<\/tr>\n | ||||||
| 23<\/td>\n | Annex A (normative) State transition table A.1 Ready state transition table Table A.1 \u2014 Ready state transition table A.2 Authenticate state transition table Table A.2 \u2014 Authenticate state transition table A.3 AuthComm state transition table Table A.3 \u2014 AuthComm state transition table A.4 SecureComm state transition table Table A.4 \u2014 SecureComm state transition table <\/td>\n<\/tr>\n | ||||||
| 24<\/td>\n | Annex B (normative) Error codes and error handling B.1 Error code format Table B.1 \u2014 Error code format B.2 Error type and error subcode Table B.2 \u2014 Error type and error subcode <\/td>\n<\/tr>\n | ||||||
| 25<\/td>\n | Annex C (normative) Cipher description <\/td>\n<\/tr>\n | ||||||
| 26<\/td>\n | Annex D (informative) Test Vectors D.1 Authentication Elliptic E curve D.2 Authentication Parameters <\/td>\n<\/tr>\n | ||||||
| 27<\/td>\n | D.3 Authentication Process <\/td>\n<\/tr>\n | ||||||
| 29<\/td>\n | D.4 Authenticate EX Command <\/td>\n<\/tr>\n | ||||||
| 31<\/td>\n | Annex E (normative) Protocol specific E.1 Protocol Specific Operation E.2 ISO\/IEC 18000-4 Mode 3 E.2.1 General E.2.2 Authenticate command Table E.1 \u2014 Payload Table E.2 \u2014 Data Table E.3 \u2014 Payload <\/td>\n<\/tr>\n | ||||||
| 32<\/td>\n | Table E.4 \u2014 Data Table E.5 \u2014 MAM1.1 Message Table E.6 \u2014 MAM1.1 Response format Table E.7 \u2014 MAM1.2 Message <\/td>\n<\/tr>\n | ||||||
| 33<\/td>\n | Table E.8 \u2014 MAM1.1 Response format E.2.3 AuthComm command Table E.9 \u2014 Payload Table E.10 \u2014 Data <\/td>\n<\/tr>\n | ||||||
| 34<\/td>\n | Table E.11 \u2014 Payload Table E.12 \u2014 Data E.2.4 SecureComm command Table E.13 \u2014 Payload Table E.14 \u2014 Data <\/td>\n<\/tr>\n | ||||||
| 35<\/td>\n | Table E.15 \u2014 Payload Table E.16 \u2014 Data <\/td>\n<\/tr>\n | ||||||
| 36<\/td>\n | Annex F (normative) Protocol message\u2019s fragmentation and defragmentation <\/td>\n<\/tr>\n | ||||||
| 37<\/td>\n | Annex G (informative) Examples of ECC parameters G.1 Principle G.2 ECC parameters used in the authentication mechanism <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":" BS ISO\/IEC 29167-16. Information technology. Automatic identification and data capture techniques. Part 16. Air interface for security services crypto suite ECDSA-ECDH<\/b><\/p>\n |