Last Call: <draft-ietf-core-http-mapping-13.txt> (Guidelines for HTTP-to-CoAP Mapping Implementations) to Informational RFC

The IESG <iesg-secretary@ietf.org> Mon, 08 August 2016 13:50 UTC

Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: Last Call: <draft-ietf-core-http-mapping-13.txt> (Guidelines for HTTP-to-CoAP Mapping Implementations) to Informational RFC
Auto-Submitted: auto-generated
Precedence: bulk
Sender: iesg-secretary@ietf.org
Message-ID: <147066424374.22974.10556677019154239237.idtracker@ietfa.amsl.com>
Date: Mon, 08 Aug 2016 06:50:43 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/5cRBzBNOXq9rPdiFB0fNxZPD-ow>
Cc: alexey.melnikov@isode.com, Jaime Jimenez <jaime.jimenez@ericsson.com>, core-chairs@ietf.org, core@ietf.org, draft-ietf-core-http-mapping@ietf.org
Reply-To: ietf@ietf.org

The IESG has received a request from the Constrained RESTful Environments
WG (core) to consider the following document:
- 'Guidelines for HTTP-to-CoAP Mapping Implementations'
  <draft-ietf-core-http-mapping-13.txt> as Informational RFC

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2016-08-22. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

Abstract


   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 file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-core-http-mapping/

IESG discussion can be tracked via
https://datatracker.ietf.org/doc/draft-ietf-core-http-mapping/ballot/


No IPR declarations have been submitted directly on this I-D.

Last Call: <draft-ietf-core-http-mapping-13.txt> … The IESG