IETF Logo Mail Archive

Re: [core] I-D Action: draft-ietf-core-http-mapping-10.txt

"Rahman, Akbar" <Akbar.Rahman@InterDigital.com> Fri, 13 May 2016 13:51 UTC

Return-Path: <Akbar.Rahman@InterDigital.com>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 360FD12B021 for <core@ietfa.amsl.com>; Fri, 13 May 2016 06:51:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.442
X-Spam-Level:
X-Spam-Status: No, score=-0.442 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RDNS_NONE=0.793, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no
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 YtlkiMD4vg8g for <core@ietfa.amsl.com>; Fri, 13 May 2016 06:51:22 -0700 (PDT)
Received: from smtp-in1.interdigital.com (unknown [68.168.94.174]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 590E712B014 for <core@ietf.org>; Fri, 13 May 2016 06:51:22 -0700 (PDT)
X-ASG-Debug-ID: 1463147480-06daaa10907e190001-aa7cYp
Received: from NISSONITE.InterDigital.com (nissonite.interdigital.com [10.2.64.252]) by smtp-in1.interdigital.com with ESMTP id 9BcUttrukIQSidHR (version=TLSv1 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO) for <core@ietf.org>; Fri, 13 May 2016 09:51:20 -0400 (EDT)
X-Barracuda-Envelope-From: Akbar.Rahman@InterDigital.com
Received: from NABESITE.InterDigital.com ([fe80::4d8a:a889:67c2:f009]) by NISSONITE.InterDigital.com ([::1]) with mapi id 14.03.0279.002; Fri, 13 May 2016 09:51:20 -0400
From: "Rahman, Akbar" <Akbar.Rahman@InterDigital.com>
To: "cabo@tzi.org" <cabo@tzi.org>, "jaime.jimenez@ericsson.com" <jaime.jimenez@ericsson.com>
Thread-Topic: [core] I-D Action: draft-ietf-core-http-mapping-10.txt
X-ASG-Orig-Subj: RE: [core] I-D Action: draft-ietf-core-http-mapping-10.txt
Thread-Index: AQHRrR0WzJNnBq5QE0q4cwryK3YZrp+24c9g
Date: Fri, 13 May 2016 13:51:20 +0000
Message-ID: <36F5869FE31AB24485E5E3222C288E1F5BAB947B@NABESITE.InterDigital.com>
References: <20160513134033.10520.69223.idtracker@ietfa.amsl.com>
In-Reply-To: <20160513134033.10520.69223.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.3.2.71]
x-exclaimer-md-config: bb79a19d-f711-475c-a0f9-4d93b71c94dd
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Barracuda-Connect: nissonite.interdigital.com[10.2.64.252]
X-Barracuda-Start-Time: 1463147480
X-Barracuda-Encrypted: ECDHE-RSA-AES256-SHA
X-Barracuda-URL: https://10.1.245.3:443/cgi-mod/mark.cgi
X-Barracuda-Scan-Msg-Size: 3318
X-Virus-Scanned: by bsmtpd at interdigital.com
X-Barracuda-BRTS-Status: 1
X-Barracuda-Spam-Score: 0.00
X-Barracuda-Spam-Status: No, SCORE=0.00 using global scores of TAG_LEVEL=1000.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=9.0 tests=BSF_SC0_MISMATCH_TO
X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.3.29545 Rule breakdown below pts rule name description ---- ---------------------- -------------------------------------------------- 0.00 BSF_SC0_MISMATCH_TO Envelope rcpt doesn't match header
Archived-At: <http://mailarchive.ietf.org/arch/msg/core/2yIbwv2W8SL32wzKs9Y_XhMUlXc>
Cc: "core@ietf.org" <core@ietf.org>
Subject: Re: [core] I-D Action: draft-ietf-core-http-mapping-10.txt
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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: Fri, 13 May 2016 13:51:24 -0000

Hi Carsten/Jaime,


We have updated the draft to cover the following:


  Changes from ietf-09 to ietf-10:

  o  Addressed Ticket #401 - Clarified that draft covers not only
     Reverse HC Proxy but that many parts also apply to Forward and
     Interception Proxies.

  o  Clarified that draft concentrates on the HTTP-to-CoAP mapping
     direction (i.e. the HC proxy is a HTTP server and a CoAP client).

  o  Clarified the "null mapping" case where no CoAP URI information is
     embedded in the HTTP request URI.

  o  Moved multicast related security text to the "Security
     Considerations" to consolidate all security information in one
     location.

  o  Removed references to "placement" of proxy (e.g. server-side vs
     client-side) as is confusing and provides little added value.

  o  Fixed version numbers on references that were corrupted in last
     revision due to outdated xml2rfc conversion tool local cache.

  o  Various editorial improvements.


Can you please review, and start the 2nd WGLC if you think that everything looks in order.


Best Regards,


Akbar

-----Original Message-----
From: core [mailto:core-bounces@ietf.org] On Behalf Of internet-drafts@ietf.org
Sent: Friday, May 13, 2016 9:41 AM
To: i-d-announce@ietf.org
Cc: core@ietf.org
Subject: [core] I-D Action: draft-ietf-core-http-mapping-10.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 of the IETF.

       Title           : Guidelines for HTTP-to-CoAP Mapping Implementations
       Authors         : Angelo P. Castellani
                         Salvatore Loreto
                         Akbar Rahman
                         Thomas Fossati
                         Esko Dijk
       Filename        : draft-ietf-core-http-mapping-10.txt
       Pages           : 36
       Date            : 2016-05-13

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 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:
https://tools.ietf.org/html/draft-ietf-core-http-mapping-10

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-core-http-mapping-10


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

v2.23.0 | Report a Bug | By Email