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

Has anyone had a look at this?


> Begin forwarded message:
> 
> From: The IESG <iesg-secretary@ietf.org>
> Subject: Last Call: <draft-ietf-core-http-mapping-13.txt> (Guidelines for HTTP-to-CoAP Mapping Implementations) to Informational RFC
> Date: 8 August 2016 at 11:50:43 PM AEST
> To: "IETF-Announce" <ietf-announce@ietf.org>
> 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
> Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/5cRBzBNOXq9rPdiFB0fNxZPD-ow>
> 
> 
> 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.
> 
> 
> 
> 

--
Mark Nottingham   https://www.mnot.net/

Received on Wednesday, 17 August 2016 02:18:54 UTC