%% You should probably cite draft-ietf-cose-cbor-encoded-cert instead of this I-D.
@techreport{mattsson-cose-cbor-cert-compress-00,
	number =	{draft-mattsson-cose-cbor-cert-compress-00},
	type =		{Internet-Draft},
	institution =	{Internet Engineering Task Force},
	publisher =	{Internet Engineering Task Force},
	note =		{Work in Progress},
	url =		{https://datatracker.ietf.org/doc/html/draft-mattsson-cose-cbor-cert-compress-00},
        author =	{John Preuß Mattsson and Göran Selander and Shahid Raza and Joel Höglund and Martin Furuhed},
	title =		{{CBOR Object Signing and Encryption (COSE): Headers for Carrying CBOR Compressed Certificates}},
	pagetotal =	6,
	year =		,
	month =		,
	day =		,
	abstract =	{Certificate chains often take up the majority of the bytes transmitted in COSE message that carry certificates. Large messages can cause problems, particularly in constrained IoT environments. RFC 7925 defines a certificate profile for constrained IoT. General purpose compression algorithms can in many cases not compress RFC 7925 profiled certificates at all. By using the fact that the certificates are profiled, the CBOR certificate compression algorithms can in many cases compress RFC 7925 profiled certificates with over 50\%. This document specifies the CBOR certificate compression algorithm for use with COSE.},
}