RESTful Design for Internet of Things Systems
draft-keranen-t2trg-rest-iot-04
|
| Document |
Type |
|
Active Internet-Draft (individual)
|
|
Last updated |
|
2017-03-13
|
|
Stream |
|
(None)
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
xml
pdf
html
bibtex
|
| Stream |
Stream state |
|
(No stream defined) |
|
Consensus Boilerplate |
|
Unknown
|
|
RFC Editor Note |
|
(None)
|
| IESG |
IESG state |
|
I-D Exists
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
Network Working Group A. Keranen
Internet-Draft Ericsson
Intended status: Informational M. Kovatsch
Expires: September 14, 2017 ETH Zurich
March 13, 2017
RESTful Design for Internet of Things Systems
draft-keranen-t2trg-rest-iot-04
Abstract
This document gives guidance for designing Internet of Things (IoT)
systems that follow the principles of the Representational State
Transfer (REST) architectural style.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on September 14, 2017.
Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Keranen & Kovatsch Expires September 14, 2017 [Page 1]
Internet-Draft RESTful Design for IoT Systems March 2017
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Basics . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
3.1. Architecture . . . . . . . . . . . . . . . . . . . . . . 6
3.2. System design . . . . . . . . . . . . . . . . . . . . . . 7
3.3. Uniform Resource Identifiers (URIs) . . . . . . . . . . . 8
3.4. Representations . . . . . . . . . . . . . . . . . . . . . 9
3.5. HTTP/CoAP Methods . . . . . . . . . . . . . . . . . . . . 9
3.5.1. GET . . . . . . . . . . . . . . . . . . . . . . . . . 10
3.5.2. POST . . . . . . . . . . . . . . . . . . . . . . . . 10
3.5.3. PUT . . . . . . . . . . . . . . . . . . . . . . . . . 10
3.5.4. DELETE . . . . . . . . . . . . . . . . . . . . . . . 11
3.6. HTTP/CoAP Status/Response Codes . . . . . . . . . . . . . 11
4. REST Constraints . . . . . . . . . . . . . . . . . . . . . . 12
4.1. Client-Server . . . . . . . . . . . . . . . . . . . . . . 12
4.2. Stateless . . . . . . . . . . . . . . . . . . . . . . . . 12
4.3. Cache . . . . . . . . . . . . . . . . . . . . . . . . . . 13
4.4. Uniform Interface . . . . . . . . . . . . . . . . . . . . 13
4.5. Layered System . . . . . . . . . . . . . . . . . . . . . 14
4.6. Code-on-Demand . . . . . . . . . . . . . . . . . . . . . 14
5. Security Considerations . . . . . . . . . . . . . . . . . . . 14
6. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 14
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 15
7.1. Normative References . . . . . . . . . . . . . . . . . . 15
7.2. Informative References . . . . . . . . . . . . . . . . . 16
Appendix A. Future Work . . . . . . . . . . . . . . . . . . . . 17
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 17
1. Introduction
The Representational State Transfer (REST) architectural style [REST]
is a set of guidelines and best practices for building distributed
hypermedia systems. At its core is a set of constraints, which when
fulfilled enable desirable properties for distributed software
systems such as scalability and modifiability. When REST principles
are applied to the design of a system, the result is often called
RESTful and in particular an API following these principles is called
a RESTful API.
Different protocols can be used with RESTful systems, but at the time
Show full document text