Re: [pim] Publishing draft-ietf-pim-dr-improvement-08

Gyan Mishra <hayabusagsm@gmail.com> Mon, 14 October 2019 21:05 UTC

Return-Path: <hayabusagsm@gmail.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A6BFE120045; Mon, 14 Oct 2019 14:05:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 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, URIBL_BLOCKED=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 ADfjCwz2UQ_k; Mon, 14 Oct 2019 14:05:19 -0700 (PDT)
Received: from mail-qk1-x72d.google.com (mail-qk1-x72d.google.com [IPv6:2607:f8b0:4864:20::72d]) (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 ED6CA12003E; Mon, 14 Oct 2019 14:05:18 -0700 (PDT)
Received: by mail-qk1-x72d.google.com with SMTP id y144so17164090qkb.7; Mon, 14 Oct 2019 14:05:18 -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=SJrNhIEH8xG918wemDksvJ4V9zgEeqa3gbuCZnxsGdM=; b=iCYHCAKjYR7l5f7FTPbEtCmxRof3zOFnRHq7wBonNLMu0CzGSrRukNgzr6O0PWBFFX zYQUxhfMa+mHCdT9WL4tvog/pPyzHgY92GAt7Mh63KbFzSRQ4yM47O92AhM7CAuYi7ll fNAVgeGPF9C9B6m32OpJup68NpACy9R8ZZk+b0khnT9kysS++sjo+RH/9PIL7UoWuN8E GPlK1EtWXB4uge82o8hWsvyyFbsnXAz5l5B1+WO1QnG+VbXJtxs9UNCy+gQyEdlaETSA 9n12x9HZxsgHSWA2Q08liGZn0LY0PT7RrZtliAxzOV8E1RVQgYFhl2sKs+kxh9Zj+F6a zcXA==
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=SJrNhIEH8xG918wemDksvJ4V9zgEeqa3gbuCZnxsGdM=; b=OvaNqNGo4R0uQeg23KwB18F4ZuyQi1bkXdXEp6dBTyx58k88752jk8XDUZQvFclpnX A/z39gbEekrElKSnLGNf+JhxS65GDAL0IMq9wwjUaA0tR00BxA+gKfZI/y/CpG4/waS1 UimSWDMd9WbEasu332xnjJlGCHuKvgqFfjiELWLN1ucKZkr6UKT8nc5ADwnWSTH+ngSP Jd/wd2mQ2kjvfO8a9SaQfM6b2a7F7jhVHz8x9yWc9ACzO/x0tLQRJsopikRsramS14RR +NFuFqilaQ95sB/h6bMk9MUR9qd9DOMWHkE+Y/8GtVQA3N7Ab9gX1A6QhTnzpUH0/G+C 9UfQ==
X-Gm-Message-State: APjAAAUiVQTWvVU+DDXnboKo/PCdUw5nHJqdVtORlQt0J27BUupVG/24 8Xm7XXifUBUEOIP5djXfWMm45PJoTzs=
X-Google-Smtp-Source: APXvYqzcfEDLKC5IXc7XjVMqEFXVe6WqFxogR63foYrtKfIbMFclm1l61tYX2lm6l6WoGC6BJx9h4A==
X-Received: by 2002:a05:620a:12c4:: with SMTP id e4mr31166563qkl.336.1571087117402; Mon, 14 Oct 2019 14:05:17 -0700 (PDT)
Received: from [192.168.1.213] (pool-72-83-194-140.washdc.fios.verizon.net. [72.83.194.140]) by smtp.gmail.com with ESMTPSA id q5sm11818788qte.38.2019.10.14.14.05.16 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 14 Oct 2019 14:05:16 -0700 (PDT)
From: Gyan Mishra <hayabusagsm@gmail.com>
X-Google-Original-From: Gyan Mishra <hayabusaGSM@gmail.com>
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (1.0)
X-Mailer: iPhone Mail (16G102)
In-Reply-To: <B1A78E6F-5403-41C4-AC84-56DBD494278E@cisco.com>
Date: Mon, 14 Oct 2019 17:05:16 -0400
Cc: Stig Venaas <stig@venaas.com>, "zhang.zheng" <zhang.zheng@zte.com.cn>, "xu.benchong@zte.com.cn" <xu.benchong@zte.com.cn>, "draft-ietf-pim-dr-improvement@ietf.org" <draft-ietf-pim-dr-improvement@ietf.org>, "pim@ietf.org" <pim@ietf.org>, Greg Mirsky <gregimirsky@gmail.com>
Content-Transfer-Encoding: quoted-printable
Message-Id: <7F5345CC-B4B8-4008-AF7B-EE3CC528523B@gmail.com>
References: <CAHANBtJBk1CDtOnBDmjXPU4x-BZJSs93OYj6b07aAGSggg5mAw@mail.gmail.com> <B1A78E6F-5403-41C4-AC84-56DBD494278E@cisco.com>
To: "Mankamana Mishra (mankamis)" <mankamis@cisco.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/pim/pJOj-Vnt6hQAsmg6tt-pV0mxtus>
Subject: Re: [pim] Publishing draft-ietf-pim-dr-improvement-08
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pim/>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Oct 2019 21:05:21 -0000

Mankamana 

I agree we can move forward with publishing this document and I can work with you on a PIM BFD Draft.

Thank you 

Gyan
Sent from my iPhone

> On Oct 14, 2019, at 4:53 PM, Mankamana Mishra (mankamis) <mankamis@cisco.com> wrote:
> 
> Hi Gyan 
> As working group member I think we should still going ahead with publishing this document . Any subsequent behavior can be covered in independent document . We can work offline on that . 
> 
> Sent from my iPhone
> 
>> On Oct 14, 2019, at 13:38, Stig Venaas <stig@venaas.com> wrote:
>> 
>> Hi
>> 
>> Gyan, are you OK with this draft being published as is, or do you
>> think there are any issues that need to be addressed?
>> 
>> Regarding BFD, it might be worth having a document specifically
>> discussing how BFD may be used with pim. There are many
>> implementations using BFD with pim, but I don't think we have any
>> documents explaining exactly how that is done, except for
>> draft-ietf-pim-bfd-p2mp-use-case, but it doesn't go into detail on the
>> pim behavior, and it is discussed in the context of p2mp BFD.
>> 
>> Regards,
>> Stig