<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<br>
*Ahem* REEEEEEEE.......<br>
<br>
You are both talking past each other.<br>
<br>
There are two key sets:<br>
<br>
The c2s/s2c pair. Generated *BY* the TLS exchange between the client
and the NTS-KE server. Stored inside the cookie. Used to encrypt
data between server and client NTPDs thereby eliminating the need
for a TLS session between NTPD clients/servers. Left unchanging,
unless an NTPD sends a KOD and forces the client to re-run the key
exchange protocol.<br>
<br>
The Master Key. Generated by ways as yet undetermined. Used to
encrypt the cookies themselves. Rotated regularly. Shared between a
NTPD server and NTS-KE server by any of several possible means.<br>
<br>
There is never a TLS session between one NTPD node and another NTPD
node; only between a client and an NTS-KE server. <br>
<br>
*HOWEVER*<br>
<br>
There is a TLS session active when c2s/s2c are generated, and the
session generates the keys. So TLS data is relevant to that key
pair.<br>
<br>
It would be advisable to banish the bare word "key" from this
discussion, so that further confusion about which keys are which may
be avoided.<br>
<br>
<div class="moz-signature">-- <br>
<i>"In the end; what separates a Man, from a Slave? Money? Power?
No. A Man Chooses, a Slave Obeys."</i> -- Andrew Ryan
<p>
<i>"Utopia cannot precede the Utopian.
It will exist the moment we are fit to occupy it."</i> --
Sophia Lamb
</p>
<p>
I work for the <a href="https://icei.org/">Internet Civil
Engineering Institute</a>, help us save the Internet from
Entropy!
</p>
</div>
</body>
</html>