RFC8075 · Guidelines for Mapping Implementations: HTTP to the Constrained Application Protocol (CoAP)
Guidelines for Mapping Implementations: HTTP to the Constrained Application Protocol (CoAP)
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.
IETF · RFCОфициальная английская аннотация
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.
{
"id": "RFC8075",
"number": 8075,
"title_en": "Guidelines for Mapping Implementations: HTTP to the Constrained Application Protocol (CoAP)",
"title_ru": "",
"summary_ru": "",
"purpose_ru": "",
"use_ru": "",
"full_translation_path": "",
"full_translation_checked_at": "",
"full_translation_source_sha256": "",
"architect_note_ru": "",
"topics_ru": [],
"translation_state": "not_prepared",
"verification_level": "not_prepared",
"verification_level_ru": "Русская выжимка не подготовлена",
"verification_note_ru": "",
"abstract_en": "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.",
"authors": [
"A. Castellani",
"S. Loreto",
"A. Rahman",
"T. Fossati",
"E. Dijk"
],
"organizations": [],
"publication_date": "2017-02-01",
"current_status": "PROPOSED STANDARD",
"current_status_ru": "Предлагаемый стандарт",
"publication_status": "PROPOSED STANDARD",
"publication_status_ru": "Предлагаемый стандарт",
"lifecycle": "active",
"lifecycle_ru": "Действующий",
"stream": "IETF",
"stream_ru": "IETF",
"area": "wit",
"area_ru": "Веб и транспорт Интернета",
"working_group": "core",
"source_draft": "draft-ietf-core-http-mapping-17",
"page_count": 40,
"doi": "10.17487/RFC8075",
"keywords": [
"CoAP",
"HTTP-CoAP mapping",
"HTTP-CoAP translation",
"proxy implementation"
],
"formats": [
"TXT",
"HTML"
],
"relations": {
"obsoletes": [],
"obsoleted_by": [],
"updates": [],
"updated_by": [],
"is_also": [],
"see_also": []
},
"links": {
"info": "https://www.rfc-editor.org/info/rfc8075/",
"html": "https://www.rfc-editor.org/rfc/rfc8075.html",
"txt": "https://www.rfc-editor.org/rfc/rfc8075.txt",
"datatracker": "https://datatracker.ietf.org/doc/rfc8075/"
}
}