Re: [Ntp] NTS IANA request

I'm strongly opposed to modifying NTS-KE to involve sending a STARTTLS
as a first step of the handshake. I don't want to make a breaking
change to a protocol that's passed WGLC and has four interoperating
implementations in order to accommodate a protocol that has never been
implemented and whose specification consists of three vague sentences
in an unadopted and expired I-D.

If the WG wants to take 123/tcp away from NTP and re-assign it to
NTS-KE, fine. But in that case it should be assigned to the existing
form of NTS-KE, which is a protocol whose immediate first step is to
perform TLS handshake with mandatory ALPN, and any future protocols
which wish to co-exist on 123/tcp will have to operate within the
constraints that that creates.

On Thu, Jun 6, 2019 at 11:06 AM Salz, Rich <rsalz@akamai.com> wrote:
>
> >    What services would they be?  Could some adjustments be made to make
>     NTP/TCP and NTS commpatible?
>
> There are typically two ways this is done.  Peek at the first few bytes and if it looks like a command, assume it's plaintext; many web servers, for example, peek for G E T. The other way is to add a new command to NTP/TCP that says STARTSSL, just like SMTP, NNTP, etc.
>
> The first requires implementers to do the work; the second also requires implementors, but anyone can draft an RFC to add the command :)
>
>
> _______________________________________________
> ntp mailing list
> ntp@ietf.org
> https://www.ietf.org/mailman/listinfo/ntp