A TCP and TLS Transport for the Constrained Application Protocol (CoAP)
draft-ietf-core-coap-tcp-tls-01

The information below is for an old version of the document
Document Type Active Internet-Draft (core WG)
Last updated 2015-11-19
Replaces draft-tschofenig-core-coap-tcp-tls
Stream IETF
Intended RFC status (None)
Formats plain text pdf html bibtex
Reviews
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
CORE                                                     C. Bormann, Ed.
Internet-Draft                                   Universitaet Bremen TZI
Intended status: Standards Track                                S. Lemay
Expires: May 22, 2016                               V. Solorzano Barboza
                                                      Zebra Technologies
                                                           H. Tschofenig
                                                                ARM Ltd.
                                                       November 19, 2015

A TCP and TLS Transport for the Constrained Application Protocol (CoAP)
                    draft-ietf-core-coap-tcp-tls-01

Abstract

   The Hypertext Transfer Protocol (HTTP) was designed with TCP as the
   underlying transport protocol.  The Constrained Application Protocol
   (CoAP), while inspired by HTTP, has been defined to make use of UDP
   instead of TCP.  Therefore, reliable delivery and a simple congestion
   control and flow control mechanism are provided by the message layer
   of the CoAP protocol.

   A number of environments benefit from the use of CoAP directly over a
   reliable byte stream such as TCP, which already provides these
   services.  This document defines the use of CoAP over TCP as well as
   CoAP over TLS.

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 May 22, 2016.

Bormann, et al.           Expires May 22, 2016                  [Page 1]
Internet-Draft         TCP/TLS Transport for CoAP          November 2015

Copyright Notice

   Copyright (c) 2015 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
   (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.  Constrained Application Protocol  . . . . . . . . . . . . . .   3
   4.  Message Format  . . . . . . . . . . . . . . . . . . . . . . .   5
     4.1.  Discussion  . . . . . . . . . . . . . . . . . . . . . . .   6
   5.  Message Transmission  . . . . . . . . . . . . . . . . . . . .   7
   6.  CoAP URI  . . . . . . . . . . . . . . . . . . . . . . . . . .   7
     6.1.  coap+tcp URI scheme . . . . . . . . . . . . . . . . . . .   7
     6.2.  coaps+tcp URI scheme  . . . . . . . . . . . . . . . . . .   8
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   8
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   8
     8.1.  Service Name and Port Number Registration . . . . . . . .   8
     8.2.  URI Schemes . . . . . . . . . . . . . . . . . . . . . . .   9
     8.3.  ALPN Protocol ID  . . . . . . . . . . . . . . . . . . . .  10
   9.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  10
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .  10
     10.1.  Normative References . . . . . . . . . . . . . . . . . .  10
     10.2.  Informative References . . . . . . . . . . . . . . . . .  11
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  12

1.  Introduction

   The Constrained Application Protocol (CoAP) [RFC7252] was designed
   for Internet of Things (IoT) deployments, assuming that UDP can be
   used unimpeded -- UDP [RFC0768], or DTLS [RFC6347] over UDP; it is a
   good choice for transferring small amounts of data across networks
   that follow the IP architecture.  Some CoAP deployments, however, may
   have to integrate well with existing enterprise infrastructure, where
   the use of UDP-based protocols may not be well-received or may even
   be blocked by firewalls.  Middleboxes that are unaware of CoAP usage

Bormann, et al.           Expires May 22, 2016                  [Page 2]
Internet-Draft         TCP/TLS Transport for CoAP          November 2015
Show full document text