On Fri, Feb 17, 2017 at 11:08:39AM +0100, Miroslav Lichvar wrote: > Awesome, I didn't realize we already have that :). Full unicast > support doesn't seem very useful to me, but maybe I just didn't see > the right use case for it.
It is specified in one of the telecom profiles. The ITU published two profiles. 1. ITU-1 G.8265.1 Frequency Profile 2. ITU-T G.8275.1 Time and Phase Profile #1 specifies unicast negotiation, forbidding multicast, boundary clocks, and transparent clocks. #2 specifies multicast, forbidding unicast. Transparent clocks are also not allowed, but they are named as a future possibility. Both profiles exhibit a surprising level of cluelessness, but #1 is worse than the other. Thanks, Richard ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot _______________________________________________ Linuxptp-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
