<div dir="auto">A different RFC, eventually. But I'm not in a rush. Let people managing large scale deployments figure out what works for them and then standardize around it later.</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Mar 6, 2019, 13:25 Achim Gratz via devel <<a href="mailto:devel@ntpsec.org">devel@ntpsec.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Daniel Franke via devel writes:<br>
> That's correct: ensuring interop between differing implementations of the<br>
> NTS-KE server and the NTP server is outside the scope of this document.<br>
<br>
So what are the plans for that department?  Have everything bloom into<br>
chaos or put it into a different RFC?<br>
<br>
<br>
Regards,<br>
Achim.<br>
-- <br>
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+<br>
<br>
Samples for the Waldorf Blofeld:<br>
<a href="http://Synth.Stromeko.net/Downloads.html#BlofeldSamplesExtra" rel="noreferrer noreferrer" target="_blank">http://Synth.Stromeko.net/Downloads.html#BlofeldSamplesExtra</a><br>
<br>
_______________________________________________<br>
devel mailing list<br>
<a href="mailto:devel@ntpsec.org" target="_blank" rel="noreferrer">devel@ntpsec.org</a><br>
<a href="http://lists.ntpsec.org/mailman/listinfo/devel" rel="noreferrer noreferrer" target="_blank">http://lists.ntpsec.org/mailman/listinfo/devel</a><br>
</blockquote></div>