Best Practices for HTTP-CoAP Mapping Implementation
draft-castellani-core-http-mapping-06

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2012-10-22
Replaced by rfc8075, draft-ietf-core-http-mapping
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
CoRE Working Group                                         A. Castellani
Internet-Draft                                      University of Padova
Intended status: Informational                                 S. Loreto
Expires: April 25, 2013                                         Ericsson
                                                               A. Rahman
                                        InterDigital Communications, LLC
                                                              T. Fossati
                                                               KoanLogic
                                                                 E. Dijk
                                                        Philips Research
                                                        October 22, 2012

          Best Practices for HTTP-CoAP Mapping Implementation
                 draft-castellani-core-http-mapping-06

Abstract

   This draft provides reference information for HTTP-CoAP proxy
   implementors focusing primarily on the reverse proxy case.  It
   details deployment options, discusses possible approaches for URI
   mapping, and provides useful considerations related to protocol
   translation.

Status of this Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on April 25, 2013.

Copyright Notice

   Copyright (c) 2012 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents

Castellani, et al.       Expires April 25, 2013                 [Page 1]
Internet-Draft              HTTP-CoAP Mapping               October 2012

   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
   2.  Terminology  . . . . . . . . . . . . . . . . . . . . . . . . .  3
   3.  Cross-Protocol Usage of URIs . . . . . . . . . . . . . . . . .  4
   4.  HTTP to CoAP URI Mapping . . . . . . . . . . . . . . . . . . .  4
     4.1.  Homogeneous Mapping  . . . . . . . . . . . . . . . . . . .  5
     4.2.  Embedded Mapping . . . . . . . . . . . . . . . . . . . . .  5
     4.3.  Scheme Security Mapping  . . . . . . . . . . . . . . . . .  5
   5.  HTTP-CoAP Reverse Cross-Protocol Proxy . . . . . . . . . . . .  6
     5.1.  Cross-Protocol Proxy Placement . . . . . . . . . . . . . .  6
     5.2.  Comparison of Proxy Placement Scenarios  . . . . . . . . .  7
     5.3.  Response Code Translations . . . . . . . . . . . . . . . .  8
     5.4.  Media Type Translations  . . . . . . . . . . . . . . . . . 10
     5.5.  Caching and Congestion Control . . . . . . . . . . . . . . 11
     5.6.  Cache Refresh via Observe  . . . . . . . . . . . . . . . . 11
     5.7.  Use of CoAP Blockwise Transfer . . . . . . . . . . . . . . 12
     5.8.  Security Translation . . . . . . . . . . . . . . . . . . . 13
     5.9.  Other guidelines . . . . . . . . . . . . . . . . . . . . . 13
   6.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 14
   7.  Security Considerations  . . . . . . . . . . . . . . . . . . . 14
     7.1.  Traffic overflow . . . . . . . . . . . . . . . . . . . . . 14
     7.2.  Handling Secured Exchanges . . . . . . . . . . . . . . . . 15
   8.  Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 15
   9.  References . . . . . . . . . . . . . . . . . . . . . . . . . . 16
     9.1.  Normative References . . . . . . . . . . . . . . . . . . . 16
     9.2.  Informative References . . . . . . . . . . . . . . . . . . 17
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 17

Castellani, et al.       Expires April 25, 2013                 [Page 2]
Internet-Draft              HTTP-CoAP Mapping               October 2012

1.  Introduction

   CoAP [I-D.ietf-core-coap] has been designed with the twofold aim to
   be an application protocol specialized for constrained environments
Show full document text