%% You should probably cite rfc9031 instead of this I-D.
@techreport{ietf-6tisch-minimal-security-04,
    number =    {draft-ietf-6tisch-minimal-security-04},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-ietf-6tisch-minimal-security/04/},
    author =    {Mališa Vučinić and Jonathan Simon and Kris Pister and Michael Richardson},
    title =     {{Minimal Security Framework for 6TiSCH}},
    pagetotal = 23,
    year =      ** No value found for 'doc.pub_date.year' **,
    month =     ** No value found for 'doc.pub_date' **,
    day =       ** No value found for 'doc.pub_date.day' **,
    abstract =  {This document describes the minimal configuration required for a new device, called "pledge", to securely join a 6TiSCH (IPv6 over the TSCH mode of IEEE 802.15.4e) network. The entities involved use CoAP (Constrained Application Protocol) and OSCORE (Object Security for Constrained RESTful Environments). The configuration requires that the pledge and the JRC (join registrar/coordinator, a central entity), share a symmetric key. How this key is provisioned is out of scope of this document. The result of the joining process is that the JRC configures the pledge with link-layer keying material and a short link-layer address. This specification also defines a new Stateless-Proxy CoAP option. Additional security mechanisms may be added on top of this minimal framework.},
}