Hybrid signature spectrums
draft-ietf-pquip-hybrid-signature-spectrums-07

Approval announcement
Draft of message to be sent after approval:

Announcement

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: The IESG <iesg@ietf.org>, draft-ietf-pquip-hybrid-signature-spectrums@ietf.org, paul.hoffman@icann.org, paul.wouters@aiven.io, pqc@ietf.org, pquip-chairs@ietf.org, rfc-editor@rfc-editor.org
Subject: Document Action: 'Hybrid signature spectrums' to Informational RFC (draft-ietf-pquip-hybrid-signature-spectrums-07.txt)

The IESG has approved the following document:
- 'Hybrid signature spectrums'
  (draft-ietf-pquip-hybrid-signature-spectrums-07.txt) as Informational RFC

This document is the product of the Post-Quantum Use In Protocols Working
Group.

The IESG contact persons are Paul Wouters and Deb Cooley.

A URL of this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-pquip-hybrid-signature-spectrums/

Ballot Text

Technical Summary

   This document describes classification of design goals and security
   considerations for hybrid digital signature schemes, including proof
   composability, non-separability of the component signatures given a
   hybrid signature, backwards/forwards compatibility, hybrid
   generality, and simultaneous verification.

   Discussion of this work is encouraged to happen on the IETF PQUIP
   mailing list pqc@ietf.org or on the GitHub repository which contains
   the draft: https://github.com/dconnolly/draft-ietf-pquip-hybrid-
   signature-spectrums

Working Group Summary

   Was there anything in the WG process that is worth noting?
   For example, was there controversy about particular points 
   or were there decisions where the consensus was
   particularly rough? 

Document Quality

   There was broad agreement. One participant had some concerns that might not
   be met in the current draft, but they were not able to give specific text
   to alleviate their conerns; the points they were concerned with should not
   block the document.

   This document not does specify a protocol.

Personnel

   The Document Shepherd for this document is Paul E. Hoffman. The
   Responsible Area Director is Paul Wouters.

RFC Editor Note