CoAP Protocol Binding (oneM2M TS- 0008-v1.0.1)

1 Scope
The present document will cover the protocol specific part of communication protocol used by oneM2M compliant systems as ‘RESTful CoAP binding’.
The scope of this specification is (not limited to as shown below):
– Binding oneM2M primitives to CoAP messages
– Binding oneM2M Response Status Codes to CoAP Response Codes
– Defining behaviour of a CoAP Client and Server depending on oneM2M parameters
2 References
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.
The following referenced documents are necessary for the application of the present document.
[1] IETF RFC 7252: “The Constrained Application Protocol (CoAP)”.
[2] oneM2M TS-0004: ” Service Layer Core Protocol Specification”.
[3] IETF draft-ietf-core-block-15: “Blockwise transfers in CoAP”.
[4] oneM2M TS-0003: “Security Solutions”.
[5] IETF RFC 6347: “Datagram Transport Layer Security Version 1.2”.
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.
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.
[i.1] oneM2M Drafting Rules.
NOTE: Available http://member.onem2m.org/Static_pages/Others/Rules_Pages/oneM2M-Drafting-RulesV1_0.doc.
3 Abbreviations and acronyms
For the purposes of the present document, the following abbreviations and acronyms apply:
DTLS Datagram Transport Layer Security
HTTP Hyper Text Transfer Protocol
IP Internet Protocol
TCP Transport Control Protocol
TLS Transport Layer Security
TLV Tag – Length – Value (data structure)
4 Conventions
The keywords “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].
5 Overview
The clause describes which features need to be supported in CoAP layer and introduces a message format and several features of CoAP used in this procotol binding specification.
5.1 Required Features
This clause explicitely specifies the required features of the CoAP layer for oneM2M to propery bind oneM2M primitives into CoAP messages.
The 4-byte binary CoAP message header is defined in Section 3 of [1].
Confirmable (CON), Acknowledgement (ACK) and Reset (RST) messages shall be supported. The Reset message is used to send a error message in response to a malformed Confirmable message in CoAP layer.