BRSKI over CoAP
draft-pritikin-coap-bootstrap-01

Document Type Active Internet-Draft (individual)
Last updated 2016-10-31
Stream (None)
Intended RFC status (None)
Formats plain text xml 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)
ANIMA WG                                                     M. Pritikin
Internet-Draft                                             P. Kampanakis
Intended status: Informational                             Cisco Systems
Expires: May 4, 2017                                    October 31, 2016

                            BRSKI over CoAP
                    draft-pritikin-coap-bootstrap-01

Abstract

   This document provides an initial discussion of Bootstrapping of
   Remote Secure key infrastructures (BRSKI) when the device being
   bootstrapped speaks CoAP.  The HTTPS REST methods leveraged by BRSKI
   are mapped to CoAP methods.  Fragmentation management of large
   messages during EST certificate enrollment is addressed.

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

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.

Pritikin & Kampanakis      Expires May 4, 2017                  [Page 1]
Internet-Draft               BRSKI over CoAP                October 2016

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   2
   3.  Scope of solution . . . . . . . . . . . . . . . . . . . . . .   3
   4.  DTLS  . . . . . . . . . . . . . . . . . . . . . . . . . . . .   3
   5.  Message Bindings  . . . . . . . . . . . . . . . . . . . . . .   4
     5.1.  cacerts . . . . . . . . . . . . . . . . . . . . . . . . .   5
     5.2.  enroll / reenroll . . . . . . . . . . . . . . . . . . . .   6
     5.3.  csrattr . . . . . . . . . . . . . . . . . . . . . . . . .   7
     5.4.  requestaudittoken, requestauditlog  . . . . . . . . . . .   7
   6.  Data Fragmentation  . . . . . . . . . . . . . . . . . . . . .   7
     6.1.  Fragmented response example with Block2 . . . . . . . . .   8
     6.2.  Fragmented request example with Block1  . . . . . . . . .  11
     6.3.  Fragmented request/response example with Block1, Size1
           and Block2  . . . . . . . . . . . . . . . . . . . . . . .  11
   7.  Proxying  . . . . . . . . . . . . . . . . . . . . . . . . . .  11
   8.  CoAP Parameters . . . . . . . . . . . . . . . . . . . . . . .  11
   9.  Security Considerations . . . . . . . . . . . . . . . . . . .  11
   10. Update Tracking . . . . . . . . . . . . . . . . . . . . . . .  11
   11. Normative References  . . . . . . . . . . . . . . . . . . . .  11
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  12

1.  Introduction

   Many IoT and other devices are expected to use CoAP over UDP
   extensively.  Bootstrapping these devices without requiring a full
   TCP stack is an often raised requirement for
   [I-D.ietf-anima-bootstrapping-keyinfra].  BRSKI provides REST methods
   over TLS that can be functional in a UDP setting with the folling
   necessary additions:

   DTLS:  Because the CoAP use of DTLS includes support for large
      handshake messages there is little to describe here.  BRSKI and
      EST [RFC7030] are expanded to include DTLS.

   REST:  The mapping of BRSKI and EST messages to CoAP REST calls is
      described.

   Fragmentation:  Use of block chaining to support fragmentation of
      large BRSKI and EST messages is described.

2.  Terminology

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
Show full document text