Re: BFD Echo mode coverage in BFD for VXLAN

Greg Mirsky <gregimirsky@gmail.com> Fri, 09 August 2019 00:03 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 C1F8D120088; Thu, 8 Aug 2019 17:03:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level:
X-Spam-Status: No, score=-1.997 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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 pMHhU_SRyU3N; Thu, 8 Aug 2019 17:03:58 -0700 (PDT)
Received: from mail-lj1-x234.google.com (mail-lj1-x234.google.com [IPv6:2a00:1450:4864:20::234]) (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 A2E63120025; Thu, 8 Aug 2019 17:03:57 -0700 (PDT)
Received: by mail-lj1-x234.google.com with SMTP id t28so90497888lje.9; Thu, 08 Aug 2019 17:03:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=HRgUPmkV7fmYBSdxgn6x/ptcFu2pj4Ty6C3+ZFGEhNw=; b=H95330tSnLUxNXR/YMSJXdfshXtX/avdx9LMkOvTNVe/givUC0zK27C3SOT5OwpMoC BbB+GjCH/6DZd17I2Jsoj798RdHY3bJ9so89xWldJKkQ4EbDfIkZ+n8Ke0mC4HtcQRdc X+tWAIrlMP322TqcGTDk8yxOFNUARuB17i5izi6q/gi5YHOLNbPFhW/aJuL4Ut1MsprF OsIYcoz6jZ3F7sPjpo6yARprErtNii/GFct1SVPFj8Yz8+Rx/3jDlhuU+4FkB/oCH26B pyK5hAACn0pxRN+gHNSFAFrtGugEFfnxoyoV2zZZoyJfpeeNgiT1Lxu88GgoK5TCmg9D G7OQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=HRgUPmkV7fmYBSdxgn6x/ptcFu2pj4Ty6C3+ZFGEhNw=; b=AYmR1P4ay2byHhgaFebU3ylf3sAdrNzM8gGogQpBZYEYDNcwllLFG5ArtO0qO1o1pz tYi6PevJTVvmqrB5UgsaxmflouuOdaoC1WUBvVRGDTpq0vpbpEC+3g4c9rpmHDpzLldR OfDM3fjxfA4pQMW4Ik3K5tTeJY23dDXhuUjlq7GjlO3HjM+IIfJfcMgWMlI/E8DGw6sA ntqP4+OYnxwQhTmVERmMzFT4F7tN++P/oAm1Ake3fls+8VQYS2eeg+GyFL97nE8P3YEs bUH3OQn43iFtGQ+Qy5eEU22tB0FFnxNUiBScHMKiI33sRHK7QSwGcdvy3RHCGWzrZB1M 6lZw==
X-Gm-Message-State: APjAAAVj9fbVyuADxSidQ+S/sGHIVkNWd5eiRuKrSlVrgPhnUQT6lAFe PnYAcHJknMgmQ+JnCiOw9ZyJuGQA8Minf8B1ZFdi1Q==
X-Google-Smtp-Source: APXvYqwYieiqvMr3nO0ZeCYVPxd9OXam0ge+lLBkNISeIFSx3K0B6mrwH4viznJvpUdkiHtxlTsUShBp29sabgdbnys=
X-Received: by 2002:a2e:7614:: with SMTP id r20mr9880495ljc.42.1565309035913; Thu, 08 Aug 2019 17:03:55 -0700 (PDT)
MIME-Version: 1.0
References: <CA+RyBmVZeLz-wuC04_V3QJxXDG_qOc_3KO0d3N5h0Y-dDTTFXQ@mail.gmail.com> <3747ADED-2F3A-42B8-BD72-20218D167DEE@cisco.com> <CA+RyBmURk5ew+DuHm9S_6yv0op=ALadoMfwWw9Qs5XLpsog2fA@mail.gmail.com>
In-Reply-To: <CA+RyBmURk5ew+DuHm9S_6yv0op=ALadoMfwWw9Qs5XLpsog2fA@mail.gmail.com>
From: Greg Mirsky <gregimirsky@gmail.com>
Date: Thu, 8 Aug 2019 17:03:45 -0700
Message-ID: <CA+RyBmVwSyD3aERjprcTJChAVqkwf1R1JsV_TerZ4Sw54UaDDQ@mail.gmail.com>
Subject: Re: BFD Echo mode coverage in BFD for VXLAN
To: "Carlos Pignataro (cpignata)" <cpignata@cisco.com>
Cc: rtg-bfd WG <rtg-bfd@ietf.org>, "bfd-chairs@ietf.org" <bfd-chairs@ietf.org>, Martin Vigoureux <martin.vigoureux@nokia.com>
Content-Type: multipart/alternative; boundary="0000000000000ca838058fa3e9f2"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-bfd/oaewujK0GOYzfdVb0pJ_tgqRbaY>
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: Fri, 09 Aug 2019 00:04:00 -0000

Dear All,
I was pointed out that my previous e-mail asking for WG help to progress
BFD over VXLAN document by sharing opinions regarding coverage of the BFD
Echo mode may be overstepping the bounds of an Editor. I apologize, that
was not my intention. I'm asking WG Chairs to help to arrive at the
conclusion of this question in a reasonable time.

Regards,
Greg

On Thu, Aug 8, 2019 at 4:06 PM Greg Mirsky <gregimirsky@gmail.com> wrote:

> Dear All,
> I have not set the when this poll closes. I hope that two weeks would be
> sufficient time for the WG community to express their thoughts.
>
> Dear Carlos,
> thank you for sharing your opinion on the scope of the document in regard
> to BFD Echo mode. You've expressed support for exploring the applicability
> of the BFD Echo mode. Would you support that effort by contributing some
> text, if WG decides that documenting the applicability of the Echo mode in
> BFD over VXLAN is useful?
>
> Regards,
> Greg
>
>
> On Wed, Aug 7, 2019 at 6:18 PM Carlos Pignataro (cpignata) <
> cpignata@cisco.com> wrote:
>
>> Dear Greg,
>>
>> The option of replacing the existing text for something more ambiguous
>> and implicit does not seem like progress in my humble opinion. The spec
>> ends up with the same capabilities, but the text is more obscure. I do not
>> support that option.
>>
>> My recommendation for your consideration would be:
>>
>>    1. Explore if it is possible to run BFD Echo as a single-hop.
>>    2. If yes, add text supporting it.
>>    3. If no, add text explaining why not on technical grounds.
>>
>>
>> A less desirable option would be if the WG does not care about BFD Echo,
>> to explicitly keep it out of scope (not on technical grounds).
>>
>> Best,
>>
>> Carlos.
>>
>> On Aug 5, 2019, at 6:16 PM, Greg Mirsky <gregimirsky@gmail.com> wrote:
>>
>> Dear All,
>> in course of reviews of the draft, several times a question was asked
>> about the rationale for excluding BFD Echo from the scope of this document:
>>
>> 7.  Echo BFD
>>
>>    Support for echo BFD is outside the scope of this document.
>>
>> Much appreciate your consideration of the following options:
>>
>>    - describe the applicability of BFD Echo in VXLAN environment in the
>>    document;
>>    - remove Section 7 and clarify in the Introduction
>>
>> NEW TEXT:
>>
>> This specification describes procedures only for BFD Asynchronous mode.
>>
>>
>>    - make no changes at all.
>>
>> Regards,
>> Greg
>>
>>
>>