Guidelines for Mapping Implementations: HTTP to the Constrained Application Protocol
RFC 8075, “Guidelines for Mapping Implementations: HTTP to the Constrained Application Protocol”, is a Proposed Standard document published in February 2017 by A. Castellani, S. Loreto, A. Rahman, T. Fossati, E. Dijk. The canonical text is published by the RFC Editor.
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.
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 8075 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 8074 Source Address Validation Improvement for Mixed Address Assignment Methods Scenario
- RFC 8076 A Usage for Shared Resources in RELOAD
- RFC 8073 Coordinating Attack Response at Internet Scale Workshop Report
- RFC 8077 Pseudowire Setup and Maintenance Using the Label Distribution Protocol
- RFC 8072 YANG Patch Media Type
- RFC 8078 Managing DS Records from the Parent via CDS/CDNSKEY
- RFC 8071 NETCONF Call Home and RESTCONF Call Home
- RFC 8079 Guidelines for End-to-End Support of the RTP Control Protocol in Back-to-Back User Agents