[TLS] Re: New Version Notification for draft-sullivan-tls-xo f-ciphers-00.txt

John Mattsson <[email protected]> Tue, 28 Jul 2026 10:28:17 +0000
Newsgroups	gmane.ietf.tls
Message-ID	<AS4PR07MB88254ED7B2770683737DCADB89CB2@AS4PR07MB8825.eurprd07.prod.outlook.com>
--===============7638498342074456539==
Content-Language: en-GB
Content-Type: multipart/alternative;
 boundary="_000_AS4PR07MB88254ED7B2770683737DCADB89CB2AS4PR07MB8825eurp_"

--_000_AS4PR07MB88254ED7B2770683737DCADB89CB2AS4PR07MB8825eurp_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi,

Would it make sense to specify the deck function in a separate draft and th=
en reference that from the TLS draft?

For example:

draft-sullivan-tls-deck-schedule + draft-sullivan-deck, or
draft-sullivan-tls-deck-schedule + draft-keccakteam-flightdeck.

I think this would make the architecture cleaner, simplify discussions with=
in the TLS WG, allow the security analysis of the deck to be performed inde=
pendently of TLS, make it easier for TLS to support different deck function=
s, allow deck functions not based on an XOF API, and a generic deck-functio=
n specification would clearly have value beyond TLS.

Cheers,
John Preu=DF Mattsson

--_000_AS4PR07MB88254ED7B2770683737DCADB89CB2AS4PR07MB8825eurp_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
</head>
<body>
<div style=3D"direction: ltr; font-family: Aptos, Arial, Helvetica, sans-se=
rif; font-size: 12pt; color: rgb(0, 0, 0);">
Hi,</div>
<div style=3D"direction: ltr; font-family: Aptos, Arial, Helvetica, sans-se=
rif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Aptos, Arial, Helvetica, sans-serif; font-size: =
12pt; color: rgb(0, 0, 0);">
Would it make sense to specify the deck function in a separate draft and th=
en reference that from the TLS draft?</div>
<div style=3D"direction: ltr; font-family: Aptos, Arial, Helvetica, sans-se=
rif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Aptos, Arial, Helvetica, sans-serif; font-size: =
12pt; color: rgb(0, 0, 0);">
For example:</div>
<div style=3D"direction: ltr; font-family: Aptos, Arial, Helvetica, sans-se=
rif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Aptos, Arial, Helvetica, sans-serif; font-size: =
12pt; color: rgb(0, 0, 0);">
draft-sullivan-tls-deck-schedule + draft-sullivan-deck, or</div>
<div style=3D"font-family: Aptos, Arial, Helvetica, sans-serif; font-size: =
12pt; color: rgb(0, 0, 0);">
draft-sullivan-tls-deck-schedule + draft-keccakteam-flightdeck.</div>
<div style=3D"direction: ltr; font-family: Aptos, Arial, Helvetica, sans-se=
rif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Aptos, Arial, Helvetica, sans-serif; font-size: =
12pt; color: rgb(0, 0, 0);">
I think this would make the architecture cleaner, simplify discussions with=
in the TLS WG, allow the security analysis of the deck to be performed inde=
pendently of TLS, make it easier for TLS to support different deck function=
s, allow deck functions not based
 on an XOF API, and a generic deck-function specification would clearly hav=
e value beyond TLS.</div>
<div style=3D"direction: ltr; font-family: Aptos, Arial, Helvetica, sans-se=
rif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Aptos, Arial, Helvetica, sans-serif; font-size: =
12pt; color: rgb(0, 0, 0);">
Cheers,</div>
<div style=3D"font-family: Aptos, Arial, Helvetica, sans-serif; font-size: =
12pt; color: rgb(0, 0, 0);">
John Preu=DF Mattsson</div>
</body>
</html>

--_000_AS4PR07MB88254ED7B2770683737DCADB89CB2AS4PR07MB8825eurp_--


--===============7638498342074456539==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline

X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KVExTIG1haWxp
bmcgbGlzdCAtLSB0bHNAaWV0Zi5vcmcKVG8gdW5zdWJzY3JpYmUgc2VuZCBhbiBlbWFpbCB0byB0
bHMtbGVhdmVAaWV0Zi5vcmcK

--===============7638498342074456539==--