IETF Logo Mail Archive

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

최영환 <yhc@etri.re.kr> Fri, 15 September 2023 05:37 UTC

Return-Path: <yhc@etri.re.kr>
X-Original-To: auth48archive@ietfa.amsl.com
Delivered-To: auth48archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BBB59C151063 for <auth48archive@ietfa.amsl.com>; Thu, 14 Sep 2023 22:37:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.904
X-Spam-Level:
X-Spam-Status: No, score=-1.904 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=dooray.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qGPuYNjZIkBT for <auth48archive@ietfa.amsl.com>; Thu, 14 Sep 2023 22:37:11 -0700 (PDT)
Received: from mscreen.etri.re.kr (mscreen.etri.re.kr [129.254.9.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 62FCAC15108C for <auth48archive@rfc-editor.org>; Thu, 14 Sep 2023 22:36:54 -0700 (PDT)
Received: from unknown (HELO send001-relay.gov-dooray.com) (211.180.235.152) by 129.254.9.16 with ESMTP; 15 Sep 2023 14:36:47 +0900
X-Original-SENDERIP: 211.180.235.152
X-Original-MAILFROM: yhc@etri.re.kr
X-Original-RCPTTO: auth48archive@rfc-editor.org, rfc-editor@rfc-editor.org
Received: from [10.162.225.112] (HELO smtp002-imp.gov-dooray.com) ([10.162.225.112]) by send001-relay.gov-dooray.com with SMTP id 944e3d936503ed6f; Fri, 15 Sep 2023 14:36:47 +0900
DKIM-Signature: a=rsa-sha256; b=QkYGQE8FfseuglD3m66b/lrEG5CdxRhOc9qoW3SnnS6aEx/swH1GszxGjLt5KXADyJKCZXEKYM ENe1b0hDe52u4BkXCLwe8tHXKTeqPp11vJIgI9fioBlQJ+GgTKP1n//JXOFDGaWbeGQ74VksMQL8 Spfs/i1bNhpn4AyBSMj4pSHyh1ritXhNPR+XfaXBhqqCEN/7sQdPKh/IYl5eeX8DWM221BST+f93 5uhrqOJ+29AAuUr7Y+a+7Uec+AbhOPoBMGfKmI3NdjrZRUgnsUrIrdvgW+RRKwSgjg2iG2Ujxohd Jw8h/x3LBf7q+Ua5Y6CEwguRe0ESQRDUni2xRWCg==; c=relaxed/relaxed; s=selector; d=dooray.com; v=1; bh=yWRJxZU/lGWOJEvbeoLr6zMAAuf2RGC+KVLLr946WO0=; h=From:To:Subject:Message-ID;
Received: from [129.254.38.88] (HELO smtpclient.apple) ([129.254.38.88]) by smtp002-imp.gov-dooray.com with SMTP id 11093b4e6503ed65; Fri, 15 Sep 2023 14:36:41 +0900
From: 최영환 <yhc@etri.re.kr>
Message-Id: <779CD653-7C6E-4968-A2A0-C5FC6A4D5CA6@etri.re.kr>
Content-Type: multipart/alternative; boundary="Apple-Mail=_94BF89FB-0A80-450E-A359-DCD633B3D20F"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.600.7\))
Date: Fri, 15 Sep 2023 14:36:25 +0900
In-Reply-To: <CACt2foFED-5i_Oy4dqo3f9H2JFdLbT8d5N2T19-LjWhJNCM=dQ@mail.gmail.com>
Cc: Erik Kline <ek.ietf@gmail.com>, Sandy Ginoza <sginoza@amsl.com>, RFC Editor <rfc-editor@rfc-editor.org>, Carles Gomez Montenegro <carles.gomez@upc.edu>, Rashid Sangi <sangi_bahrian@yahoo.com>, samita Chakrabarti <samitac.ietf@gmail.com>, 6lo-ads@ietf.org, 6lo-chairs@ietf.org, Shwetha <shwetha.bhandari@gmail.com>, auth48archive <auth48archive@rfc-editor.org>
To: Yong-Geun Hong <yonggeun.hong@gmail.com>
References: <20230808073125.CCB933E8A7@rfcpa.amsl.com> <FFB231D5-654A-4987-B673-FFBFDC3F8660@etri.re.kr> <CACt2foFEkkgOUor6x5B-Cj3WL06_50vbf2DvrUiz699nhJZAhQ@mail.gmail.com> <CAMGpriVd9jaadsm13aC6JF=tshNN10S-RC2_M=rGGon0kNx2aw@mail.gmail.com> <CACt2foH7Cdw3QJ0dkBqiGMgtfY3RmURxAttae1gKWuRnPc+bbg@mail.gmail.com> <63920AE5-21AC-46D0-A34E-1B07BFDB6BE3@amsl.com> <CAMGpriX2tr15xGJ7f5FHFep8HtUXW1UD=FG=N3Aooa8NTi9c_A@mail.gmail.com> <CACt2foFED-5i_Oy4dqo3f9H2JFdLbT8d5N2T19-LjWhJNCM=dQ@mail.gmail.com>
X-Mailer: Apple Mail (2.3731.600.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/auth48archive/2eyyuG8TpbtooILEVNaxiUJiXVQ>
Subject: Re: [auth48] AUTH48: RFC-to-be 9453 <draft-ietf-6lo-use-cases-16> for your review
X-BeenThere: auth48archive@rfc-editor.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "Archiving AUTH48 exchanges between the RFC Production Center, the authors, and other related parties" <auth48archive.rfc-editor.org>
List-Unsubscribe: <https://mailman.rfc-editor.org/mailman/options/auth48archive>, <mailto:auth48archive-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/auth48archive/>
List-Post: <mailto:auth48archive@rfc-editor.org>
List-Help: <mailto:auth48archive-request@rfc-editor.org?subject=help>
List-Subscribe: <https://mailman.rfc-editor.org/mailman/listinfo/auth48archive>, <mailto:auth48archive-request@rfc-editor.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Sep 2023 05:37:15 -0000

Dear all, 

I agree with the modifications.
Thanks a lot.

Best regards,
Younghwan

> 2023. 9. 15. 오전 10:33, Yong-Geun Hong <yonggeun.hong@gmail.com> 작성:
> 
> 
> 2023년 9월 15일 (금) 오전 9:52, Erik Kline <ek.ietf@gmail.com <mailto:ek.ietf@gmail.com>>님이 작성:
>> On Thu, Sep 14, 2023 at 4:47 PM Sandy Ginoza <sginoza@amsl.com <mailto:sginoza@amsl.com>> wrote:
>> >
>> > 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.
>> 
>> Ah, okay.  Ctrl-f for "master" and for "slave" finds them only ever
>> used within the phrase "Master-Slave/Token Passing (MS/TP)".  There
>> are 3 matches, and one is in the references section.
>> 
>> > > 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]).
>> 
>> I think this sounds perfect, thank you!
> 
> I also agree with this modification. Thank you.
> 
>

v2.23.0 | Report a Bug | By Email