Hi TLS,

Chris Patton and I have produced another revision of our Pseudorandom cTLS
draft, which adds a symmetric key to enable a purely pseudorandom bitstream
(to an observer who doesn't hold the cTLS template).

Some changes in this draft:

* Rebase across changes in cTLS-05, which help to simplify this
specification.
* Add a Key Derivation step and simplify the tweak construction.
* Define an optional Protocol Confusion defense that injects fresh entropy
into every message.
* Reserve a codepoint for experimental use of a specific underlying cipher
(HCTR2)
* Describe a reliable procedure for key rotation.
* Remove tricky state machine recommendations; recommend authenticating the
ClientHello instead.
* Numerous other text changes: new "experiment" section, s/STPRP/TSPRP/,
discussion of the cTLS extension mechanism, etc.

We believe this draft is nearly ready for WG adoption, and will be
implementable once the open issues in the cTLS draft are addressed.  Please
review.

Thanks,
Ben Schwartz

---------- Forwarded message ---------
From: <internet-dra...@ietf.org>
Date: Sun, Apr 10, 2022 at 8:40 PM
Subject: New Version Notification for draft-cpbs-pseudorandom-ctls-01.txt
To: Benjamin Schwartz <bem...@google.com>, Christopher Patton <
cpat...@cloudflare.com>



A new version of I-D, draft-cpbs-pseudorandom-ctls-01.txt
has been successfully submitted by Benjamin Schwartz and posted to the
IETF repository.

Name:           draft-cpbs-pseudorandom-ctls
Revision:       01
Title:          The Pseudorandom Extension for cTLS
Document date:  2022-04-11
Group:          Individual Submission
Pages:          13
URL:
https://www.ietf.org/archive/id/draft-cpbs-pseudorandom-ctls-01.txt
Status:
https://datatracker.ietf.org/doc/draft-cpbs-pseudorandom-ctls/
Html:
https://www.ietf.org/archive/id/draft-cpbs-pseudorandom-ctls-01.html
Htmlized:
https://datatracker.ietf.org/doc/html/draft-cpbs-pseudorandom-ctls
Diff:
https://www.ietf.org/rfcdiff?url2=draft-cpbs-pseudorandom-ctls-01

Abstract:
   This draft describes a cTLS extension that allows each party to emit
   a purely pseudorandom bitstream.

Discussion Venues

   This note is to be removed before publishing as an RFC.

   Source for this draft and an issue tracker can be found at
   https://github.com/bemasc/pseudorandom-ctls.




The IETF Secretariat

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

_______________________________________________
TLS mailing list
TLS@ietf.org
https://www.ietf.org/mailman/listinfo/tls

Reply via email to