Re: [auth48] AUTH48: RFC-to-be 9314 <draft-ietf-bfd-rfc9127-bis-04> for your review
Mahesh Jethanandani <mjethanandani@gmail.com> Tue, 30 August 2022 18:11 UTC
Return-Path: <mjethanandani@gmail.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 4134FC1524D0; Tue, 30 Aug 2022 11:11:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.105
X-Spam-Level:
X-Spam-Status: No, score=-2.105 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=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=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 xDuHZxBdT965; Tue, 30 Aug 2022 11:10:58 -0700 (PDT)
Received: from mail-pg1-x529.google.com (mail-pg1-x529.google.com [IPv6:2607:f8b0:4864:20::529]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 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 4B437C1524D3; Tue, 30 Aug 2022 11:10:58 -0700 (PDT)
Received: by mail-pg1-x529.google.com with SMTP id 73so3021481pga.1; Tue, 30 Aug 2022 11:10:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=references:to:cc:in-reply-to:date:subject:mime-version:message-id :from:from:to:cc; bh=rOmeKKqJPolLb1FU17LYIRvc5bitklM5T8EYVQ3pRs0=; b=JVrMaBXeSIesKreXmD/GSF2UQbYH3Zq4xNh8ceVEPnCK0my+WxGpccgkpq8sYYyPtG w/AysgpYX04Q8sOLEht9SobSmsCn9IPS8ImAOXZ1gI5xw2zInmjp2OoueRK4iW8bg64s 0Q4rpCR0Lg3b7WhjKQn5U9sNin7ekjymSR2c82OsDmAq7FQTuv/rJaF59ueM1SlA4cZn D3+RUNhfu3bLDBUXsHV6S8YekGGk6KDIoROTDE6YqbF2FWTCQ2IW6kvdXoERD+Ihkx4V 1CG/vPwNDe0sgTYVZGs9BNuC1qzlQotZhIs1ggkT97H16H6lmH7GBgmGcBzQeW5oUffZ Dr0Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=references:to:cc:in-reply-to:date:subject:mime-version:message-id :from:x-gm-message-state:from:to:cc; bh=rOmeKKqJPolLb1FU17LYIRvc5bitklM5T8EYVQ3pRs0=; b=XpYZYte6Q+rXvK5aCqv/AGbH8acXTU2tYbpIbaOoVK+f0j5ZOiqSzhtCQj3RsVlHNz J+qL4nFaaSRuCEAIt19bUlIls+RJ+FKT35UQ36kYwBsbmQLWtxjXbtbChNQi6VpJBWe+ JY3F3VCjGZ81A5pLFExCPWYdD8KTjgniihmB08zz0Xn+0NZuAXyjUI5Ta5fmerfF5emB MmTj2Zh2Pb91WxEAIy04uIdbLWkG3DeBgFEKiH6iXFhnGWeIFwEdaumwIaDM79o8xDrt KEe/A04nI4qIXW9LWdwIAsmdyMeLCjnDZ2aQ5DbquXlRH0k0+7gsubObShx/TNKncLC4 MfAw==
X-Gm-Message-State: ACgBeo2AVysfutw/9WJ9D0gKEu/M7ebgaKZ88Vh53RAatG4AyoBBOHTe tkPyslp6nv4jSAqrwf/6cupqpYScpsU=
X-Google-Smtp-Source: AA6agR4aKCEfT3XQrDckGabUeCKNyAQ5UI9B/47lbKBHjy1Fux3ctVr+wHDWAZi5rALpfoIMUMOLBQ==
X-Received: by 2002:a05:6a00:850:b0:536:341b:99b7 with SMTP id q16-20020a056a00085000b00536341b99b7mr22287924pfk.47.1661883056863; Tue, 30 Aug 2022 11:10:56 -0700 (PDT)
Received: from smtpclient.apple ([70.234.233.187]) by smtp.gmail.com with ESMTPSA id nh16-20020a17090b365000b001fd8316db51sm5230541pjb.7.2022.08.30.11.10.55 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 30 Aug 2022 11:10:56 -0700 (PDT)
From: Mahesh Jethanandani <mjethanandani@gmail.com>
Message-Id: <88D06E81-2AEC-4ABE-A934-67A3DBEC228A@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_4E70A369-F2B6-4ED0-A8BF-9B9F807079CD"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.13\))
Date: Tue, 30 Aug 2022 11:10:54 -0700
In-Reply-To: <20220830024146.E1BC255D49@rfcpa.amsl.com>
Cc: Reshad Rehman <reshad@yahoo.com>, "Vero Zheng (vero.zheng@huawei.com)" <veronique_cheng@hotmail.com>, "Santosh P. K." <santosh.pallagatti@gmail.com>, Greg Mirsky <gregimirsky@gmail.com>, bfd-ads@ietf.org, bfd-chairs@ietf.org, Jeffrey Haas <jhaas@pfrc.org>, auth48archive@rfc-editor.org
To: RFC Editor <rfc-editor@rfc-editor.org>
References: <20220830024146.E1BC255D49@rfcpa.amsl.com>
X-Mailer: Apple Mail (2.3654.120.0.1.13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/auth48archive/9unvW2QpOvwaBFJOe09jaljO2aM>
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: Tue, 30 Aug 2022 18:11:03 -0000
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