Few suggestions:
AVB uses end-stations and relays, as well as initiator/responder as the context maybe, like: - PTP End Instance: The AVB talkers and listener end-stations. It may also be a GM. - PTP Relay Instance: Could be inside a bridge, a router, or a multiport end-station. - PTP .1AS initiator: The node that has initiated the Peer-to-Peer delay mechanism. - PTP .1AS responder: The peer-node that is responding to the P2P delay request. And Source/Sink or Client/Server may also be ok, in the documentation. The master/slave etc will have to be replaced in the IEEE 1588 and GM etc all the way to ITU-T telecom standards. The term, “slave” has the negative connotations, rather a “follower” that chooses its leader or role-model (GM -> RM) and looks-up to follow its lead. Anyways, even in the IEEE standard (like Richard mentioned), a master is not employing slaves, instead, it is the follower that is "choosing" who it needs to consider a leader and subsequently follow it, so in our conversations, we are starting to use these terminologies instead. Regards, Jagmeet On Wed, Aug 19, 2020 at 3:26 AM Richard Cochran <richardcoch...@gmail.com> wrote: > On Tue, Aug 18, 2020 at 02:51:26PM -0700, Jacob Keller wrote: > > Yep, makes sense. Long term, after changing the stuff which doesn't > > impact config, we can work towards finding a way to deprecate and rename > > config options in a way that won't break existing deployment. I'm > > personally Ok with simply leaving the original name as a deprecated > > alternative name with an explanation. > > That is what I was thinking, too. > > Thanks, > Richard > > > _______________________________________________ > Linuxptp-devel mailing list > Linuxptp-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/linuxptp-devel > -- Best Regards, ~ Jagmeet Singh Hanspal ~
_______________________________________________ Linuxptp-devel mailing list Linuxptp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
