Re: [auth48] AUTH48: RFC-to-be 9451 <draft-ietf-sfc-oam-packet-03> for your review
Sarah Tarrant <starrant@amsl.com> Fri, 04 August 2023 18:00 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 7E1A2C15DF44; Fri, 4 Aug 2023 11:00:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.209
X-Spam-Level:
X-Spam-Status: No, score=-4.209 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] 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 rDnCtjKciUPo; Fri, 4 Aug 2023 11:00:34 -0700 (PDT)
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 8EE18C1782C3; Fri, 4 Aug 2023 11:00:34 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 6392E424B446; Fri, 4 Aug 2023 11:00:34 -0700 (PDT)
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 gmiSZiPbd60A; Fri, 4 Aug 2023 11:00:34 -0700 (PDT)
Received: from smtpclient.apple (unknown [IPv6:2600:1700:8f1d:4000:697f:20ed:44b3:b389]) by c8a.amsl.com (Postfix) with ESMTPSA id DC727424B444; Fri, 4 Aug 2023 11:00:33 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.500.231\))
From: Sarah Tarrant <starrant@amsl.com>
In-Reply-To: <CA+RyBmXWX1=uyREfN5dvLc3ciMn0E7M4c2+9urxZ5zR0dS2nTw@mail.gmail.com>
Date: Fri, 04 Aug 2023 13:00:22 -0500
Cc: RFC Editor <rfc-editor@rfc-editor.org>, "sfc-ads@ietf.org" <sfc-ads@ietf.org>, "sfc-chairs@ietf.org" <sfc-chairs@ietf.org>, "andrew-ietf@liquid.tech" <andrew-ietf@liquid.tech>, "auth48archive@rfc-editor.org" <auth48archive@rfc-editor.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <2B34BE38-543A-4FFD-9D4E-28F3FA498114@amsl.com>
References: <20230801002929.4DB34119E2@rfcpa.amsl.com> <DU2PR02MB10160B416383EFB4F418C7D05880AA@DU2PR02MB10160.eurprd02.prod.outlook.com> <09063087-C02F-40EE-9082-737F89033F0B@amsl.com> <DU2PR02MB1016006B2BAE5F10D2AD947C08808A@DU2PR02MB10160.eurprd02.prod.outlook.com> <634D9A53-DA5F-49E0-98C3-089F0ED093BC@amsl.com> <DU2PR02MB101605F8641CC2994FABEB0CC8808A@DU2PR02MB10160.eurprd02.prod.outlook.com> <CA+RyBmXWX1=uyREfN5dvLc3ciMn0E7M4c2+9urxZ5zR0dS2nTw@mail.gmail.com>
To: Greg Mirsky <gregimirsky@gmail.com>, "<mohamed.boucadair@orange.com>" <mohamed.boucadair@orange.com>
X-Mailer: Apple Mail (2.3731.500.231)
Archived-At: <https://mailarchive.ietf.org/arch/msg/auth48archive/Ehx_u8ViP6NEduWTPcdiPAhnAM8>
Subject: Re: [auth48] AUTH48: RFC-to-be 9451 <draft-ietf-sfc-oam-packet-03> 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, 04 Aug 2023 18:00:39 -0000
Hi Med and Greg, Thank you for pointing this out. We will begin to prepare the document for publication at this time. Sincerely, RFC Editor/st > On Aug 3, 2023, at 7:50 PM, Greg Mirsky <gregimirsky@gmail.com> wrote: > > Hi Sarah, > as I understand it, RFC-to-be-9452 is draft-ietf-sfc-ioam-nsh. As the Shepherd for draft-ietf-sfc-oam-packet, I don't see a good reason for holding back the publication of draft-ietf-sfc-oam-packet because of the processing of draft-ietf-sfc-ioam-nsh. > > Kind regards, > Greg > > On Thu, Aug 3, 2023 at 11:33 AM <mohamed.boucadair@orange.com> wrote: > Re-, > > > AUTH48 for this document is now complete. However, this document > > is part of cluster 479 and will be published at the same time as > > RFC-to-be 9452 (currently in AUTH48). > > Not sure to understand the rationale here especially that this document does not depend on the other I-Ds in that cluster. It is actually the other way around. > > I don't see any reason to delay the publication :-) > > Cheers, > Med > > > -----Message d'origine----- > > De : Sarah Tarrant <starrant@amsl.com> > > Envoyé : jeudi 3 août 2023 18:57 > > À : BOUCADAIR Mohamed INNOV/NET <mohamed.boucadair@orange.com> > > Cc : RFC Editor <rfc-editor@rfc-editor.org>; sfc-ads@ietf.org; > > sfc-chairs@ietf.org; gregimirsky@gmail.com; andrew- > > ietf@liquid.tech; auth48archive@rfc-editor.org > > Objet : Re: AUTH48: RFC-to-be 9451 <draft-ietf-sfc-oam-packet-03> > > for your review > > > > Hello Med, > > > > Thank you for your quick reply! We have noted your approval on the > > AUTH48 status page for this document > > (https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2F > > www.rfc- > > editor.org%2Fauth48%2Frfc9451&data=05%7C01%7Cmohamed.boucadair%40o > > range.com%7Cd0dbc7aa130b4410dde408db9442a29c%7C90c7a20af34b40bfbc4 > > 8b9253b6f5d20%7C0%7C0%7C638266786154608585%7CUnknown%7CTWFpbGZsb3d > > 8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3 > > D%7C3000%7C%7C%7C&sdata=R4kp638u2dXMNFBrpKLKdJ2yTeLhYinKnJN78Ay7BQ > > A%3D&reserved=0). > > > > AUTH48 for this document is now complete. However, this document > > is part of cluster 479 and will be published at the same time as > > RFC-to-be 9452 (currently in AUTH48). > > > > Thank you, > > > > RFC Editor/st > > > > > On Aug 3, 2023, at 8:57 AM, mohamed.boucadair@orange.com wrote: > > > > > > Hi Sarah, > > > > > > The edits look good to me. I approve the publication of this > > version. > > > > > > Thank you. > > > > > > Cheers, > > > Med > > > > > >> -----Message d'origine----- > > >> De : Sarah Tarrant <starrant@amsl.com> Envoyé : jeudi 3 août > > 2023 > > >> 15:43 À : BOUCADAIR Mohamed INNOV/NET > > <mohamed.boucadair@orange.com> > > >> Cc : RFC Editor <rfc-editor@rfc-editor.org>; sfc-ads@ietf.org; > > >> sfc-chairs@ietf.org; gregimirsky@gmail.com; andrew- > > ietf@liquid.tech; > > >> auth48archive@rfc-editor.org Objet : Re: AUTH48: RFC-to-be 9451 > > >> <draft-ietf-sfc-oam-packet-03> for your review > > >> > > >> Hello Med, > > >> > > >> Thank you for your reply. We have updated the document > > accordingly. > > >> All of our questions have now been addressed. Please let us > > know if > > >> you have further changes or if you approve the document in its > > >> current form. > > >> > > > .. > > >> Thank you, > > >> > > >> RFC Editor/st > > >> > > >>> On Aug 1, 2023, at 3:18 AM, mohamed.boucadair@orange.com > > wrote: > > >>> > > >>> Re-, > > >>> > > >>> Thank you for the edited version. > > >>> > > >>> Please find below two comments: > > >>> > > >>> * Section I: I would revert the change and expand NSH. > > >>> * Section II: > > >>> > > >>> Initial: > > >>> | NSH-encapsulated ... even if some SFC OAM data (e.g., > > >>> | record route) is also supplied in the packet. > > >>> | > > >>> | When SFC OAM data is included in the inner packet, the > > >> Next > > >>> > > >>> Edited: > > >>> > > >>> | NSH-encapsulated ...even if some SFC OAM data (e.g., > > >>> | record route) are also supplied in the packet. > > >>> | > > >>> | When SFC OAM data is included in the inner packet, the > > >> Next > > >>> > > >>> We used "SFC OAM data ..is" in these two sentences for > > >> consistency. The edited version seems to be inconsistent. > > >>> > > >>> Cheers, > > >>> Med > > >>> > > > > > > > > __________________________________________________________________ > > ____ > > > ______________________________________ > > > Ce message et ses pieces jointes peuvent contenir des > > informations > > > confidentielles ou privilegiees et ne doivent donc pas etre > > diffuses, > > > exploites ou copies sans autorisation. Si vous avez recu ce > > message > > > par erreur, veuillez le signaler a l'expediteur et le detruire > > ainsi que les pieces jointes. Les messages electroniques etant > > susceptibles d'alteration, Orange decline toute responsabilite si > > ce message a ete altere, deforme ou falsifie. Merci. > > > > > > This message and its attachments may contain confidential or > > > privileged information that may be protected by law; they should > > not be distributed, used or copied without authorisation. > > > If you have received this email in error, please notify the > > sender and delete this message and its attachments. > > > As emails may be altered, Orange is not liable for messages that > > have been modified, changed or falsified. > > > Thank you. > > > > > ____________________________________________________________________________________________________________ > Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc > pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler > a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, > Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. > > This message and its attachments may contain confidential or privileged information that may be protected by law; > they should not be distributed, used or copied without authorisation. > If you have received this email in error, please notify the sender and delete this message and its attachments. > As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. > Thank you. >
- [auth48] AUTH48: RFC-to-be 9451 <draft-ietf-sfc-o… rfc-editor
- Re: [auth48] AUTH48: RFC-to-be 9451 <draft-ietf-s… rfc-editor
- Re: [auth48] AUTH48: RFC-to-be 9451 <draft-ietf-s… mohamed.boucadair
- Re: [auth48] AUTH48: RFC-to-be 9451 <draft-ietf-s… mohamed.boucadair
- Re: [auth48] AUTH48: RFC-to-be 9451 <draft-ietf-s… Sarah Tarrant
- Re: [auth48] AUTH48: RFC-to-be 9451 <draft-ietf-s… mohamed.boucadair
- Re: [auth48] AUTH48: RFC-to-be 9451 <draft-ietf-s… Sarah Tarrant
- Re: [auth48] AUTH48: RFC-to-be 9451 <draft-ietf-s… mohamed.boucadair
- Re: [auth48] AUTH48: RFC-to-be 9451 <draft-ietf-s… Greg Mirsky
- Re: [auth48] AUTH48: RFC-to-be 9451 <draft-ietf-s… Sarah Tarrant