Already a subscriber?
MADCAD.com Free Trial
Sign up for a 3 day free trial to explore the MADCAD.com interface, PLUS access the
2009 International Building Code to see how it all works.
If you like to setup a quick demo, let us know at support@madcad.com
or +1 800.798.9296 and we will be happy to schedule a webinar for you.
Security check
Please login to your personal account to use this feature.
Please login to your authorized staff account to use this feature.
Are you sure you want to empty the cart?
14/30276451 DC BS ISO/IEC 29167-16. Information technology. Automatic identification and data capture techniques. Part 16. Air interface for security services crypto suite ECDSA-ECDH, 2014
- ISO_IEC_DIS_29167-16(E)-Character_PDF_document.pdf [Go to Page]
- Foreword
- Part 1: Air Interface for security services and file management for RFID architecture
- Part 10: Air Interface for security services crypto suite AES128
- Part 11: Air Interface for security services crypto suite PRESENT-80
- Part 12: Air Interface for security services crypto suite ECC-DH
- Part 13: Air Interface for security services crypto suite Grain-128A
- Part 14: Air Interface for security services crypto suite AES-OFB
- Part 15: Air Interface for security services crypto suite XOR
- Part 16: Air Interface for security services crypto suite ECDSA-ECDH
- Part 17: Air Interface for security services crypto suite Crypto GPS
- Part 19: Air Interface for security services crypto suite RAMON
- Introduction
- 1 Scope
- 2 Conformance [Go to Page]
- 2.1 Claiming conformance
- 2.2 Interrogator conformance and obligations
- 2.3 Tag conformance and obligations
- 3 Normative references
- 4 Terms and definitions [Go to Page]
- 4.1 Terms and definitions
- 4.1.1
- Command (Message)
- Command that Interrogator sends to Tag with "Message" as parameter
- 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 [Go to Page]
- 4.2 Symbols
- 4.3 Abbreviated terms
- 5 Cipher introduction
- 6 Parameter definitions
- 7 State diagram
- Figure 1 — State diagram
- 8 Authentication
- Figure 2 — Mutual authentication with key agreement
- Figure 3 — Protocol flows between TTP and interrogator [Go to Page]
- 8.1 Command [Go to Page]
- 8.1.1 Authenticate command
- 8.1.2 Authenticate(MAM1.1 Message)
- 8.1.3 MAM1.1 Response
- 8.1.4 Authenticate(MAM1.2 Message)
- 8.1.5 MAM1.2 Response
- 8.1.6 Authenticate_EX
- 8.1.7 Authenticate_EX Response
- 8.2 Authentication procedure [Go to Page]
- 8.2.1 Protocol requirements
- 8.2.2 Procedure
- 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 – Authenticate communication
- 10 Secure Communication
- Figure 5 – Secure communication
- Annex A (normative) State transition table [Go to Page]
- A.1 Ready state transition table
- Table A.1 — Ready state transition table [Go to Page]
- A.2 Authenticate state transition table
- Table A.2 — Authenticate state transition table [Go to Page]
- A.3 AuthComm state transition table
- Table A.3 — AuthComm state transition table [Go to Page]
- A.4 SecureComm state transition table
- Table A.4 — SecureComm state transition table
- Annex B (normative) Error codes and error handling [Go to Page]
- B.1 Error code format
- Table B.1 — Error code format [Go to Page]
- B.2 Error type and error subcode
- Table B.2 — Error type and error subcode
- Annex C (normative) Cipher description
- Annex D (informative) Test Vectors [Go to Page]
- D.1 Authentication Elliptic E curve
- D.2 Authentication Parameters
- D.3 Authentication Process
- D.4 Authenticate EX Command
- Annex E (normative) Protocol specific [Go to Page]
- E.1 Protocol Specific Operation
- E.2 ISO/IEC 18000-4 Mode 3 [Go to Page]
- E.2.1 General
- E.2.2 Authenticate command
- Table E.1 — Payload
- Table E.2 — Data
- Table E.3 — Payload
- Table E.4 — Data
- Table E.5 — MAM1.1 Message
- Table E.6 — MAM1.1 Response format
- Table E.7 — MAM1.2 Message
- Table E.8 — MAM1.1 Response format [Go to Page]
- E.2.3 AuthComm command
- Table E.9 — Payload
- Table E.10 — Data
- Table E.11 — Payload
- Table E.12 — Data [Go to Page]
- E.2.4 SecureComm command
- Table E.13 — Payload
- Table E.14 — Data
- Table E.15 — Payload
- Table E.16 — Data
- Annex F (normative) Protocol message’s fragmentation and defragmentation
- Annex G (informative) Examples of ECC parameters
- G.1 Principle
- G.2 ECC parameters used in the authentication mechanism [Go to Page]