hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 8.3.6.2.3 Certificate Re-Provisioning procedure using EST | Purpose: Enabling an MEF Client to renew/rekey a currently valid Enrolled Certificate. See also the client certificate reissuance operational scenario in section 2.3 of IETF RFC 7030 [59]. Pre-Conditions: [59] A. Common Pre-conditions for all Certificate Provisioning Procedures: see pre-condition A in clause 8.3.6.2.2.... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 8.3.6.3 Certificate Provisioning procedures using SCEP | |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 8.3.6.3.1 Introduction | The Simple Certificate Enrolment Protocol (SCEP) is specified in the IETF RFC 8894 [66]. When SCEP is used for Certificate Provisioning procedures, the following mapping of concepts shall be applied: • The M2M Enrolment Function (MEF) Client acts as the SCEP Client. • The MEF acts as the SCEP Server (also known as a SC... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 8.3.6.3.2 Details of Certificate Provisioning procedures using SCEP | Purpose: Enabling an MEF Client to request its first certificate and subsequent certificates from the MEF using SCEP as specified in IETF RFC 8894 [66]. Pre-Conditions: A. Common Pre-conditions for all Certificate Provisioning Procedures: i) The MEF Client and MEF support SCEP. ii) The MEF Client is provided with the b... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 8.3.7 MEF Client Configuration Details | |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 8.3.7.1 MEF Client Credential Configuration Details | The MEF Client and MEF shall be configured with credentials for mutual authentication of the MEF Client and MEF. The credentials for mutual authentication shall be either pre-provisioned or remotely provisioned by another MEF using Remote Security Provisioning Frameworks, or by Device Configuration as specified in ETSI... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 8.3.7.2 MEF Client Registration Configuration Details | Purpose: The MEF Client Registration Configuration describes the information provisioned to a MEF Client to enable it to perform MEF procedures authorized by an administrating stakeholder. The administrating stakeholder arranges for the MEF Client Registration Configuration to be provided to the MEF Client. Pre-conditi... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 8.3.7.3 MEF Key Registration Configuration Details | Purpose: The MEF Key Registration Configuration describes the information provisioned to a MEF Client to enable it to perform MEF procedures authorized by an administrating stakeholder. The administrating stakeholder arranges for the MEF Client Registration Configuration to be provided to the MEF Client. Pre-conditions... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 8.3.8 Profile for Device Configuration within an Enrolment Exchange | ETSI TS 118 122 [57] specifies a series of resources types, and procedures on those resource types, for configuration of AEs and CSEs on Field Devices. As stated in clause 8.3.4.5, Device Configuration can be performed within an Enrolment Exchange with a MEF, or in a DM session with other DM servers (separate from an E... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 8.3.9 MEF Client Command Processing | |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 8.3.9.1 Introduction | Purpose: The MEF Client Commands are used by an MEF to control the sequence of Enrolment Exchange procedures executed by the MEF Client. A MEF Client Command is issued, or reissued, by the MEF to the MEF Client in the response of a MEF Client Command Retrieve procedure (clause 8.3.9.2) or MEF Client Command Update proc... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 8.3.9.2 MEF Client Command Retrieve Procedure | Triggering the Procedure: See clause 8.3.4.6 for mechanisms which can trigger MEF Client Command procedures. Pre-Conditions: a) The MEF and MEF Client have performed an MEF Handshake, see clause 8.3.5.2.2. b) The MEF Client Registration is not expired, and the MEF Client has obtained the MEFClientRegID for the registra... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 8.3.9.3 MEF Client Command Update procedure | Triggering: The MEF Client shall initiate the MEF Client Command Update procedure only when triggered from within the MEF Client Command Retrieve procedure (clause 8.3.9.2), or MEF Client Command Update procedure (as defined in the present clause) or a MEF Client Command Class-specific procedure (clauses 8.3.9.6, 8.3.9... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 8.3.9.4 The cmdDescription element | The cmdDescription element has data type sec:cmdDescription defined in clause 12.4.4 and includes the following elements: • cmdClassID: identifying a class of MEF Client Commands. • (conditional on cmdClassID) cmdArgs: containing arguments specific to the cmdClass. • (optional) targetID: When the MEF Client is a Node a... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 8.3.9.5 The cmdStatusCode element | |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 8.3.9.5.1 Introduction | The cmdStatusCode is used by the MEF and MEF Client to indicate the status of an issued Command. The value in the cmdStatusCode element is of datatype sec:cmdStatusCode, specified in clause 12.3.2.4. Table 8.3.9.5.1-1 provides an informative summary of the cmdStatusCode, with normative description in the remaining clau... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 8.3.9.5.2 cmdStatusCode MEF_CLIENT_CMD_ISSUED | The MEF is issuing the command, and the MEF expects that this is the first time that the MEF Client is receiving the command. |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 8.3.9.5.3 cmdStatusCode MEF_CLIENT_CMD_REISSUED | The MEF previously issued the command, and did not receive a corresponding MEF Client Command Update from the MEF Client (in particular, providing the status of the executed command), and consequently the MEF is reissuing the command. If the MEF Client already performed the command, then it reports the status, otherwis... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 8.3.9.5.4 cmdStatusCode MEF_CLIENT_CMD_OK | The MEF Client successfully performed the command. |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 8.3.9.5.5 cmdStatusCode MEF_CLIENT_CMD_REPEATED_CMD_ID | The cmdID in the MEF Client Command Response message matches the cmdID sent in the most recent MEF Client Command Update procedure. This would indicate some processing error on the MEF. |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 8.3.9.5.6 cmdStatusCode MEF_CLIENT_CMD_CLASS_NOT_SUPPORTED | The MEF Client does not support the requested cmdClass. ETSI ETSI TS 118 103 V4.7.1 (2026-03) 133 oneM2M TS-0003 version 4.7.1 Release 4 |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 8.3.9.5.7 cmdStatusCode MEF_CLIENT_CMD_BAD_ARGUMENTS | The MEF Client supports the cmdClass, but the MEF Client could not parse cmdArgs. |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 8.3.9.5.8 cmdStatusCode MEF_CLIENT_CMD_UNACCEPTABLE_ARGUMENTS | The MEF Client supports the cmdClass, and the MEF Client parsed cmdArgs element, but at least one of the elements of cmdArgs which could be processed by the MEF Client had an unacceptable value. |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 8.3.9.5.9 cmdStatusCode MEF_CLIENT_CMD_CERT_PROV_SERVER_ERROR | The MEF Client supports the CERT_PROV cmdClass, and the MEF Client parsed the cmdArgs element, but was unable to perform the command due to some error regarding communicating with the Certificate Provisioning server or an error internal to the Certificate Provisioning server. |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 8.3.9.5.10 cmdStatusCode MEF_CLIENT_CMD_CERT_PROV_CLIENT_ERROR | The MEF Client supports the CERT_PROV cmdClass, and the MEF Client parsed the cmdArgs element, but was unable to perform the command due to a processing error on the MEF Client. |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 8.3.9.5.11 cmdStatusCode MEF_CLIENT_CMD_DEV_CFG_SERVER_ERROR | The MEF Client supports the DEV_CFG cmdClass, and the MEF Client parsed the cmdArgs element, but was unable to perform the command due to some error regarding communicating with the Device Configuration server or an error internal to the Device Configuration server. |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 8.3.9.5.12 cmdStatusCode MEF_CLIENT_CMD_DEV_CFG_CLIENT_ERROR | The MEF Client supports the DEV_CFG cmdClass, and the MEF Client parsed the cmdArgs element, but was unable to perform the command due to some issue a processing error on the MEF Client. |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 8.3.9.5.13 cmdStatusCode MEF_CLIENT_CMD_MO_NODE_NOT_FOUND | The MEF Client supports the MO_Node cmdClass, and parsed the cmdArgs element, but could not find the MO node at the objectPath element in the MEF Client Command arguments. |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 8.3.9.5.14 cmdStatusCode MEF_CLIENT_CMD_MO_NODE_TYPE_CONFLICT | The MEF Client supports the MO_Node cmdClass, parsed the cmdArgs element, and found the MO node at the objectPath element, but the type of the MO Node does not match the objectType element in the MEF Client Command arguments. |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 8.3.9.5.15 cmdStatusCode MEF_CLIENT_CMD_MO_NODE_BAD_ARGS | The MEF Client supports the MO_Node cmdClass, parsed the cmdArgs element, and found the MO node at the objectPath element, and the type of the MO Node matches the objectTypeID element, but the MEF Client could not parse the objectTypeSpecifcArgs elememt. |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 8.3.9.5.16 cmdStatusCode MEF_CLIENT_CMD_MO_NODE_UNACCEPTABLE_ARGS | The MEF Client supports the MO_Node cmdClass, parsed the cmdArgs element, and found the MO node at the objectPath element, and the type of the MO Node matches the objectType element, and the MEF Client could not parse the objectTypeSpecifcArgs element but the remaining MO-type-specific arguments in MEF Client Command a... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 8.3.9.5.17 cmdStatusCode MEF_CLIENT_CMD_MO_NODE_INCONSISTENT_CONFIG | The MEF Client supports the MO_Node cmdClass, parsed the cmdArgs element, and found the MO node at the objectPath element, and the type of the MO Node matches the objectTypeID element, and the remaining MO-type- specific arguments in MEF Client Command arguments are acceptable, but the configuration of the MO nodes is ... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 8.3.9.5.18 cmdStatusCode MEF_CLIENT_CMD_MO_NODE_PROCESSING_FAILED | The MEF Client supports the MO_Node cmdClass, parsed the cmdArgs element, and found the MO node at the objectPath element, and the type of the MO Node matches the objectType element, and the remaining MO-type-specific arguments in MEF Client Command arguments are acceptable, but there has been some other error in execu... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 8.3.9.6 NO_MORE_COMMANDS MEF Client Command Class-specific Processes | Purpose: When cmdClassID indicates NO_MORE_COMMANDS, then the MEF is indicating that it has no more MEF Client Commands for the MEF Client. Elements of cmdArgs: If cmdDescription contains cmdClassID indicating NO_MORE_COMMANDS, then cmdArgs shall contain the noMoreCmdArgs element of data type sec:noMoreCmdArgs which in... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 8.3.9.7 CERT_PROV MEF Client Command Class-specific Processes | Purpose: When cmdClassID indicates CERT_PROV, then the MEF is indicating that the MEF Client is to perform a Certificate Provisioning Procedure with the MEF. ETSI ETSI TS 118 103 V4.7.1 (2026-03) 135 oneM2M TS-0003 version 4.7.1 Release 4 Elements of cmdArgs: If cmdDescription contains cmdClassID indicating CERT_PROV, ... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 8.3.9.8 DEV_CFG MEF Client Command Class-specific Processes | Purpose: When cmdClassID indicates DEV_CFG, then the MEF is indicating that the MEF Client is to perform a Device Configuration (ETSI TS 118 122 [57]) with the MEF Client acting as the DM Client and the MEF acting as the DM Server. Elements of cmdArgs: If cmdDescription contains cmdClassID indicating DEV_CFG, then the ... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 8.3.9.9 MO_NODE MEF Client Command Class-specific Processes | |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 8.3.9.9.1 Generic MO_NODE Processes | Purpose: When cmdClassID indicates MO_NODE, then the MEF is indicating that the MEF Client is to process an MO_NODE that has been already configured to the DM Client of the MEF Client (e.g. using Device Configuration in ETSI TS 118 122 [57]). Elements of cmdArgs: If cmdDescription contains cmdClassID indicating MO_NODE... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 8.3.9.9.2 [authenticationProfile]-specific Processes | Purpose: Processing an [authenticationProfile] MO node ensures that the MEF Client has been able to establish the credentials needed to use that [authenticationProfile] MO node for mutual authentication. Elements of objectTypeSpecificArgs: when objectTypeID matches the [authenticationProfile] specialization of the <mgm... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 8.3.9.9.3 Process [authenticationProfile] MO Node with pre-provisioned symmetric key | Purpose: Processing an [authenticationProfile] MO node with pre-provisioned symmetric key SUID (in the set {11,12,13}) ensures that the MEF Client has access to a local copy of the pre-provisioned symmetric key, for subsequent use with the [authenticationProfile] MO node. Preconditions: A. This procedure will succeed o... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 8.3.9.9.4 Process [authenticationProfile] MO Node with MEF-established symmetric key | Purpose: Processing an [authenticationProfile] MO node with MEF-established symmetric key SUID (in the set {21, 22, 23}) ensures that the MEF Client establishes a symmetric key with the MEF for subsequent use with the [authenticationProfile] MO node. Preconditions: A. This procedure will succeed only if the [authentica... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 8.3.9.9.5 Process [authenticationProfile] MO Node with MAF-established symmetric key | Purpose: Processing an [authenticationProfile] MO node with MEF-established symmetric key SUID (in the set {31,32,33}) ensures that the MEF Client, acting as a Source MAF Client, establishes a symmetric key with the MAF for subsequent use with the [authenticationProfile] MO node. Preconditions: A. This procedure will s... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 8.3.9.9.6 Process [authenticationProfile] MO Node with Certificate | Purpose: Processing an [authenticationProfile] MO node with Certificate SUID (in the set {41,42,43}) ensures that the MEF Client has access to a local copy of the MEF Client's Certificate and corresponding private key, for subsequent use with the [authenticationProfile] MO node. Preconditions: A. This procedure will su... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 8.3.9.9.7 [trustAnchorCred]-specific Processes | Purpose: Processing a [trustAnchorCred] MO node ensures that the MEF Client has a local copy of the trust anchor CA certificate identified by the [trustAnchorCred] MO node. Elements of objectTypeSpecificArgs: The objectTypeSpecificArgs element is not present for the [trustAnchorCred] specialization. Processing a [trust... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 8.3.9.9.8 [MAFClientRegCfg]-specific Processes | Purpose: Processing an [MAFClientRegCfg] MO node ensures that the MEF Client, acting as an MAF Client, has successfully registered with the MAF using the attributes in the [MAFClientRegCfg] MO node. Elements of objectTypeSpecificArgs: The objectTypeSpecificArgs element is not present for the [MAFClientRegCfg] specializ... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 8.4 End-to-End Security of Primitives (ESPrim) | |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 8.4.1 Purpose of E2E Security of Primitives (ESPrim) | End-to-End Security of Primitives (ESPrim) provides an interoperable framework for securing oneM2M primitives so CSEs (forwarding the primitive) do not need to be trusted with the confidentiality and integrity of the primitive. ESPrim provides mutual authentication, confidentiality, integrity protection and a freshness... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 8.4.2 End-to-End Security of Primitives (ESPrim) Architecture | The credential management aspects and data protection aspects for ESPrim are specified in the present clause. Clause 11.3.2, ETSI TS 118 101 [1] specifies the transport of ESPrim Objects. The primitive to be secured is called the inner primitive, and the primitive which is used to transport a secured inner primitive is... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 8.4.3 End-to-End Security of Primitives (ESPrim) Protocol Details | |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 8.4.3.1 End-to-End Security of Primitives (ESPrim) Parameter Definitions | |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 8.4.3.1.1 originatorESPrimRandObject parameter definition | The structure of the originator2ERandObject parameter is shown in table 8.4.3.1.1-1. This parameter is used in establishing sessionESPrimKey as part of End-to-End Security of Primitives (ESPrim), described in clause 8.4.2. The data type of the originatorESPrimRandObject parameter is specified in ETSI TS 118 104 [4]. Ta... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 8.4.3.1.2 receiverESPrimRandObject parameter definition | The structure of the receiver2ERandObject parameter is shown in table 8.4.3.1.2-1. This parameter is used in establishing sessionESPrimKey as part of End-to-End Security of Primitives (ESPrim), described in clause 8.4.2. The data type of the receiverESPrimRandObject parameter is specified in ETSI TS 118 104 [4]. ETSI E... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 8.4.3.1.3 e2eSecInfo resource attribute definition | The e2eSecInfo attribute occurs in the <CSEBase>, <remoteCSE> and <AE> resource types. The structure of the e2eSecInfo resource attribute is shown in table 8.4.3.1.3-1. This parameter is used in establishing sessionESPrimKey as part of End-to-End Security of Primitives (ESPrim), described in clause 8.4.2. The data type... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 8.5 End-to-End Security of Data (ESData) | |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 8.5.1 Purpose of ESData | End-to-End Security of Data (ESData) provides an interoperable framework for protecting data that ends up transported using oneM2M reference points, in order that so transited CSEs do not need to be trusted with that data. The data to be protected is called the ESData Payload. ESData payload could typically compose all... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 8.5.2 ESData Architecture | |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 8.5.2.1 List of ESData Security Classes and ESData Protection Options | The following ESData security classes are provided: • Encryption only: (see note) which offers confidentiality and integrity protection. This payload is protected using symmetric keys, and these symmetric keys are established using one or more of the following: - Symmetric keys otherwise established with the target end... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 8.5.2.2 Encryption-Only ESData Security Class | |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 8.5.2.2.1 Encryption-Only ESData Security Class Overview | The ESData protection option supported for the Encryption-Only Security Class are listed in table 8.5.2.1-1 "ESData protection Options". Encryption-Only ESData supports encrypting using any combination of Protection Options and using multiple credentials for each protection option. ESData Encryption Mode. ESData Securi... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 8.5.2.2.2 Encryption using Provisioned Symmetric ESData Key | For this Protection Option, the Source End-Point and each Target End-Point shall be provisioned with Provisioned Symmetric ESData Key, Provisioned Symmetric ESData Key Identifier and optionally Provisioned Symmetric ESData Key lifetime. This credential shall be provisioned via one of: • Pre-provisioning; • A Remote Sec... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 8.5.2.2.3 Encryption using Trust Enabling Function | This is specified in clause 8.6. ETSI ETSI TS 118 103 V4.7.1 (2026-03) 160 oneM2M TS-0003 version 4.7.1 Release 4 |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 8.5.2.2.4 Encryption using Target End-Point Certificates | 8.5.2.2.4.1 Associating Public Key Certificate with Target End-Points For this Protection Option, each Target End-Point shall be provisioned with a public key certificate which the Source End-Point trusts to be associated with the intended Target End-Point. The following options are supported: • The Target End-Point Ce... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 8.5.2.3 Signature-Only ESData Security Class | |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 8.5.2.3.1 Signature-Only ESData Security Class Overview | The ESData protection option supported for the Signature-Only ESData Security Class are listed in table 8.5.2.1-1 "ESData protection Options". ETSI ETSI TS 118 103 V4.7.1 (2026-03) 161 oneM2M TS-0003 version 4.7.1 Release 4 NOTE 1: The present document supports only one Signature-Only ESData Protection Option, but the ... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 8.5.2.3.2 Digital Signature using Source End-Point Certificate | 8.5.2.3.2.1 Associating Public Key Certificate with Source End-Point For this Protection Option, each Source End-Point shall be provisioned with a public key certificate which the Target End-Point trusts to be associated with the intended Source End-Point. The following options are supported: • The Source End-Point Cer... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 8.5.2.4 Nested Sign-then-Encrypt | For these options, the following high-level steps are performs (Credential Configuration steps and CEK Management steps are not shown): 1) The Source End-Point shall generate an inner Envelope containing one or more digital signatures for the inner Payload using one or more certificates according to the "Digital Signat... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 8.5.3 End-to-End Security of Data (ESData) Protocol Details | |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 8.5.3.1 Introduction | The End-to-End Security of Primitives (ESData) security classes support protocols shown in table 8.5.3.1-1. Table 8.5.3.1-1: ESData Security Classes, and mapping to XML-based and JSON-Based security protocols ESData Security Class XML-Based JOSE: JSON-Based Security Encryption only XML-ENC applied to ESData payload JWE... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 8.5.3.2 Encryption-Only ESData Security Class Protocol Details | To maintain consistency, key management algorithms are provided which are available in both XML-ENC [55] and JSON Web Encryption (JWE) [50]: • Direct Encryption. • AES Key Wrap, using 128-bit, 256-bit keys. • RSA-OAEP with MGF1 with SHA256. • Elliptic Curve Diffie-Hellman (ECDH) Key Agreement in Ephemeral-Static Mode u... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 8.5.3.3 Signature-Only ESData Security Class Protocol Details | To maintain consistency, signature types are provided which are available in both XML-Signature [52] and JSON Web Signature (JWS) [51]. • HMAC using SHA-256, SHA-384 or SHA-512. • RSA signature using PKCS1-v1.5 or PSS and MGF1 with SHA-256, SHA-384 or SHA-512. • ECDSA signature using P-256, P-384 or P-512 with SHA-256,... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 8.5.3.4 Nested-Sign-then-Encrypt ESData Security Class Protocol Details | The high level steps for the Nested-Sign-then-Encrypt ESData Security Class are described in clause 8.5.2.4. The inner Envelope shall be generated and processed according to one or more RSA or ECDSA signature types specified in clause 8.5.3.3. The inner Envelope shall be generated and processed according to any combina... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 8.6 Remote Security Frameworks for End-to-End Security | 8.6.1 Overview on Remote Provisioning and Registration of Credentials for End-to-End Security |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 8.6.1.1 Introduction | The Remote Provisioning Framework for End-to-End Security shall involve the ability for an entity to register and provision end-to-end credentials by means of a Trust Enabling Function for end-to-end security. An M2M Enrolment Function, M2M Authentication Function or a MN-CSE that is equipped with the ability to regist... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 8.6.3 Detailed Description on Source-Generated End-to-End Credentials | This clause describes the Generation and Registration of Symmetric End-to-End Security credentials by a Source ESF End-Point. The end-to-end security credentials that were self-generated by a Source shall be registered with the Trust Enabling Function. Such a mechanism is particularly useful when data (attribute) as we... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 8.7.1 Purpose of ESCertKE | End-to-End Certificate-based Key Establishment (ESCertKE) provides an interoperable framework for two end-points to use certificates for establishing a secret symmetric key called pairwiseE2EKey from which symmetric keys are derived for use in other end-to-end security frameworks such as End-to-End Security of Data (ES... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 8.7.2 ESCertKE Architecture | |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 8.7.2.1 ESCertKE Reference Model | The entities in the ESCertKE reference model are the ESCertKE Initiating End-Point which initiates the procedure and the single ESCertKE Terminating End-Point with which the ESCertKE Initiating End-Point intends to establish a pairwiseE2EKey. NOTE: Within the scope of clause 8.7, terms including the word "ESCertKE" can... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 8.7.2.2 ESCertKE Procedure Message Flow | The ESCertKE Messages shall be transported as specified in ETSI TS 118 101 [1]; for example, the <e2EKeyCSE> resource may be used. The ESCertKE Messages shall contain the TLS v1.2 [5] messages defined in table 8.7.2.2-1 "ESCertKE Message definitions". The ESCertKE Procedure message flow is shown in figure 8.7.2.2-1, an... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 8.8 MAF Security Framework Details | |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 8.8.1 Introduction to the MAF Security Framework Details | Clause 8.8 describes the common details and procedures used in the MAF-based Security Frameworks; in the present document these frameworks include: • The MAF-Based Security Association Establishment Framework (SAEF). • The MAF-Based End-to-End Security of Primitives (ESPrim) Framework. • The MAF-based End-to-End Securi... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 8.8.2 MAF Security Framework Processing and Information Flows | |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 8.8.2.1 Introduction | Clause 8.8.2 specifies the processing and information flows of the MAF procedures. |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 8.8.2.2 MAF Handshake Procedure | Purpose: A MAF Handshake procedure establishes a mutually authenticated TLS or DTLS session for protecting the communication between an MAF Client and MAF. In the case of the MAF Key Registration procedure, the TLS or DTLS session may be used by the Source MAF Client and MAF to establish the Key Value. ETSI ETSI TS 118... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 8.8.2.3 MAF Client Registration Procedure | Purpose: The MAF Client registers with the MAF to confirm that it is willing to use the services of the MAF, under the authorization of the administrating stakeholder. If remote provisioning is used to establish a symmetric key between an MAF Client and the MAF, then the MAF Client triggers the MAF (in the TLS handshak... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 8.8.2.4 MAF Client Configuration Retrieval Procedure | Purpose: This procedure enables a MAF Client to retrieve MAF Client Configurations provided by the administrating stakeholder to the MAF. Pre-Conditions: • The MAF Client has previously performed the MAF Client Registration procedure to create the MAF Client Registration record. • The MAF Client Registration record is ... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 8.8.2.5 MAF Client Registration Update Procedure | Purpose: This procedure enables a MAF Client to update the MAF Client registration by any combination of extending the expirationTime of the MAF Client Registration record, updating the labels or establish a new Km and KmID. Pre-Conditions: • The MAF Client has previously performed the MAF Client Registration procedure... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 8.8.2.6 MAF Client De-Registration Procedure | Purpose: This procedure enables a MAF Client to end its registration with the MAF. Pre-Conditions: • The MAF Client has previously performed the MAF Client Registration procedure to create the MAF Client Registration record. • The MAF Client Registration record is not expired. Procedure Description. The procedure compr... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 8.8.2.7 MAF Key Registration Procedure | Purpose: This procedure enables a Source MAF Client to establish a symmetric key with the MAF which can be retrieved for use by one or more Target MAF Clients. This procedure is performed between the Source MAF Client and the MAF. Pre-Conditions: • The Source MAF Client is provided with (or has otherwise determined) th... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 8.8.2.8 MAF Key Retrieval Procedure | Purpose: This procedure enables a Target MAF Client to retrieve the Key Value from a MAF corresponding to a RelativeKeyID received by the Target MAF Client. Pre-Conditions: • The Target MAF Client has performed the MAF Client Credential Configuration (clause 8.8.2.1) with the MAF, including configuration of the MAF Key... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 8.8.2.9 MAF Key Registration Update Procedure | Purpose: This procedure enables a Source MAF Client to update the metadata associated with a registered key. This procedure is performed between the Source MAF Client and the MAF. Pre-Conditions: • The MAF Client has previously performed the MAF Key Registration procedure to create the key registration. • The key regis... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 8.8.2.10 MAF Key De-Registration Procedure | Purpose: This procedure enables a Source MAF Client to request the MAF to stop distributing the registered key. This procedure is performed between the Source MAF Client and the MAF. Pre-Conditions: • The MAF Client has previously performed the MAF Key Registration procedure to create the key registration. • The key re... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 8.8.3 MAF Client Configuration Details | |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 8.8.3.1 MAF Client Credential Configuration Details | The MAF Client and MAF shall be configured with credentials for mutual authentication of the MAF Client and MAF. The credentials for mutual authentication shall be either pre-provisioned or remotely provisioned thanks to Remote Security Provisioning Frameworks. Either symmetric key credentials or certificate credential... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 8.8.3.2 MAF Client Registration Configuration Details | Purpose: The MAF Client Registration Configuration describes the information provisioned to a MAF Client to enable it to perform MAF procedures authorized by an administrating stakeholder. The administrating stakeholder arranges for the MAF Client Registration Configuration to be provided to the MAF Client. Pre-conditi... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 8.8.3.3 MAF Key Registration Configuration Details | Purpose: The MAF Key Registration Configuration describes the information provisioned to a MAF Client to enable it to perform MAF procedures authorized by an administrating stakeholder. The administrating stakeholder arranges for the MAF Client Registration Configuration to be provided to the MAF Client. Pre-conditions... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 9 Security Framework Procedures and Parameters | |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 9.0 Introduction | This clause specifies procedures and parameters of the phases of Security Association Establishment Frameworks (clause 8.2) and Remote Security Provisioning Frameworks (clause 8.3). 9.1 Security Association Establishment Framework Procedures and Parameters |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 9.1.1 Credential Configuration Parameters | |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 9.1.1.0 Introduction | The following Credential Configuration procedures are described in the present clause: • Credential Configuration of Entity A and Entity B, see clause 9.1.1.1. • Credential Configuration of M2M Authentication Functions, see clause 9.1.1.2. |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 9.1.1.1 Credential Configuration of Entity A and Entity B | Table 9.1.1.1-1 lists the parameters that may be configured to Entity A during the Credential Configuration phase and which are common to all Security Association Establishment Frameworks. Table 9.1.1.1-1: Parameters that may be configured to Entity A during the Credential Configuration phase and which are common to al... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.