API Build-data JSON Resources
Theme

Choose how MSRBot.io looks on this device.

Auto (match system) Light mode Dark mode

Preference is stored in this browser only.

IETF RFC 8075
[ACTIVE]

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

Metadata

Publisher
IETF
Doc Type
Standard
Pages
40
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.
Publication Date
2017-02-01
Status Note
Proposed Standard
DOI
10.17487/RFC8075
Link
https://doi.org/10.17487/RFC8075
Author(s)
Angelo P. Castellani
Salvatore Loreto
Akbar Rahman
Thomas Fossati
Esko Dijk
Keyword(s)
CoAP, HTTP-CoAP Mapping, HTTP-CoAP Translation, Proxy Implementation
Latest version of IETF RFC 8075

Document Versions — IETF RFC 8075

  • ▶ IETF RFC 8075 (2017-02-01)
    THIS DOC [ACTIVE] [LATEST VERSION]

Normative Reference(s)

Bibliographic Reference(s)

Source Data (JSON)

Full registry record with provenance metadata. Open directly: /api/doc/RFC8075.json

Reference Tree

Explore all references and references to this document, as a navigable tree.

Open Reference Tree
Reference this Doc

Plain text (ISO 690 compliant)

Preview:
IETF RFC 8075, Guidelines for Mapping Implementations: HTTP to the Constrained Application Protocol (CoAP). Available at https://doi.org/10.17487/RFC8075
Snippet:
IETF RFC 8075, Guidelines for Mapping Implementations: HTTP to the Constrained Application Protocol (CoAP). Available at https://doi.org/10.17487/RFC8075

HTML (ISO 690 compliant)

Preview:
IETF RFC 8075, Guidelines for Mapping Implementations: HTTP to the Constrained Application Protocol (CoAP). Available at https://doi.org/10.17487/RFC8075
Snippet:
<span class="citation"><cite>IETF RFC 8075</cite>, Guidelines for Mapping Implementations: HTTP to the Constrained Application Protocol (CoAP). Available at <a href="https://doi.org/10.17487/RFC8075" target="_blank" rel="noopener">https://doi.org/10.17487/RFC8075</a></span>

SMPTE Icon SMPTE's HTML Pub

Preview:
IETF RFC 8075, Guidelines for Mapping Implementations: HTTP to the Constrained Application Protocol (CoAP)
doi: 10.17487/RFC8075
url: https://doi.org/10.17487/RFC8075
Snippet:
<li>
<cite id="bib-rfc8075">IETF RFC 8075</cite>, Guidelines for Mapping Implementations: HTTP to the Constrained Application Protocol (CoAP)
<span class="doi">10.17487/RFC8075</span>
</li>

Referenced By