IETF Logo Mail Archive

Re: Some comments to the authors of draft-ietf-bfd-unsolicited

Greg Mirsky <gregimirsky@gmail.com> Mon, 28 February 2022 15:21 UTC

Return-Path: <gregimirsky@gmail.com>
X-Original-To: rtg-bfd@ietfa.amsl.com
Delivered-To: rtg-bfd@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 541923A12B1; Mon, 28 Feb 2022 07:21:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.106
X-Spam-Level:
X-Spam-Status: No, score=-2.106 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, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham 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 QCCKr4Fb8l5T; Mon, 28 Feb 2022 07:21:00 -0800 (PST)
Received: from mail-ej1-x632.google.com (mail-ej1-x632.google.com [IPv6:2a00:1450:4864:20::632]) (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 14AD03A12A3; Mon, 28 Feb 2022 07:21:00 -0800 (PST)
Received: by mail-ej1-x632.google.com with SMTP id dr20so761872ejc.6; Mon, 28 Feb 2022 07:20:59 -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=krC7db1qF1sQXZdGhvrKkYm0bM8X95iMGwNP5WK23ec=; b=IMge9bheMKDl9thJ9CFYb/cDIIBCUp627PCGeqh98CkNbHdvy6gzxSta/RivkDoSQV 7+tBb+Ubkt8dzG3TJ5lN2mDwAH04g7HBbvD6b5ujYxMw8wW7T7dcC/VH3GWiuKe1RzzB a+OhjcjVsqNnGfuzsHLMisy4HTw1YOdXm5b89+fPcW5rm/33dwMf0Uk3Duew2tnHJ/Og eUryBz6WJxFOa1fk4yhfanXsU1oyXcwjjsHft9sM1VpvZ+9+lZk0FKsh4oQPR7Znnx8d 7zbitqDaUlzgHYBUrtGhBE5rxlf8Tcnr4bIwizl5MzxKZ+TE3OgNUzKy9cAtTAk5b25G CdGQ==
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=krC7db1qF1sQXZdGhvrKkYm0bM8X95iMGwNP5WK23ec=; b=BqQXPkdtwCNqZ4vUhCODk5sUGHxLXI5qdLnH7Ex+hAhRisehtkiU+7HIL0OMbq8gO5 N0mMjhrJvTuEc+IMa/duY/0k9KET10gHmJtuRFzDp9aIN3UpIzbaDZQyb/v1R/wELhLg nM3VDyBVz+6D1Rooj+6AIyy1X4pxADXYw866rGbw5a3jPaTztqhluBGdcX7yHqO9w6s1 R+OsSxOww/jkfQOQcZZP16B7co+o10SdaXpcIq3SI/DOMthKBwjsWxixqhwbEKkUXO4I yradXHtpbXo37N5zGB4pcO1iIPVA71lIXiE8Tfzq/srXsDOi7SzpLkl7cN0Qat7e10iO CoGw==
X-Gm-Message-State: AOAM532C+fhOzhUc72GXEJmPpQdsx/TAdAFTYxtlBlyBalZ7M1Dc+J3X WGL63+W20tMQ8qUTASUJ1UmQZGspyaM1bO+MWoQ=
X-Google-Smtp-Source: ABdhPJz6py5jbTAmMvOIhz0yO+yTWYAxl4rlVzTI2t/Wt0mt0oP5tPvS51UOwdPZQcCOEyBFQAlo694ygIkS0hWiPfA=
X-Received: by 2002:a17:907:3e94:b0:6d1:d64e:3141 with SMTP id hs20-20020a1709073e9400b006d1d64e3141mr14795228ejc.213.1646061657873; Mon, 28 Feb 2022 07:20:57 -0800 (PST)
MIME-Version: 1.0
References: <CA+RyBmX8oAQFqJMjVhcj_78wYfrvz+afnSoP2-VjWyfCEunqmQ@mail.gmail.com> <381777191.1553826.1645979075642@mail.yahoo.com> <20220227225309.GA2990@pfrc.org> <CA+RyBmU_FAPf2OLv_aWnf48TATd4ddLgjTFWoKxR5xY4FL+YMQ@mail.gmail.com> <C1D5204A-C691-411F-A3BE-9FD9376563E7@pfrc.org>
In-Reply-To: <C1D5204A-C691-411F-A3BE-9FD9376563E7@pfrc.org>
From: Greg Mirsky <gregimirsky@gmail.com>
Date: Mon, 28 Feb 2022 07:20:46 -0800
Message-ID: <CA+RyBmVCZ=fHHosOjSqBdEix1-u+fXSB1ku3=Hrz4hRNbNJRDg@mail.gmail.com>
Subject: Re: Some comments to the authors of draft-ietf-bfd-unsolicited
To: Jeffrey Haas <jhaas@pfrc.org>
Cc: Reshad Rahman <reshad@yahoo.com>, "draft-ietf-bfd-unsolicited@ietf.org" <draft-ietf-bfd-unsolicited@ietf.org>, rtg-bfd WG <rtg-bfd@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000065605205d91598aa"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-bfd/sl3FVp7RD3KGxGh1X7u6-5MO-RI>
X-BeenThere: rtg-bfd@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "RTG Area: Bidirectional Forwarding Detection DT" <rtg-bfd.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtg-bfd>, <mailto:rtg-bfd-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtg-bfd/>
List-Post: <mailto:rtg-bfd@ietf.org>
List-Help: <mailto:rtg-bfd-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtg-bfd>, <mailto:rtg-bfd-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Feb 2022 15:21:04 -0000

Thank you, Jeff. Let ADs discuss it when the document comes to the IESG.

Regards,
Greg

On Mon, Feb 28, 2022 at 3:39 AM Jeffrey Haas <jhaas@pfrc.org> wrote:

> Greg,
>
> On Feb 27, 2022, at 7:54 PM, Greg Mirsky <gregimirsky@gmail.com> wrote:
>
> Hi Jeff,
> of course, the WG can send the document IESG on its current track. What is
> not clear to me is what is being standardized by the document. It appears
> that everything described is a local behavior that does not affect any
> other BFD system. Is my understanding correct? Or I'm missing something?
> I also have some follow-up notes to share with the authors.
>
>
> See the cited message from the OPS AD.
>
> I suggest not spending energy fighting this point in the Working Group.
> Feel free to direct your questions directly to Rob.
>
> -- Jeff
>
>
> https://mailarchive.ietf.org/arch/msg/rtg-bfd/vOMZl9ucZwNKu5_MHHti-4ImOjQ/#
>>
>
>

v2.23.0 | Report a Bug | By Email