oneM2M TS-0009Release Notes diff from v5.1.0 to v5.1.0References 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] IETF RFC 7235 (June 2014): "Hypertext Transfer Protocol (HTTP/1.1): Authentication".
[5] IETF RFC 6750 (October 2012): "The Oauth 2.0 Authorization Framework: Bearer Token Usage".
[6] oneM2M TS-0011: Common Terminology.
[7] oneM2M TS-0001: Functional Architecture.
[8] IETF RFC 7232 (June 2014): "Hypertext Transfer Protocol (HTTP/1.1): "Conditional Requests".
[9] IETF RFC 3986 (January 2005): "Uniform Resource Identifier (URI): Generic Syntax".
[10] IETF RFC 7231 (June 2014): "HTTP/1.1 Semantics and Content"
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://www.onem2m.org/images/files/oneM2M-Drafting-Rules.pdf.
[i.2] Void
[i.3] Void
[i.4] IETF RFC 6455 (December 2011):"The WebSocket Protocol".
[i.5] Void