Re: [auth48] AUTH48: RFC-to-be 9314 <draft-ietf-bfd-rfc9127-bis-04> for your review

[Mahesh Jethanandani <[e-mail]>]

Adding Vero’s email address that I have.

Mahesh Jethanandani
[e-mail]

> On Sep 10, 2022, at 8:19 AM, Rahman <[e-mail]> wrote:
> 
> Apologies for the delay. All good with me. Thanks Mahesh.
> 
> Vero’s Huawei email is not valid anymore afaik.
> Greg i believe you have a recent email address for Vero?
> 
> Regards,
> Reshad.
> 
> Sent from my iPhone
> 
>> On Sep 7, 2022, at 7:20 PM, Alanna Paloma <[e-mail]> wrote:
>> 
>> Hi Reshad, Lianshu, and Santosh,
>> 
>> This is a friendly reminder that we await your approvals of this document. We will wait to hear from you before continuing with the publication process.
>> 
>> The files have been posted here (please refresh):
>> https://www.rfc-editor.org/authors/rfc9314.xml
>> https://www.rfc-editor.org/authors/rfc9314.txt
>> https://www.rfc-editor.org/authors/rfc9314.html
>> https://www.rfc-editor.org/authors/rfc9314.pdf
>> 
>> The relevant diff files have been posted here:
>> https://www.rfc-editor.org/authors/rfc9314-diff.html (comprehensive diff)
>> https://www.rfc-editor.org/authors/rfc9314-auth48diff.html (AUTH48 changes)
>> 
>> The AUTH48 status page for this document is located here:
>> https://www.rfc-editor.org/auth48/rfc9314
>> 
>> Thank you,
>> RFC Editor/ap
>> 
>>>> On Aug 31, 2022, at 5:23 PM, Alanna Paloma <[e-mail]> wrote:
>>> 
>>> Hi Mahesh and Greg,
>>> 
>>> Thank you for your replies.  We have updated as requested and noted your approvals on the AUTH48 status page.
>>> 
>>> The files have been posted here (please refresh):
>>> https://www.rfc-editor.org/authors/rfc9314.xml
>>> https://www.rfc-editor.org/authors/rfc9314.txt
>>> https://www.rfc-editor.org/authors/rfc9314.html
>>> https://www.rfc-editor.org/authors/rfc9314.pdf
>>> 
>>> The relevant diff files have been posted here:
>>> https://www.rfc-editor.org/authors/rfc9314-diff.html (comprehensive diff)
>>> https://www.rfc-editor.org/authors/rfc9314-auth48diff.html (AUTH48 changes)
>>> 
>>> We will await approvals from the remaining parties listed on the AUTH48 status page below prior to moving this document forward in the publication process.
>>> 
>>> For the AUTH48 status of this document, please see:
>>> https://www.rfc-editor.org/auth48/rfc9314
>>> 
>>> Thank you,
>>> RFC Editor/ap
>>> 
>>>>> On Aug 30, 2022, at 12:31 PM, Greg Mirsky <[e-mail]> wrote:
>>>> 
>>>> Dear RFC Editor,
>>>> I don't have any updates to the clarifications shared by Mahesh (thank you, Mahesh).
>>>> I've reviewed the proposed updates and approved them all. Please let me know if there are any further questions and/or actions I need to take.
>>>> 
>>>> Regards,
>>>> Greg
>>>> 
>>>>> On Tue, Aug 30, 2022 at 11:10 AM Mahesh Jethanandani <[e-mail]> wrote:
>>>> Hi RFC Editor,
>>>> 
>>>> I have reviewed the .txt diffs, the IANA Considerations, contact information for the authors, and I approve of the changes.
>>>> 
>>>> I have also responded separately to the questions raised by you.
>>>> 
>>>> Thanks.
>>>> 
>>>>> On Aug 29, 2022, at 7:41 PM, [e-mail] wrote:
>>>>> 
>>>>> *****IMPORTANT*****
>>>>> 
>>>>> Updated 2022/08/29
>>>>> 
>>>>> 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://www.rfc-editor.org/faq/).
>>>>> 
>>>>> 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 – https://trustee.ietf.org/license-info/).
>>>>> 
>>>>> *  Semantic markup
>>>>> 
>>>>> Please review the markup in the XML file to ensure that elements of  
>>>>> content are correctly tagged.  For example, ensure that <sourcecode> 
>>>>> and <artwork> are set correctly.  See details at
>>>>> <https://authors.ietf.org/rfcxml-vocabulary>.
>>>>> 
>>>>> *  Formatted output
>>>>> 
>>>>> Please review the PDF, HTML, and TXT files to ensure that the 
>>>>> formatted output, as generated from the markup in the XML file, is 
>>>>> reasonable.  Please note that the TXT will have formatting 
>>>>> limitations compared to the PDF and HTML.
>>>>> 
>>>>> 
>>>>> Submitting changes
>>>>> ------------------
>>>>> 
>>>>> To submit changes, please reply to this email using ‘REPLY ALL’ as all 
>>>>> the parties CCed on this message need to see your changes. The parties 
>>>>> include:
>>>>> 
>>>>> *  your coauthors
>>>>> 
>>>>> *  [e-mail] (the RPC team)
>>>>> 
>>>>> *  other document participants, depending on the stream (e.g., 
>>>>>   IETF Stream participants are your working group chairs, the 
>>>>>   responsible ADs, and the document shepherd).
>>>>> 
>>>>> *  [e-mail], which is a new archival mailing list 
>>>>>   to preserve AUTH48 conversations; it is not an active discussion 
>>>>>   list:
>>>>> 
>>>>>  *  More info:
>>>>>     https://mailarchive.ietf.org/arch/msg/ietf-announce/yb6lpIGh-4Q9l2USxIAe6P8O4Zc
>>>>> 
>>>>>  *  The archive itself:
>>>>>     https://mailarchive.ietf.org/arch/browse/auth48archive/
>>>>> 
>>>>>  *  Note: If only absolutely necessary, you may temporarily opt out 
>>>>>     of the archiving of messages (e.g., to discuss a sensitive matter).
>>>>>     If needed, please add a note at the top of the message that you 
>>>>>     have dropped the address. When the discussion is concluded, 
>>>>>     [e-mail] will be re-added to the CC list and 
>>>>>     its addition will be noted at the top of the message. 
>>>>> 
>>>>> You may submit your changes in one of two ways:
>>>>> 
>>>>> An update to the provided XML file
>>>>> — OR —
>>>>> An explicit list of changes in this format
>>>>> 
>>>>> Section # (or indicate Global)
>>>>> 
>>>>> OLD:
>>>>> old text
>>>>> 
>>>>> NEW:
>>>>> new text
>>>>> 
>>>>> You do not need to reply with both an updated XML file and an explicit 
>>>>> list of changes, as either form is sufficient.
>>>>> 
>>>>> We will ask a stream manager to review and approve any changes that seem
>>>>> beyond editorial in nature, e.g., addition of new text, deletion of text, 
>>>>> and technical changes.  Information about stream managers can be found in 
>>>>> the FAQ.  Editorial changes do not require approval from a stream manager.
>>>>> 
>>>>> 
>>>>> Approving for publication
>>>>> --------------------------
>>>>> 
>>>>> To approve your RFC for publication, please reply to this email stating
>>>>> that you approve this RFC for publication.  Please use ‘REPLY ALL’,
>>>>> as all the parties CCed on this message need to see your approval.
>>>>> 
>>>>> 
>>>>> Files 
>>>>> -----
>>>>> 
>>>>> The files are available here:
>>>>> https://www.rfc-editor.org/authors/rfc9314.xml
>>>>> https://www.rfc-editor.org/authors/rfc9314.html
>>>>> https://www.rfc-editor.org/authors/rfc9314.pdf
>>>>> https://www.rfc-editor.org/authors/rfc9314.txt
>>>>> 
>>>>> Diff file of the text:
>>>>> https://www.rfc-editor.org/authors/rfc9314-diff.html
>>>>> https://www.rfc-editor.org/authors/rfc9314-rfcdiff.html (side by side)
>>>>> 
>>>>> Diff of the XML: 
>>>>> https://www.rfc-editor.org/authors/rfc9314-xmldiff1.html
>>>>> 
>>>>> 
>>>>> Tracking progress
>>>>> -----------------
>>>>> 
>>>>> The details of the AUTH48 status of your document are here:
>>>>> https://www.rfc-editor.org/auth48/rfc9314
>>>>> 
>>>>> Please let us know if you have any questions.  
>>>>> 
>>>>> Thank you for your cooperation,
>>>>> 
>>>>> RFC Editor
>>>>> 
>>>>> --------------------------------------
>>>>> RFC 9314 (draft-ietf-bfd-rfc9127-bis-04)
>>>>> 
>>>>> Title            : YANG Data Model for Bidirectional Forwarding Detection (BFD)
>>>>> Author(s)        : M. Jethanandani, Ed., R. Rahman, Ed., L. Zheng, Ed., S. Pallagatti, G. Mirsky
>>>>> WG Chair(s)      : Jeffrey Haas, Reshad Rahman
>>>>> Area Director(s) : Alvaro Retana, John Scudder, Andrew Alston
>>>>> 
>>>>> 
>>>> 
>>>> 
>>>> Mahesh Jethanandani
>>>> [e-mail]
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>> 
>> 
>