%% You should probably cite draft-ietf-core-oscore-groupcomm-21 instead of this revision.
@techreport{ietf-core-oscore-groupcomm-14,
    number =    {draft-ietf-core-oscore-groupcomm-14},
    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-core-oscore-groupcomm/14/},
    author =    {Marco Tiloca and Göran Selander and Francesca Palombini and John Preuß Mattsson and Jiye Park},
    title =     {{Group OSCORE - Secure Group Communication for CoAP}},
    pagetotal = 103,
    year =      2022,
    month =     mar,
    day =       7,
    abstract =  {This document defines Group Object Security for Constrained RESTful Environments (Group OSCORE), providing end-to-end security of CoAP messages exchanged between members of a group, e.g., sent over IP multicast. In particular, the described approach defines how OSCORE is used in a group communication setting to provide source authentication for CoAP group requests, sent by a client to multiple servers, and for protection of the corresponding CoAP responses. Group OSCORE also defines a pairwise mode where each member of the group can efficiently derive a symmetric pairwise key with any other member of the group for pairwise OSCORE communication.},
}