RE: BFD stability follow-up from IETF-91

"Fan, Peng" <fanpeng@chinamobile.com> Fri, 28 November 2014 10:51 UTC

Return-Path: <fanpeng@chinamobile.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 ED69D1A1B07 for <rtg-bfd@ietfa.amsl.com>; Fri, 28 Nov 2014 02:51:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.21
X-Spam-Level: **
X-Spam-Status: No, score=2.21 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, RELAY_IS_221=2.222, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=no
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 BYDQkVVwkrnW for <rtg-bfd@ietfa.amsl.com>; Fri, 28 Nov 2014 02:51:20 -0800 (PST)
Received: from cmccmta1.chinamobile.com (cmccmta1.chinamobile.com [221.176.66.79]) by ietfa.amsl.com (Postfix) with SMTP id A6D901A1B11 for <rtg-bfd@ietf.org>; Fri, 28 Nov 2014 02:51:19 -0800 (PST)
Received: from spf.mail.chinamobile.com (unknown[172.16.121.9]) by rmmx-syy-dmz-app01-12001 (RichMail) with SMTP id 2ee1547853a0d3b-21236; Fri, 28 Nov 2014 18:51:12 +0800 (CST)
X-RM-TRANSID: 2ee1547853a0d3b-21236
X-RM-SPAM-FLAG: 00000000
Received: from cmccPC (unknown[223.69.29.130]) by rmsmtp-syy-appsvr05-12005 (RichMail) with SMTP id 2ee55478539efcd-78c2c; Fri, 28 Nov 2014 18:51:12 +0800 (CST)
X-RM-TRANSID: 2ee55478539efcd-78c2c
From: "Fan, Peng" <fanpeng@chinamobile.com>
To: rtg-bfd@ietf.org
References: <20141126001931.GJ20330@pfrc> <CAG1kdoghcA=xSaXmkr68qduH2t8oC=-ZazoQztj8JK12SazKsw@mail.gmail.com> <20141126005023981392.0c488535@sniff.de> <F73A3CB31E8BE34FA1BBE3C8F0CB2AE28B2D9A97@SZXEMA510-MBX.china.huawei.com> <20141126094242449051.c8abfe39@sniff.de> <F73A3CB31E8BE34FA1BBE3C8F0CB2AE28B2DB0BD@SZXEMA510-MBX.china.huawei.com> <315041E4211CB84E86EF7C25A2AB583D3476B1C0@xmb-rcd-x15.cisco.com>
In-Reply-To: <315041E4211CB84E86EF7C25A2AB583D3476B1C0@xmb-rcd-x15.cisco.com>
Subject: RE: BFD stability follow-up from IETF-91
Date: Fri, 28 Nov 2014 18:50:43 +0800
Message-ID: <007701d00af9$28719050$7954b0f0$@chinamobile.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQI18HhYe6tGWNESNbniYme3DP4jzQHs2X59A36o7WAByV58bgMd6y/MAfpW6v8Clvl7hpsy71Tg
Content-Language: zh-cn
Archived-At: http://mailarchive.ietf.org/arch/msg/rtg-bfd/uLZxcr35j6g5Mm6AEGFxYCV3i1o
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: Fri, 28 Nov 2014 10:51:22 -0000

Hi Jeff, all,

I have been following this stability extension from the beginning, and as an
operator I would like to express that this draft enables the "advanced
feature" we desire for BFD to provide additional useful information that
helps operators understand network issues. A relevant use case is detecting
lossy or "quasi-disconnected" links or member LAG links. An example of such
situation we experienced was a loosely connected fiber link resulting in
continuous, small amount of packet loss. BFD could get the information of
lost BFD frames on such unstable link, and probably report when a target
level is reached, say a certain number of frames are lost over a period or
among a total number of frames.

Best regards,
Peng