Proper formatting and latest version: http://jaimejim.github.io/temp/draft-ietf-core-http-mapping#shepherd-writeup
Document Shepherd: [Jaime Jiménez](firstname.lastname@example.org)
Area Director: [Alexey Melnikov](email@example.com)
This document provides reference information for implementing a cross-protocol network proxy that performs translation from the HTTP protocol to the CoAP protocol. This will enable a HTTP client to access resources on a CoAP server through the proxy. This document describes how a HTTP request is mapped to a CoAP request, and then how a CoAP response is mapped back to a HTTP response. This includes guidelines for URI mapping, media type mapping and additional proxy implementation issues. This document covers the Reverse, Forward and Interception cross-protocol proxy cases.
The document is intended as an Informational RFC.
###Review and Consensus
The document has gone through multiple expert reviews over the years and was last presented on IETF95.
There are several implementations available:
1. Squid HTTP-CoAP mapping module, Angelo Castellani. <http://telecom.dei.unipd.it/iot>
2. HTTP-CoAP proxy based on EvCoAP, Thomas Fossati, and Salvatore Loreto. <https://github.com/koanlogic/webthings/tree/master/bridge/sw/lib/evcoap>
3. FIWARE (Ericsson) implementation. <https://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/Gateway_Device_Management_-_Ericsson_Gateway_-_User_and_Programmers_Guide#HTTP-CoAP_mapping>
4. Oliver Kleine implementation, <https://media.itm.uni-luebeck.de/people/kleine/poster_kleine_ssp.pdf> available here: <http://core.ietf.narkive.com/d4MCPLLl/http-coap-proxy-setup>
5. Californium uses the default URI Mapping (section 5.3): <http://example.org/proxy/coap://coap.example.org>
Each author has stated that they do not have direct, personal knowledge of any IPR related to this document. I am not aware of any IPR discussion about this document on the CoRE WG.
Appendix-A should be removed before publication. <https://tools.ietf.org/html/draft-ietf-core-http-mapping-12#appendix-A>
On the IANA section, the part that describes `Interoperability considerations:
Published specification: (this I-D - TBD)` should be updated with the `RFCXXXX` reference.
Few changes since the shepherds review, see: <https://tools.ietf.org//rfcdiff?url1=https://tools.ietf.org/id/draft-ietf-core-http-mapping-10.txt&url2=https://tools.ietf.org/id/draft-ietf-core-http-mapping-13.txt>
The working group has very good consensus on this document as it is. HTTP mapping aspects raised by future CoAP extensions will then be addressed by these extensions or in separate documents.
* [x] Does the shepherd stand behind the document and think the document is ready for publication?
* [x] Is the correct RFC type indicated in the title page header?
* [x] Is the abstract both brief and sufficient, and does it stand alone as a brief summary?
* [x] Is the intent of the document accurately and adequately explained in the introduction?
* [x] Have all required formal reviews (MIB Doctor, Media Type, URI, etc.) been requested and/or completed?
Yes, some edits have been done, see https://tools.ietf.org//rfcdiff?url1=https://tools.ietf.org/id/draft-ietf-core-http-mapping-10.txt&url2=https://tools.ietf.org/id/draft-ietf-core-http-mapping-13.txt
* [x] Has the shepherd performed automated checks -- idnits (see http://www.ietf.org/tools/idnits/ and the Internet-Drafts Checklist), checks of BNF rules, XML code and schemas, MIB definitions, and so on -- and determined that the document passes the tests?
No errors, but some warnings are shown about existing ABNF.
I aggregated all CoAP ABNF refs here: http://jaimejim.github.io/temp/coap-abnf
* [x] Has each author stated that their direct, personal knowledge of any IPR related to this document has already been disclosed, in conformance with BCPs 78 and 79?
* [x] Have all references within this document been identified as either normative or informative, and does the shepherd agree with how they have been classified?
* [x] Are all normative references made to documents that are ready for advancement and are otherwise in a clear state?
Clear state, but non-Standard reference
* [x] If publication of this document changes the status of any existing RFCs, are those RFCs listed on the title page header, and are the changes listed in the abstract and discussed (explained, not just mentioned) in the introduction? ```Does not apply```
* [x] If this is a "bis" document, have all of the errata been considered? ```Does not apply```
* IANA Considerations:
* [x] Are the IANA Considerations clear and complete? Remember that IANA have to understand unambiguously what's being requested, so they can perform the required actions.
* [x] Are all protocol extensions that the document makes associated with the appropriate reservations in IANA registries?
* [x] Are all IANA registries referred to by their exact names (check them in http://www.iana.org/protocols/ to be sure)?
* [x] Have you checked that any registrations made by this document correctly follow the policies and procedures for the appropriate registries?
* [x] For registrations that require expert review (policies of Expert Review or Specification Required), have you or the working group had any early review done, to make sure the requests are ready for last call?
* [x] For any new registries that this document creates, has the working group actively chosen the allocation procedures and policies and discussed the alternatives?
```No registries are created. ```
* [x] Have reasonable registry names been chosen (that will not be confused with those of other registries), and have the initial contents and valid value ranges been clearly specified? ```No registries are created.```