{"draft":"draft-ietf-core-http-mapping-17","doc_id":"RFC8075","title":"Guidelines for Mapping Implementations: HTTP to the Constrained Application Protocol (CoAP)","authors":["A. Castellani","S. Loreto","A. Rahman","T. Fossati","E. Dijk"],"format":["ASCII","HTML"],"page_count":"40","pub_status":"PROPOSED STANDARD","status":"PROPOSED STANDARD","source":"Constrained RESTful Environments","abstract":"This document provides reference information for implementing a\r\ncross-protocol network proxy that performs translation from the HTTP\r\nprotocol to the Constrained Application Protocol (CoAP).  This will\r\nenable an HTTP client to access resources on a CoAP server through\r\nthe proxy.  This document describes how an HTTP request is mapped to\r\na CoAP request and how a CoAP response is mapped back to an HTTP\r\nresponse.  This includes guidelines for status code, URI, and media\r\ntype mappings, as well as additional interworking advice.","pub_date":"February 2017","keywords":["CoAP","HTTP-CoAP mapping","HTTP-CoAP translation","proxy implementation"],"obsoletes":[],"obsoleted_by":[],"updates":[],"updated_by":[],"see_also":[],"doi":"10.17487\/RFC8075","errata_url":null}