[Ntp] Last Call: <draft-ietf-ntp-using-nts-for-ntp-22.txt>

[Daniel Franke]

Hal,

Yes, we'll be getting a new port number, but the more important item
for IANA is the NTP extension registry. I know NTPsec and several
other NTS implementations are all squatting on a set of EF type
numbers and we probably don't want these to change. You and other
maintainers should coordinate in asking IANA to make these assignments
official.

On Fri, Feb 14, 2020 at 2:26 PM Hal Murray via devel <devel at ntpsec.org> wrote:
>
>
> > The IESG plans to make a decision in the next few weeks, and solicits final
> > comments on this action.
>
> I assume we are going to want to do a release as soon as the  RFC is official.
>
> Looks like it will get a new port number so we'll need to do a release to
> support that.  What else do we need to do?
>
> The python stuff is broken.  See #642
> I'd like to see #547 get fixed.
>
> -----------
>
> Subject: [Ntp] Last Call: <draft-ietf-ntp-using-nts-for-ntp-22.txt> (Network
>  Time Security for the Network Time Protocol) to Proposed Standard
> From: The IESG <iesg-secretary at ietf.org>
> Date: Fri, 14 Feb 2020 06:46:16 -0800
> To: "IETF-Announce" <ietf-announce at ietf.org>
> Cc: ntp-chairs at ietf.org, ntp at ietf.org,
>         draft-ietf-ntp-using-nts-for-ntp at ietf.org,
>         "Karen O'Donoghue" <odonoghue at isoc.org>, suresh at kaloom.com
>
> The IESG has received a request from the Network Time Protocol WG (ntp) to
> consider the following document: - 'Network Time Security for the Network
> Time Protocol'
>   <draft-ietf-ntp-using-nts-for-ntp-22.txt> as Proposed Standard
>
> The IESG plans to make a decision in the next few weeks, and solicits final
> comments on this action. Please send substantive comments to the
> last-call at ietf.org mailing lists by 2020-02-28. Exceptionally, comments may
> be sent to iesg at ietf.org instead. In either case, please retain the beginning
> of the Subject line to allow automated sorting.
>
> Abstract
>
>
>    This memo specifies Network Time Security (NTS), a mechanism for
>    using Transport Layer Security (TLS) and Authenticated Encryption
>    with Associated Data (AEAD) to provide cryptographic security for the
>    client-server mode of the Network Time Protocol (NTP).
>
>    NTS is structured as a suite of two loosely coupled sub-protocols.
>    The first (NTS-KE) handles initial authentication and key
>    establishment over TLS.  The second handles encryption and
>    authentication during NTP time synchronization via extension fields
>    in the NTP packets, and holds all required state only on the client
>    via opaque cookies.
>
>
>
>
> The file can be obtained via
> https://datatracker.ietf.org/doc/draft-ietf-ntp-using-nts-for-ntp/
>
> IESG discussion can be tracked via
> https://datatracker.ietf.org/doc/draft-ietf-ntp-using-nts-for-ntp/ballot/
>
>
> No IPR declarations have been submitted directly on this I-D.
>
>
> The document contains these normative downward references.
> See RFC 3967 for additional information:
>     rfc5297: Synthetic Initialization Vector (SIV) Authenticated Encryption
> Using the Advanced Encryption Standard (AES) (Informational - IETF stream)
>
>
>
> --
> These are my opinions.  I hate spam.
>
>
>
> _______________________________________________
> devel mailing list
> devel at ntpsec.org
> http://lists.ntpsec.org/mailman/listinfo/devel