Re: [OSPF] OSPF GR and BFD operability

Anil Raj <anilraj85@gmail.com> Tue, 25 August 2015 15:51 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 CF5E81B3565 for <ospf@ietfa.amsl.com>; Tue, 25 Aug 2015 08:51:02 -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 PGsyTQM6RgiR for <ospf@ietfa.amsl.com>; Tue, 25 Aug 2015 08:51:01 -0700 (PDT)
Received: from mail-qk0-x233.google.com (mail-qk0-x233.google.com [IPv6:2607:f8b0:400d:c09::233]) (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 208B81B3562 for <ospf@ietf.org>; Tue, 25 Aug 2015 08:51:01 -0700 (PDT)
Received: by qkda128 with SMTP id a128so53002438qkd.3 for <ospf@ietf.org>; Tue, 25 Aug 2015 08:51:00 -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=l+cMMnW/nbf7NjsWvzUxDvCwbkg/5VGq2m0XwAKSChA=; b=EDX/W1z+9MOYwEFPZbAfqSGrNeG7eI261wsnSFIcymHju4zI/uBqSa6O6YX5K/4oqw jc7Ugc5zID9x/1Y5cbwOvHDxxhNnbE8q0eH/yybTJxcN0fMKr6aFKp+owqmLwar+v84S H9kFLloPQTSloZCUQsNpVaqgp5fVY8t7DF5b3Q1I/y+NlZf/g9jS52kKVnCyle5HMaFp jQqn6/j6Wa76RM4PN/dMCyrBvKC9YSDGjzxYOlpyEQHgfWK1jYS4RUBoB9tmAjt9dmhN iEXNyjQ1p0KXkc+RyiT0bxKzsZelT/uxbNo8RJ9JB/uGSHahdJdXAy3aPY47Ixm7E5iT 2CAA==
MIME-Version: 1.0
X-Received: by 10.55.217.23 with SMTP id u23mr65483669qki.58.1440517860452; Tue, 25 Aug 2015 08:51:00 -0700 (PDT)
Received: by 10.140.40.106 with HTTP; Tue, 25 Aug 2015 08:51:00 -0700 (PDT)
In-Reply-To: <F3ADE4747C9E124B89F0ED2180CC814F5956187C@xmb-aln-x02.cisco.com>
References: <CAPj3AOpO+o2hBp3J+mPXpwWiho5fMxE97b1SKsHigRfTQSGzjw@mail.gmail.com> <D201F336.2C912%acee@cisco.com> <F3ADE4747C9E124B89F0ED2180CC814F5956187C@xmb-aln-x02.cisco.com>
Date: Tue, 25 Aug 2015 21:21:00 +0530
Message-ID: <CAPj3AOok5_dY9mq=95aLji52-MbkwCrCAQisR4T4XipO5JpDfw@mail.gmail.com>
From: Anil Raj <anilraj85@gmail.com>
To: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>
Content-Type: multipart/alternative; boundary=001a1147a08a5d706f051e24b3c1
Archived-At: <http://mailarchive.ietf.org/arch/msg/ospf/slOG98MCqo7Tz2qRVNHudCnQdCw>
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:51:03 -0000

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 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
>
>