IETF Logo Mail Archive

Re: [OSPF] OSPF GR and BFD operability

"Acee Lindem (acee)" <acee@cisco.com> Tue, 25 August 2015 14:53 UTC

Return-Path: <acee@cisco.com>
X-Original-To: ospf@ietfa.amsl.com
Delivered-To: ospf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9C1D61B2E67 for <ospf@ietfa.amsl.com>; Tue, 25 Aug 2015 07:53:51 -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 xc8uGsETXqlk for <ospf@ietfa.amsl.com>; Tue, 25 Aug 2015 07:53:50 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 974E31B3031 for <ospf@ietf.org>; Tue, 25 Aug 2015 07:53:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5101; q=dns/txt; s=iport; t=1440514429; x=1441724029; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=IvShYgdBGNqsh7PIuoqwMLQRZLa14k9Ms3hH6ISVjc0=; b=XfnClwC0HVUyvAYtiyWKKtO9FhycjN2vqK4bRPZzu0NafuoAODrN2uWU LwoWJ23hBRrAT2Ni+tc/wC2oqKywfqu8nt5i/Dkscq+Vb7dHxkVxiUjOT pHDS4zHih/KfsmI0v0gUhQI4JfnVcrAoQaiADycMzEbw+DDhgdUot1mlw s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CgAgCrgNxV/4MNJK1dgk5NgT0Ggx+6ZgEJh3ICHIEWOBQBAQEBAQEBgQqEIwEBAQQjZgIBCAQNAwECKAMCAgIfERQJCAIEARKIGQMSsmmPWw2FLgEBAQEBAQEBAgEBAQEBAQEBGotXgk+BYEoYgmmBQwWVNwGLBIFtkxqHOiaDfnGBSIEEAQEB
X-IronPort-AV: E=Sophos; i="5.15,746,1432598400"; d="scan'208,217"; a="27155893"
Received: from alln-core-1.cisco.com ([173.36.13.131]) by rcdn-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 25 Aug 2015 14:53:48 +0000
Received: from XCH-RCD-019.cisco.com (xch-rcd-019.cisco.com [173.37.102.29]) by alln-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id t7PErmfR027795 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 25 Aug 2015 14:53:48 GMT
Received: from xch-rcd-019.cisco.com (173.37.102.29) by XCH-RCD-019.cisco.com (173.37.102.29) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Tue, 25 Aug 2015 09:53:47 -0500
Received: from xhc-rcd-x06.cisco.com (173.37.183.80) by xch-rcd-019.cisco.com (173.37.102.29) with Microsoft SMTP Server (TLS) id 15.0.1104.5 via Frontend Transport; Tue, 25 Aug 2015 09:53:47 -0500
Received: from xmb-aln-x06.cisco.com ([169.254.1.223]) by xhc-rcd-x06.cisco.com ([173.37.183.80]) with mapi id 14.03.0248.002; Tue, 25 Aug 2015 09:53:47 -0500
From: "Acee Lindem (acee)" <acee@cisco.com>
To: Anil Raj <anilraj85@gmail.com>, OSPF WG List <ospf@ietf.org>
Thread-Topic: [OSPF] OSPF GR and BFD operability
Thread-Index: AQHQ30EdJhQjUSmLyUGmsy+tTypsap4c3f6A
Date: Tue, 25 Aug 2015 14:53:46 +0000
Message-ID: <D201F336.2C912%acee@cisco.com>
References: <CAPj3AOpO+o2hBp3J+mPXpwWiho5fMxE97b1SKsHigRfTQSGzjw@mail.gmail.com>
In-Reply-To: <CAPj3AOpO+o2hBp3J+mPXpwWiho5fMxE97b1SKsHigRfTQSGzjw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [173.37.102.29]
Content-Type: multipart/alternative; boundary="_000_D201F3362C912aceeciscocom_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ospf/bGIJWvaNHz5WaT1-qiKMfvy7C0s>
Subject: Re: [OSPF] OSPF GR and BFD operability
X-BeenThere: ospf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: The Official IETF OSPG WG Mailing List <ospf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ospf>, <mailto:ospf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ospf/>
List-Post: <mailto:ospf@ietf.org>
List-Help: <mailto:ospf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ospf>, <mailto:ospf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Aug 2015 14:53:51 -0000

Hi Anil,

OSPF and OSPFv3 graceful restart pre-dated BFD so this wasn’t explicitly covered. However, given that the intension is that the data plane is preserved during restart, an implementation could interpret this as a topology change and terminate helper mode as documented in section 3.2 of RFC 3623.
Hope this helps,
Acee



From: OSPF <ospf-bounces@ietf.org<mailto:ospf-bounces@ietf.org>> on behalf of Anil Raj <anilraj85@gmail.com<mailto:anilraj85@gmail.com>>
Date: Tuesday, August 25, 2015 at 10:19 AM
To: OSPF WG List <ospf@ietf.org<mailto:ospf@ietf.org>>
Subject: [OSPF] OSPF GR and BFD operability

Hi,

I need clarification on the behavior when BFD notifies remote inactivity for a OSPF session, when OSPF neighbor is undergoing Graceful restart? OSPF router in helper mode will ideally inactivate the restarting neighbor only after grace period, and if BFD notifies neighbor down to OSPF, should the adjacency be terminated? If not, will it cause a blackhole for the entire grace period if the neighbor is actually down?

Appreciate if you can help here.

Regards,
Anil

v2.23.0 | Report a Bug | By Email