http binding proposals, questions, and examples group name: wg3 source: phillip brown, interdigital...

14
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

Upload: andra-harris

Post on 21-Dec-2015

216 views

Category:

Documents


0 download

TRANSCRIPT

Page 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

HTTP Binding Proposals, Questions, and Examples

Group Name: WG3Source: Phillip Brown, InterDigitalMeeting Date: 2014-07-28 (PRO#12.0)Agenda Item: HTTP Binding

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

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<Document number>

2

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

Example: HTTP Binding of Create <remoteCSE>Request:Method: POST URI: http://cse01.m2m.sp1.com/CSE01Base?rt=remoteCSE&nm=remoteCSE02From: http://cse02.m2m.sp1.comX-M2M-RI: 0001Content-Type: application/xmlContent-Length: length of ContentContent: <remoteCSE> 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 Parameter HTTP 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

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

Response:Status: 201 CreatedX-M2M-RI:0001Location: http://cse01.m2m.sp1.com/CSE01Base/remoteCSE02Content-Type: application/xmlContent-Length: length of ContentContent: <remoteCSE> representation + possible response parametersETag: “7845739”

Example: HTTP Binding of Create <remoteCSE>

*** 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 Parameter HTTP 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

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

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<Document number>

5

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

More Detailed Examples…

The following slides show oneM2M/HTTP Procedures:

1.CSE-CSE Registration/De-Registration2.AE-CSE Registration/De-Registration3.Container Create/Retrieve/Update/Delete

© 2013 oneM2M Partners<Document number>

6

Page 7: HTTP Binding Proposals, Questions, and Examples Group Name: WG3 Source: Phillip Brown, InterDigital Meeting Date: 2014-07-28 (PRO#12.0) Agenda Item: HTTP
Page 8: HTTP Binding Proposals, Questions, and Examples Group Name: WG3 Source: Phillip Brown, InterDigital Meeting Date: 2014-07-28 (PRO#12.0) Agenda Item: HTTP
Page 9: HTTP Binding Proposals, Questions, and Examples Group Name: WG3 Source: Phillip Brown, InterDigital Meeting Date: 2014-07-28 (PRO#12.0) Agenda Item: HTTP
Page 10: HTTP Binding Proposals, Questions, and Examples Group Name: WG3 Source: Phillip Brown, InterDigital Meeting Date: 2014-07-28 (PRO#12.0) Agenda Item: HTTP
Page 11: HTTP Binding Proposals, Questions, and Examples Group Name: WG3 Source: Phillip Brown, InterDigital Meeting Date: 2014-07-28 (PRO#12.0) Agenda Item: HTTP
Page 12: HTTP Binding Proposals, Questions, and Examples Group Name: WG3 Source: Phillip Brown, InterDigital Meeting Date: 2014-07-28 (PRO#12.0) Agenda Item: HTTP
Page 13: HTTP Binding Proposals, Questions, and Examples Group Name: WG3 Source: Phillip Brown, InterDigital Meeting Date: 2014-07-28 (PRO#12.0) Agenda Item: HTTP
Page 14: HTTP Binding Proposals, Questions, and Examples Group Name: WG3 Source: Phillip Brown, InterDigital Meeting Date: 2014-07-28 (PRO#12.0) Agenda Item: HTTP