IETF Logo Mail Archive

Re: PIM BFD RFC

Greg Mirsky <gregimirsky@gmail.com> Sat, 12 October 2019 04:07 UTC

Return-Path: <gregimirsky@gmail.com>
X-Original-To: rtg-bfd@ietfa.amsl.com
Delivered-To: rtg-bfd@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D1D4612080D for <rtg-bfd@ietfa.amsl.com>; Fri, 11 Oct 2019 21:07:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.497
X-Spam-Level:
X-Spam-Status: No, score=-1.497 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, SUBJ_ALL_CAPS=0.5, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 qfOYrySs_jtg for <rtg-bfd@ietfa.amsl.com>; Fri, 11 Oct 2019 21:07:16 -0700 (PDT)
Received: from mail-lj1-x243.google.com (mail-lj1-x243.google.com [IPv6:2a00:1450:4864:20::243]) (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 17511120809 for <rtg-bfd@ietf.org>; Fri, 11 Oct 2019 21:07:16 -0700 (PDT)
Received: by mail-lj1-x243.google.com with SMTP id 7so11669065ljw.7 for <rtg-bfd@ietf.org>; Fri, 11 Oct 2019 21:07:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=O4gYF+lfJhAZi6x8hHb8WgeVM+z3IZwoOloJ/eWh63w=; b=o4JXGV6cqF5xupcW9kcb6XzlvrDDG2UPJUPShziNTvJmDracwdKqrQoq179GhSSS9f 3ybTvviaI/Fnaz9z5hnIT/mBm9OIG+W0KzLJuGJYsyYPdie34+UNsKuS9prXEPULrsUz QcyRZ+20hWRHmfK9/s7NYiU+S0D0F6+ZEWA184l3E7ulojCsEumZRdIgBsBSWK9LgFlA eTCgw/tXO2gOJDgBPloN4Ct77Tk9pI0J0BPjo+Rj0eeAdRgqLNQTIk1lFgXuMd4JnnXD wF1FGpTdqLr/foipxJJuMQgXjpafd+gBTwRCJvCFhfpm7oxBYZ1nP5ieHWhz7grai4ND HFfg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=O4gYF+lfJhAZi6x8hHb8WgeVM+z3IZwoOloJ/eWh63w=; b=sNmVJzY8bclNIKcv9BozC1p5AzMXfSYwKuR4xqILWYZvrbUT1fytSyiAWKoOUFLx3E o5xnmXhyk9DwD4MMo9j30cIDalbbyzJTWViK3gY54JEjpz0j2oJTwOwIWMYngDLiP1iB U1XEXI3vF4G3c9OSDhE5cG7+1mHYol1m6e5Ls/0uI15anSQzG0qApixDieJghvRN328I Fivz4IhNRx/XaEFKo1o7PAtSvUq+3P9BRmF4PTd8EhLAgs5L/j/M1qFiVtFnAsJipgFX inGI3XNA/ElWb/acDJ5o10NMrKFKsYVYk4oQw9xTBmKIteGzOCR55TGMK7PXeBxgMBH9 l9zw==
X-Gm-Message-State: APjAAAXrlnFPvApMTmC5zozjgc3fO/65eOrhDQu0PB/X6Pwo0TG7hKQ+ dExG2USLSjCTTZRwQahV76ffUYRhvaCGa59t2HE=
X-Google-Smtp-Source: APXvYqzTwnz/CyQqgNJFvhm1d051ADi/vEr96YdUi0wnX/8PaHfulR2Q6NRUGHyFqSWOfRTI2u+1vWrHq/8gsa3lllA=
X-Received: by 2002:a2e:9b8a:: with SMTP id z10mr11098745lji.66.1570853234227; Fri, 11 Oct 2019 21:07:14 -0700 (PDT)
MIME-Version: 1.0
References: <37FED5C8-F400-4C72-B72E-0552AD398895@gmail.com> <F4C0E27E-A90D-450D-99F1-FD985E9639D8@gmail.com>
In-Reply-To: <F4C0E27E-A90D-450D-99F1-FD985E9639D8@gmail.com>
From: Greg Mirsky <gregimirsky@gmail.com>
Date: Fri, 11 Oct 2019 21:07:03 -0700
Message-ID: <CA+RyBmXZYTaZWQf0VLBTPKM+ZXEvWEOucGHUeQs9pEb5E3shGg@mail.gmail.com>
Subject: Re: PIM BFD RFC
To: Gyan Mishra <hayabusagsm@gmail.com>
Cc: rtg-bfd WG <rtg-bfd@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000053da20594aec543"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-bfd/n1H3mIZGihnZ9mKAukeH7rZt1_g>
X-BeenThere: rtg-bfd@ietf.org
X-Mailman-Version: 2.1.29
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: Sat, 12 Oct 2019 04:07:18 -0000

Hi Gyan,
thank you for your interest in this draft. We've described how RFC 8562 BFD
for Multipoint Networks <https://datatracker.ietf.org/doc/rfc8562/> can be
used to shorten convergence in PIM-SM. The similar scenario discussed in
draft-ietf-bess-mvpn-fast-failover
<https://datatracker.ietf.org/doc/draft-ietf-bess-mvpn-fast-failover/> where
p2mp BFD is used by tails to detect the failure of the head/root or the
multicast tree. If it is required for the head/root to detect a defect of
the multicast tree toward a tail, we'll turn to RFC 8563 BFD for
Multipoint  Active Tails <https://datatracker.ietf.org/doc/rfc8563/> as in
draft-hu-bier-bfd <https://datatracker.ietf.org/doc/draft-hu-bier-bfd/>.
Hope this information would be helpful to you. I always welcome your
questions.

Regards,
Greg

On Fri, Oct 11, 2019 at 7:40 PM Gyan Mishra <hayabusagsm@gmail.com> wrote:

> Greg
>
> I saw your draft on PIM BFD use cases but could not find the RFC on PIM
> BFD.
>
>
> https://tools.ietf.org/id/draft-mirsky-pim-bfd-p2mp-use-case-02.html
>
> Thanks
>
> Gyan
> Verizon Communications
> Cell-301 502-1347
>
>
> Sent from my iPhone
>
> On Oct 11, 2019, at 9:53 PM, Gyan Mishra <hayabusagsm@gmail.com> wrote:
>
>
> BFD WG
>
> Anyone know what the RFC or draft for PIM BFD support.
>
> Thank you
>
> Gyan
> Verizon Communications
>
>
>
> Sent from my iPhone
>
>

v2.23.0 | Report a Bug | By Email