Guidelines for Mapping Implementations: HTTP to the Constrained Application Protocol (CoAP)
RFC 8075
|
| Document |
Type |
|
RFC - Proposed Standard
(February 2017; No errata)
|
|
Last updated |
|
2017-02-28
|
|
Replaces |
|
draft-castellani-core-http-mapping
|
|
Stream |
|
IETF
|
|
Formats |
|
plain text
pdf
html
bibtex
|
|
Reviews |
|
GENART,
RTGDIR
will not review this version
|
| Stream |
WG state
|
|
Submitted to IESG for Publication
(wg milestone:
Jul 2016 - Best Practices for H...
)
|
|
Document shepherd |
|
Jaime Jimenez
|
|
Shepherd write-up |
|
Show
(last changed 2016-07-22)
|
| IESG |
IESG state |
|
RFC 8075 (Proposed Standard)
|
|
Consensus Boilerplate |
|
Yes
|
|
Telechat date |
|
|
|
Responsible AD |
|
Alexey Melnikov
|
|
Send notices to |
|
"Jaime Jimenez" <jaime.jimenez@ericsson.com>
|
| IANA |
IANA review state |
|
IANA OK - Actions Needed
|
|
IANA action state |
|
RFC-Ed-Ack
|
Internet Engineering Task Force (IETF) A. Castellani
Request for Comments: 8075 University of Padova
Category: Standards Track S. Loreto
ISSN: 2070-1721 Ericsson
A. Rahman
InterDigital Communications, LLC
T. Fossati
Nokia
E. Dijk
Philips Lighting
February 2017
Guidelines for Mapping Implementations:
HTTP to the Constrained Application Protocol (CoAP)
Abstract
This document provides reference information for implementing a
cross-protocol network proxy that performs translation from the HTTP
protocol to the Constrained Application Protocol (CoAP). This will
enable an HTTP client to access resources on a CoAP server through
the proxy. This document describes how an HTTP request is mapped to
a CoAP request and how a CoAP response is mapped back to an HTTP
response. This includes guidelines for status code, URI, and media
type mappings, as well as additional interworking advice.
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 7841.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc8075.
Castellani, et al. Standards Track [Page 1]
RFC 8075 HTTP-to-CoAP Mapping February 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.
Castellani, et al. Standards Track [Page 2]
RFC 8075 HTTP-to-CoAP Mapping February 2017
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5
3. HTTP-to-CoAP Proxy . . . . . . . . . . . . . . . . . . . . . 6
4. Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . . 7
5. URI Mapping . . . . . . . . . . . . . . . . . . . . . . . . . 7
5.1. URI Terminology . . . . . . . . . . . . . . . . . . . . . 8
5.2. Null Mapping . . . . . . . . . . . . . . . . . . . . . . 9
5.3. Default Mapping . . . . . . . . . . . . . . . . . . . . . 9
5.3.1. Optional Scheme Omission . . . . . . . . . . . . . . 9
5.3.2. Encoding Caveats . . . . . . . . . . . . . . . . . . 10
5.4. URI Mapping Template . . . . . . . . . . . . . . . . . . 10
5.4.1. Simple Form . . . . . . . . . . . . . . . . . . . . . 10
5.4.2. Enhanced Form . . . . . . . . . . . . . . . . . . . . 12
5.5. Discovery . . . . . . . . . . . . . . . . . . . . . . . . 13
5.5.1. Examples . . . . . . . . . . . . . . . . . . . . . . 14
6. Media Type Mapping . . . . . . . . . . . . . . . . . . . . . 15
6.1. Overview . . . . . . . . . . . . . . . . . . . . . . . . 15
6.2. 'application/coap-payload' Media Type . . . . . . . . . . 16
6.3. Loose Media Type Mapping . . . . . . . . . . . . . . . . 17
6.4. Media Type to Content-Format Mapping Algorithm . . . . . 18
6.5. Content Transcoding . . . . . . . . . . . . . . . . . . . 19
6.5.1. General . . . . . . . . . . . . . . . . . . . . . . . 19
6.5.2. CoRE Link Format . . . . . . . . . . . . . . . . . . 20
6.6. Diagnostic Payloads . . . . . . . . . . . . . . . . . . . 20
Show full document text