Re: [Ntp] [EXT] I-D Action: draft-ietf-ntp-over-ptp-02.txt

[Miroslav Lichvar <[e-mail]>]

On Fri, Jan 19, 2024 at 06:55:41AM +0000, Windl, Ulrich wrote:
> Hi!
> 
> " type is 0x8000 (ORGANIZATION_EXTENSION_DO_NOT_PROPAGATE)" for a prospective standard seems odd (I mean the "do not propagate"), but I admit that I'm unsure what DO_NOT_PROPAGATE actually means for PTP.

The propagation is in respect to data exchanged in PTP announce
messages and boundary clocks. A TLV which should be propagated has to
be saved by the client side of the boundary clock and then included
in its own announce messages transmitted as a server.

In our case with the NTP TLV it shouldn't matter if it's marked as
"propage" or "do not propage" as the TLV is included only in delay
request messages, not announce messages. "do not propagate" seems like
a safer choice in case of bugs.

I understand that having a standard which is not freely available in
normative references is problematic. I'm not sure how well these
things are expected to be explained in an IETF draft.

> I also think that "   This document specifies a transport for the Network Time Protocol
>    (NTP) client-server and symmetric modes using the Precision Time
>    Protocol (PTP)" is sub-optimal: "Isn't it more a "PTP transport for NTP" ? Or is "the PTP protocol" only the packet format?

I probably don't understand the language well enough to see the
difference between the two. Maybe someone else can explain it better.

-- 
Miroslav Lichvar