Guidelines for Mapping Implementations: HTTP to the Constrained Application Protocol (CoAP) (RFC8075)
Original Publication Date: 2017-Feb-01
Included in the Prior Art Database: 2017-Mar-01
Internet Society Requests For Comment (RFCs)
A. Castellani: AUTHOR [+5]
The Constrained Application Protocol (CoAP) [RFC7252] has been designed with a twofold aim: it's an application protocol specialized for constrained environments and it's easily used in architectures based on Representational State Transfer (REST) [Fielding], such as the web. The latter goal has led to defining CoAP to easily interoperate with HTTP [RFC7230] through an intermediary proxy that performs cross-protocol conversion.
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)
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.
al. Standards Track [Page 1]
RFC 8075 HTTP-to-CoAP Mapping February 2017
Copyright (c) 2017 IETF Trust and the persons identified as the document au...