hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
32612c3dc6baea8dc1c17ee9ca2b1a68 | 119 142-3 | 6.2.2 Notation for requirements | This clause describes the notation used for defining the requirements of the different PAdES signature levels. The requirements on the elements and services are expressed in tables. A row in the table either specifies requirements for an element or a service. These tables contain five columns. 1) Column "Elements/Servi... |
32612c3dc6baea8dc1c17ee9ca2b1a68 | 119 142-3 | 6.3 Requirements on components and services | This clause defines requirements on elements and services that PAdES signatures have to fulfil. Table 1 shows the presence and cardinality requirements on the elements and services indicated in the first column for the two PAdES-DTS levels, namely: PAdES-DTS-BET and PAdES-DTS-A. Additional requirements are detailed bel... |
f46e47df06cd8c6873bddc70686b1058 | 118 132 | 1 Scope | The present document specifies communication between the M2M Authentication Function (MAF) and MAF clients on the reference point Mmaf and between the M2M Enrolment Function (MEF) and MEF clients on the reference point Mmef. |
f46e47df06cd8c6873bddc70686b1058 | 118 132 | 2 References | |
f46e47df06cd8c6873bddc70686b1058 | 118 132 | 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 referenced document (including any amendments) applies. Referenced documents which a... |
f46e47df06cd8c6873bddc70686b1058 | 118 132 | 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 referenced document (including any amendments) applies. NOTE: While any hyperlinks i... |
f46e47df06cd8c6873bddc70686b1058 | 118 132 | 3 Definition of terms, symbols and abbreviations | |
f46e47df06cd8c6873bddc70686b1058 | 118 132 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI TS 118 111 [7], ETSI TS 118 103 [2] and the following apply: MAF Client: functionality for performing MAF procedures on behalf of an associated CSE or AE, or on behalf of CSE or AE(s) present on an associated Node MAF interface: communication interface b... |
f46e47df06cd8c6873bddc70686b1058 | 118 132 | 3.2 Symbols | Void. |
f46e47df06cd8c6873bddc70686b1058 | 118 132 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in ETSI TS 118 111 [7], ETSI TS 118 103 [2] and the following abbreviations apply: ADN Application Dedicated Node AE Application Entity AE-ID Application Entity Identifier API Application Programming Interface ASN Application Service Node BBF Broadband F... |
f46e47df06cd8c6873bddc70686b1058 | 118 132 | 4 Conventions | The key words "Shall", "Shall not", "May", "Need not", "Should", "Should not" in the present document are to be interpreted as described in the oneM2M Drafting Rules [i.1]. |
f46e47df06cd8c6873bddc70686b1058 | 118 132 | 5 General Description | |
f46e47df06cd8c6873bddc70686b1058 | 118 132 | 5.1 MAF Interface | |
f46e47df06cd8c6873bddc70686b1058 | 118 132 | 5.1.1 Introduction | The MAF Interface is a simple variant of the Mcc/Mca reference points specifying the interaction of MAF Clients with a M2M Authentication Function (MAF), acting on behalf of an administrating stakeholder such as an M2M SP or third party M2M Trust Enabler (MTE). The present document does not specify the operation and ma... |
f46e47df06cd8c6873bddc70686b1058 | 118 132 | 5.1.2 MAF Interface Overview | This MAF Interface overview is based on the specification in clause 6 of ETSI TS 118 104 [3]. Identifiers such as M2M-SP-ID, AE-ID and CSE-ID as defined in 6.2.3 of [3] also apply to the MAF Interface. M2M Trust Enablers (MTEs) are identified using an M2M-SP-ID. Resources are addressed as specified in clause 6.2.4 in [... |
f46e47df06cd8c6873bddc70686b1058 | 118 132 | 5.2 MEF Interface | |
f46e47df06cd8c6873bddc70686b1058 | 118 132 | 5.2.1 Introduction | The M2M Enrolment Function (MEF) is an essential part of the oneM2M Remote Security Provisioning architecture. Clause 6.1.2.1 of ETSI TS 118 103 [2] defines the following three variants of Remote Security Provisioning Frameworks (RSPF): • Pre-Provisioned Symmetric Key RSPF • Certificate-Based RSPF • GBA-based RSPF The ... |
f46e47df06cd8c6873bddc70686b1058 | 118 132 | 5.2.2 MEF Interface Overview | This MEF Interface overview is based on the specification in clause 6 of ETSI TS 118 104 [3]. Identifiers such as M2M-SP-ID, AE-ID and CSE-ID as defined in 6.2.3 of ETSI TS 118 104 [3] also apply to the MEF Interface. M2M Trust Enablers (MTEs) are identified using an M2M-SP-ID. Resources are addressed as specified in c... |
f46e47df06cd8c6873bddc70686b1058 | 118 132 | 6 Processing and Representation of Primitives | |
f46e47df06cd8c6873bddc70686b1058 | 118 132 | 6.1 Common aspects of the MAF and MEF interface | This clause corresponds to the specification in clauses 7 and 8 of ETSI TS 118 104 [3]. Both, MAF and MEF Interface request primitive formats conform to clause 7.2.1.1 of ETSI TS 118 104 [3], constrained to the CRUD operations, with request parameters listed in table 5.1.2-1 and table 5.2.2-1, respectively. Both, MAF a... |
f46e47df06cd8c6873bddc70686b1058 | 118 132 | 6.2 MAF Interface | The MAF Interface generic resource request procedure for originators and receivers conforms to clauses 7.2.2.1 and 7.2.2.2 of ETSI TS 118 104 [3], with the following clarification: • The MAF Client acts as the originator, and the MAF acts as the receiver and resource hosting entity. • The MAF Handshake procedure (claus... |
f46e47df06cd8c6873bddc70686b1058 | 118 132 | 6.3 MEF Interface | The MEF Interface generic resource request procedure for originators and receivers conforms to clauses 7.2.2.1 and 7.2.2.2 of ETSI TS 118 104 [3] with the following clarification: • The MEF Client acts as the originator, and the MEF acts as the receiver and resource hosting entity. • The MEF Handshake procedure (clause... |
f46e47df06cd8c6873bddc70686b1058 | 118 132 | 7 Resource types definitions | |
f46e47df06cd8c6873bddc70686b1058 | 118 132 | 7.1 Namespaces used for resource and data types | Representations of resources applicable to the MAF and MEF Interfaces employ the namespace identifier "sec:" for global XML elements associated with a resource type. Data types of the attributes and complex-type elements of these resource types may use any of the name space identifiers listed in table 7.1-1. Any data t... |
f46e47df06cd8c6873bddc70686b1058 | 118 132 | 7.2 Resource Type <MAFBase> | The <MAFBase> resource shall represent a MAF. ETSI MAF and MEF Interface Specification 16 oneM2M TS-0032 version 4.0.1 Release 4 The <MAFBase> resource shall contain the child resources specified in table 7.2-1. Table 7.2-1: Child resources of <MAFBase> resource Child Resources of <MAFBase> Child Resource Type Multipli... |
f46e47df06cd8c6873bddc70686b1058 | 118 132 | 7.3 Resource Type <MEFBase> | The <MEFBase> resource shall represent a MEF. The <MEFBase> resource shall contain the child resources specified in table 7.3-1. Table 7.3-1: Child resources of <MEFBase> resource Child Resources of <MEFBase> Child Resource Type Multiplicity Description [variable] <mefClientReg> 0..n See clause 7.4 [variable] <symmKeyR... |
f46e47df06cd8c6873bddc70686b1058 | 118 132 | 7.4 Resource Type <mafClientReg> | The <mafClientReg> resource shall represent a MAF Client enrolled with an M2M SP or M2M Trust Enabler (MTE). NOTE: A single MAF Client can be enrolled with at most one M2M SP and any number of MTEs (typically enabling end-to-end security to MAF Clients outside the MAF Client's M2M SP's domain). Consequently, a single M... |
f46e47df06cd8c6873bddc70686b1058 | 118 132 | 7.5 Resource Type <mefClientReg> | The <mefClientReg> resource shall represent a MEF Client enrolled with an M2M SP or M2M Trust Enabler (MTE). NOTE: A single MEF Client can be enrolled with at most one M2M SP and any number of MTEs (typically enabling end-to-end security to MEF Clients outside the MEF Client's M2M SP's domain). Consequently, a single M... |
f46e47df06cd8c6873bddc70686b1058 | 118 132 | 7.6 Resource Type <symmKeyReg> | The <symmKeyReg> resource shall represent a symmetric key that a source MAF Client or a source MEF Client has established with the MAF or MEF, respectively, for distributing to authorized Target MAF or MEF Clients and/or another MAF or MEF. The MAF or MEF Client provides a list of authorized Targets when the resource i... |
f46e47df06cd8c6873bddc70686b1058 | 118 132 | 7.7 Resource Type <mefClientCmd> | A <mefClientCmd> resource includes instructions for the MEF client associated with the parent <mefClientReg> resource to be executed. The <mefClientCmd> resource shall contain no child resources. The <mefClientCmd> resource shall contain the attributes specified in table 7.7-1. Table 7.7-1: Attributes of <mefClientCmd>... |
f46e47df06cd8c6873bddc70686b1058 | 118 132 | 8 Resource-type specific procedures and definitions | |
f46e47df06cd8c6873bddc70686b1058 | 118 132 | 8.1 Resource Type <MAFBase> | |
f46e47df06cd8c6873bddc70686b1058 | 118 132 | 8.1.1 Introduction | A <MAFBase> resource shall represent a MAF. This <MAFBase> resource shall be the root for all the resources that are residing on the MAF. Table 8.1.1-1: Data Type Definition of <MAFBase> Data Type ID File Name Note MAFBase SEC-MAFBase-v2_1_0.xsd The <MAFBase> resource has no resource-specific attributes. ETSI MAF and M... |
f46e47df06cd8c6873bddc70686b1058 | 118 132 | 8.1.2 <MAFBase> resource specific procedures on CRUD operations | |
f46e47df06cd8c6873bddc70686b1058 | 118 132 | 8.1.2.1 Create | Originator: The <MAFBase> resource shall not be created via API. Receiver: Primitive specific operation on Recv-1.0 "Check the syntax of received message": 1) If the request is received, the MAF shall execute the following steps in order: a) "Create an unsuccessful Response primitive" with the Response Status Code indi... |
f46e47df06cd8c6873bddc70686b1058 | 118 132 | 8.1.2.2 Retrieve | Originator: No change from the generic procedures in clause 7.2.2.1 of ETSI TS 118 104 [3] with clarifications discussed in clauses 5.1 and 6. Receiver: Same as the generic procedures in clause 7.2.2.2 of ETSI TS 118 104 [3] with clarifications discussed in clauses 5.1 and 6, and performing the following step in the pl... |
f46e47df06cd8c6873bddc70686b1058 | 118 132 | 8.1.2.3 Update | Originator: The <MAFBase> resource shall not be updated via API. Receiver: Primitive specific operation on Recv-1.0 "Check the syntax of received message": 1) If the request is received, the MAF shall execute the following steps in order: a) "Create an unsuccessful Response primitive" with the Response Status Code indi... |
f46e47df06cd8c6873bddc70686b1058 | 118 132 | 8.1.2.4 Delete | Originator: The <MAFBase> resource shall not be DELETEed via API. ETSI MAF and MEF Interface Specification 21 oneM2M TS-0032 version 4.0.1 Release 4 Receiver: Primitive specific operation on Recv-1.0 "Check the syntax of received message": 1) If the request is received, the MAF shall execute the following steps in orde... |
f46e47df06cd8c6873bddc70686b1058 | 118 132 | 8.2 Resource Type <MEFBase> | |
f46e47df06cd8c6873bddc70686b1058 | 118 132 | 8.2.1 Introduction | A <MEFBase> resource shall represent a MEF. This <MEFBase> resource shall be the root for all the resources that are residing on the MEF. Table 8.2.1-1: Data Type Definition of <MEFBase> Data Type ID File Name Note MEFBase SEC-MEFBase-v2_1_0.xsd The <MEFBase> resource has no resource-specific attributes. Table 8.2.1-2:... |
f46e47df06cd8c6873bddc70686b1058 | 118 132 | 8.2.2 <MEFBase> resource specific procedures on CRUD operations | |
f46e47df06cd8c6873bddc70686b1058 | 118 132 | 8.2.2.1 Create | Originator: The <MEFBase> resource shall not be created via API. Receiver: Primitive specific operation on Recv-1.0 "Check the syntax of received message": 1) If the request is received, the MEF shall execute the following steps in order: a) "Create an unsuccessful Response primitive" with the Response Status Code indi... |
f46e47df06cd8c6873bddc70686b1058 | 118 132 | 8.2.2.2 Retrieve | Originator: No change from the generic procedures in clause 7.2.2.1 of ETSI TS 118 104 [3] with clarifications discussed in clauses 5.2 and 6. ETSI MAF and MEF Interface Specification 22 oneM2M TS-0032 version 4.0.1 Release 4 Receiver: Same as the generic procedures in clause 7.2.2.2 of [3] with clarifications discusse... |
f46e47df06cd8c6873bddc70686b1058 | 118 132 | 8.2.2.3 Update | Originator: The <MEFBase> resource shall not be updated via API. Receiver: Primitive specific operation on Recv-1.0 "Check the syntax of received message": 1) If the request is received, the MEF shall execute the following steps in order: a) "Create an unsuccessful Response primitive" with the Response Status Code indi... |
f46e47df06cd8c6873bddc70686b1058 | 118 132 | 8.2.2.4 Delete | Originator: The <MEFBase> resource shall not be DELETEed via API. Receiver: Primitive specific operation on Recv-1.0 "Check the syntax of received message": 1) If the request is received, the MEF shall execute the following steps in order: a) "Create an unsuccessful Response primitive" with the Response Status Code ind... |
f46e47df06cd8c6873bddc70686b1058 | 118 132 | 8.3 Resource Type <mafClientReg> | |
f46e47df06cd8c6873bddc70686b1058 | 118 132 | 8.3.1 Introduction | A <mafClientReg> resource shall represent a MAF Client enrolled with the MAF on behalf of an M2M Service Provider or M2M Trust Enabler. A <mafClientReg> resource shall be a child resource of the MAF's <MAFBase> resource. Table 8.3.1-1: Data Type Definition of <mafClientReg> Data Type ID File Name Note mafClientReg SEC-... |
f46e47df06cd8c6873bddc70686b1058 | 118 132 | 8.3.2 <mafClientReg> resource specific procedures on CRUD operations | |
f46e47df06cd8c6873bddc70686b1058 | 118 132 | 8.3.2.1 Create | This procedure is denoted MAF Client Registration in clause 8.8.2.3 of ETSI TS 118 103 [2]. The To parameter of the <mafClientReg> create request primitive includes the MAF-FQDN and the character "–" (dash) as a shorthand notation for the name of the <MAFBase> resource: //{MAF-FQDN}/–/ EXAMPLE: //maf123.mafprovider.org... |
f46e47df06cd8c6873bddc70686b1058 | 118 132 | 8.3.2.2 Retrieve | This procedure is denoted MAF Client Configuration Retrieval in clause 8.8.2.4 of ETSI TS 118 103 [2]. This procedure is used to retrieve the <mafClientReg> resource. Originator: No change from the generic procedures in clause 7.2.2.1 of [3] with clarifications discussed in clauses 5.1.2 and 6.2. Receiver: Same as the ... |
f46e47df06cd8c6873bddc70686b1058 | 118 132 | 8.3.2.3 Update | This procedure is denoted MAF Client Configuration Update in clause 8.8.2.5 of ETSI TS 118 103 [2]. This procedure is used to update attributes of the <mafClientReg> resource, such as e.g. labels, expiration time. Originator: The <mafClientReg> resource shall not be updated by a MAF client via API. ETSI MAF and MEF Int... |
f46e47df06cd8c6873bddc70686b1058 | 118 132 | 8.3.2.4 Delete | This procedure is denoted MAF Client De-Registration in clause 8.8.2.6 of ETSI TS 118 103 [2]. This procedure enables the MAF client to delete its own <mafClientReg> resource on a MAF. Originator: No change from the generic procedures in clause 7.2.2.1 of ETSI TS 118 104 [3] with clarifications discussed in clauses 5.1... |
f46e47df06cd8c6873bddc70686b1058 | 118 132 | 8.4 Resource Type <mefClientReg> | |
f46e47df06cd8c6873bddc70686b1058 | 118 132 | 8.4.1 Introduction | A <mefClientReg> resource shall represent a MEF Client enrolled with the MEF on behalf of an M2M Service Provider or M2M Trust Enabler. A <mefClientReg> resource shall be a child resource of the MEF's <MEFBase> resource. ETSI MAF and MEF Interface Specification 26 oneM2M TS-0032 version 4.0.1 Release 4 Table 8.4.1-1: D... |
f46e47df06cd8c6873bddc70686b1058 | 118 132 | 8.4.2 <mefClientReg> resource specific procedures on CRUD operations | |
f46e47df06cd8c6873bddc70686b1058 | 118 132 | 8.4.2.1 Create | This procedure is denoted MEF Client Registration in clause 8.3.5.2.3 of ETSI TS 118 103 [2]. The To parameter of the <mefClientReg> create request primitive includes the MEF-FQDN and the character "–" (dash) as a shorthand notation for the name of the <MEFBase> resource: //{MEF-FQDN}/–/ EXAMPLE: //mef123.mefprovider.o... |
f46e47df06cd8c6873bddc70686b1058 | 118 132 | 8.4.2.2 Retrieve | This procedure is denoted MEF Client Configuration Retrieval in clause 8.3.5.2.4 of ETSI TS 118 103 [2]. This procedure is used to retrieve the <mefClientReg> resource. Originator: No change from the generic procedures in clause 7.2.2.1 of [3] with clarifications discussed in clauses 5.2.2 and 6.3. Receiver: Same as th... |
f46e47df06cd8c6873bddc70686b1058 | 118 132 | 8.4.2.3 Update | This procedure is denoted MEF Client Configuration Update in clause 8.3.5.2.5 of ETSI TS 118 103 [2]. This procedure is used to update attributes of the <mefClientReg> resource, such as e.g. labels, expiration time. Originator: The <mefClientReg> resource shall not be updated by a MEF client via API. Receiver: Same as ... |
f46e47df06cd8c6873bddc70686b1058 | 118 132 | 8.4.2.4 Delete | This procedure is denoted MEF Client De-Registration in clause 8.3.5.2.6 of ETSI TS 118 103 [2]. This procedure enables the MEF client to delete its own <mefClientReg> resource on a MEF. Originator: No change from the generic procedures in clause 7.2.2.1 of [3] with clarifications discussed in clauses 5.2.2 and 6.3. Re... |
f46e47df06cd8c6873bddc70686b1058 | 118 132 | 8.5 Resource Type <symmKeyReg> | |
f46e47df06cd8c6873bddc70686b1058 | 118 132 | 8.5.1 Introduction | A <symmKeyReg> resource shall represent a symmetric key registered with a MAF or MEF and administrated by the identified administrating stakeholder. A <symmKeyReg> resource shall be a child resource of a <MAFBase> or a <MEFBase> resource. Table 8.5.1-1: Data Type Definition of <symmKeyReg> Data Type ID File Name Note s... |
f46e47df06cd8c6873bddc70686b1058 | 118 132 | 8.5.2 <symmKeyReg> resource specific procedures on CRUD operations | |
f46e47df06cd8c6873bddc70686b1058 | 118 132 | 8.5.2.1 Create | This procedure is denoted MAF Key Registration in clause 8.8.2.7 of ETSI TS 118 103 [2] and MEF Key Registration in clause 8.3.5.2.7 of ETSI TS 118 103 [2]. This procedure enables a Source MAF Client or a Source MEF Client to establish a symmetric key with the MAF or MEF, respectively, which can be retrieved for use by... |
f46e47df06cd8c6873bddc70686b1058 | 118 132 | 8.5.2.2 Retrieve | This procedure is denoted MAF Key Retrieval in clause 8.8.2.8 of ETSI TS 118 103 [2] and MEF Key Retrieval in clause 8.3.5.2.8 of ETSI TS 118 103. It enables a Target MAF Client to retrieve the Key Value from a MAF corresponding to a RelativeKeyID available to the Target MAF Client. Originator: No change from the gener... |
f46e47df06cd8c6873bddc70686b1058 | 118 132 | 8.5.2.3 Update | This procedure is denoted MAF Key Registration Update in clause 8.8.2.9 of ETSI TS 118 103 [2] and MEF Key Registration Update in clause 8.3.5.2.9 of ETSI TS 118 103. It enables a Source MAF Client or Source MEF Client to update the metadata associated with a registered key. Originator: No change from the generic proce... |
f46e47df06cd8c6873bddc70686b1058 | 118 132 | 8.5.2.4 Delete | This procedure is denoted MAF Key De-Registration in clause 8.8.2.10 of ETSI TS 118 103 [2] and MEF Key De- Registration in clause 8.3.5.2.10 of ETSI TS 118 103. It enables a Source MAF Client to request the MAF to stop distributing the registered key. ETSI MAF and MEF Interface Specification 32 oneM2M TS-0032 version ... |
f46e47df06cd8c6873bddc70686b1058 | 118 132 | 8.6 Resource Type <mefClientCmd> | |
f46e47df06cd8c6873bddc70686b1058 | 118 132 | 8.6.1 Introduction | A <mefClientCmd> resource shall represent a command to be indicated to a MEF client by a MEF, and a status report on the attempted parsing and execution of that command to be indicated to the MEF by a MEF Client. The retrieve procedure and update procedure are used for this purpose. Table 8.6.1-1: Data Type Definition ... |
f46e47df06cd8c6873bddc70686b1058 | 118 132 | 8.6.2 <mefClientCmd> resource specific procedures on CRUD operations | |
f46e47df06cd8c6873bddc70686b1058 | 118 132 | 8.6.2.1 Create | Originator: The <mefClientCmd> resource shall not be created via API. It is instantiated by a MEF when the parent <mefClientReg> resource is created as described in clause 8.4.2.1. Receiver: The primitive specific operation on Recv-1.0 "Check the syntax of received message" defined in ETSI TS 118 104 [3] applies: 2) If... |
f46e47df06cd8c6873bddc70686b1058 | 118 132 | 8.6.2.2 Retrieve | This procedure is denoted MEF Client Command Retrieval in clause 8.3.9.2 of ETSI TS 118 103 [2]. This procedure is used to retrieve the <mefClientCmd> resource. Originator: No change from the generic procedures in clause 7.2.2.1 of [3] with clarifications discussed in clauses 5.2.2 and 6.3, and with following differenc... |
f46e47df06cd8c6873bddc70686b1058 | 118 132 | 8.6.2.3 Update | This procedure is denoted MEF Client Command Update in clause 8.3.9.3 of ETSI TS 118 103 [2]. This procedure is used by the MEF Client to report on the status of an issued MEF Client Command, and for an MEF to issue another MEF Client Command. Originator: No change from the generic procedures in clause 7.2.2.1 of [3] w... |
f46e47df06cd8c6873bddc70686b1058 | 118 132 | 8.6.2.4 Delete | Originator: The <mefClientCmd> resource shall not be deleted via API. It is deleted by a MEF when the parent <mefClientReg> resource is deleted. ETSI MAF and MEF Interface Specification 35 oneM2M TS-0032 version 4.0.1 Release 4 Receiver: The primitive specific operation on Recv-1.0 "Check the syntax of received message... |
f46e47df06cd8c6873bddc70686b1058 | 118 132 | 9 Short Names | |
f46e47df06cd8c6873bddc70686b1058 | 118 132 | 9.1 Introduction | The short names are introduced in clause 8.2.1 of ETSI TS 118 104 [3]. The short names in ETSI TS 118 104 [3] shall apply in addition to the short names defined here. |
f46e47df06cd8c6873bddc70686b1058 | 118 132 | 9.2 Security-specific oneM2M Resource attributes | In protocol bindings resource attributes names shall be translated into short names of table 9.2-1 and in table 8.2.3-1 of ETSI TS 118 104 [3]. Table 9.2-1: Security-specific oneM2M Attribute Short Names Attribute Name Occurs in Short Name Notes resourceType All ty* Defined in ETSI TS 118 104 [3]. resourceID All ri* De... |
f46e47df06cd8c6873bddc70686b1058 | 118 132 | 9.3 Security-specific oneM2M Resource types | In protocol bindings resource type names shall be translated into short names of table 9.3-1. ETSI MAF and MEF Interface Specification 36 oneM2M TS-0032 version 4.0.1 Release 4 Table 9.3-1: Security-specific Resource Type Short Names Attribute Name Short Name MAFBase maf MEFBase mef mafClientReg macr mefClientReg mecr ... |
f46e47df06cd8c6873bddc70686b1058 | 118 132 | 9.4 Security-specific oneM2M Complex data type members | In protocol bindings complex data types member names shall be translated into short names of table 9.4-1. NOTE: The member names of the security configuration parameters mefClientRegCfg, mafClientRegCfg, mefKeyRegCfg and mafKeyRegCfg are defined in clause 12.4 of ETSI TS 118 103 [3]. Table 9.4-1: Security-specific oneM... |
882a9535e25bda129ad6471740c0ad69 | 119 134-3 | 1 Scope | The present document defines a number of test suites to assess the interoperability between implementations claiming conformance to extended XAdES signatures as specified in ETSI EN 319 132-2 [2]. The present document defines test suites for each level defined in ETSI EN 319 132-2 [2]. Test suites also cover augmentati... |
882a9535e25bda129ad6471740c0ad69 | 119 134-3 | 2 References | |
882a9535e25bda129ad6471740c0ad69 | 119 134-3 | 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 referenced document (including any amendments) applies. Referenced documents which a... |
882a9535e25bda129ad6471740c0ad69 | 119 134-3 | 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 referenced document (including any amendments) applies. NOTE: While any hyperlinks i... |
882a9535e25bda129ad6471740c0ad69 | 119 134-3 | 3 Definitions, symbols and abbreviations | |
882a9535e25bda129ad6471740c0ad69 | 119 134-3 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in ETSI TR 119 001 [i.2] and the following apply: negative test case: test case either for a signature that is not an extended XAdES signature, or for a signature whose validation according to ETSI EN 319 102-1 [i.4] would not result in TOTAL_PAS... |
882a9535e25bda129ad6471740c0ad69 | 119 134-3 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in ETSI TR 119 001 [i.2] and the following apply: CA Certification Authority CRL Certificate Revocation List OCSP Online Certificate Status Provider TSA Time-Stamping Authority |
882a9535e25bda129ad6471740c0ad69 | 119 134-3 | 4 Overview | This clause describes the overall approach used throughout the present document to specify test suites for extended XAdES signatures as specified in ETSI EN 319 132-2 [2]. ETSI EN 319 132-2 [2] defines eight different levels of extended XAdES signatures. The test suites are defined with different layers reflecting the ... |
882a9535e25bda129ad6471740c0ad69 | 119 134-3 | 5.1 Introduction | Clause 5 presents a test suite for testing interoperability of extended XAdES signatures as specified in in ETSI EN 319 132-2 [2]. |
882a9535e25bda129ad6471740c0ad69 | 119 134-3 | 5.2 Testing interoperability of XAdES-E-BES signatures | This clause presents a test suite for testing interoperability of XAdES-E-BES signatures as specified in in ETSI EN 319 132-2 [2]. The test suite for testing interoperability XAdES-E-BES signatures as specified in ETSI EN 319 132-2 [2] shall include the test cases defined in ETSI TS 119 134-2 [3], clause 5, Table 2 and... |
882a9535e25bda129ad6471740c0ad69 | 119 134-3 | 6.1 Introduction | This clause describes the so called augmentation tests cases. For running them a certain signer generates an extended XAdES signature of a certain level. After that a verifier validates the signature and augments it to a higher level by adding a number of unsigned qualifying properties. Finally, a third entity validate... |
882a9535e25bda129ad6471740c0ad69 | 119 134-3 | 6.2 Augmentation to XAdES-E-C signatures | This clause defines a test suite for augmenting XAdES-E-BES and XAdES-E-T signatures to XAdES-E-C signatures. The test suite is formed by the test cases defined in Table 10. ETSI ETSI TS 119 134-3 V1.1.1 (2016-06) 33 Table 10: Test cases for augmentation to XAdES-E-C signatures TC ID Description Pass criteria Signature... |
882a9535e25bda129ad6471740c0ad69 | 119 134-3 | 6.3 Augmentation to XAdES-E-X signatures | This clause defines a test suite for augmenting XAdES-E-BES, XAdES-E-T, and XAdES-E-C signatures to XAdES-E- X signatures. The test suite is formed by the test cases defined in Table 11. ETSI ETSI TS 119 134-3 V1.1.1 (2016-06) 35 Table 11: Test cases for augmentation to XAdES-E-X signatures TC ID Description Pass crite... |
882a9535e25bda129ad6471740c0ad69 | 119 134-3 | 6.4 Augmentation to XAdES-E-X-L signatures | This clause defines a test suite for augmenting XAdES-E-BES, XAdES-E-T, XAdES-E-C, and XAdES-E-X signatures to XAdES-E-X-L. The test suite is formed by the test cases defined in Table 12. ETSI ETSI TS 119 134-3 V1.1.1 (2016-06) 37 Table 12: Test cases for augmentation to XAdES-E-X-L signatures TC ID Description Pass cr... |
882a9535e25bda129ad6471740c0ad69 | 119 134-3 | 6.3 Augmentation to XAdES-E-A signatures | This clause defines a test suite for augmenting XAdES-E-BES, XAdES-E-T, XAdES-E-C, XAdES-E-X, and XAdES- E-X-L signatures to XAdES-E-A. The test suite is formed by the test cases defined in Table 13. ETSI ETSI TS 119 134-3 V1.1.1 (2016-06) 40 Table 13: Test cases for augmentation to XAdES-E-A signatures TC ID Descripti... |
882a9535e25bda129ad6471740c0ad69 | 119 134-3 | 7 Test suites with negative test cases | |
882a9535e25bda129ad6471740c0ad69 | 119 134-3 | 7.1 Introduction | The present clause define a number of negative test cases for extended XAdES signatures. The present clause distinguishes two different types of negative test cases: 1) Test cases leading to valid signatures that nevertheless, are not XAdES signatures. 2) Test cases leading to extended XAdES signatures whose validation... |
882a9535e25bda129ad6471740c0ad69 | 119 134-3 | 7.2 Test cases generating non XAdES signatures | The test case XAdES/NB/4 defined in ETSI TS 119 134-2 [3] clause 10.2 generates a XML signature that is not a XAdES signature. |
882a9535e25bda129ad6471740c0ad69 | 119 134-3 | 7.3 Test cases for XAdES-E-BES signatures | This clause defines a test suite of negative test cases for XAdES-E-BES signatures. The test suite of negative test cases for XAdES-E-BES signatures as specified in ETSI EN 319 132-2 [2] shall include the test cases defined in ETSI TS 119 134-2 [3], clause10.3 (except test case XAdES/BBN/8, which is a test case for a X... |
882a9535e25bda129ad6471740c0ad69 | 119 134-3 | 7.4 Test cases generating non valid XAdES-E-EPES signatures | This clause defines a test suite of negative test cases for XAdES-E-EPES signatures. The test suite of negative test cases for XAdES-E-EPES signatures as specified in ETSI EN 319 132-2 [2] shall include the test case XAdES/BBN/8 defined in ETSI TS 119 134-2 [3], clause 10.3 and the test cases defined in Table 15. Table... |
882a9535e25bda129ad6471740c0ad69 | 119 134-3 | 7.5 Test cases generating non valid XAdES-E-T signatures | This clause defines a test suite of negative test cases for XAdES-E-T signatures. The test suite of negative test cases for XAdES-E-T signatures as specified in ETSI EN 319 132-2 [2] shall include the test cases defined in ETSI TS 119 134-2 [3], clause10.4 and the test cases defined in Table 16. ETSI ETSI TS 119 134-3 ... |
882a9535e25bda129ad6471740c0ad69 | 119 134-3 | 7.6 Test cases generating non valid XAdES-E-A signatures | This clause defines a test suite of negative test cases for XAdES-E-A signatures. The test suite of negative test cases for XAdES-E-A signatures as specified in ETSI EN 319 132-2 [2] shall include the test cases defined in ETSI TS 119 134-2 [3], clause 10.5 and the test cases defined in Table 17. ETSI ETSI TS 119 134-3... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.