Re: [pim] Sticky PIM DR, should it be added to PIM DR improvements or different draft Mon, 07 December 2020 09:38 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 3CFEE3A1205 for <>; Mon, 7 Dec 2020 01:38:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.916
X-Spam-Status: No, score=-1.916 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, HTML_NONELEMENT_30_40=0.001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id SgNGcBCwQdNt for <>; Mon, 7 Dec 2020 01:38:02 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 0AC3C3A1289 for <>; Mon, 7 Dec 2020 01:38:01 -0800 (PST)
Received: from (unknown []) by Forcepoint Email with ESMTPS id C174E654DA998AF6D95D; Mon, 7 Dec 2020 17:37:59 +0800 (CST)
Received: from ([]) by with SMTP id 0B79bgnI053712; Mon, 7 Dec 2020 17:37:42 +0800 (GMT-8) (envelope-from
Received: from mapi (njxapp04[null]) by mapi (Zmail) with MAPI id mid203; Mon, 7 Dec 2020 17:37:42 +0800 (CST)
Date: Mon, 7 Dec 2020 17:37:42 +0800 (CST)
X-Zmail-TransId: 2afc5fcdf7e65a037abe
X-Mailer: Zmail v1.0
Message-ID: <>
In-Reply-To: <>
Mime-Version: 1.0
From: <>
To: <>
Cc: <>, <>
Content-Type: multipart/mixed; boundary="=====_001_next====="
X-MAIL: 0B79bgnI053712
Archived-At: <>
Subject: Re: [pim] =?utf-8?q?Sticky_PIM_DR=2C_should_it_be_added_to_PIM_DR_im?= =?utf-8?q?provements_or_different_draft?=
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Protocol Independent Multicast <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 07 Dec 2020 09:38:04 -0000

Hi Stig, 

We are OK to have the two separate documents. 

But as Alvaro pointed out, if a router supports both of the solutions, but the router receives the hello message without DR/BDR options defined in "draft-ietf-pim-dr-improvement", 

whether the router should use the function defined in "draft-mankamana-pim-bdr", or use the function defined in RFC7761.

IMO if the router receives the advertisement of "PIM_DR_MAX_Priority" as Mankamana said, the router can use the function defined in "draft-mankamana-pim-bdr", otherwise uses the function defined in RFC7761. 

What do you think of it?




抄送人:Mankamana Mishra (mankamis);;
日 期 :2020年12月05日 00:03
主 题 :Re: [pim] Sticky PIM DR, should it be added to PIM DR improvements or different draft

Here is my thinking regarding the two drafts. Maybe they can be
merged, but in my mind it might make sense to keep them separate.
This is informational and discusses how to improve DR election without
any protocol changes. An implementation can follow these procedures
and interoperate with any standard implementation. Some of these
improvements are already implemented by several vendors.
This mainly introduces the concept of sticky DR and it requires
protocol changes. It would be standards track or experimental. This is
something entirely new and only works between routers that support
If one wants to improve on the current DR election, but doesn't need
stickiness then the first draft makes sense to me. If stickiness is
needed, then the second draft is needed. I can imagine implementations
supporting both or either. It is up to the user whether they want the
DR to be sticky or not.
Both the drafts discuss the concept of BDR. In the first draft I think
this is not defining anything new, BDR is just terminology to talk
about the next-best DR, the router that would become DR if the DR goes
away. The second draft formalizes this more as if I understand
correctly it also elects a sticky BDR. If an implementation only wants
to support sticky DR (but not BDR), then maybe that can be done with
the second draft, by not making BDR election mandatory.
Thoughts? Do you see this differently?
On Thu, Dec 3, 2020 at 7:33 PM <> wrote:
> Hi Stig, Mankamana,
> The function defined in PIM DR Improvement doesn't need the new priority advertisement.
> AD asked that if the two drafts will considered to be combined into one draft.
> If they are combined, two functions can be introduced in one draft, except the existed PIM DR hello options, the other choice is the new priority announcement.
> PIM DR Improvement draft is open for add the new functions, or keep it still, either is OK.
> AD, chairs, anyone's suggestion is welcomed! :-)
> Best regards,
> Sandy
> 原始邮件
> 发件人:StigVenaas
> 收件人:Mankamana Mishra (mankamis);
> 抄送人;
> 日 期 :2020年12月04日 10:07
> 主 题 :Re: [pim] Sticky PIM DR, should it be added to PIM DR improvements or different draft
> Hi
> If I understand the dr-improvement draft correctly, it supports sticky
> DR as is. Isn't that the main purpose of the draft, aside from also
> electing a BDR? The DR Address Option would announce the address of
> the sticky DR. Why would you need to announce the priority?
> Regards,
> Stig
> On Thu, Dec 3, 2020 at 9:51 AM Mankamana Mishra (mankamis)
> <> wrote:
> > 
> > All,
> > 
> > 
> > 
> > draft briefly talks about PIM DR being sticky. But does not have much detail yet.  There are providers who do want to use Sticky PIM DR functionality. Since DR improvement talks about Hello options and carry elected PIM DR . There are two options.
> > 
> > 
> > 
> > Add new Sticky PIM DR procedures to this draft
> > Have new draft which talks only about sticky PIM DR without any hello option
> > 
> > 
> > 
> > 
> > 
> > Brief about Sticky PIM DR procedures
> > 
> > If Sticky DR is configured in PIM router , initial DR election happens it is defined in PIM RFC today.
> > To make sure now elected DR does not give up it DR role, now it will start advertising PIM_DR_MAX_Priority (this number to be reserved from DR priority value )
> > Now if any new router comes up, it will never try to take role of DR since at step2 elected DR was advertising highest priority.
> > 
> > 
> > 
> > 
> > 
> > This is the brief about what would go in draft.
> > 
> > 
> > 
> > Any input would be appreciated.
> > 
> > 
> > 
> > Mankamana
> > 
> > _______________________________________________
> > pim mailing list
> >
> >
> _______________________________________________
> pim mailing list