Re: [pim] Sticky PIM DR, should it be added to PIM DR improvements or different draft Fri, 04 December 2020 03:33 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 8762D3A12B6 for <>; Thu, 3 Dec 2020 19:33:24 -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 auiwKMoHzzhV for <>; Thu, 3 Dec 2020 19:33:22 -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 16C913A12B3 for <>; Thu, 3 Dec 2020 19:33:22 -0800 (PST)
Received: from (unknown []) by Forcepoint Email with ESMTPS id C7BFF71A8EC08315FED8; Fri, 4 Dec 2020 11:33:19 +0800 (CST)
Received: from ([]) by with SMTP id 0B43XANT018843; Fri, 4 Dec 2020 11:33:10 +0800 (GMT-8) (envelope-from
Received: from mapi (njxapp04[null]) by mapi (Zmail) with MAPI id mid203; Fri, 4 Dec 2020 11:33:10 +0800 (CST)
Date: Fri, 4 Dec 2020 11:33:10 +0800 (CST)
X-Zmail-TransId: 2afc5fc9adf6d873129d
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: 0B43XANT018843
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: Fri, 04 Dec 2020 03:33:25 -0000

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,



收件人:Mankamana Mishra (mankamis);
日 期 :2020年12月04日 10:07
主 题 :Re: [pim] Sticky PIM DR, should it be added to PIM DR improvements or different draft

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?
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