RE: ops-dir review of draft-ietf-bfd-rfc5884-clarifications

"Vengada Prasad Govindan (venggovi)" <venggovi@cisco.com> Tue, 13 October 2015 04:30 UTC

Return-Path: <venggovi@cisco.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 312B61B3749; Mon, 12 Oct 2015 21:30:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level:
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 aNCxHBjxnJab; Mon, 12 Oct 2015 21:30:02 -0700 (PDT)
Received: from alln-iport-4.cisco.com (alln-iport-4.cisco.com [173.37.142.91]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2CA0D1B3748; Mon, 12 Oct 2015 21:30:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=11136; q=dns/txt; s=iport; t=1444710603; x=1445920203; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=leNW1bi3kuSeSVnTayECLmhcCkPLYFlvpdNEizqiNpI=; b=CIGGBqSDzRpDgphWOG5euzSYY+Cynk9fnvvhH3vgSyzPokCLUk55OaIH cK2hz3to66frFLhnCmecMiiVq6VsVB465bRUeEwR0Yu1aDUisV+cqVH1m 2HdPJ1HlLmOQ/mKI9cPg+FpqANNT+yXsjM5E9ILFkRdGGRvoXuZ3uEMjT 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0C3AgBgiBxW/5xdJa1dDoJLTVRuBr4KAQ2BWoMTggp/AhyBGjgUAQEBAQEBAYEKhCYBAQEEIwpMDAQCAQgRBAEBKAMCAgIwFAkIAgQBDQUIiCasbZNcAQEBAQEBAQEBAQEBAQEBAQEBAQEBF4Z1g3iBBoUNBgEGgmOBRQWSVYNAAY0SgV+WPoNuAR8BAUKDRD5xhWuBBgEBAQ
X-IronPort-AV: E=Sophos;i="5.17,676,1437436800"; d="scan'208,217";a="196783672"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by alln-iport-4.cisco.com with ESMTP; 13 Oct 2015 04:29:52 +0000
Received: from XCH-ALN-018.cisco.com (xch-aln-018.cisco.com [173.36.7.28]) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id t9D4Tpne004287 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 13 Oct 2015 04:29:51 GMT
Received: from xch-rcd-020.cisco.com (173.37.102.30) by XCH-ALN-018.cisco.com (173.36.7.28) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Mon, 12 Oct 2015 23:29:38 -0500
Received: from xch-rcd-020.cisco.com ([173.37.102.30]) by XCH-RCD-020.cisco.com ([173.37.102.30]) with mapi id 15.00.1104.000; Mon, 12 Oct 2015 23:29:38 -0500
From: "Vengada Prasad Govindan (venggovi)" <venggovi@cisco.com>
To: "Bradner, Scott" <sob@harvard.edu>, "ops-dir@ietf.org" <ops-dir@ietf.org>, "draft-ietf-bfd-rfc5884-clarifications.all@ietf.org" <draft-ietf-bfd-rfc5884-clarifications.all@ietf.org>
Subject: RE: ops-dir review of draft-ietf-bfd-rfc5884-clarifications
Thread-Topic: ops-dir review of draft-ietf-bfd-rfc5884-clarifications
Thread-Index: AQHRBPd9Wie+K0/swkOFtgAlhD4Y+p5o1GOw
Date: Tue, 13 Oct 2015 04:29:38 +0000
Message-ID: <b30ef1e555e446cca7e08255cf534586@XCH-RCD-020.cisco.com>
References: <478C7FCA-AC58-40FF-AFB4-0059AE737A29@harvard.edu>
In-Reply-To: <478C7FCA-AC58-40FF-AFB4-0059AE737A29@harvard.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.65.43.97]
Content-Type: multipart/alternative; boundary="_000_b30ef1e555e446cca7e08255cf534586XCHRCD020ciscocom_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtg-bfd/d5xdIjmjFuCQXtNi6QGnV8Di78s>
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: <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: Tue, 13 Oct 2015 04:30:04 -0000

Hello Scott/ all,

Thanks for your comment, do you think the proposed text below makes better sense (additions highlighted in green):



      The BFD session MAY be removed in the egress LSR if the BFD

      session transitions from UP to DOWN.  This can either be done

      immediately after the BFD session transitions from UP to DOWN

     or after the  expiry of a configurable timer started after the BFD

    session state  transitions from UP to DOWN at the egress LSR.

I can post a new revision reflecting this comment if you are fine with the proposed text.

Thanks

Prasad



-----Original Message-----
From: Bradner, Scott [mailto:sob@harvard.edu]
Sent: Monday, October 12, 2015 7:39 PM
To: ops-dir@ietf.org; draft-ietf-bfd-rfc5884-clarifications.all@ietf.org
Subject: ops-dir review of draft-ietf-bfd-rfc5884-clarifications



I have done a OPS-DIR review of "Clarifications to RFC 5884” <draft-ietf-bfd-rfc5884-clarifications-03.txt>



summary - ready for publication



This document clarifies how best to operate multiple BFD (Bidirectional Forwarding Detection) sessions in MPLS environments.

Any document that purports to clarify operational procedures is, by definition, a good thing when it comes to operational impact, assuming the document is clear and makes sense.  This document is clear and makes sense.



One suggestion though.

The first observation in Section 2.3 says:



      The BFD session MAY be removed in the egress LSR if the BFD

      session transitions from UP to DOWN.  This can be done after the

      expiry of a configurable timer started after the BFD session state

      transitions from UP to DOWN at the egress LSR.



It might be helpful to specifically say what the aim of using such a timer is.  My guess is that the timer is used to introduce hysteresis to reduce flapping - but it would nice to say one way or the other



Scott