RFC 9591 on The Flexible Round-Optimized Schnorr Threshold (FROST) Protocol for Two-Round Schnorr Signatures

rfc-editor@rfc-editor.org Fri, 28 June 2024 20:59 UTC

Return-Path: <wwwrun@rfcpa.rfc-editor.org>
X-Original-To: ietf-announce@ietf.org
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from rfcpa.rfc-editor.org (unknown [167.172.21.234]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8B672C14F686; Fri, 28 Jun 2024 13:59:09 -0700 (PDT)
Received: by rfcpa.rfc-editor.org (Postfix, from userid 461) id E0D827FA61; Fri, 28 Jun 2024 13:59:08 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org, irtf-announce@irtf.org
Subject: RFC 9591 on The Flexible Round-Optimized Schnorr Threshold (FROST) Protocol for Two-Round Schnorr Signatures
From: rfc-editor@rfc-editor.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20240628205908.E0D827FA61@rfcpa.rfc-editor.org>
Date: Fri, 28 Jun 2024 13:59:08 -0700
Message-ID-Hash: 7GTLC63RW6VDBG7PFARZZW6BFPCDY6YJ
X-Message-ID-Hash: 7GTLC63RW6VDBG7PFARZZW6BFPCDY6YJ
X-MailFrom: wwwrun@rfcpa.rfc-editor.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ietf-announce.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, cfrg@irtf.org
X-Mailman-Version: 3.3.9rc4
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/1trJ4QC_USGuz08Yte_RR0D3kkk>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Owner: <mailto:ietf-announce-owner@ietf.org>
List-Post: <mailto:ietf-announce@ietf.org>
List-Subscribe: <mailto:ietf-announce-join@ietf.org>
List-Unsubscribe: <mailto:ietf-announce-leave@ietf.org>

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

        
        RFC 9591

        Title:      The Flexible Round-Optimized Schnorr Threshold 
                    (FROST) Protocol for Two-Round Schnorr Signatures 
        Author:     D. Connolly,
                    C. Komlo,
                    I. Goldberg,
                    C. A. Wood
        Status:     Informational
        Stream:     IRTF
        Date:       June 2024
        Mailbox:    durumcrustulum@gmail.com,
                    ckomlo@uwaterloo.ca,
                    iang@uwaterloo.ca,
                    caw@heapingbits.net
        Pages:      47
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-irtf-cfrg-frost-15.txt

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

        DOI:        10.17487/RFC9591

This document specifies the Flexible Round-Optimized Schnorr
Threshold (FROST) signing protocol.  FROST signatures can be issued
after a threshold number of entities cooperate to compute a
signature, allowing for improved distribution of trust and redundancy
with respect to a secret key. FROST depends only on a prime-order
group and cryptographic hash function. This document specifies a
number of ciphersuites to instantiate FROST using different
prime-order groups and hash functions. This document is a product of
the Crypto Forum Research Group (CFRG) in the IRTF.


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, rfc-dist and IRTF-Announce lists.To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
  https://www.irtf.org/mailman/listinfo/irtf-announce

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-editor@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