Best Practices for HTTP-CoAP Mapping Implementation
draft-ietf-core-http-mapping-00

The information below is for an old version of the document
Document Type Active Internet-Draft (core WG)
Last updated 2013-06-03
Stream IETF
Intended RFC status (None)
Formats pdf htmlized (tools) htmlized bibtex
Reviews
Stream WG state WG Document
Document shepherd None
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
CoRE Working Group                                       A.P. Castellani
Internet-Draft                                      University of Padova
Intended status: Informational                                 S. Loreto
Expires: December 05, 2013                                      Ericsson
                                                               A. Rahman
                                        InterDigital Communications, LLC
                                                              T. Fossati
                                                               KoanLogic
                                                                 E. Dijk
                                                        Philips Research
                                                           June 03, 2013

          Best Practices for HTTP-CoAP Mapping Implementation
                    draft-ietf-core-http-mapping-00

Abstract

   This draft provides reference information for HTTP-CoAP protocol
   translation proxy implementors, focusing primarily on the reverse
   proxy case.  It details deployment options, discusses possible
   approaches for URI mapping, and provides a set of guidelines and
   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 December 05, 2013.

Copyright Notice

   Copyright (c) 2013 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 December 05, 2013                [Page 1]
Internet-Draft             HTTP-CoAP Mapping                   June 2013

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

1.  Introduction

   CoAP [I-D.ietf-core-coap] has been designed with the twofold aim to
   be an application protocol specialized for constrained environments
   and to be easily used in REST architectures such as the Web.  The
   latter goal has led to define CoAP to easily interoperate with HTTP
   [RFC2616] through an intermediary proxy which performs cross-protocol
Show full document text