%% You should probably cite draft-ietf-ace-coap-est instead of this I-D.
@techreport{vanderstok-ace-coap-est-02,
    number =    {draft-vanderstok-ace-coap-est-02},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-vanderstok-ace-coap-est/02/},
    author =    {Sandeep S. Kumar and Peter Van der Stok and Panos Kampanakis and Martin Furuhed and Shahid Raza},
    title =     {{EST over secure CoAP (EST-coaps)}},
    pagetotal = 37,
    year =      2017,
    month =     jun,
    day =       12,
    abstract =  {Low-resource devices in a Low-power and Lossy Network (LLN) can operate in a mesh network using the IPv6 over Low-power Wireless Personal Area Networks (6LoWPAN) and IEEE 802.15.4 link-layer standards. Provisioning these devices in a secure manner with keys (often called secure bootstrapping) used to encrypt and authenticate messages, is the subject of Bootstrapping of Remote Secure Key Infrastructures (BRSKI) {[}I-D.ietf-anima-bootstrapping-keyinfra{]} and 6tisch Secure Join {[}I-D.ietf-6tisch-dtsecurity-secure-join{]}. Enrollment over Secure Transport (EST) {[}RFC7030{]}, based on TLS and HTTP, is used in BRSKI. Low-resource devices often use the lightweight Constrained Application Protocol (CoAP) {[}RFC7252{]} for message exchanges. This document defines how low-resource devices are expected to use EST over secure CoAP (EST-coaps) for secure bootstrapping and certificate enrollment. 6LoWPAN fragmentation management and extensions to CoAP registries are needed to enable EST-coaps.},
}