W3C home > Mailing lists > Public > ietf-http-wg@w3.org > October to December 2016

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

From: Mark Nottingham <mnot@mnot.net>
Date: Tue, 29 Nov 2016 11:30:01 +1100
Message-Id: <D2C4C74D-2DA4-41EE-A07C-14938342AF79@mnot.net>
To: HTTP Working Group <ietf-http-wg@w3.org>
FYI. Has anyone here reviewed yet?


> Begin forwarded message:
> From: The IESG <iesg-secretary@ietf.org>
> Subject: Last Call: <draft-ietf-core-http-mapping-17.txt> (Guidelines for HTTP-to-CoAP Mapping Implementations) to Informational RFC
> Date: 29 November 2016 at 6:08:39 am AEDT
> To: "IETF-Announce" <ietf-announce@ietf.org>
> Cc: alexey.melnikov@isode.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/Nr9Ds78Buln0dM70oVFz9rCbTGw>
> 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-17.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-12-12. 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.
> This is a Second IETF LC for the document. The document was initially
> targeted at Informational, but is now targeting to become Proposed Standard.
> Abstract
>   This document provides reference information for implementing a
>   cross-protocol network proxy that performs translation from the HTTP
>   protocol to CoAP (Constrained Application Protocol).  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 then 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.
> 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 Tuesday, 29 November 2016 00:30:36 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 29 November 2016 00:30:44 UTC