HTTP Protocol Binding (oneM2M TS- 0009-v1.0.1)

The present document will cover the protocol specific part of communication protocol used by oneM2M compliant systems as RESTful HTTP binding.
The scope of the present document is (not limited to as shown below):
Binding oneM2M Protocol primitive types to HTTP method.
Binding oneM2M response status codes (successful/unsuccessful) to HTTP response codes.
Binding oneM2M RESTful resources to HTTP resources.
The present document is depending on Core Protocol specification (oneM2M TS-0004) for data types.
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 7230 (June 2014): “Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing”.
[2] oneM2M TS-0003: Security Solutions.
[3] oneM2M TS-0004: “Service Layer Core Protocol Specification”.
[4] RFC7235: “Hypertext Transfer Protocol (HTTP/1.1): Authentication”, IETF, June 2014.
[5] RFC6750: “The OAuth 2.0 Authorization Framework: Bearer Token Usage”, October 2012.
[6] oneM2M TS-0011: Common Terminology.
[7] oneM2M TS-0001: Functional Architecture.
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 at http://member.onem2m.org/Static_pages/Others/Rules_Pages/oneM2M-Drafting-Rules V1_0.doc.
[i.2] IETF RFC 2617 (June 1999): “HTTP Authentication: Basic and Digest Access Authentication”.
[i.3] IETF RFC 6750 (October 2012): “The OAuth 2.0 Authorization Framework: Bearer Token Usage”.
[i.4] IETF RFC 6455 (December 2011):”The WebSocket Protocol”.
3 Abbreviations
For the purposes of the present document, the following abbreviations those given in TS-0011-Common Terminology [6] apply:
CSE-ID Common Service Entity Identifier
HTTP Hyper Text Transfer Protocol
TLS Trasport Layer Security
URI Uniform Resource Identifier
4 Conventions
The keywords “Shall”, “Shall not”, “May”, “Need not”, “Should”, “Should not” in this document are to be interpreted as described in the oneM2M Drafting Rules [i.1].
5 Overview of HTTP Binding
This clause describes what oneM2M primitive parameters can be mapped to HTTP request/response messages.