We should be following the guidelines being set by the IEEE 1588 working group – on this topic, specifically IEEE SA - P1588g<https://standards.ieee.org/ieee/1588g/10478/>
This amendment adds an optional alternative suitable and inclusive terminology to the terms “master” and “slave” but it does not replace the terms “master” and “slave” In addition, the amendment fixes errors in the standard and clarifies unclear passages. The latest D1.1 has gone through Ballot 2. Hopefully below summary text from the amendment will help: If alternative terms for “master” and “slave” are used in PTP implementations or PTP Profiles, then the guidelines below should be followed: •In place of the term “master”, use the term “timeTransmitter”. In place of the term “slave”, use the term “timeReceiver”. •Capitalization of the terms remains unchanged. For example, “master” becomes “timeTransmitter”, and “Master” becomes “TimeTransmitter”. •Replacements include parts of compound words. For example, the “<foreignMasterList>” becomes "<foreignTimeTransmitterList>”. •“BMCA” is replaced by “BTCA”, because “Best Master Clock Algorithm” is replaced by “Best TimeTransmitter Clock Algorithm”. •For PTP Port state names: use “TIME_TRANSMITTER” in place of “MASTER”; use “TIME_RECEIVER” in place of “SLAVE”. •When PTP Instance, Clock roles, or PTP Port states are abbreviated in diagrams, the abbreviations are “TT” for timeTransmitter and TIME_TRANSMITTER, and “TR” for timeReceiver and TIME_RECEIVER. The term “Grandmaster” should remain “Grandmaster”. Use of other terms (i.e. client) should be avoided to prevent disconnect from the IEEE standard. Greg Greg Armstrong Principal System Architect, Timing Products Division Renesas Electronics Canada Limited Mobile: 1-613-218-9373 From: Erez <erezge...@gmail.com> Sent: May 16, 2022 6:02 AM To: linuxptp-devel@lists.sourceforge.net; Richard Cochran <richardcoch...@gmail.com> Subject: [Linuxptp-devel] Question regarding terminology of Master and Slave Hi, I remember we had a discussion on the matter. And decide to rename "Master" to "source" and "Slave" to "sink". My questions are: 1. I see in the code "client", for example "clientOnly" mode. When do we use "client" and when do we use "sink"? Are they the same or represent different things? 2. Did we define the border? When do we use the official IEEE "master" and "slave", and when do we use the new "source" and "sink"? I see, for example, the management IDs remain with IEEE terminologie. 3. What about "grandmaster", do we call it grandsource? I think we should set clear rules, so we can minimize the confusion in the project. Something simple like 4-5 rules perhaps. Erez
_______________________________________________ Linuxptp-devel mailing list Linuxptp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
