Re: PIM BFD RFCOGyan,

Gyan Mishra <hayabusagsm@gmail.com> Sat, 19 October 2019 02:26 UTC

Return-Path: <hayabusagsm@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 53C95120804 for <rtg-bfd@ietfa.amsl.com>; Fri, 18 Oct 2019 19:26:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham 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 dCZWNZQ3y6-K for <rtg-bfd@ietfa.amsl.com>; Fri, 18 Oct 2019 19:26:37 -0700 (PDT)
Received: from mail-qt1-x82d.google.com (mail-qt1-x82d.google.com [IPv6:2607:f8b0:4864:20::82d]) (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 8AC40120271 for <rtg-bfd@ietf.org>; Fri, 18 Oct 2019 19:26:37 -0700 (PDT)
Received: by mail-qt1-x82d.google.com with SMTP id 3so12008769qta.1 for <rtg-bfd@ietf.org>; Fri, 18 Oct 2019 19:26:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:mime-version:subject:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=85QVH4Ep7QLSycJU3RmOh9fgSAk3bILZxhbNINV2B8U=; b=Qtjg+aHVBDk0H7jg0ZL56bBkQoFtv59VZ5qvkCWC6VznmYCHCCvKbbCw3knHsJi4yD PE2gce7R+G9Tm/PT8ZzniJDesH6T/RtU8LNjI5n4aTl3eYF3SaobmcrMz1OJeGP7E6fp 1pCQZFitbHHGjJBGXTQuTmIn88b28qJEmWpynTaUaB1+3mC5ikzptD30OucmZ0grH/fg 5/1EKb4wbIt5GMRyGqF0Nang0TRkPncaaOpd2Du1VWtKSPaf8MP80bRARrlNOj703VOt 4rspjrCw15/iKo+/EEXN2Z9coiUWMXagOOtcCt7R94mGg9jxKG3X3XNs4bQ7JGcIlHj8 rnHg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:mime-version:subject:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=85QVH4Ep7QLSycJU3RmOh9fgSAk3bILZxhbNINV2B8U=; b=RlKLFnPgNs8kol/jcNRdKS6bVltfHD0xwAsTDsZGrv8C3qfRrOBVdmmgorkEkHz1qi Ai0xwR1fFtcIrc3rFKVzjGtZfMV63CxRLGp06LxeeA3WFkiMpdGHtRCQH7FJLcyBI2WN Y2bEnVpqP75VaDbWpDH5uV4DCufpfNOw9JSoS3JZM2xF6OeNrH6CsJwh9tOeP/Q7+ZuJ iZF2DhGWXKcYl3RcGS1QasW9bj/n8FrRs4IxYSzhbQnsxn337iKnjAiBWCf9I/sSb1Px L8nfdC3F5bPFdI9YxewkL31D8pprvBvI1Fgiy4Iwdh/u85urH0j1QllmkqCIstdsNecp UscQ==
X-Gm-Message-State: APjAAAWG2lm7gaIqgcNltWFwUeKXnyTQHj7oyCi/5TMdV2qldyuKmZ5B XQxwevMIxD6oNyrSHZJdG5U2bOKp
X-Google-Smtp-Source: APXvYqzNOF7+8TWcVyOrKsp93YFcK8Kqv8oRhoFLwFltbZv9VbaI1z7XF2Or11kd0BgmhuIlptD6MA==
X-Received: by 2002:ac8:21b5:: with SMTP id 50mr13264579qty.60.1571451995666; Fri, 18 Oct 2019 19:26:35 -0700 (PDT)
Received: from ?IPv6:2600:1003:b108:7d8c:e817:ff92:1312:e420? ([2600:1003:b108:7d8c:e817:ff92:1312:e420]) by smtp.gmail.com with ESMTPSA id u132sm3962708qka.50.2019.10.18.19.26.33 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 18 Oct 2019 19:26:34 -0700 (PDT)
From: Gyan Mishra <hayabusagsm@gmail.com>
X-Google-Original-From: Gyan Mishra <hayabusaGSM@gmail.com>
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (1.0)
Subject: Re: PIM BFD RFCOGyan,
X-Mailer: iPhone Mail (16G102)
In-Reply-To: <20191018164320.GA23366@pfrc.org>
Date: Fri, 18 Oct 2019 22:26:32 -0400
Cc: Greg Mirsky <gregimirsky@gmail.com>, rtg-bfd WG <rtg-bfd@ietf.org>, mankamis@cisco.com, xu.benchong@zte.com.cn
Content-Transfer-Encoding: quoted-printable
Message-Id: <A434B296-131C-442D-8591-3BDF41C75614@gmail.com>
References: <37FED5C8-F400-4C72-B72E-0552AD398895@gmail.com> <F4C0E27E-A90D-450D-99F1-FD985E9639D8@gmail.com> <CA+RyBmXZYTaZWQf0VLBTPKM+ZXEvWEOucGHUeQs9pEb5E3shGg@mail.gmail.com> <F8DFF05F-AB75-42B1-8112-7B5E00A86A18@gmail.com> <20191018164320.GA23366@pfrc.org>
To: Jeffrey Haas <jhaas@pfrc.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-bfd/MIshtaExOd8JzwFq1xunKqwFh_k>
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, 19 Oct 2019 02:26:39 -0000

Thank you 

Thank you for clarification on which WG should initiate the draft.

I will work with the PIM WG and engage BFD WG as necessary during Last Call.

Gyan

Sent from my iPhone

> On Oct 18, 2019, at 12:43 PM, Jeffrey Haas <jhaas@pfrc.org> wrote:
> 
> Gyan,
> 
>> On Wed, Oct 16, 2019 at 12:10:25AM -0400, Gyan Mishra wrote:
>> https://tools.ietf.org/html/draft-ietf-pim-drlb-11
>> 
>> 
>> So the BFD PIM Draft would register the PIM protocol and in asynchronous mode with echo disabled we can achieve sub millisecond detection time and convergence during failover.
>> 
>> So I do think we need a PIM BFD Draft. 
>> 
>> Since this falls between multiple WG but since BFD related this would be under the BFD WG.
> 
> Generally, when we're talking about whether a draft that utilizes BFD
> belongs in BFD or not, the deciding criteria is usually whether there's
> changes to the BFD protocol itself.
> 
> I believe in these cases we'd be making use of existing p2mp BFD procedures
> rather than extending them.  In that case, we'd normally suggest the work
> live in the related protocol Working Group.
> 
> Part of BFD's charter is to help review uses of BFD in such protocols, so
> even if the work was happening in the related multicast working groups, the
> chairs of those groups are welcome to request simultaneous review in BFD
> during last call.
> 
> -- Jeff