Movatterモバイル変換


[0]ホーム

URL:


Search RFCs

Advanced Search

RFC Editor

RFC 8075

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

File formats:
icon for text fileicon for PDFicon for HTML
Status:
PROPOSED STANDARD
Authors:
A. Castellani
S. Loreto
A. Rahman
T. Fossati
E. Dijk
Stream:
IETF
Source:
core (wit)

Cite this RFC:TXT  | XML  |  BibTeX

DOI:  https://doi.org/10.17487/RFC8075

Discuss this RFC: Send questions or comments to the mailing listcore@ietf.org

Other actions:Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC 8075


Abstract

This document provides reference information for implementing across-protocol network proxy that performs translation from the HTTPprotocol to the Constrained Application Protocol (CoAP). This willenable an HTTP client to access resources on a CoAP server throughthe proxy. This document describes how an HTTP request is mapped toa CoAP request and how a CoAP response is mapped back to an HTTPresponse. This includes guidelines for status code, URI, and mediatype mappings, as well as additional interworking advice.


For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.




IABIANAIETFIRTFISEISOCIETF Trust
ReportsPrivacy StatementSite MapContact Us

Advanced Search

[8]ページ先頭

©2009-2026 Movatter.jp