Re: BFD stability follow-up from IETF-91
Manav Bhatia <manavbhatia@gmail.com> Mon, 08 December 2014 06:26 UTC
Return-Path: <manavbhatia@gmail.com>
X-Original-To: rtg-bfd@ietfa.amsl.com
Delivered-To: rtg-bfd@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 68C121A6F56 for <rtg-bfd@ietfa.amsl.com>; Sun, 7 Dec 2014 22:26:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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, SPF_PASS=-0.001] autolearn=ham
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 nyJtXJm904m6 for <rtg-bfd@ietfa.amsl.com>; Sun, 7 Dec 2014 22:26:45 -0800 (PST)
Received: from mail-ob0-x22c.google.com (mail-ob0-x22c.google.com [IPv6:2607:f8b0:4003:c01::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0E5C01A6F51 for <rtg-bfd@ietf.org>; Sun, 7 Dec 2014 22:26:45 -0800 (PST)
Received: by mail-ob0-f172.google.com with SMTP id wn1so3205317obc.31 for <rtg-bfd@ietf.org>; Sun, 07 Dec 2014 22:26:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=kuWAeVWuYkkjt73K9lAtZULJLop70m6C+/KbEpYvVlM=; b=FBoOefSR4WTbSLtabZjloE6ccDmHRAq57aBxkTgrKo2HvvvLjiwj4MyQ014M0rPu5A 8q0+iMkE0U/t6ku8tu8kybXMlBkDJOxrDFegp940504+4IxeWMI4z/Z/N51PmlRgusgE ulvwd55HBh9Ig8ZlhguNaiTXQmZzNl2gwhc6Q73f2H+HGYBl+EnoIZ8XvpJiLdl0bQn5 uRA0YOAVvTM+QOKz3i1AK0Cn/y27GhytgFmH/vnpDZETjF9wZ8LysYVdNZCdOFskIy2I zcz3VxDNZepwaNydlyWAHgOEHsS4xl1KzDKzZ5HhLB023QLoqMv8ImCMnETDA36bYMFf oovA==
MIME-Version: 1.0
X-Received: by 10.60.146.231 with SMTP id tf7mr6572004oeb.48.1418020004380; Sun, 07 Dec 2014 22:26:44 -0800 (PST)
Received: by 10.76.178.199 with HTTP; Sun, 7 Dec 2014 22:26:44 -0800 (PST)
In-Reply-To: <7347100B5761DC41A166AC17F22DF1121B8AE751@eusaamb103.ericsson.se>
References: <CO2PR0501MB823C222B7D62779F4DF58CDB3780@CO2PR0501MB823.namprd05.prod.outlook.com> <D0A647C1.28843%mmudigon@cisco.com> <CO2PR0501MB8234A1BDDFD008EE12C847AB3780@CO2PR0501MB823.namprd05.prod.outlook.com> <CECE764681BE964CBE1DFF78F3CDD3943F5AE38D@xmb-aln-x01.cisco.com> <CAG1kdogkUr2YyodeUPWOqea+2jqOkmdYnPywVHCw8j1+=9eM6A@mail.gmail.com> <CECE764681BE964CBE1DFF78F3CDD3943F5AE4AE@xmb-aln-x01.cisco.com> <CAG1kdoh5DwdKrJWK_aSvo4KQ6Xu5ZaTObe_PLhV66YZ4yQozmg@mail.gmail.com> <20141207193610211284.1f098741@sniff.de> <CAG1kdojxdDY0qXPYnZ5K67rizVaD7gHte1MdRA2q==K6SoRVsw@mail.gmail.com> <CO2PR0501MB823962B235ACA590C076236B3640@CO2PR0501MB823.namprd05.prod.outlook.com> <7347100B5761DC41A166AC17F22DF1121B8AE751@eusaamb103.ericsson.se>
Date: Mon, 08 Dec 2014 11:56:44 +0530
Message-ID: <CAG1kdogLZs_ih61MZHHDUK6Yp8WgoZnHwXfeTS7dHWf+TZJzwg@mail.gmail.com>
Subject: Re: BFD stability follow-up from IETF-91
From: Manav Bhatia <manavbhatia@gmail.com>
To: Gregory Mirsky <gregory.mirsky@ericsson.com>
Content-Type: multipart/alternative; boundary="047d7b5d341aa5456b0509ae82a6"
Archived-At: http://mailarchive.ietf.org/arch/msg/rtg-bfd/hAI0OP7hghC9ehA0p5lARzFJovM
Cc: "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>
X-BeenThere: rtg-bfd@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 08 Dec 2014 06:26:47 -0000
Hi Greg, What if i dont have a single-hop session? Do you want the operator to set up one between the sender and its immediate next-hop and another between the receiver and its immediate next-hop? Cheers, Manav On Mon, Dec 8, 2014 at 11:52 AM, Gregory Mirsky <gregory.mirsky@ericsson.com > wrote: > Hi Santosh, > > do you envision scenario when BFD multi-hop and single-hop sessions that > share the same sender behave differently? In my opinion, if multi-hop > session is unstable and single-hop is stable, then the problem is likely in > the network and thus is real, rather than in the BFD sender and more > implementation specific. Thus running BFD Echo even without cooperation of > the next hop node (no timestamps there) would give sender information about > latencies BFD is subjected to in this node. > > > > Regards, > > Greg > > > > *From:* Rtg-bfd [mailto:rtg-bfd-bounces@ietf.org] *On Behalf Of *Santosh > P K > *Sent:* Monday, December 08, 2014 2:07 PM > *To:* Manav Bhatia; Marc Binderberger > *Cc:* rtg-bfd@ietf.org > *Subject:* RE: BFD stability follow-up from IETF-91 > > > > Hello Mac and Manav, > > Are we just talking about singlehop? How about MPLS BFD and multihop > where echo does not work? > > > > Thanks > > Santosh P K > > > > *From:* Rtg-bfd [mailto:rtg-bfd-bounces@ietf.org > <rtg-bfd-bounces@ietf.org>] *On Behalf Of *Manav Bhatia > *Sent:* Monday, December 08, 2014 9:33 AM > *To:* Marc Binderberger > *Cc:* rtg-bfd@ietf.org > *Subject:* Re: BFD stability follow-up from IETF-91 > > > > Hi Marc, > > > > > > * Greg's echo idea is of course do-able - when you think timestamping in > hardware can be done then it can be done in the forwarding path for echos > as > well. Depends on your hardware :-) and on an agreed (minimal) format for > echo. As mentioned BFD echo is not defined/used for multiple BFD features, > which limits it's use though. > > > > For the echo mechanism to work, do you agree that you would have to > continuously send Echos so that you can detect the issue? > > > > Or are you suggesting that once BFD flaps we will start sending Echoes > overloaded with debug information to detect the issue? > > > > I'd like to understand this before the mailing list sees a barrage of > emails. Alternatively, we can also take it offline and only report the > summary of our discussion to the list. > > > > Cheers, Manav >
- BFD stability follow-up from IETF-91 Jeffrey Haas
- Re: BFD stability follow-up from IETF-91 Manav Bhatia
- Re: BFD stability follow-up from IETF-91 Marc Binderberger
- RE: BFD stability follow-up from IETF-91 Mach Chen
- RE: BFD stability follow-up from IETF-91 Marc Binderberger
- RE: BFD stability follow-up from IETF-91 Gregory Mirsky
- Re: BFD stability follow-up from IETF-91 Manav Bhatia
- RE: BFD stability follow-up from IETF-91 Mach Chen
- RE: BFD stability follow-up from IETF-91 Vengada Prasad Govindan (venggovi)
- Re: BFD stability follow-up from IETF-91 Manav Bhatia
- Re: BFD stability follow-up from IETF-91 Manav Bhatia
- RE: BFD stability follow-up from IETF-91 Santosh P K
- RE: BFD stability follow-up from IETF-91 Santosh P K
- RE: BFD stability follow-up from IETF-91 Santosh P K
- RE: BFD stability follow-up from IETF-91 Santosh P K
- Re: BFD stability follow-up from IETF-91 Manav Bhatia
- RE: BFD stability follow-up from IETF-91 Santosh P K
- Re: BFD stability follow-up from IETF-91 Manav Bhatia
- Re: BFD stability follow-up from IETF-91 Abhishek Verma
- RE: BFD stability follow-up from IETF-91 Fan, Peng
- Re: BFD stability follow-up from IETF-91 MALLIK MUDIGONDA (mmudigon)
- RE: BFD stability follow-up from IETF-91 Fan, Peng
- Re: BFD stability follow-up from IETF-91 MALLIK MUDIGONDA (mmudigon)
- RE: BFD stability follow-up from IETF-91 Santosh P K
- Re: BFD stability follow-up from IETF-91 Manav Bhatia
- RE: BFD stability follow-up from IETF-91 Gregory Mirsky
- Re: BFD stability follow-up from IETF-91 Jeffrey Haas
- RE: BFD stability follow-up from IETF-91 Gregory Mirsky
- Re: BFD stability follow-up from IETF-91 Marc Binderberger
- Re: BFD stability follow-up from IETF-91 Marc Binderberger
- RE: BFD stability follow-up from IETF-91 Marc Binderberger
- RE: BFD stability follow-up from IETF-91 Fan, Peng
- RE: BFD stability follow-up from IETF-91 Gregory Mirsky
- Re: BFD stability follow-up from IETF-91 Mahesh Jethanandani
- RE: BFD stability follow-up from IETF-91 Santosh P K
- RE: BFD stability follow-up from IETF-91 Gregory Mirsky
- RE: BFD stability follow-up from IETF-91 Gregory Mirsky
- RE: BFD stability follow-up from IETF-91 Santosh P K
- RE: BFD stability follow-up from IETF-91 Gregory Mirsky
- RE: BFD stability follow-up from IETF-91 Vengada Prasad Govindan (venggovi)
- RE: BFD stability follow-up from IETF-91 Santosh P K
- RE: BFD stability follow-up from IETF-91 Santosh P K
- Re: BFD stability follow-up from IETF-91 Manav Bhatia
- Re: BFD stability follow-up from IETF-91 Mahesh Jethanandani
- RE: BFD stability follow-up from IETF-91 Gregory Mirsky
- Re: BFD stability follow-up from IETF-91 MALLIK MUDIGONDA (mmudigon)
- Re: BFD stability follow-up from IETF-91 MALLIK MUDIGONDA (mmudigon)
- RE: BFD stability follow-up from IETF-91 Santosh P K
- RE: BFD stability follow-up from IETF-91 Nobo Akiya (nobo)
- Re: BFD stability follow-up from IETF-91 Manav Bhatia
- RE: BFD stability follow-up from IETF-91 Nobo Akiya (nobo)
- Re: BFD stability follow-up from IETF-91 Jeffrey Haas
- RE: BFD stability follow-up from IETF-91 Santosh P K
- Re: BFD stability follow-up from IETF-91 Manav Bhatia
- RE: BFD stability follow-up from IETF-91 Gregory Mirsky
- RE: BFD stability follow-up from IETF-91 Gregory Mirsky
- RE: BFD stability follow-up from IETF-91 Gregory Mirsky
- Re: BFD stability follow-up from IETF-91 Manav Bhatia
- Re: BFD stability follow-up from IETF-91 Sam K. Aldrin
- Re: BFD stability follow-up from IETF-91 Manav Bhatia
- RE: BFD stability follow-up from IETF-91 Gregory Mirsky
- Re: BFD stability follow-up from IETF-91 Manav Bhatia
- Re: BFD stability follow-up from IETF-91 Sam K. Aldrin
- Re: BFD stability follow-up from IETF-91 Manav Bhatia
- Re: BFD stability follow-up from IETF-91 Manav Bhatia
- Re: BFD stability follow-up from IETF-91 Sam K. Aldrin
- RE: BFD stability follow-up from IETF-91 Gregory Mirsky
- RE: BFD stability follow-up from IETF-91 Gregory Mirsky
- RE: BFD stability follow-up from IETF-91 Gregory Mirsky
- Re: BFD stability follow-up from IETF-91 Mahesh Jethanandani
- Re: BFD stability follow-up from IETF-91 Manav Bhatia
- Re: BFD stability follow-up from IETF-91 MALLIK MUDIGONDA (mmudigon)
- Re: BFD stability follow-up from IETF-91 Marc Binderberger
- Re: BFD stability follow-up from IETF-91 Manav Bhatia
- Re: BFD stability follow-up from IETF-91 Marc Binderberger
- Re: BFD stability follow-up from IETF-91 Marc Binderberger
- Re: BFD stability follow-up from IETF-91 Marc Binderberger
- RE: BFD stability follow-up from IETF-91 Gregory Mirsky
- Re: BFD stability follow-up from IETF-91 Manav Bhatia
- RE: BFD stability follow-up from IETF-91 Gregory Mirsky
- RE: BFD stability follow-up from IETF-91 Santosh P K
- Re: BFD stability follow-up from IETF-91 Manav Bhatia
- RE: BFD stability follow-up from IETF-91 Gregory Mirsky
- Re: BFD stability follow-up from IETF-91 Manav Bhatia
- Re: BFD stability follow-up from IETF-91 MALLIK MUDIGONDA (mmudigon)
- RE: BFD stability follow-up from IETF-91 Gregory Mirsky
- RE: BFD stability follow-up from IETF-91 Gregory Mirsky
- Re: BFD stability follow-up from IETF-91 Sam Aldrin
- RE: BFD stability follow-up from IETF-91 Gregory Mirsky
- Re: BFD stability follow-up from IETF-91 Mahesh Jethanandani
- Re: BFD stability follow-up from IETF-91 Marc Binderberger
- Re: BFD stability follow-up from IETF-91 MALLIK MUDIGONDA (mmudigon)
- Re: BFD stability follow-up from IETF-91 Manav Bhatia
- Re: BFD stability follow-up from IETF-91 Marc Binderberger
- TWAMP analysis for assisting BFD debuggin (was Re… Jeffrey Haas
- RE: TWAMP analysis for assisting BFD debuggin (wa… Gregory Mirsky
- Re: TWAMP analysis for assisting BFD debuggin (wa… Mahesh Jethanandani
- RE: TWAMP analysis for assisting BFD debuggin (wa… Gregory Mirsky
- Re: TWAMP analysis for assisting BFD debuggin (wa… Jeffrey Haas
- Re: TWAMP analysis for assisting BFD debuggin (wa… Jeffrey Haas