Re: [OSPF] OSPF GR and BFD operability

Anil Raj <anilraj85@gmail.com> Wed, 26 August 2015 03:07 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 C98081A877F for <ospf@ietfa.amsl.com>; Tue, 25 Aug 2015 20:07:58 -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 V_iei2BMDGFx for <ospf@ietfa.amsl.com>; Tue, 25 Aug 2015 20:07:57 -0700 (PDT)
Received: from mail-qg0-x229.google.com (mail-qg0-x229.google.com [IPv6:2607:f8b0:400d:c04::229]) (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 7FA3B1A8741 for <ospf@ietf.org>; Tue, 25 Aug 2015 20:07:56 -0700 (PDT)
Received: by qgeb6 with SMTP id b6so118962623qge.3 for <ospf@ietf.org>; Tue, 25 Aug 2015 20:07:55 -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=Fx6tzcVJ+3nXHE02owC4meh4TYQXzrVUR3pPpRCsTGI=; b=R22mjbixupsBwnaaobRoHiGaQDIxe2cnKBJB76gOFfVsFVOj100gnio0DlX/w+cT8V aDUvf+d2jDzc4Bhzrm3GZrT9NOqreQhL1Yqe4NTVRkqtUEckhV7dhj13FuzOBGJLNxDK QuYGPzfjDaYaH1hEv85Srlhy30X9+WHJQhoAyBNkX5Y/9PvgpQ/MTarDwMEYVA2Xgwfi 81eGIHRJZ6LCHw0TYY6QELWDEVX0J1WTr8IfSXO//zY0nxJ+Su9uNmNZZnECWAH4PGSo kEbKavOwFwF2ju19mRYGoAU6f0G3Tfjw2K4bfdLnp0uK3u+9ITivfsC/W7KLoKDucWnj 7w9A==
MIME-Version: 1.0
X-Received: by 10.140.165.198 with SMTP id l189mr71871539qhl.85.1440558475815; Tue, 25 Aug 2015 20:07:55 -0700 (PDT)
Received: by 10.140.40.106 with HTTP; Tue, 25 Aug 2015 20:07:55 -0700 (PDT)
In-Reply-To: <D20212C1.2C975%acee@cisco.com>
References: <CAPj3AOpO+o2hBp3J+mPXpwWiho5fMxE97b1SKsHigRfTQSGzjw@mail.gmail.com> <D201F336.2C912%acee@cisco.com> <F3ADE4747C9E124B89F0ED2180CC814F5956187C@xmb-aln-x02.cisco.com> <CAPj3AOok5_dY9mq=95aLji52-MbkwCrCAQisR4T4XipO5JpDfw@mail.gmail.com> <F3ADE4747C9E124B89F0ED2180CC814F595619CA@xmb-aln-x02.cisco.com> <D20212C1.2C975%acee@cisco.com>
Date: Wed, 26 Aug 2015 08:37:55 +0530
Message-ID: <CAPj3AOq+UAJH9muA87SuEbDcGKKA8wFS8KMpu0Xmjfxd2z9MUw@mail.gmail.com>
From: Anil Raj <anilraj85@gmail.com>
To: "Acee Lindem (acee)" <acee@cisco.com>
Content-Type: multipart/alternative; boundary="001a1134ee6e3aafd2051e2e28ae"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ospf/c7oBGYHTdN4h6p-X8y-_wJgZpoI>
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: Wed, 26 Aug 2015 03:07:59 -0000

I got it. Thanks Les for the details and reference.

Regards,
Anil

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

> I agree. Thanks Les for the reference to RFC 5882.
>
> Thanks,
> Acee
>
> From: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>
> Date: Tuesday, August 25, 2015 at 12:29 PM
> To: Anil Raj <anilraj85@gmail.com>
> Cc: Acee Lindem <acee@cisco.com>, OSPF WG List <ospf@ietf.org>
> Subject: RE: [OSPF] OSPF GR and BFD operability
>
> Anil –
>
>
>
> IF BFD does NOT share fate w the Control plane then what you say is true.
>
>
>
> If BFD shares fate w the control plane then the behavior depends on the
> neighbor knowing that a restart is in progress. If neighbor knows this then
> the BFD down event can be ignored w minimal risk – otherwise you need to
> treat it as a real failure.
>
>
>
>    Les
>
>
>
>
>
> *From:* Anil Raj [mailto:anilraj85@gmail.com <anilraj85@gmail.com>]
> *Sent:* Tuesday, August 25, 2015 8:51 AM
> *To:* Les Ginsberg (ginsberg)
> *Cc:* Acee Lindem (acee); OSPF WG List
> *Subject:* Re: [OSPF] OSPF GR and BFD operability
>
>
>
> Thanks Acess, Les.
>
>
>
> So ideally it is recommended to tear down OSPF adjacency and signal
> topology change, and thus honor BFD notification in this case.
>
>
>
> Regards,
>
> Anil
>
>
>
> On Tue, Aug 25, 2015 at 8:57 PM, Les Ginsberg (ginsberg) <
> ginsberg@cisco.com> wrote:
>
> https://www.rfc-editor.org/rfc/rfc5882.txt Section 4.3
> <https://www.rfc-editor.org/rfc/rfc5882.txt%20Section%204.3> is relevant
> here.
>
>
>
>    Les
>
>
>
>
>
> *From:* OSPF [mailto:ospf-bounces@ietf.org] *On Behalf Of *Acee Lindem
> (acee)
> *Sent:* Tuesday, August 25, 2015 7:54 AM
> *To:* Anil Raj; OSPF WG List
> *Subject:* Re: [OSPF] OSPF GR and BFD operability
>
>
>
> 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
>
>
>
>