Re: Correcting BFD Echo model

Greg Mirsky <gregimirsky@gmail.com> Fri, 24 March 2017 19:09 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 8FB41127011; Fri, 24 Mar 2017 12:09:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 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_LOW=-0.7, SPF_PASS=-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 dFPFECOgFWr9; Fri, 24 Mar 2017 12:09:18 -0700 (PDT)
Received: from mail-oi0-x22a.google.com (mail-oi0-x22a.google.com [IPv6:2607:f8b0:4003:c06::22a]) (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 3373312987B; Fri, 24 Mar 2017 12:09:18 -0700 (PDT)
Received: by mail-oi0-x22a.google.com with SMTP id l203so6113737oia.0; Fri, 24 Mar 2017 12:09:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=mK1bZ+jnxjwYA8gxMOEXExBH6AUeoha4nkHQaQRcx4I=; b=OGdYpelhwJQOgMZotVB4w4AKRz57XL/433n11DfS25n9xlpTrX6cPhPQ+hYz8q+l3w nQHZSH313U17urh0AI8JB7mbRQmOQdachiba/4s6i3ztCqaj33PDhHeie/ei1xxKaR6K rJEoWaX8PiO9iZwvFrwn9kDYNOlEml33gATx2e9X/9zvR/FZKpDRrZ6+uElAF1CtQ0be P7K5z2EB2Atx057xyswxcXdp6IU+XfVJvNpLoc2Qw21AFaa5SJLEMRrADx35gnTZ1aiw /TUU8y3gqHQZgBO1b3lh5sXrX/Lsb8AYQTK4oXRG4/DbJmyD2wvO4SfNCDarnqPiV/YC etSg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=mK1bZ+jnxjwYA8gxMOEXExBH6AUeoha4nkHQaQRcx4I=; b=VivRU4OCZXQCGJwHJGG8Jj+0OCF21Rqzq09+FqtwkTf/i7bkkOdbBXiBVQ7Hx4CAW7 KFcg+AlEZGQd/pOp/RGuHhLa4/7D4saVVOZCOUd8l+RBITlMKam3nnIEzwwDh1bKSMHV oQjZ00Vf32lsjcQZEzFTs3wpiXWYR4KwzvPmmfNxk+gukzlCyWX8Ovenp7V+LTGYt//U jAiMEZ5s3b36CIWvw1fj5BzjFQ8rQOgc+zg55/GtCUyzYqWeA1BQEg07CIf058eeJVva 87MP5dObXQ7lv+vpGWs+mBTXySS9mWrxo5h4C8k2ePEVKy/thTyEPUgbVixIpEJLhiCz 2hXQ==
X-Gm-Message-State: AFeK/H3ob0hLcnuwMrnUpPHK+4FSEHpbPbUgC6EVDXGrr8ZahHlqcWisBoqyZBrJ7bbacRqD7Y55musGz5jbaA==
X-Received: by 10.202.77.1 with SMTP id a1mr5650156oib.157.1490382557602; Fri, 24 Mar 2017 12:09:17 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.157.21.21 with HTTP; Fri, 24 Mar 2017 12:09:17 -0700 (PDT)
In-Reply-To: <F6DB90E6-B6DF-4175-83DC-188CDEF2D67F@cisco.com>
References: <CA+RyBmWcU79iCBYM_bi__Ce1RpWwNn_jZCkPHv3Sc+qtybt_pg@mail.gmail.com> <D4D8BE31.25AE5C%rrahman@cisco.com> <CA+RyBmWyQZs5B3LG8x=ZoVXTkiHhGPzbZwRX70jCyT_MpQwzCA@mail.gmail.com> <E308FD25-A695-498C-8E34-756250776CE4@gmail.com> <CA+RyBmW=t0DH5H_UVau8t5rS_1A8Qpsh478ayVUN=Se6qqKHyg@mail.gmail.com> <D4D9967A.25B679%rrahman@cisco.com> <CA+RyBmV9QiGGCgxxEHmC8GjnecHksjfZgVO3NJ5q2aLSSrZMvA@mail.gmail.com> <20170324154640.GO27015@pfrc.org> <CA+RyBmUE3g1gNTtf30Wr7hvgMhahnuCznt7LY77kLGSXNYQ=Xg@mail.gmail.com> <F6DB90E6-B6DF-4175-83DC-188CDEF2D67F@cisco.com>
From: Greg Mirsky <gregimirsky@gmail.com>
Date: Fri, 24 Mar 2017 14:09:17 -0500
Message-ID: <CA+RyBmWsy=dhzH3Fpe+4o20BgVWduKuQrpkFyyyOhfGWq+aVtg@mail.gmail.com>
Subject: Re: Correcting BFD Echo model
To: "Carlos Pignataro (cpignata)" <cpignata@cisco.com>
Cc: Jeff Haas <jhaas@pfrc.org>, "Reshad Rahman (rrahman)" <rrahman@cisco.com>, "rtg-bfd@ietf. org" <rtg-bfd@ietf.org>, "draft-ietf-bfd-yang@ietf.org" <draft-ietf-bfd-yang@ietf.org>
Content-Type: multipart/alternative; boundary="001a11c15cd2ecf1b8054b7eba86"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-bfd/j_5hblS7Lsx3jgzWk4dkmN-3_Cs>
X-BeenThere: rtg-bfd@ietf.org
X-Mailman-Version: 2.1.22
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, 24 Mar 2017 19:09:21 -0000

Hi Carlos,
indeed, the RFC 5880 does explain that the rate of BFD control packets
transmitted in Async mode may be reduced when Echo is activated. If anyone
is familiar with such implementation, I'd be glad to learn and discuss how
this mechanism affects the data model. Regrettably, I don't have personal
experience with using or implementing such mechanism.

Greg

On Fri, Mar 24, 2017 at 1:59 PM, Carlos Pignataro (cpignata) <
cpignata@cisco.com> wrote:

> Hi, Greg,
>
> It would be useful to understand uses of BFD Echo for on-demand scenarios.
>
> It’s not clear how that would be:
>
>    When a system is using the Echo function, it is advantageous to
>    choose a sedate reception rate for Control packets, since liveness
>    detection is being handled by the Echo packets.  This can be
>
> Thanks,
>
> — Carlos.
>
> On Mar 24, 2017, at 2:50 PM, Greg Mirsky <gregimirsky@gmail.com> wrote:
>
> Hi Jeff,
> I'll be glad to put couple slides to help jumstart the discussion on BFD
> Echo.
>
> Regards,
> Greg
>
> On Fri, Mar 24, 2017 at 10:46 AM, Jeffrey Haas <jhaas@pfrc.org> wrote:
>
>> [continuing the top-posting heresy to preserve context]
>>
>> Greg,
>>
>> Our schedule is relatively open right now, and this matter is esoteric
>> enough that it probably warrants a slide for the majority of the Working
>> Group to follow this issue.  Would you prepare a slide or two to use as a
>> discussion point?
>>
>> I'll also use this opportunity to point out that in S-BFD scenarios, we
>> have
>> somewhat similar ambiguities since it's an on-demand service.
>>
>> -- Jeff
>>
>> On Mon, Feb 27, 2017 at 07:31:01AM -0800, Greg Mirsky wrote:
>> > Hi Reshad,
>> > thank you for providing the context to BFD Echo TX. Indeed, I'm familiar
>> > with implementations that use BFD Echo as Echo request/reply and thus Tx
>> > would be in RPC, not in configuration. I think that it would be good to
>> > discuss this in Chicago unless we hear comments from others on the list.
>> >
>> > Regards,
>> > Greg
>> >
>> > On Mon, Feb 27, 2017 at 5:56 AM, Reshad Rahman (rrahman) <
>> rrahman@cisco.com>
>> > wrote:
>> >
>> > > Hi Greg,
>> > >
>> > > draft-zheng-mpls-ls-ping-yang-cfg defines transmit interval in RPC
>> > > because all ping operations are done via RPC.  I do not consider BFD
>> echo
>> > > to be “on demand” like LSP Ping (caveat: this is possibly due to the
>> BFD
>> > > configuration/implementation I am most familiar with).
>>
>>
>
>