Re: [auth48] AUTH48: RFC-to-be 9543 <draft-ietf-teas-ietf-network-slices-25> for your review
Sarah Tarrant <starrant@amsl.com> Wed, 28 February 2024 22:06 UTC
Return-Path: <starrant@amsl.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 5F77BC14F61E; Wed, 28 Feb 2024 14:06:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.208
X-Spam-Level:
X-Spam-Status: No, score=-4.208 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
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 KHluT8xkTYDa; Wed, 28 Feb 2024 14:06:24 -0800 (PST)
Received: from c8a.amsl.com (c8a.amsl.com [4.31.198.40]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5B817C14F60A; Wed, 28 Feb 2024 14:06:24 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 3A556424B455; Wed, 28 Feb 2024 14:06:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vUQ3nelP_gBG; Wed, 28 Feb 2024 14:06:24 -0800 (PST)
Received: from smtpclient.apple (unknown [IPv6:2600:1700:8f1d:4000:5da8:5000:cfbf:38ff]) by c8a.amsl.com (Postfix) with ESMTPSA id 4F335424B432; Wed, 28 Feb 2024 14:06:23 -0800 (PST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.200.91.1.1\))
From: Sarah Tarrant <starrant@amsl.com>
In-Reply-To: <SJ0PR04MB8391AA1D6010ABCB28053C5DCD582@SJ0PR04MB8391.namprd04.prod.outlook.com>
Date: Wed, 28 Feb 2024 16:06:12 -0600
Cc: John Drake <je_drake@yahoo.com>, Jeff Tantsura <jefftant.ietf@gmail.com>, Shunsuke Homma <shunsuke.homma.ietf@gmail.com>, kiranm@futurewei.com, RFC Editor <rfc-editor@rfc-editor.org>, luismiguel.contrerasmurillo@telefonica.com, teas-ads@ietf.org, teas-chairs@ietf.org, Vishnu Pavan Beeram <vbeeram@juniper.net>, auth48archive@rfc-editor.org, Adrian Farrel <adrian@olddog.co.uk>, John Scudder <jgs@juniper.net>
Content-Transfer-Encoding: quoted-printable
Message-Id: <8A118D27-3A2A-41BF-B6DD-1ED2D0F84046@amsl.com>
References: <103AD0BE-4348-403D-96EC-105E8CF80ACE@amsl.com> <EB9804FC-2E57-4E8C-8EF4-D1BB391BBDC2@gmail.com> <SJ0PR04MB83910E9F024A020699AF470ACD582@SJ0PR04MB8391.namprd04.prod.outlook.com> <3947C869-7633-4DA6-8140-B2823DCBECF0@amsl.com> <SJ0PR04MB8391AA1D6010ABCB28053C5DCD582@SJ0PR04MB8391.namprd04.prod.outlook.com>
To: "Rokui, Reza" <rrokui@ciena.com>
X-Mailer: Apple Mail (2.3774.200.91.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/auth48archive/1oruR3qIkwVYxx0ktfp-kTIsxSo>
Subject: Re: [auth48] AUTH48: RFC-to-be 9543 <draft-ietf-teas-ietf-network-slices-25> 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, 28 Feb 2024 22:06:29 -0000
Hi Reza, My apologies! I see we have your name formatted correctly in the document, so just my last email was incorrect. Sincerely, RFC Editor/st > On Feb 28, 2024, at 3:12 PM, Rokui, Reza <rrokui@ciena.com> wrote: > > Just a minor comment. My first name is Reza. > > Reza > > Sent from my iPhone > From: Sarah Tarrant <starrant@amsl.com> > Sent: Wednesday, February 28, 2024 9:31:40 PM > To: Rokui, Reza <rrokui@ciena.com>; John Drake <je_drake@yahoo.com>; Jeff Tantsura <jefftant.ietf@gmail.com> > Cc: Shunsuke Homma <shunsuke.homma.ietf@gmail.com>; John Scudder <jgs@juniper.net>; RFC Editor <rfc-editor@rfc-editor.org>; kiranm@futurewei.com <kiranm@futurewei.com>; luismiguel.contrerasmurillo@telefonica.com <luismiguel.contrerasmurillo@telefonica.com>; teas-ads@ietf.org <teas-ads@ietf.org>; teas-chairs@ietf.org <teas-chairs@ietf.org>; Vishnu Pavan Beeram <vbeeram@juniper.net>; auth48archive@rfc-editor.org <auth48archive@rfc-editor.org>; Adrian Farrel <adrian@olddog.co.uk> > Subject: [**EXTERNAL**] Re: AUTH48: RFC-to-be 9543 <draft-ietf-teas-ietf-network-slices-25> for your review Hi Jeff, John, and Rokui, > > Thank you for your replies. We have noted your approvals on the AUTH48 status page for this document (https://urldefense.com/v3/__http://www.rfc-editor.org/auth48/rfc9543__;!!OSsGDw!Ip6N4KVJLS5mqChC8a4m70UktRN4Gd6EEjQDpKKFEqfolu2Qrj9KYaHnC39_HuWufgiX302G5wnm$ [rfc-editor[.]org]). We will await approvals from each author prior to moving forward in the publication process. > > John - We are still looking in to why you didn’t receive certain emails. > > Sincerely, > RFC Editor/st > > > > On Feb 28, 2024, at 9:12 AM, Rokui, Reza <rrokui@ciena.com> wrote: > > > > Hi Sarah, > > After incorporation of all changes, I also approve the publication of this publication. > > Cheers, > > Reza > > From: Jeff Tantsura <jefftant.ietf@gmail.com> > > Date: Wednesday, February 28, 2024 at 2:47 AM > > To: Sarah Tarrant <starrant@amsl.com> > > Cc: John Drake <je_drake@yahoo.com>, Shunsuke Homma <shunsuke.homma.ietf@gmail.com>, John Scudder <jgs@juniper.net>, RFC Editor <rfc-editor@rfc-editor.org>, Rokui, Reza <rrokui@ciena.com>, kiranm@futurewei.com<kiranm@futurewei.com>, luismiguel.contrerasmurillo@telefonica.com<luismiguel.contrerasmurillo@telefonica.com>, teas-ads@ietf.org <teas-ads@ietf.org>, teas-chairs@ietf.org <teas-chairs@ietf.org>, Vishnu Pavan Beeram <vbeeram@juniper.net>, auth48archive@rfc-editor.org <auth48archive@rfc-editor.org>, Adrian Farrel <adrian@olddog.co.uk> > > Subject: [**EXTERNAL**] Re: AUTH48: RFC-to-be 9543 <draft-ietf-teas-ietf-network-slices-25> for your review > > Hi Sarah, > > > > With the changes incorporated, I approve the publication. > > > > Thanks! > > > > Cheers, > > Jeff > > > > > On Feb 27, 2024, at 09:12, Sarah Tarrant <starrant@amsl.com> wrote: > > > > > > Hi John, > > > > > > Apologies! We did forward you the emails you requested yesterday, but since it appears you did not receive that email or any of the others, we’re looking into what could have happened. > > > > > > In the meantime, we suggest that you take a look at the AUTH48 archive thread at:https://urldefense.com/v3/__https://mailarchive.ietf.org/arch/msg/auth48archive/NWzDf_uFjUM4VAIcN_LwSnhjeTI/__;!!OSsGDw!Pu2uAZ3rKa4i8vkkvyay6uTMbNl1CRkLX18t_KhnKu62O1pfGn6HIGXfmYbmsnA9sUURcZ0wB9gmbWMgjGY$ [mailarchive[.]ietf[.]org] > > > > > > You can view the emails there and also let us know if you missed any additional emails. That would help us as we look into this issue. > > > > > > Additionally, the updated files have been posted here (please refresh): > > > https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9543.txt__;!!OSsGDw!Pu2uAZ3rKa4i8vkkvyay6uTMbNl1CRkLX18t_KhnKu62O1pfGn6HIGXfmYbmsnA9sUURcZ0wB9gm9OVfWPA$ [rfc-editor[.]org] > > > https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9543.pdf__;!!OSsGDw!Pu2uAZ3rKa4i8vkkvyay6uTMbNl1CRkLX18t_KhnKu62O1pfGn6HIGXfmYbmsnA9sUURcZ0wB9gmErcV738$ [rfc-editor[.]org] > > > https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9543.html__;!!OSsGDw!Pu2uAZ3rKa4i8vkkvyay6uTMbNl1CRkLX18t_KhnKu62O1pfGn6HIGXfmYbmsnA9sUURcZ0wB9gmZxPtZlo$ [rfc-editor[.]org] > > > https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9543.xml__;!!OSsGDw!Pu2uAZ3rKa4i8vkkvyay6uTMbNl1CRkLX18t_KhnKu62O1pfGn6HIGXfmYbmsnA9sUURcZ0wB9gm63rKWEk$ [rfc-editor[.]org] > > > > > > The relevant diff files have been posted here (please refresh): > > > https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9543-diff.html__;!!OSsGDw!Pu2uAZ3rKa4i8vkkvyay6uTMbNl1CRkLX18t_KhnKu62O1pfGn6HIGXfmYbmsnA9sUURcZ0wB9gm4iN9we4$ [rfc-editor[.]org] (comprehensive diff) > > > https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9543-auth48diff.html__;!!OSsGDw!Pu2uAZ3rKa4i8vkkvyay6uTMbNl1CRkLX18t_KhnKu62O1pfGn6HIGXfmYbmsnA9sUURcZ0wB9gm-UV1BIY$ [rfc-editor[.]org] (AUTH48 changes only) > > > > > > Note that it may be necessary for you to refresh your browser to view the most recent version. > > > > > > For the AUTH48 status of this document, please see: > > > https://urldefense.com/v3/__https://www.rfc-editor.org/auth48/rfc9543__;!!OSsGDw!Pu2uAZ3rKa4i8vkkvyay6uTMbNl1CRkLX18t_KhnKu62O1pfGn6HIGXfmYbmsnA9sUURcZ0wB9gmmq5MIms$ [rfc-editor[.]org] > > > > > > Thank you, > > > RFC Editor/st > > > > > >> On Feb 27, 2024, at 10:11 AM, John Drake <je_drake@yahoo.com> wrote: > > >> > > >> Sarah, > > >> > > >> Did you miss my email,below? > > >> > > >> Thanks, > > >> > > >> John > > >> > > >> ----- Forwarded Message ----- > > >> From: John Drake <je_drake@yahoo.com> > > >> To: Sarah Tarrant <starrant@amsl.com>; Shunsuke Homma <shunsuke.homma.ietf@gmail.com> > > >> Cc: Adrian Farrel <adrian@olddog.co.uk> > > >> Sent: Saturday, February 24, 2024 at 07:16:37 AM PST > > >> Subject: Re: [*AD] AUTH48: RFC-to-be 9543 <draft-ietf-teas-ietf-network-slices-25> for your review > > >> > > >> Sarah, > > >> > > >> I didn't receive either your original email or Adrian's reply. > > >> > > >> Thanks, > > >> > > >> John > > >> > > >> On Friday, February 23, 2024 at 06:42:33 PM PST, Shunsuke Homma <shunsuke.homma.ietf@gmail.com> wrote: > > >> > > >> > > >> Hi Sarah, > > >> > > >> Thank you very much for your work. > > >> > > >> All updates work for me. Also, as far as I read the latest 3GPP documents(i.e., TS23.501 v18.4.0 and TS28.530 v18.0.0), I didn't find any issues with quoting them. > > >> > > >> Therefore, I approve the document. > > >> > > >> Best regards, > > >> > > >> Shunsuke > > >> > > >> On Sat, Feb 24, 2024 at 7:52 AM Sarah Tarrant <starrant@amsl.com> wrote: > > >> Hi Adrian, > > >> > > >> Thank you for your reply. We have updated the document accordingly and noted your approval on the AUTH48 status page for this document (https://urldefense.com/v3/__http://www.rfc-editor.org/auth48/rfc9543__;!!OSsGDw!Pu2uAZ3rKa4i8vkkvyay6uTMbNl1CRkLX18t_KhnKu62O1pfGn6HIGXfmYbmsnA9sUURcZ0wB9gm-8TZKC4$ [rfc-editor[.]org]). > > >> > > >> As for you inquiry about semaphore artists, we’ve yet to receive any feedback from them or anyone else regarding the use of “to flag” in our documentation. Should that change, we may review our current inclusive language procedures in the future. > > >> > > >> Sincerely, > > >> RFC Editor/st > > >> > > >>>> On Feb 23, 2024, at 12:22 PM, Adrian Farrel <adrian@olddog.co.uk> wrote: > > >>> > > >>> Hi Sarah, > > >>> > > >>> With consideration of the comments below, I approve the document. Thanks so much for the work. > > >>> > > >>> [snip] > > >>> > > >>>> We have a few followup questions/comments. > > >>>> > > >>>> A) FYI - Regarding: > > >>>> 15) <!-- [rfced] May we update the text starting with "a robust..." as follows? > > >>>> > > >>>> Current: > > >>>> Furthermore, both the > > >>>> IETF Network Slice Service Interface and the Network Configuration > > >>>> Interface need to be secured with a robust authentication and > > >>>> authorization; and associated auditing mechanism. > > >>>> > > >>>> Perhaps: > > >>>> Furthermore, both the > > >>>> IETF Network Slice Service Interface and the Network Configuration > > >>>> Interface need to be secured with a robust authentication and > > >>>> authorizations mechanism and an associated auditing mechanism. > > >>>> --> > > >>>> > > >>>> Hmmm, > > >>>> New... > > >>>> Furthermore, both the > > >>>> IETF Network Slice Service Interface and the Network Configuration > > >>>> Interface need to be secured with robust authentication and > > >>>> authorization mechanisms, and with an associated auditing mechanism. > > >>>> > > >>>> Shunsuke updated to: > > >>>> Furthermore, both the > > >>>> IETF Network Slice Service Interface and the Network Configuration > > >>>> Interface need to be secured with a robust authentication and > > >>>> authorization mechanism and associated auditing mechanism. > > >>>> > > >>>> We updated to: > > >>>> Furthermore, both the > > >>>> IETF Network Slice Service Interface and the Network Configuration > > >>>> Interface need to be secured with a robust authentication and > > >>>> authorization mechanism and with associated auditing mechanism. > > >>>> > > >>>> Please let us know if there are any objections. > > >>> > > >>> wfm > > >>> > > >>>> B) Regarding: > > >>>> 16) <!-- [rfced] Please review whether this "Note:" should be in the <aside> > > >>>> element. It is defined as "a container for content that is semantically > > >>>> less important or tangential to the content that surrounds it" > > >>>> (https://urldefense.com/v3/__https://authors.ietf.org/en/rfcxml-vocabulary*aside__;Iw!!OSsGDw!Pu2uAZ3rKa4i8vkkvyay6uTMbNl1CRkLX18t_KhnKu62O1pfGn6HIGXfmYbmsnA9sUURcZ0wB9gmuGNoqG4$ [authors[.]ietf[.]org]). > > >>>> > > >>>> Current: > > >>>> Note: See [NGMN_SEC] on 5G network slice security for discussion > > >>>> relevant to this section. > > >>>> --> > > >>>> > > >>>> Sure, I am still reading the XML2RFC v3 manual :-) > > >>>> > > >>>> Shunsuke updated by removing “Note,” entirely, which resolved our questions. Is this update agreeable? > > >>> > > >>> wfm > > >>> > > >>>> C) Regarding: > > >>>> > > >>>> > > >>>> 18) <!-- [rfced] New versions are available for the following 3GPP > > >>>> references. Would you like to cite the latest version, or would do you > > >>>> prefer the current? > > >>>> > > >>>> a) Latest version is 18.4.0 with date of 2023: > > >>>> https://urldefense.com/v3/__https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=3144__;!!OSsGDw!Pu2uAZ3rKa4i8vkkvyay6uTMbNl1CRkLX18t_KhnKu62O1pfGn6HIGXfmYbmsnA9sUURcZ0wB9gm4-ZM-us$ [portal[.]3gpp[.]org] > > >>>> > > >>>> Original: > > >>>> [TS23501] 3GPP, "System architecture for the 5G System (5GS)", 3GPP > > >>>> TS 23.501, 2019. > > >>>> > > >>>> Perhaps: > > >>>> [TS23.501] 3GPP, "System architecture for the 5G System (5GS)", 3GPP > > >>>> TS 23.501, 2023. > > >>>> > > >>>> b) Latest version is 18.0.0 with date of 2024: > > >>>> https://urldefense.com/v3/__https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=3273__;!!OSsGDw!Pu2uAZ3rKa4i8vkkvyay6uTMbNl1CRkLX18t_KhnKu62O1pfGn6HIGXfmYbmsnA9sUURcZ0wB9gmO70kGds$ [portal[.]3gpp[.]org] > > >>>> > > >>>> Original: > > >>>> [TS28530] 3GPP, "Management and orchestration; Concepts, use cases > > >>>> and requirements", 3GPP TS 28.530, 2019. > > >>>> > > >>>> Perhaps: > > >>>> [TS28.530] 3GPP, "Management and orchestration; Concepts, use cases > > >>>> and requirements", 3GPP TS 28.530, 2024. > > >>>> --> > > >>>> > > >>>> Take the latest in both cases > > >>>> > > >>>> If updating to the latest versions/dates does not affect the content referenced > > >>>> by the RFC, we can update to the latest at the time of publication. Otherwise, > > >>>> please let us know which versions we should update to if referencing older > > >>>> versions/dates, as there are a few versions available for the provided years. > > >>>> > > >>>> Original: > > >>>> [TS23501] 3GPP, "System architecture for the 5G System (5GS)", 3GPP > > >>>> TS 23.501, 2019. > > >>>> > > >>>> Latest version & date: > > >>>> [TS23.501] 3GPP, "System architecture for the 5G System (5GS)", 3GPP > > >>>> TS 23.501, Version 18.4.0, 2023. > > >>>> > > >>>> Original: > > >>>> [TS28530] 3GPP, "Management and orchestration; Concepts, use cases > > >>>> and requirements", 3GPP TS 28.530, 2019. > > >>>> > > >>>> Latest version & date: > > >>>> [TS28.530] 3GPP, "Management and orchestration; Concepts, use cases > > >>>> and requirements", 3GPP TS 28.530, Version 18.0.0, 2024. > > >>> > > >>> Go with the versions you have shown here. (I don't want to have to *keep* checking new versions to check they are in line with our text :-) > > >>> > > >>>> D) FYI - Regarding: > > >>>> 21) <!-- [rfced] Would it be helpful to add a colon after "constructs" and move > > >>>> the open parentheses to appear before "represented"? > > >>>> > > >>>> Original: > > >>>> To achieve this, the customer may request > > >>>> an IETF Network Slice Service comprising two P2P connectivity > > >>>> constructs (CE1-CE2 and CE2-CE3 represented as *** in the figure). > > >>>> ... > > >>>> This service contains two P2P connectivity > > >>>> constructs (CE1-ACE1 and ACE1-CE3 represented as ooo in the figure). > > >>>> ... > > >>>> In this > > >>>> case, the IETF Network Slice Service request contains two P2P > > >>>> connectivity constructs (CE1-ServiceFunction and ServiceFunction-CE3 > > >>>> represented as xxx in the figure). > > >>>> > > >>>> Perhaps: > > >>>> To achieve this, the customer may request > > >>>> an IETF Network Slice Service comprising two P2P connectivity > > >>>> constructs: CE1-CE2 and CE2-CE3 (represented with "*" in > > >>>> Figure 6). > > >>>> ... > > >>>> This service contains two P2P connectivity > > >>>> constructs: CE1-ACE1 and ACE1-CE3 (represented with "o" in > > >>>> Figure 6). > > >>>> ... > > >>>> In this case, the IETF Network Slice Service request contains two P2P > > >>>> connectivity constructs: CE1-ServiceFunction and ServiceFunction-CE3 > > >>>> (represented with "x" in Figure 6). > > >>>> --> > > >>>> > > >>>> Don't mind the colon and parentheses. Slightly prefer using the multiple symbols (xxx etc.) in particular because the character 'o' has a habit of turning up in text and so causing confusion. > > >>>> > > >>>> Shunsuke updated to our suggested text, so that is how we left the update. > > >>> > > >>> OK > > >>> > > >>>> E) Regarding: > > >>>> 25) <!-- [rfced] Please review the "Inclusive Language" portion of the online > > >>>> Style Guide <https://urldefense.com/v3/__https://www.rfc-editor.org/styleguide/part2/*inclusive_language__;Iw!!OSsGDw!Pu2uAZ3rKa4i8vkkvyay6uTMbNl1CRkLX18t_KhnKu62O1pfGn6HIGXfmYbmsnA9sUURcZ0wB9gmSh_VvVc$ [rfc-editor[.]org]> > > >>>> and let us know if any changes are needed. > > >>>> > > >>>> Note that our script did not flag any words in particular, but this should > > >>>> still be reviewed as a best practice. > > >>>> > > >>>> --> > > >>>> > > >>>> Are you allowed to use 'to flag'? > > >>>> I'm pretty careful with the language these days, which is possibly why your script finds nothing. > > >>>> > > >>>> Adrian - It appears that “to flag” is not an item we search for in our inclusive language search. > > >>> > > >>> Doesn't this show inherent bias against semaphore artists? > > >>> > > >>>> The updated files have been posted here (please refresh): > > >>>> https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9543.txt__;!!OSsGDw!Pu2uAZ3rKa4i8vkkvyay6uTMbNl1CRkLX18t_KhnKu62O1pfGn6HIGXfmYbmsnA9sUURcZ0wB9gm9OVfWPA$ [rfc-editor[.]org] > > >>>> > > >>>> The relevant diff files have been posted here (please refresh): > > >>>> https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9543-diff.html__;!!OSsGDw!Pu2uAZ3rKa4i8vkkvyay6uTMbNl1CRkLX18t_KhnKu62O1pfGn6HIGXfmYbmsnA9sUURcZ0wB9gm4iN9we4$ [rfc-editor[.]org] (comprehensive diff) > > >>> > > >>> I looked at the text and the diff. > > >>> All good. > > >>> > > >>> Adrian > > >>> > > >> > > > >
- Re: [auth48] [AD]* AUTH48: RFC-to-be 9543 <draft-… John Scudder
- [auth48] AUTH48: RFC-to-be 9543 <draft-ietf-teas-… rfc-editor
- Re: [auth48] AUTH48: RFC-to-be 9543 <draft-ietf-t… Sarah Tarrant
- Re: [auth48] AUTH48: RFC-to-be 9543 <draft-ietf-t… rfc-editor
- Re: [auth48] AUTH48: RFC-to-be 9543 <draft-ietf-t… Sarah Tarrant
- Re: [auth48] AUTH48: RFC-to-be 9543 <draft-ietf-t… Shunsuke Homma
- Re: [auth48] AUTH48: RFC-to-be 9543 <draft-ietf-t… Adrian Farrel
- Re: [auth48] AUTH48: RFC-to-be 9543 <draft-ietf-t… Shunsuke Homma
- Re: [auth48] AUTH48: RFC-to-be 9543 <draft-ietf-t… Adrian Farrel
- Re: [auth48] AUTH48: RFC-to-be 9543 <draft-ietf-t… Shunsuke Homma
- [auth48] [*AD] Re: AUTH48: RFC-to-be 9543 <draft-… Sarah Tarrant
- Re: [auth48] [*AD] Re: AUTH48: RFC-to-be 9543 <dr… Adrian Farrel
- Re: [auth48] [*AD] AUTH48: RFC-to-be 9543 <draft-… Sarah Tarrant
- Re: [auth48] [*AD] AUTH48: RFC-to-be 9543 <draft-… Shunsuke Homma
- Re: [auth48] [*AD] AUTH48: RFC-to-be 9543 <draft-… Shunsuke Homma
- Re: [auth48] AUTH48: RFC-to-be 9543 <draft-ietf-t… Sarah Tarrant
- Re: [auth48] AUTH48: RFC-to-be 9543 <draft-ietf-t… Shunsuke Homma
- Re: [auth48] AUTH48: RFC-to-be 9543 <draft-ietf-t… Sarah Tarrant
- Re: [auth48] AUTH48: RFC-to-be 9543 <draft-ietf-t… Jeff Tantsura
- Re: [auth48] AUTH48: RFC-to-be 9543 <draft-ietf-t… John Drake
- Re: [auth48] [**EXTERNAL**] Re: AUTH48: RFC-to-be… Rokui, Reza
- Re: [auth48] AUTH48: RFC-to-be 9543 <draft-ietf-t… Sarah Tarrant
- Re: [auth48] AUTH48: RFC-to-be 9543 <draft-ietf-t… Sarah Tarrant
- Re: [auth48] [**EXTERNAL**] Re: AUTH48: RFC-to-be… Rokui, Reza
- [auth48] [AD]* AUTH48: RFC-to-be 9543 <draft-ietf… Sarah Tarrant
- Re: [auth48] [AD]* AUTH48: RFC-to-be 9543 <draft-… Sarah Tarrant
- Re: [auth48] [AD]* AUTH48: RFC-to-be 9543 <draft-… Adrian Farrel
- Re: [auth48] [AD]* AUTH48: RFC-to-be 9543 <draft-… John Scudder
- Re: [auth48] [**EXTERNAL**] Re: AUTH48: RFC-to-be… LUIS MIGUEL CONTRERAS MURILLO