Re: I-D Action: draft-ashesh-bfd-stability-02.txt

Santosh P K <santoshpk@juniper.net> Sun, 03 May 2015 12:58 UTC

Return-Path: <santoshpk@juniper.net>
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 EC96B1A1A22 for <rtg-bfd@ietfa.amsl.com>; Sun, 3 May 2015 05:58:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_HELO_PASS=-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 TBtxaAL-Ls3c for <rtg-bfd@ietfa.amsl.com>; Sun, 3 May 2015 05:58:15 -0700 (PDT)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1bon0774.outbound.protection.outlook.com [IPv6:2a01:111:f400:fc10::1:774]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 607491A1A20 for <rtg-bfd@ietf.org>; Sun, 3 May 2015 05:58:15 -0700 (PDT)
Received: from SN1PR0501MB1760.namprd05.prod.outlook.com (25.163.130.27) by SN1PR0501MB1725.namprd05.prod.outlook.com (25.163.130.16) with Microsoft SMTP Server (TLS) id 15.1.154.19; Sun, 3 May 2015 12:57:59 +0000
Received: from SN1PR0501MB1760.namprd05.prod.outlook.com (25.163.130.27) by SN1PR0501MB1760.namprd05.prod.outlook.com (25.163.130.27) with Microsoft SMTP Server (TLS) id 15.1.154.19; Sun, 3 May 2015 12:57:58 +0000
Received: from SN1PR0501MB1760.namprd05.prod.outlook.com ([25.163.130.27]) by SN1PR0501MB1760.namprd05.prod.outlook.com ([25.163.130.27]) with mapi id 15.01.0154.018; Sun, 3 May 2015 12:57:58 +0000
From: Santosh P K <santoshpk@juniper.net>
To: "draft-ashesh-bfd-stability@tools.ietf.org" <draft-ashesh-bfd-stability@tools.ietf.org>, Marc Binderberger <marc@sniff.de>
Subject: Re: I-D Action: draft-ashesh-bfd-stability-02.txt
Thread-Topic: I-D Action: draft-ashesh-bfd-stability-02.txt
Thread-Index: AQHQhUSTteRhSK7eN063ujc/mRWFTZ1qNwXE
Date: Sun, 03 May 2015 12:57:58 +0000
Message-ID: <auq7fqp1p3rs8f3muegtt0v1.1430657873272@email.android.com>
References: <20150423175850.1715.93626.idtracker@ietfa.amsl.com>, <20150502185745786713.426ac3a2@sniff.de>
In-Reply-To: <20150502185745786713.426ac3a2@sniff.de>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: tools.ietf.org; dkim=none (message not signed) header.d=none;
x-originating-ip: [1.39.62.132]
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:; SRVR:SN1PR0501MB1760; UriScan:; BCL:0; PCL:0; RULEID:; SRVR:SN1PR0501MB1725;
x-microsoft-antispam-prvs: <SN1PR0501MB1760A0063BAD231656029B94B3D30@SN1PR0501MB1760.namprd05.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(5005006)(3002001); SRVR:SN1PR0501MB1760; BCL:0; PCL:0; RULEID:; SRVR:SN1PR0501MB1760;
x-forefront-prvs: 056544FBEE
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(377454003)(377424004)(24454002)(51704005)(106116001)(92566002)(230783001)(19617315012)(63666004)(95246002)(16236675004)(19625215002)(33646002)(62966003)(77156002)(5001920100001)(5001770100001)(86362001)(46102003)(122556002)(66066001)(40100003)(99286002)(5001960100002)(2501003)(54356999)(2656002)(50986999)(19580405001)(15975445007)(19580395003)(87936001)(102836002)(2950100001)(2900100001); DIR:OUT; SFP:1102; SCL:1; SRVR:SN1PR0501MB1760; H:SN1PR0501MB1760.namprd05.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en;
Content-Type: multipart/alternative; boundary="_000_auq7fqp1p3rs8f3muegtt0v11430657873272emailandroidcom_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 03 May 2015 12:57:58.2179 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SN1PR0501MB1760
X-OriginatorOrg: juniper.net
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtg-bfd/6l4-RVM9dwJ7P0IGcFkhuSJ50tQ>
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: Sun, 03 May 2015 12:58:18 -0000

Marc,
    Thanks for your comments. Draft was expiring and hence we updated draft without any changes. This week we will upload document with changes we have discussed.

Thanks
Santosh P K



sent from handheld device.
On May 3, 2015 7:27 AM, Marc Binderberger <marc@sniff.de> wrote:
Hello authors of BFD stability,

the diff says not much has changes since v01 (?!).
Anyway, let me provide some feedback :-)


"Sequence Number"

- what happens when the counter wraps? Are you okay to start at zero again -
but zero has a special meaning. Wrapping back to "1"?  The draft should
define what comes after 2^32 - 1.

- would is make sense to have the mechanism always running, including
Down/Init packets? The Down-Init-Up can happen rapidly, what about deugging
packet loss during this sequence?


"Security Consideration"

- I don't think that saying "well, it's either us or crypto-authentication"
is a good statement for IETF. Especially with the effort to make
authentication more realistic for BFD (like draft-mahesh-bfd-authentication)
it's not forward-looking. You could at least outline how every existing
authentication could be "cloned" to have the new fields you introduce, to
allow for both packet loss counting and authentication.


Kevin asked in his email:

> 2) Can you specify that these features will be optional for an
implementation
> and some method should be provided to turn this capability off if needed

I support this idea. There are implementations that drop BFD packets with the
A bit set (as no authentication is supported in the implementation). I'm also
not sure how quickly hardware-based BFD implementations can be upgraded. So
for backward compatibility it would be good to be able to turn it off.


Regards, Marc



On Thu, 23 Apr 2015 10:58:50 -0700, internet-drafts@ietf.org wrote:
>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
>
>
>         Title           : BFD Stability
>         Authors         : Ashesh Mishra
>                           Mahesh Jethanandani
>                           Ankur Saxena
>                           Santosh Pallagatti
>                           Mach Chen
>        Filename        : draft-ashesh-bfd-stability-02.txt
>        Pages           : 5
>        Date            : 2015-04-23
>
> Abstract:
>    This document describes extensions to the Bidirectional Forwarding
>    Detection (BFD) protocol to measure BFD stability.  Specifically, it
>    describes a mechanism for detection of BFD frame loss.
>
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ashesh-bfd-stability/
>
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-ashesh-bfd-stability-02
>
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=draft-ashesh-bfd-stability-02
>
>
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/i-d-announce
> Internet-Draft directories: http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>