Re: [Ntp] Shorter NTS packets?

Hello Miroslav,

I think it will not work well. I understand you and basically it is an interesting idea. But there are some problems from my point of view:

1. you would outsource a NTS security property to NTP to reduce the amount of data. It seems more like a work-around and would not be a good protocol design.

2. if the client requests cookies and uses placeholders, the NTP message will still grow. So it would not solve the problem cleanly.

3. the size of the cookie depends on the AEAD algorithm. Depending on a 256- or 512-bit key, the size grows up to 64 bytes per cookie. Also consider that the server always sends a fresh cookie to the client to ensure unlinkability.

According to the measurements, the frame size of an unsecured NTP packet is around 90 bytes and for NTS secured packets around 270-920 bytes (see here: https://weberblog.net/setting-up-nts-secured-ntp-with-ntpsec/) I hope I could help a bit.

best regards,

Martin

-------------------
Martin Langer, M.Eng.
Ostfalia Hochschule für angewandte Wissenschaften
- Hochschule Braunschweig/Wolfenbüttel
University of Applied Sciences

Labor Datentechnik, Labor Design Digitaler Systeme
Fakultät Elektrotechnik
Salzdahlumer Straße 46/48
38302 Wolfenbüttel
Germany

Tel.: +49 5331 939 43370
Web: https://www.ostfalia.de/cms/de/pws/bermbach/mitarbeiter/martin-langer

________________________________
Von: ntp <ntp-bounces@ietf.org> im Auftrag von Miroslav Lichvar <mlichvar@redhat.com>
Gesendet: Donnerstag, 9. Dezember 2021 10:52:43
An: ntp@ietf.org
Betreff: [Ntp] Shorter NTS packets?

>From the discussion about the alternative port it looks like we might
be stuck with the UDP port 123 forever.

There is one relatively simple thing we could potentially do to make
NTS more reliable without horribly wasting bandwidth. We could make
the Uniq ID extension field optional in some common cases. That would
save 36 octets and make the typical NTPv4+NTS packet short enough to
not be impacted by the length-specific filtering that was described in
this post:

https://weberblog.net/ntp-filtering-delay-blockage-in-the-internet/

The Uniq ID field was added to NTS to avoid any assumptions about
NTP's susceptibility to replay attacks. However, if we specify some
requirements for NTP, the Uniq ID could be unnecessary. Support
for this feature could be negotiated over NTS-KE to avoid
incompatibilities with existing server implementations following
RFC 8915, which requires the Uniq ID to be always present.

The NTP header has the transmit timestamp field (64 bits). It can be
fully randomized (as was proposed in the data minimization draft). The
validity of the server NTS key encrypting cookies can be limited (e.g.
to 1 week) and also the rate of NTP requests can be limited (e.g. to 1
per second). Clients that need to send requests at a higher rate are
likely synchronizing over local network, where the filtering is not
happening, and they could still use the Uniq ID field as before.

Together these limits limit the number of packets authenticated by a
C2S/S2C key. With the 1 week / 1s example that's 604800 packets. If
I'm calculating right that's about 1 in 100 million chance of a
collision per key.

If that is not good enough, the transmit timestamp could be used as a
counter, possibly encrypted to not break the privacy-protecting
property of NTS. This would require the client to be careful with how
it saves the NTS keys and cookies to not reuse a transmit timestamp
after restart, etc.

Does this make sense?

--
Miroslav Lichvar

_______________________________________________
ntp mailing list
ntp@ietf.org
https://www.ietf.org/mailman/listinfo/ntp