Re: [pim] Éric Vyncke's No Objection on draft-ietf-pim-bfd-p2mp-use-case-09: (with COMMENT)
Greg Mirsky <gregimirsky@gmail.com> Tue, 30 November 2021 16:23 UTC
Return-Path: <gregimirsky@gmail.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 571BB3A1408; Tue, 30 Nov 2021 08:23:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.696
X-Spam-Level:
X-Spam-Status: No, score=-0.696 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_COMMENT_SAVED_URL=1.391, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_HTML_ATTACH=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OoY5tUhRpTF3; Tue, 30 Nov 2021 08:23:28 -0800 (PST)
Received: from mail-ed1-x52d.google.com (mail-ed1-x52d.google.com [IPv6:2a00:1450:4864:20::52d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EB0C93A1405; Tue, 30 Nov 2021 08:23:27 -0800 (PST)
Received: by mail-ed1-x52d.google.com with SMTP id v1so88999941edx.2; Tue, 30 Nov 2021 08:23:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=6jxFvxqt6g+gd2S0JFGC+JVll+pHRtiVWyQG9fWtlAc=; b=fO4iRsNn54CQt/5WTpnPiOu0M0h5qNNXWCUu/cgzz4Fr+17BjIRzWqCzwNGy5oPrPa 4LsBnC25hO6KCz2vVfli0dq9T8dmhAmyukvd5UqJ10lpW0qlQL/LW5+/dUzn61czRoue P4bTRSPBAqYeKpwiqx2MTp8joA+PR794fTLcQDh/c7ZhaKoEhfb9K17drcx8hgzzDEhx pP3auU/BVj0laVDybD1Ve7rkdKZxijXMy1kJZhL4IPE3ALgaBQbqhza7kbDOwf4CU5z8 uIueVaRqIYSTiZYeyudHXe3ZG7mpRObru9lJ8dM/lcoEnvAng8TXAsJ4zke5of9bzyMQ DqZQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=6jxFvxqt6g+gd2S0JFGC+JVll+pHRtiVWyQG9fWtlAc=; b=LBLA2p59i2wL3RTyMiB4KPoHc21FDmSYmxVNunWTszOP0JCERVfbjInywiLmRbWPoY /l6LMk/uy6GIOWG2ccpwGzTXlZGG74cQ+rLubiKOdVH64Zyr44cZPEC/M46rtuXx99VM 76BDOBo6w7hxnMrcnzieLG5SsozW4IFieewQhkqR1q+kWLBaD1p92RR93BFIQgwAQp9L OgZqOkWMPV31ql9lMWJdZsY/gV2uRm/7gKB+n/IycDOi0pvEN3zpUSgnhChU5CYiAcka JchsJS7jHlQHb1X9B8hQSKzuiH5sJqjM/HEsn9y1a8nSFAcE/2Bc388q7b5jjVaAfEsD kqeg==
X-Gm-Message-State: AOAM5302sURWGPtghxR4VqUto6Jd8MiHn2Wwjkv3jYCtUJ+w4jRhGS6Q YL20qq/pRLO9bvhErf9FA9pNEaPEyexkB09QLkbdQAY9
X-Google-Smtp-Source: ABdhPJzvEDN5eTOL+C8tMnmrBorYhni+SztN0Az5M56+C/2ugp0/l8/bWJA/AEaJl5Tz5nl1wwTgkAZCs/ZcUvL7pAI=
X-Received: by 2002:aa7:d048:: with SMTP id n8mr83384919edo.333.1638289405141; Tue, 30 Nov 2021 08:23:25 -0800 (PST)
MIME-Version: 1.0
References: <163828697036.11594.10665829870648284999@ietfa.amsl.com>
In-Reply-To: <163828697036.11594.10665829870648284999@ietfa.amsl.com>
From: Greg Mirsky <gregimirsky@gmail.com>
Date: Tue, 30 Nov 2021 08:23:13 -0800
Message-ID: <CA+RyBmUCF2wYd7xgh438br0jEBiq2StHMuCPhVGg48WOQgUGkQ@mail.gmail.com>
To: Éric Vyncke <evyncke@cisco.com>
Cc: The IESG <iesg@ietf.org>, draft-ietf-pim-bfd-p2mp-use-case@ietf.org, pim-chairs@ietf.org, pim@ietf.org, mmcbride7@gmail.com, Alvaro Retana <aretana.ietf@gmail.com>
Content-Type: multipart/mixed; boundary="00000000000008783d05d203faca"
Archived-At: <https://mailarchive.ietf.org/arch/msg/pim/l76WZM1rmUgRa5RYyQ48V8Lt0aU>
Subject: Re: [pim] Éric Vyncke's No Objection on draft-ietf-pim-bfd-p2mp-use-case-09: (with COMMENT)
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pim/>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Nov 2021 16:23:32 -0000
Hi Éric, thank you for your kind words supporting this work. Please find my notes in-lined after your comments under the GIM>> tag. Attached, please find the diff highlighting the updates in the working version of the draft. Regards, Greg On Tue, Nov 30, 2021 at 7:42 AM Éric Vyncke via Datatracker < noreply@ietf.org> wrote: > Éric Vyncke has entered the following ballot position for > draft-ietf-pim-bfd-p2mp-use-case-09: No Objection > > When responding, please keep the subject line intact and reply to all > email addresses included in the To and CC lines. (Feel free to cut this > introductory paragraph, however.) > > > Please refer to https://www.ietf.org/blog/handling-iesg-ballot-positions/ > for more information about how to handle DISCUSS and COMMENT positions. > > > The document, along with other ballot positions, can be found here: > https://datatracker.ietf.org/doc/draft-ietf-pim-bfd-p2mp-use-case/ > > > > ---------------------------------------------------------------------- > COMMENT: > ---------------------------------------------------------------------- > > Thank you for the work put into this document. > > Please find below some non-blocking COMMENT points (but replies would be > appreciated even if only for my own education). > > Special thanks to Mike McBride the shepherd's write-up including the > section > about the WG consensus. > > I hope that this helps to improve the document, > > Regards, > > -éric > > == COMMENTS == > > Does the use of BFD prevent the use of normal PIM detection? It is a little > unclear from the text and I hope that BFD comes on the top of normal PIM > detection mode. > GIM>> You're correct, BFD does not negate any of the PIM mechanisms, including the loss of a neighbor. I would be much obliged if you can suggest any text update or addition to stress that. > > -- Section 2.3 -- > Please add "All received BFD Control packets that are > demultiplexed to the session MUST be discarded if the received TTL or > Hop Limit is not equal to 255." Copied from RFC 5881. > GIM>> Added. > > -- Section 4 -- > The security section appears rather light to me as now any BFD security > issues > can also impact PIM. > GIM>> Indeed. A reference to RFC 5881 has been added to the Security Consideration section (working version).
- [pim] Éric Vyncke's No Objection on draft-ietf-pi… Éric Vyncke via Datatracker
- Re: [pim] Éric Vyncke's No Objection on draft-iet… Greg Mirsky