Re: [auth48] [Albert Cabellos] AUTH48: RFC-to-be 9437 <draft-ietf-lisp-pubsub-15> for your review

[Sandy Ginoza <[e-mail]>]

Hi Albert,

Thank you for your reply.  We have noted your approval on the AUTH48 page and will continue with the publication process shortly.

Thank you,
RFC Editor/sg


> On Aug 2, 2023, at 12:17 AM, Albert Cabellos <[e-mail]> wrote:
> 
> Hi 
> 
> Sorry for the late reply. I replied on the wrong thread.
> 
> Looks good for me.
> 
> Albert
> 
> On Tue, 1Aug 2023 at 20:56, Sandy Ginoza <[e-mail]> wrote:
> Hi Albert,
> 
> We do not believe we have heard from you regarding this document’s readiness for publication.  Please review the document and let us know if any updates are needed or if you approve the RFC for publication.
> 
> The current files are available here:
> https://www.rfc-editor.org/authors/rfc9437.xml
> https://www.rfc-editor.org/authors/rfc9437.txt
> https://www.rfc-editor.org/authors/rfc9437.pdf
> https://www.rfc-editor.org/authors/rfc9437.html
> 
> AUTH48 diff: 
> https://www.rfc-editor.org/authors/rfc9437-auth48diff.html
> 
> Comprehensive diffs: 
> https://www.rfc-editor.org/authors/rfc9437-diff.html
> https://www.rfc-editor.org/authors/rfc9437-rfcdiff.html
> 
> Thank you,
> RFC Editor/sg
> 
> 
> 
> 
> > On Jul 21, 2023, at 9:30 AM, Sandy Ginoza <[e-mail]> wrote:
> > 
> > Hi Vina,
> > 
> > Thank you for your reply.  We have noted your approval on the AUTH48 page <https://www.rfc-editor.org/auth48/rfc9437>.
> > 
> > We will continue once we have received approval from Albert Cabellos as well.
> > 
> > Thanks,
> > RFC Editor/sg
> > 
> >> On Jul 20, 2023, at 9:51 AM, Vina Ermagan <[e-mail]> wrote:
> >> 
> >> Hi All,
> >> 
> >> Looks good from my end.
> >> 
> >> Thanks,
> >> 
> >> On Thu, Jul 20, 2023 at 9:37 AM Sandy Ginoza <[e-mail]> wrote:
> >> Hi Sharon,
> >> 
> >> Thank you for your reply.  We have noted your approval on the AUTH48 page <https://www.rfc-editor.org/auth48/rfc9437>. 
> >> 
> >> We will wait to hear from Albert and Vina before continuing with the publication process.
> >> 
> >> Thank you,
> >> RFC Editor/sg
> >> 
> >>> On Jul 20, 2023, at 4:50 AM, Sharon Barkai <[e-mail]> wrote:
> >>> 
> >>> Looks good my end.
> >>> 
> >>> --szb
> >>> Cell: +972.53.2470068
> >>> WhatsApp: [phone]
> >>> 
> >>>> On Jul 20, 2023, at 01:24, Sandy Ginoza <[e-mail]> wrote:
> >>>> 
> >>>> Hi Med, Alberto,
> >>>> 
> >>>> Med, thanks for catching the missing hyphens - my mistake! 
> >>>> 
> >>>> Alberto, thank you for your review; we have noted your approval on the AUTH48 page. 
> >>>> 
> >>>> The document has been updated and the revised files are available here:
> >>>> https://www.rfc-editor.org/authors/rfc9437.xml
> >>>> https://www.rfc-editor.org/authors/rfc9437.txt
> >>>> https://www.rfc-editor.org/authors/rfc9437.pdf
> >>>> https://www.rfc-editor.org/authors/rfc9437.html
> >>>> 
> >>>> Diff of most recent updates only: 
> >>>> https://www.rfc-editor.org/authors/rfc9437-lastdiff.html
> >>>> https://www.rfc-editor.org/authors/rfc9437-lastrfcdiff.html
> >>>> 
> >>>> AUTH48 diff: 
> >>>> https://www.rfc-editor.org/authors/rfc9437-auth48diff.html
> >>>> 
> >>>> Comprehensive diffs: 
> >>>> https://www.rfc-editor.org/authors/rfc9437-diff.html
> >>>> https://www.rfc-editor.org/authors/rfc9437-rfcdiff.html
> >>>> 
> >>>> We will wait to hear from your coauthors before continuing with the publication process.
> >>>> 
> >>>> Thank you,
> >>>> RFC Editor/sg
> >>>> 
> >>>> 
> >>>> 
> >>>>> On Jul 17, 2023, at 12:16 AM, [e-mail] wrote:
> >>>>> 
> >>>>> Hi Sandy, 
> >>>>> 
> >>>>> Thank you.
> >>>>> 
> >>>>> When checking the latest diff, I see that you unreverted some changes in the para starting with "If the Map-Server receives ..." in Section 5. Please replace "less specific" and "more specific" with "less-specific" and "more-specific" respectively. This is to be consistent with other parts of the document and also RFC9301. Thanks.
> >>>>> 
> >>>>> Cheers,
> >>>>> Med
> >>>>> 
> >>>>>> -----Message d'origine-----
> >>>>>> De : Sandy Ginoza <[e-mail]>
> >>>>>> Envoyé : jeudi 13 juillet 2023 18:45
> >>>>>> À : BOUCADAIR Mohamed INNOV/NET <[e-mail]>
> >>>>>> Cc : RFC Editor <[e-mail]>; [e-mail];
> >>>>>> [e-mail]; [e-mail];
> >>>>>> [e-mail]; [e-mail]; lisp-
> >>>>>> [e-mail]; [e-mail]; Alvaro Retana
> >>>>>> <[e-mail]>; [e-mail]
> >>>>>> Objet : Re: AUTH48: RFC-to-be 9437 <draft-ietf-lisp-pubsub-15> for
> >>>>>> your review
> >>>>>> 
> >>>>>> Hi Med,
> >>>>>> 
> >>>>>> We have updated the document and noted your approval on the AUTH48
> >>>>>> page
> >>>>>> <https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2
> >>>>>> Fwww.rfc-
> >>>>>> editor.org%2Fauth48%2Frfc9437&data=05%7C01%7Cmohamed.boucadair%40o
> >>>>>> range.com%7Cb5b8c0ccc3bd41f7354908db83c0a18c%7C90c7a20af34b40bfbc4
> >>>>>> 8b9253b6f5d20%7C0%7C0%7C638248635581399489%7CUnknown%7CTWFpbGZsb3d
> >>>>>> 8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3
> >>>>>> D%7C3000%7C%7C%7C&sdata=NDtBaLsE7bRLqXMhh%2FMg%2FOQ9et1HJFGr9jS%2F
> >>>>>> QMlAd1g%3D&reserved=0>.  The RFC will be published once we have
> >>>>>> received approval from your coauthors as well.
> >>>>>> 
> >>>>>> Thank you for your review.
> >>>>>> RFC Editor/sg
> >>>>>> 
> >>>>>>>> On Jul 13, 2023, at 7:12 AM, [e-mail] wrote:
> >>>>>>>> 
> >>>>>>>> Hi Sandy, all,
> >>>>>>>> 
> >>>>>>>>> This is similar to the original wording - just "to use" has
> >>>>>> been
> >>>>>>>> deleted.  Is this accurate?
> >>>>>>> 
> >>>>>>> Yes I confirm.
> >>>>>>> 
> >>>>>>> I see that Alberto replied to (3). We could add a note that
> >>>>>> echoes the clarification provided by Alberto so that readers can
> >>>>>> easily understand why that section is also cited.
> >>>>>>> 
> >>>>>>> Assuming the pending changes are implemented, I approve the
> >>>>>> publication of the document.
> >>>>>>> 
> >>>>>>> Thank you for all your effort.
> >>>>>>> 
> >>>>>>> Cheers,
> >>>>>>> Med
> >>>>>>> 
> >>>>>>>> -----Message d'origine-----
> >>>>>>>> De : Sandy Ginoza <[e-mail]>
> >>>>>>>> Envoyé : vendredi 7 juillet 2023 19:06 À : BOUCADAIR Mohamed
> >>>>>>>> INNOV/NET <[e-mail]> Cc : RFC Editor
> >>>>>>>> <[e-mail]>; [e-mail];
> >>>>>> [e-mail];
> >>>>>>>> [e-mail]; [e-mail]; lisp-
> >>>>>> [e-mail];
> >>>>>>>> lisp- [e-mail]; [e-mail]; Alvaro Retana
> >>>>>>>> <[e-mail]>; [e-mail] Objet :
> >>>>>> Re:
> >>>>>>>> AUTH48: RFC-to-be 9437 <draft-ietf-lisp-pubsub-15> for your
> >>>>>> review
> >>>>>>>> 
> >>>>>>>> Hi Med,
> >>>>>>>> 
> >>>>>>>> Thanks again for your reply.  We have updated the document as
> >>>>>>>> described, but are still having trouble parsing the following:
> >>>>>>>> 
> >>>>>>>>> NEW:
> >>>>>>>>> If there is no nonce that can be
> >>>>>>>>> used for the explicit subscription state at the time the
> >>>>>>>> explicit
> >>>>>>>>> subscription is configured (e.g., from a different
> >>>>>>>> subscription
> >>>>>>>>> already established with the same xTR when a single nonce is
> >>>>>>>> kept per
> >>>>>>>>> xTR-ID), then an initial nonce value MUST be configured to
> >>>>>>>> both the xTR and Map-Server.
> >>>>>>>> 
> >>>>>>>> 
> >>>>>>>> Perhaps:
> >>>>>>>>> then both the xTR and Map-Server MUST be configured with the
> >>>>>>>> initial nonce value.
> >>>>>>>> 
> >>>>>>>> 
> >>>>>>>> 
> >>>>>>>> This is similar to the original wording - just "to use" has
> >>>>>> been
> >>>>>>>> deleted.  Is this accurate?
> >>>>>>>> 
> >>>>>>> 
> >>>>> 
> >>>>> ____________________________________________________________________________________________________________
> >>>>> 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.
> >>>>> 
> >>>> 
> >>> 
> >> 
> > 
>