EST over secure CoAP (EST-coaps)
draft-ietf-ace-coap-est-02

Document Type Active Internet-Draft (ace WG)
Last updated 2018-06-21
Replaces draft-vanderstok-ace-coap-est
Stream IETF
Intended RFC status (None)
Formats plain text pdf xml html bibtex
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)
ACE                                                      P. van der Stok
Internet-Draft                                                Consultant
Intended status: Standards Track                           P. Kampanakis
Expires: December 23, 2018                                 Cisco Systems
                                                                S. Kumar
                                               Philips Lighting Research
                                                           M. Richardson
                                                                     SSW
                                                              M. Furuhed
                                                             Nexus Group
                                                                 S. Raza
                                                               RISE SICS
                                                           June 21, 2018

                    EST over secure CoAP (EST-coaps)
                       draft-ietf-ace-coap-est-02

Abstract

   Enrollment over Secure Transport (EST) is used as a certificate
   provisioning protocol over HTTPS.  Low-resource devices often use the
   lightweight Constrained Application Protocol (CoAP) for message
   exchanges.  This document defines how to transport EST payloads over
   secure CoAP (EST-coaps), which allows low-resource constrained
   devices to use existing EST functionality for provisioning
   certificates.

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 https://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 23, 2018.

van der Stok, et al.    Expires December 23, 2018               [Page 1]
Internet-Draft                  EST-coaps                      June 2018

Copyright Notice

   Copyright (c) 2018 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
   (https://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.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Conformance to RFC7925 profiles . . . . . . . . . . . . . . .   3
   4.  Protocol Design . . . . . . . . . . . . . . . . . . . . . . .   4
     4.1.  Payload format  . . . . . . . . . . . . . . . . . . . . .   5
       4.1.1.  Content Format application/multipart-core . . . . . .   6
     4.2.  Message Bindings  . . . . . . . . . . . . . . . . . . . .   6
     4.3.  CoAP response codes . . . . . . . . . . . . . . . . . . .   6
     4.4.  Delayed Results . . . . . . . . . . . . . . . . . . . . .   7
     4.5.  Server-side Key Generation  . . . . . . . . . . . . . . .   8
     4.6.  Message fragmentation . . . . . . . . . . . . . . . . . .   9
     4.7.  Deployment limits . . . . . . . . . . . . . . . . . . . .  10
   5.  Discovery and URI . . . . . . . . . . . . . . . . . . . . . .  10
   6.  DTLS Transport Protocol . . . . . . . . . . . . . . . . . . .  11
   7.  HTTPS-CoAPS Registrar . . . . . . . . . . . . . . . . . . . .  13
   8.  Parameters  . . . . . . . . . . . . . . . . . . . . . . . . .  15
   9.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  16
     9.1.  Content-Format Registry . . . . . . . . . . . . . . . . .  16
     9.2.  Resource Type registry  . . . . . . . . . . . . . . . . .  17
   10. Security Considerations . . . . . . . . . . . . . . . . . . .  17
     10.1.  EST server considerations  . . . . . . . . . . . . . . .  17
     10.2.  HTTPS-CoAPS Registrar considerations . . . . . . . . . .  18
   11. Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  19
   12. Change Log  . . . . . . . . . . . . . . . . . . . . . . . . .  19
   13. References  . . . . . . . . . . . . . . . . . . . . . . . . .  20
     13.1.  Normative References . . . . . . . . . . . . . . . . . .  20
     13.2.  Informative References . . . . . . . . . . . . . . . . .  21
Show full document text