[core] Update to draft-ietf-core-http-mapping-06
"Dijk, Esko" <esko.dijk@philips.com> Tue, 10 March 2015 12:58 UTC
Return-Path: <esko.dijk@philips.com>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EFDBD1A8854 for <core@ietfa.amsl.com>; Tue, 10 Mar 2015 05:58:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iYbov-ZMcoh1 for <core@ietfa.amsl.com>; Tue, 10 Mar 2015 05:58:41 -0700 (PDT)
Received: from emea01-am1-obe.outbound.protection.outlook.com (mail-am1on0734.outbound.protection.outlook.com [IPv6:2a01:111:f400:fe00::734]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3E1A81A87A8 for <core@ietf.org>; Tue, 10 Mar 2015 05:58:41 -0700 (PDT)
Received: from DBXPR04CA0041.eurprd04.prod.outlook.com (10.141.8.169) by DB4PR04MB489.eurprd04.prod.outlook.com (10.141.238.140) with Microsoft SMTP Server (TLS) id 15.1.106.15; Tue, 10 Mar 2015 12:58:20 +0000
Received: from DB3FFO11FD055.protection.gbl (2a01:111:f400:7e04::151) by DBXPR04CA0041.outlook.office365.com (2a01:111:e400:9414::41) with Microsoft SMTP Server (TLS) id 15.1.106.15 via Frontend Transport; Tue, 10 Mar 2015 12:58:20 +0000
Received: from mail.philips.com (206.191.242.68) by DB3FFO11FD055.mail.protection.outlook.com (10.47.217.127) with Microsoft SMTP Server (TLS) id 15.1.112.13 via Frontend Transport; Tue, 10 Mar 2015 12:58:19 +0000
Received: from AMSPRD9003MB066.MGDPHG.emi.philips.com ([169.254.5.132]) by AMSPRD9003HT002.MGDPHG.emi.philips.com ([141.251.33.79]) with mapi id 14.16.0478.000; Tue, 10 Mar 2015 12:58:18 +0000
From: "Dijk, Esko" <esko.dijk@philips.com>
To: "core@ietf.org" <core@ietf.org>
Thread-Topic: Update to draft-ietf-core-http-mapping-06
Thread-Index: AdBbMLsIwXbDoNTTQeeZFo0vlNx7mQ==
Date: Tue, 10 Mar 2015 12:58:18 +0000
Message-ID: <031DD135F9160444ABBE3B0C36CED61839AE6465@AMSPRD9003MB066.MGDPHG.emi.philips.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [83.85.143.215]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EOPAttributedMessage: 0
Received-SPF: None (protection.outlook.com: philips.com does not designate permitted sender hosts)
Authentication-Results: spf=none (sender IP is 206.191.242.68) smtp.mailfrom=esko.dijk@philips.com; ietf.org; dkim=none (message not signed) header.d=none;
X-Forefront-Antispam-Report: CIP:206.191.242.68; CTRY:US; IPV:NLI; EFV:NLI; BMV:1; SFV:NSPM; SFS:(10019020)(6009001)(428002)(189002)(199003)(13464003)(377424004)(85714005)(374574003)(23726002)(62966003)(450100001)(77156002)(92566002)(87936001)(55846006)(19580395003)(19580405001)(6806004)(1720100001)(230783001)(2420400003)(104016003)(102836002)(2656002)(15975445007)(2900100001)(2920100001)(46102003)(50986999)(97756001)(86362001)(101416001)(54356999)(33656002)(561944003)(105586002)(106466001)(2351001)(110136001)(47776003)(50466002)(2930100002)(46406003)(107886001)(229853001)(66066001)(2501003)(567094001); DIR:OUT; SFP:1102; SCL:1; SRVR:DB4PR04MB489; H:mail.philips.com; FPR:; SPF:None; MLV:sfv; MX:1; A:1; LANG:en;
X-Microsoft-Antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:DB4PR04MB489;
X-Microsoft-Antispam-PRVS: <DB4PR04MB489C41328C4FA0713EE27E0F2180@DB4PR04MB489.eurprd04.prod.outlook.com>
X-Exchange-Antispam-Report-Test: UriScan:;
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(601004)(5002009)(5005006); SRVR:DB4PR04MB489; BCL:0; PCL:0; RULEID:; SRVR:DB4PR04MB489;
X-Forefront-PRVS: 051158ECBB
X-OriginatorOrg: philips.com
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 10 Mar 2015 12:58:19.1789 (UTC)
X-MS-Exchange-CrossTenant-Id: 1a407a2d-7675-4d17-8692-b3ac285306e4
X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=1a407a2d-7675-4d17-8692-b3ac285306e4; Ip=[206.191.242.68]; Helo=[mail.philips.com]
X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB4PR04MB489
Archived-At: <http://mailarchive.ietf.org/arch/msg/core/zX03I9FBke2diT6BcGz_gA7vjyw>
Subject: [core] Update to draft-ietf-core-http-mapping-06
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" <core.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/core>, <mailto:core-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/core/>
List-Post: <mailto:core@ietf.org>
List-Help: <mailto:core-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/core>, <mailto:core-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Mar 2015 12:58:45 -0000
Dear all, After substantial edits by the authors we have now uploaded the new version -06 of the HTTP-CoAP mapping draft. There are now clear main sections on the topics of HTTP-CoAP proxy basics, use cases, URI mapping, media type mapping, and response code mapping. Plus various other improvements. http://tools.ietf.org/html/draft-ietf-core-http-mapping-06 In the current version, 3 tickets are still open. One that should be discussed is #376 (http://trac.tools.ietf.org/wg/core/trac/ticket/376) , about how to map a CoAP 4.05 response and the issues when using HTTP 405 for this. Basically in HTTP 405 the server needs to indicate which methods are allowed; CoAP does not provide such information. One proposal is therefore to define a new CoAP Option to encode the allowed methods for a resource. This option (to be effective) then MUST be used by any CoAP server that returns a 4.05. We will probably start a separate thread on this item to go over all the solutions. Regards On behalf of the authors Esko --- Changes from ietf-05 to ietf-06: o Fully restructured the draft, bringing introductory text more to the front and allocating main sections to each of the key topics; addressing Ticket #379; o Addressed Ticket #382, fix of enhanced form URI template definition of q in Section 5.3.2; o Addressed Ticket #381, found a mapping 4.01 to 401 Unauthorized in Section 7; o Addressed Ticket #380 (Add IANA registration for "core.hc" Resource Type) in Section 9; o Addressed Ticket #376 (CoAP 4.05 response can't be translated to HTTP 405 by HC proxy) in Section 7 by use of empty 'Allow' header; o Removed details on the pros and cons of HC proxy placement options; o Addressed review comments of Carsten Bormann; o Clarified failure in mapping of HTTP Accept headers (Section 6.3); o Clarified detection of CoAP servers not supporting blockwise (Section 8.3); o Changed CoAP request timeout min value to MAX_RTT + MAX_SERVER_RESPONSE_DELAY (Section 8.6); o Added security section item (Section 10.3) related to use of CoAP blockwise transfers; o Many editorial improvements. -----Original Message----- From: core [mailto:core-bounces@ietf.org] On Behalf Of internet-drafts@ietf.org Sent: Monday, March 09, 2015 14:38 To: i-d-announce@ietf.org Cc: core@ietf.org Subject: [core] I-D Action: draft-ietf-core-http-mapping-06.txt A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Constrained RESTful Environments Working Group of the IETF. Title : Guidelines for HTTP-CoAP Mapping Implementations Authors : Angelo P. Castellani Salvatore Loreto Akbar Rahman Thomas Fossati Esko Dijk Filename : draft-ietf-core-http-mapping-06.txt Pages : 32 Date : 2015-03-09 Abstract: This document provides reference information for implementing a proxy that performs translation between the HTTP protocol and the CoAP protocol, focusing on the reverse proxy case. It describes how a HTTP request is mapped to a CoAP request and how a CoAP response is mapped back to a HTTP response. Furthermore it defines a template for URI mapping and provides a set of guidelines for HTTP to CoAP protocol translation and related proxy implementations. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-core-http-mapping/ There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-core-http-mapping-06 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=draft-ietf-core-http-mapping-06 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ _______________________________________________ core mailing list core@ietf.org https://www.ietf.org/mailman/listinfo/core ________________________________ The information contained in this message may be confidential and legally protected under applicable law. The message is intended solely for the addressee(s). If you are not the intended recipient, you are hereby notified that any use, forwarding, dissemination, or reproduction of this message is strictly prohibited and may be unlawful. If you are not the intended recipient, please contact the sender by return e-mail and destroy all copies of the original message.