[pim] Re: Default BSR priority issue!
Nidhi Bhaskar <nbhaskar@cisco.com> Wed, 03 November 2004 05:04 UTC
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA27257 for <pim-archive@lists.ietf.org>; Wed, 3 Nov 2004 00:04:18 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CPDA3-0005qB-Ig; Tue, 02 Nov 2004 23:54:19 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CPD64-00032O-Mf for pim@megatron.ietf.org; Tue, 02 Nov 2004 23:50:12 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA26672 for <pim@ietf.org>; Tue, 2 Nov 2004 23:50:10 -0500 (EST)
Received: from catarina.usc.edu ([204.57.0.1]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CPDLF-0000xg-36 for pim@ietf.org; Wed, 03 Nov 2004 00:05:58 -0500
Received: from sj-iport-2.cisco.com (sj-iport-2-in.cisco.com [171.71.176.71]) by catarina.usc.edu (8.12.9/8.12.9) with ESMTP id iA34naoh067034 for <pim@catarina.usc.edu>; Tue, 2 Nov 2004 20:49:36 -0800 (PST) (envelope-from nbhaskar@cisco.com)
Received: from sj-core-1.cisco.com (171.71.177.237) by sj-iport-2.cisco.com with ESMTP; 02 Nov 2004 20:59:53 -0800
Received: from cypher.cisco.com (cypher.cisco.com [171.69.11.142]) by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id iA34nQon001285; Tue, 2 Nov 2004 20:49:26 -0800 (PST)
Date: Tue, 02 Nov 2004 20:49:28 -0800
From: Nidhi Bhaskar <nbhaskar@cisco.com>
To: Prashant Jhingran <prashantj@huawei.com>
In-Reply-To: <000001c4c15b$54a30110$30226e0a@huawei8tthy486>
Message-ID: <Pine.GSO.4.58.0411022040470.5229@cypher.cisco.com>
References: <000001c4c15b$54a30110$30226e0a@huawei8tthy486>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Cc: pim@catarina.usc.edu, ctbrown@nexthop.com, Stig.Venaas@uninett.no, Nidhi Bhaskar <nbhaskar@cisco.com>, bwilliam@cisco.com
Subject: [pim] Re: Default BSR priority issue!
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
Sender: pim-bounces@ietf.org
Errors-To: pim-bounces@ietf.org
> The latest BSR draft no where mentions about the default BSR priority & > that's why probably few > Developers/vendors are using the value "Zero" as default BSR priority. > > The problem comes when the EBSR is getting shutdown. > > There are no means by which the current EBSR can inform the other > routers in the domain about itself going down. > (Since default BSR priority and the priority to inform when BSR goes > down boils down to the same numerical value i.e. Zero). > > I think this issue is more important than the RP-mapping we are > discussion currently and this problem should be resolved in the coming > BSR draft....this would also lead to faster convergence during graceful > EBSR shutdown scenarios. Yes, we could have better defaults, but this problem is fairly simple to fix via appropriate configuration (unlike the RP-mapping issue being discussed). So don't agree on the importance ranking :). That said, I am open to putting in a better default in the spec. Will include this in the longish todolist we have for this document... Thanks, Nidhi. _______________________________________________ pim mailing list pim@ietf.org https://www1.ietf.org/mailman/listinfo/pim
- [pim] Default BSR priority issue! Prashant Jhingran
- [pim] Re: Default BSR priority issue! Nidhi Bhaskar