Re: [auth48] AUTH48: RFC-to-be 9453 <draft-ietf-6lo-use-cases-16> for your review

[Sandy Ginoza <[e-mail]>]

Hi Yong-Geun and Erik,

I don’t think it’s clear that those words are being used for consistency with the referenced materials and within the industry.  

> Is there a way to leave it as is but add a kind of a footnote about
> the terminology?


Perhaps something like this could be added to the end of the introduction? 

Note that the use of “master” and “slave” have been retained in this document to align with use within the industry (e.g., [TIA-485-A] and [BACnet]).

Thanks,
RFC Editor/sg



> On Sep 12, 2023, at 7:40 PM, Yong-Geun Hong <[e-mail]> wrote:
> 
> Dear Eric.
> 
> Thanks for your comments.
> 
> Regarding your comment, I tried to find relevant references. 
> 
> In the RFC8163(Transmission of IPv6 over Master-Slave/Token-Passing (MS/TP) Networks), 
> there are two related paragraphs.
> 
> "Master-Slave/Token-Passing (MS/TP) is a Medium Access Control (MAC)
>    protocol for the RS-485 [TIA-485-A] physical layer and is used
>    primarily in building automation networks." 
> 
> " This section provides a brief overview of MS/TP, as specified in
>    Clause 9 of the ANSI/ASHRAE Standard 135-2016 [BACnet].  The latest
>    version of [BACnet] integrates changes to legacy MS/TP (approved as
>    [Addendum_an]) that provide support for larger frame sizes and
>    improved error handling.  [BACnet], Clause 9 also covers physical-
>    layer deployment options."
> 
> And the [TIA-485-A] and [BACnet] references are that ; 
> 
>    [TIA-485-A]
>               TIA, "Electrical Characteristics of Generators and
>               Receivers for Use in Balanced Digital Multipoint Systems",
>               TIA-485-A (Revision of TIA-485), March 2003,
>               <https://global.ihs.com/
>               doc_detail.cfm?item_s_key=00032964>.
> 
>    [BACnet]   ASHRAE, "BACnet-A Data Communication Protocol for Building
>               Automation and Control Networks", ANSI/ASHRAE Standard
>               135-2016, January 2016,
>               <http://www.techstreet.com/ashrae/standards/
>               ashrae-135-2016?product_id=1918140#jumps>.
> 
> In the 6lo use case draft, we already have the two [TIA-485-A] and  [BACnet] references.
> But, the  [Addendum_an] reference is not included in the 6lo use case draft.
> 
>    [Addendum_an]
>               ANSI/ASHRAE, "Addenda: BACnet -- A Data Communication
>               Protocol for Building Automation and Control Networks",
>               ANSI/ASHRAE Addenda an, at, au, av, aw, ax, and az
>               to ANSI/ASHRAE Standard 135-2012, July 2014,
>               <https://www.ashrae.org/File%20Library/docLib/StdsAddenda/
>               07-31-2014_135_2012_an_at_au_av_aw_ax_az_Final.pdf>.
> 
> If it is necessary to show something, we can add one more MS/TP related reference [Addendum_an].
> 
> Best regards.
> 
> Yong-Geun. 
> 
> 2023년 9월 11일 (월) 오후 3:08, Erik Kline <[e-mail]>님이 작성:
> >> 16) <!-- [rfced] Please review the "Inclusive Language" portion of the
> >> online Style Guide <https://www.rfc-editor.org/styleguide/part2/#inclusive_language>
> >> and let us know if any changes are needed.
> >>
> >> For example, please consider whether the following should be updated:
> >>   Master
> >>   Slave
> >
> > [Yong-Geun] The expression of ‘Master’ and ‘Slave’ is not inclusive language but is a technical word. I think it is O.K.
> 
> RFC Editor,
> 
> The only reference I see in the document is for the Master-Slave/Token
> Passing protocol.  Some light Googling suggests that this is in fact a
> thing, and a thing with a regrettable name.
> 
> Is there a way to leave it as is but add a kind of a footnote about
> the terminology?  Additionally/alternatively, perhaps Yong-Geun might
> be able to find a reference to a standard that we might add to the
> Informational references section (thereby reinforcing that this is the
> name of a specific thing in industry automation circles).
> 
> -ek