%% You should probably cite draft-ietf-tsvwg-sctp-dtls-chunk-04 instead of this revision.
@techreport{ietf-tsvwg-sctp-dtls-chunk-02,
    number =    {draft-ietf-tsvwg-sctp-dtls-chunk-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-ietf-tsvwg-sctp-dtls-chunk/02/},
    author =    {Magnus Westerlund and John Preuß Mattsson and Claudio Porfiri and Michael Tüxen},
    title =     {{Stream Control Transmission Protocol (SCTP) DTLS Chunk}},
    pagetotal = 41,
    year =      ,
    month =     ,
    day =       ,
    abstract =  {This document describes a method for adding Datagram Transport Layer Security (DTLS) based authentication and cryptographic protection to the Stream Control Transmission Protocol (SCTP). This SCTP extension is intended to enable communication privacy for applications that use SCTP as their transport protocol and allows applications to communicate in a way that is designed to prevent eavesdropping and detect tampering or message forgery. Once enabled, this also applies to the SCTP payload as well as the SCTP control information. Applications using this SCTP extension can use most of the transport features provided by SCTP and its other extensions. The use of the SCTP Authentication extension defined in RFC 4895 is incompatible with the extension defined in this document but would not provide any additional service. This implies that the Dynamic Address Reconfiguration as specified in RFC 5061 can only be used as described in this document.},
}