Re: [pim] Publishing draft-ietf-pim-dr-improvement-08
Gyan Mishra <hayabusagsm@gmail.com> Mon, 14 October 2019 19:35 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 011B2120106; Mon, 14 Oct 2019 12:35:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level:
X-Spam-Status: No, score=-1.997 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, 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 akp0VZJZZ8KO; Mon, 14 Oct 2019 12:35:32 -0700 (PDT)
Received: from mail-io1-xd36.google.com (mail-io1-xd36.google.com [IPv6:2607:f8b0:4864:20::d36]) (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 804C312087E; Mon, 14 Oct 2019 12:35:32 -0700 (PDT)
Received: by mail-io1-xd36.google.com with SMTP id b19so40531799iob.4; Mon, 14 Oct 2019 12:35:32 -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=emWfGRN/MNSsU6KKIa+tydmMTRUNwf2aYnPyy1N9vOk=; b=TMpFFKpfjSvrbX2SXI2yyC2jjb4NYuZpk+AD56svODbMScxJ/dAovKiaPv8rtBHaYG gRUsNxqborAGzOV8r+LJ0J6XEAuYRlPCJpqdyWb4DnkNsVAtGt85iglltkNcJG3aVVKv igcFrmWgEET8mb5gXME3s2mf3ch1Ekvkc0SBeAk5WBTIRVjx67HKP4CoTxax3LfsfPmF byv4NXHkGqm1UGpBbRzkHIq8CxGJlDlF6RF3WuS38u/zxPbqHbMILEGoxLdYLLuFXBQ5 rKtIR6iEP1GHG9+wTYfEoNXAYKgEJ2VkeNDRA1d/ivxo/nYpx7BjlcZqRwYEcmNiUcPQ G02A==
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=emWfGRN/MNSsU6KKIa+tydmMTRUNwf2aYnPyy1N9vOk=; b=LdIIir1N6HvMxr9jH4QNdzO9i7J2qEFHQ6yWUS7z6qbuX0mdL7uyfYsglzj/8rkfL6 HfAiAWXON5a5EW+Z6jpvQZ9SIMixyWSCzsHxn/+5U219c2z3FkwrVAVsW+XPdHn1r8/U xT69DQzn61gFug2X/puRxSOusnhnX/afw9HFjbr+8lPTT82xE4uSYAVbnoni1Auh8Ecq KdTI+Dw4Y9bsU4P6Xi22b/tRD8dHX+oqYaBMrA0w30hXNNlDa7yfQkAakOBW+LVriLO7 mW0pGPmHl5/KGH0dh4L1qE3O2W8nBWWIxCuXKnJbJgwiRW0ffpyCGJovBBbD4vYbDWIm FUVw==
X-Gm-Message-State: APjAAAWbpCPod2OMuBc2fhj/AQHsXMGCMkQ/0pyadoiyuxY+eLNHLNUo vIF2YNePS1LclyFBM/Nc3czOMyHK4pGVGrUwGFA=
X-Google-Smtp-Source: APXvYqxQBROd9MSR9bpyJx9yL7hfbyatS8b7EARJZaUK0FAkZ2s+HGf3EmcXhwzWnYtJHs+g0TvG1SSBVRNSoEZzWR8=
X-Received: by 2002:a6b:ab03:: with SMTP id u3mr18372529ioe.158.1571081731470; Mon, 14 Oct 2019 12:35:31 -0700 (PDT)
MIME-Version: 1.0
References: <DB7F3CF2-52AA-4634-8B73-365112A819A6@gmail.com> <201910141537113951663@zte.com.cn>
In-Reply-To: <201910141537113951663@zte.com.cn>
From: Gyan Mishra <hayabusagsm@gmail.com>
Date: Mon, 14 Oct 2019 15:35:17 -0400
Message-ID: <CABNhwV1XSO7k=Em+FY65dWeEVDF__6Go6YdnjkFQw_j-5wVs4g@mail.gmail.com>
To: zhang.zheng@zte.com.cn
Cc: xu.benchong@zte.com.cn, stig@venaas.com, draft-ietf-pim-dr-improvement@ietf.org, pim@ietf.org, Greg Mirsky <gregimirsky@gmail.com>
Content-Type: multipart/alternative; boundary="000000000000847cb10594e3f80b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/pim/SbUGvSkPX6qb85hIvi5Hk5MKIdg>
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 19:35:35 -0000
Thanks Sandy!! In an DR/BDR scenario Active/Backup DR would you then have MRIB/MFIB state on both the DR & BDR which is how you achieve fast convergence or would the state only be on both in MLAG scenario. Thanks Gyan On Mon, Oct 14, 2019 at 3:39 AM <zhang.zheng@zte.com.cn> wrote: > Hi Gyan, > > > As co-author, thank you very much for your review! :-) > > The motivation of this draft is from the actual PIM deployment of our > customers. And the solution works well. > > From RFC7761, the default value of DR priority is 1. For the interface > which never becomes DR you may set the DR priority to 0 by configuration. > > > Thanks, > > Sandy > > > 原始邮件 > *发件人:*GyanMishra <hayabusagsm@gmail.com> > *收件人:*Gyan Mishra <hayabusagsm@gmail.com>; > *抄送人:*徐本崇10065053;stig@venaas.com <stig@venaas.com>; > draft-ietf-pim-dr-improvement@ietf.org < > draft-ietf-pim-dr-improvement@ietf.org>;pim@ietf.org <pim@ietf.org>; > gregimirsky@gmail.com <gregimirsky@gmail.com>; > *日 期 :*2019年10月12日 22:40 > *主 题 :**Re: [pim] Publishing draft-ietf-pim-dr-improvement-08* > PIM WG > > In reviewing the draft I agree this is a much needed for PIM stability to > prevent preemption from occurring when a PIM neighbor comes up with a > higher priority. > > I have seen this scenario come up many times and had caused many multicast > outages over the years with PIM being enabled accidentally on a terminal > server or L2 switch for a vlan and had a higher IP address and became the > DR or had a higher priority configured and became the DR. > > Is there a way to have a DR priority 0 to make the device non DR eligible > similar to ospf DR priority 0. > > I had posted PIM BFD spec from the BFD WG which helps tune down PIM timers > to sub millisecond convergence which helps to get hitless convergence for > LAN multipoint scenario and for MVPN, however this draft is critical to > provide LHR DR stability and prevent DR preemption from occurring. Also > adding the role priority DR/BDR state I think also adds to faster > convergence when the DR goes down. > > In environments where MLAG or like Cisco proprietary vPC is used > forwarding happens to both DR and BDR active/active state which is very > common have PIM MRIB MFIB state on both routers so is that addressed how > that would work in the draft. > > Also was wondering in the case of active backup for faster convergence is > it possible for both DR and BDR to have their MRIB MFIB state table built > for ASM SPT tree and with PIM BFD tuned down timers so that convergence > becomes hitless. > > Thank you > > Gyan Mishra > Verizon Communications > Cell 301 502-1347 > > Sent from my iPhone > > On Oct 11, 2019, at 8:58 PM, Gyan Mishra <hayabusagsm@gmail.com> wrote: > > > I agree that PIM SM DR process and failover does need improvements of > which I would like to bring to everyone’s attention the BFD WG draft for > PIM BFD for fast hitless convergence. > > https://tools.ietf.org/html/draft-mirsky-pim-bfd-p2mp-use-case-02 > > Gyan Mishra > Verizon Communications > Cell 301 502-1347 > > Sent from my iPhone > > On Oct 8, 2019, at 11:39 PM, <xu.benchong@zte.com.cn> < > xu.benchong@zte.com.cn> wrote: > > > Hi, Stig > > I don't know any other undisclosed IPR. > > Thanks > > Benchong Xu > > > > _______________________________________________ > pim mailing list > pim@ietf.org > https://www.ietf.org/mailman/listinfo/pim > > *发件人:*StigVenaas <stig@venaas.com> > *收件人:*pim@ietf.org <pim@ietf.org>;draft-ietf-pim-dr-improvement@ietf.org < > draft-ietf-pim-dr-improvement@ietf.org>; > *日 期 :*2019年10月09日 06:06 > *主 题 :**Re: Publishing draft-ietf-pim-dr-improvement-08* > Hi > > Looks that there are no concerns moving ahead with publication. Can > the authors, and any others that might know > anything about IPR, let us know if they are aware of any other IPR > claims than what has been filed already? > > Stig > > On Tue, Oct 1, 2019 at 11:18 AM Stig Venaas <stig@venaas.com> wrote: > > > > Hi > > > > An earlier version of this draft passed WGLC many months ago. However, > > as discussed in the WG we agreed it should have some text pointing out > > how it relates to draft-mankamana-pim-bdr-02 that we are considering > > for adoption. This text has now been added, as well as some other > > minor changes. > > > > Please look at revision 08 and speak up if you have any concerns. > > > > Authors, and others, please let us know if you are aware of any other > > IPR claims than the one that already has been filed. > > > > I'll wait a week or so to give people a chance to respond. We need at > > least all the authors to respond regarding IPR before proceeding > > though. > > > > Thanks, > > Stig > > > -- Gyan S. Mishra IT Network Engineering & Technology Verizon Communications Inc. (VZ) 13101 Columbia Pike FDC1 3rd Floor Silver Spring, MD 20904 United States Phone: 301 502-1347 Email: gyan.s.mishra@verizon.com www.linkedin.com/in/networking-technologies-consultant
- [pim] Publishing draft-ietf-pim-dr-improvement-08 Stig Venaas
- Re: [pim] Publishing draft-ietf-pim-dr-improvemen… Stig Venaas
- Re: [pim] Publishing draft-ietf-pim-dr-improvemen… Mankamana Mishra (mankamis)
- Re: [pim] Publishing draft-ietf-pim-dr-improvemen… zhang.zheng
- Re: [pim] Publishing draft-ietf-pim-dr-improvemen… 胡方伟
- Re: [pim] Publishing draft-ietf-pim-dr-improvemen… xu.benchong
- Re: [pim] Publishing draft-ietf-pim-dr-improvemen… Gyan Mishra
- Re: [pim] Publishing draft-ietf-pim-dr-improvemen… Gyan Mishra
- Re: [pim] Publishing draft-ietf-pim-dr-improvemen… zhang.zheng
- Re: [pim] Publishing draft-ietf-pim-dr-improvemen… Gyan Mishra
- Re: [pim] Publishing draft-ietf-pim-dr-improvemen… Stig Venaas
- Re: [pim] Publishing draft-ietf-pim-dr-improvemen… Mankamana Mishra (mankamis)
- Re: [pim] Publishing draft-ietf-pim-dr-improvemen… Gyan Mishra
- Re: [pim] Publishing draft-ietf-pim-dr-improvemen… Gyan Mishra
- Re: [pim] Publishing draft-ietf-pim-dr-improvemen… xu.benchong
- Re: [pim] Publishing draft-ietf-pim-dr-improvemen… Gyan Mishra
- Re: [pim] Publishing draft-ietf-pim-dr-improvemen… xu.benchong
- Re: [pim] Publishing draft-ietf-pim-dr-improvemen… Gyan Mishra
- Re: [pim] Publishing draft-ietf-pim-dr-improvemen… Stig Venaas
- Re: [pim] Publishing draft-ietf-pim-dr-improvemen… zhang.zheng
- Re: [pim] Publishing draft-ietf-pim-dr-improvemen… Stig Venaas