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

"Chakrabarti, Samita" <samita.chakrabarti@verizon.com> Wed, 06 September 2023 15:48 UTC

Return-Path: <samita.chakrabarti@verizon.com>
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 D9380C151538 for <auth48archive@ietfa.amsl.com>; Wed, 6 Sep 2023 08:48:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.102
X-Spam-Level:
X-Spam-Status: No, score=-7.102 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=verizon.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 rbVgZSX1cAD4 for <auth48archive@ietfa.amsl.com>; Wed, 6 Sep 2023 08:48:01 -0700 (PDT)
Received: from mx0a-0024a201.pphosted.com (mx0a-0024a201.pphosted.com [148.163.149.93]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B02C1C151094 for <auth48archive@rfc-editor.org>; Wed, 6 Sep 2023 08:48:01 -0700 (PDT)
Received: from pps.filterd (m0114266.ppops.net [127.0.0.1]) by mx0a-0024a201.pphosted.com (8.17.1.19/8.17.1.19) with ESMTP id 386ChZ5u021470 for <auth48archive@rfc-editor.org>; Wed, 6 Sep 2023 11:48:01 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=verizon.com; h=mime-version : references : in-reply-to : from : date : message-id : subject : to : cc : content-type; s=prodmail; bh=8sVFRZpVxgMdIr6eZhrmo5qKhak1J3emIzDVHkV2Nqo=; b=Tg3qIEp/F0Gcesb2yMqMd2S3hzkRW9sak3lXTZy9LKosYzOWgCahsYCaOpya8Jn5fXGL 3IQD676BU6g5JK5K3Q02+f50NdliELRi6Dg52EK8ml0WGs+QuR88tzIIpdqf2AlyVmjf QeSW9rxypOd0d1jB+ZgFptCCe8nYvZh45Yrm/2V5AEhJW43c05nXYAnA9DdM1BXehcNd P7eAUl+FoZGBGpyEKO6QnzAMQZi8SY5EoL7LF09KZk4Fw6r15UuCgX9cV/faRY4Ij7cm kUbu/Cpoe1rwp6ScAWMxtlACOv1UMVURULvGd76C6BiKOoppQyWTOp8Db7RfGvcnTEsj qQ==
Received: from mail-yw1-f199.google.com (mail-yw1-f199.google.com [209.85.128.199]) by mx0a-0024a201.pphosted.com (PPS) with ESMTPS id 3sxeut93xr-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT) for <auth48archive@rfc-editor.org>; Wed, 06 Sep 2023 11:47:59 -0400
Received: by mail-yw1-f199.google.com with SMTP id 00721157ae682-58cbf62bae8so40711917b3.3 for <auth48archive@rfc-editor.org>; Wed, 06 Sep 2023 08:47:58 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1694015277; x=1694620077; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=8sVFRZpVxgMdIr6eZhrmo5qKhak1J3emIzDVHkV2Nqo=; b=XAg4Jo7w23nbiNbT766bxkqhYxFm4CdhzvIwCsvDU6Bjrp0sXSAD413UEKJSV6FN/h kWAOvWEAKTrkFrOtoUvNrEpGOwTKlv4EPFI4JoqaqGZSYucPnHGnQgzsn1CCIq8zf2as heIEdhsQAiDtxHI2w4cj2LGUsTeiDkRzTN+qQ5pOFP20Xplxe5jyTLndFEPRh2elic6m yVIoxN+VdTDRLFYe+bnUumCPsxkWG5Q1W51xNJtStzc6AeNlrHcdG47C+lRe+y6I2nSc 2PDdCCT/uFq6il+la9w1cSp0LVvtT6tnabbjYKtbSfvJNdLpjwhm3BLONDM1ZQALPqNC 53RQ==
X-Gm-Message-State: AOJu0Yxhgicj9nkDc+xJ+FCC3EbG+QhJq/Q+TBjRDi2dkXS5c22G+/+f wm5OcfFmTrDKM+vx1pBcrnCH20mZ/XL3fN1mJpajfCUahMYJCeVcrOKKDq5ZsaJ8d4tpvaNKmUH hUffWcQwzrk7ErF7f5xeso5E/FXAkC17U7x47xhR/
X-Received: by 2002:a0d:d493:0:b0:589:e586:6f0a with SMTP id w141-20020a0dd493000000b00589e5866f0amr19245815ywd.3.1694015276786; Wed, 06 Sep 2023 08:47:56 -0700 (PDT)
X-Google-Smtp-Source: AGHT+IGXjWwst0yvbtzGvLPz7jyHPmHcvSG9fG+19wxapIUidgoiI2zG9ApCMQX1aeR7ZZiZ4lG3LHAf63N9wt+fhUI=
X-Received: by 2002:a0d:d493:0:b0:589:e586:6f0a with SMTP id w141-20020a0dd493000000b00589e5866f0amr19245769ywd.3.1694015276045; Wed, 06 Sep 2023 08:47:56 -0700 (PDT)
MIME-Version: 1.0
References: <20230808073125.CCB933E8A7@rfcpa.amsl.com> <FFB231D5-654A-4987-B673-FFBFDC3F8660@etri.re.kr> <CACt2foFEkkgOUor6x5B-Cj3WL06_50vbf2DvrUiz699nhJZAhQ@mail.gmail.com> <0BAA6F3B-0664-4757-A73A-D1D78B164A51@amsl.com> <CACt2foFgXX9g-cu=K1t73DvPVX0DGWUkN1mZuBG4ke_ffZ+4RQ@mail.gmail.com> <371CB92D-5DF4-4712-A74E-B480CDFEE847@amsl.com> <CACt2foEcX1Wwae9mH=tYa_noXC+25rotr_k_XHU3W7gYZV0pLQ@mail.gmail.com> <rhf7dm98xzq5.rhf7dm97nbu6.g1@dooray.com> <6AD4005B-065D-463A-8A27-F2462D041505@amsl.com> <1421995501.1889822.1693544394682@mail.yahoo.com> <CAAUO2xyhFkNqV9u30s8romaqWrEmaeLgC7QT8N4RaVcbtk2uEA@mail.gmail.com> <C3B221B1-E5A4-4358-B45D-099C78A55F86@amsl.com> <5FD01940-6EA9-4069-893C-8D8CA57B1BB2@amsl.com> <CAKmdBpf10XBv2OBseZ29Tjvkbv0h3O8wT8bu992K1m86KVuDRQ@mail.gmail.com> <D7E02C49-CBCC-4705-9395-B5F9F2D4490E@amsl.com>
In-Reply-To: <D7E02C49-CBCC-4705-9395-B5F9F2D4490E@amsl.com>
From: "Chakrabarti, Samita" <samita.chakrabarti@verizon.com>
Date: Wed, 06 Sep 2023 11:47:42 -0400
Message-ID: <CAHYRG6P5u4-ikCvG6ugHi9S_tzN24E=6zX5MAA6UW_MBzb9+XA@mail.gmail.com>
To: Sandy Ginoza <sginoza@amsl.com>
Cc: Samita Chakrabarti <samitac.ietf@gmail.com>, Carles Gomez Montenegro <carles.gomez@upc.edu>, Rashid Sangi <sangi_bahrian@yahoo.com>, 최영환 <yhc@etri.re.kr>, Yong-Geun Hong <yonggeun.hong@gmail.com>, RFC Editor <rfc-editor@rfc-editor.org>, 6lo-ads@ietf.org, 6lo-chairs@ietf.org, Shwetha <shwetha.bhandari@gmail.com>, Erik Kline <ek.ietf@gmail.com>, auth48archive@rfc-editor.org
Content-Type: multipart/alternative; boundary="000000000000c5ed460604b2aa4c"
X-mailroute: internal
X-Proofpoint-GUID: 2luKeC8DW18PRo_a8L3KvyxSZXMQMhl8
X-Proofpoint-ORIG-GUID: 2luKeC8DW18PRo_a8L3KvyxSZXMQMhl8
Archived-At: <https://mailarchive.ietf.org/arch/msg/auth48archive/aa7ybHWczcgLzdgS6wh1iA3Pp2Q>
Subject: Re: [auth48] [E] Re: 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: Wed, 06 Sep 2023 15:48:05 -0000

Looks good. Thank you.
-Samita

On Wed, Sep 6, 2023 at 11:35 AM Sandy Ginoza <sginoza@amsl.com> wrote:

> Hi Samita,
>
> Thank you for your reply.  We have updated the document as described below
> and posted the revised files here?
>
>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.rfc-2Deditor.org_authors_rfc9453.xml&d=DwIFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=pWMzx7FsqijEJPyfMBfn-HJss-wVVTf0K5y-cxCTXL8&m=h7eY105YwBdd1cBwW79HiOwMaHGLKd6Ir5Bzi2wBityeE2Xmz-hl5ZHLMSLowNfq&s=Ln9_Xwwx93738eRVlzbwjGUpVsr1IVaWKQjSb2ku5GI&e=
>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.rfc-2Deditor.org_authors_rfc9453.txt&d=DwIFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=pWMzx7FsqijEJPyfMBfn-HJss-wVVTf0K5y-cxCTXL8&m=h7eY105YwBdd1cBwW79HiOwMaHGLKd6Ir5Bzi2wBityeE2Xmz-hl5ZHLMSLowNfq&s=heABRT-P-Km8JMhNN4zFcGyHBsQrAyCOaR_9h8AtiC8&e=
>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.rfc-2Deditor.org_authors_rfc9453.pdf&d=DwIFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=pWMzx7FsqijEJPyfMBfn-HJss-wVVTf0K5y-cxCTXL8&m=h7eY105YwBdd1cBwW79HiOwMaHGLKd6Ir5Bzi2wBityeE2Xmz-hl5ZHLMSLowNfq&s=Cy9Y202bSvTBue1bsjlKvY2eZH64kUAJEYdUkjtSEfs&e=
>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.rfc-2Deditor.org_authors_rfc9453.html&d=DwIFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=pWMzx7FsqijEJPyfMBfn-HJss-wVVTf0K5y-cxCTXL8&m=h7eY105YwBdd1cBwW79HiOwMaHGLKd6Ir5Bzi2wBityeE2Xmz-hl5ZHLMSLowNfq&s=v7NzwyI1zUJ5a4oVqQrupZGQVtXaFGGZTRk3yfRs5IQ&e=
>
> Diffs highlighting the most recent updates only:
>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.rfc-2Deditor.org_authors_rfc9453-2Dlastdiff.html&d=DwIFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=pWMzx7FsqijEJPyfMBfn-HJss-wVVTf0K5y-cxCTXL8&m=h7eY105YwBdd1cBwW79HiOwMaHGLKd6Ir5Bzi2wBityeE2Xmz-hl5ZHLMSLowNfq&s=Gk6-MhCDp3pAzYHginrKvgGvoYVCOTIOmnI8Bt_x4Kk&e=
>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.rfc-2Deditor.org_authors_rfc9453-2Dlastrfcdiff.html&d=DwIFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=pWMzx7FsqijEJPyfMBfn-HJss-wVVTf0K5y-cxCTXL8&m=h7eY105YwBdd1cBwW79HiOwMaHGLKd6Ir5Bzi2wBityeE2Xmz-hl5ZHLMSLowNfq&s=1NWdrhehlsgON0g-HjhWC9BQXDaWwoVNR2FngxsN15Q&e=
>
> AUTH48 diff:
>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.rfc-2Deditor.org_authors_rfc9453-2Dauth48diff.html&d=DwIFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=pWMzx7FsqijEJPyfMBfn-HJss-wVVTf0K5y-cxCTXL8&m=h7eY105YwBdd1cBwW79HiOwMaHGLKd6Ir5Bzi2wBityeE2Xmz-hl5ZHLMSLowNfq&s=Fptx-PlxUFZ4FpzdhvtLbxzyOY5r_o1qTIFaG9TPaUc&e=
>
> Comprehensive diffs:
>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.rfc-2Deditor.org_authors_rfc9453-2Ddiff.html&d=DwIFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=pWMzx7FsqijEJPyfMBfn-HJss-wVVTf0K5y-cxCTXL8&m=h7eY105YwBdd1cBwW79HiOwMaHGLKd6Ir5Bzi2wBityeE2Xmz-hl5ZHLMSLowNfq&s=_4aZM5Hf8YQWqnpmHGTGMnZGejR-0eAhoL8NzBUmFFY&e=
>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.rfc-2Deditor.org_authors_rfc9453-2Drfcdiff.html&d=DwIFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=pWMzx7FsqijEJPyfMBfn-HJss-wVVTf0K5y-cxCTXL8&m=h7eY105YwBdd1cBwW79HiOwMaHGLKd6Ir5Bzi2wBityeE2Xmz-hl5ZHLMSLowNfq&s=KqFP7uDVI7fQ9SzHBgjURncDez_9RxYXpkqxA5v3cUQ&e=
>
>
> With this update, we believe you approve the RFC for publication.  We have
> marked your approval on the AUTH48 page <
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.rfc-2Deditor.org_auth48_rfc9453&d=DwIFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=pWMzx7FsqijEJPyfMBfn-HJss-wVVTf0K5y-cxCTXL8&m=h7eY105YwBdd1cBwW79HiOwMaHGLKd6Ir5Bzi2wBityeE2Xmz-hl5ZHLMSLowNfq&s=7MYfVC9otpNCIXilfJJpjKhNuFifhP7pkrYOHMe1SHQ&e=
> and we will continue with the publication process shortly.
>
> Thank you,
> RFC Editor/sg
>
>
>
>
>
>
>
> > On Sep 5, 2023, at 1:58 PM, Samita Chakrabarti <samitac.ietf@gmail.com>
> wrote:
> >
> > Hi Sandy,
> >
> > Sorry, I missed the messages earlier.  Now adding my work email to the
> distribution list.
> >
> > I am fine with the document.  A few changes regarding my information.
> >
> > At the very end:
> >
> > Samita Chakrabarti
> > Bedminster, NJ
> > USA
> > Email: samita.chakrabarti@verizon.com
> >
> >
> > And my affiliation is Verizon.
> >
> > Thanks,
> > -Samita
> >
> > On Tue, Sep 5, 2023, 12:54 PM Sandy Ginoza <sginoza@amsl.com> wrote:
> > Hi Samita,
> >
> > We do not believe we have heard from you regarding this document’s
> readiness for publication.  Please review the files at the URLs below and
> let us know if any updates are needed or if you approve the RFC for
> publication.  Please let us know if you would like to update your
> affiliation and contact information.
> >
> > Thank you,
> > RFC Editor/sg
> >
> >
> >
> > > On Sep 1, 2023, at 8:26 AM, Sandy Ginoza <sginoza@amsl.com> wrote:
> > >
> > > Hi Carles, Rashid,
> > >
> > > Thank you for your reviews.  We have updated the document as described
> by Carles and posted the revised files here:
> > >
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.rfc-2Deditor.org_authors_rfc9453.xml&d=DwIFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=pWMzx7FsqijEJPyfMBfn-HJss-wVVTf0K5y-cxCTXL8&m=h7eY105YwBdd1cBwW79HiOwMaHGLKd6Ir5Bzi2wBityeE2Xmz-hl5ZHLMSLowNfq&s=Ln9_Xwwx93738eRVlzbwjGUpVsr1IVaWKQjSb2ku5GI&e=
> > >
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.rfc-2Deditor.org_authors_rfc9453.txt&d=DwIFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=pWMzx7FsqijEJPyfMBfn-HJss-wVVTf0K5y-cxCTXL8&m=h7eY105YwBdd1cBwW79HiOwMaHGLKd6Ir5Bzi2wBityeE2Xmz-hl5ZHLMSLowNfq&s=heABRT-P-Km8JMhNN4zFcGyHBsQrAyCOaR_9h8AtiC8&e=
> > >
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.rfc-2Deditor.org_authors_rfc9453.pdf&d=DwIFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=pWMzx7FsqijEJPyfMBfn-HJss-wVVTf0K5y-cxCTXL8&m=h7eY105YwBdd1cBwW79HiOwMaHGLKd6Ir5Bzi2wBityeE2Xmz-hl5ZHLMSLowNfq&s=Cy9Y202bSvTBue1bsjlKvY2eZH64kUAJEYdUkjtSEfs&e=
> > >
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.rfc-2Deditor.org_authors_rfc9453.html&d=DwIFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=pWMzx7FsqijEJPyfMBfn-HJss-wVVTf0K5y-cxCTXL8&m=h7eY105YwBdd1cBwW79HiOwMaHGLKd6Ir5Bzi2wBityeE2Xmz-hl5ZHLMSLowNfq&s=v7NzwyI1zUJ5a4oVqQrupZGQVtXaFGGZTRk3yfRs5IQ&e=
> > >
> > > Diffs highlighting the updates described below only:
> > >
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.rfc-2Deditor.org_authors_rfc9453-2Dlastdiff.html&d=DwIFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=pWMzx7FsqijEJPyfMBfn-HJss-wVVTf0K5y-cxCTXL8&m=h7eY105YwBdd1cBwW79HiOwMaHGLKd6Ir5Bzi2wBityeE2Xmz-hl5ZHLMSLowNfq&s=Gk6-MhCDp3pAzYHginrKvgGvoYVCOTIOmnI8Bt_x4Kk&e=
> > >
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.rfc-2Deditor.org_authors_rfc9453-2Dlastrfcdiff.html&d=DwIFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=pWMzx7FsqijEJPyfMBfn-HJss-wVVTf0K5y-cxCTXL8&m=h7eY105YwBdd1cBwW79HiOwMaHGLKd6Ir5Bzi2wBityeE2Xmz-hl5ZHLMSLowNfq&s=1NWdrhehlsgON0g-HjhWC9BQXDaWwoVNR2FngxsN15Q&e=
> > >
> > > AUTH48 diff:
> > >
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.rfc-2Deditor.org_authors_rfc9453-2Dauth48diff.html&d=DwIFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=pWMzx7FsqijEJPyfMBfn-HJss-wVVTf0K5y-cxCTXL8&m=h7eY105YwBdd1cBwW79HiOwMaHGLKd6Ir5Bzi2wBityeE2Xmz-hl5ZHLMSLowNfq&s=Fptx-PlxUFZ4FpzdhvtLbxzyOY5r_o1qTIFaG9TPaUc&e=
> > >
> > > Comprehensive diffs:
> > >
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.rfc-2Deditor.org_authors_rfc9453-2Ddiff.html&d=DwIFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=pWMzx7FsqijEJPyfMBfn-HJss-wVVTf0K5y-cxCTXL8&m=h7eY105YwBdd1cBwW79HiOwMaHGLKd6Ir5Bzi2wBityeE2Xmz-hl5ZHLMSLowNfq&s=_4aZM5Hf8YQWqnpmHGTGMnZGejR-0eAhoL8NzBUmFFY&e=
> > >
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.rfc-2Deditor.org_authors_rfc9453-2Drfcdiff.html&d=DwIFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=pWMzx7FsqijEJPyfMBfn-HJss-wVVTf0K5y-cxCTXL8&m=h7eY105YwBdd1cBwW79HiOwMaHGLKd6Ir5Bzi2wBityeE2Xmz-hl5ZHLMSLowNfq&s=KqFP7uDVI7fQ9SzHBgjURncDez_9RxYXpkqxA5v3cUQ&e=
> > >
> > >
> > > We have marked both of your approvals on the AUTH48 page <
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.rfc-2Deditor.org_auth48_rfc9453&d=DwIFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=pWMzx7FsqijEJPyfMBfn-HJss-wVVTf0K5y-cxCTXL8&m=h7eY105YwBdd1cBwW79HiOwMaHGLKd6Ir5Bzi2wBityeE2Xmz-hl5ZHLMSLowNfq&s=7MYfVC9otpNCIXilfJJpjKhNuFifhP7pkrYOHMe1SHQ&e=
> >.  We will wait to hear from Samita Chakrabarti before continuing with the
> process.
> > >
> > > Thank you,
> > > RFC Editor/sg
> > >
> > >
> > >
> > >
> > >
> > >
> > >> On Aug 31, 2023, at 10:53 PM, Carles Gomez Montenegro <
> carles.gomez@upc.edu> wrote:
> > >>
> > >> Dear Sandy, all,
> > >>
> > >> Many thanks for the editorial work done.
> > >>
> > >> I have two update requests, as shown below.
> > >>
> > >>
> > >> 1. In the Acknowledgments section, first paragraph:
> > >>
> > >> OLD:
> > >>     2017 through grant SGR 376.
> > >>
> > >> NEW:
> > >>     through grants 2017 SGR 376 and 2021 SGR 00330.
> > >>
> > >>
> > >> 2. In the Authors' Addresses section:
> > >>
> > >> OLD:
> > >>       Universitat Politecnica de Catalunya/Fundacio i2cat
> > >>
> > >> NEW:
> > >>       Universitat Politecnica de Catalunya
> > >>
> > >> Other than the above, I approve the RFC for publication.
> > >>
> > >> Once again, many thanks.
> > >>
> > >> Best regards,
> > >>
> > >> Carles Gomez
> > >>
> > >> On Fri, 1 Sept 2023 at 07:00, Rashid Sangi <sangi_bahrian@yahoo.com>
> wrote:
> > >>>
> > >>> Dear all,
> > >>>
> > >>> Thank you for your efforts.
> > >>>
> > >>> There is no update request from my side.
> > >>>
> > >>> Regards,
> > >>> Rashid Sangi
> > >>>
> > >>> On Friday, September 1, 2023 at 12:42:59 PM GMT+8, Sandy Ginoza <
> sginoza@amsl.com> wrote:
> > >>>
> > >>>
> > >>> Greetings Younghwan Choi and Yong-Geun,
> > >>>
> > >>> Thank you for your review.  We have noted your approvals on the
> AUTH48 page <
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.rfc-2Deditor.org_auth48_rfc9453&d=DwIFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=pWMzx7FsqijEJPyfMBfn-HJss-wVVTf0K5y-cxCTXL8&m=h7eY105YwBdd1cBwW79HiOwMaHGLKd6Ir5Bzi2wBityeE2Xmz-hl5ZHLMSLowNfq&s=7MYfVC9otpNCIXilfJJpjKhNuFifhP7pkrYOHMe1SHQ&e=
> >.
> > >>>
> > >>> We will wait to hear from each of your coauthors before continuing
> with the publication process.  In particular, we will confirm Samita's
> affiliation prior to publication.
> > >>>
> > >>> Thank you,
> > >>> RFC Editor/sg
> > >>>
> > >>>
> > >>>
> > >>>> On Aug 31, 2023, at 9:17 PM, 최영환 <yhc@etri.re.kr> wrote:
> > >>>>
> > >>>> Dear Sandy Ginoza and Yong-Geun,
> > >>>>
> > >>>> I am Younghwan Choi, who is one of the authors.
> > >>>> I have no comments on the updates.
> > >>>>
> > >>>> Many thanks.
> > >>>>
> > >>>> Best Regards,
> > >>>> Younghwan Choi
> > >>>>
> > >>>> -----------------------------------
> > >>>> YOUNGHWAN CHOI, Ph.D.
> > >>>> Principal Researcher, PEC, ETRI
> > >>>> Tel +82-42-860-1429  Fax +82-42-860-5404
> > >>>> Email  yhc@etri.re.kr
> > >>>>
> > >>>>
> > >>>> -----Original Message-----
> > >>>> From: "Yong-Geun Hong" <yonggeun.hong@gmail.com>
> > >>>> To: "Sandy Ginoza" <sginoza@amsl.com>;
> > >>>> Cc: "RFC Editor" <rfc-editor@rfc-editor.org>; "Carles Gomez
> Montenegro" <carles.gomez@upc.edu>; "최영환" <yhc@etri.re.kr>; "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>; "Erik Kline" <ek.ietf@gmail.com>;
> <auth48archive@rfc-editor.org>;
> > >>>> Sent: 2023-09-01 (금) 10:02:17 (UTC+09:00)
> > >>>> Subject: Re: AUTH48: RFC-to-be 9453 <draft-ietf-6lo-use-cases-16>
> for your review
> > >>>>
> > >>>> Dear Sandy Ginoza.
> > >>>>
> > >>>> Thanks again for your efforts.
> > >>>>
> > >>>> From my side, there is no request to update. Everything is O.K.
> > >>>>
> > >>>> I want to check one thing for Samita's affiliation.
> > >>>> Samita, if you want to reflect your new affiliation, let us know.
> > >>>>
> > >>>> Best regards.
> > >>>>
> > >>>> Yong-Geun.
> > >>>>
> > >>>> 2023년 9월 1일 (금) 오전 8:40, Sandy Ginoza <sginoza@amsl.com>님이 작성:
> > >>>> Hi Yong-Geun, Authors,
> > >>>>
> > >>>> We have updated the document as described below.  Please review and
> let us know if any additional updates are needed or if you approve the RFC
> for publication.
> > >>>>
> > >>>> Note that we require an approval from each individual listed in the
> document header.
> > >>>>
> > >>>>
> > >>>> The files are available here:
> > >>>>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.rfc-2Deditor.org_authors_rfc9453.xml&d=DwIFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=pWMzx7FsqijEJPyfMBfn-HJss-wVVTf0K5y-cxCTXL8&m=h7eY105YwBdd1cBwW79HiOwMaHGLKd6Ir5Bzi2wBityeE2Xmz-hl5ZHLMSLowNfq&s=Ln9_Xwwx93738eRVlzbwjGUpVsr1IVaWKQjSb2ku5GI&e=
> > >>>>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.rfc-2Deditor.org_authors_rfc9453.txt&d=DwIFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=pWMzx7FsqijEJPyfMBfn-HJss-wVVTf0K5y-cxCTXL8&m=h7eY105YwBdd1cBwW79HiOwMaHGLKd6Ir5Bzi2wBityeE2Xmz-hl5ZHLMSLowNfq&s=heABRT-P-Km8JMhNN4zFcGyHBsQrAyCOaR_9h8AtiC8&e=
> > >>>>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.rfc-2Deditor.org_authors_rfc9453.pdf&d=DwIFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=pWMzx7FsqijEJPyfMBfn-HJss-wVVTf0K5y-cxCTXL8&m=h7eY105YwBdd1cBwW79HiOwMaHGLKd6Ir5Bzi2wBityeE2Xmz-hl5ZHLMSLowNfq&s=Cy9Y202bSvTBue1bsjlKvY2eZH64kUAJEYdUkjtSEfs&e=
> > >>>>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.rfc-2Deditor.org_authors_rfc9453.html&d=DwIFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=pWMzx7FsqijEJPyfMBfn-HJss-wVVTf0K5y-cxCTXL8&m=h7eY105YwBdd1cBwW79HiOwMaHGLKd6Ir5Bzi2wBityeE2Xmz-hl5ZHLMSLowNfq&s=v7NzwyI1zUJ5a4oVqQrupZGQVtXaFGGZTRk3yfRs5IQ&e=
> > >>>>
> > >>>> Diffs highlighting the most recent updates only:
> > >>>>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.rfc-2Deditor.org_authors_rfc9453-2Dlastdiff.html&d=DwIFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=pWMzx7FsqijEJPyfMBfn-HJss-wVVTf0K5y-cxCTXL8&m=h7eY105YwBdd1cBwW79HiOwMaHGLKd6Ir5Bzi2wBityeE2Xmz-hl5ZHLMSLowNfq&s=Gk6-MhCDp3pAzYHginrKvgGvoYVCOTIOmnI8Bt_x4Kk&e=
> > >>>>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.rfc-2Deditor.org_authors_rfc9453-2Dlastrfcdiff.html&d=DwIFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=pWMzx7FsqijEJPyfMBfn-HJss-wVVTf0K5y-cxCTXL8&m=h7eY105YwBdd1cBwW79HiOwMaHGLKd6Ir5Bzi2wBityeE2Xmz-hl5ZHLMSLowNfq&s=1NWdrhehlsgON0g-HjhWC9BQXDaWwoVNR2FngxsN15Q&e=
> > >>>>
> > >>>> AUTH48 diff (highlighting changes since the document entered
> AUTH48):
> > >>>>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.rfc-2Deditor.org_authors_rfc9453-2Dauth48diff.html&d=DwIFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=pWMzx7FsqijEJPyfMBfn-HJss-wVVTf0K5y-cxCTXL8&m=h7eY105YwBdd1cBwW79HiOwMaHGLKd6Ir5Bzi2wBityeE2Xmz-hl5ZHLMSLowNfq&s=Fptx-PlxUFZ4FpzdhvtLbxzyOY5r_o1qTIFaG9TPaUc&e=
> > >>>>
> > >>>> Comprehensive diffs:
> > >>>>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.rfc-2Deditor.org_authors_rfc9453-2Ddiff.html&d=DwIFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=pWMzx7FsqijEJPyfMBfn-HJss-wVVTf0K5y-cxCTXL8&m=h7eY105YwBdd1cBwW79HiOwMaHGLKd6Ir5Bzi2wBityeE2Xmz-hl5ZHLMSLowNfq&s=_4aZM5Hf8YQWqnpmHGTGMnZGejR-0eAhoL8NzBUmFFY&e=
> > >>>>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.rfc-2Deditor.org_authors_rfc9453-2Drfcdiff.html&d=DwIFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=pWMzx7FsqijEJPyfMBfn-HJss-wVVTf0K5y-cxCTXL8&m=h7eY105YwBdd1cBwW79HiOwMaHGLKd6Ir5Bzi2wBityeE2Xmz-hl5ZHLMSLowNfq&s=KqFP7uDVI7fQ9SzHBgjURncDez_9RxYXpkqxA5v3cUQ&e=
> > >>>>
> > >>>> An alternative comprehensive diff - this version will allow you to
> view changes in the Acknowledgements more easily:
> > >>>>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.rfc-2Deditor.org_authors_rfc9453-2Dalt-2Ddiff.html&d=DwIFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=pWMzx7FsqijEJPyfMBfn-HJss-wVVTf0K5y-cxCTXL8&m=h7eY105YwBdd1cBwW79HiOwMaHGLKd6Ir5Bzi2wBityeE2Xmz-hl5ZHLMSLowNfq&s=s81EMSy63tYX2FjW72MzJzY16FGR2ZZeYZd4DfgH_0s&e=
> > >>>>
> > >>>>
> > >>>> Thank you,
> > >>>> RFC Editor/sg
> > >>>>
> > >>>>
> > >>>>
> > >>>>> On Aug 23, 2023, at 5:52 PM, Yong-Geun Hong <
> yonggeun.hong@gmail.com> wrote:
> > >>>>>
> > >>>>> Dear Sandy Ginoza.
> > >>>>>
> > >>>>> Thanks again for your efforts.
> > >>>>>
> > >>>>> I added my response in lines.
> > >>>>>
> > >>>>> Best regards.
> > >>>>>
> > >>>>> Yong-Geun.
> > >>>>>
> > >>>>>
> > >>>>> 2023년 8월 24일 (목) 오전 1:25, Sandy Ginoza <sginoza@amsl.com>님이 작성:
> > >>>>> Greetings Yong-Geun,
> > >>>>>
> > >>>>> Thank you for your review and detailed reply.  We have updated the
> document and have a few remaining questions below.  The current files are
> available here:
> > >>>>>
> > >>>>>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.rfc-2Deditor.org_authors_rfc9453.xml&d=DwIFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=pWMzx7FsqijEJPyfMBfn-HJss-wVVTf0K5y-cxCTXL8&m=h7eY105YwBdd1cBwW79HiOwMaHGLKd6Ir5Bzi2wBityeE2Xmz-hl5ZHLMSLowNfq&s=Ln9_Xwwx93738eRVlzbwjGUpVsr1IVaWKQjSb2ku5GI&e=
> > >>>>>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.rfc-2Deditor.org_authors_rfc9453.txt&d=DwIFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=pWMzx7FsqijEJPyfMBfn-HJss-wVVTf0K5y-cxCTXL8&m=h7eY105YwBdd1cBwW79HiOwMaHGLKd6Ir5Bzi2wBityeE2Xmz-hl5ZHLMSLowNfq&s=heABRT-P-Km8JMhNN4zFcGyHBsQrAyCOaR_9h8AtiC8&e=
> > >>>>>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.rfc-2Deditor.org_authors_rfc9453.pdf&d=DwIFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=pWMzx7FsqijEJPyfMBfn-HJss-wVVTf0K5y-cxCTXL8&m=h7eY105YwBdd1cBwW79HiOwMaHGLKd6Ir5Bzi2wBityeE2Xmz-hl5ZHLMSLowNfq&s=Cy9Y202bSvTBue1bsjlKvY2eZH64kUAJEYdUkjtSEfs&e=
> > >>>>>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.rfc-2Deditor.org_authors_rfc9453.html&d=DwIFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=pWMzx7FsqijEJPyfMBfn-HJss-wVVTf0K5y-cxCTXL8&m=h7eY105YwBdd1cBwW79HiOwMaHGLKd6Ir5Bzi2wBityeE2Xmz-hl5ZHLMSLowNfq&s=v7NzwyI1zUJ5a4oVqQrupZGQVtXaFGGZTRk3yfRs5IQ&e=
> > >>>>>
> > >>>>> AUTH48 diff (highlighting changes since the document entered
> AUTH48):
> > >>>>>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.rfc-2Deditor.org_authors_rfc9453-2Dauth48diff.html&d=DwIFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=pWMzx7FsqijEJPyfMBfn-HJss-wVVTf0K5y-cxCTXL8&m=h7eY105YwBdd1cBwW79HiOwMaHGLKd6Ir5Bzi2wBityeE2Xmz-hl5ZHLMSLowNfq&s=Fptx-PlxUFZ4FpzdhvtLbxzyOY5r_o1qTIFaG9TPaUc&e=
> > >>>>>
> > >>>>> Comprehensive diffs:
> > >>>>>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.rfc-2Deditor.org_authors_rfc9453-2Ddiff.html&d=DwIFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=pWMzx7FsqijEJPyfMBfn-HJss-wVVTf0K5y-cxCTXL8&m=h7eY105YwBdd1cBwW79HiOwMaHGLKd6Ir5Bzi2wBityeE2Xmz-hl5ZHLMSLowNfq&s=_4aZM5Hf8YQWqnpmHGTGMnZGejR-0eAhoL8NzBUmFFY&e=
> > >>>>>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.rfc-2Deditor.org_authors_rfc9453-2Drfcdiff.html&d=DwIFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=pWMzx7FsqijEJPyfMBfn-HJss-wVVTf0K5y-cxCTXL8&m=h7eY105YwBdd1cBwW79HiOwMaHGLKd6Ir5Bzi2wBityeE2Xmz-hl5ZHLMSLowNfq&s=KqFP7uDVI7fQ9SzHBgjURncDez_9RxYXpkqxA5v3cUQ&e=
> > >>>>>
> > >>>>> An alternative comprehensive diff - this version will allow you to
> view changes in the Acknowledgements more easily:
> > >>>>>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.rfc-2Deditor.org_authors_rfc9453-2Dalt-2Ddiff.html&d=DwIFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=pWMzx7FsqijEJPyfMBfn-HJss-wVVTf0K5y-cxCTXL8&m=h7eY105YwBdd1cBwW79HiOwMaHGLKd6Ir5Bzi2wBityeE2Xmz-hl5ZHLMSLowNfq&s=s81EMSy63tYX2FjW72MzJzY16FGR2ZZeYZd4DfgH_0s&e=
> > >>>>>
> > >>>>>
> > >>>>> Open items:
> > >>>>>
> > >>>>> 1) We mistakenly did not include this in our original set of
> questions.  For readability, may we update the following?
> > >>>>>
> > >>>>> Original:
> > >>>>>  A user may turn on/off or may control home
> > >>>>>  appliances by pressing a wall switch or by pressing a button in a
> > >>>>>  remote control.
> > >>>>>
> > >>>>> Perhaps:
> > >>>>>  A user may turn home appliances on and off, or the user may
> control them
> > >>>>>  by pressing a wall switch or a button on a
> > >>>>>  remote control.
> > >>>>>
> > >>>>> [Yong-Geun]  Thanks for the update. Agreed.
> > >>>>>
> > >>>>> 2) Regarding table 2, thank you for your suggested updates.
> Unfortunately, some of the hyphenation did not display as desired in all of
> the outputs (i.e., the hyphenation breaks in the text were different from
> those in the html).  Please review our updates to Table 2 and let us know
> if you have concerns with the current format and use of abbreviations
> (e.g., Tx is used for transmission; we removed the brackets from RFCs
> (seems reasonable because they are all referenced elsewhere in the
> document).
> > >>>>>
> > >>>>> [Yong-Geun]  Thanks for the update. It looks better and simpler.
> > >>>>>                    One question.  As it changed from 'Automation'
> to 'Autom.', how about changing from "Requirement" to "Req." ?
> > >>>>>
> > >>>>>
> > >>>>> Thank you,
> > >>>>> RFC Editor/sg
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>>> On Aug 18, 2023, at 11:04 PM, Yong-Geun Hong <
> yonggeun.hong@gmail.com> wrote:
> > >>>>>>
> > >>>>>> Dear RFC Editor.
> > >>>>>>
> > >>>>>> Thanks for your efforts to publish RFC 9453.
> > >>>>>>
> > >>>>>> I add my response in lines.
> > >>>>>>
> > >>>>>> Best regards.
> > >>>>>>
> > >>>>>> Yong-Geun.
> > >>>>>>
> > >>>>>>
> > >>>>>>
> > >>>>>>
> > >>>>>>> 보낸 사람: rfc-editor@rfc-editor.org
> > >>>>>>> 날짜: 2023년 8월 8일 오후 4시 31분 32초 GMT+9
> > >>>>>>> 받는 사람: yonggeun.hong@gmail.com, carles.gomez@upc.edu,
> yhc@etri.re.kr, sangi_bahrian@yahoo.com, samitac.ietf@gmail.com
> > >>>>>>> 참조: rfc-editor@rfc-editor.org, 6lo-ads@ietf.org,
> 6lo-chairs@ietf.org, shwetha.bhandari@gmail.com, ek.ietf@gmail.com,
> auth48archive@rfc-editor.org
> > >>>>>>> 제목: Re: AUTH48: RFC-to-be 9453 <draft-ietf-6lo-use-cases-16> for
> your review
> > >>>>>>>
> > >>>>>>> Authors,
> > >>>>>>>
> > >>>>>>> While reviewing this document during AUTH48, please resolve (as
> necessary)
> > >>>>>>> the following questions, which are also in the XML file.
> > >>>>>>>
> > >>>>>>> 1) <!-- [rfced] For readability, we would like to flip the order
> of the
> > >>>>>>> title.  In addition, to match the 6lo Working Group's wording
> (see
> > >>>>>>>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__datatracker.ietf.org_wg_6lo_charter_&d=DwIFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=pWMzx7FsqijEJPyfMBfn-HJss-wVVTf0K5y-cxCTXL8&m=h7eY105YwBdd1cBwW79HiOwMaHGLKd6Ir5Bzi2wBityeE2Xmz-hl5ZHLMSLowNfq&s=ZlVblK4mbWHGlvItug5JY10s030pW5rUzP2dEo5BfGY&e=
> ), should the title be updated
> > >>>>>>> as follows?  Please review.
> > >>>>>>>
> > >>>>>>> Note that this update would also affect terminology in the
> abstract.
> > >>>>>>>
> > >>>>>>> Original:
> > >>>>>>> IPv6 over Constrained Node Networks (6lo) Applicability & Use
> cases
> > >>>>>>>
> > >>>>>>> Perhaps:
> > >>>>>>> Applicability and Use Cases for IPv6 over Networks of
> Resource-constrained Nodes (6lo)
> > >>>>>>> -->
> > >>>>>> [Yong-Geun] Agreed.
> > >>>>>>>
> > >>>>>>>
> > >>>>>>>
> > >>>>>>> 2) <!-- [rfced] Please insert any keywords (beyond those that
> appear in the
> > >>>>>>> title) for use on
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.rfc-2Deditor.org_search&d=DwIFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=pWMzx7FsqijEJPyfMBfn-HJss-wVVTf0K5y-cxCTXL8&m=h7eY105YwBdd1cBwW79HiOwMaHGLKd6Ir5Bzi2wBityeE2Xmz-hl5ZHLMSLowNfq&s=mMStdqWRlVMDsR3OFJ202YmJ321wv2jsPyMKVH4ecC8&e=
> .
> > >>>>>>> -->
> > >>>>>> [Yong-Geun]  It seems that the updated title is enough.
> > >>>>>>>
> > >>>>>>>
> > >>>>>>>
> > >>>>>>> 3) <!-- [rfced] Should this list of design space dimensions be
> capitalized
> > >>>>>>> as they are in Appendix A, or may we lowecase the dimensions in
> Appendix A?
> > >>>>>>> In addition, we note that Security Level does not appear in the
> list in
> > >>>>>>> Appendix A; should it be added to match the list in section 1?
> > >>>>>>>
> > >>>>>>> Original:
> > >>>>>>> In addition, it considers various network design space
> > >>>>>>> dimensions such as deployment, network size, power source,
> > >>>>>>> connectivity, multi-hop communication, traffic pattern, security
> > >>>>>>> level, mobility, and QoS requirements (see Appendix A).
> > >>>>>>>
> > >>>>>>> Original from Appendix A:
> > >>>>>>> In [RFC6568], the following design space dimensions are
> described:
> > >>>>>>> Deployment, Network size, Power source, Connectivity, Multi-hop
> > >>>>>>> communication, Traffic pattern, Mobility, Quality of Service
> (QoS).
> > >>>>>>> -->
> > >>>>>> [Yong-Geun]  Agree to modify the list of design space dimensions
> to be capitalized in Appendix A.
> > >>>>>>                    I propose to delete “Security Level”.
> > >>>>>>>
> > >>>>>>>
> > >>>>>>>
> > >>>>>>> 4) <!-- [rfced] May we expand SIG as Special Interest Group?
> > >>>>>>>
> > >>>>>>> Original:
> > >>>>>>> The Bluetooth
> > >>>>>>> SIG has also published the Internet Protocol Support Profile
> (IPSP).
> > >>>>>>>
> > >>>>>>> Perhaps (which matches what appears in RFC 9159):
> > >>>>>>> The Bluetooth Special Interest Group (Bluetooth SIG) has also
> published
> > >>>>>>> the Internet Protocol Support Profile (IPSP).
> > >>>>>>> -->
> > >>>>>> [Yong-Geun] Agreed.
> > >>>>>>>
> > >>>>>>>
> > >>>>>>>
> > >>>>>>> 5) <!-- [rfced] Did you intend to include references for ISO/IEC
> 14443 A&B
> > >>>>>>> and JIS-X 6319-4?  If yes, please provide us with the reference
> information
> > >>>>>>> or pointers to the reference information.
> > >>>>>>>
> > >>>>>>> Original:
> > >>>>>>> NFC complements many popular consumer-level wireless
> > >>>>>>> technologies, by utilizing the key elements in existing
> standards for
> > >>>>>>> contactless card technology (ISO/IEC 14443 A&B and JIS-X 6319-4).
> > >>>>>>> -->
> > >>>>>> [Yong-Geun] The reference for ISO/IEC 14443 A&B and JIS-X 6319-4
> is not necessary in this draft. So proposed the expression of ISO/IEC 14443
> A&B and JIS-X 6319-4
> > >>>>>>
> > >>>>>> --> Proposal:
> > >>>>>> NFC complements many popular consumer-level wireless
> > >>>>>> technologies, by utilizing the key elements in existing standards
> for
> > >>>>>> contactless card technology.
> > >>>>>>>
> > >>>>>>>
> > >>>>>>>
> > >>>>>>> 6) <!-- [rfced] We have the following questions related to Table
> 2.
> > >>>>>>>
> > >>>>>>> a) Table 2 exceeds the 72-character line limit by 5 characters.
> We are reviewing possible ways to trim the length of the table.  Please let
> us know if you have any suggestions.
> > >>>>>>>
> > >>>>>>> b) Please confirm that the reference to RFC 7428 is correct. We
> ask because
> > >>>>>>> we do not see mention of Z-Wave, Home Automation, L2-mesh, or
> L3-mesh.
> > >>>>>>> -->
> > >>>>>> [Yong-Geun] Make the table 2 shorter under 72-character. Please
> find the attached XML file
> > >>>>>> [Yong-Geun] The reference to RFC 7428 is correct because RFC 7428
> (Transmission of IPv6 Packets over ITU-T G.9959 Networks) is related to
> ITU-T G.9959 Networks and the ITU-T G.9959 is one of protocol for Z-wave.
> > >>>>>>>
> > >>>>>>>
> > >>>>>>>
> > >>>>>>> 7) <!-- [rfced] "IPv6 address" is seemingly redundant.  May we
> update the
> > >>>>>>> text as follows?
> > >>>>>>>
> > >>>>>>> Original:
> > >>>>>>>    For MAC-derived IPv6 addresses, please
> > >>>>>>>    refer to [RFC8163] for IPv6 address mapping examples.
> > >>>>>>>
> > >>>>>>> Perhaps:
> > >>>>>>>    For MAC-derived IPv6 addresses, refer to [RFC8163] for mapping
> > >>>>>>>    examples.
> > >>>>>>> -->
> > >>>>>> [Yong-Geun] Agreed.
> > >>>>>>>
> > >>>>>>>
> > >>>>>>>
> > >>>>>>> 8) <!-- [rfced] For clarity and ease of the reader, may we
> update the text
> > >>>>>>> as follows?
> > >>>>>>>
> > >>>>>>> Original:
> > >>>>>>>    The 6LoWPAN node should
> > >>>>>>>    also support [RFC8505] and use it as the default Neighbor
> > >>>>>>>    Discovery method.
> > >>>>>>>
> > >>>>>>> Perhaps:
> > >>>>>>>    The 6LoWPAN node should
> > >>>>>>>    also support the registration extensions defined in [RFC8505]
> and
> > >>>>>>>    use the mechanism as the default Neighbor Discovery method.
> > >>>>>>> -->
> > >>>>>> [Yong-Geun] Agreed.
> > >>>>>>>
> > >>>>>>>
> > >>>>>>>
> > >>>>>>> 9) <!-- [rfced] May we update the expansion for AP-ND to match
> what appears
> > >>>>>>> in RFC 8929, which expands it as "Address-Protected Neighbor
> Discovery"?
> > >>>>>>>
> > >>>>>>> Original:
> > >>>>>>>    Address Protection for 6LoWPAN
> > >>>>>>>    Neighbor Discovery (AP-ND) [RFC8928] enables Source Address
> > >>>>>>>    Validation [RFC6620] and protects the address ownership
> against
> > >>>>>>>    impersonation attacks.
> > >>>>>>> -->
> > >>>>>> [Yong-Geun] Agreed.
> > >>>>>>>
> > >>>>>>>
> > >>>>>>>
> > >>>>>>> 10) <!-- [rfced] Is "objective function" needed here?  It seems
> redundant
> > >>>>>>> with the expansion of MRHOF.
> > >>>>>>>
> > >>>>>>> Original:
> > >>>>>>> Note
> > >>>>>>> that the L3 routing in Netricity uses RPL in non-storing mode
> with
> > >>>>>>> the MRHOF (Minimum Rank with Hysteresis Objective Function)
> objective
> > >>>>>>> function based on their own defined Estimated Transmission Time
> (ETT)
> > >>>>>>> metric.
> > >>>>>>> -->
> > >>>>>> [Yong-Geun] Agreed and proposed to delete ‘objective function’.
> > >>>>>>>
> > >>>>>>>
> > >>>>>>>
> > >>>>>>> 11) <!-- [rfced] For readability, may we update "enjoys the
> advantage of"
> > >>>>>>> to "benefits from"? Or is there another way we may update?
> > >>>>>>>
> > >>>>>>> Original:
> > >>>>>>> Although other wired and wireless technologies are also used in
> Smart
> > >>>>>>> Grid, PLC enjoys the advantage of reliable data communication
> over
> > >>>>>>> electrical power lines that are already present, and the
> deployment
> > >>>>>>> cost can be comparable to wireless technologies.
> > >>>>>>>
> > >>>>>>> Perhaps:
> > >>>>>>> Although other wired and wireless technologies are also used in a
> > >>>>>>> smart grid, PLC benefits from reliable data
> > >>>>>>> communication over electrical power lines that are already
> present,
> > >>>>>>> and the deployment cost can be comparable to wireless
> technologies.
> > >>>>>>> -->
> > >>>>>> [Yong-Geun] Agreed.
> > >>>>>>>
> > >>>>>>>
> > >>>>>>> 12) <!-- [rfced] We have the following questions related to
> references.
> > >>>>>>>
> > >>>>>>> a) Would you like to update the reference [BACnet] reference to
> the most
> > >>>>>>> recent version from 2020?
> > >>>>>>>
> > >>>>>>> Current:
> > >>>>>>> [BACnet]  ASHRAE, "BACnet-A Data Communication Protocol for
> Building
> > >>>>>>>            Automation and Control Networks (ANSI Approved)",
> ANSI/
> > >>>>>>>            ASHRAE Standard 135-2016, January 2016,
> > >>>>>>>            <
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.techstreet.com_ashrae_standards_ashrae-2D&d=DwIFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=pWMzx7FsqijEJPyfMBfn-HJss-wVVTf0K5y-cxCTXL8&m=h7eY105YwBdd1cBwW79HiOwMaHGLKd6Ir5Bzi2wBityeE2Xmz-hl5ZHLMSLowNfq&s=4qpJ4iZ_Ld5chEYp4_Oiq0A9wmSSkZzskimxs6v2r_U&e=
> > >>>>>>>            135-2016?product_id=1918140#jumps>.
> > >>>>>>>
> > >>>>>> [Yong-Geun] Proposal :
> > >>>>>>              [BACnet]  ASHRAE, "BACnet-A Data Communication
> Protocol for Building
> > >>>>>>                              Automation and Control Networks
> (ANSI Approved)", ANSI/
> > >>>>>>                            ASHRAE Standard 135-2020, Ja20,
> October 2020.
> > >>>>>>                            <
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.techstreet.com_standards_ashrae-2D135-2D2020-3Fproduct-5Fid-3D2191852&d=DwIFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=pWMzx7FsqijEJPyfMBfn-HJss-wVVTf0K5y-cxCTXL8&m=h7eY105YwBdd1cBwW79HiOwMaHGLKd6Ir5Bzi2wBityeE2Xmz-hl5ZHLMSLowNfq&s=Dde1ZQDyphHtUQIFXKFHfemKE5E3FD_FckwU21P41Fs&e=
> >.
> > >>>>>>
> > >>>>>>>
> > >>>>>>> b) For the specification [BTCorev4.1], would you like to update
> to the most
> > >>>>>>> recent version 5.4? Please review and let us know how/if we may
> update.
> > >>>>>>>
> > >>>>>>> Current:
> > >>>>>>> [BTCorev4.1]
> > >>>>>>>            Bluetooth, "Core Specification Version 4.1", December
> > >>>>>>>            2013, <
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.bluetooth.com_specifications_specs_&d=DwIFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=pWMzx7FsqijEJPyfMBfn-HJss-wVVTf0K5y-cxCTXL8&m=h7eY105YwBdd1cBwW79HiOwMaHGLKd6Ir5Bzi2wBityeE2Xmz-hl5ZHLMSLowNfq&s=4yKpyqs8xPSy21hmNZiI3Zkqx7ZD1_pir6Osuh70KgI&e=
> > >>>>>>>            core-specification-4-1/>.
> > >>>>>> [Yong-Geun] Proposal:
> > >>>>>>              [BTCorev5.4]
> > >>>>>>                        Bluetooth, "Core Specification Version
> 5.4", January
> > >>>>>>                        2023, <
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.bluetooth.com_specifications_specs_core-2Dspecification-2D5-2D4_&d=DwIFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=pWMzx7FsqijEJPyfMBfn-HJss-wVVTf0K5y-cxCTXL8&m=h7eY105YwBdd1cBwW79HiOwMaHGLKd6Ir5Bzi2wBityeE2Xmz-hl5ZHLMSLowNfq&s=tAZl2qJFEwEY9IxzmaRt0aQW8KDD3ZNVuDjAD6Q4imk&e=
> >.
> > >>>>>>>
> > >>>>>>>
> > >>>>>>>
> > >>>>>>> c) The URL provided for [IPSP] directs to a page titled
> "Specifications and Documents", but there is no document named "Bluetooth
> Internet Protocol Support Profile Specification Version 1.0.0".  We are
> unable to locate a document with this title.  Please let us know how this
> entry should be updated.
> > >>>>>>>
> > >>>>>>>
> > >>>>>>> Original:
> > >>>>>>> [IPSP]    Bluetooth Special Interest Group, "Bluetooth Internet
> > >>>>>>>            Protocol Support Profile Specification Version 1.0.0",
> > >>>>>>>            December 2014, <
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.bluetooth.org_en-2D&d=DwIFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=pWMzx7FsqijEJPyfMBfn-HJss-wVVTf0K5y-cxCTXL8&m=h7eY105YwBdd1cBwW79HiOwMaHGLKd6Ir5Bzi2wBityeE2Xmz-hl5ZHLMSLowNfq&s=iV397RFbfxlcNv9ZoKfJ0gg9hKf_x02LY4OX4acjTdc&e=
> > >>>>>>>            us/specification/adopted-specifications>.>.
> > >>>>>>>
> > >>>>>>> perhaps the URL should be to <
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.bluetooth.com_specifications_specs_&d=DwIFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=pWMzx7FsqijEJPyfMBfn-HJss-wVVTf0K5y-cxCTXL8&m=h7eY105YwBdd1cBwW79HiOwMaHGLKd6Ir5Bzi2wBityeE2Xmz-hl5ZHLMSLowNfq&s=4yKpyqs8xPSy21hmNZiI3Zkqx7ZD1_pir6Osuh70KgI&e=
> > or
> > >>>>>>> <
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.bluetooth.com_specifications_specs_internet-2Dprotocol-2Dsupport-2Dprofile-2D1-2D0_&d=DwIFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=pWMzx7FsqijEJPyfMBfn-HJss-wVVTf0K5y-cxCTXL8&m=h7eY105YwBdd1cBwW79HiOwMaHGLKd6Ir5Bzi2wBityeE2Xmz-hl5ZHLMSLowNfq&s=GxNvUELUjeYimaRgWaC_CBz-fK5u76_O-p44t04JxLo&e=
> >?
> > >>>>>>>
> > >>>>>> [Yong-Geun] Proposal:
> > >>>>>>
> > >>>>>>              [IPSP]    Bluetooth Special Interest Group,
> "Bluetooth Internet
> > >>>>>>                          Protocol Support Profile Specification
> Version 1.0.0",
> > >>>>>>                        December 2014, <
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.bluetooth.com_specifications_specs_internet-2Dprotocol-2Dsupport-2Dprofile-2D1-2D0_&d=DwIFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=pWMzx7FsqijEJPyfMBfn-HJss-wVVTf0K5y-cxCTXL8&m=h7eY105YwBdd1cBwW79HiOwMaHGLKd6Ir5Bzi2wBityeE2Xmz-hl5ZHLMSLowNfq&s=GxNvUELUjeYimaRgWaC_CBz-fK5u76_O-p44t04JxLo&e=
> >.
> > >>>>>>>
> > >>>>>>> d) Would you like to update the provided URL for [LLCP-1.4] to
> the
> > >>>>>>> following to lead directly to the document?
> > >>>>>>>
> > >>>>>>> Original:
> > >>>>>>> [LLCP-1.4] NFC Forum, "NFC Logical Link Control Protocol, Version
> > >>>>>>>            1.4", NFC Forum Technical Specification , January
> 2021,
> > >>>>>>>            <
> https://urldefense.proofpoint.com/v2/url?u=https-3A__nfc-2Dforum.org_build_specifications&d=DwIFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=pWMzx7FsqijEJPyfMBfn-HJss-wVVTf0K5y-cxCTXL8&m=h7eY105YwBdd1cBwW79HiOwMaHGLKd6Ir5Bzi2wBityeE2Xmz-hl5ZHLMSLowNfq&s=xeRrYCUDDowJV0N5P9_JTIkZVwApyykSmfUkC02mADA&e=
> >.
> > >>>>>>>
> > >>>>>>> Perhaps:
> > >>>>>>> [LLCP-1.4] NFC Forum, "Logical Link Control Protocol Technical
> > >>>>>>>            Specification", Version 1.4, December 2022,
> > >>>>>>>        <
> https://urldefense.proofpoint.com/v2/url?u=https-3A__nfc-2Dforum.org_build_specifications_logical-2D&d=DwIFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=pWMzx7FsqijEJPyfMBfn-HJss-wVVTf0K5y-cxCTXL8&m=h7eY105YwBdd1cBwW79HiOwMaHGLKd6Ir5Bzi2wBityeE2Xmz-hl5ZHLMSLowNfq&s=Q2T3TybYrAFr6aZ9h3_246qxi8yQyfPdMxmOWHLrUfY&e=
> > >>>>>>>        link-control-protocol-technical-specification/>.
> > >>>>>>> -->
> > >>>>>> [Yong-Geun] Agreed.
> > >>>>>>>
> > >>>>>>>
> > >>>>>>>
> > >>>>>>> 13) <!-- [rfced] Please note that we have updated this sentence
> as follows.
> > >>>>>>> Please review and let us know if any corrections are needed.
> > >>>>>>>
> > >>>>>>> Original:
> > >>>>>>> *  Buffering requirements: Some 6lo use case may require higher
> data
> > >>>>>>>    rate than the link layer technology support.
> > >>>>>>>
> > >>>>>>> Current:
> > >>>>>>> Buffering Requirements:
> > >>>>>>>    Some 6lo use cases may require a higher data rate than the
> link-
> > >>>>>>>    layer technology supports.
> > >>>>>>> -->
> > >>>>>> [Yong-Geun] Agreed.
> > >>>>>>>
> > >>>>>>>
> > >>>>>>>
> > >>>>>>> 14) <!-- [rfced] We have the following terminology-related
> questions.
> > >>>>>>>
> > >>>>>>> a) We have updated the document to use "link-layer" (with a
> hyphen) where
> > >>>>>>> the terms are acting as an adjective appearing before the noun.
> > >>>>>>>
> > >>>>>>> Similarly, we have updated "constrained node" to
> "constrained-node" (with a
> > >>>>>>> hyphen).
> > >>>>>>>
> > >>>>>>> Please review and let us know if you have any concerns.
> > >>>>>> [Yong-Geun] Thanks for the update. Agreed.
> > >>>>>>>
> > >>>>>>>
> > >>>>>>> b) Throughout the text, the following acronyms are missing
> expansions.
> > >>>>>>> Please review and let us know if/how we may update. We provided
> possible
> > >>>>>>> expansions the right.
> > >>>>>>>
> > >>>>>>> GPRS - General Packet Radio Service or Ground Penetrating Radar
> Systems
> > >>>>>>> ISM - Industrial, Scientific, and Medical
> > >>>>>>> LV PLC networks - Low-Voltage PLC networks
> > >>>>>>>
> > >>>>>>> Do instances of Low, Medium, and High Voltage need to be
> capitalized?
> > >>>>>> [Yong-Geun] Proposal:
> > >>>>>>          GPRS - General Packet Radio Service
> > >>>>>>          ISM - Industrial, Scientific, and Medical
> > >>>>>>          LV PLC networks - Low-Voltage PLC networks
> > >>>>>>>
> > >>>>>>>
> > >>>>>>> c) FYI, for clarity, we added the following expansions to the
> provided
> > >>>>>>> acronyms. Please let us know of any objections.
> > >>>>>>>
> > >>>>>>> FDMA - Frequency-Division Multiplex
> > >>>>>>> TDMA - Time-Division Multiple Access
> > >>>>>>> TDD - Time-Division Duplex
> > >>>>>>> -->
> > >>>>>> [Yong-Geun] Thanks for the update. Agreed.
> > >>>>>>>
> > >>>>>>>
> > >>>>>>>
> > >>>>>>> 15) <!-- [rfced] Some author comments are present in the XML.
> Please
> > >>>>>>> confirm that no updates related to these comments are
> outstanding. Note
> > >>>>>>> that the comments will be deleted prior to publication.
> > >>>>>>> -->
> > >>>>>> [Yong-Geun] There are no updates related to these comments. It is
> appreciated to delete the comments.
> > >>>>>>>
> > >>>>>>>
> > >>>>>>>
> > >>>>>>> 16) <!-- [rfced] Please review the "Inclusive Language" portion
> of the
> > >>>>>>> online Style Guide <
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.rfc-2Deditor.org_styleguide_part2_-23inclusive-5Flanguage&d=DwIFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=pWMzx7FsqijEJPyfMBfn-HJss-wVVTf0K5y-cxCTXL8&m=h7eY105YwBdd1cBwW79HiOwMaHGLKd6Ir5Bzi2wBityeE2Xmz-hl5ZHLMSLowNfq&s=WW0KP86iB0ioOvr8zLodZ-VsUZXy1Ksya64XDxi9DKI&e=
> >
> > >>>>>>> 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.
> > >>>>>>>
> > >>>>>>>
> > >>>>>>> In addition, some guides suggest avoiding "senior citizen" and
> recommend
> > >>>>>>> replacements such as "older adults" or "persons 65 years and
> older" (see
> > >>>>>>> information about "Age" in
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.apa.org_about_apa_equity-2Ddiversity-2Dinclusion_language-2Dguidelines-3F-5Fgl-3D1-2Aw1b56-2A-5Fga-2AMTg0ODg5NzI0My4xNjkxNDc0OTI5-2A-5Fga-5FSZXLGDJGNB-2AMTY5MTQ3NDkyOS4xLjAuMTY5MTQ3NDkzNy4wLjAuMA..-26-5Fga-3D2.202736337.1920239215.1691474929-2D1848897243.1691474929&d=DwIFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=pWMzx7FsqijEJPyfMBfn-HJss-wVVTf0K5y-cxCTXL8&m=h7eY105YwBdd1cBwW79HiOwMaHGLKd6Ir5Bzi2wBityeE2Xmz-hl5ZHLMSLowNfq&s=Ey3h6yeEDbnytDJ_T30xuRHIE2hrZEPMD9d1fblAc2k&e=
> ).
> > >>>>>>> -->
> > >>>>>> [Yong-Geun]  I prefer the expression of ‘older adults” rather
> than ‘senior citizen’
> > >>>>>>>
> > >>>>>>>
> > >>>>>>>
> > >>>>>>> Thank you.
> > >>>>>>>
> > >>>>>>> RFC Editor
> > >>>>>>>
> > >>>>>>>
> > >>>>>>> On Aug 8, 2023, at 12:20 AM, rfc-editor@rfc-editor.org wrote:
> > >>>>>>>
> > >>>>>>> *****IMPORTANT*****
> > >>>>>>>
> > >>>>>>> Updated 2023/08/08
> > >>>>>>>
> > >>>>>>> RFC Author(s):
> > >>>>>>> --------------
> > >>>>>>>
> > >>>>>>> Instructions for Completing AUTH48
> > >>>>>>>
> > >>>>>>> Your document has now entered AUTH48.  Once it has been reviewed
> and
> > >>>>>>> approved by you and all coauthors, it will be published as an
> RFC.
> > >>>>>>> If an author is no longer available, there are several remedies
> > >>>>>>> available as listed in the FAQ (
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.rfc-2Deditor.org_faq_&d=DwIFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=pWMzx7FsqijEJPyfMBfn-HJss-wVVTf0K5y-cxCTXL8&m=h7eY105YwBdd1cBwW79HiOwMaHGLKd6Ir5Bzi2wBityeE2Xmz-hl5ZHLMSLowNfq&s=rsd9nnL_i8yincbHnZnMliOxKe70894OKkfK7phbxo8&e=
> ).
> > >>>>>>>
> > >>>>>>> You and you coauthors are responsible for engaging other parties
> > >>>>>>> (e.g., Contributors or Working Group) as necessary before
> providing
> > >>>>>>> your approval.
> > >>>>>>>
> > >>>>>>> Planning your review
> > >>>>>>> ---------------------
> > >>>>>>>
> > >>>>>>> Please review the following aspects of your document:
> > >>>>>>>
> > >>>>>>> *  RFC Editor questions
> > >>>>>>>
> > >>>>>>> Please review and resolve any questions raised by the RFC Editor
> > >>>>>>> that have been included in the XML file as comments marked as
> > >>>>>>> follows:
> > >>>>>>>
> > >>>>>>> <!-- [rfced] ... -->
> > >>>>>>>
> > >>>>>>> These questions will also be sent in a subsequent email.
> > >>>>>>>
> > >>>>>>> *  Changes submitted by coauthors
> > >>>>>>>
> > >>>>>>> Please ensure that you review any changes submitted by your
> > >>>>>>> coauthors.  We assume that if you do not speak up that you
> > >>>>>>> agree to changes submitted by your coauthors.
> > >>>>>>>
> > >>>>>>> *  Content
> > >>>>>>>
> > >>>>>>> Please review the full content of the document, as this cannot
> > >>>>>>> change once the RFC is published.  Please pay particular
> attention to:
> > >>>>>>> - IANA considerations updates (if applicable)
> > >>>>>>> - contact information
> > >>>>>>> - references
> > >>>>>>>
> > >>>>>>> *  Copyright notices and legends
> > >>>>>>>
> > >>>>>>> Please review the copyright notice and legends as defined in
> > >>>>>>> RFC 5378 and the Trust Legal Provisions
> > >>>>>>> (TLP –
> https://urldefense.proofpoint.com/v2/url?u=https-3A__trustee.ietf.org_license-2Dinfo_&d=DwIFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=pWMzx7FsqijEJPyfMBfn-HJss-wVVTf0K5y-cxCTXL8&m=h7eY105YwBdd1cBwW79HiOwMaHGLKd6Ir5Bzi2wBityeE2Xmz-hl5ZHLMSLowNfq&s=LTTt8xInK9cKGWJxa1s5NwgtuN3nx4rXyd1CXFB-GUg&e=
> ).
> > >>>>>>>
> > >>>>>>> *  Semantic markup
> > >>>>>>>
> > >>>>>>> Please review the markup in the XML file to ensure that elements
> of
> > >>>>>>> content are correctly tagged.  For example, ensure that
> <sourcecode>
> > >>>>>>> and <artwork> are set correctly.  See details at
> > >>>>>>> <
> https://urldefense.proofpoint.com/v2/url?u=https-3A__authors.ietf.org_rfcxml-2Dvocabulary&d=DwIFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=pWMzx7FsqijEJPyfMBfn-HJss-wVVTf0K5y-cxCTXL8&m=h7eY105YwBdd1cBwW79HiOwMaHGLKd6Ir5Bzi2wBityeE2Xmz-hl5ZHLMSLowNfq&s=Mbw5zSdK2eQ6UOsGHBn8jsORyhyJa_wgxraXc8d-vLM&e=
> >.
> > >>>>>>>
> > >>>>>>> *  Formatted output
> > >>>>>>>
> > >>>>>>> Please review the PDF, HTML, and TXT files to ensure that the
> > >>>>>>> formatted output, as generated from the markup in the XML file,
> is
> > >>>>>>> reasonable.  Please note that the TXT will have formatting
> > >>>>>>> limitations compared to the PDF and HTML.
> > >>>>>>>
> > >>>>>>>
> > >>>>>>> Submitting changes
> > >>>>>>> ------------------
> > >>>>>>>
> > >>>>>>> To submit changes, please reply to this email using ‘REPLY ALL’
> as all
> > >>>>>>> the parties CCed on this message need to see your changes. The
> parties
> > >>>>>>> include:
> > >>>>>>>
> > >>>>>>> *  your coauthors
> > >>>>>>>
> > >>>>>>> *  rfc-editor@rfc-editor.org (the RPC team)
> > >>>>>>>
> > >>>>>>> *  other document participants, depending on the stream (e.g.,
> > >>>>>>>    IETF Stream participants are your working group chairs, the
> > >>>>>>>    responsible ADs, and the document shepherd).
> > >>>>>>>
> > >>>>>>> *  auth48archive@rfc-editor.org, which is a new archival
> mailing list
> > >>>>>>>    to preserve AUTH48 conversations; it is not an active
> discussion
> > >>>>>>>    list:
> > >>>>>>>
> > >>>>>>>  *  More info:
> > >>>>>>>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__mailarchive.ietf.org_arch_msg_ietf-2Dannounce_yb6lpIGh-2D4Q9l2USxIAe6P8O4Zc&d=DwIFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=pWMzx7FsqijEJPyfMBfn-HJss-wVVTf0K5y-cxCTXL8&m=h7eY105YwBdd1cBwW79HiOwMaHGLKd6Ir5Bzi2wBityeE2Xmz-hl5ZHLMSLowNfq&s=WVSUdPF79Km5cttVPwij09M9VWOsP-NKN6--xe0sg3Q&e=
> > >>>>>>>
> > >>>>>>>  *  The archive itself:
> > >>>>>>>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__mailarchive.ietf.org_arch_browse_auth48archive_&d=DwIFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=pWMzx7FsqijEJPyfMBfn-HJss-wVVTf0K5y-cxCTXL8&m=h7eY105YwBdd1cBwW79HiOwMaHGLKd6Ir5Bzi2wBityeE2Xmz-hl5ZHLMSLowNfq&s=Ot4WKkPtS1XRYDxSEh52ukVsJgKT2Vz2ixjFT0qSC_o&e=
> > >>>>>>>
> > >>>>>>>  *  Note: If only absolutely necessary, you may temporarily opt
> out
> > >>>>>>>      of the archiving of messages (e.g., to discuss a sensitive
> matter).
> > >>>>>>>      If needed, please add a note at the top of the message that
> you
> > >>>>>>>      have dropped the address. When the discussion is concluded,
> > >>>>>>>      auth48archive@rfc-editor.org will be re-added to the CC
> list and
> > >>>>>>>      its addition will be noted at the top of the message.
> > >>>>>>>
> > >>>>>>> You may submit your changes in one of two ways:
> > >>>>>>>
> > >>>>>>> An update to the provided XML file
> > >>>>>>> — OR —
> > >>>>>>> An explicit list of changes in this format
> > >>>>>>>
> > >>>>>>> Section # (or indicate Global)
> > >>>>>>>
> > >>>>>>> OLD:
> > >>>>>>> old text
> > >>>>>>>
> > >>>>>>> NEW:
> > >>>>>>> new text
> > >>>>>>>
> > >>>>>>> You do not need to reply with both an updated XML file and an
> explicit
> > >>>>>>> list of changes, as either form is sufficient.
> > >>>>>>>
> > >>>>>>> We will ask a stream manager to review and approve any changes
> that seem
> > >>>>>>> beyond editorial in nature, e.g., addition of new text, deletion
> of text,
> > >>>>>>> and technical changes.  Information about stream managers can be
> found in
> > >>>>>>> the FAQ.  Editorial changes do not require approval from a
> stream manager.
> > >>>>>>>
> > >>>>>>>
> > >>>>>>> Approving for publication
> > >>>>>>> --------------------------
> > >>>>>>>
> > >>>>>>> To approve your RFC for publication, please reply to this email
> stating
> > >>>>>>> that you approve this RFC for publication.  Please use ‘REPLY
> ALL’,
> > >>>>>>> as all the parties CCed on this message need to see your
> approval.
> > >>>>>>>
> > >>>>>>>
> > >>>>>>> Files
> > >>>>>>> -----
> > >>>>>>>
> > >>>>>>> The files are available here:
> > >>>>>>>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.rfc-2Deditor.org_authors_rfc9453.xml&d=DwIFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=pWMzx7FsqijEJPyfMBfn-HJss-wVVTf0K5y-cxCTXL8&m=h7eY105YwBdd1cBwW79HiOwMaHGLKd6Ir5Bzi2wBityeE2Xmz-hl5ZHLMSLowNfq&s=Ln9_Xwwx93738eRVlzbwjGUpVsr1IVaWKQjSb2ku5GI&e=
> > >>>>>>>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.rfc-2Deditor.org_authors_rfc9453.html&d=DwIFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=pWMzx7FsqijEJPyfMBfn-HJss-wVVTf0K5y-cxCTXL8&m=h7eY105YwBdd1cBwW79HiOwMaHGLKd6Ir5Bzi2wBityeE2Xmz-hl5ZHLMSLowNfq&s=v7NzwyI1zUJ5a4oVqQrupZGQVtXaFGGZTRk3yfRs5IQ&e=
> > >>>>>>>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.rfc-2Deditor.org_authors_rfc9453.pdf&d=DwIFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=pWMzx7FsqijEJPyfMBfn-HJss-wVVTf0K5y-cxCTXL8&m=h7eY105YwBdd1cBwW79HiOwMaHGLKd6Ir5Bzi2wBityeE2Xmz-hl5ZHLMSLowNfq&s=Cy9Y202bSvTBue1bsjlKvY2eZH64kUAJEYdUkjtSEfs&e=
> > >>>>>>>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.rfc-2Deditor.org_authors_rfc9453.txt&d=DwIFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=pWMzx7FsqijEJPyfMBfn-HJss-wVVTf0K5y-cxCTXL8&m=h7eY105YwBdd1cBwW79HiOwMaHGLKd6Ir5Bzi2wBityeE2Xmz-hl5ZHLMSLowNfq&s=heABRT-P-Km8JMhNN4zFcGyHBsQrAyCOaR_9h8AtiC8&e=
> > >>>>>>>
> > >>>>>>> Diff file of the text:
> > >>>>>>>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.rfc-2Deditor.org_authors_rfc9453-2Ddiff.html&d=DwIFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=pWMzx7FsqijEJPyfMBfn-HJss-wVVTf0K5y-cxCTXL8&m=h7eY105YwBdd1cBwW79HiOwMaHGLKd6Ir5Bzi2wBityeE2Xmz-hl5ZHLMSLowNfq&s=_4aZM5Hf8YQWqnpmHGTGMnZGejR-0eAhoL8NzBUmFFY&e=
> > >>>>>>>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.rfc-2Deditor.org_authors_rfc9453-2Drfcdiff.html&d=DwIFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=pWMzx7FsqijEJPyfMBfn-HJss-wVVTf0K5y-cxCTXL8&m=h7eY105YwBdd1cBwW79HiOwMaHGLKd6Ir5Bzi2wBityeE2Xmz-hl5ZHLMSLowNfq&s=KqFP7uDVI7fQ9SzHBgjURncDez_9RxYXpkqxA5v3cUQ&e=
> (side by side)
> > >>>>>>>
> > >>>>>>> Diff of the XML:
> > >>>>>>>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.rfc-2Deditor.org_authors_rfc9453-2Dxmldiff1.html&d=DwIFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=pWMzx7FsqijEJPyfMBfn-HJss-wVVTf0K5y-cxCTXL8&m=h7eY105YwBdd1cBwW79HiOwMaHGLKd6Ir5Bzi2wBityeE2Xmz-hl5ZHLMSLowNfq&s=e41trGDTsIp04J3UO-gFRXuvMTYEARShjeNUyEYX-78&e=
> > >>>>>>>
> > >>>>>>> The following files are provided to facilitate creation of your
> own
> > >>>>>>> diff files of the XML.
> > >>>>>>>
> > >>>>>>> Initial XMLv3 created using XMLv2 as input:
> > >>>>>>>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.rfc-2Deditor.org_authors_rfc9453.original.v2v3.xml&d=DwIFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=pWMzx7FsqijEJPyfMBfn-HJss-wVVTf0K5y-cxCTXL8&m=h7eY105YwBdd1cBwW79HiOwMaHGLKd6Ir5Bzi2wBityeE2Xmz-hl5ZHLMSLowNfq&s=30O-4tuJyLf8nwsedTlcJQuTwIoaML5u1SzSPcW0N-I&e=
> > >>>>>>>
> > >>>>>>> XMLv3 file that is a best effort to capture v3-related format
> updates
> > >>>>>>> only:
> > >>>>>>>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.rfc-2Deditor.org_authors_rfc9453.form.xml&d=DwIFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=pWMzx7FsqijEJPyfMBfn-HJss-wVVTf0K5y-cxCTXL8&m=h7eY105YwBdd1cBwW79HiOwMaHGLKd6Ir5Bzi2wBityeE2Xmz-hl5ZHLMSLowNfq&s=YiwcK5DRmWlTapISB8Cbd8IYwhwrCnS8m5GZiQH4QZw&e=
> > >>>>>>>
> > >>>>>>>
> > >>>>>>> Tracking progress
> > >>>>>>> -----------------
> > >>>>>>>
> > >>>>>>> The details of the AUTH48 status of your document are here:
> > >>>>>>>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.rfc-2Deditor.org_auth48_rfc9453&d=DwIFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=pWMzx7FsqijEJPyfMBfn-HJss-wVVTf0K5y-cxCTXL8&m=h7eY105YwBdd1cBwW79HiOwMaHGLKd6Ir5Bzi2wBityeE2Xmz-hl5ZHLMSLowNfq&s=7MYfVC9otpNCIXilfJJpjKhNuFifhP7pkrYOHMe1SHQ&e=
> > >>>>>>>
> > >>>>>>> Please let us know if you have any questions.
> > >>>>>>>
> > >>>>>>> Thank you for your cooperation,
> > >>>>>>>
> > >>>>>>> RFC Editor
> > >>>>>>>
> > >>>>>>> --------------------------------------
> > >>>>>>> RFC9453 (draft-ietf-6lo-use-cases-16)
> > >>>>>>>
> > >>>>>>> Title            : IPv6 over Constrained Node Networks (6lo)
> Applicability & Use cases
> > >>>>>>> Author(s)        : Y. Hong, C. Gomez, Y. Choi, A. Sangi, S.
> Chakrabarti
> > >>>>>>> WG Chair(s)      : Shwetha Bhandari, Carles Gomez
> > >>>>>>>
> > >>>>>>> Area Director(s) : Erik Kline, Éric Vyncke
> > >>>>>>>
> > >>>>>>>
> > >>>>>>>
> > >>>>>> <draft-ietf-6lo-use-cases-16_Table2.xml>
> > >>>>>
> > >>>>
> > >>>
> > >>
> > >
> >
>
>