rfc9054v4.txt		rfc9054.txt
	Internet Engineering Task Force (IETF) J. Schaad		Internet Engineering Task Force (IETF) J. Schaad
	Request for Comments: 9054 August Cellars		Request for Comments: 9054 August Cellars
	Category: Informational July 2022		Category: Informational August 2022
	ISSN: 2070-1721		ISSN: 2070-1721
	CBOR Object Signing and Encryption (COSE): Hash Algorithms		CBOR Object Signing and Encryption (COSE): Hash Algorithms
	Abstract		Abstract
	The CBOR Object Signing and Encryption (COSE) syntax (see RFC 9052)		The CBOR Object Signing and Encryption (COSE) syntax (see RFC 9052)
	does not define any direct methods for using hash algorithms. There		does not define any direct methods for using hash algorithms. There
	are, however, circumstances where hash algorithms are used, such as		are, however, circumstances where hash algorithms are used, such as
	indirect signatures, where the hash of one or more contents are		indirect signatures, where the hash of one or more contents are
	skipping to change at line 441 ¶		skipping to change at line 441 ¶
	[RFC3174] Eastlake 3rd, D. and P. Jones, "US Secure Hash Algorithm 1		[RFC3174] Eastlake 3rd, D. and P. Jones, "US Secure Hash Algorithm 1
	(SHA1)", RFC 3174, DOI 10.17487/RFC3174, September 2001,		(SHA1)", RFC 3174, DOI 10.17487/RFC3174, September 2001,
	<https://www.rfc-editor.org/info/rfc3174>.		<https://www.rfc-editor.org/info/rfc3174>.
	[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC		[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
	2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,		2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
	May 2017, <https://www.rfc-editor.org/info/rfc8174>.		May 2017, <https://www.rfc-editor.org/info/rfc8174>.
	[RFC9052] Schaad, J., "CBOR Object Signing and Encryption (COSE):		[RFC9052] Schaad, J., "CBOR Object Signing and Encryption (COSE):
	Structures and Process", STD 96, RFC 9052,		Structures and Process", STD 96, RFC 9052,
	DOI 10.17487/RFC9052, July 2022,		DOI 10.17487/RFC9052, August 2022,
	<https://www.rfc-editor.org/info/rfc9052>.		<https://www.rfc-editor.org/info/rfc9052>.
	6.2. Informative References		6.2. Informative References
	[BCP201] Housley, R., "Guidelines for Cryptographic Algorithm		[BCP201] Housley, R., "Guidelines for Cryptographic Algorithm
	Agility and Selecting Mandatory-to-Implement Algorithms",		Agility and Selecting Mandatory-to-Implement Algorithms",
	BCP 201, RFC 7696, November 2015,		BCP 201, RFC 7696, November 2015,
	<https://www.rfc-editor.org/info/bcp201>.		<https://www.rfc-editor.org/info/bcp201>.
	[CMS] Housley, R., "Cryptographic Message Syntax (CMS)", STD 70,		[CMS] Housley, R., "Cryptographic Message Syntax (CMS)", STD 70,
	skipping to change at line 487 ¶		skipping to change at line 487 ¶
	Stevens, M., Bursztein, E., Karpman, P., Albertini, A.,		Stevens, M., Bursztein, E., Karpman, P., Albertini, A.,
	and Y. Markov, "The first collision for full SHA-1",		and Y. Markov, "The first collision for full SHA-1",
	February 2017,		February 2017,
	<https://shattered.io/static/shattered.pdf>.		<https://shattered.io/static/shattered.pdf>.
	[SUIT-MANIFEST]		[SUIT-MANIFEST]
	Moran, B., Tschofenig, H., Birkholz, H., and K. Zandberg,		Moran, B., Tschofenig, H., Birkholz, H., and K. Zandberg,
	"A Concise Binary Object Representation (CBOR)-based		"A Concise Binary Object Representation (CBOR)-based
	Serialization Format for the Software Updates for Internet		Serialization Format for the Software Updates for Internet
	of Things (SUIT) Manifest", Work in Progress, Internet-		of Things (SUIT) Manifest", Work in Progress, Internet-
	Draft, draft-ietf-suit-manifest-18, 11 July 2022,		Draft, draft-ietf-suit-manifest-19, 9 August 2022,
	<https://datatracker.ietf.org/doc/html/draft-ietf-suit-		<https://datatracker.ietf.org/doc/html/draft-ietf-suit-
	manifest-18>.		manifest-19>.
	Author's Address		Author's Address
	Jim Schaad		Jim Schaad
	August Cellars		August Cellars
	Email: ietf@augustcellars.com
End of changes. 5 change blocks.
	4 lines changed or deleted		4 lines changed or added
This html diff was produced by rfcdiff 1.48.