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

Slides:



Advertisements
Similar presentations
XPointer and HTTP Range A possible design for a scalable and extensible RDF Data Access protocol. Bryan Thompson draft Presented to the RDF.
Advertisements

Call for test suites Group Name: REQ Source: Jiaxin Yin, Huawei Technologies Co., Ltd., Meeting Date: Agenda Item: TBD.
Summary on the M2M CMDH Policies Management Object (MCMDHMO)
Problem of Current Notification Group Name: ARC WG Source: Heedong Choi, LG Electronics, Meeting Date: ARC 9.0 Agenda Item: TBD.
WG 3 Progress Report at TP12 Group Name: oneM2M TP12 Source: Raymond Forbes, LM Ericsson, Meeting Date: to
Problem of non-Blocking Synchronous mode Group Name: ARC WG Source: Yuan Tao, Mitch Tseng, Huawei Technologies Meeting Date: ARC 15.0 Agenda Item: TBD.
CS320 Web and Internet Programming Generating HTTP Responses
REST API versioning Group Name: ARC/PRO
Client, Server, HTTP, IP Address, Domain Name. Client-Server Model Client Bob Yahoo Server yahoo.com/finance.html A text file named finance.html.
CGI Programming: Part 1. What is CGI? CGI = Common Gateway Interface Provides a standardized way for web browsers to: –Call programs on a server. –Pass.
Resource Announcement Procedures Group Name: WG2 Source: Rajesh Bhalla, Hao Wu - ZTE Meeting Date: Agenda Item: TBD.
2-levels Access control for HTTP binding Group Name: WG4 (& WG2/WG3 for information) Source: Shingo Fujimoto, FUJITSU, Meeting.
GET Examples – db.org/sops/3/experimental_conditions/55http://seek.sysmo- db.org/sops/3/experimental_conditions/55 –
Discussions for oneM2M Semantics Standardization Group Name: WG5 Source: InterDigital Communications Meeting Date: Agenda Item: WI-0005 ASN/MN-CSE.
CollectionSpace Service REST-based APIs June 2009 Face-to-face Aron Roberts U.C. Berkeley IST/Data Services.
Thoughts on oneM2M resource tree Group Name: WG2 Architecture at TP#7 (Sophia, October 2013) Source: Nicolas Damour, Sierra Wireless
OneM2M-ARC Enhancement_on_resources Some thoughts on oneM2M resources Group Name: WG2 Source: Norio Uchida, NEC, Barbara.
Introduction of PRO WG activities Group Name: TP Source: Shingo Fujimoto, FUJITSU, Meeting Date: Agenda Item:
PRO R01-URI_mapping_discussion Discussion on URI mapping in protocol context Group Name: PRO and ARC Source: Shingo Fujimoto, FUJITSU,
Introduction to the SharePoint 2013 REST API. 2 About Me SharePoint Solutions Architect at Sparkhound in Baton Rouge
Web Server Design Week 8 Old Dominion University Department of Computer Science CS 495/595 Spring 2010 Martin Klein 3/3/10.
Management of CMDH Policies Group Name: WG5-MAS Source: Wolfgang Granzow, Qualcomm, Meeting Date: Agenda Item: Management.
App-ID Discussion Group Name: ARC WG Source: Seongyoon Kim, LG Electronics, Meeting Date: 31 July 2014 Agenda Item: TBD.
Web Server Design Assignment #1: Basic Operations Due: 02/03/2010 Old Dominion University Department of Computer Science CS 495/595 Spring 2010 Martin.
Response Status Codes Concepts for oneM2M Group Name: WG3 Source: Philip Jacobs, Cisco, Meeting Date: Agenda Item: TS-0004.
Supporting long polling Group Name: ARC WG Source: SeungMyeong, LG Electronics, Meeting Date: x-xx Agenda Item: TBD.
Customized Resource Types MAS Group Name: MAS + ARC + PRO WGs Source: Wolfgang Granzow, Qualcomm Inc., Meeting Date:
Discussion on the problem of non- Blocking Synchronous mode Group Name: ARC WG Source: Yuan Tao, Mitch Tseng, Huawei Technologies Meeting Date: ARC 15.2.
Web Server Design Assignment #2: Conditionals & Persistence Due: 02/24/2010 Old Dominion University Department of Computer Science CS 495/595 Spring 2010.
Appendix E: Overview of HTTP ©SoftMoore ConsultingSlide 1.
Matching Resources with CSFs Group Name: WG2 (ARC) Source: Hongbeom Ahn, LG Electronics, Meeting Date:
WG 3 Progress Report at TP15 Group Name: oneM2M TP15 Source: Raymond Forbes, LM Ericsson, Meeting Date: to
Ontology Resource Discussion
Ontology Architectural Support Options Group Name: MAS WG Source: Catalina Mladin, Lijun Dong, InterDigital Meeting Date: Agenda Item: TBD.
RESTful Web Services What is RESTful?
Management of Semantic Instances in resources using SPARQL update operation with HTTP verbs Group Name: MAS 19 Source: Minwoo Ryu, jaeho Kim, Sungchan.
RESTful Studies Services Jim Philbin American College of Radiology Johns Hopkins School of Medicine DICOM Standard Committee, User Co-Chair DICOM WG-27,
HTTP protocol Java Servlets. HTTP protocol Web system communicates with end-user via HTTP protocol HTTP protocol methods: GET, POST, HEAD, PUT, OPTIONS,
WG-2 - ARC TP #18 Status Report Group Name: oneM2M TP #18 Source: WG2 Chair (Nicolas Damour – Meeting Date: Agenda.
PRO/ARC and TST/PRO joint sessions at TP20 Group Name: oneM2M TP20 Source: Peter Niblett, IBM Meeting Date:
Web Server Design Week 6 Old Dominion University Department of Computer Science CS 495/595 Spring 2010 Martin Klein 2/17/10.
WG5 – MAS#19 Status Report Group Name: WG5 MAS (Management, Abstraction & Semantics) Source: Yongjing Zhang (Huawei, WG5 Chair) Meeting Date:
Protocol Issues related to Plugtest Group Name: TST Source: Wolfgang Granzow, Qualcomm Inc., Meeting Date: Agenda.
Web Server Design Assignment #5: Unsafe Methods & CGI Due: 05/05/2010 Old Dominion University Department of Computer Science CS 495/595 Spring 2010 Martin.
SEC #11 WG4 Status & Release 1 Outlook Group Name: Source:,, Meeting Date: Agenda Item:
Template proposal Group Name: PRO Source: Barbara PAreglio, NEC, Meeting Date: Agenda Item: input contribution.
WG2 PRO Status Report at TP19 Group Name: oneM2M TP19 Source: Peter Niblett, IBM Meeting Date: to Agenda Item: TP19, Item 10.3, Reports.
Call for input from WGs on things to test Group Name: TST Source: Jiaxin Yin, Huawei Technologies Co., Ltd., Meeting Date:
Adding Non-blocking Requests Contribution: oneM2M-ARC-0441R01R01 Source: Josef Blanz, Qualcomm UK, Meeting Date: ARC 7.0,
Protocol Issues related to Plugtest Group Name: TST Source: Wolfgang Granzow, Qualcomm Inc., Meeting Date: Agenda.
Subscription and Notification Issue Group Name: WG2 Source: Qi Yu, Mitch Tseng- Huawei Technologies, Co. LTD. Meeting Date: ~23 Agenda Item:
Discussion of open issues for WebSocket binding Group Name: PRO WG Source: Qualcomm Inc., Wolfgang Granzow, Nobu Uchida Meeting Date: PRO#22,
Possible Solution of Interworking between oneM2M and OSGi
Discussion for Testing related Activities Group Name: TP Source: JaeSeung Song, KETI, Meeting Date: Agenda.
TS-0004 guideline for new resource type definition Group Name: PRO WG Source: SeungMyeong JEONG, LG Electronics Meeting Date: Agenda Item: TS.
Methods of Work Report Group Name: TP#10 Source: Enrico Scarrone, Telecom Italia, Meeting.
Joint PRO/ARC session at TP20 Group Name: oneM2M TP20 Source: Peter Niblett, IBM Meeting Date:
Call to Action To increase market adoption of oneM2M, more publically available CSEs, AEs, tools and guides are needed for developers and systems integrators.
[authenticationProfile] <mgmtObj> specialization
oneM2M interop 3 issues and optimizations
Thoughts on Architecture for the Internet of Things
MIME Type Definition Group Name: PRO WG
Group multicast fanOut Procedure
oneM2M Service Layer Protocol Version Handling
MAF&MEF Interface Specification discussion of the next steps
Considering issues regarding handling token
Service Layer Dynamic Authorization [SLDA]
Change Proposals for SHAKEN Documents
BINDing URIs to SIP AORs
Presentation transcript:

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

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

Example: HTTP Binding of Create Request: Method: POST URI: From: 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

Response: Status: 201 Created X-M2M-RI:0001 Location: Content-Type: application/xml Content-Length: length of Content Content: representation + possible response parameters ETag: “ ” 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

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

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