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

Alexey Melnikov <alexey.melnikov@isode.com> Wed, 17 August 2016 09:15 UTC

Return-Path: <alexey.melnikov@isode.com>
X-Original-To: appsdir@ietfa.amsl.com
Delivered-To: appsdir@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id CC44112D0DA for <appsdir@ietfa.amsl.com>; Wed, 17 Aug 2016 02:15:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.246
X-Spam-Status: No, score=-3.246 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RP_MATCHES_RCVD=-1.247, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=isode.com
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id cW_tbYifEcC0 for <appsdir@ietfa.amsl.com>; Wed, 17 Aug 2016 02:15:25 -0700 (PDT)
Received: from statler.isode.com (Statler.isode.com []) by ietfa.amsl.com (Postfix) with ESMTP id BCAE912D08C for <appsdir@ietf.org>; Wed, 17 Aug 2016 02:15:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1471425323; d=isode.com; s=june2016; i=@isode.com; bh=IYkYi/YAnnkjUMQtwi9m/fMrTEUquyyGBO+ZADw+LXA=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=USBnwqpfxf4mkOV/6HnFr1R5C3F68hb3bwsnYzUGGsPCTkAXgxig5I/us5fUdwgU3bY6IZ 1sSXdKJhAWVx8ji4uzleKFQ1SiX7XOytfOHD5hygys8KqxWIz3XYlZlxe9OnmS0tEXaG1u f1qU+3HYR5ny33lYReKfJrV9SXBKWP0=;
Received: from [] ((unknown) []) by statler.isode.com (submission channel) via TCP with ESMTPSA id <V7QrKwASxxiz@statler.isode.com>; Wed, 17 Aug 2016 10:15:23 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
Date: Wed, 17 Aug 2016 10:26:51 +0100
References: <6480226A-3EDE-42F5-A705-9F4B85528DAC@mnot.net>
To: appsdir@ietf.org
Message-Id: <B20A4CCB-F073-4A87-A1DF-EB8F01CC54A2@isode.com>
X-Mailer: iPhone Mail (13G35)
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary=Apple-Mail-CB6B6805-8F0C-4B73-83A6-AE59F70A5E84
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/appsdir/-GJfw-uoAWeNfcyLUBHLMmBVCZ4>
Subject: [appsdir] Fwd: Last Call: <draft-ietf-core-http-mapping-13.txt> (Guidelines for HTTP-to-CoAP Mapping Implementations) to Informational RFC
X-BeenThere: appsdir@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Apps Area Review List <appsdir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/appsdir>, <mailto:appsdir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/appsdir/>
List-Post: <mailto:appsdir@ietf.org>
List-Help: <mailto:appsdir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/appsdir>, <mailto:appsdir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Aug 2016 09:15:27 -0000

Can I ask somebody with HTTP background to review this?

Begin forwarded message:

> Resent-From: ietf-http-wg@w3.org
> From: Mark Nottingham <mnot@mnot.net>;
> Date: 17 August 2016 at 03:18:25 BST
> To: HTTP Working Group <ietf-http-wg@w3.org>;
> Subject: 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/