[pim] Re: Bootstrap Router Mechanism: Forwarding of non-preferred BSMs
Mark Doll <doll@tm.uka.de> Thu, 24 May 2007 09:19 UTC
Return-path: <pim-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hr9Tn-0004Js-Vv; Thu, 24 May 2007 05:19:31 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hr9Tm-0004Ji-5G for pim@ietf.org; Thu, 24 May 2007 05:19:30 -0400
Received: from iramx2.ira.uni-karlsruhe.de ([141.3.10.81]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hr9Tj-0002Kn-KD for pim@ietf.org; Thu, 24 May 2007 05:19:30 -0400
Received: from irams1.ira.uni-karlsruhe.de ([141.3.10.5]) by iramx2.ira.uni-karlsruhe.de with esmtps id 1Hr9TP-0003Df-TJ; Thu, 24 May 2007 11:19:23 +0200
Received: from i72ms.tm.uni-karlsruhe.de ([141.3.70.5] helo=smtp.ipv6.tm.uni-karlsruhe.de) by irams1.ira.uni-karlsruhe.de with esmtps id 1Hr9TP-0000Uj-HI; Thu, 24 May 2007 11:19:07 +0200
Received: from [IPv6:2001:638:204:6:20d:60ff:fe79:f80d] (mad.ipv6.tm.uni-karlsruhe.de [IPv6:2001:638:204:6:20d:60ff:fe79:f80d]) by smtp.ipv6.tm.uni-karlsruhe.de (Postfix) with ESMTP id D7E042FC097; Thu, 24 May 2007 11:19:06 +0200 (CEST)
Message-ID: <4655588A.1090001@tm.uka.de>
Date: Thu, 24 May 2007 11:19:06 +0200
From: Mark Doll <doll@tm.uka.de>
Organization: Karlsruhe Institute of Technology
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.10) Gecko/20070403 Thunderbird/1.5.0.10 Mnenhy/0.7.5.0
MIME-Version: 1.0
To: Alexander Gall <gall@switch.ch>
References: <4648C703.5070105@tm.uka.de> <18004.23158.807122.197704@hadron.switch.ch>
In-Reply-To: <18004.23158.807122.197704@hadron.switch.ch>
X-Enigmail-Version: 0.94.3.0
OpenPGP: url=http://mark.doll.name/key.asc
X-Face: |"["9\|/{; `lo<kq3XVQRkrm%`q>E4p07x]r.[1'$Et?"m$n4j?'NGC/:IcaH.j2q]SMGY/lH{$!fK-#487&4t%Bs:D+VsQ=3>Ll%[eeVm-D|&TbC.t{I<qj,n~WRC'&SE.Uq@+|i8=kWxKP{(93; J0.S.mj7n9v&>UFa; o!OEQT^,6:LpwfZ+Wo{wUJf; /G/C"pDR, rq7&2-w<y7oNoi9LmfOgEVD^Hx6]nCuR?*C=ydJ>b_i_/#o9)s6sFppkpjeR9o|LAyl, :K, KU+G212yszo6r9
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Spam-Status: No
X-Spam-Score: -1.0 (-)
X-Spam-Report: -1.4 ALL_TRUSTED Passed through trusted hosts only via SMTP 0.5 AWL AWL: From: address is in the auto white-list
X-ATIS-Checksum: v3zoCAcc32ckk
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
Cc: Nidhi Bhaskar <nbhaskar@cisco.com>, James Lingard <jchl@arastra.com>, Stig Venaas <Stig.Venaas@uninett.no>, pim <pim@ietf.org>
Subject: [pim] Re: Bootstrap Router Mechanism: Forwarding of non-preferred BSMs
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>
Errors-To: pim-bounces@ietf.org
Hi Alexander!
Alexander Gall wrote:
> On Mon, 14 May 2007 22:30:59 +0200, Mark Doll <doll@tm.uka.de> said:
>> First:
>> =====
>> Why do routers in state "Candidate BSR" forward non-preferred BSMs from the
>> elected BSR (and switch to state P-BSR), but routers in state "Accept
>> preferred" don't?
>
> They do. In the description of the event "Receive Preferred BSM" in
> section 3.1.4 it is stated that
>
> A Bootstrap message is also preferred if it is from the
> current BSR with a lower weight than the previous BSM it
> sent ...
>
> for precisely this reason. However, this is not evident if you just
> read the description of the event "Receive Non-preferred BSM". To
> make this clear, I suggest to add a reference to this exception:
>
> Receive Non-preferred BSM
> A Bootstrap message is received from a BSR that has lower
> weight than the current BSR with the exception detailed
> above. If a router is in P-BSR state, then it uses its own
> weight as that of the current BSR.
>
Thanks for your clarification. That makes sense and I think, too, all cases
are covered by the current spec. Nevertheless, I'm not shure, if your proposed
pointer to the exception is really clear enough. Maybe explicitly saying that
Receive Non-Preferred BSM (+) Receive Preferred BSM = Receive BSM? So maybe:
Receive Non-preferred BSM
A Bootstrap message other than a preferred Bootstrap message is
received. That is a message from a BSR with a lower weight than
the current BSR with the exception detailed above. If a router is
in P-BSR state, then it uses its own weight as that of the current
BSR.
Mark.
_______________________________________________
pim mailing list
pim@ietf.org
https://www1.ietf.org/mailman/listinfo/pim
- [pim] Re: Bootstrap Router Mechanism: Forwarding … Alexander Gall
- [pim] Bootstrap Router Mechanism: Forwarding of n… Mark Doll
- [pim] Re: Bootstrap Router Mechanism: Forwarding … Alexander Gall
- [pim] Re: Bootstrap Router Mechanism: Forwarding … Mark Doll
- [pim] Re: Bootstrap Router Mechanism: Forwarding … Mark Doll