Re: [OSPF] OSPF GR and BFD operability

Anil Raj <anilraj85@gmail.com> Tue, 25 August 2015 15:36 UTC

Return-Path: <anilraj85@gmail.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 06CC81B3571 for <ospf@ietfa.amsl.com>; Tue, 25 Aug 2015 08:36:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.749
X-Spam-Level:
X-Spam-Status: No, score=-1.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] 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 M3DoPfYdd6MA for <ospf@ietfa.amsl.com>; Tue, 25 Aug 2015 08:36:33 -0700 (PDT)
Received: from mail-qg0-x22d.google.com (mail-qg0-x22d.google.com [IPv6:2607:f8b0:400d:c04::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A651C1B3572 for <ospf@ietf.org>; Tue, 25 Aug 2015 08:36:33 -0700 (PDT)
Received: by qgeg42 with SMTP id g42so109021052qge.1 for <ospf@ietf.org>; Tue, 25 Aug 2015 08:36:33 -0700 (PDT)
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=lkF7HfTnNQQkiVdqUrctNDJP74C09PX5awYIgWTGWvU=; b=MqtASIgE7xcX59ZJZvq0kjrwdraLFcpNPSQArQZ11CmC6j6eSyNijTINAwJLJfQIaA yBFrkNJ2NGT2RAZpApQYFgYfYIw1klWNXJRdFwsEVEwl+9RyalnYYmB4gqVeIaOyHbcG VE2gXD+wTyxxJK1O7aDJUbTL2kPK6UpcuGTu8FGPVX9c77ZPXaxl4nFSyOY3T/GcQow6 ZjU+7EJtIF9vsbkVkc6v+k0dYp7biBbC2IFLvktNsBnff69Xd1LgtncIolUz3Ux2ns4I f2KVyh0SRyFMbKE+3nwepZlYP4plslZuRgSoeNWUWHFYKAK0pHZ4xSYLnXGle4c2qB3Z vELQ==
MIME-Version: 1.0
X-Received: by 10.141.23.84 with SMTP id z81mr70554409qhd.50.1440516992871; Tue, 25 Aug 2015 08:36:32 -0700 (PDT)
Received: by 10.140.40.106 with HTTP; Tue, 25 Aug 2015 08:36:32 -0700 (PDT)
In-Reply-To: <D201F336.2C912%acee@cisco.com>
References: <CAPj3AOpO+o2hBp3J+mPXpwWiho5fMxE97b1SKsHigRfTQSGzjw@mail.gmail.com> <D201F336.2C912%acee@cisco.com>
Date: Tue, 25 Aug 2015 21:06:32 +0530
Message-ID: <CAPj3AOqS_SPfCK_Sq_pKvYW_6yjcDq3QEzWHi8W_JR7QTtE-gA@mail.gmail.com>
From: Anil Raj <anilraj85@gmail.com>
To: "Acee Lindem (acee)" <acee@cisco.com>
Content-Type: multipart/alternative; boundary="001a114236d0a7353d051e247f26"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ospf/SKw9DTlssJUJSAoX6rzTZSWnrCU>
Cc: OSPF WG List <ospf@ietf.org>
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 15:36:36 -0000

Thanks Acee for the details.
My concern was also in regards that, in a BFD-less setup during
helper-mode, OSPF hello packets from the neighbor are not honored at all
and is not used as a heartbeat mechanism, and hence waits for the entire
grace period before announcing the peer down. So any BFD implementation
done on software (may be multi-hop peers if applicable), this may still
cause BFD to cause remote inactivity notification, with data plane still
intact.

Regards,
Anil

On Tue, Aug 25, 2015 at 8:23 PM, Acee Lindem (acee) <acee@cisco.com> wrote:

> 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> on behalf of Anil Raj <
> anilraj85@gmail.com>
> Date: Tuesday, August 25, 2015 at 10:19 AM
> To: OSPF WG List <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
>
>