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

["Fossati, Thomas (Nokia - GB)" <[e-mail]>]

Hi Carsten & Jaime,

A gentle prod to our chairs for restarting WGLC on the HTTP-CoAP mapping
I-D ;-)

Thanks, cheers,
t

On 18/05/2016 14:55, "core on behalf of Rahman, Akbar"
<[e-mail] on behalf of [e-mail]> wrote:
>Hi Carsten/Jamie,
>
>
>Just resending this email as I believe the first time it did not get
>correctly to Carsten due to some problem with my mail server.  I've been
>told by me IST department that the problem has now been fixed so I am
>resending this request to re-start the WGLC.
>
>
>Thanks,
>
>
>Akbar
>
>-----Original Message-----
>From: core [mailto:[e-mail]] On Behalf Of Rahman, Akbar
>Sent: Friday, May 13, 2016 9:51 AM
>To: [e-mail]; [e-mail]
>Cc: [e-mail]
>Subject: Re: [core] I-D Action: draft-ietf-core-http-mapping-10.txt
>
>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:[e-mail]] On Behalf Of
>[e-mail]
>Sent: Friday, May 13, 2016 9:41 AM
>To: [e-mail]
>Cc: [e-mail]
>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
>[e-mail]
>https://www.ietf.org/mailman/listinfo/core
>
>_______________________________________________
>core mailing list
>[e-mail]
>https://www.ietf.org/mailman/listinfo/core
>
>_______________________________________________
>core mailing list
>[e-mail]
>https://www.ietf.org/mailman/listinfo/core
>