A new Request for Comments is now available in online RFC libraries.

        
        RFC 9054

        Title:      CBOR Object Signing and Encryption (COSE):
                    Hash Algorithms 
        Author:     J. Schaad
        Status:     Informational
        Stream:     IETF
        Date:       August 2022
        Pages:      9
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-cose-hash-algs-09.txt

        URL:        https://www.rfc-editor.org/info/rfc9054

        DOI:        10.17487/RFC9054

The CBOR Object Signing and Encryption (COSE) syntax (see RFC 9052)
does not define any direct methods for using hash algorithms. There
are, however, circumstances where hash algorithms are used, such as
indirect signatures, where the hash of one or more contents are
signed, and identification of an X.509 certificate or other object by
the use of a fingerprint. This document defines hash algorithms that
are identified by COSE algorithm identifiers.

This document is a product of the CBOR Object Signing and Encryption Working 
Group of the IETF.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-edi...@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC

_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce

Reply via email to