Skip to main content

Guidelines for Mapping Implementations: HTTP to the Constrained Application Protocol (CoAP)
RFC 8075

Revision differences

Document history

Date By Action
2017-02-28
(System)
Received changes through RFC Editor sync (created alias RFC 8075, changed title to 'Guidelines for Mapping Implementations: HTTP to the Constrained Application Protocol (CoAP)', …
Received changes through RFC Editor sync (created alias RFC 8075, changed title to 'Guidelines for Mapping Implementations: HTTP to the Constrained Application Protocol (CoAP)', changed abstract to '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.', changed pages to 40, changed standardization level to Proposed Standard, changed state to RFC, added RFC published event at 2017-02-28, changed IESG state to RFC Published)
2017-02-28
(System) RFC published