Re: [auth48] AUTH48: RFC-to-be 9314 <draft-ietf-bfd-rfc9127-bis-04> for your review
Alanna Paloma <apaloma@amsl.com> Mon, 12 September 2022 21:03 UTC
Return-Path: <apaloma@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 13F4AC1522A3; Mon, 12 Sep 2022 14:03:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.907
X-Spam-Level:
X-Spam-Status: No, score=-6.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham 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 jzQr9m_ei-Pu; Mon, 12 Sep 2022 14:03:18 -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 6E51AC1522B4; Mon, 12 Sep 2022 14:03:18 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 4FCD04243EF8; Mon, 12 Sep 2022 14:03:18 -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 B6vv4svd0z7o; Mon, 12 Sep 2022 14:03:18 -0700 (PDT)
Received: from amss-mbp.attlocal.net (unknown [IPv6:2600:1700:bac0:1070:591e:4641:a0a7:68a2]) by c8a.amsl.com (Postfix) with ESMTPSA id D5B36424B440; Mon, 12 Sep 2022 14:03:17 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
From: Alanna Paloma <apaloma@amsl.com>
In-Reply-To: <CACi9rdsQ2S2jDnYbUmbv=pjG+-e-uiXT99Qy_q-iAdSyH+mjTg@mail.gmail.com>
Date: Mon, 12 Sep 2022 14:03:17 -0700
Cc: Greg Mirsky <gregimirsky@gmail.com>, Mahesh Jethanandani <mjethanandani@gmail.com>, RFC Editor <rfc-editor@rfc-editor.org>, "Vero Zheng (vero.zheng@huawei.com)" <veronique_cheng@hotmail.com>, bfd-ads@ietf.org, bfd-chairs@ietf.org, Jeffrey Haas <jhaas@pfrc.org>, auth48archive@rfc-editor.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <C8FEB7E9-803D-4EA7-87E9-295003830CD3@amsl.com>
References: <20220830024146.E1BC255D49@rfcpa.amsl.com> <88D06E81-2AEC-4ABE-A934-67A3DBEC228A@gmail.com> <CA+RyBmUwxWMWN+b4QKApSEyq4Dua=WG3d9JTenpLxdwbgtL2=Q@mail.gmail.com> <F28D8CE2-52B3-4A47-8412-ABC266BE43DB@amsl.com> <CACi9rdsQ2S2jDnYbUmbv=pjG+-e-uiXT99Qy_q-iAdSyH+mjTg@mail.gmail.com>
To: Santosh P K <santosh.pallagatti@gmail.com>, Reshad Rehman <reshad@yahoo.com>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/auth48archive/DwPnfbKWgoJ2mSIhUiDKLLfhHoA>
Subject: Re: [auth48] AUTH48: RFC-to-be 9314 <draft-ietf-bfd-rfc9127-bis-04> 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: Mon, 12 Sep 2022 21:03:22 -0000
Greetings, Thank you for your replies. We have noted Reshad’s and Santosh’s approvals on the AUTH48 status page: https://www.rfc-editor.org/auth48/rfc9314 Once we receive approval from Vero, we will move forward with the publication process. Best regards, RFC Editor/ap > On Sep 12, 2022, at 8:34 AM, Santosh P K <santosh.pallagatti@gmail.com> wrote: > > Hello Alanna, > Sorry for the late reply. I've reviewed the updates and approved them all. > > Thanks > Santosh P K > > > > On Thu, Sep 1, 2022 at 5:53 AM Alanna Paloma <apaloma@amsl.com> 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 <gregimirsky@gmail.com> 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 <mjethanandani@gmail.com> 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, rfc-editor@rfc-editor.org 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 > >> > >> * rfc-editor@rfc-editor.org (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). > >> > >> * auth48archive@rfc-editor.org, 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, > >> auth48archive@rfc-editor.org 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 > > mjethanandani@gmail.com > > > > > > > > > > > > >
- [auth48] AUTH48: RFC-to-be 9314 <draft-ietf-bfd-r… rfc-editor
- Re: [auth48] AUTH48: RFC-to-be 9314 <draft-ietf-b… rfc-editor
- Re: [auth48] AUTH48: RFC-to-be 9314 <draft-ietf-b… Mahesh Jethanandani
- Re: [auth48] AUTH48: RFC-to-be 9314 <draft-ietf-b… Mahesh Jethanandani
- Re: [auth48] AUTH48: RFC-to-be 9314 <draft-ietf-b… Greg Mirsky
- Re: [auth48] AUTH48: RFC-to-be 9314 <draft-ietf-b… Alanna Paloma
- Re: [auth48] AUTH48: RFC-to-be 9314 <draft-ietf-b… Alanna Paloma
- Re: [auth48] AUTH48: RFC-to-be 9314 <draft-ietf-b… Rahman
- Re: [auth48] AUTH48: RFC-to-be 9314 <draft-ietf-b… Mahesh Jethanandani
- Re: [auth48] AUTH48: RFC-to-be 9314 <draft-ietf-b… Santosh P K
- Re: [auth48] AUTH48: RFC-to-be 9314 <draft-ietf-b… Alanna Paloma
- Re: [auth48] AUTH48: RFC-to-be 9314 <draft-ietf-b… Veronique ZHENG Lianshu
- Re: [auth48] AUTH48: RFC-to-be 9314 <draft-ietf-b… Alanna Paloma
- Re: [auth48] AUTH48: RFC-to-be 9314 <draft-ietf-b… Sandy Ginoza
- Re: [auth48] AUTH48: RFC-to-be 9314 <draft-ietf-b… John Scudder
- Re: [auth48] AUTH48: RFC-to-be 9314 <draft-ietf-b… Sandy Ginoza