draft-irtf-cfrg-bls-signature-00.txt
draft-irtf-cfrg-bls-signature-00

Document Type Active Internet-Draft (cfrg RG)
Last updated 2019-08-12
Replaces draft-boneh-bls-signature
Stream IRTF
Intended RFC status Informational
Formats plain text xml pdf html bibtex
Stream IRTF state (None)
Consensus Boilerplate Unknown
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
CFRG                                                            D. Boneh
Internet-Draft                                                  R. Wahby
Expires: February 9, 2020                            Stanford University
                                                             S. Gorbunov
                                     Algorand and University of Waterloo
                                                                  H. Wee
                                                 Algorand and ENS, Paris
                                                                Z. Zhang
                                                                Algorand
                                                          August 8, 2019

                  draft-irtf-cfrg-bls-signature-00.txt
                    draft-irtf-cfrg-bls-signature-00

Abstract

   BLS is a digital signature scheme with compression properties.  With
   a given set of signatures (signature_1, ..., signature_n) anyone can
   produce a compressed signature signature_compressed.  The same is
   true for a set of secret keys or public keys, while keeping the
   connection between sets (i.e., a compressed public key is associated
   to its compressed secret key).  Furthermore, the BLS signature scheme
   is deterministic, non-malleable, and efficient.  Its simplicity and
   cryptographic properties allows it to be useful in a variety of use-
   cases, specifically when minimal storage space or bandwidth are
   required.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on February 9, 2020.

Boneh, et al.           Expires February 9, 2020                [Page 1]
Internet-Draft                BLS-signature                  August 2019

Copyright Notice

   Copyright (c) 2019 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (https://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  Comparison with ECDSA . . . . . . . . . . . . . . . . . .   4
     1.2.  Organization of this document . . . . . . . . . . . . . .   4
     1.3.  Terminology and definitions . . . . . . . . . . . . . . .   5
     1.4.  API . . . . . . . . . . . . . . . . . . . . . . . . . . .   7
     1.5.  Requirements  . . . . . . . . . . . . . . . . . . . . . .   7
   2.  Core operations . . . . . . . . . . . . . . . . . . . . . . .   7
     2.1.  Variants  . . . . . . . . . . . . . . . . . . . . . . . .   7
     2.2.  Parameters  . . . . . . . . . . . . . . . . . . . . . . .   8
     2.3.  KeyGen  . . . . . . . . . . . . . . . . . . . . . . . . .   9
     2.4.  KeyValidate . . . . . . . . . . . . . . . . . . . . . . .  10
     2.5.  CoreSign  . . . . . . . . . . . . . . . . . . . . . . . .  11
     2.6.  CoreVerify  . . . . . . . . . . . . . . . . . . . . . . .  11
     2.7.  Aggregate . . . . . . . . . . . . . . . . . . . . . . . .  12
     2.8.  CoreAggregateVerify . . . . . . . . . . . . . . . . . . .  12
   3.  BLS Signatures  . . . . . . . . . . . . . . . . . . . . . . .  13
     3.1.  Basic scheme  . . . . . . . . . . . . . . . . . . . . . .  13
       3.1.1.  AggregateVerify . . . . . . . . . . . . . . . . . . .  14
     3.2.  Message augmentation  . . . . . . . . . . . . . . . . . .  14
       3.2.1.  Sign  . . . . . . . . . . . . . . . . . . . . . . . .  14
       3.2.2.  Verify  . . . . . . . . . . . . . . . . . . . . . . .  15
       3.2.3.  AggregateVerify . . . . . . . . . . . . . . . . . . .  15
     3.3.  Proof of possession . . . . . . . . . . . . . . . . . . .  16
       3.3.1.  Parameters  . . . . . . . . . . . . . . . . . . . . .  16
       3.3.2.  PopProve  . . . . . . . . . . . . . . . . . . . . . .  17
       3.3.3.  PopVerify . . . . . . . . . . . . . . . . . . . . . .  17
       3.3.4.  FastAggregateVerify . . . . . . . . . . . . . . . . .  18
Show full document text