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

["Alberto Rodriguez-Natal (natal)" <[e-mail]>]

Hi all,

Thanks Med for taking a look at this. I'm currently on vacation. I'll try to take a look at this over the weekend.

Thanks
Alberto
________________________________
From: Luigi Iannone <[e-mail]>
Sent: Monday, July 3, 2023 1:50 PM
To: [e-mail] <[e-mail]>
Cc: [e-mail] <[e-mail]>; Alberto Rodriguez-Natal (natal) <[e-mail]>; [e-mail] <[e-mail]>; [e-mail] <[e-mail]>; [e-mail] <[e-mail]>; [e-mail] <[e-mail]>; [e-mail] <[e-mail]>; [e-mail] <[e-mail]>; [e-mail] <[e-mail]>
Subject: Re: AUTH48: RFC-to-be 9437 <draft-ietf-lisp-pubsub-15> for your review

Hi,

@All co-authors (except Med)

Just a reminder that if you do not reply to the RFC Editor in a reasonable time it is assumed that you agree with the proposed changes.

Reasonable time == 2 Weeks

You have until next week to reply. ;-)

Thanks

Ciao

L.


> On 29 Jun 2023, at 16:33, [e-mail] wrote:
>
> Dear RFC Editor, all,
>
> Thank you for sharing this edited version.
>
> Please find below some few comments on this version:
>
> * Abstract: I would simply delete "that is based on request/reply" from the abstract.
>
> * Section 3:
>
> OLD: this document defines the following deployment requirements
> NEW: this document imposes the following deployment requirements
>
> * Section 5:
>
> (1) I suggest to revert to the original text:
>
> Current: because the xTR was not successful in establishing a
> NEW: because the xTR tried but was not successful in establishing a
>
> (2) I suggest to also revert to the original text as that was consistent with RFC9301 (same in Section 6)
>
> CURRENT: "less specific" and "more specific"
> NEW: "less-specific" and "more-specific"
>
> Thank you.
>
> Cheers,
> Med
>
>> -----Message d'origine-----
>> De : [e-mail] <[e-mail]>
>> Envoyé : mardi 27 juin 2023 07:50
>> À : [e-mail]; [e-mail]; [e-mail];
>> [e-mail]; BOUCADAIR Mohamed INNOV/NET
>> <[e-mail]>
>> Cc : [e-mail]; [e-mail]; lisp-
>> [e-mail]; [e-mail]; [e-mail];
>> [e-mail]
>> Objet : AUTH48: RFC-to-be 9437 <draft-ietf-lisp-pubsub-15> for
>> your review
>>
>> *****IMPORTANT*****
>>
>> Updated 2023/06/26
>>
>> 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://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2
>> Fwww.rfc-
>> editor.org%2Ffaq%2F&data=05%7C01%7Cmohamed.boucadair%40orange.com%
>> 7C16f3131a4ec94de0448908db76d293d3%7C90c7a20af34b40bfbc48b9253b6f5
>> d20%7C0%7C0%7C638234419018278526%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiM
>> C4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7
>> C%7C%7C&sdata=6qszr4DCTql1jxAnldTYzVdClBsVE4JwfwrDAHx3cz8%3D&reser
>> ved=0).
>>
>> 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 -
>
> ____________________________________________________________________________________________________________
> 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.
>