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

The IESG <> Mon, 28 November 2016 19:08 UTC

Return-Path: <>
Received: from (localhost [IPv6:::1]) by (Postfix) with ESMTP id D58C1129F8F; Mon, 28 Nov 2016 11:08:39 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <>
To: IETF-Announce <>
Subject: Last Call: <draft-ietf-core-http-mapping-17.txt> (Guidelines for HTTP-to-CoAP Mapping Implementations) to Informational RFC
X-Test-IDTracker: no
X-IETF-IDTracker: 6.38.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <>
Date: Mon, 28 Nov 2016 11:08:39 -0800
Archived-At: <>
X-Mailman-Version: 2.1.17
List-Id: "IETF announcement list. No discussions." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 28 Nov 2016 19:08:40 -0000

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 mailing lists by 2016-12-12. Exceptionally, comments may be
sent to 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.


   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

IESG discussion can be tracked via

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