Re: [auth48] AUTH48: RFC-to-be 9451 <draft-ietf-sfc-oam-packet-03> for your review

[Greg Mirsky <[e-mail]>]

Hi Sarah,
as I understand it, RFC-to-be-9452 is draft-ietf-sfc-ioam-nsh
<https://datatracker.ietf.org/doc/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 <[e-mail]> 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 <[e-mail]>
> > Envoyé : jeudi 3 août 2023 18:57
> > À : BOUCADAIR Mohamed INNOV/NET <[e-mail]>
> > Cc : RFC Editor <[e-mail]>; [e-mail];
> > [e-mail]; [e-mail]; andrew-
> > [e-mail]; [e-mail]
> > 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, [e-mail] 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 <[e-mail]> Envoyé : jeudi 3 août
> > 2023
> > >> 15:43 À : BOUCADAIR Mohamed INNOV/NET
> > <[e-mail]>
> > >> Cc : RFC Editor <[e-mail]>; [e-mail];
> > >> [e-mail]; [e-mail]; andrew-
> > [e-mail];
> > >> [e-mail] 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, [e-mail]
> > 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.
>
>