On Mon, Jan 13, 2020 at 6:58 PM Jeremy Harris <j...@wizmail.org> wrote:
> On 13/01/2020 17:48, internet-dra...@ietf.org wrote: > > Title : Batch Signing for TLS > > Author : David Benjamin > > Filename : draft-ietf-tls-batch-signing-00.txt > > Pages : 10 > > Date : 2020-01-13 > > > > Abstract: > > This document describes a mechanism for batch signing in TLS. > > As a non-cryptographer, my immediate question is > "signing of what?" > Whatever input TLS passes into the signing algorithm. :-P I'm being somewhat flippant, but the payloads aren't necessarily anything coherent. See RFC8446, which defines the signing payload for a CertificateVerify message. It's not a coherent protocol entity, rather it's all the context necessary to meet the protocol's security requirements. https://tools.ietf.org/html/rfc8446#section-4.4.3 Other drafts, like delegated credentials, define other payloads. (Although it is unlikely anyone would actually want to batch-sign delegated credentials.) Perhaps "This document described a batched signature algorithm for TLS."?
_______________________________________________ TLS mailing list TLS@ietf.org https://www.ietf.org/mailman/listinfo/tls
