[pim] Query about scoped Bootstrap Message

sumanta seal <seal_sum@yahoo.co.in> Thu, 11 January 2007 05:13 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1H4sFK-0000Rg-B6; Thu, 11 Jan 2007 00:13:02 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1H4sFJ-0000Qc-6T for pim@ietf.org; Thu, 11 Jan 2007 00:13:01 -0500
Received: from web8502.mail.in.yahoo.com ([202.43.219.164]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1H4sFH-0001mt-AF for pim@ietf.org; Thu, 11 Jan 2007 00:13:01 -0500
Received: (qmail 87611 invoked by uid 60001); 11 Jan 2007 05:06:16 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.co.in; h=X-YMail-OSG:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=46BOeBpkMPkzcQTS/IomTzJ+8s71Xx2rDZ6aVt1VvpzyFhRrRv1ZFNsWDbtqol1gMbrJjv6bgJ1geBHyvERDM2PrWxuYoUj2RvOSMROBFjzAF3Xqyeq+bndyBGgAFBW3ZxM0lUXWmNfh5n8FmuWEcyMY/aNNuacpWCPzMWVbGhM=;
X-YMail-OSG: 6I9wE.MVM1lP0uTrD233IeZiZU7hW_V_urIv.eCVWYO45cKeY5I6_EtIhsURONX3RHrO8lf7JZ4fdqPUOQwm4rzwLD7TkFc11NXAnpqZrZ0KSyOmF4iDLU.1EqzRMfF4ht12X30WxZMEkwoXQl9GALqWs2pExz8MYYo1aVIEirSYM3Hm722dJYwe05LPMNaAMEhc1wc-
Received: from [203.197.124.190] by web8502.mail.in.yahoo.com via HTTP; Thu, 11 Jan 2007 05:06:15 GMT
Date: Thu, 11 Jan 2007 05:06:15 +0000
From: sumanta seal <seal_sum@yahoo.co.in>
To: pim@ietf.org
MIME-Version: 1.0
Message-ID: <932765.86504.qm@web8502.mail.in.yahoo.com>
X-Spam-Score: 0.5 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Subject: [pim] Query about scoped Bootstrap Message
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>
Content-Type: multipart/mixed; boundary="===============1716395131=="
Errors-To: pim-bounces@ietf.org

Hi,

I have some confusion about one statement in the draft "draft-ietf-pim-sm-bsr-09". In section  3.3 (page 21), the draft says the following --
"RP mappings may be included in the first group range of a BSM, just as for any other group range. After this group range, other group ranges for which there are RP mappings appear in any order ".

Suppose a situation where the BSR is configured with one scope, say G and it becomes the elected BSR for that scope. At the same time it is receiving one C-RP-Adv message for the same scope (i.e . another router wants to be the candidate RP for the same multicast group range G) with address  X. Now when the BSR will send BSM, G will always present in the first group-rp-set of the BSM (with Z bit 1). But will it include the RP address X in the first group-rp-set or it will add another group-rp-set with group address G ( Z bit 0) where it will include the RP address X. 

Please let me know if more information is required.

Thanks and regards,
Sumanta

 				
---------------------------------
 Here’s a new way to find what you're looking for - Yahoo! Answers 
_______________________________________________
pim mailing list
pim@ietf.org
https://www1.ietf.org/mailman/listinfo/pim