EST based on DTLS secured CoAP (EST-coaps)
draft-vanderstok-core-coap-est-00

Document Type Active Internet-Draft (individual)
Last updated 2016-10-29
Stream (None)
Intended RFC status (None)
Formats plain text pdf xml 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)
anima                                                           S. Kumar
Internet-Draft                                 Philips Lighting Research
Intended status: Standards Track                         P. van der Stok
Expires: May 2, 2017                                          Consultant
                                                        October 29, 2016

               EST based on DTLS secured CoAP (EST-coaps)
                   draft-vanderstok-core-coap-est-00

Abstract

   Low-resource devices in a Low-power and Lossy Network (LLN) can
   operate in a mesh network using the IPv6 over Low-power Personal Area
   Networks (6LoWPAN) and IEEE 802.15.4 link-layer standards.
   Provisioning these devices in a secure manner with keys (often called
   security bootstrapping) used to encrypt and authenticate messages is
   the subject of Bootstrapping of Remote Secure Key Infrastructures
   (BRSKI) [I-D.ietf-anima-bootstrapping-keyinfra].  Enrollment over
   Secure Transport (EST) [RFC7030], based on TLS and HTTP, is used for
   BRSKI.  This document defines how low-resource devices are expected
   to use EST over DTLS and CoAP. 6LoWPAN fragmentation management and
   minor extensions to CoAP are needed to enable EST over DTLS-secured
   CoAP (EST-coaps).

Note

   Many of the concepts in this document are taken over from [RFC7030].
   Consequently, much text is directly traceable to [RFC7030].  The same
   document structure is followed to point out the differences and
   commonalities between EST and EST-coaps.

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 2, 2017.

Kumar & van der Stok       Expires May 2, 2017                  [Page 1]

Internet-Draft                  EST-coaps                   October 2016

Copyright Notice

   Copyright (c) 2016 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
     1.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   4
   2.  Operational Scenarios Overview  . . . . . . . . . . . . . . .   4
   3.  Protocol Design and Layering  . . . . . . . . . . . . . . . .   5
     3.1.  CoAP response codes . . . . . . . . . . . . . . . . . . .   7
     3.2.  Message fragmentation using Block . . . . . . . . . . . .   7
     3.3.  CoAP message headers  . . . . . . . . . . . . . . . . . .   8
   4.  Protocol Exchange Details . . . . . . . . . . . . . . . . . .   9
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   9
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .  12
   7.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  12
   8.  Change Log  . . . . . . . . . . . . . . . . . . . . . . . . .  12
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  12
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .  12
     9.2.  Informative References  . . . . . . . . . . . . . . . . .  13
   Appendix A.  Operational Scenario Example Messages  . . . . . . .  14
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  15

1.  Introduction

   IPv6 over Low-power Wireless Personal Area Networks (6LoWPANs)
   [RFC4944] on IEEE 802.15.4 [ieee802.15.4] wireless networks is
   becoming common in many professional application domains such as
   lighting controls.  However commissioning of such networks suffers
   from a lack of standardized secure bootstrapping mechanisms for these
   networks.

   Although IEEE 802.15.4 defines how security can be enabled between
   nodes within a single mesh network, it does not specify the
Show full document text