hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
89973e643aae79d7801b63dc41097bde | 103 106 | 8.3.1 Description of tests | Two narrowband experiments following the EATS-3 subjective test plan [i.1] were conducted. The test set-up, background noise reproduction calibration and levels, noise types and convergence sequencing are according to the EATS-3 subjective test plan [i.1], except where noted. The reference conditions are according to [... |
89973e643aae79d7801b63dc41097bde | 103 106 | 8.3.2 Description of validation results | Each individual sample used in Experiments 6 and 7 was processed by HEAD Acoustics GmbH using the re-trained P.835 objective predictor model. An average of the objective scores per condition (average of the scores of 16 samples), as well as the 95 % confidence interval was computed and plotted against the results of th... |
89973e643aae79d7801b63dc41097bde | 103 106 | 9 Application of the retrained model | In order to avoid ambiguities in the results the objective model should be applied in the way it was applied during the training process which also reflects the listening test: 1) The speech samples used in conjunction with the model should be the ones used in the subjective tests: 16 sentences of male and female speak... |
32cc1a79aae2591ed4d318f569c2d2ac | 103 104 | 1 Scope | The present document specifies Interoperability Test Descriptions (TDs) for the CoAP binding as specified in Annex D of TS 102 921 [5]. The Test Descriptions cover the CoAP protocol specification where relevant. The purpose of the interoperability testing is to prove that end-to-end functionality between devices such a... |
32cc1a79aae2591ed4d318f569c2d2ac | 103 104 | 2 References | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. Referenced documents which ar... |
32cc1a79aae2591ed4d318f569c2d2ac | 103 104 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] draft-ietf-core-coap-12: "Constrained Application Protocol (CoAP)". NOTE: Available at: http://tools.ietf.org/html/draft-ietf-core-coap-12. [2] IETF RFC 6690: "Constrained RESTful Environments (CoRE) Link Forma". [3] draft... |
32cc1a79aae2591ed4d318f569c2d2ac | 103 104 | 2.2 Informative references | The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. Not applicable. ETSI ETSI TS 103 104 V1.1.1 (2013-04) 6 |
32cc1a79aae2591ed4d318f569c2d2ac | 103 104 | 3 Definitions and abbreviations | |
32cc1a79aae2591ed4d318f569c2d2ac | 103 104 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: Device' (D'): Hosts DA that communicates to a GSCL using the dIa reference point application Point of Contract (aPoC): URI that identifies how requests are re-targeted |
32cc1a79aae2591ed4d318f569c2d2ac | 103 104 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: ACK Acknowledgement aPoC application Point of Contract CFG ConFigGuration CoAP Constrained Application Protocol CON Confirmable CORE Constrained RESTful Environment D' Device' DA Device Application dIa device application Interface EUT Equipmen... |
32cc1a79aae2591ed4d318f569c2d2ac | 103 104 | 4 Conventions | |
32cc1a79aae2591ed4d318f569c2d2ac | 103 104 | 4.1 The Test Description proforma | The test descriptions are provided in proforma tables. The following different types of test operator actions are considered during the test execution: • A stimulus corresponds to an event that enforces an EUT to proceed with a specific protocol action, like sending a message for instance. • A verify consists of verify... |
32cc1a79aae2591ed4d318f569c2d2ac | 103 104 | 4.2 Test Description naming convention | Table 1: TD naming convention TD/<root>/<gr>/<nn> <root> = root COAP Constrained Application Protocol M2M_COAP CoAP Binding for M2M <gr> = group CORE Core protocol LINK CoRE Link Format BLOCK Blockwise transfers OBS Observing Ressources <nn> = sequential number 01 to 99 |
32cc1a79aae2591ed4d318f569c2d2ac | 103 104 | 5 Test Description Summary | |
32cc1a79aae2591ed4d318f569c2d2ac | 103 104 | 5.1 CoAP Binding for M2M REST Resources | Table 2: CoAP Binding for M2M REST Resources 1 TD_M2M_COAP_01 M2M DA registers to its local SCL via an applicationCreateRequest (CoAP POST) 2 TD_M2M_COAP_02 M2M DA retrieves application resource via an applicationRetrieveRequest (CoAP GET) 3 TD_M2M_COAP_03 M2M DA updates attribute in application resource via an applica... |
32cc1a79aae2591ed4d318f569c2d2ac | 103 104 | 5.2 Additional CoAP | Table 3: CoAP Tests 1 TD_COAP_CORE_01 Perform GET transaction (CON mode) 2 TD_COAP_CORE_02 Perform POST transaction (CON mode) 3 TD_COAP_CORE_03 Perform PUT transaction (CON mode) 4 TD_COAP_CORE_04 Perform DELETE transaction (CON mode) 5 TD_COAP_CORE_05 Perform GET transaction (NON mode) 6 TD_COAP_CORE_06 Perform POST ... |
32cc1a79aae2591ed4d318f569c2d2ac | 103 104 | 6 Basic Configuration | |
32cc1a79aae2591ed4d318f569c2d2ac | 103 104 | 6.1 Resources offered by servers under test | In order to ease test setup and execution, CoAP servers are requested to support the following resources and primitives: Table 4: M2M Primitives Subject Primitive Application management applicationCreateRequest / Response applicationRetrieveRequest / Response applicationUpdateRequest / Response applicationDeleteRequest... |
32cc1a79aae2591ed4d318f569c2d2ac | 103 104 | 6.2 M2M Access Control | M2M Access control is not being used. Hence there is no primitive attribute 'requestingEntity' being mapped to any CoAP query parameter. |
32cc1a79aae2591ed4d318f569c2d2ac | 103 104 | 6.3 aPoc Re-Targeting Procedure | When M2M DA registers to its GSCL it can: • either use the aPoc Re-Targeting mechanism; • or create and update contentInstance resource on the GSCL. As a consequence, when the GSCL receives a resource retrieve request, it will: • either forward the request to DA; • or reply directly to the request itself. |
32cc1a79aae2591ed4d318f569c2d2ac | 103 104 | 6.4 CoAP settings | Unless stated otherwise, the following settings shall be applied: • Each equipment under test shall be configured with a unicast address • Client cache shall be cleaned up after each test • Use of ETag option shall be avoided, but implementation should be prepared to handle it • Use of Token shall be avoided, but imple... |
32cc1a79aae2591ed4d318f569c2d2ac | 103 104 | 7 Test Configurations | This clause defines the different test configurations. ETSI ETSI TS 103 104 V1.1.1 (2013-04) 14 |
32cc1a79aae2591ed4d318f569c2d2ac | 103 104 | 7.1 Basic M2M CoAP (M2M_CFG_01) | Figure 1 |
32cc1a79aae2591ed4d318f569c2d2ac | 103 104 | 7.2 M2M CoAP Multihop (M2M_CFG_02) | Figure 2 |
32cc1a79aae2591ed4d318f569c2d2ac | 103 104 | 7.3 Basic CoAP 1 (CoAP_CFG_01) | Figure 3: Basic One-2-One CoAP client/server Configuration GSCL D' DA dIa NSCL mId NA mIa GSCL D' DA dIa Client Server Packet sniffer Test Operator ETSI ETSI TS 103 104 V1.1.1 (2013-04) 15 |
32cc1a79aae2591ed4d318f569c2d2ac | 103 104 | 7.4 CoAP in lossy context (CoAP_CFG_02) | Figure 4: Basic One-2-One CoAP client/server Configuration in lossy context The Gateway emulates a lossy medium between the client and the server. It does not implement the CoAP protocol itself (in other terms it is not a CoAP proxy), but works at the transport layer. It provides two features: • It performs NAT-style U... |
32cc1a79aae2591ed4d318f569c2d2ac | 103 104 | 7.5 Test Configuration 3 (CoAP_CFG_03) | Figure 5: Basic One-2-One CoAP proxy/server Configuration The reverse proxy shown in the Figure 5 is assumed as CoAP/CoAP proxy. Test operator includes an interface (it can be a CoAP client) that creates the stimulus to initiate the tests for reverse proxy. More clearly, there exist two methods to create the stimulus f... |
32cc1a79aae2591ed4d318f569c2d2ac | 103 104 | 8 Test Descriptions | |
32cc1a79aae2591ed4d318f569c2d2ac | 103 104 | 8.1 CoAP Binding for M2M REST Resources | |
32cc1a79aae2591ed4d318f569c2d2ac | 103 104 | 8.1.1 ApplicationCreateRequest | Interoperability Test Description Identifier: TD_M2M_COAP_01 Objective: M2M DA registers to its local SCL via an applicationCreateRequest (CoAP POST) Configuration: M2M_CFG_01 [5], clauses 10.8.2, Annex D [6], clause 9.3.2.8 Pre-test conditions: void Test Sequence: Step Type Description 1 Stimulus M2M DA is requested t... |
32cc1a79aae2591ed4d318f569c2d2ac | 103 104 | 8.1.2 ApplicationRetrieveRequest | Interoperability Test Description Identifier: TD_M2M_COAP_02 Objective: M2M DA retrieves application resource via an applicationRetrieveRequest (CoAP GET) Configuration: M2M_CFG_01 References: [5], clauses 10.8.3, Annex D [6], clause 9.3.2.8 Pre-test conditions: • DA has created an Application resource <app> on SCL Tes... |
32cc1a79aae2591ed4d318f569c2d2ac | 103 104 | 8.1.3 ApplicationUpdateRequest | Interoperability Test Description Identifier: TD_M2M_COAP_03 Objective: M2M DA updates attribute in application resource via an applicationUpdateRequest (CoAP PUT) Configuration: M2M_CFG_01 References: [5], clauses 10.8.4, Annex D [6], clause 9.3.2.8 Pre-test conditions: • DA has created an Application resource <app> o... |
32cc1a79aae2591ed4d318f569c2d2ac | 103 104 | 8.1.4 SubscriptionCreateRequest | Interoperability Test Description Identifier: TD_M2M_COAP_04 Objective: M2M DA creates a subscription to application resource via subscriptionCreateRequest (CoAP POST) Configuration: M2M_CFG_01 References: [5], clauses 10.25.2, Annex D [6], clause 9.3.2.8.19 Pre-test conditions: • DA has created an Application resource... |
32cc1a79aae2591ed4d318f569c2d2ac | 103 104 | 8.1.5 SubscriptionNotifyRequest | Interoperability Test Description Identifier: TD_M2M_COAP_05 Objective: M2M GSCL sends notification(s) via subscriptionNotifyRequest (CoAP POST) Configuration: M2M_CFG_01 References: [5], clauses 10.25.7, Annex D [6], clause 9.3.2.8.19 Pre-test conditions: • DA has created an Application resource <app> on SCL • DA has ... |
32cc1a79aae2591ed4d318f569c2d2ac | 103 104 | 8.1.6 SubscriptionDeleteRequest | Interoperability Test Description Identifier: TD_M2M_COAP_06 Objective: M2M DA cancels subscription via an subscriptionDeleteRequest (CoAP DELETE) Configuration: M2M_CFG_01 References: [5], clauses 10.25.5, Annex D [6], clause 9.3.2.8.19 Pre-test conditions: • DA has created an Application resource <app> on SCL • DA ha... |
32cc1a79aae2591ed4d318f569c2d2ac | 103 104 | 8.1.7 ApplicationDeleteRequest | Interoperability Test Description Identifier: TD_M2M_COAP_07 Objective: M2M DA de-registers by deleting application resource via an applicationDeleteRequest (CoAP DELETE) Configuration: M2M_CFG_01 References: [5], clauses 10.8.5, Annex D [6], clause 9.3.2.8 Pre-test conditions: • DA has created an Application resource ... |
32cc1a79aae2591ed4d318f569c2d2ac | 103 104 | 8.1.8 TargetID containing several path segments | Interoperability Test Description Identifier: TD_M2M_COAP_08 Objective: Handle contentInstanceRetrieveRequest with targetID containing several path segments Configuration: M2M_CFG_01 References: [5], clauses 10.19.3, Annex D [6], clause 9.3.2.15 Pre-test conditions: • DA has created an Application resource <app> on SCL... |
32cc1a79aae2591ed4d318f569c2d2ac | 103 104 | 8.1.9 TargetID containing several query options | Interoperability Test Description Identifier: TD_M2M_COAP_09 Objective: Handle contentInstanceRetrieveRequest with targetID containing several query options Configuration: M2M_CFG_01 References: [5], clauses 10.19.3, Annex D [6], clause 9.3.2.15 Pre-test conditions: • DA has created an Application resource <app> on SCL... |
32cc1a79aae2591ed4d318f569c2d2ac | 103 104 | 8.1.10 TargetID using partial addressing | Interoperability Test Description Identifier: TD_M2M_COAP_10 Objective: Handle contentInstanceRetrieveRequest with targetID using partial addressing Configuration: M2M_CFG_01 References: [5], clauses 10.19.3, Annex D [6], clause 9.3.2.15 Pre-test conditions: • DA has created an Application resource <app> on SCL • DA ha... |
32cc1a79aae2591ed4d318f569c2d2ac | 103 104 | 8.1.11 Announcement | Interoperability Test Description Identifier: TD_M2M_COAP_11 Objective: M2M DA registration with Announcement Configuration: M2M_CFG_02 References: [5], clauses 10.9.2, Annex D [6], clause 9.3.2.28 Pre-test conditions: • GSCL has registered to NSCL as <gscl> Test Sequence: Step Type Description 1 Stimulus M2M DA is req... |
32cc1a79aae2591ed4d318f569c2d2ac | 103 104 | 8.1.12 Multihop retrieval using Proxy-Uri and aPoC | Interoperability Test Description Identifier: TD_M2M_COAP_12 Objective: M2M NA multi-hop resource retrieval using Proxy-URI (CoAP proxy) Configuration: M2M_CFG_02 References: [5], clauses 10.19.3, Annex D 1.5 [6], clause 9.3.2.15 Pre-test conditions: • DA has created an announceable Application resource <app_ann> on GS... |
32cc1a79aae2591ed4d318f569c2d2ac | 103 104 | 8.1.13 Multihop retrieval using m2mPocs | Interoperability Test Description Identifier: TD_M2M_COAP_12 Objective: M2M NA multi-hop resource retrieval using m2mPocs (M2M proxy) Configuration: M2M_CFG_02 References: [5], clauses 10.19.3, Annex D [6], clause 7.3, 9.2.1.9, 9.2.3.4, 9.2.3.24, 9.2.3.25, 9.3.2.21 Pre-test conditions: • DA has created a Application re... |
32cc1a79aae2591ed4d318f569c2d2ac | 103 104 | 8.2 Additional CoAP | |
32cc1a79aae2591ed4d318f569c2d2ac | 103 104 | 8.2.1 CoAP protocol | Interoperability Test Description Identifier: TD_COAP_CORE_01 Objective: Perform GET transaction (CON mode) Configuration: CoAP_CFG_01 References: [1], clauses 5.8.1,1.2,2.1,2.2,3.1 Pre-test conditions: • Server offers the resource /test with resource content is not empty that handles GET with an arbitrary payload Test... |
32cc1a79aae2591ed4d318f569c2d2ac | 103 104 | 8.2.2 CoRE Link Format | Interoperability Test Description Identifier: TD_COAP_LINK_01 Objective: Access to well-known interface for resource discovery Configuration: CoAP_CFG_01 References: [2] Pre-test conditions: Client and server supports CoRE Link Format Server supports /.well-known/core resource and the CoRE Link Format Test Sequence: St... |
32cc1a79aae2591ed4d318f569c2d2ac | 103 104 | 8.2.3 Blockwise transfers | Identifier: TD_COAP_BLOCK_01 Objective: Handle GET blockwise transfer for large resource (early negotiation) Configuration: CoAP_CFG_01 References: [4], clause 2.2 Pre-test conditions: • Client supports Block transfers • Server supports Block transfers • Server offers a large resource /large • Client knows /large requi... |
32cc1a79aae2591ed4d318f569c2d2ac | 103 104 | 8.2.4 Observing Resources | Interoperability Test Description Identifier: TD_COAP_OBS_01 Objective: Handle resource observation with CON messages Configuration: CoAP_CFG_01 References: [4], clause 1.2, Pre-test conditions: • Client supports Observe option • Server supports Observe option • Server offers an observable resource /obs changing period... |
b59c289c5793ee073de017c39c1aebc8 | 103 097 | 1 Scope | The present document specifies security header and certificate formats for Intelligent Transport Systems. These formats are defined specifically for securing G5 communication. |
b59c289c5793ee073de017c39c1aebc8 | 103 097 | 2 References | |
b59c289c5793ee073de017c39c1aebc8 | 103 097 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. Referenced documents which ar... |
b59c289c5793ee073de017c39c1aebc8 | 103 097 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. NOTE: While any hyperlinks in... |
b59c289c5793ee073de017c39c1aebc8 | 103 097 | 3 Definitions and abbreviations | |
b59c289c5793ee073de017c39c1aebc8 | 103 097 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: enumeration: set of values with distinct meaning |
b59c289c5793ee073de017c39c1aebc8 | 103 097 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: AES Advanced Encryption Standard CA Certificate Authority CAM Cooperative Awareness Message CRL Certificate Revocation List DENM Decentralized Environmental Notification Message DHAES Diffie-Hellman: An Encryption Scheme ECC Elliptic Curve Cry... |
b59c289c5793ee073de017c39c1aebc8 | 103 097 | 4 Basic format elements | |
b59c289c5793ee073de017c39c1aebc8 | 103 097 | 4.1 Presentation Language | The presentation language is derived from the Internet Engineering Task Force (IETF) RFC 2246 (TLS) [5] and from IEEE 1609.2-2012 [i.2] (draft D12) and is described in table 1. The encoding of multi-byte elements of the presentation language shall always use network byte order, i.e. big endian byte order, if applicable... |
b59c289c5793ee073de017c39c1aebc8 | 103 097 | 4.2 Specification of basic format elements | |
b59c289c5793ee073de017c39c1aebc8 | 103 097 | 4.2.1 IntX | int_x IntX; This data type encodes an integer of variable length. The length of this integer is encoded by a number of 1 bits followed by a 0 bit, where the number of 1 bits is equal to the number of additional octets used to encode the integer besides those used (partially) to encode the length. The encoding of the le... |
b59c289c5793ee073de017c39c1aebc8 | 103 097 | 4.2.2 PublicKeyAlgorithm | enum { ecdsa_nistp256_with_sha256(0), ecies_nistp256(1), reserved(240..255), (2^8-1) } PublicKeyAlgorithm; This enumeration lists supported algorithms based on public key cryptography. Values in the range of 240 to 255 shall not be used as they are reserved for internal testing purposes. NOTE: This definition is simila... |
b59c289c5793ee073de017c39c1aebc8 | 103 097 | 4.2.3 SymmetricAlgorithm | enum { aes_128_ccm (0), reserved (240..255), (2^8-1) } SymmetricAlgorithm; This enumeration lists supported algorithms based on symmetric key cryptography. Values in the range of 240 to 255 shall not be used as they are reserved for internal testing purposes. The algorithm aes_128_ccm denotes the symmetric key cryptogr... |
b59c289c5793ee073de017c39c1aebc8 | 103 097 | 4.2.4 PublicKey | struct { PublicKeyAlgorithm algorithm; select(algorithm) { case ecdsa_nistp256_with_sha256: EccPoint public_key; case ecies_nistp256: SymmetricAlgorithm supported_symm_alg; EccPoint public_key; unknown: opaque other_key<var>; } } PublicKey; This structure defines a wrapper for public keys by specifying the used algorit... |
b59c289c5793ee073de017c39c1aebc8 | 103 097 | 4.2.5 EccPoint | struct { extern PublicKeyAlgorithm algorithm; extern uint8 field_size; EccPointType type; opaque x[field_size]; select(type) { case x_coordinate_only: case compressed_lsb_y_0: case compressed_lsb_y_1: ; case uncompressed: opaque y[field_size]; unknown: opaque data<var>; } } EccPoint; This structure defines a public key... |
b59c289c5793ee073de017c39c1aebc8 | 103 097 | 4.2.6 EccPointType | enum { x_coordinate_only(0), compressed_lsb_y_0(2), compressed_lsb_y_1(3), uncompressed(4), (2^8-1) } EccPointType; This enumeration lists supported ECC point types. NOTE: This definition is identical to the one in IEEE 1609.2 Draft D12 [i.2], clause 6.2.19. |
b59c289c5793ee073de017c39c1aebc8 | 103 097 | 4.2.7 EncryptionParameters | struct { SymmetricAlgorithm symm_algorithm; select(symm_algorithm) { case aes_128_ccm: opaque nonce[12]; unknown: opaque params<var>; } } EncryptionParameters; This structure holds basic parameters and additional data required for encryption and decryption of data using different symmetric encryption algorithms. In cas... |
b59c289c5793ee073de017c39c1aebc8 | 103 097 | 4.2.8 Signature | struct { PublicKeyAlgorithm algorithm; select(algorithm) { case ecdsa_nistp256_with_sha256: EcdsaSignature ecdsa_signature; unknown: opaque signature<var>; } } Signature; This structure defines a container that encapsulates signatures based on public key cryptography. Depending on the value of algorithm, different data... |
b59c289c5793ee073de017c39c1aebc8 | 103 097 | 4.2.9 EcdsaSignature | struct { extern PublicKeyAlgorithm algorithm; extern uint8 field_size; EccPoint R; opaque s[field_size]; } EcdsaSignature; This structure defines the details needed to describe an ECDSA based signature. This field's length field_size is derived from the applied ECDSA algorithm using the mapping as specified in table 2.... |
b59c289c5793ee073de017c39c1aebc8 | 103 097 | 4.2.10 SignerInfo | struct { SignerInfoType type; select(type){ case self: ; case certificate_digest_with_sha256: HashedId8 digest; case certificate: Certificate certificate; case certificate_chain: Certificate certificates<var>; case certificate_digest_with_other_algorithm: PublicKeyAlgorithm algorithm; HashedId8 digest; unknown: opaque ... |
b59c289c5793ee073de017c39c1aebc8 | 103 097 | 4.2.11 SignerInfoType | enum { self(0), certificate_digest_with_sha256(1), certificate(2), certificate_chain(3), certificate_digest_with_other_algorithm(4), reserved(240..255), (2^8-1) } SignerInfoType; This enumeration lists methods to describe a message's signer. Values in the range of 240 to 255 shall not be used as they are reserved for i... |
b59c289c5793ee073de017c39c1aebc8 | 103 097 | 4.2.12 HashedId8 | opaque HashedId8[8]; This value is used to identify data such as a certificate. It shall be calculated by first computing the SHA-256 hash of the input data, and then taking the least significant eight bytes from the hash output. A canonical encoding for the EccPoint R contained in the signature field of a Certificate ... |
b59c289c5793ee073de017c39c1aebc8 | 103 097 | 4.2.13 HashedId3 | opaque HashedId3[3]; This value is used to give an indication on an identifier, where real identification is not required. This can be used to request a certificate from other surrounding stations. It shall be calculated by first computing the SHA-256 hash of the input data, and then taking the least significant three ... |
b59c289c5793ee073de017c39c1aebc8 | 103 097 | 4.2.14 Time32 | uint32 Time32; Time32 is an unsigned 32-bit integer, encoded in big-endian format, giving the number of International Atomic Time (TAI) seconds since 00:00:00 UTC, 01 January 2004. NOTE 1: The period of 232 seconds lasts about 136 years that is until 2140. NOTE 2: This definition is identical to the one in IEEE 1609.2 ... |
b59c289c5793ee073de017c39c1aebc8 | 103 097 | 4.2.15 Time64 | uint64 Time64; Time64 is a 64-bit unsigned integer, encoded in big-endian format, giving the number of International Atomic Time (TAI) microseconds since 00:00:00 UTC, 01 January 2004. NOTE: This definition is identical to the one in IEEE 1609.2 Draft D17 [i.3], clause 6.2.12. |
b59c289c5793ee073de017c39c1aebc8 | 103 097 | 4.2.16 Time64WithStandardDeviation | struct { Time64 time; uint8 log_std_dev; } Time64WithStandardDeviation; This structure defines how to encode time along with the standard deviation of time values. log_std_dev values 0 to 254 represent the rounded up value of the log to the base 1,134666 of the implementation's estimate of the standard deviation in uni... |
b59c289c5793ee073de017c39c1aebc8 | 103 097 | 4.2.17 Duration | uint16 Duration; This uint16 encodes the duration of a time span (e.g. a certificate's validity). The first three bits shall encode the units as given in table 3. The remaining 13 bits shall be treated as an integer encoded. NOTE 1: Except naming, this definition is identical to the one in IEEE 1609.2 Draft D12 [i.2], ... |
b59c289c5793ee073de017c39c1aebc8 | 103 097 | 4.2.18 TwoDLocation | struct { sint32 latitude; sint32 longitude; } TwoDLocation; This structure defines how to specify a two dimensional location. It is used to define validity regions of a certificate. latitude and longitude encode a coordinate in tenths of micro degrees relative to the World Geodetic System (WGS)-84 datum as defined in N... |
b59c289c5793ee073de017c39c1aebc8 | 103 097 | 4.2.19 ThreeDLocation | struct { sint32 latitude; sint32 longitude; opaque elevation[2]; } ThreeDLocation; This structure defines how to specify a three dimensional location. latitude and longitude encode coordinate in tenths of micro degrees relative to the World Geodetic System (WGS)-84 datum as defined in NIMA Technical Report TR8350.2 [2]... |
b59c289c5793ee073de017c39c1aebc8 | 103 097 | 4.2.20 GeographicRegion | struct { RegionType region_type; select(region_type){ case circle: CircularRegion circular_region; case rectangle: RectangularRegion rectangular_region<var>; case polygon: PolygonalRegion polygonal_region; case id: ETSI ETSI TS 103 097 V1.2.1 (2015-06) 16 IdentifiedRegion id_region; case none: ; unknown: opaque other_r... |
b59c289c5793ee073de017c39c1aebc8 | 103 097 | 4.2.21 RegionType | enum { none(0), circle(1), rectangle(2), polygon(3), id(4), reserved(240..255), (2^8-1) } RegionType; This enumeration lists possible region types. Values in the range of 240 to 255 shall not be used as they are reserved for internal testing purposes. NOTE: This definition is similar to the one in IEEE 1609.2 Draft D12... |
b59c289c5793ee073de017c39c1aebc8 | 103 097 | 4.2.22 CircularRegion | struct { TwoDLocation center; uint16 radius; } CircularRegion; This structure defines a circular region with radius given in metres and center at center. The region shall include all points on the reference ellipsoid's surface with a distance over surface of Earth equal to or less than the radius to the center point. F... |
b59c289c5793ee073de017c39c1aebc8 | 103 097 | 4.2.23 RectangularRegion | struct { TwoDLocation northwest; TwoDLocation southeast; } RectangularRegion; This structure defines a rectangular region by connecting the four points in the order (northwest.latitude, northwest.longitude), (northwest.longitude, southeast.longitude), (southeast.longitude, southeast.longitude), and (southeast.longitude... |
b59c289c5793ee073de017c39c1aebc8 | 103 097 | 4.2.24 PolygonalRegion | TwoDLocation PolygonalRegion<var>; This variable-length vector describes a region by enumerating points on the region's boundary. If two consecutively specified points P and Q define a line of constant bearing from P to Q, the left side of the line is defined as being outside of the polygon and the line itself and the ... |
b59c289c5793ee073de017c39c1aebc8 | 103 097 | 4.2.25 IdentifiedRegion | struct { RegionDictionary region_dictionary; uint16 region_identifier; IntX local_region; } IdentifiedRegion; This structure defines a predefined geographic region determined by the region dictionary region_dictionary and the region identifier region_identifier. local_region may optionally specify a more detailed regio... |
b59c289c5793ee073de017c39c1aebc8 | 103 097 | 4.2.26 RegionDictionary | enum { iso_3166_1(0), un_stats(1), (2^8-1) } RegionDictionary; This enumeration lists dictionaries containing two-octet records of globally defined regions. The dictionary that corresponds to iso_3166_1 shall contain values that correspond to numeric country codes as defined in ISO 3166-1 [3]. The dictionary that corre... |
b59c289c5793ee073de017c39c1aebc8 | 103 097 | 5 Specification of security header | |
b59c289c5793ee073de017c39c1aebc8 | 103 097 | 5.1 SecuredMessage | struct { uint8 protocol_version; HeaderField header_fields<var>; Payload payload_field; TrailerField trailer_fields<var>; } SecuredMessage; This structure defines how to encode a generic secured message: • protocol_version specifies the applied protocol version. For compliance with the present document, protocol versio... |
b59c289c5793ee073de017c39c1aebc8 | 103 097 | 5.2 Payload | struct { PayloadType type; select (type) { case signed_external: ; case unsecured: case signed: case encrypted: case signed_and_encrypted: unknown: opaque data<var>; } } Payload; This structure defines how to encode payload. In case of externally signed payload, no payload data shall be given as all data is external. I... |
b59c289c5793ee073de017c39c1aebc8 | 103 097 | 5.3 PayloadType | enum { unsecured(0), signed(1), encrypted(2), signed_external(3), signed_and_encrypted(4), (2^8-1) } PayloadType; This enumeration lists the supported types of payloads. NOTE: This definition is not available in IEEE 1609.2 Draft D12 [i.2]. |
b59c289c5793ee073de017c39c1aebc8 | 103 097 | 5.4 HeaderField | struct { HeaderFieldType type; select(type) { case generation_time: Time64 generation_time; case generation_time_standard_deviation: Time64WithStandardDeviation generation_time_with_standard_deviation; case expiration: Time32 expiry_time; case generation_location: ETSI ETSI TS 103 097 V1.2.1 (2015-06) 19 ThreeDLocation... |
b59c289c5793ee073de017c39c1aebc8 | 103 097 | 5.5 HeaderFieldType | enum { generation_time(0), generation_time_standard_deviation(1), expiration(2), generation_location(3), request_unrecognized_certificate(4), its_aid(5), signer_info(128), encryption_parameters(129), recipient_info(130), (2^8-1) } HeaderFieldType; This enumeration lists the supported types of header fields. NOTE: This ... |
b59c289c5793ee073de017c39c1aebc8 | 103 097 | 5.6 TrailerField | struct { TrailerFieldType type; select(type) { case signature: Signature signature; unkown: opaque security_field<var>; } } TrailerField; This structure defines how to encode information used by the security layer after processing the payload. A trailer field may contain data of the following cases: • signature: the si... |
b59c289c5793ee073de017c39c1aebc8 | 103 097 | 5.7 TrailerFieldType | enum { signature(1), (2^8-1) } TrailerFieldType; This enumeration lists the supported types of trailer fields. NOTE: This definition is not available in IEEE 1609.2 Draft D12 [i.2]. ETSI ETSI TS 103 097 V1.2.1 (2015-06) 21 |
b59c289c5793ee073de017c39c1aebc8 | 103 097 | 5.8 RecipientInfo | struct { HashedId8 cert_id; PublicKeyAlgorithm pk_encryption; select (pk_encryption) { case ecies_nistp256: EciesEncryptedKey enc_key; unknown: opaque enc_key<var>; } } RecipientInfo; This structure contains information for the decryption of a message for a recipient. This information is used to distribute recipient sp... |
b59c289c5793ee073de017c39c1aebc8 | 103 097 | 5.9 EciesEncryptedKey | struct { extern SymmetricAlgorithm symm_alg; extern uint32 symm_key_len; EccPoint v; opaque c[symm_key_len]; opaque t[16]; } EciesEncryptedKey; This structure defines how to transmit an ECIES-encrypted symmetric key as defined in IEEE Std 1363a-2004 [i.1]. The EccPoint v contains the sender's ECC ephemeral key used for... |
b59c289c5793ee073de017c39c1aebc8 | 103 097 | 6 Specification of certificate format | |
b59c289c5793ee073de017c39c1aebc8 | 103 097 | 6.1 Certificate | struct { uint8 version; SignerInfo signer_info; SubjectInfo subject_info; SubjectAttribute subject_attributes<var>; ValidityRestriction validity_restrictions<var>; Signature signature; } Certificate; This structure defines how to encode a certificate. • version specifies this certificate's version and shall be set to 2... |
b59c289c5793ee073de017c39c1aebc8 | 103 097 | 6.2 SubjectInfo | struct { SubjectType subject_type; opaque subject_name<2^8-1>; } SubjectInfo; This structure defines how to encode information about a certificate's subject. It contains the type of information in subject_type and the information itself in the variable-length vector subject_name. The subject_name variable-length vector... |
b59c289c5793ee073de017c39c1aebc8 | 103 097 | 6.3 SubjectType | enum { enrollment_credential(0), authorization_ticket(1), authorization_authority(2), enrollment_authority(3), root_ca(4), crl_signer(5), (2^8-1) } SubjectType; This enumeration lists the possible types of subjects: • Regular ITS stations shall use certificates containing a SubjectInfo of SubjectType enrollment_credent... |
b59c289c5793ee073de017c39c1aebc8 | 103 097 | 6.4 SubjectAttribute | struct { SubjectAttributeType type; select(type) { case verification_key: case encryption_key: PublicKey key; case reconstruction_value: EccPoint rv; case assurance_level: SubjectAssurance assurance_level; case its_aid_list: IntX its_aid_list<var>; case its_aid_ssp_list: ItsAidSsp its_aid_ssp_list<var>; unknown: opaque... |
b59c289c5793ee073de017c39c1aebc8 | 103 097 | 6.5 SubjectAttributeType | enum { verification_key(0), encryption_key(1), assurance_level(2), reconstruction_value(3), its_aid_list(32), its_aid_ssp_list(33), (2^8-1) } SubjectAttributeType; This enumeration lists the possible types of subject attributes. NOTE: This definition is not available in IEEE 1609.2 Draft D12 [i.2]. |
b59c289c5793ee073de017c39c1aebc8 | 103 097 | 6.6 SubjectAssurance | opaque SubjectAssurance; This field contains the ITS-S's assurance, which denotes the ITS-S's security of both the platform and storage of secret keys as well as the confidence in this assessment. This field shall be encoded as defined in table 5, where "A" denotes bit fields specifying an assurance level, "R" reserved... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.