1. HTTP Binding Proposals, Questions, and Examples Group Name: WG3 Source: Phillip Brown, InterDigital Meeting Date: 2014-07-28 (PRO#12.0) Agenda Item: HTTP Binding

2. Proposals 1.oneM2M should define a HTTP header field for M2M-Request-ID (e.g. X-M2M-RI) – Would avoid having to decode HTTP Content on intermediate CSEs – Would allow M2M-Request-ID to be carried in HTTP header of both requests and responses in a symmetric fashion – Nicely aligned with CoAP ‘Token’ header option 2.oneM2M should use URI Query String to carry at least rt and nm request parameters – Probably should consider other request parameters as well E.g. rt, nm, ot, rqet, rset, oet, rp, rc, ec, da, gid, fc, Disrestype © 2013 oneM2M Partners 2

3. Example: HTTP Binding of Create Request: Method: POST URI: http://cse01.m2m.sp1.com/CSE01Base?rt=remoteCSE&nm=remoteCSE02 From: http://cse02.m2m.sp1.com X-M2M-RI: 0001 Content-Type: application/xml Content-Length: length of Content Content: representation *** Other optional oneM2M request parameters not shown can be carried in HTTP URI Query String or in oneM2M defined HTTP header fields (e.g. ot, rqet, rset, oet, rp, rc, ec, da, gid, fc, Disrestype) oneM2M Request ParameterHTTP Binding Operation (op)HTTP Method To (to)HTTP URI Resource Type (rt)HTTP URI Query String Parameter (rt) Name (nm)HTTP URI Query String Parameter (nm) From (fr)HTTP From Header Field M2M Request Identifier (ri)New oneM2M HTTP X-M2M-RI Header Field Content (cn)HTTP Content, Content-Length, Content-Type Header Fields

4. Response: Status: 201 Created X-M2M-RI:0001 Location: http://cse01.m2m.sp1.com/CSE01Base/remoteCSE02 Content-Type: application/xml Content-Length: length of Content Content: representation + possible response parameters ETag: “7845739” Example: HTTP Binding of Create *** Other optional oneM2M response parameters not shown can be carried in HTTP Content or possibly oneM2M defined HTTP header fields (e.g. to, from, ot, rset, cs, ra) oneM2M Response ParameterHTTP Binding Response Code (rs)HTTP Method M2M Request Identifier (ri)New oneM2M HTTP X-M2M-RI Header Field Address of Content Created (not currently defined as a oneM2M response parameter) HTTP Location Header Field Content (cn)HTTP Content, Content-Length, Content-Type Header Fields

5. Questions? 1.Should oneM2M consider defining any other HTTP header fields? – E.g. For response parameters that do not map to existing HTTP header fields since responses do not have URI query string like requests 2.Which oneM2M request or response parameters (if any) are better suited to be carried in HTTP content vs. header fields? © 2013 oneM2M Partners 5

6. More Detailed Examples… The following slides show oneM2M/HTTP Procedures: 1.CSE-CSE Registration/De-Registration 2.AE-CSE Registration/De-Registration 3.Container Create/Retrieve/Update/Delete © 2013 oneM2M Partners 6