A Hitchhiker's Guide to the (Datagram) Transport Layer Security Protocol for Smart Objects and Constrained Node Networks
draft-ietf-lwig-tls-minimal-00

The information below is for an old version of the document
Document Type Active Internet-Draft (lwig WG)
Last updated 2013-09-04
Replaces draft-tschofenig-lwig-tls-minimal
Stream IETF
Intended RFC status (None)
Formats plain text pdf html
Stream WG state WG Document
Document shepherd None
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
LWIG Working Group                                            S.S. Kumar
Internet-Draft                                          Philips Research
Intended status: Informational                                   S. Keoh
Expires: March 8, 2014                             University of Glasgow
                                                           H. Tschofenig
                                                  Nokia Siemens Networks
                                                       September 4, 2013

A Hitchhiker's Guide to the (Datagram) Transport Layer Security Protocol
            for Smart Objects and Constrained Node Networks
                draft-ietf-lwig-tls-minimal-00

Abstract

   Transport Layer Security (TLS) is a widely used security protocol
   that offers communication security services at the transport layer.
   The initial design of TLS was focused on the protection of
   applications running on top of the Transmission Control Protocol
   (TCP), and was a good match for securing the Hypertext Transfer
   Protocol (HTTP).  Subsequent standardization efforts lead to the
   publication of the Datagram Transport Layer Security (DTLS) protocol,
   which allows the re-use of the TLS security functionality and the
   payloads to be exchanged on top of the User Datagram Protocol (UDP).

   With the work on the Constrained Application Protocol (CoAP), as a
   specialized web transfer protocol for use with constrained nodes and
   constrained networks, DTLS is a preferred communication security
   protocol.

   Smart objects are constrained in various ways (e.g., CPU, memory,
   power consumption) and these limitations may impose restrictions on
   the protocol stack such a device runs. This document only looks at
   the security part of that protocol stacks and the ability to
   customize TLS/DTLS. To offer input for implementers and system
   architects this document illustrates the costs and benefits of
   various TLS/DTLS features for use with smart objects and constraint
   node networks.

Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC 2119 [RFC2119]

Status of this Memo

 

Kumar, et al.            Expires March 8, 2014                  [Page 1]
Internet-Draft      Hitchhiker's Guide to TLS / DTLS   September 4, 2013

   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 August 29, 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
   (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.  Overview . . . . . . . . . . . . . . . . . . . . . . . . . . .  4
   3.  Design Decisions . . . . . . . . . . . . . . . . . . . . . . .  6
   4.  Performance Numbers  . . . . . . . . . . . . . . . . . . . . .  7
     4.1. Pre-Shared Key (PSK) based DTLS implementation  . . . . . .  7
       4.1.1. Prototype Environment . . . . . . . . . . . . . . . . .  7
       4.1.2. Code size and Memory Consumption  . . . . . . . . . . .  8
       4.1.3. Communication Overhead  . . . . . . . . . . . . . . . .  8
       4.1.4. Message Delay, Success Rate and Bandwidth . . . . . . . 10
     4.2. Certificate based and Raw-public key based TLS 
          implementation  . . . . . . . . . . . . . . . . . . . . . . 11
       4.2.1. Prototype Environment . . . . . . . . . . . . . . . . . 11
       4.2.2. Code size . . . . . . . . . . . . . . . . . . . . . . . 11
Show full document text