Steven, That sounds good to me. I tend to see this as "Get the good ideas for possible replacements out there so the folks doing the work have some inspiration for the choices". Please don't take the link as suggesting that list is the end all and be all of possible choices :)
Ed On Tue, Jul 14, 2020 at 11:54 AM Steven Luong (sluong) <slu...@cisco.com> wrote: > The list has a good number of suggestions. In 802.1ax spec, they use the > term aggregator and member link. So I am inclined to stick to > aggregator/member unless someone finds that it is unacceptable. > > > > Steven > > > > *From: *Ed Warnicke <hagb...@gmail.com> > *Date: *Tuesday, July 14, 2020 at 9:45 AM > *To: *"Jerome Tollet (jtollet)" <jtol...@cisco.com> > *Cc: *"Steven Luong (sluong)" <slu...@cisco.com>, "Dave Barach (dbarach)" > <dbar...@cisco.com>, "Kinsella, Ray" <m...@ashroe.eu>, Stephen Hemminger < > step...@networkplumber.org>, "vpp-dev@lists.fd.io" <vpp-dev@lists.fd.io>, > "t...@lists.fd.io" <t...@lists.fd.io>, "Ed Warnicke (eaw)" <e...@cisco.com> > *Subject: *Re: [tsc] [vpp-dev] Replacing master/slave nomenclature > > > > This is a pretty good summary of various suggestions for replacement terms: > > > > > https://www.zdnet.com/article/linux-team-approves-new-terminology-bans-terms-like-blacklist-and-slave/ > > > > Ed > > > > On Tue, Jul 14, 2020 at 11:36 AM Jerome Tollet via lists.fd.io <jtollet= > cisco....@lists.fd.io> wrote: > > Hi Steven, > Please note that per this proposition, https://lkml.org/lkml/2020/7/4/229, > slave must be avoided but master can be kept. > Maybe master/member or master/secondary could be options too. > Jerome > > Le 14/07/2020 18:32, « vpp-dev@lists.fd.io au nom de steven luong via > lists.fd.io » <vpp-dev@lists.fd.io au nom de sluong=cisco....@lists.fd.io> > a écrit : > > I am in the process of pushing a patch to replace master/slave with > aggregator/member for the bonding. > > Steven > > On 7/13/20, 4:44 AM, "vpp-dev@lists.fd.io on behalf of Dave Barach > via lists.fd.io" <vpp-dev@lists.fd.io on behalf of dbarach= > cisco....@lists.fd.io> wrote: > > +1, especially since our next release will be supported for a > year, and API name changes are involved... > > -----Original Message----- > From: Kinsella, Ray <m...@ashroe.eu> > Sent: Monday, July 13, 2020 6:01 AM > To: Dave Barach (dbarach) <dbar...@cisco.com>; Stephen Hemminger < > step...@networkplumber.org>; vpp-dev@lists.fd.io; t...@lists.fd.io; Ed > Warnicke (eaw) <e...@cisco.com> > Subject: Re: [vpp-dev] Replacing master/slave nomenclature > > Hi Stephen, > > I agree, I don't think we should ignore this. > Ed - I suggest we table a discussion at the next FD.io TSC? > > Ray K > > On 09/07/2020 17:05, Dave Barach via lists.fd.io wrote: > > Looping in the technical steering committee... > > > > -----Original Message----- > > From: vpp-dev@lists.fd.io <vpp-dev@lists.fd.io> On Behalf Of > Stephen Hemminger > > Sent: Thursday, July 2, 2020 7:02 PM > > To: vpp-dev@lists.fd.io > > Subject: [vpp-dev] Replacing master/slave nomenclature > > > > Is the VPP project addressing the use of master/slave > nomenclature in the code base, documentation and CLI? We are doing this > for DPDK and it would be good if the replacement wording used in DPDK > matched the wording used in FD.io projects. > > > > Particularly problematic is the use of master/slave in bonding. > > This seems to be a leftover from Linux, since none of the > commercial products use that terminology and it is not present in 802.1AX > standard. > > > > The IEEE and IETF are doing an across the board look at these > terms in standards. > > > > > > > > > > > > >
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#16954): https://lists.fd.io/g/vpp-dev/message/16954 Mute This Topic: https://lists.fd.io/mt/75503014/21656 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
