From pim-admin@ietf.org  Tue Nov  4 06:56:33 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA10547
	for <pim-archive@lists.ietf.org>; Tue, 4 Nov 2003 06:56:33 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AGzn0-0007Id-LQ; Tue, 04 Nov 2003 06:56:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AGzml-0007Hd-9I
	for pim@optimus.ietf.org; Tue, 04 Nov 2003 06:55:47 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA10495
	for <pim@ietf.org>; Tue, 4 Nov 2003 06:55:33 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AGzmg-0003yc-00
	for pim@ietf.org; Tue, 04 Nov 2003 06:55:43 -0500
Received: from catarina.usc.edu ([204.57.0.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AGzmg-0003xs-00
	for pim@ietf.org; Tue, 04 Nov 2003 06:55:42 -0500
Received: from v6.hitachi.co.jp (galilei.v6.hitachi.co.jp [133.145.167.4])
	by catarina.usc.edu (8.12.9/8.12.9) with ESMTP id hA4BtCLT076285
	for <pim@catarina.usc.edu>; Tue, 4 Nov 2003 03:55:13 -0800 (PST)
	(envelope-from suz@crl.hitachi.co.jp)
Received: from s30.crl.hitachi.co.jp (galilei.v6.hitachi.co.jp [133.145.167.4])
	by v6.hitachi.co.jp (8.12.10/8.11.6) with ESMTP id hA4BvM1Q069993;
	Tue, 4 Nov 2003 20:57:22 +0900 (JST)
	(envelope-from suz@crl.hitachi.co.jp)
Date: Tue, 04 Nov 2003 20:55:09 +0900
Message-ID: <x7wuagic0y.wl%suz@crl.hitachi.co.jp>
From: SUZUKI Shinsuke <suz@crl.hitachi.co.jp>
To: pusateri@juniper.net
Cc: kouvelas@cisco.com, pim@catarina.usc.edu
Subject: Re: [pim] some comments to draft-ietf-pim-sm-v2-new-08.txt 
X-cite: xcite 1.33
In-Reply-To: <200311010025.hA10PQi17292@merlot.juniper.net>
References: <kouvelas@cisco.com>
	<200310282247.h9SMl5jP009244@sj-core-1.cisco.com>
	<200311010025.hA10PQi17292@merlot.juniper.net>
User-Agent: User-Agent: Wanderlust/2.11.14 (Wonderwall) Emacs/21.3 Mule/5.0 (SAKAKI)
Organization: Network Systems Research Dept., Central Research Laboratory, Hitachi, Ltd, Japan
MIME-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen")
Content-Type: text/plain; charset=US-ASCII
Sender: pim-admin@ietf.org
Errors-To: pim-admin@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Id: Protocol Independent Multicast <pim.ietf.org>
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>

Hello,

>>>>> On Fri, 31 Oct 2003 16:25:26 -0800
>>>>> pusateri@juniper.net(Tom Pusateri)  said:

> >>	The Interface_Address_List Option MUST be included in all
> >>	Hello messages. This option advertises all the secondary
> >>	addresses associated with the source interface of the router
> >>	originating the message.  If there is no secondary address
> >>	associated with the source interface, this option MAY be
> >>	omitted.
> >
> >I will change the text in the spec to reflect your comment.
>

> I was thinking it would be great to send the address list hello
> option regardless so that it is possible to tell that your neighbors
> all support it.  This would make it easy to diagnose problems at the
> border between two domains.

When there is no secondary address on a link, it is not so useful in
debugging whether some neighbor supports this option or not, since
this option does not affect the protocol behavior in that case.

You can estimate if other vendors carefully read the latest spec from
the Hello message:-)   This may be a reason to always include this
option, but not a reason to mandate it to all PIM-SM implementations...

Am I understanding your intension correctly?


Thanks,
----
SUZUKI, Shinsuke @ Hitachi / KAME Project

_______________________________________________
pim mailing list
pim@ietf.org
https://www1.ietf.org/mailman/listinfo/pim


From exim@www1.ietf.org  Tue Nov  4 06:56:37 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA10562
	for <pim-archive@odin.ietf.org>; Tue, 4 Nov 2003 06:56:37 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AGznG-0007Mb-Nz
	for pim-archive@odin.ietf.org; Tue, 04 Nov 2003 06:56:21 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hA4BuIEi028301
	for pim-archive@odin.ietf.org; Tue, 4 Nov 2003 06:56:18 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AGznG-0007MO-Hw
	for pim-web-archive@optimus.ietf.org; Tue, 04 Nov 2003 06:56:18 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA10509
	for <pim-web-archive@ietf.org>; Tue, 4 Nov 2003 06:56:04 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AGznC-0003yx-00
	for pim-web-archive@ietf.org; Tue, 04 Nov 2003 06:56:14 -0500
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AGznB-0003ys-00
	for pim-web-archive@ietf.org; Tue, 04 Nov 2003 06:56:13 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AGzn0-0007Id-LQ; Tue, 04 Nov 2003 06:56:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AGzml-0007Hd-9I
	for pim@optimus.ietf.org; Tue, 04 Nov 2003 06:55:47 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA10495
	for <pim@ietf.org>; Tue, 4 Nov 2003 06:55:33 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AGzmg-0003yc-00
	for pim@ietf.org; Tue, 04 Nov 2003 06:55:43 -0500
Received: from catarina.usc.edu ([204.57.0.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AGzmg-0003xs-00
	for pim@ietf.org; Tue, 04 Nov 2003 06:55:42 -0500
Received: from v6.hitachi.co.jp (galilei.v6.hitachi.co.jp [133.145.167.4])
	by catarina.usc.edu (8.12.9/8.12.9) with ESMTP id hA4BtCLT076285
	for <pim@catarina.usc.edu>; Tue, 4 Nov 2003 03:55:13 -0800 (PST)
	(envelope-from suz@crl.hitachi.co.jp)
Received: from s30.crl.hitachi.co.jp (galilei.v6.hitachi.co.jp [133.145.167.4])
	by v6.hitachi.co.jp (8.12.10/8.11.6) with ESMTP id hA4BvM1Q069993;
	Tue, 4 Nov 2003 20:57:22 +0900 (JST)
	(envelope-from suz@crl.hitachi.co.jp)
Date: Tue, 04 Nov 2003 20:55:09 +0900
Message-ID: <x7wuagic0y.wl%suz@crl.hitachi.co.jp>
From: SUZUKI Shinsuke <suz@crl.hitachi.co.jp>
To: pusateri@juniper.net
Cc: kouvelas@cisco.com, pim@catarina.usc.edu
Subject: Re: [pim] some comments to draft-ietf-pim-sm-v2-new-08.txt 
X-cite: xcite 1.33
In-Reply-To: <200311010025.hA10PQi17292@merlot.juniper.net>
References: <kouvelas@cisco.com>
	<200310282247.h9SMl5jP009244@sj-core-1.cisco.com>
	<200311010025.hA10PQi17292@merlot.juniper.net>
User-Agent: User-Agent: Wanderlust/2.11.14 (Wonderwall) Emacs/21.3 Mule/5.0 (SAKAKI)
Organization: Network Systems Research Dept., Central Research Laboratory, Hitachi, Ltd, Japan
MIME-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen")
Content-Type: text/plain; charset=US-ASCII
Sender: pim-admin@ietf.org
Errors-To: pim-admin@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Id: Protocol Independent Multicast <pim.ietf.org>
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>

Hello,

>>>>> On Fri, 31 Oct 2003 16:25:26 -0800
>>>>> pusateri@juniper.net(Tom Pusateri)  said:

> >>	The Interface_Address_List Option MUST be included in all
> >>	Hello messages. This option advertises all the secondary
> >>	addresses associated with the source interface of the router
> >>	originating the message.  If there is no secondary address
> >>	associated with the source interface, this option MAY be
> >>	omitted.
> >
> >I will change the text in the spec to reflect your comment.
>

> I was thinking it would be great to send the address list hello
> option regardless so that it is possible to tell that your neighbors
> all support it.  This would make it easy to diagnose problems at the
> border between two domains.

When there is no secondary address on a link, it is not so useful in
debugging whether some neighbor supports this option or not, since
this option does not affect the protocol behavior in that case.

You can estimate if other vendors carefully read the latest spec from
the Hello message:-)   This may be a reason to always include this
option, but not a reason to mandate it to all PIM-SM implementations...

Am I understanding your intension correctly?


Thanks,
----
SUZUKI, Shinsuke @ Hitachi / KAME Project

_______________________________________________
pim mailing list
pim@ietf.org
https://www1.ietf.org/mailman/listinfo/pim



From pim-admin@ietf.org  Fri Nov  7 04:10:43 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA06380
	for <pim-archive@lists.ietf.org>; Fri, 7 Nov 2003 04:10:43 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AI2cz-0001Cb-FU; Fri, 07 Nov 2003 04:10:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AI2c5-0001B5-7z
	for pim@optimus.ietf.org; Fri, 07 Nov 2003 04:09:05 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA06328
	for <pim@ietf.org>; Fri, 7 Nov 2003 04:08:49 -0500 (EST)
From: shiroko.nr@ncos.nec.co.jp
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AI2bx-0001XA-00
	for pim@ietf.org; Fri, 07 Nov 2003 04:08:57 -0500
Received: from tyo201.gate.nec.co.jp ([210.143.35.51])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AI2bw-0001X5-00
	for pim@ietf.org; Fri, 07 Nov 2003 04:08:56 -0500
Received: from mailgate3.nec.co.jp ([10.7.69.161])
	by TYO201.gate.nec.co.jp (8.11.7/3.7W01080315) with ESMTP id hA798tg03008
	for <pim@ietf.org>; Fri, 7 Nov 2003 18:08:55 +0900 (JST)
Received: (from root@localhost) by mailgate3.nec.co.jp (8.11.7/3.7W-MAILGATE-NEC)
	id hA798sR12622 for pim@ietf.org; Fri, 7 Nov 2003 18:08:54 +0900 (JST)
Received: from ncos.nec.co.jp (mailgate.ncos.nec.co.jp [10.40.15.11]) by mailsv4.nec.co.jp (8.11.7/3.7W-MAILSV4-NEC) with SMTP
	id hA798ra08248 for <pim@ietf.org>; Fri, 7 Nov 2003 18:08:53 +0900 (JST)
Received: (qmail 29815 invoked by uid 0); 7 Nov 2003 18:08:52 +0900
Received: from unknown (HELO segp2127) (10.40.20.127)
  by 172.16.255.129 with SMTP; 7 Nov 2003 18:08:52 +0900
To: pim@ietf.org
Message-Id: <20031107180925shiroko.nr@smtp.ncos.nec.co.jp>
Mime-Version: 1.0
X-Mailer: WeMail32[2.09A] ID:NCOSWM
Date: Fri, 7 Nov 2003 18:09:25 +0900
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [pim] Query regarding the fragmentation for Register message
Sender: pim-admin@ietf.org
Errors-To: pim-admin@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Id: Protocol Independent Multicast <pim.ietf.org>
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-Transfer-Encoding: 7bit

Hello, 

I have a question regarding the fragmentation for PIM register 
messages defined in the draft draft-ietf-pim-sm-v2-new-08.txt 
Section 4.4.1. 

    If a multicast packet is fragmented on the way into the 
    Register Tunnel, each fragment is encapsulated individually so it 
    contains IP, PIM, and inner IP headers. 

    In IPv6, an ICMP Fragmentation Required message may be sent by the 
    encapsulating DR. 

My understanding is that inner multicast data would be fragmented 
before it is encapsulated with outer IP header and PIM header. 

I want to know the reason to go through the procedure mentioned above. 
Is it wrong procedure that fragmentation is done after a multicast 
packet is encapsulated with outer IP header and PIM header ? 

In IPv6, when an original multicast packet is smaller than 
IPv6 minimum MTU(1280bytes), DR cannot send PACKET_TOO_BIG to sender.  
And DR would have to fragment the packet when it is larger than the 
Path-MTU toward the RP. 
At that time, If original packet was fragmented by the sender, 
DR cannot fragment it anymore, I think. 

Please let me know if I am making any mistake.  

Thanks, 

Shiroko 

_______________________________________________
pim mailing list
pim@ietf.org
https://www1.ietf.org/mailman/listinfo/pim


From exim@www1.ietf.org  Fri Nov  7 04:10:45 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA06399
	for <pim-archive@odin.ietf.org>; Fri, 7 Nov 2003 04:10:45 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AI2dN-0001FU-Ge
	for pim-archive@odin.ietf.org; Fri, 07 Nov 2003 04:10:26 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hA79APQW004797
	for pim-archive@odin.ietf.org; Fri, 7 Nov 2003 04:10:25 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AI2dN-0001FI-0a
	for pim-web-archive@optimus.ietf.org; Fri, 07 Nov 2003 04:10:25 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA06374
	for <pim-web-archive@ietf.org>; Fri, 7 Nov 2003 04:10:13 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AI2dK-0001YX-00
	for pim-web-archive@ietf.org; Fri, 07 Nov 2003 04:10:22 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AI2dJ-0001YT-00
	for pim-web-archive@ietf.org; Fri, 07 Nov 2003 04:10:21 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AI2cz-0001Cb-FU; Fri, 07 Nov 2003 04:10:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AI2c5-0001B5-7z
	for pim@optimus.ietf.org; Fri, 07 Nov 2003 04:09:05 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA06328
	for <pim@ietf.org>; Fri, 7 Nov 2003 04:08:49 -0500 (EST)
From: shiroko.nr@ncos.nec.co.jp
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AI2bx-0001XA-00
	for pim@ietf.org; Fri, 07 Nov 2003 04:08:57 -0500
Received: from tyo201.gate.nec.co.jp ([210.143.35.51])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AI2bw-0001X5-00
	for pim@ietf.org; Fri, 07 Nov 2003 04:08:56 -0500
Received: from mailgate3.nec.co.jp ([10.7.69.161])
	by TYO201.gate.nec.co.jp (8.11.7/3.7W01080315) with ESMTP id hA798tg03008
	for <pim@ietf.org>; Fri, 7 Nov 2003 18:08:55 +0900 (JST)
Received: (from root@localhost) by mailgate3.nec.co.jp (8.11.7/3.7W-MAILGATE-NEC)
	id hA798sR12622 for pim@ietf.org; Fri, 7 Nov 2003 18:08:54 +0900 (JST)
Received: from ncos.nec.co.jp (mailgate.ncos.nec.co.jp [10.40.15.11]) by mailsv4.nec.co.jp (8.11.7/3.7W-MAILSV4-NEC) with SMTP
	id hA798ra08248 for <pim@ietf.org>; Fri, 7 Nov 2003 18:08:53 +0900 (JST)
Received: (qmail 29815 invoked by uid 0); 7 Nov 2003 18:08:52 +0900
Received: from unknown (HELO segp2127) (10.40.20.127)
  by 172.16.255.129 with SMTP; 7 Nov 2003 18:08:52 +0900
To: pim@ietf.org
Message-Id: <20031107180925shiroko.nr@smtp.ncos.nec.co.jp>
Mime-Version: 1.0
X-Mailer: WeMail32[2.09A] ID:NCOSWM
Date: Fri, 7 Nov 2003 18:09:25 +0900
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [pim] Query regarding the fragmentation for Register message
Sender: pim-admin@ietf.org
Errors-To: pim-admin@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Id: Protocol Independent Multicast <pim.ietf.org>
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-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hello, 

I have a question regarding the fragmentation for PIM register 
messages defined in the draft draft-ietf-pim-sm-v2-new-08.txt 
Section 4.4.1. 

    If a multicast packet is fragmented on the way into the 
    Register Tunnel, each fragment is encapsulated individually so it 
    contains IP, PIM, and inner IP headers. 

    In IPv6, an ICMP Fragmentation Required message may be sent by the 
    encapsulating DR. 

My understanding is that inner multicast data would be fragmented 
before it is encapsulated with outer IP header and PIM header. 

I want to know the reason to go through the procedure mentioned above. 
Is it wrong procedure that fragmentation is done after a multicast 
packet is encapsulated with outer IP header and PIM header ? 

In IPv6, when an original multicast packet is smaller than 
IPv6 minimum MTU(1280bytes), DR cannot send PACKET_TOO_BIG to sender.  
And DR would have to fragment the packet when it is larger than the 
Path-MTU toward the RP. 
At that time, If original packet was fragmented by the sender, 
DR cannot fragment it anymore, I think. 

Please let me know if I am making any mistake.  

Thanks, 

Shiroko 

_______________________________________________
pim mailing list
pim@ietf.org
https://www1.ietf.org/mailman/listinfo/pim



From pim-admin@ietf.org  Tue Nov 11 14:31:32 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA16884
	for <pim-archive@lists.ietf.org>; Tue, 11 Nov 2003 14:31:32 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJeE9-0005W1-Ld; Tue, 11 Nov 2003 14:31:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJeDG-0005GW-60
	for pim@optimus.ietf.org; Tue, 11 Nov 2003 14:30:06 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA16713
	for <pim@ietf.org>; Tue, 11 Nov 2003 14:29:53 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJeDD-0000ay-00
	for pim@ietf.org; Tue, 11 Nov 2003 14:30:03 -0500
Received: from catarina.usc.edu ([204.57.0.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJeDC-0000aP-00
	for pim@ietf.org; Tue, 11 Nov 2003 14:30:03 -0500
Received: from tyholt.uninett.no (tyholt.uninett.no [158.38.60.10])
	by catarina.usc.edu (8.12.9/8.12.9) with ESMTP id hABJTVLT023498
	for <pim@catarina.usc.edu>; Tue, 11 Nov 2003 11:29:32 -0800 (PST)
	(envelope-from Stig.Venaas@uninett.no)
Received: from sverresborg.uninett.no (sverresborg.uninett.no [IPv6:2001:700:e000:0:204:75ff:fee4:423b])
	by tyholt.uninett.no (8.12.10/8.12.10) with ESMTP id hABJTPpI029149
	for <pim@catarina.usc.edu>; Tue, 11 Nov 2003 20:29:25 +0100
Received: from sverresborg.uninett.no (localhost.localdomain [127.0.0.1])
	by sverresborg.uninett.no (8.12.8/8.12.9) with ESMTP id hABJTPR7015869
	for <pim@catarina.usc.edu>; Tue, 11 Nov 2003 20:29:25 +0100
Received: (from venaas@localhost)
	by sverresborg.uninett.no (8.12.8/8.12.8/Submit) id hABJTObf015868
	for pim@catarina.usc.edu; Tue, 11 Nov 2003 20:29:24 +0100
X-Authentication-Warning: sverresborg.uninett.no: venaas set sender to Stig.Venaas@uninett.no using -f
Date: Tue, 11 Nov 2003 20:29:24 +0100
From: Stig Venaas <Stig.Venaas@uninett.no>
To: pim@catarina.usc.edu
Message-ID: <20031111192924.GA15859@sverresborg.uninett.no>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4.1i
Subject: [pim] Volunteer for BSR spec
Sender: pim-admin@ietf.org
Errors-To: pim-admin@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Id: Protocol Independent Multicast <pim.ietf.org>
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>

I've been told that you're looking for a volunteer to work on the
spec. I'm unfortunately not at the pim wg meeting.

I would be interested in this. I've been doing some work in this
area and are not quite happy with current spec. I would like to
see spec be improved and moved forward.

Since I'm not at the meeting, I'm not quite sure what you expect
from a volunteer though...

Stig


_______________________________________________
pim mailing list
pim@ietf.org
https://www1.ietf.org/mailman/listinfo/pim


From exim@www1.ietf.org  Tue Nov 11 14:31:34 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA16899
	for <pim-archive@odin.ietf.org>; Tue, 11 Nov 2003 14:31:34 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJeEO-0005bZ-6A
	for pim-archive@odin.ietf.org; Tue, 11 Nov 2003 14:31:16 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hABJVGTF021541
	for pim-archive@odin.ietf.org; Tue, 11 Nov 2003 14:31:16 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJeEN-0005bM-VM
	for pim-web-archive@optimus.ietf.org; Tue, 11 Nov 2003 14:31:16 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA16833
	for <pim-web-archive@ietf.org>; Tue, 11 Nov 2003 14:31:03 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJeEL-0000fH-00
	for pim-web-archive@ietf.org; Tue, 11 Nov 2003 14:31:13 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJeEK-0000fB-00
	for pim-web-archive@ietf.org; Tue, 11 Nov 2003 14:31:12 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJeE9-0005W1-Ld; Tue, 11 Nov 2003 14:31:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJeDG-0005GW-60
	for pim@optimus.ietf.org; Tue, 11 Nov 2003 14:30:06 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA16713
	for <pim@ietf.org>; Tue, 11 Nov 2003 14:29:53 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJeDD-0000ay-00
	for pim@ietf.org; Tue, 11 Nov 2003 14:30:03 -0500
Received: from catarina.usc.edu ([204.57.0.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJeDC-0000aP-00
	for pim@ietf.org; Tue, 11 Nov 2003 14:30:03 -0500
Received: from tyholt.uninett.no (tyholt.uninett.no [158.38.60.10])
	by catarina.usc.edu (8.12.9/8.12.9) with ESMTP id hABJTVLT023498
	for <pim@catarina.usc.edu>; Tue, 11 Nov 2003 11:29:32 -0800 (PST)
	(envelope-from Stig.Venaas@uninett.no)
Received: from sverresborg.uninett.no (sverresborg.uninett.no [IPv6:2001:700:e000:0:204:75ff:fee4:423b])
	by tyholt.uninett.no (8.12.10/8.12.10) with ESMTP id hABJTPpI029149
	for <pim@catarina.usc.edu>; Tue, 11 Nov 2003 20:29:25 +0100
Received: from sverresborg.uninett.no (localhost.localdomain [127.0.0.1])
	by sverresborg.uninett.no (8.12.8/8.12.9) with ESMTP id hABJTPR7015869
	for <pim@catarina.usc.edu>; Tue, 11 Nov 2003 20:29:25 +0100
Received: (from venaas@localhost)
	by sverresborg.uninett.no (8.12.8/8.12.8/Submit) id hABJTObf015868
	for pim@catarina.usc.edu; Tue, 11 Nov 2003 20:29:24 +0100
X-Authentication-Warning: sverresborg.uninett.no: venaas set sender to Stig.Venaas@uninett.no using -f
Date: Tue, 11 Nov 2003 20:29:24 +0100
From: Stig Venaas <Stig.Venaas@uninett.no>
To: pim@catarina.usc.edu
Message-ID: <20031111192924.GA15859@sverresborg.uninett.no>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4.1i
Subject: [pim] Volunteer for BSR spec
Sender: pim-admin@ietf.org
Errors-To: pim-admin@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Id: Protocol Independent Multicast <pim.ietf.org>
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>

I've been told that you're looking for a volunteer to work on the
spec. I'm unfortunately not at the pim wg meeting.

I would be interested in this. I've been doing some work in this
area and are not quite happy with current spec. I would like to
see spec be improved and moved forward.

Since I'm not at the meeting, I'm not quite sure what you expect
from a volunteer though...

Stig


_______________________________________________
pim mailing list
pim@ietf.org
https://www1.ietf.org/mailman/listinfo/pim



From pim-admin@ietf.org  Tue Nov 11 18:39:26 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA28856
	for <pim-archive@lists.ietf.org>; Tue, 11 Nov 2003 18:39:26 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJi68-0000zL-KP; Tue, 11 Nov 2003 18:39:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJi5a-0000yv-0O
	for pim@optimus.ietf.org; Tue, 11 Nov 2003 18:38:26 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA28828
	for <pim@ietf.org>; Tue, 11 Nov 2003 18:38:11 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJi5W-0004X2-00
	for pim@ietf.org; Tue, 11 Nov 2003 18:38:22 -0500
Received: from catarina.usc.edu ([204.57.0.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJi5V-0004Wi-00
	for pim@ietf.org; Tue, 11 Nov 2003 18:38:22 -0500
Received: from merlot.juniper.net (natint2.juniper.net [207.17.136.150])
	by catarina.usc.edu (8.12.9/8.12.9) with ESMTP id hABNbqLT024253
	for <pim@catarina.usc.edu>; Tue, 11 Nov 2003 15:37:52 -0800 (PST)
	(envelope-from pusateri@juniper.net)
Received: from juniper.net (garnet.juniper.net [172.17.28.17])
	by merlot.juniper.net (8.11.3/8.11.3) with ESMTP id hABNbdi77647;
	Tue, 11 Nov 2003 15:37:39 -0800 (PST)
	(envelope-from pusateri@juniper.net)
Message-Id: <200311112337.hABNbdi77647@merlot.juniper.net>
To: Stig Venaas <Stig.Venaas@uninett.no>
cc: pim@catarina.usc.edu, pusateri@juniper.net
Subject: Re: [pim] Volunteer for BSR spec 
In-Reply-To: Message from Stig Venaas <Stig.Venaas@uninett.no> 
   of "Tue, 11 Nov 2003 20:29:24 +0100." <20031111192924.GA15859@sverresborg.uninett.no> 
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <80954.1068593859.1@juniper.net>
Date: Tue, 11 Nov 2003 15:37:39 -0800
From: Tom Pusateri <pusateri@juniper.net>
Sender: pim-admin@ietf.org
Errors-To: pim-admin@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Id: Protocol Independent Multicast <pim.ietf.org>
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>

Thanks, we're organizing this work now and we'll definitely get back
to you real soon now on what this would involve.

Thanks,
Tom

In message <20031111192924.GA15859@sverresborg.uninett.no> you write:
>I've been told that you're looking for a volunteer to work on the
>spec. I'm unfortunately not at the pim wg meeting.
>
>I would be interested in this. I've been doing some work in this
>area and are not quite happy with current spec. I would like to
>see spec be improved and moved forward.
>
>Since I'm not at the meeting, I'm not quite sure what you expect
>from a volunteer though...
>
>Stig
>
>
>_______________________________________________
>pim mailing list
>pim@ietf.org
>https://www1.ietf.org/mailman/listinfo/pim

_______________________________________________
pim mailing list
pim@ietf.org
https://www1.ietf.org/mailman/listinfo/pim


From exim@www1.ietf.org  Tue Nov 11 18:39:28 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA28871
	for <pim-archive@odin.ietf.org>; Tue, 11 Nov 2003 18:39:28 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJi6J-00010x-H8
	for pim-archive@odin.ietf.org; Tue, 11 Nov 2003 18:39:12 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hABNdBlr003893
	for pim-archive@odin.ietf.org; Tue, 11 Nov 2003 18:39:11 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJi6I-00010i-Ro
	for pim-web-archive@optimus.ietf.org; Tue, 11 Nov 2003 18:39:10 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA28839
	for <pim-web-archive@ietf.org>; Tue, 11 Nov 2003 18:38:56 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJi6F-0004XV-00
	for pim-web-archive@ietf.org; Tue, 11 Nov 2003 18:39:07 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJi6F-0004XS-00
	for pim-web-archive@ietf.org; Tue, 11 Nov 2003 18:39:07 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJi68-0000zL-KP; Tue, 11 Nov 2003 18:39:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJi5a-0000yv-0O
	for pim@optimus.ietf.org; Tue, 11 Nov 2003 18:38:26 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA28828
	for <pim@ietf.org>; Tue, 11 Nov 2003 18:38:11 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJi5W-0004X2-00
	for pim@ietf.org; Tue, 11 Nov 2003 18:38:22 -0500
Received: from catarina.usc.edu ([204.57.0.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJi5V-0004Wi-00
	for pim@ietf.org; Tue, 11 Nov 2003 18:38:22 -0500
Received: from merlot.juniper.net (natint2.juniper.net [207.17.136.150])
	by catarina.usc.edu (8.12.9/8.12.9) with ESMTP id hABNbqLT024253
	for <pim@catarina.usc.edu>; Tue, 11 Nov 2003 15:37:52 -0800 (PST)
	(envelope-from pusateri@juniper.net)
Received: from juniper.net (garnet.juniper.net [172.17.28.17])
	by merlot.juniper.net (8.11.3/8.11.3) with ESMTP id hABNbdi77647;
	Tue, 11 Nov 2003 15:37:39 -0800 (PST)
	(envelope-from pusateri@juniper.net)
Message-Id: <200311112337.hABNbdi77647@merlot.juniper.net>
To: Stig Venaas <Stig.Venaas@uninett.no>
cc: pim@catarina.usc.edu, pusateri@juniper.net
Subject: Re: [pim] Volunteer for BSR spec 
In-Reply-To: Message from Stig Venaas <Stig.Venaas@uninett.no> 
   of "Tue, 11 Nov 2003 20:29:24 +0100." <20031111192924.GA15859@sverresborg.uninett.no> 
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <80954.1068593859.1@juniper.net>
Date: Tue, 11 Nov 2003 15:37:39 -0800
From: Tom Pusateri <pusateri@juniper.net>
Sender: pim-admin@ietf.org
Errors-To: pim-admin@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Id: Protocol Independent Multicast <pim.ietf.org>
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>

Thanks, we're organizing this work now and we'll definitely get back
to you real soon now on what this would involve.

Thanks,
Tom

In message <20031111192924.GA15859@sverresborg.uninett.no> you write:
>I've been told that you're looking for a volunteer to work on the
>spec. I'm unfortunately not at the pim wg meeting.
>
>I would be interested in this. I've been doing some work in this
>area and are not quite happy with current spec. I would like to
>see spec be improved and moved forward.
>
>Since I'm not at the meeting, I'm not quite sure what you expect
>from a volunteer though...
>
>Stig
>
>
>_______________________________________________
>pim mailing list
>pim@ietf.org
>https://www1.ietf.org/mailman/listinfo/pim

_______________________________________________
pim mailing list
pim@ietf.org
https://www1.ietf.org/mailman/listinfo/pim



From pim-admin@ietf.org  Tue Nov 11 19:02:24 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA29597
	for <pim-archive@lists.ietf.org>; Tue, 11 Nov 2003 19:02:24 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJiSP-0002JB-9z; Tue, 11 Nov 2003 19:02:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJiSG-0002Iy-6m
	for pim@optimus.ietf.org; Tue, 11 Nov 2003 19:01:52 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA29580
	for <pim@ietf.org>; Tue, 11 Nov 2003 19:01:37 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJiSC-0004pL-00
	for pim@ietf.org; Tue, 11 Nov 2003 19:01:48 -0500
Received: from h-135-207-24-32.research.att.com ([135.207.24.32] helo=mailman.research.att.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJiSC-0004on-00
	for pim@ietf.org; Tue, 11 Nov 2003 19:01:48 -0500
Received: from unixmail.research.att.com (unixmail.research.att.com [135.207.26.71])
	by mailman.research.att.com (8.12.8/8.12.8) with ESMTP id hAC0rquQ025039;
	Tue, 11 Nov 2003 19:53:52 -0500
Received: from windsor.research.att.com (windsor.research.att.com [135.207.26.46])
	by unixmail.research.att.com (8.12.8+Sun/8.8.7) with ESMTP id hABNwTZn020619;
	Tue, 11 Nov 2003 18:58:29 -0500 (EST)
From: Bill Fenner <fenner@research.att.com>
Received: (from fenner@localhost)
	by windsor.research.att.com (8.11.6+Sun/8.8.5) id hAC015t26578;
	Tue, 11 Nov 2003 16:01:05 -0800 (PST)
Message-Id: <200311120001.hAC015t26578@windsor.research.att.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
To: shiroko.nr@ncos.nec.co.jp
Subject: Re: [pim] Query regarding the fragmentation for Register message
Cc: pim@ietf.org
Date: Tue, 11 Nov 2003 16:01:02 -0800
Versions: dmail (solaris) 2.5a/makemail 2.9d
Sender: pim-admin@ietf.org
Errors-To: pim-admin@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Id: Protocol Independent Multicast <pim.ietf.org>
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>


Shiroko,

  You are right; if the MTU of the DR->RP path is 1280 then the DR
may not send an ICMP fragmentation required error.  The idea behind
having the fragmentation occur inside the tunnel is to prevent
the RP from being overloaded with reassembly load.

  One possible way to handle this is that if the DR->RP path MTU is
1288 or less then use fragmentation on the outer packet.  This leaves
the overhead on the end systems if possible and only moves it to the
RP when necessary.  However, it's a little obscure and possibly
confusing.  Anyone have any thoughts on this?

Thanks,
  Bill

_______________________________________________
pim mailing list
pim@ietf.org
https://www1.ietf.org/mailman/listinfo/pim


From exim@www1.ietf.org  Tue Nov 11 19:02:26 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA29612
	for <pim-archive@odin.ietf.org>; Tue, 11 Nov 2003 19:02:26 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJiSX-0002ML-Pt
	for pim-archive@odin.ietf.org; Tue, 11 Nov 2003 19:02:10 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAC029pW009063
	for pim-archive@odin.ietf.org; Tue, 11 Nov 2003 19:02:09 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJiSX-0002M6-KX
	for pim-web-archive@optimus.ietf.org; Tue, 11 Nov 2003 19:02:09 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA29584
	for <pim-web-archive@ietf.org>; Tue, 11 Nov 2003 19:01:55 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJiSU-0004pS-00
	for pim-web-archive@ietf.org; Tue, 11 Nov 2003 19:02:06 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJiSU-0004pP-00
	for pim-web-archive@ietf.org; Tue, 11 Nov 2003 19:02:06 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJiSP-0002JB-9z; Tue, 11 Nov 2003 19:02:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJiSG-0002Iy-6m
	for pim@optimus.ietf.org; Tue, 11 Nov 2003 19:01:52 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA29580
	for <pim@ietf.org>; Tue, 11 Nov 2003 19:01:37 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJiSC-0004pL-00
	for pim@ietf.org; Tue, 11 Nov 2003 19:01:48 -0500
Received: from h-135-207-24-32.research.att.com ([135.207.24.32] helo=mailman.research.att.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJiSC-0004on-00
	for pim@ietf.org; Tue, 11 Nov 2003 19:01:48 -0500
Received: from unixmail.research.att.com (unixmail.research.att.com [135.207.26.71])
	by mailman.research.att.com (8.12.8/8.12.8) with ESMTP id hAC0rquQ025039;
	Tue, 11 Nov 2003 19:53:52 -0500
Received: from windsor.research.att.com (windsor.research.att.com [135.207.26.46])
	by unixmail.research.att.com (8.12.8+Sun/8.8.7) with ESMTP id hABNwTZn020619;
	Tue, 11 Nov 2003 18:58:29 -0500 (EST)
From: Bill Fenner <fenner@research.att.com>
Received: (from fenner@localhost)
	by windsor.research.att.com (8.11.6+Sun/8.8.5) id hAC015t26578;
	Tue, 11 Nov 2003 16:01:05 -0800 (PST)
Message-Id: <200311120001.hAC015t26578@windsor.research.att.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
To: shiroko.nr@ncos.nec.co.jp
Subject: Re: [pim] Query regarding the fragmentation for Register message
Cc: pim@ietf.org
Date: Tue, 11 Nov 2003 16:01:02 -0800
Versions: dmail (solaris) 2.5a/makemail 2.9d
Sender: pim-admin@ietf.org
Errors-To: pim-admin@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Id: Protocol Independent Multicast <pim.ietf.org>
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>


Shiroko,

  You are right; if the MTU of the DR->RP path is 1280 then the DR
may not send an ICMP fragmentation required error.  The idea behind
having the fragmentation occur inside the tunnel is to prevent
the RP from being overloaded with reassembly load.

  One possible way to handle this is that if the DR->RP path MTU is
1288 or less then use fragmentation on the outer packet.  This leaves
the overhead on the end systems if possible and only moves it to the
RP when necessary.  However, it's a little obscure and possibly
confusing.  Anyone have any thoughts on this?

Thanks,
  Bill

_______________________________________________
pim mailing list
pim@ietf.org
https://www1.ietf.org/mailman/listinfo/pim



From pim-admin@ietf.org  Mon Nov 17 11:32:37 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA19124
	for <pim-archive@lists.ietf.org>; Mon, 17 Nov 2003 11:32:36 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ALmIC-00086m-Ot; Mon, 17 Nov 2003 11:32:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ALmI5-00086J-PK
	for pim@optimus.ietf.org; Mon, 17 Nov 2003 11:31:53 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA19076
	for <pim@ietf.org>; Mon, 17 Nov 2003 11:31:41 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ALmI4-00014z-00
	for pim@ietf.org; Mon, 17 Nov 2003 11:31:52 -0500
Received: from colo-dns-ext2.juniper.net ([207.17.137.64])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ALmI4-00014f-00
	for pim@ietf.org; Mon, 17 Nov 2003 11:31:52 -0500
Received: from merlot.juniper.net (merlot.juniper.net [172.17.27.10])
	by colo-dns-ext2.juniper.net (8.11.5/8.9.3) with ESMTP id hAHGTZF98845;
	Mon, 17 Nov 2003 08:29:45 -0800 (PST)
	(envelope-from pusateri@juniper.net)
Received: from juniper.net (garnet.juniper.net [172.17.28.17])
	by merlot.juniper.net (8.11.3/8.11.3) with ESMTP id hAHGTUt65426;
	Mon, 17 Nov 2003 08:29:30 -0800 (PST)
	(envelope-from pusateri@juniper.net)
Message-Id: <200311171629.hAHGTUt65426@merlot.juniper.net>
To: pim@ietf.org
cc: Alex Zinin <zinin@psg.com>, Bill Fenner <fenner@research.att.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <70418.1069086570.1@juniper.net>
Date: Mon, 17 Nov 2003 08:29:30 -0800
From: Tom Pusateri <pusateri@juniper.net>
Subject: [pim] WG Last Call - PIM Sparse Mode
Sender: pim-admin@ietf.org
Errors-To: pim-admin@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Id: Protocol Independent Multicast <pim.ietf.org>
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>

Today begins a Working Group Last Call for the PIM Sparse Mode Protocol
Specification. The last call runs 2 weeks from Monday, November 17th, 2003
to Monday, December 1st, 2003.

Please review this document and send comments either to the list or
directly to the authors.

If you have previously volunteered as a reviewer for this spec, please
submit your review comments by the end of the Last Call period.

The document can be found at
http://ietf.org/internet-drafts/draft-ietf-pim-sm-v2-new-08.txt

Thanks,
Tom & Liming

_______________________________________________
pim mailing list
pim@ietf.org
https://www1.ietf.org/mailman/listinfo/pim


From exim@www1.ietf.org  Mon Nov 17 11:32:38 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA19139
	for <pim-archive@odin.ietf.org>; Mon, 17 Nov 2003 11:32:38 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ALmIW-000889-7t
	for pim-archive@odin.ietf.org; Mon, 17 Nov 2003 11:32:20 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAHGWKDn031249
	for pim-archive@odin.ietf.org; Mon, 17 Nov 2003 11:32:20 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ALmIW-00087w-2H
	for pim-web-archive@optimus.ietf.org; Mon, 17 Nov 2003 11:32:20 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA19093
	for <pim-web-archive@ietf.org>; Mon, 17 Nov 2003 11:32:07 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ALmIV-00015L-00
	for pim-web-archive@ietf.org; Mon, 17 Nov 2003 11:32:19 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ALmIU-00015H-00
	for pim-web-archive@ietf.org; Mon, 17 Nov 2003 11:32:18 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ALmIC-00086m-Ot; Mon, 17 Nov 2003 11:32:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ALmI5-00086J-PK
	for pim@optimus.ietf.org; Mon, 17 Nov 2003 11:31:53 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA19076
	for <pim@ietf.org>; Mon, 17 Nov 2003 11:31:41 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ALmI4-00014z-00
	for pim@ietf.org; Mon, 17 Nov 2003 11:31:52 -0500
Received: from colo-dns-ext2.juniper.net ([207.17.137.64])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ALmI4-00014f-00
	for pim@ietf.org; Mon, 17 Nov 2003 11:31:52 -0500
Received: from merlot.juniper.net (merlot.juniper.net [172.17.27.10])
	by colo-dns-ext2.juniper.net (8.11.5/8.9.3) with ESMTP id hAHGTZF98845;
	Mon, 17 Nov 2003 08:29:45 -0800 (PST)
	(envelope-from pusateri@juniper.net)
Received: from juniper.net (garnet.juniper.net [172.17.28.17])
	by merlot.juniper.net (8.11.3/8.11.3) with ESMTP id hAHGTUt65426;
	Mon, 17 Nov 2003 08:29:30 -0800 (PST)
	(envelope-from pusateri@juniper.net)
Message-Id: <200311171629.hAHGTUt65426@merlot.juniper.net>
To: pim@ietf.org
cc: Alex Zinin <zinin@psg.com>, Bill Fenner <fenner@research.att.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <70418.1069086570.1@juniper.net>
Date: Mon, 17 Nov 2003 08:29:30 -0800
From: Tom Pusateri <pusateri@juniper.net>
Subject: [pim] WG Last Call - PIM Sparse Mode
Sender: pim-admin@ietf.org
Errors-To: pim-admin@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Id: Protocol Independent Multicast <pim.ietf.org>
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>

Today begins a Working Group Last Call for the PIM Sparse Mode Protocol
Specification. The last call runs 2 weeks from Monday, November 17th, 2003
to Monday, December 1st, 2003.

Please review this document and send comments either to the list or
directly to the authors.

If you have previously volunteered as a reviewer for this spec, please
submit your review comments by the end of the Last Call period.

The document can be found at
http://ietf.org/internet-drafts/draft-ietf-pim-sm-v2-new-08.txt

Thanks,
Tom & Liming

_______________________________________________
pim mailing list
pim@ietf.org
https://www1.ietf.org/mailman/listinfo/pim



From pim-admin@ietf.org  Wed Nov 19 06:55:33 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA13515
	for <pim-archive@lists.ietf.org>; Wed, 19 Nov 2003 06:55:33 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMQvG-00046l-05; Wed, 19 Nov 2003 06:55:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMQuG-00043f-V9
	for pim@optimus.ietf.org; Wed, 19 Nov 2003 06:54:03 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA13465
	for <pim@ietf.org>; Wed, 19 Nov 2003 06:53:45 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMQuC-0005hs-00
	for pim@ietf.org; Wed, 19 Nov 2003 06:53:56 -0500
Received: from catarina.usc.edu ([204.57.0.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMQu9-0005hh-00
	for pim@ietf.org; Wed, 19 Nov 2003 06:53:56 -0500
Received: from usc.edu (root@usc.edu [128.125.253.136])
	by catarina.usc.edu (8.12.9/8.12.9) with ESMTP id hAJBrOsp031465
	for <pim@catarina.usc.edu>; Wed, 19 Nov 2003 03:53:24 -0800 (PST)
	(envelope-from srinivas@mail15.com)
Received: from mcphail.usc.edu (mcphail.usc.edu [128.125.253.51])
	by usc.edu (8.9.3.1/8.9.3/usc) with SMTP
	id DAA20526 for <pim@catarina.usc.edu>; Wed, 19 Nov 2003 03:53:24 -0800 (PST)
Received: from www.mail15.com(62.118.249.44) by mcphail.usc.edu via csmap 
	 id 2c62a988_1a87_11d8_9bd2_0002b3c946b2_21303;
	Wed, 19 Nov 2003 03:54:48 -0800 (PST)
Received: (from cyrus@localhost)
	by www.mail15.com (8.12.6/8.12.6) id hAJBofkl066964;
	Wed, 19 Nov 2003 14:50:41 +0300 (MSK)
	(envelope-from srinivas@mail15.com)
Date: Wed, 19 Nov 2003 14:50:41 +0300 (MSK)
Message-Id: <200311191150.hAJBofkl066964@www.mail15.com>
From: srinivas <srinivas@mail15.com>
To: pim@catarina.usc.edu
Cc: shwetha@tasmannetworks.com, srini@tasmannetworks.com
MIME-Version: 1.0
Content-Type: text/plain; charset="koi8-r"
Content-Transfer-Encoding: 8bit
X-Originating-IP: [61.95.224.136]
Content-Transfer-Encoding: 8bit
Subject: [pim] Doubt regarding BSR & Bootstrap messages
Sender: pim-admin@ietf.org
Errors-To: pim-admin@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Id: Protocol Independent Multicast <pim.ietf.org>
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-Transfer-Encoding: 8bit

Hi all,
  
 Here is my Setup:-
   
R1<-------->R2
^
|
|
V
R3

In the above setup,
Enable PIM over all interfaces in R1, R2 & R3.
Enable BSR using Interface address in R1, say x.x.x.x, which is 
connected to R2. 
Let the R1 get elected as BSR using x.x.x.x.
Now bring the interface correspnding to x.x.x.x down.
you can note that BSMs are sent to R3 from R1.
But in R3, the BSMs get rejected since there is no route to 
x.x.x.x.

So, is it valid to send out Bootstrap Messages even when the 
corresponding interface is down?
What is the use if at all we are sending it?

Now considering the above scenario, R1 is "Elected" BSR even 
though all its BSMs are getting rejected.
R2 & R3 will not have BSR info. So, it is improper to display R1 
as "Elected" whereas none of the neighboring
routers know about the BSR.

Can any one explain about this behavior?

Thanks & regards,
Srinivas
Tasman Networks

_______________________________________________
pim mailing list
pim@ietf.org
https://www1.ietf.org/mailman/listinfo/pim


From exim@www1.ietf.org  Wed Nov 19 06:55:36 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA13533
	for <pim-archive@odin.ietf.org>; Wed, 19 Nov 2003 06:55:35 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMQvX-00048u-US
	for pim-archive@odin.ietf.org; Wed, 19 Nov 2003 06:55:21 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAJBtJIU015920
	for pim-archive@odin.ietf.org; Wed, 19 Nov 2003 06:55:19 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMQvX-00048h-L1
	for pim-web-archive@optimus.ietf.org; Wed, 19 Nov 2003 06:55:19 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA13478
	for <pim-web-archive@ietf.org>; Wed, 19 Nov 2003 06:55:04 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMQvT-0005ij-00
	for pim-web-archive@ietf.org; Wed, 19 Nov 2003 06:55:15 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMQvT-0005if-00
	for pim-web-archive@ietf.org; Wed, 19 Nov 2003 06:55:15 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMQvG-00046l-05; Wed, 19 Nov 2003 06:55:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMQuG-00043f-V9
	for pim@optimus.ietf.org; Wed, 19 Nov 2003 06:54:03 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA13465
	for <pim@ietf.org>; Wed, 19 Nov 2003 06:53:45 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMQuC-0005hs-00
	for pim@ietf.org; Wed, 19 Nov 2003 06:53:56 -0500
Received: from catarina.usc.edu ([204.57.0.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMQu9-0005hh-00
	for pim@ietf.org; Wed, 19 Nov 2003 06:53:56 -0500
Received: from usc.edu (root@usc.edu [128.125.253.136])
	by catarina.usc.edu (8.12.9/8.12.9) with ESMTP id hAJBrOsp031465
	for <pim@catarina.usc.edu>; Wed, 19 Nov 2003 03:53:24 -0800 (PST)
	(envelope-from srinivas@mail15.com)
Received: from mcphail.usc.edu (mcphail.usc.edu [128.125.253.51])
	by usc.edu (8.9.3.1/8.9.3/usc) with SMTP
	id DAA20526 for <pim@catarina.usc.edu>; Wed, 19 Nov 2003 03:53:24 -0800 (PST)
Received: from www.mail15.com(62.118.249.44) by mcphail.usc.edu via csmap 
	 id 2c62a988_1a87_11d8_9bd2_0002b3c946b2_21303;
	Wed, 19 Nov 2003 03:54:48 -0800 (PST)
Received: (from cyrus@localhost)
	by www.mail15.com (8.12.6/8.12.6) id hAJBofkl066964;
	Wed, 19 Nov 2003 14:50:41 +0300 (MSK)
	(envelope-from srinivas@mail15.com)
Date: Wed, 19 Nov 2003 14:50:41 +0300 (MSK)
Message-Id: <200311191150.hAJBofkl066964@www.mail15.com>
From: srinivas <srinivas@mail15.com>
To: pim@catarina.usc.edu
Cc: shwetha@tasmannetworks.com, srini@tasmannetworks.com
MIME-Version: 1.0
Content-Type: text/plain; charset="koi8-r"
Content-Transfer-Encoding: 8bit
X-Originating-IP: [61.95.224.136]
Content-Transfer-Encoding: 8bit
Subject: [pim] Doubt regarding BSR & Bootstrap messages
Sender: pim-admin@ietf.org
Errors-To: pim-admin@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Id: Protocol Independent Multicast <pim.ietf.org>
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-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

Hi all,
  
 Here is my Setup:-
   
R1<-------->R2
^
|
|
V
R3

In the above setup,
Enable PIM over all interfaces in R1, R2 & R3.
Enable BSR using Interface address in R1, say x.x.x.x, which is 
connected to R2. 
Let the R1 get elected as BSR using x.x.x.x.
Now bring the interface correspnding to x.x.x.x down.
you can note that BSMs are sent to R3 from R1.
But in R3, the BSMs get rejected since there is no route to 
x.x.x.x.

So, is it valid to send out Bootstrap Messages even when the 
corresponding interface is down?
What is the use if at all we are sending it?

Now considering the above scenario, R1 is "Elected" BSR even 
though all its BSMs are getting rejected.
R2 & R3 will not have BSR info. So, it is improper to display R1 
as "Elected" whereas none of the neighboring
routers know about the BSR.

Can any one explain about this behavior?

Thanks & regards,
Srinivas
Tasman Networks

_______________________________________________
pim mailing list
pim@ietf.org
https://www1.ietf.org/mailman/listinfo/pim



From pim-admin@ietf.org  Wed Nov 19 13:37:30 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA02159
	for <pim-archive@lists.ietf.org>; Wed, 19 Nov 2003 13:37:30 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMXCI-0006mI-0y; Wed, 19 Nov 2003 13:37:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMXC9-0006lL-8m
	for pim@optimus.ietf.org; Wed, 19 Nov 2003 13:36:53 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA02015
	for <pim@ietf.org>; Wed, 19 Nov 2003 13:36:39 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMXC7-0006FM-00
	for pim@ietf.org; Wed, 19 Nov 2003 13:36:51 -0500
Received: from catarina.usc.edu ([204.57.0.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMXC4-0006Dd-00
	for pim@ietf.org; Wed, 19 Nov 2003 13:36:50 -0500
Received: from usc.edu (root@usc.edu [128.125.253.136])
	by catarina.usc.edu (8.12.9/8.12.9) with ESMTP id hAJIaIsp032667
	for <pim@catarina.usc.edu>; Wed, 19 Nov 2003 10:36:18 -0800 (PST)
	(envelope-from bharat_joshi@infosys.com)
Received: from mcphil.usc.edu (mcphil.usc.edu [128.125.253.15])
	by usc.edu (8.9.3.1/8.9.3/usc) with SMTP
	id KAA05128 for <pim@catarina.usc.edu>; Wed, 19 Nov 2003 10:36:18 -0800 (PST)
Received: from bosgate01.itlinfosys.com(216.251.53.3) by mcphil.usc.edu via csmap 
	 id 8f9c2bd6_1abf_11d8_9b37_00304811e8ca_5000;
	Wed, 19 Nov 2003 10:38:26 -0800 (PST)
Received: from 192.168.200.83 by bosgate01.infosys.com (InterScan E-Mail VirusWall NT); Wed, 19 Nov 2003 13:30:40 -0500
Received: from BLRKECIMR01.ad.infosys.com ([192.168.200.58]) by INDHUBBHS03.ad.infosys.com with Microsoft SMTPSVC(5.0.2195.6713);
	 Thu, 20 Nov 2003 00:03:51 +0530
Received: from kecmsg06.ad.infosys.com ([192.168.200.75]) by BLRKECIMR01.ad.infosys.com with Microsoft SMTPSVC(5.0.2195.6713);
	 Thu, 20 Nov 2003 00:03:51 +0530
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: base64
Subject: RE: [pim] Doubt regarding BSR & Bootstrap messages
Date: Thu, 20 Nov 2003 00:03:50 +0530
Message-ID: <56E2573C375A414191118970BDE06A150ABE62D2@kecmsg06.ad.infosys.com>
Thread-Topic: [pim] Doubt regarding BSR & Bootstrap messages
Thread-Index: AcOuk/AwVWYwjkRnQYK8xot/cD9UlAANE+OY
From: "bharat_joshi" <bharat_joshi@infosys.com>
To: "srinivas" <srinivas@mail15.com>, <pim@catarina.usc.edu>
Cc: <shwetha@tasmannetworks.com>, <srini@tasmannetworks.com>
X-OriginalArrivalTime: 19 Nov 2003 18:33:51.0158 (UTC) FILETIME=[ADA82D60:01C3AECB]
Content-Transfer-Encoding: base64
Sender: pim-admin@ietf.org
Errors-To: pim-admin@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Id: Protocol Independent Multicast <pim.ietf.org>
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-Transfer-Encoding: base64

IA0KIEhlcmUgaXMgbXkgU2V0dXA6LQ0KICANClIxPC0tLS0tLS0tPlIyDQpeDQp8DQp8DQpWDQpS
Mw0KDQpJbiB0aGUgYWJvdmUgc2V0dXAsDQpFbmFibGUgUElNIG92ZXIgYWxsIGludGVyZmFjZXMg
aW4gUjEsIFIyICYgUjMuDQpFbmFibGUgQlNSIHVzaW5nIEludGVyZmFjZSBhZGRyZXNzIGluIFIx
LCBzYXkgeC54LngueCwgd2hpY2ggaXMNCmNvbm5lY3RlZCB0byBSMi4NCkxldCB0aGUgUjEgZ2V0
IGVsZWN0ZWQgYXMgQlNSIHVzaW5nIHgueC54LnguDQpOb3cgYnJpbmcgdGhlIGludGVyZmFjZSBj
b3JyZXNwbmRpbmcgdG8geC54LngueCBkb3duLg0KeW91IGNhbiBub3RlIHRoYXQgQlNNcyBhcmUg
c2VudCB0byBSMyBmcm9tIFIxLg0KQnV0IGluIFIzLCB0aGUgQlNNcyBnZXQgcmVqZWN0ZWQgc2lu
Y2UgdGhlcmUgaXMgbm8gcm91dGUgdG8NCngueC54LnguDQoNClNvLCBpcyBpdCB2YWxpZCB0byBz
ZW5kIG91dCBCb290c3RyYXAgTWVzc2FnZXMgZXZlbiB3aGVuIHRoZQ0KY29ycmVzcG9uZGluZyBp
bnRlcmZhY2UgaXMgZG93bj8NCldoYXQgaXMgdGhlIHVzZSBpZiBhdCBhbGwgd2UgYXJlIHNlbmRp
bmcgaXQ/DQoNCj4+PiA+Pj4NCkJoYXJhdDoNCiANCkNvdWxkIHlvdSBwbGVhc2UgZXhwbGFpbiB3
aHkgYSBzd2ljdGgvcm91dGVyIHdpbGwga2VlcCBzZW5kaW5nDQpCU01zIGV2ZW4gaWYgaXRzIGlu
dGVyZmFjZSBpcyBkb3duLg0KIA0KSXRzIHByb2JhYmx5IGEgd3JvbmcgY29uZmlndXJhdGlvbi4g
QmVjdWFzZSByb3V0ZSBmb3IgeW91ciBCU1IncyBJUA0KYWRkcmVzcyB3aWxsIG5vdCBiZSBhdmFp
bGFibGUgaW4gUjMncyB1bmljYXN0IHJvdXRpbmcgdGFibGUuDQogDQpBc3NpZ25pbmcgYW4gSVAg
YWRkcmVzcyBmb3IgQlNSIGFkZHJlc3MgY2FuIGJlIGltcGxlbWVudGF0aW9uIHNwZWNpZmljLg0K
SW4geW91ciBjYXNlLCBZb3UgY2FuIGNob29zZSB0aGUgQlNSIGFkZHJlc3MgaW5kZXBlbmRlbnQg
b2YgeW91ciBQSU0gDQppbnRlcmZhY2VzLiBUaGF0IGNvdWxkIGJlIGEgUk9UVUVSL1NXSVRDSCdz
IElQIGFkZHJlc3Mgd2hpY2ggbXVzdA0KYWx3YXlzIGJlIGRpc3RyaWJpdXRlZCB1c2luZyBVbmlj
YXN0IFJvdXRpbmcgcHJvdG9jb2wuDQogDQo8PDw8PDwNCg0KTm93IGNvbnNpZGVyaW5nIHRoZSBh
Ym92ZSBzY2VuYXJpbywgUjEgaXMgIkVsZWN0ZWQiIEJTUiBldmVuDQp0aG91Z2ggYWxsIGl0cyBC
U01zIGFyZSBnZXR0aW5nIHJlamVjdGVkLg0KUjIgJiBSMyB3aWxsIG5vdCBoYXZlIEJTUiBpbmZv
LiBTbywgaXQgaXMgaW1wcm9wZXIgdG8gZGlzcGxheSBSMQ0KYXMgIkVsZWN0ZWQiIHdoZXJlYXMg
bm9uZSBvZiB0aGUgbmVpZ2hib3JpbmcNCnJvdXRlcnMga25vdyBhYm91dCB0aGUgQlNSLg0KDQo+
Pj4+Pg0KQmhhcmF0Og0KIA0KUjEncyBCU00gd2lsbCBiZSBkaXNjYXJkZWQgaWYgdGhleSBjb21l
IHdpdGggYSB1bmljYXN0IGFkZHJlc3Mgd2hpY2gNClIzIGNhbiBub3QgcmVhY2ggdXNpbmcgdGhl
IHNhbWUgaW50ZXJmYWNlLg0KIA0KQnV0IGlmIFIxJ3MgQlNNcyBhcmUgZ2V0dGluZyBkaXNjYXJk
ZWQgLCBob3cgUjEgd2lsbCBiZSBlbGVjdGVkIGFzIEUtQlNSPw0KSWYgUjEgd2FzIGVsZWN0ZWQg
YXMgQlNSIGluIFIzLCBpdCB3aWxsIHRpbWVvdXQgYWZ0ZXIgQlMgdGltZW91dCBiZWNhdXNlIFIz
DQp3b3VsZCBub3QgcmVjZWl2ZSBhbnkgdmFsaWQgQlNNLiBOb3cgdGhlIGRlY2lzaW9uIHRvIGZs
dXNoIHRoZSBSUCBzZXQgaXMgDQpzdGlsbCBnb2luZyBvbiB0aGlzIGxpc3QuIEkgYW0gbm90IHN1
cmUgaWYgYW55IGNvbmNyZXRlIHRoaW5nIGhhcyBjb21lIG91dC4NCiANCkFmdGVyIHRoaXMgdGlt
ZW91dCwgSSB0aGluayBvbmx5IFIxIHdpbGwgc2hvdyBoaW1zZWxmIGFzIEUtQlNSLCByaWdodD8/
DQogDQpJIGhvcGUgdGhpcyBhbnN3ZXIgeW91ciBxdWVzdGlvbi4NCiANClBlb3BsZSwgcGxlYXNl
IGNvcnJlY3QgbWUgaWYgSSBhbSB3cm9uZy4NCiANClRoYW5rcyAmIFJlZ2FyZHMsDQpCaGFyYXQN
CiANCjw8PDw8DQoNCkNhbiBhbnkgb25lIGV4cGxhaW4gYWJvdXQgdGhpcyBiZWhhdmlvcj8NCg0K
VGhhbmtzICYgcmVnYXJkcywNClNyaW5pdmFzDQpUYXNtYW4gTmV0d29ya3MNCg0KX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCnBpbSBtYWlsaW5nIGxpc3QN
CnBpbUBpZXRmLm9yZw0KaHR0cHM6Ly93d3cxLmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vcGlt
IDxodHRwczovL3d3dzEuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9waW0+IA0KDQo=

_______________________________________________
pim mailing list
pim@ietf.org
https://www1.ietf.org/mailman/listinfo/pim


From exim@www1.ietf.org  Wed Nov 19 13:37:34 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA02183
	for <pim-archive@odin.ietf.org>; Wed, 19 Nov 2003 13:37:34 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMXCV-0006qK-HT
	for pim-archive@odin.ietf.org; Wed, 19 Nov 2003 13:37:17 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAJIbEAt026294
	for pim-archive@odin.ietf.org; Wed, 19 Nov 2003 13:37:14 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMXCT-0006q1-Vb
	for pim-web-archive@optimus.ietf.org; Wed, 19 Nov 2003 13:37:14 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA02061
	for <pim-web-archive@ietf.org>; Wed, 19 Nov 2003 13:37:00 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMXCR-0006HH-00
	for pim-web-archive@ietf.org; Wed, 19 Nov 2003 13:37:11 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMXCR-0006HD-00
	for pim-web-archive@ietf.org; Wed, 19 Nov 2003 13:37:11 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMXCI-0006mI-0y; Wed, 19 Nov 2003 13:37:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMXC9-0006lL-8m
	for pim@optimus.ietf.org; Wed, 19 Nov 2003 13:36:53 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA02015
	for <pim@ietf.org>; Wed, 19 Nov 2003 13:36:39 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMXC7-0006FM-00
	for pim@ietf.org; Wed, 19 Nov 2003 13:36:51 -0500
Received: from catarina.usc.edu ([204.57.0.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMXC4-0006Dd-00
	for pim@ietf.org; Wed, 19 Nov 2003 13:36:50 -0500
Received: from usc.edu (root@usc.edu [128.125.253.136])
	by catarina.usc.edu (8.12.9/8.12.9) with ESMTP id hAJIaIsp032667
	for <pim@catarina.usc.edu>; Wed, 19 Nov 2003 10:36:18 -0800 (PST)
	(envelope-from bharat_joshi@infosys.com)
Received: from mcphil.usc.edu (mcphil.usc.edu [128.125.253.15])
	by usc.edu (8.9.3.1/8.9.3/usc) with SMTP
	id KAA05128 for <pim@catarina.usc.edu>; Wed, 19 Nov 2003 10:36:18 -0800 (PST)
Received: from bosgate01.itlinfosys.com(216.251.53.3) by mcphil.usc.edu via csmap 
	 id 8f9c2bd6_1abf_11d8_9b37_00304811e8ca_5000;
	Wed, 19 Nov 2003 10:38:26 -0800 (PST)
Received: from 192.168.200.83 by bosgate01.infosys.com (InterScan E-Mail VirusWall NT); Wed, 19 Nov 2003 13:30:40 -0500
Received: from BLRKECIMR01.ad.infosys.com ([192.168.200.58]) by INDHUBBHS03.ad.infosys.com with Microsoft SMTPSVC(5.0.2195.6713);
	 Thu, 20 Nov 2003 00:03:51 +0530
Received: from kecmsg06.ad.infosys.com ([192.168.200.75]) by BLRKECIMR01.ad.infosys.com with Microsoft SMTPSVC(5.0.2195.6713);
	 Thu, 20 Nov 2003 00:03:51 +0530
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: base64
Subject: RE: [pim] Doubt regarding BSR & Bootstrap messages
Date: Thu, 20 Nov 2003 00:03:50 +0530
Message-ID: <56E2573C375A414191118970BDE06A150ABE62D2@kecmsg06.ad.infosys.com>
Thread-Topic: [pim] Doubt regarding BSR & Bootstrap messages
Thread-Index: AcOuk/AwVWYwjkRnQYK8xot/cD9UlAANE+OY
From: "bharat_joshi" <bharat_joshi@infosys.com>
To: "srinivas" <srinivas@mail15.com>, <pim@catarina.usc.edu>
Cc: <shwetha@tasmannetworks.com>, <srini@tasmannetworks.com>
X-OriginalArrivalTime: 19 Nov 2003 18:33:51.0158 (UTC) FILETIME=[ADA82D60:01C3AECB]
Content-Transfer-Encoding: base64
Sender: pim-admin@ietf.org
Errors-To: pim-admin@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Id: Protocol Independent Multicast <pim.ietf.org>
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-Transfer-Encoding: base64
Content-Transfer-Encoding: base64

IA0KIEhlcmUgaXMgbXkgU2V0dXA6LQ0KICANClIxPC0tLS0tLS0tPlIyDQpeDQp8DQp8DQpWDQpS
Mw0KDQpJbiB0aGUgYWJvdmUgc2V0dXAsDQpFbmFibGUgUElNIG92ZXIgYWxsIGludGVyZmFjZXMg
aW4gUjEsIFIyICYgUjMuDQpFbmFibGUgQlNSIHVzaW5nIEludGVyZmFjZSBhZGRyZXNzIGluIFIx
LCBzYXkgeC54LngueCwgd2hpY2ggaXMNCmNvbm5lY3RlZCB0byBSMi4NCkxldCB0aGUgUjEgZ2V0
IGVsZWN0ZWQgYXMgQlNSIHVzaW5nIHgueC54LnguDQpOb3cgYnJpbmcgdGhlIGludGVyZmFjZSBj
b3JyZXNwbmRpbmcgdG8geC54LngueCBkb3duLg0KeW91IGNhbiBub3RlIHRoYXQgQlNNcyBhcmUg
c2VudCB0byBSMyBmcm9tIFIxLg0KQnV0IGluIFIzLCB0aGUgQlNNcyBnZXQgcmVqZWN0ZWQgc2lu
Y2UgdGhlcmUgaXMgbm8gcm91dGUgdG8NCngueC54LnguDQoNClNvLCBpcyBpdCB2YWxpZCB0byBz
ZW5kIG91dCBCb290c3RyYXAgTWVzc2FnZXMgZXZlbiB3aGVuIHRoZQ0KY29ycmVzcG9uZGluZyBp
bnRlcmZhY2UgaXMgZG93bj8NCldoYXQgaXMgdGhlIHVzZSBpZiBhdCBhbGwgd2UgYXJlIHNlbmRp
bmcgaXQ/DQoNCj4+PiA+Pj4NCkJoYXJhdDoNCiANCkNvdWxkIHlvdSBwbGVhc2UgZXhwbGFpbiB3
aHkgYSBzd2ljdGgvcm91dGVyIHdpbGwga2VlcCBzZW5kaW5nDQpCU01zIGV2ZW4gaWYgaXRzIGlu
dGVyZmFjZSBpcyBkb3duLg0KIA0KSXRzIHByb2JhYmx5IGEgd3JvbmcgY29uZmlndXJhdGlvbi4g
QmVjdWFzZSByb3V0ZSBmb3IgeW91ciBCU1IncyBJUA0KYWRkcmVzcyB3aWxsIG5vdCBiZSBhdmFp
bGFibGUgaW4gUjMncyB1bmljYXN0IHJvdXRpbmcgdGFibGUuDQogDQpBc3NpZ25pbmcgYW4gSVAg
YWRkcmVzcyBmb3IgQlNSIGFkZHJlc3MgY2FuIGJlIGltcGxlbWVudGF0aW9uIHNwZWNpZmljLg0K
SW4geW91ciBjYXNlLCBZb3UgY2FuIGNob29zZSB0aGUgQlNSIGFkZHJlc3MgaW5kZXBlbmRlbnQg
b2YgeW91ciBQSU0gDQppbnRlcmZhY2VzLiBUaGF0IGNvdWxkIGJlIGEgUk9UVUVSL1NXSVRDSCdz
IElQIGFkZHJlc3Mgd2hpY2ggbXVzdA0KYWx3YXlzIGJlIGRpc3RyaWJpdXRlZCB1c2luZyBVbmlj
YXN0IFJvdXRpbmcgcHJvdG9jb2wuDQogDQo8PDw8PDwNCg0KTm93IGNvbnNpZGVyaW5nIHRoZSBh
Ym92ZSBzY2VuYXJpbywgUjEgaXMgIkVsZWN0ZWQiIEJTUiBldmVuDQp0aG91Z2ggYWxsIGl0cyBC
U01zIGFyZSBnZXR0aW5nIHJlamVjdGVkLg0KUjIgJiBSMyB3aWxsIG5vdCBoYXZlIEJTUiBpbmZv
LiBTbywgaXQgaXMgaW1wcm9wZXIgdG8gZGlzcGxheSBSMQ0KYXMgIkVsZWN0ZWQiIHdoZXJlYXMg
bm9uZSBvZiB0aGUgbmVpZ2hib3JpbmcNCnJvdXRlcnMga25vdyBhYm91dCB0aGUgQlNSLg0KDQo+
Pj4+Pg0KQmhhcmF0Og0KIA0KUjEncyBCU00gd2lsbCBiZSBkaXNjYXJkZWQgaWYgdGhleSBjb21l
IHdpdGggYSB1bmljYXN0IGFkZHJlc3Mgd2hpY2gNClIzIGNhbiBub3QgcmVhY2ggdXNpbmcgdGhl
IHNhbWUgaW50ZXJmYWNlLg0KIA0KQnV0IGlmIFIxJ3MgQlNNcyBhcmUgZ2V0dGluZyBkaXNjYXJk
ZWQgLCBob3cgUjEgd2lsbCBiZSBlbGVjdGVkIGFzIEUtQlNSPw0KSWYgUjEgd2FzIGVsZWN0ZWQg
YXMgQlNSIGluIFIzLCBpdCB3aWxsIHRpbWVvdXQgYWZ0ZXIgQlMgdGltZW91dCBiZWNhdXNlIFIz
DQp3b3VsZCBub3QgcmVjZWl2ZSBhbnkgdmFsaWQgQlNNLiBOb3cgdGhlIGRlY2lzaW9uIHRvIGZs
dXNoIHRoZSBSUCBzZXQgaXMgDQpzdGlsbCBnb2luZyBvbiB0aGlzIGxpc3QuIEkgYW0gbm90IHN1
cmUgaWYgYW55IGNvbmNyZXRlIHRoaW5nIGhhcyBjb21lIG91dC4NCiANCkFmdGVyIHRoaXMgdGlt
ZW91dCwgSSB0aGluayBvbmx5IFIxIHdpbGwgc2hvdyBoaW1zZWxmIGFzIEUtQlNSLCByaWdodD8/
DQogDQpJIGhvcGUgdGhpcyBhbnN3ZXIgeW91ciBxdWVzdGlvbi4NCiANClBlb3BsZSwgcGxlYXNl
IGNvcnJlY3QgbWUgaWYgSSBhbSB3cm9uZy4NCiANClRoYW5rcyAmIFJlZ2FyZHMsDQpCaGFyYXQN
CiANCjw8PDw8DQoNCkNhbiBhbnkgb25lIGV4cGxhaW4gYWJvdXQgdGhpcyBiZWhhdmlvcj8NCg0K
VGhhbmtzICYgcmVnYXJkcywNClNyaW5pdmFzDQpUYXNtYW4gTmV0d29ya3MNCg0KX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCnBpbSBtYWlsaW5nIGxpc3QN
CnBpbUBpZXRmLm9yZw0KaHR0cHM6Ly93d3cxLmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vcGlt
IDxodHRwczovL3d3dzEuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9waW0+IA0KDQo=

_______________________________________________
pim mailing list
pim@ietf.org
https://www1.ietf.org/mailman/listinfo/pim



From pim-admin@ietf.org  Wed Nov 19 15:30:47 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA10118
	for <pim-archive@lists.ietf.org>; Wed, 19 Nov 2003 15:30:47 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMYwh-0005lz-9n; Wed, 19 Nov 2003 15:29:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMYwG-0005XI-Vx
	for pim@optimus.ietf.org; Wed, 19 Nov 2003 15:28:37 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09882;
	Wed, 19 Nov 2003 15:28:23 -0500 (EST)
Message-Id: <200311192028.PAA09882@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: pim@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Wed, 19 Nov 2003 15:28:23 -0500
Subject: [pim] I-D ACTION:draft-ietf-pim-anycast-rp-00.txt
Sender: pim-admin@ietf.org
Errors-To: pim-admin@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Id: Protocol Independent Multicast <pim.ietf.org>
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>

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Protocol Independent Multicast Working Group of the IETF.

	Title		: Anycast-RP using PIM
	Author(s)	: D. Farinacci
	Filename	: draft-ietf-pim-anycast-rp-00.txt
	Pages		: 7
	Date		: 2003-11-19
	
This proposal allows Anycast-RP to be used inside a domain which runs
PIM only. There are no other multicast protocols required to support
Anycast-RP, such as MSDP, which has been used traditionally to solve
this problem.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pim-anycast-rp-00.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-pim-anycast-rp-00.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-pim-anycast-rp-00.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<2003-11-19144808.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-pim-anycast-rp-00.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-pim-anycast-rp-00.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2003-11-19144808.I-D@ietf.org>

--OtherAccess--

--NextPart--



_______________________________________________
pim mailing list
pim@ietf.org
https://www1.ietf.org/mailman/listinfo/pim


From pim-admin@ietf.org  Thu Nov 20 00:40:34 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA04978
	for <pim-archive@lists.ietf.org>; Thu, 20 Nov 2003 00:40:34 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMhXu-0005yM-0L; Thu, 20 Nov 2003 00:40:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMhXZ-0005xf-Oy
	for pim@optimus.ietf.org; Thu, 20 Nov 2003 00:39:42 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA04935
	for <pim@ietf.org>; Thu, 20 Nov 2003 00:39:27 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMhXX-0003tU-00
	for pim@ietf.org; Thu, 20 Nov 2003 00:39:39 -0500
Received: from catarina.usc.edu ([204.57.0.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMhXW-0003t4-00
	for pim@ietf.org; Thu, 20 Nov 2003 00:39:38 -0500
Received: from www.mail15.com (www.mail15.com [62.118.249.44])
	by catarina.usc.edu (8.12.9/8.12.9) with ESMTP id hAK5d8sp034665
	for <pim@catarina.usc.edu>; Wed, 19 Nov 2003 21:39:09 -0800 (PST)
	(envelope-from srinivas@mail15.com)
Received: (from cyrus@localhost)
	by www.mail15.com (8.12.6/8.12.6) id hAK5d3tb029915;
	Thu, 20 Nov 2003 08:39:03 +0300 (MSK)
	(envelope-from srinivas@mail15.com)
Date: Thu, 20 Nov 2003 08:39:03 +0300 (MSK)
Message-Id: <200311200539.hAK5d3tb029915@www.mail15.com>
From: srinivas <srinivas@mail15.com>
To: bharat_joshi <bharat_joshi@infosys.com>
Cc: srinivas <srinivas@mail15.com>, pim@catarina.usc.edu,
        shwetha@tasmannetworks.com, srini@tasmannetworks.com
MIME-Version: 1.0
Content-Type: text/plain; charset="koi8-r"
Content-Transfer-Encoding: 8bit
X-Originating-IP: [61.95.224.136]
Subject: RE: [pim] Doubt regarding BSR & Bootstrap messages
Content-Transfer-Encoding: 8bit
Sender: pim-admin@ietf.org
Errors-To: pim-admin@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Id: Protocol Independent Multicast <pim.ietf.org>
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-Transfer-Encoding: 8bit

Hi,
 My comments are inline.

>>>Bharat:
 
>>>Could you please explain why a swicth/router will keep sending
>>>BSMs even if its interface is down

This is what I am also precisely asking for.
Probably I was not clear in my first mail.
I feel BSMs should not be sent to R3 at all. BSMs will not be sent anyways 
to R2 since interface is down.

>>>Assigning an IP address for BSR address can be implementation specific.

Agreed, Since I am using Cisco & Tasman routers, I have to specify the 
interface/interface address as Candidate BSR.

>>>R1's BSM will be discarded if they come with a unicast address which
>>>R3 can not reach using the same interface.

Correct, my doubt is NOT "why BSMs are getting rejected in R3", but "Why R1 
is sending BSMs when corresponding interface is down, since all the BSMs are 
going to be rejected anyway" .

>>>But if R1's BSMs are getting discarded , how R1 will be elected as E-BSR?

R1 is elected BSR in R1 itself. R2 & R3 will not have info about BSR since 
R3 is rejects all the BSMs & R2 doesn't receive any.

Though my question is more implementation specific, I thought of posting 
this to the group since 
both Cisco router as well as Tasman router behaved in similar fashion,
and I didnt know where else to post this question.


Thanks,
Srinivas

 



 bharat_joshi <bharat_joshi@infosys.com>:

> 
 Here is my Setup:-

R1<-------->R2
^
|
|
V
R3

In the above setup,
Enable PIM over all interfaces in R1, R2 & R3.
Enable BSR using Interface address in R1, say x.x.x.x, which is
connected to R2.
Let the R1 get elected as BSR using x.x.x.x.
Now bring the interface correspnding to x.x.x.x down.
you can note that BSMs are sent to R3 from R1.
But in R3, the BSMs get rejected since there is no route to
x.x.x.x.

So, is it valid to send out Bootstrap Messages even when the
corresponding interface is down?
What is the use if at all we are sending it?

>>> >>>
Bharat:

Could you please explain why a swicth/router will keep sending
BSMs even if its interface is down.

Its probably a wrong configuration. Becuase route for your BSR's IP
address will not be available in R3's unicast routing table.

Assigning an IP address for BSR address can be implementation specific.
In your case, You can choose the BSR address independent of your PIM
interfaces. That could be a ROTUER/SWITCH's IP address which must
always be distribiuted using Unicast Routing protocol.

<<<<<<

Now considering the above scenario, R1 is "Elected" BSR even
though all its BSMs are getting rejected.
R2 & R3 will not have BSR info. So, it is improper to display R1
as "Elected" whereas none of the neighboring
routers know about the BSR.

>>>>>
Bharat:

R1's BSM will be discarded if they come with a unicast address which
R3 can not reach using the same interface.

But if R1's BSMs are getting discarded , how R1 will be elected as E-BSR?
If R1 was elected as BSR in R3, it will timeout after BS timeout because R3
would not receive any valid BSM. Now the decision to flush the RP set is
still going on this list. I am not sure if any concrete thing has come out.

After this timeout, I think only R1 will show himself as E-BSR, right??

I hope this answer your question.

People, please correct me if I am wrong.

Thanks & Regards,
Bharat

<<<<<

Can any one explain about this behavior?

Thanks & regards,
Srinivas
Tasman Networks

_______________________________________________
pim mailing list
pim@ietf.org
https://www1.ietf.org/mailman/listinfo/pim 
<https://www1.ietf.org/mailman/listinfo/pim>



_______________________________________________
pim mailing list
pim@ietf.org
https://www1.ietf.org/mailman/listinfo/pim


From exim@www1.ietf.org  Thu Nov 20 00:40:38 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA04993
	for <pim-archive@odin.ietf.org>; Thu, 20 Nov 2003 00:40:38 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMhYD-0005zp-0T
	for pim-archive@odin.ietf.org; Thu, 20 Nov 2003 00:40:22 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAK5eKD2023050
	for pim-archive@odin.ietf.org; Thu, 20 Nov 2003 00:40:20 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMhYB-0005zg-Ps
	for pim-web-archive@optimus.ietf.org; Thu, 20 Nov 2003 00:40:19 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA04950
	for <pim-web-archive@ietf.org>; Thu, 20 Nov 2003 00:40:05 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMhY9-0003tt-00
	for pim-web-archive@ietf.org; Thu, 20 Nov 2003 00:40:17 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMhY8-0003tq-00
	for pim-web-archive@ietf.org; Thu, 20 Nov 2003 00:40:16 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMhXu-0005yM-0L; Thu, 20 Nov 2003 00:40:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMhXZ-0005xf-Oy
	for pim@optimus.ietf.org; Thu, 20 Nov 2003 00:39:42 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA04935
	for <pim@ietf.org>; Thu, 20 Nov 2003 00:39:27 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMhXX-0003tU-00
	for pim@ietf.org; Thu, 20 Nov 2003 00:39:39 -0500
Received: from catarina.usc.edu ([204.57.0.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMhXW-0003t4-00
	for pim@ietf.org; Thu, 20 Nov 2003 00:39:38 -0500
Received: from www.mail15.com (www.mail15.com [62.118.249.44])
	by catarina.usc.edu (8.12.9/8.12.9) with ESMTP id hAK5d8sp034665
	for <pim@catarina.usc.edu>; Wed, 19 Nov 2003 21:39:09 -0800 (PST)
	(envelope-from srinivas@mail15.com)
Received: (from cyrus@localhost)
	by www.mail15.com (8.12.6/8.12.6) id hAK5d3tb029915;
	Thu, 20 Nov 2003 08:39:03 +0300 (MSK)
	(envelope-from srinivas@mail15.com)
Date: Thu, 20 Nov 2003 08:39:03 +0300 (MSK)
Message-Id: <200311200539.hAK5d3tb029915@www.mail15.com>
From: srinivas <srinivas@mail15.com>
To: bharat_joshi <bharat_joshi@infosys.com>
Cc: srinivas <srinivas@mail15.com>, pim@catarina.usc.edu,
        shwetha@tasmannetworks.com, srini@tasmannetworks.com
MIME-Version: 1.0
Content-Type: text/plain; charset="koi8-r"
Content-Transfer-Encoding: 8bit
X-Originating-IP: [61.95.224.136]
Subject: RE: [pim] Doubt regarding BSR & Bootstrap messages
Content-Transfer-Encoding: 8bit
Sender: pim-admin@ietf.org
Errors-To: pim-admin@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Id: Protocol Independent Multicast <pim.ietf.org>
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-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

Hi,
 My comments are inline.

>>>Bharat:
 
>>>Could you please explain why a swicth/router will keep sending
>>>BSMs even if its interface is down

This is what I am also precisely asking for.
Probably I was not clear in my first mail.
I feel BSMs should not be sent to R3 at all. BSMs will not be sent anyways 
to R2 since interface is down.

>>>Assigning an IP address for BSR address can be implementation specific.

Agreed, Since I am using Cisco & Tasman routers, I have to specify the 
interface/interface address as Candidate BSR.

>>>R1's BSM will be discarded if they come with a unicast address which
>>>R3 can not reach using the same interface.

Correct, my doubt is NOT "why BSMs are getting rejected in R3", but "Why R1 
is sending BSMs when corresponding interface is down, since all the BSMs are 
going to be rejected anyway" .

>>>But if R1's BSMs are getting discarded , how R1 will be elected as E-BSR?

R1 is elected BSR in R1 itself. R2 & R3 will not have info about BSR since 
R3 is rejects all the BSMs & R2 doesn't receive any.

Though my question is more implementation specific, I thought of posting 
this to the group since 
both Cisco router as well as Tasman router behaved in similar fashion,
and I didnt know where else to post this question.


Thanks,
Srinivas

 



 bharat_joshi <bharat_joshi@infosys.com>:

> 
 Here is my Setup:-

R1<-------->R2
^
|
|
V
R3

In the above setup,
Enable PIM over all interfaces in R1, R2 & R3.
Enable BSR using Interface address in R1, say x.x.x.x, which is
connected to R2.
Let the R1 get elected as BSR using x.x.x.x.
Now bring the interface correspnding to x.x.x.x down.
you can note that BSMs are sent to R3 from R1.
But in R3, the BSMs get rejected since there is no route to
x.x.x.x.

So, is it valid to send out Bootstrap Messages even when the
corresponding interface is down?
What is the use if at all we are sending it?

>>> >>>
Bharat:

Could you please explain why a swicth/router will keep sending
BSMs even if its interface is down.

Its probably a wrong configuration. Becuase route for your BSR's IP
address will not be available in R3's unicast routing table.

Assigning an IP address for BSR address can be implementation specific.
In your case, You can choose the BSR address independent of your PIM
interfaces. That could be a ROTUER/SWITCH's IP address which must
always be distribiuted using Unicast Routing protocol.

<<<<<<

Now considering the above scenario, R1 is "Elected" BSR even
though all its BSMs are getting rejected.
R2 & R3 will not have BSR info. So, it is improper to display R1
as "Elected" whereas none of the neighboring
routers know about the BSR.

>>>>>
Bharat:

R1's BSM will be discarded if they come with a unicast address which
R3 can not reach using the same interface.

But if R1's BSMs are getting discarded , how R1 will be elected as E-BSR?
If R1 was elected as BSR in R3, it will timeout after BS timeout because R3
would not receive any valid BSM. Now the decision to flush the RP set is
still going on this list. I am not sure if any concrete thing has come out.

After this timeout, I think only R1 will show himself as E-BSR, right??

I hope this answer your question.

People, please correct me if I am wrong.

Thanks & Regards,
Bharat

<<<<<

Can any one explain about this behavior?

Thanks & regards,
Srinivas
Tasman Networks

_______________________________________________
pim mailing list
pim@ietf.org
https://www1.ietf.org/mailman/listinfo/pim 
<https://www1.ietf.org/mailman/listinfo/pim>



_______________________________________________
pim mailing list
pim@ietf.org
https://www1.ietf.org/mailman/listinfo/pim



From pim-admin@ietf.org  Thu Nov 20 04:00:36 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA25741
	for <pim-archive@lists.ietf.org>; Thu, 20 Nov 2003 04:00:36 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMkfS-0002Z1-VF; Thu, 20 Nov 2003 04:00:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMkf3-0002Y8-3E
	for pim@optimus.ietf.org; Thu, 20 Nov 2003 03:59:37 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA25699
	for <pim@ietf.org>; Thu, 20 Nov 2003 03:59:24 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMkf1-00070I-00
	for pim@ietf.org; Thu, 20 Nov 2003 03:59:35 -0500
Received: from catarina.usc.edu ([204.57.0.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMkf0-000709-00
	for pim@ietf.org; Thu, 20 Nov 2003 03:59:34 -0500
Received: from zeus.corecess.com ([218.147.97.51])
	by catarina.usc.edu (8.12.9/8.12.9) with ESMTP id hAK8x2sp035187
	for <pim@catarina.usc.edu>; Thu, 20 Nov 2003 00:59:03 -0800 (PST)
	(envelope-from ganapath@Corecess.com)
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C3AF44.49694FC2"
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
Date: Thu, 20 Nov 2003 17:57:12 +0900
Message-ID: <37BAA3695E46C24A91128FB94F0CC3E06AC0CC@zeus>
Thread-Topic: query on maintaining secondary address list
Thread-Index: AcOvRElpgZME/52zQTuiATHBFbVTPg==
From: "Ganapathasaa" <ganapath@Corecess.com>
To: <pim@catarina.usc.edu>
Subject: [pim] query on maintaining secondary address list
Sender: pim-admin@ietf.org
Errors-To: pim-admin@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Id: Protocol Independent Multicast <pim.ietf.org>
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>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C3AF44.49694FC2
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: base64

SGksDQogDQpOZXcgUElNLVNNIGRyYWZ0IGRyYWZ0LWlldGYtcGltLXNtLXYyLW5ldy0wOC50eHQg
bWVudGlvbnMgYWJvdXQgIk1haW50YWluaW5nIFNlY29uZGFyeSBBZGRyZXNzIExpc3RzIiBpbiBz
ZWN0aW9uDQo0LjMuNC4gSSBhbSBub3QgcXVpdGUgY2xlYXIgd2h5IGRvIHdlIG5lZWQgdG8gbWFp
bnRhaW4gc2Vjb25kYXJ5IGFkZHJlc3MgbGlzdHMgaW4gZmlyc3QgcGxhY2UuIElzIHRoaXMgaGVs
cGZ1bCBvbmx5IGluIGFsZXJ0aW5nIGFkbWluc3RyYXRvciBpbiBjYXNlIG9mIHdyb25nIGNvbmZp
Z3VyYXRpb25zPyBJdCBsb29rcyBsaWtlLCBuZXcgb3B0aW9uIGluY2x1ZGVkIGluIEhlbGxvIG1l
c3NhZ2UgaXMgdG8gZGlzdGluZ3Vpc2ggYW5kIHRvIG1ha2UgaW5kZXBlbmRlbnQgcHJvY2Vzc2lu
ZyBjaGVja3MgYXQgcHJpbWFyeSBhbmQgc2Vjb25kYXJ5IElQLiBBbnl3YXkgSSBhbSBub3QgY2xl
YXIsIHBsZWFzZSBzZW5kIHlvdXIgY29tbWVudHMgb24gdGhpcy4NCiANClRoYW54IGluIGFkdmFu
Y2UsDQpHYW5hcGF0aA0KLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NCkVuZ2lu
ZWVyLCBQcm90b2NvbCBUZWFtL1ImRCBDZW50ZXINCkNvcmVjZXNzIEluYywNCjUwMC0yLCBTYW5n
ZGFld29uLURvbmcsIEp1bmd3b24tS3UsDQpTZW9uZ25hbS1jaXR5LCBLeXVuZ2tpLWRvLA0KS29y
ZWEsIDQ2Mi0xMjANClRlbCkgODItMzEtNzM5LTY5MDcNCkZheCkgODItMzEtNzM5LTY4OTkNCnd3
dy5jb3JlY2Vzcy5jb20NCi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tIA0K

------_=_NextPart_001_01C3AF44.49694FC2
Content-Type: text/html;
	charset="utf-8"
Content-Transfer-Encoding: base64

PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBUcmFuc2l0aW9uYWwv
L0VOIj48SFRNTD48SEVBRD48TUVUQSBIVFRQLUVRVUlWPSJDb250ZW50LVR5cGUiIENPTlRFTlQ9
InRleHQvaHRtbDsgY2hhcnNldD11dGYtOCI+PC9IRUFEPjxCT0RZIHN0eWxlPSJGT05ULVNJWkU6
IDEwcHQiPgo8RElWPkhpLDwvRElWPgo8RElWPiZuYnNwOzwvRElWPgo8RElWPk5ldyBQSU0tU00g
ZHJhZnQgZHJhZnQtaWV0Zi1waW0tc20tdjItbmV3LTA4LnR4dCBtZW50aW9ucyBhYm91dCAKIk1h
aW50YWluaW5nIFNlY29uZGFyeSBBZGRyZXNzIExpc3RzIiBpbiBzZWN0aW9uPEJSPjQuMy40LiZu
YnNwO0kgYW0gbm90IHF1aXRlIApjbGVhciB3aHkgZG8gd2UgbmVlZCB0byBtYWludGFpbiBzZWNv
bmRhcnkgYWRkcmVzcyBsaXN0cyBpbiBmaXJzdCBwbGFjZS4gSXMgdGhpcyAKaGVscGZ1bCBvbmx5
IGluIGFsZXJ0aW5nIGFkbWluc3RyYXRvciBpbiBjYXNlIG9mIHdyb25nIGNvbmZpZ3VyYXRpb25z
PyBJdCBsb29rcyAKbGlrZSwmbmJzcDtuZXcgb3B0aW9uIGluY2x1ZGVkIGluIEhlbGxvIG1lc3Nh
Z2UgaXMgdG8gZGlzdGluZ3Vpc2ggYW5kIHRvIG1ha2UgCmluZGVwZW5kZW50IHByb2Nlc3Npbmcg
Y2hlY2tzIGF0IHByaW1hcnkgYW5kIHNlY29uZGFyeSBJUC4gQW55d2F5IEkgYW0gbm90IApjbGVh
ciwgcGxlYXNlJm5ic3A7c2VuZCB5b3VyJm5ic3A7Y29tbWVudHMgb24gdGhpcy48L0RJVj4KPERJ
Vj4mbmJzcDs8L0RJVj4KPERJVj5UaGFueCBpbiBhZHZhbmNlLDwvRElWPgo8RElWPkdhbmFwYXRo
PC9ESVY+CjxESVY+PFBSRT4tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLTxCUj5F
bmdpbmVlciwgUHJvdG9jb2wgVGVhbS9SJmFtcDtEIENlbnRlcjxCUj5Db3JlY2VzcyBJbmMsPEJS
PjUwMC0yLCBTYW5nZGFld29uLURvbmcsIEp1bmd3b24tS3UsPEJSPlNlb25nbmFtLWNpdHksIEt5
dW5na2ktZG8sPEJSPktvcmVhLCA0NjItMTIwPEJSPlRlbCkgODItMzEtNzM5LTY5MDc8QlI+RmF4
KSA4Mi0zMS03MzktNjg5OTxCUj53d3cuY29yZWNlc3MuY29tPEJSPi0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tJm5ic3A7PC9QUkU+PC9ESVY+PC9CT0RZPjwvSFRNTD4=

------_=_NextPart_001_01C3AF44.49694FC2--

_______________________________________________
pim mailing list
pim@ietf.org
https://www1.ietf.org/mailman/listinfo/pim


From exim@www1.ietf.org  Thu Nov 20 04:00:39 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA25756
	for <pim-archive@odin.ietf.org>; Thu, 20 Nov 2003 04:00:39 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMkfl-0002b5-DD
	for pim-archive@odin.ietf.org; Thu, 20 Nov 2003 04:00:21 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAK90LLk009982
	for pim-archive@odin.ietf.org; Thu, 20 Nov 2003 04:00:21 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMkfj-0002ar-Dw
	for pim-web-archive@optimus.ietf.org; Thu, 20 Nov 2003 04:00:19 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA25728
	for <pim-web-archive@ietf.org>; Thu, 20 Nov 2003 04:00:06 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMkfh-00070f-00
	for pim-web-archive@ietf.org; Thu, 20 Nov 2003 04:00:17 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMkfh-00070c-00
	for pim-web-archive@ietf.org; Thu, 20 Nov 2003 04:00:17 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMkfS-0002Z1-VF; Thu, 20 Nov 2003 04:00:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMkf3-0002Y8-3E
	for pim@optimus.ietf.org; Thu, 20 Nov 2003 03:59:37 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA25699
	for <pim@ietf.org>; Thu, 20 Nov 2003 03:59:24 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMkf1-00070I-00
	for pim@ietf.org; Thu, 20 Nov 2003 03:59:35 -0500
Received: from catarina.usc.edu ([204.57.0.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMkf0-000709-00
	for pim@ietf.org; Thu, 20 Nov 2003 03:59:34 -0500
Received: from zeus.corecess.com ([218.147.97.51])
	by catarina.usc.edu (8.12.9/8.12.9) with ESMTP id hAK8x2sp035187
	for <pim@catarina.usc.edu>; Thu, 20 Nov 2003 00:59:03 -0800 (PST)
	(envelope-from ganapath@Corecess.com)
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C3AF44.49694FC2"
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
Date: Thu, 20 Nov 2003 17:57:12 +0900
Message-ID: <37BAA3695E46C24A91128FB94F0CC3E06AC0CC@zeus>
Thread-Topic: query on maintaining secondary address list
Thread-Index: AcOvRElpgZME/52zQTuiATHBFbVTPg==
From: "Ganapathasaa" <ganapath@Corecess.com>
To: <pim@catarina.usc.edu>
Subject: [pim] query on maintaining secondary address list
Sender: pim-admin@ietf.org
Errors-To: pim-admin@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Id: Protocol Independent Multicast <pim.ietf.org>
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>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C3AF44.49694FC2
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: base64

SGksDQogDQpOZXcgUElNLVNNIGRyYWZ0IGRyYWZ0LWlldGYtcGltLXNtLXYyLW5ldy0wOC50eHQg
bWVudGlvbnMgYWJvdXQgIk1haW50YWluaW5nIFNlY29uZGFyeSBBZGRyZXNzIExpc3RzIiBpbiBz
ZWN0aW9uDQo0LjMuNC4gSSBhbSBub3QgcXVpdGUgY2xlYXIgd2h5IGRvIHdlIG5lZWQgdG8gbWFp
bnRhaW4gc2Vjb25kYXJ5IGFkZHJlc3MgbGlzdHMgaW4gZmlyc3QgcGxhY2UuIElzIHRoaXMgaGVs
cGZ1bCBvbmx5IGluIGFsZXJ0aW5nIGFkbWluc3RyYXRvciBpbiBjYXNlIG9mIHdyb25nIGNvbmZp
Z3VyYXRpb25zPyBJdCBsb29rcyBsaWtlLCBuZXcgb3B0aW9uIGluY2x1ZGVkIGluIEhlbGxvIG1l
c3NhZ2UgaXMgdG8gZGlzdGluZ3Vpc2ggYW5kIHRvIG1ha2UgaW5kZXBlbmRlbnQgcHJvY2Vzc2lu
ZyBjaGVja3MgYXQgcHJpbWFyeSBhbmQgc2Vjb25kYXJ5IElQLiBBbnl3YXkgSSBhbSBub3QgY2xl
YXIsIHBsZWFzZSBzZW5kIHlvdXIgY29tbWVudHMgb24gdGhpcy4NCiANClRoYW54IGluIGFkdmFu
Y2UsDQpHYW5hcGF0aA0KLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NCkVuZ2lu
ZWVyLCBQcm90b2NvbCBUZWFtL1ImRCBDZW50ZXINCkNvcmVjZXNzIEluYywNCjUwMC0yLCBTYW5n
ZGFld29uLURvbmcsIEp1bmd3b24tS3UsDQpTZW9uZ25hbS1jaXR5LCBLeXVuZ2tpLWRvLA0KS29y
ZWEsIDQ2Mi0xMjANClRlbCkgODItMzEtNzM5LTY5MDcNCkZheCkgODItMzEtNzM5LTY4OTkNCnd3
dy5jb3JlY2Vzcy5jb20NCi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tIA0K

------_=_NextPart_001_01C3AF44.49694FC2
Content-Type: text/html;
	charset="utf-8"
Content-Transfer-Encoding: base64

PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBUcmFuc2l0aW9uYWwv
L0VOIj48SFRNTD48SEVBRD48TUVUQSBIVFRQLUVRVUlWPSJDb250ZW50LVR5cGUiIENPTlRFTlQ9
InRleHQvaHRtbDsgY2hhcnNldD11dGYtOCI+PC9IRUFEPjxCT0RZIHN0eWxlPSJGT05ULVNJWkU6
IDEwcHQiPgo8RElWPkhpLDwvRElWPgo8RElWPiZuYnNwOzwvRElWPgo8RElWPk5ldyBQSU0tU00g
ZHJhZnQgZHJhZnQtaWV0Zi1waW0tc20tdjItbmV3LTA4LnR4dCBtZW50aW9ucyBhYm91dCAKIk1h
aW50YWluaW5nIFNlY29uZGFyeSBBZGRyZXNzIExpc3RzIiBpbiBzZWN0aW9uPEJSPjQuMy40LiZu
YnNwO0kgYW0gbm90IHF1aXRlIApjbGVhciB3aHkgZG8gd2UgbmVlZCB0byBtYWludGFpbiBzZWNv
bmRhcnkgYWRkcmVzcyBsaXN0cyBpbiBmaXJzdCBwbGFjZS4gSXMgdGhpcyAKaGVscGZ1bCBvbmx5
IGluIGFsZXJ0aW5nIGFkbWluc3RyYXRvciBpbiBjYXNlIG9mIHdyb25nIGNvbmZpZ3VyYXRpb25z
PyBJdCBsb29rcyAKbGlrZSwmbmJzcDtuZXcgb3B0aW9uIGluY2x1ZGVkIGluIEhlbGxvIG1lc3Nh
Z2UgaXMgdG8gZGlzdGluZ3Vpc2ggYW5kIHRvIG1ha2UgCmluZGVwZW5kZW50IHByb2Nlc3Npbmcg
Y2hlY2tzIGF0IHByaW1hcnkgYW5kIHNlY29uZGFyeSBJUC4gQW55d2F5IEkgYW0gbm90IApjbGVh
ciwgcGxlYXNlJm5ic3A7c2VuZCB5b3VyJm5ic3A7Y29tbWVudHMgb24gdGhpcy48L0RJVj4KPERJ
Vj4mbmJzcDs8L0RJVj4KPERJVj5UaGFueCBpbiBhZHZhbmNlLDwvRElWPgo8RElWPkdhbmFwYXRo
PC9ESVY+CjxESVY+PFBSRT4tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLTxCUj5F
bmdpbmVlciwgUHJvdG9jb2wgVGVhbS9SJmFtcDtEIENlbnRlcjxCUj5Db3JlY2VzcyBJbmMsPEJS
PjUwMC0yLCBTYW5nZGFld29uLURvbmcsIEp1bmd3b24tS3UsPEJSPlNlb25nbmFtLWNpdHksIEt5
dW5na2ktZG8sPEJSPktvcmVhLCA0NjItMTIwPEJSPlRlbCkgODItMzEtNzM5LTY5MDc8QlI+RmF4
KSA4Mi0zMS03MzktNjg5OTxCUj53d3cuY29yZWNlc3MuY29tPEJSPi0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tJm5ic3A7PC9QUkU+PC9ESVY+PC9CT0RZPjwvSFRNTD4=

------_=_NextPart_001_01C3AF44.49694FC2--

_______________________________________________
pim mailing list
pim@ietf.org
https://www1.ietf.org/mailman/listinfo/pim



From pim-admin@ietf.org  Thu Nov 20 04:15:28 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA26139
	for <pim-archive@lists.ietf.org>; Thu, 20 Nov 2003 04:15:28 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMktx-0003hN-IJ; Thu, 20 Nov 2003 04:15:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMkt7-0003bL-DI
	for pim@optimus.ietf.org; Thu, 20 Nov 2003 04:14:10 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA26023
	for <pim@ietf.org>; Thu, 20 Nov 2003 04:13:56 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMkt5-00079l-00
	for pim@ietf.org; Thu, 20 Nov 2003 04:14:07 -0500
Received: from catarina.usc.edu ([204.57.0.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMkt4-00079G-00
	for pim@ietf.org; Thu, 20 Nov 2003 04:14:06 -0500
Received: from fsnt.future.futsoft.com ([203.197.140.35])
	by catarina.usc.edu (8.12.9/8.12.9) with ESMTP id hAK9DVsp035243
	for <pim@catarina.usc.edu>; Thu, 20 Nov 2003 01:13:34 -0800 (PST)
	(envelope-from ketant@future.futsoft.com)
Received: from kailash.future.futsoft.com (unverified [203.197.140.36]) by 
    fsnt.future.futsoft.com (Content Technologies SMTPRS 4.3.6) with ESMTP id 
    <T660606000ecbc58c234c0@fsnt.future.futsoft.com>; Thu, 20 Nov 2003 
    14:48:40 +0530
Received: from future.futsoft.com (fsweb.future.futsoft.com [10.0.8.5]) by 
    kailash.future.futsoft.com (8.11.0/8.11.0) with SMTP id hAK9D6317845; Thu
    , 20 Nov 2003 14:43:08 +0530
Received: from 195.207.101.112 (SquirrelMail authenticated user ketant) by 
    fsweb.future.futsoft.com with HTTP; Thu, 20 Nov 2003 11:08:56 +0100 (CET)
Message-ID: 
    <53908.195.207.101.112.1069322936.squirrel@fsweb.future.futsoft.com>
Date: Thu, 20 Nov 2003 11:08:56 +0100 (CET)
Subject: RE: [pim] Doubt regarding BSR & Bootstrap messages
From: "Ketan TALAULIKAR" <ketant@future.futsoft.com>
To: <srinivas@mail15.com>
In-Reply-To: <200311200539.hAK5d3tb029915@www.mail15.com>
References: <200311200539.hAK5d3tb029915@www.mail15.com>
X-Priority: 3
Importance: Normal
Cc: <bharat_joshi@infosys.com>, <pim@catarina.usc.edu>,
        <shwetha@tasmannetworks.com>, <srini@tasmannetworks.com>
X-Mailer: SquirrelMail (version 1.2.10)
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit
Sender: pim-admin@ietf.org
Errors-To: pim-admin@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Id: Protocol Independent Multicast <pim.ietf.org>
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-Transfer-Encoding: 8bit

Hi Srinivas,

Indeed the question is implementation specific and in this case, I feel
the implementations you mentioned are incorrect. The BSR address used must
be reachable (and configured to be advertised via routing) for it to be
used for originating BSM.

Some implementations allow use of a loopback address (with no dependency
on running PIM over that interface) for BSR. This makes the BSR
independent of a specific router interface - same reason that loopback
addresses are used for other router configurations.

Best regards,
Ketan
-- 
Ketan TALAULIKAR
FutureSoft
www.futsoft.com
Work: +32-3-240-8997  GSM: +32-485-370445

srinivas said:
> Hi,
>  My comments are inline.
>
>>>>Bharat:
>
>>>>Could you please explain why a swicth/router will keep sending
>>>>BSMs even if its interface is down
>
> This is what I am also precisely asking for.
> Probably I was not clear in my first mail.
> I feel BSMs should not be sent to R3 at all. BSMs will not be sent
> anyways  to R2 since interface is down.
>
>>>>Assigning an IP address for BSR address can be implementation
>>>> specific.
>
> Agreed, Since I am using Cisco & Tasman routers, I have to specify the
> interface/interface address as Candidate BSR.
>
>>>>R1's BSM will be discarded if they come with a unicast address which
>>>> R3 can not reach using the same interface.
>
> Correct, my doubt is NOT "why BSMs are getting rejected in R3", but "Why
> R1  is sending BSMs when corresponding interface is down, since all the
> BSMs are  going to be rejected anyway" .
>
>>>>But if R1's BSMs are getting discarded , how R1 will be elected as
>>>> E-BSR?
>
> R1 is elected BSR in R1 itself. R2 & R3 will not have info about BSR
> since  R3 is rejects all the BSMs & R2 doesn't receive any.
>
> Though my question is more implementation specific, I thought of posting
>  this to the group since
> both Cisco router as well as Tasman router behaved in similar fashion,
> and I didnt know where else to post this question.
>
>
> Thanks,
> Srinivas
>
>
>
>
>
>  bharat_joshi <bharat_joshi@infosys.com>:
>
>>
>  Here is my Setup:-
>
> R1<-------->R2
> ^
> |
> |
> V
> R3
>
> In the above setup,
> Enable PIM over all interfaces in R1, R2 & R3.
> Enable BSR using Interface address in R1, say x.x.x.x, which is
> connected to R2.
> Let the R1 get elected as BSR using x.x.x.x.
> Now bring the interface correspnding to x.x.x.x down.
> you can note that BSMs are sent to R3 from R1.
> But in R3, the BSMs get rejected since there is no route to
> x.x.x.x.
>
> So, is it valid to send out Bootstrap Messages even when the
> corresponding interface is down?
> What is the use if at all we are sending it?
>
>>>> >>>
> Bharat:
>
> Could you please explain why a swicth/router will keep sending
> BSMs even if its interface is down.
>
> Its probably a wrong configuration. Becuase route for your BSR's IP
> address will not be available in R3's unicast routing table.
>
> Assigning an IP address for BSR address can be implementation specific.
> In your case, You can choose the BSR address independent of your PIM
> interfaces. That could be a ROTUER/SWITCH's IP address which must
> always be distribiuted using Unicast Routing protocol.
>
> <<<<<<
>
> Now considering the above scenario, R1 is "Elected" BSR even
> though all its BSMs are getting rejected.
> R2 & R3 will not have BSR info. So, it is improper to display R1
> as "Elected" whereas none of the neighboring
> routers know about the BSR.
>
>>>>>>
> Bharat:
>
> R1's BSM will be discarded if they come with a unicast address which R3
> can not reach using the same interface.
>
> But if R1's BSMs are getting discarded , how R1 will be elected as
> E-BSR? If R1 was elected as BSR in R3, it will timeout after BS timeout
> because R3 would not receive any valid BSM. Now the decision to flush
> the RP set is still going on this list. I am not sure if any concrete
> thing has come out.
>
> After this timeout, I think only R1 will show himself as E-BSR, right??
>
> I hope this answer your question.
>
> People, please correct me if I am wrong.
>
> Thanks & Regards,
> Bharat
>
> <<<<<
>
> Can any one explain about this behavior?
>
> Thanks & regards,
> Srinivas
> Tasman Networks
>
> _______________________________________________
> pim mailing list
> pim@ietf.org
> https://www1.ietf.org/mailman/listinfo/pim
> <https://www1.ietf.org/mailman/listinfo/pim>
>
>
>
> _______________________________________________
> pim mailing list
> pim@ietf.org
> https://www1.ietf.org/mailman/listinfo/pim





***************************************************************************
This message is proprietary to Future Software Limited (FSL)
and is intended solely for the use of the individual to whom it
is addressed. It may contain  privileged or confidential information
and should not be circulated or used for any purpose other than for
what it is intended.

If you have received this message in error, please notify the
originator immediately. If you are not the intended recipient,
you are notified that you are strictly prohibited from using,
copying, altering, or disclosing the contents of this message.
FSL accepts no responsibility for loss or damage arising from
the use of the information transmitted by this email including
damage from virus.
***************************************************************************


_______________________________________________
pim mailing list
pim@ietf.org
https://www1.ietf.org/mailman/listinfo/pim


From exim@www1.ietf.org  Thu Nov 20 04:15:32 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA26166
	for <pim-archive@odin.ietf.org>; Thu, 20 Nov 2003 04:15:32 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMku9-0003ki-GZ
	for pim-archive@odin.ietf.org; Thu, 20 Nov 2003 04:15:15 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAK9FDHU014416
	for pim-archive@odin.ietf.org; Thu, 20 Nov 2003 04:15:13 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMku8-0003kR-Jl
	for pim-web-archive@optimus.ietf.org; Thu, 20 Nov 2003 04:15:12 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA26123
	for <pim-web-archive@ietf.org>; Thu, 20 Nov 2003 04:14:59 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMku6-0007CF-00
	for pim-web-archive@ietf.org; Thu, 20 Nov 2003 04:15:10 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMku6-0007CC-00
	for pim-web-archive@ietf.org; Thu, 20 Nov 2003 04:15:10 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMktx-0003hN-IJ; Thu, 20 Nov 2003 04:15:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMkt7-0003bL-DI
	for pim@optimus.ietf.org; Thu, 20 Nov 2003 04:14:10 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA26023
	for <pim@ietf.org>; Thu, 20 Nov 2003 04:13:56 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMkt5-00079l-00
	for pim@ietf.org; Thu, 20 Nov 2003 04:14:07 -0500
Received: from catarina.usc.edu ([204.57.0.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMkt4-00079G-00
	for pim@ietf.org; Thu, 20 Nov 2003 04:14:06 -0500
Received: from fsnt.future.futsoft.com ([203.197.140.35])
	by catarina.usc.edu (8.12.9/8.12.9) with ESMTP id hAK9DVsp035243
	for <pim@catarina.usc.edu>; Thu, 20 Nov 2003 01:13:34 -0800 (PST)
	(envelope-from ketant@future.futsoft.com)
Received: from kailash.future.futsoft.com (unverified [203.197.140.36]) by 
    fsnt.future.futsoft.com (Content Technologies SMTPRS 4.3.6) with ESMTP id 
    <T660606000ecbc58c234c0@fsnt.future.futsoft.com>; Thu, 20 Nov 2003 
    14:48:40 +0530
Received: from future.futsoft.com (fsweb.future.futsoft.com [10.0.8.5]) by 
    kailash.future.futsoft.com (8.11.0/8.11.0) with SMTP id hAK9D6317845; Thu
    , 20 Nov 2003 14:43:08 +0530
Received: from 195.207.101.112 (SquirrelMail authenticated user ketant) by 
    fsweb.future.futsoft.com with HTTP; Thu, 20 Nov 2003 11:08:56 +0100 (CET)
Message-ID: 
    <53908.195.207.101.112.1069322936.squirrel@fsweb.future.futsoft.com>
Date: Thu, 20 Nov 2003 11:08:56 +0100 (CET)
Subject: RE: [pim] Doubt regarding BSR & Bootstrap messages
From: "Ketan TALAULIKAR" <ketant@future.futsoft.com>
To: <srinivas@mail15.com>
In-Reply-To: <200311200539.hAK5d3tb029915@www.mail15.com>
References: <200311200539.hAK5d3tb029915@www.mail15.com>
X-Priority: 3
Importance: Normal
Cc: <bharat_joshi@infosys.com>, <pim@catarina.usc.edu>,
        <shwetha@tasmannetworks.com>, <srini@tasmannetworks.com>
X-Mailer: SquirrelMail (version 1.2.10)
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit
Sender: pim-admin@ietf.org
Errors-To: pim-admin@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Id: Protocol Independent Multicast <pim.ietf.org>
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-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

Hi Srinivas,

Indeed the question is implementation specific and in this case, I feel
the implementations you mentioned are incorrect. The BSR address used must
be reachable (and configured to be advertised via routing) for it to be
used for originating BSM.

Some implementations allow use of a loopback address (with no dependency
on running PIM over that interface) for BSR. This makes the BSR
independent of a specific router interface - same reason that loopback
addresses are used for other router configurations.

Best regards,
Ketan
-- 
Ketan TALAULIKAR
FutureSoft
www.futsoft.com
Work: +32-3-240-8997  GSM: +32-485-370445

srinivas said:
> Hi,
>  My comments are inline.
>
>>>>Bharat:
>
>>>>Could you please explain why a swicth/router will keep sending
>>>>BSMs even if its interface is down
>
> This is what I am also precisely asking for.
> Probably I was not clear in my first mail.
> I feel BSMs should not be sent to R3 at all. BSMs will not be sent
> anyways  to R2 since interface is down.
>
>>>>Assigning an IP address for BSR address can be implementation
>>>> specific.
>
> Agreed, Since I am using Cisco & Tasman routers, I have to specify the
> interface/interface address as Candidate BSR.
>
>>>>R1's BSM will be discarded if they come with a unicast address which
>>>> R3 can not reach using the same interface.
>
> Correct, my doubt is NOT "why BSMs are getting rejected in R3", but "Why
> R1  is sending BSMs when corresponding interface is down, since all the
> BSMs are  going to be rejected anyway" .
>
>>>>But if R1's BSMs are getting discarded , how R1 will be elected as
>>>> E-BSR?
>
> R1 is elected BSR in R1 itself. R2 & R3 will not have info about BSR
> since  R3 is rejects all the BSMs & R2 doesn't receive any.
>
> Though my question is more implementation specific, I thought of posting
>  this to the group since
> both Cisco router as well as Tasman router behaved in similar fashion,
> and I didnt know where else to post this question.
>
>
> Thanks,
> Srinivas
>
>
>
>
>
>  bharat_joshi <bharat_joshi@infosys.com>:
>
>>
>  Here is my Setup:-
>
> R1<-------->R2
> ^
> |
> |
> V
> R3
>
> In the above setup,
> Enable PIM over all interfaces in R1, R2 & R3.
> Enable BSR using Interface address in R1, say x.x.x.x, which is
> connected to R2.
> Let the R1 get elected as BSR using x.x.x.x.
> Now bring the interface correspnding to x.x.x.x down.
> you can note that BSMs are sent to R3 from R1.
> But in R3, the BSMs get rejected since there is no route to
> x.x.x.x.
>
> So, is it valid to send out Bootstrap Messages even when the
> corresponding interface is down?
> What is the use if at all we are sending it?
>
>>>> >>>
> Bharat:
>
> Could you please explain why a swicth/router will keep sending
> BSMs even if its interface is down.
>
> Its probably a wrong configuration. Becuase route for your BSR's IP
> address will not be available in R3's unicast routing table.
>
> Assigning an IP address for BSR address can be implementation specific.
> In your case, You can choose the BSR address independent of your PIM
> interfaces. That could be a ROTUER/SWITCH's IP address which must
> always be distribiuted using Unicast Routing protocol.
>
> <<<<<<
>
> Now considering the above scenario, R1 is "Elected" BSR even
> though all its BSMs are getting rejected.
> R2 & R3 will not have BSR info. So, it is improper to display R1
> as "Elected" whereas none of the neighboring
> routers know about the BSR.
>
>>>>>>
> Bharat:
>
> R1's BSM will be discarded if they come with a unicast address which R3
> can not reach using the same interface.
>
> But if R1's BSMs are getting discarded , how R1 will be elected as
> E-BSR? If R1 was elected as BSR in R3, it will timeout after BS timeout
> because R3 would not receive any valid BSM. Now the decision to flush
> the RP set is still going on this list. I am not sure if any concrete
> thing has come out.
>
> After this timeout, I think only R1 will show himself as E-BSR, right??
>
> I hope this answer your question.
>
> People, please correct me if I am wrong.
>
> Thanks & Regards,
> Bharat
>
> <<<<<
>
> Can any one explain about this behavior?
>
> Thanks & regards,
> Srinivas
> Tasman Networks
>
> _______________________________________________
> pim mailing list
> pim@ietf.org
> https://www1.ietf.org/mailman/listinfo/pim
> <https://www1.ietf.org/mailman/listinfo/pim>
>
>
>
> _______________________________________________
> pim mailing list
> pim@ietf.org
> https://www1.ietf.org/mailman/listinfo/pim





***************************************************************************
This message is proprietary to Future Software Limited (FSL)
and is intended solely for the use of the individual to whom it
is addressed. It may contain  privileged or confidential information
and should not be circulated or used for any purpose other than for
what it is intended.

If you have received this message in error, please notify the
originator immediately. If you are not the intended recipient,
you are notified that you are strictly prohibited from using,
copying, altering, or disclosing the contents of this message.
FSL accepts no responsibility for loss or damage arising from
the use of the information transmitted by this email including
damage from virus.
***************************************************************************


_______________________________________________
pim mailing list
pim@ietf.org
https://www1.ietf.org/mailman/listinfo/pim



From pim-admin@ietf.org  Thu Nov 20 04:44:37 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA26853
	for <pim-archive@lists.ietf.org>; Thu, 20 Nov 2003 04:44:37 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMlM5-00056Z-3e; Thu, 20 Nov 2003 04:44:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMlLB-00055o-O2
	for pim@optimus.ietf.org; Thu, 20 Nov 2003 04:43:10 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA26785
	for <pim@ietf.org>; Thu, 20 Nov 2003 04:42:56 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMlL9-0007Xe-00
	for pim@ietf.org; Thu, 20 Nov 2003 04:43:07 -0500
Received: from catarina.usc.edu ([204.57.0.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMlL8-0007XM-00
	for pim@ietf.org; Thu, 20 Nov 2003 04:43:07 -0500
Received: from fsnt.future.futsoft.com ([203.197.140.35])
	by catarina.usc.edu (8.12.9/8.12.9) with ESMTP id hAK9gRsp035305
	for <pim@catarina.usc.edu>; Thu, 20 Nov 2003 01:42:32 -0800 (PST)
	(envelope-from ketant@future.futsoft.com)
Received: from kailash.future.futsoft.com (unverified [203.197.140.36]) by 
    fsnt.future.futsoft.com (Content Technologies SMTPRS 4.3.6) with ESMTP id 
    <T6606185df6cbc58c234c0@fsnt.future.futsoft.com>; Thu, 20 Nov 2003 
    15:08:44 +0530
Received: from future.futsoft.com (fsweb.future.futsoft.com [10.0.8.5]) by 
    kailash.future.futsoft.com (8.11.0/8.11.0) with SMTP id hAK9X7318939; Thu
    , 20 Nov 2003 15:03:07 +0530
Received: from 195.207.101.112 (SquirrelMail authenticated user ketant) by 
    fsweb.future.futsoft.com with HTTP; Thu, 20 Nov 2003 11:28:56 +0100 (CET)
Message-ID: 
    <33339.195.207.101.112.1069324136.squirrel@fsweb.future.futsoft.com>
Date: Thu, 20 Nov 2003 11:28:56 +0100 (CET)
Subject: RE: [pim] Doubt regarding BSR & Bootstrap messages
From: "Ketan TALAULIKAR" <ketant@future.futsoft.com>
To: <bharat_joshi@infosys.com>
In-Reply-To: 
    <56E2573C375A414191118970BDE06A150ABE62D2@kecmsg06.ad.infosys.com>
References: <56E2573C375A414191118970BDE06A150ABE62D2@kecmsg06.ad.infosys.com>
X-Priority: 3
Importance: Normal
Cc: <srinivas@mail15.com>, <pim@catarina.usc.edu>,
        <shwetha@tasmannetworks.com>, <srini@tasmannetworks.com>
X-Mailer: SquirrelMail (version 1.2.10)
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit
Sender: pim-admin@ietf.org
Errors-To: pim-admin@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Id: Protocol Independent Multicast <pim.ietf.org>
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-Transfer-Encoding: 8bit


> Assigning an IP address for BSR address can be implementation specific.
> In your case, You can choose the BSR address independent of your PIM
> interfaces. That could be a ROTUER/SWITCH's IP address which must
> always be distribiuted using Unicast Routing protocol.

Note that the current PIM MIB specs will not allow the use of IP address
other than of a PIM enabled interface since the CBSR preference
configuration is in the pimInterfaceTable.

But I agree with your views and feel its something which needs to be
corrected in the MIB. i.e. remove the dependency.

Also, I have a question here, does it make sense to use more than one
router interface as BSR address ? I believe the requirement would only be
of having one per PIM Component (or domain). Ofcourse, its possible that
with admin-scoped BSMs one can use different BSR addresses but I have seen
such usage running into problems when we have (most) implementations which
do not understand admin-scoped BSMs.

Best regards,
Ketan

-- 
Ketan TALAULIKAR
FutureSoft
www.futsoft.com
Work: +32-3-240-8997  GSM: +32-485-370445







***************************************************************************
This message is proprietary to Future Software Limited (FSL)
and is intended solely for the use of the individual to whom it
is addressed. It may contain  privileged or confidential information
and should not be circulated or used for any purpose other than for
what it is intended.

If you have received this message in error, please notify the
originator immediately. If you are not the intended recipient,
you are notified that you are strictly prohibited from using,
copying, altering, or disclosing the contents of this message.
FSL accepts no responsibility for loss or damage arising from
the use of the information transmitted by this email including
damage from virus.
***************************************************************************


_______________________________________________
pim mailing list
pim@ietf.org
https://www1.ietf.org/mailman/listinfo/pim


From exim@www1.ietf.org  Thu Nov 20 04:44:42 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA26874
	for <pim-archive@odin.ietf.org>; Thu, 20 Nov 2003 04:44:42 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMlMN-0005Bn-20
	for pim-archive@odin.ietf.org; Thu, 20 Nov 2003 04:44:25 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAK9iN3W019948
	for pim-archive@odin.ietf.org; Thu, 20 Nov 2003 04:44:23 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMlML-0005Bf-4x
	for pim-web-archive@optimus.ietf.org; Thu, 20 Nov 2003 04:44:21 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA26814
	for <pim-web-archive@ietf.org>; Thu, 20 Nov 2003 04:44:07 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMlMJ-0007Yb-00
	for pim-web-archive@ietf.org; Thu, 20 Nov 2003 04:44:19 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMlMI-0007YX-00
	for pim-web-archive@ietf.org; Thu, 20 Nov 2003 04:44:18 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMlM5-00056Z-3e; Thu, 20 Nov 2003 04:44:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMlLB-00055o-O2
	for pim@optimus.ietf.org; Thu, 20 Nov 2003 04:43:10 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA26785
	for <pim@ietf.org>; Thu, 20 Nov 2003 04:42:56 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMlL9-0007Xe-00
	for pim@ietf.org; Thu, 20 Nov 2003 04:43:07 -0500
Received: from catarina.usc.edu ([204.57.0.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMlL8-0007XM-00
	for pim@ietf.org; Thu, 20 Nov 2003 04:43:07 -0500
Received: from fsnt.future.futsoft.com ([203.197.140.35])
	by catarina.usc.edu (8.12.9/8.12.9) with ESMTP id hAK9gRsp035305
	for <pim@catarina.usc.edu>; Thu, 20 Nov 2003 01:42:32 -0800 (PST)
	(envelope-from ketant@future.futsoft.com)
Received: from kailash.future.futsoft.com (unverified [203.197.140.36]) by 
    fsnt.future.futsoft.com (Content Technologies SMTPRS 4.3.6) with ESMTP id 
    <T6606185df6cbc58c234c0@fsnt.future.futsoft.com>; Thu, 20 Nov 2003 
    15:08:44 +0530
Received: from future.futsoft.com (fsweb.future.futsoft.com [10.0.8.5]) by 
    kailash.future.futsoft.com (8.11.0/8.11.0) with SMTP id hAK9X7318939; Thu
    , 20 Nov 2003 15:03:07 +0530
Received: from 195.207.101.112 (SquirrelMail authenticated user ketant) by 
    fsweb.future.futsoft.com with HTTP; Thu, 20 Nov 2003 11:28:56 +0100 (CET)
Message-ID: 
    <33339.195.207.101.112.1069324136.squirrel@fsweb.future.futsoft.com>
Date: Thu, 20 Nov 2003 11:28:56 +0100 (CET)
Subject: RE: [pim] Doubt regarding BSR & Bootstrap messages
From: "Ketan TALAULIKAR" <ketant@future.futsoft.com>
To: <bharat_joshi@infosys.com>
In-Reply-To: 
    <56E2573C375A414191118970BDE06A150ABE62D2@kecmsg06.ad.infosys.com>
References: <56E2573C375A414191118970BDE06A150ABE62D2@kecmsg06.ad.infosys.com>
X-Priority: 3
Importance: Normal
Cc: <srinivas@mail15.com>, <pim@catarina.usc.edu>,
        <shwetha@tasmannetworks.com>, <srini@tasmannetworks.com>
X-Mailer: SquirrelMail (version 1.2.10)
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit
Sender: pim-admin@ietf.org
Errors-To: pim-admin@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Id: Protocol Independent Multicast <pim.ietf.org>
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-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit


> Assigning an IP address for BSR address can be implementation specific.
> In your case, You can choose the BSR address independent of your PIM
> interfaces. That could be a ROTUER/SWITCH's IP address which must
> always be distribiuted using Unicast Routing protocol.

Note that the current PIM MIB specs will not allow the use of IP address
other than of a PIM enabled interface since the CBSR preference
configuration is in the pimInterfaceTable.

But I agree with your views and feel its something which needs to be
corrected in the MIB. i.e. remove the dependency.

Also, I have a question here, does it make sense to use more than one
router interface as BSR address ? I believe the requirement would only be
of having one per PIM Component (or domain). Ofcourse, its possible that
with admin-scoped BSMs one can use different BSR addresses but I have seen
such usage running into problems when we have (most) implementations which
do not understand admin-scoped BSMs.

Best regards,
Ketan

-- 
Ketan TALAULIKAR
FutureSoft
www.futsoft.com
Work: +32-3-240-8997  GSM: +32-485-370445







***************************************************************************
This message is proprietary to Future Software Limited (FSL)
and is intended solely for the use of the individual to whom it
is addressed. It may contain  privileged or confidential information
and should not be circulated or used for any purpose other than for
what it is intended.

If you have received this message in error, please notify the
originator immediately. If you are not the intended recipient,
you are notified that you are strictly prohibited from using,
copying, altering, or disclosing the contents of this message.
FSL accepts no responsibility for loss or damage arising from
the use of the information transmitted by this email including
damage from virus.
***************************************************************************


_______________________________________________
pim mailing list
pim@ietf.org
https://www1.ietf.org/mailman/listinfo/pim



From pim-admin@ietf.org  Thu Nov 20 19:28:32 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA10592
	for <pim-archive@lists.ietf.org>; Thu, 20 Nov 2003 19:28:32 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMz9V-0000ez-P5; Thu, 20 Nov 2003 19:28:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMz8m-0000eZ-1J
	for pim@optimus.ietf.org; Thu, 20 Nov 2003 19:27:16 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA10465
	for <pim@ietf.org>; Thu, 20 Nov 2003 19:27:02 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMz8k-0007kc-00
	for pim@ietf.org; Thu, 20 Nov 2003 19:27:14 -0500
Received: from catarina.usc.edu ([204.57.0.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMz8j-0007if-00
	for pim@ietf.org; Thu, 20 Nov 2003 19:27:13 -0500
Received: from ghrr.org (jn-234-162.reachone.net [216.177.234.162])
	by catarina.usc.edu (8.12.9/8.12.9) with SMTP id hAL0Qhsp038089
	for <pim@catarina.usc.edu>; Thu, 20 Nov 2003 16:26:43 -0800 (PST)
	(envelope-from davison@cs.utk.edu)
Received: (qmail 11312 invoked from network); 21 Nov 2003 07:01:43 -0000
Received: from lytle.ghrr.org (192.168.1.173)
  by 0 with SMTP; 21 Nov 2003 07:01:43 -0000
Subject: Re: [pim] query on maintaining secondary address list
From: Mike Davison <davison@cs.utk.edu>
To: pim@catarina.usc.edu
In-Reply-To: <37BAA3695E46C24A91128FB94F0CC3E06AC0CC@zeus>
References: <37BAA3695E46C24A91128FB94F0CC3E06AC0CC@zeus>
Content-Type: text/plain
Message-Id: <1069374799.11146.841.camel@lytle.ghrr.org>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.4.4 
Date: Thu, 20 Nov 2003 16:33:19 -0800
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: pim-admin@ietf.org
Errors-To: pim-admin@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Id: Protocol Independent Multicast <pim.ietf.org>
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-Transfer-Encoding: 7bit


The secondary address list is needed for IPv6 support. PIM uses a
link-local IPv6 address when communicating with neighbors yet a
global-scope address is also needed.

Mike


On Thu, 2003-11-20 at 00:57, Ganapathasaa wrote:
> Hi,
>  
> New PIM-SM draft draft-ietf-pim-sm-v2-new-08.txt mentions about
> "Maintaining Secondary Address Lists" in section
> 4.3.4. I am not quite clear why do we need to maintain secondary
> address lists in first place. Is this helpful only in alerting
> adminstrator in case of wrong configurations? It looks like, new
> option included in Hello message is to distinguish and to make
> independent processing checks at primary and secondary IP. Anyway I am
> not clear, please send your comments on this.
>  
> Thanx in advance,
> Ganapath
> -----------------------------------
> Engineer, Protocol Team/R&D Center
> Corecess Inc,
> 500-2, Sangdaewon-Dong, Jungwon-Ku,
> Seongnam-city, Kyungki-do,
> Korea, 462-120
> Tel) 82-31-739-6907
> Fax) 82-31-739-6899
> www.corecess.com
> ----------------------------------- 


_______________________________________________
pim mailing list
pim@ietf.org
https://www1.ietf.org/mailman/listinfo/pim


From exim@www1.ietf.org  Thu Nov 20 19:28:33 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA10607
	for <pim-archive@odin.ietf.org>; Thu, 20 Nov 2003 19:28:33 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMz9l-0000gi-1J
	for pim-archive@odin.ietf.org; Thu, 20 Nov 2003 19:28:17 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAL0SHXj002640
	for pim-archive@odin.ietf.org; Thu, 20 Nov 2003 19:28:17 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMz9k-0000gV-SF
	for pim-web-archive@optimus.ietf.org; Thu, 20 Nov 2003 19:28:16 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA10562
	for <pim-web-archive@ietf.org>; Thu, 20 Nov 2003 19:28:02 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMz9j-0007mx-00
	for pim-web-archive@ietf.org; Thu, 20 Nov 2003 19:28:15 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMz9i-0007mt-00
	for pim-web-archive@ietf.org; Thu, 20 Nov 2003 19:28:14 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMz9V-0000ez-P5; Thu, 20 Nov 2003 19:28:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMz8m-0000eZ-1J
	for pim@optimus.ietf.org; Thu, 20 Nov 2003 19:27:16 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA10465
	for <pim@ietf.org>; Thu, 20 Nov 2003 19:27:02 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMz8k-0007kc-00
	for pim@ietf.org; Thu, 20 Nov 2003 19:27:14 -0500
Received: from catarina.usc.edu ([204.57.0.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMz8j-0007if-00
	for pim@ietf.org; Thu, 20 Nov 2003 19:27:13 -0500
Received: from ghrr.org (jn-234-162.reachone.net [216.177.234.162])
	by catarina.usc.edu (8.12.9/8.12.9) with SMTP id hAL0Qhsp038089
	for <pim@catarina.usc.edu>; Thu, 20 Nov 2003 16:26:43 -0800 (PST)
	(envelope-from davison@cs.utk.edu)
Received: (qmail 11312 invoked from network); 21 Nov 2003 07:01:43 -0000
Received: from lytle.ghrr.org (192.168.1.173)
  by 0 with SMTP; 21 Nov 2003 07:01:43 -0000
Subject: Re: [pim] query on maintaining secondary address list
From: Mike Davison <davison@cs.utk.edu>
To: pim@catarina.usc.edu
In-Reply-To: <37BAA3695E46C24A91128FB94F0CC3E06AC0CC@zeus>
References: <37BAA3695E46C24A91128FB94F0CC3E06AC0CC@zeus>
Content-Type: text/plain
Message-Id: <1069374799.11146.841.camel@lytle.ghrr.org>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.4.4 
Date: Thu, 20 Nov 2003 16:33:19 -0800
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: pim-admin@ietf.org
Errors-To: pim-admin@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Id: Protocol Independent Multicast <pim.ietf.org>
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-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


The secondary address list is needed for IPv6 support. PIM uses a
link-local IPv6 address when communicating with neighbors yet a
global-scope address is also needed.

Mike


On Thu, 2003-11-20 at 00:57, Ganapathasaa wrote:
> Hi,
>  
> New PIM-SM draft draft-ietf-pim-sm-v2-new-08.txt mentions about
> "Maintaining Secondary Address Lists" in section
> 4.3.4. I am not quite clear why do we need to maintain secondary
> address lists in first place. Is this helpful only in alerting
> adminstrator in case of wrong configurations? It looks like, new
> option included in Hello message is to distinguish and to make
> independent processing checks at primary and secondary IP. Anyway I am
> not clear, please send your comments on this.
>  
> Thanx in advance,
> Ganapath
> -----------------------------------
> Engineer, Protocol Team/R&D Center
> Corecess Inc,
> 500-2, Sangdaewon-Dong, Jungwon-Ku,
> Seongnam-city, Kyungki-do,
> Korea, 462-120
> Tel) 82-31-739-6907
> Fax) 82-31-739-6899
> www.corecess.com
> ----------------------------------- 


_______________________________________________
pim mailing list
pim@ietf.org
https://www1.ietf.org/mailman/listinfo/pim



From pim-admin@ietf.org  Sun Nov 23 20:53:30 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA07280
	for <pim-archive@lists.ietf.org>; Sun, 23 Nov 2003 20:53:29 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AO5uP-0005GH-Dr; Sun, 23 Nov 2003 20:53:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AO5uG-0005Fz-AB
	for pim@optimus.ietf.org; Sun, 23 Nov 2003 20:52:52 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA07266
	for <pim@ietf.org>; Sun, 23 Nov 2003 20:52:39 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AO5uD-0002go-00
	for pim@ietf.org; Sun, 23 Nov 2003 20:52:49 -0500
Received: from catarina.usc.edu ([204.57.0.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AO5uC-0002gk-00
	for pim@ietf.org; Sun, 23 Nov 2003 20:52:49 -0500
Received: from zeus.corecess.com ([218.147.97.51])
	by catarina.usc.edu (8.12.9/8.12.9) with ESMTP id hAO1qH8A005703
	for <pim@catarina.usc.edu>; Sun, 23 Nov 2003 17:52:18 -0800 (PST)
	(envelope-from ganapath@Corecess.com)
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C3B22D.4FF0771C"
Subject: RE: [pim] query on maintaining secondary address list
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
Date: Mon, 24 Nov 2003 10:50:18 +0900
Message-ID: <37BAA3695E46C24A91128FB94F0CC3E06AC0D3@zeus>
Thread-Topic: [pim] query on maintaining secondary address list
Thread-Index: AcOvxiImzzl2B/fASWiyD/c5p3p5eQCZv3GQ
From: "Ganapathasaa" <ganapath@Corecess.com>
To: "Mike Davison" <davison@cs.utk.edu>
Cc: <pim@catarina.usc.edu>
Sender: pim-admin@ietf.org
Errors-To: pim-admin@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Id: Protocol Independent Multicast <pim.ietf.org>
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>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C3B22D.4FF0771C
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: base64

SGksDQpJcyBpdCBub3Qgc2FtZSBldmVuIGluIElQdjQ/IFRoZSBvbmx5IHVzZSBJIGNhbiBzZWUg
ZnJvbSBtYWludGFpbmluZyBzZWNvbmRhcnkgSVAgYWRkcmVzcyBsaXN0IGlzLCB3ZSBjYW4gc2Vu
ZCBQSU0gam9pbnMgZGlyZWN0bHkgdG8gc2Vjb25kYXJ5IGFkZHJlc3MoaW4gcGxhY2Ugb2YgdXBz
dHJlYW0gbmVpZ2hib3IncyBhZGRyZXNzKWV2ZW4gaWYgd2UgZG9udCBoYXZlIHJvdXRpbmcgZW50
cnkoZm9yIHRoYXQgcGVydGljdWxhciBzZWNvbmRhcnkgYWRkcmVzcykgaW4gb3VyIHVuaWNhc3Qg
cm91dGluZyB0YWJsZS4gQnV0IGlzIHRoaXMgdGhlIHdvcmsgdG8gYmUgZG9uZSBieSBQSU0/IGFu
ZCBJIGZlZWwgdGhpcyBpcyBub3QgdGhlIHB1cnBvc2Ugb2YgbWFpbnRhaW5pbmcgc2Vjb25kYXJ5
IGFkZHJlc3MgbGlzdHMuIFN0aWxsIEkgYW0gbm90IGNsZWFyIGFib3V0IGluY2x1ZGluZyBhZGRy
ZXNzIGxpc3Qgb3B0aW9uIGluIEhlbGxvIG1lc3NhZ2VzLg0KUGxlYXNlIHNlbmQgeW91ciBjb21t
ZW50cyBvbiB0aGlzLA0KDQpSZWdhcmRzLA0KR2FuYXBhdGgNCg0KCS0tLS0tT3JpZ2luYWwgTWVz
c2FnZS0tLS0tIA0KCUZyb206IE1pa2UgRGF2aXNvbiBbbWFpbHRvOmRhdmlzb25AY3MudXRrLmVk
dV0gDQoJU2VudDogRnJpIDExLzIxLzIwMDMgOTozMyBBTSANCglUbzogcGltQGNhdGFyaW5hLnVz
Yy5lZHUgDQoJQ2M6IA0KCVN1YmplY3Q6IFJlOiBbcGltXSBxdWVyeSBvbiBtYWludGFpbmluZyBz
ZWNvbmRhcnkgYWRkcmVzcyBsaXN0DQoJDQoJDQoNCg0KCVRoZSBzZWNvbmRhcnkgYWRkcmVzcyBs
aXN0IGlzIG5lZWRlZCBmb3IgSVB2NiBzdXBwb3J0LiBQSU0gdXNlcyBhIA0KCWxpbmstbG9jYWwg
SVB2NiBhZGRyZXNzIHdoZW4gY29tbXVuaWNhdGluZyB3aXRoIG5laWdoYm9ycyB5ZXQgYSANCgln
bG9iYWwtc2NvcGUgYWRkcmVzcyBpcyBhbHNvIG5lZWRlZC4gDQoNCglNaWtlIA0KDQoNCglPbiBU
aHUsIDIwMDMtMTEtMjAgYXQgMDA6NTcsIEdhbmFwYXRoYXNhYSB3cm90ZTogDQoJPiBIaSwgDQoJ
PiAgDQoJPiBOZXcgUElNLVNNIGRyYWZ0IGRyYWZ0LWlldGYtcGltLXNtLXYyLW5ldy0wOC50eHQg
bWVudGlvbnMgYWJvdXQgDQoJPiAiTWFpbnRhaW5pbmcgU2Vjb25kYXJ5IEFkZHJlc3MgTGlzdHMi
IGluIHNlY3Rpb24gDQoJPiA0LjMuNC4gSSBhbSBub3QgcXVpdGUgY2xlYXIgd2h5IGRvIHdlIG5l
ZWQgdG8gbWFpbnRhaW4gc2Vjb25kYXJ5IA0KCT4gYWRkcmVzcyBsaXN0cyBpbiBmaXJzdCBwbGFj
ZS4gSXMgdGhpcyBoZWxwZnVsIG9ubHkgaW4gYWxlcnRpbmcgDQoJPiBhZG1pbnN0cmF0b3IgaW4g
Y2FzZSBvZiB3cm9uZyBjb25maWd1cmF0aW9ucz8gSXQgbG9va3MgbGlrZSwgbmV3IA0KCT4gb3B0
aW9uIGluY2x1ZGVkIGluIEhlbGxvIG1lc3NhZ2UgaXMgdG8gZGlzdGluZ3Vpc2ggYW5kIHRvIG1h
a2UgDQoJPiBpbmRlcGVuZGVudCBwcm9jZXNzaW5nIGNoZWNrcyBhdCBwcmltYXJ5IGFuZCBzZWNv
bmRhcnkgSVAuIEFueXdheSBJIGFtIA0KCT4gbm90IGNsZWFyLCBwbGVhc2Ugc2VuZCB5b3VyIGNv
bW1lbnRzIG9uIHRoaXMuIA0KCT4gIA0KCT4gVGhhbnggaW4gYWR2YW5jZSwgDQoJPiBHYW5hcGF0
aCANCgk+IC0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tIA0KCT4gRW5naW5lZXIs
IFByb3RvY29sIFRlYW0vUiZEIENlbnRlciANCgk+IENvcmVjZXNzIEluYywgDQoJPiA1MDAtMiwg
U2FuZ2RhZXdvbi1Eb25nLCBKdW5nd29uLUt1LCANCgk+IFNlb25nbmFtLWNpdHksIEt5dW5na2kt
ZG8sIA0KCT4gS29yZWEsIDQ2Mi0xMjAgDQoJPiBUZWwpIDgyLTMxLTczOS02OTA3IA0KCT4gRmF4
KSA4Mi0zMS03MzktNjg5OSANCgk+IHd3dy5jb3JlY2Vzcy5jb20gDQoJPiAtLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLSANCg0KDQoJX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX18gDQoJcGltIG1haWxpbmcgbGlzdCANCglwaW1AaWV0Zi5vcmcg
DQoJaHR0cHM6Ly93d3cxLmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vcGltIA0KDQogDQo=

------_=_NextPart_001_01C3B22D.4FF0771C
Content-Type: text/html;
	charset="utf-8"
Content-Transfer-Encoding: base64

PE1FVEEgSFRUUC1FUVVJVj0iQ29udGVudC1UeXBlIiBDT05URU5UPSJ0ZXh0L2h0bWw7IGNoYXJz
ZXQ9dXRmLTgiPgo8IURPQ1RZUEUgSFRNTCBQVUJMSUMgIi0vL1czQy8vRFREIEhUTUwgMy4yLy9F
TiI+CjxIVE1MPgo8SEVBRD4KCjxNRVRBIE5BTUU9IkdlbmVyYXRvciIgQ09OVEVOVD0iTVMgRXhj
aGFuZ2UgU2VydmVyIHZlcnNpb24gNi4wLjU3NjIuMyI+CjxUSVRMRT5SZTogW3BpbV0gcXVlcnkg
b24gbWFpbnRhaW5pbmcgc2Vjb25kYXJ5IGFkZHJlc3MgbGlzdDwvVElUTEU+CjwvSEVBRD4KPEJP
RFkgZGlyPWx0cj4KPERJVj5IaSw8L0RJVj4KPERJVj5JcyBpdCBub3Qgc2FtZSBldmVuIGluIElQ
djQ/IFRoZSBvbmx5IHVzZSBJIGNhbiBzZWUgZnJvbSBtYWludGFpbmluZyAKc2Vjb25kYXJ5IElQ
IGFkZHJlc3MgbGlzdCBpcywgd2UgY2FuIHNlbmQgUElNIGpvaW5zIGRpcmVjdGx5IHRvIHNlY29u
ZGFyeSAKYWRkcmVzcyhpbiBwbGFjZSBvZiB1cHN0cmVhbSBuZWlnaGJvcidzIGFkZHJlc3MpZXZl
biBpZiB3ZSBkb250IGhhdmUgcm91dGluZyAKZW50cnkoZm9yIHRoYXQgcGVydGljdWxhciBzZWNv
bmRhcnkgYWRkcmVzcykgaW4gb3VyIHVuaWNhc3Qgcm91dGluZyB0YWJsZS4gQnV0IAppcyB0aGlz
IHRoZSB3b3JrIHRvIGJlIGRvbmUgYnkgUElNPyBhbmQgSSBmZWVsIHRoaXMgaXMgbm90IHRoZSBw
dXJwb3NlIG9mIAptYWludGFpbmluZyBzZWNvbmRhcnkgYWRkcmVzcyBsaXN0cy4gU3RpbGwgSSBh
bSBub3QgY2xlYXIgYWJvdXQgaW5jbHVkaW5nIAphZGRyZXNzIGxpc3Qgb3B0aW9uIGluIEhlbGxv
IG1lc3NhZ2VzLjxCUj5QbGVhc2Ugc2VuZCB5b3VyIGNvbW1lbnRzIG9uIAp0aGlzLDwvRElWPgo8
RElWPjxCUj5SZWdhcmRzLDxCUj5HYW5hcGF0aDwvRElWPgo8QkxPQ0tRVU9URSBkaXI9bHRyIHN0
eWxlPSJNQVJHSU4tUklHSFQ6IDBweCI+CiAgPERJVj48Rk9OVCBzaXplPTI+LS0tLS1PcmlnaW5h
bCBNZXNzYWdlLS0tLS0gPEJSPjxCPkZyb206PC9CPiBNaWtlIERhdmlzb24gCiAgW21haWx0bzpk
YXZpc29uQGNzLnV0ay5lZHVdIDxCUj48Qj5TZW50OjwvQj4gRnJpIDExLzIxLzIwMDMgOTozMyBB
TSAKICA8QlI+PEI+VG86PC9CPiBwaW1AY2F0YXJpbmEudXNjLmVkdSA8QlI+PEI+Q2M6PC9CPiA8
QlI+PEI+U3ViamVjdDo8L0I+IFJlOiAKICBbcGltXSBxdWVyeSBvbiBtYWludGFpbmluZyBzZWNv
bmRhcnkgYWRkcmVzcyBsaXN0PEJSPjxCUj48L0ZPTlQ+PC9ESVY+PEJSPgogIDxQPjxGT05UIHNp
emU9Mj5UaGUgc2Vjb25kYXJ5IGFkZHJlc3MgbGlzdCBpcyBuZWVkZWQgZm9yIElQdjYgc3VwcG9y
dC4gUElNIAogIHVzZXMgYTwvRk9OVD4gPEJSPjxGT05UIHNpemU9Mj5saW5rLWxvY2FsIElQdjYg
YWRkcmVzcyB3aGVuIGNvbW11bmljYXRpbmcgd2l0aCAKICBuZWlnaGJvcnMgeWV0IGE8L0ZPTlQ+
IDxCUj48Rk9OVCBzaXplPTI+Z2xvYmFsLXNjb3BlIGFkZHJlc3MgaXMgYWxzbyAKICBuZWVkZWQu
PC9GT05UPiA8L1A+CiAgPFA+PEZPTlQgc2l6ZT0yPk1pa2U8L0ZPTlQ+IDwvUD48QlI+CiAgPFA+
PEZPTlQgc2l6ZT0yPk9uIFRodSwgMjAwMy0xMS0yMCBhdCAwMDo1NywgR2FuYXBhdGhhc2FhIHdy
b3RlOjwvRk9OVD4gCiAgPEJSPjxGT05UIHNpemU9Mj4mZ3Q7IEhpLDwvRk9OVD4gPEJSPjxGT05U
IHNpemU9Mj4mZ3Q7Jm5ic3A7IDwvRk9OVD48QlI+PEZPTlQgCiAgc2l6ZT0yPiZndDsgTmV3IFBJ
TS1TTSBkcmFmdCBkcmFmdC1pZXRmLXBpbS1zbS12Mi1uZXctMDgudHh0IG1lbnRpb25zIAogIGFi
b3V0PC9GT05UPiA8QlI+PEZPTlQgc2l6ZT0yPiZndDsgIk1haW50YWluaW5nIFNlY29uZGFyeSBB
ZGRyZXNzIExpc3RzIiBpbiAKICBzZWN0aW9uPC9GT05UPiA8QlI+PEZPTlQgc2l6ZT0yPiZndDsg
NC4zLjQuIEkgYW0gbm90IHF1aXRlIGNsZWFyIHdoeSBkbyB3ZSAKICBuZWVkIHRvIG1haW50YWlu
IHNlY29uZGFyeTwvRk9OVD4gPEJSPjxGT05UIHNpemU9Mj4mZ3Q7IGFkZHJlc3MgbGlzdHMgaW4g
Zmlyc3QgCiAgcGxhY2UuIElzIHRoaXMgaGVscGZ1bCBvbmx5IGluIGFsZXJ0aW5nPC9GT05UPiA8
QlI+PEZPTlQgc2l6ZT0yPiZndDsgCiAgYWRtaW5zdHJhdG9yIGluIGNhc2Ugb2Ygd3JvbmcgY29u
ZmlndXJhdGlvbnM/IEl0IGxvb2tzIGxpa2UsIG5ldzwvRk9OVD4gCiAgPEJSPjxGT05UIHNpemU9
Mj4mZ3Q7IG9wdGlvbiBpbmNsdWRlZCBpbiBIZWxsbyBtZXNzYWdlIGlzIHRvIGRpc3Rpbmd1aXNo
IGFuZCAKICB0byBtYWtlPC9GT05UPiA8QlI+PEZPTlQgc2l6ZT0yPiZndDsgaW5kZXBlbmRlbnQg
cHJvY2Vzc2luZyBjaGVja3MgYXQgcHJpbWFyeSAKICBhbmQgc2Vjb25kYXJ5IElQLiBBbnl3YXkg
SSBhbTwvRk9OVD4gPEJSPjxGT05UIHNpemU9Mj4mZ3Q7IG5vdCBjbGVhciwgcGxlYXNlIAogIHNl
bmQgeW91ciBjb21tZW50cyBvbiB0aGlzLjwvRk9OVD4gPEJSPjxGT05UIHNpemU9Mj4mZ3Q7Jm5i
c3A7IAogIDwvRk9OVD48QlI+PEZPTlQgc2l6ZT0yPiZndDsgVGhhbnggaW4gYWR2YW5jZSw8L0ZP
TlQ+IDxCUj48Rk9OVCBzaXplPTI+Jmd0OyAKICBHYW5hcGF0aDwvRk9OVD4gPEJSPjxGT05UIHNp
emU9Mj4mZ3Q7IAogIC0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tPC9GT05UPiA8
QlI+PEZPTlQgc2l6ZT0yPiZndDsgRW5naW5lZXIsIAogIFByb3RvY29sIFRlYW0vUiZhbXA7RCBD
ZW50ZXI8L0ZPTlQ+IDxCUj48Rk9OVCBzaXplPTI+Jmd0OyBDb3JlY2VzcyBJbmMsPC9GT05UPiAK
ICA8QlI+PEZPTlQgc2l6ZT0yPiZndDsgNTAwLTIsIFNhbmdkYWV3b24tRG9uZywgSnVuZ3dvbi1L
dSw8L0ZPTlQ+IDxCUj48Rk9OVCAKICBzaXplPTI+Jmd0OyBTZW9uZ25hbS1jaXR5LCBLeXVuZ2tp
LWRvLDwvRk9OVD4gPEJSPjxGT05UIHNpemU9Mj4mZ3Q7IEtvcmVhLCAKICA0NjItMTIwPC9GT05U
PiA8QlI+PEZPTlQgc2l6ZT0yPiZndDsgVGVsKSA4Mi0zMS03MzktNjkwNzwvRk9OVD4gPEJSPjxG
T05UIAogIHNpemU9Mj4mZ3Q7IEZheCkgODItMzEtNzM5LTY4OTk8L0ZPTlQ+IDxCUj48Rk9OVCBz
aXplPTI+Jmd0OyAKICB3d3cuY29yZWNlc3MuY29tPC9GT05UPiA8QlI+PEZPTlQgc2l6ZT0yPiZn
dDsgCiAgLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0gPC9GT05UPjwvUD48QlI+
CiAgPFA+PEZPTlQgc2l6ZT0yPl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fPC9GT05UPiAKICA8QlI+PEZPTlQgc2l6ZT0yPnBpbSBtYWlsaW5nIGxpc3Q8L0ZP
TlQ+IDxCUj48Rk9OVCBzaXplPTI+cGltQGlldGYub3JnPC9GT05UPiAKICA8QlI+PEZPTlQgc2l6
ZT0yPjxBIAogIGhyZWY9Imh0dHBzOi8vd3d3MS5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3Bp
bSI+aHR0cHM6Ly93d3cxLmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vcGltPC9BPjwvRk9OVD4g
CiAgPC9QPjwvQkxPQ0tRVU9URT4KPERJVj4mbmJzcDs8L0RJVj4KCjwvQk9EWT4KPC9IVE1MPg==

------_=_NextPart_001_01C3B22D.4FF0771C--

_______________________________________________
pim mailing list
pim@ietf.org
https://www1.ietf.org/mailman/listinfo/pim


From exim@www1.ietf.org  Sun Nov 23 20:53:32 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA07295
	for <pim-archive@odin.ietf.org>; Sun, 23 Nov 2003 20:53:32 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AO5ub-0005HY-Gv
	for pim-archive@odin.ietf.org; Sun, 23 Nov 2003 20:53:14 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAO1rD4T020298
	for pim-archive@odin.ietf.org; Sun, 23 Nov 2003 20:53:13 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AO5ub-0005HJ-C7
	for pim-web-archive@optimus.ietf.org; Sun, 23 Nov 2003 20:53:13 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA07275
	for <pim-web-archive@ietf.org>; Sun, 23 Nov 2003 20:53:00 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AO5uZ-0002gw-00
	for pim-web-archive@ietf.org; Sun, 23 Nov 2003 20:53:11 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AO5uY-0002gs-00
	for pim-web-archive@ietf.org; Sun, 23 Nov 2003 20:53:10 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AO5uP-0005GH-Dr; Sun, 23 Nov 2003 20:53:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AO5uG-0005Fz-AB
	for pim@optimus.ietf.org; Sun, 23 Nov 2003 20:52:52 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA07266
	for <pim@ietf.org>; Sun, 23 Nov 2003 20:52:39 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AO5uD-0002go-00
	for pim@ietf.org; Sun, 23 Nov 2003 20:52:49 -0500
Received: from catarina.usc.edu ([204.57.0.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AO5uC-0002gk-00
	for pim@ietf.org; Sun, 23 Nov 2003 20:52:49 -0500
Received: from zeus.corecess.com ([218.147.97.51])
	by catarina.usc.edu (8.12.9/8.12.9) with ESMTP id hAO1qH8A005703
	for <pim@catarina.usc.edu>; Sun, 23 Nov 2003 17:52:18 -0800 (PST)
	(envelope-from ganapath@Corecess.com)
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C3B22D.4FF0771C"
Subject: RE: [pim] query on maintaining secondary address list
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
Date: Mon, 24 Nov 2003 10:50:18 +0900
Message-ID: <37BAA3695E46C24A91128FB94F0CC3E06AC0D3@zeus>
Thread-Topic: [pim] query on maintaining secondary address list
Thread-Index: AcOvxiImzzl2B/fASWiyD/c5p3p5eQCZv3GQ
From: "Ganapathasaa" <ganapath@Corecess.com>
To: "Mike Davison" <davison@cs.utk.edu>
Cc: <pim@catarina.usc.edu>
Sender: pim-admin@ietf.org
Errors-To: pim-admin@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Id: Protocol Independent Multicast <pim.ietf.org>
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>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C3B22D.4FF0771C
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: base64

SGksDQpJcyBpdCBub3Qgc2FtZSBldmVuIGluIElQdjQ/IFRoZSBvbmx5IHVzZSBJIGNhbiBzZWUg
ZnJvbSBtYWludGFpbmluZyBzZWNvbmRhcnkgSVAgYWRkcmVzcyBsaXN0IGlzLCB3ZSBjYW4gc2Vu
ZCBQSU0gam9pbnMgZGlyZWN0bHkgdG8gc2Vjb25kYXJ5IGFkZHJlc3MoaW4gcGxhY2Ugb2YgdXBz
dHJlYW0gbmVpZ2hib3IncyBhZGRyZXNzKWV2ZW4gaWYgd2UgZG9udCBoYXZlIHJvdXRpbmcgZW50
cnkoZm9yIHRoYXQgcGVydGljdWxhciBzZWNvbmRhcnkgYWRkcmVzcykgaW4gb3VyIHVuaWNhc3Qg
cm91dGluZyB0YWJsZS4gQnV0IGlzIHRoaXMgdGhlIHdvcmsgdG8gYmUgZG9uZSBieSBQSU0/IGFu
ZCBJIGZlZWwgdGhpcyBpcyBub3QgdGhlIHB1cnBvc2Ugb2YgbWFpbnRhaW5pbmcgc2Vjb25kYXJ5
IGFkZHJlc3MgbGlzdHMuIFN0aWxsIEkgYW0gbm90IGNsZWFyIGFib3V0IGluY2x1ZGluZyBhZGRy
ZXNzIGxpc3Qgb3B0aW9uIGluIEhlbGxvIG1lc3NhZ2VzLg0KUGxlYXNlIHNlbmQgeW91ciBjb21t
ZW50cyBvbiB0aGlzLA0KDQpSZWdhcmRzLA0KR2FuYXBhdGgNCg0KCS0tLS0tT3JpZ2luYWwgTWVz
c2FnZS0tLS0tIA0KCUZyb206IE1pa2UgRGF2aXNvbiBbbWFpbHRvOmRhdmlzb25AY3MudXRrLmVk
dV0gDQoJU2VudDogRnJpIDExLzIxLzIwMDMgOTozMyBBTSANCglUbzogcGltQGNhdGFyaW5hLnVz
Yy5lZHUgDQoJQ2M6IA0KCVN1YmplY3Q6IFJlOiBbcGltXSBxdWVyeSBvbiBtYWludGFpbmluZyBz
ZWNvbmRhcnkgYWRkcmVzcyBsaXN0DQoJDQoJDQoNCg0KCVRoZSBzZWNvbmRhcnkgYWRkcmVzcyBs
aXN0IGlzIG5lZWRlZCBmb3IgSVB2NiBzdXBwb3J0LiBQSU0gdXNlcyBhIA0KCWxpbmstbG9jYWwg
SVB2NiBhZGRyZXNzIHdoZW4gY29tbXVuaWNhdGluZyB3aXRoIG5laWdoYm9ycyB5ZXQgYSANCgln
bG9iYWwtc2NvcGUgYWRkcmVzcyBpcyBhbHNvIG5lZWRlZC4gDQoNCglNaWtlIA0KDQoNCglPbiBU
aHUsIDIwMDMtMTEtMjAgYXQgMDA6NTcsIEdhbmFwYXRoYXNhYSB3cm90ZTogDQoJPiBIaSwgDQoJ
PiAgDQoJPiBOZXcgUElNLVNNIGRyYWZ0IGRyYWZ0LWlldGYtcGltLXNtLXYyLW5ldy0wOC50eHQg
bWVudGlvbnMgYWJvdXQgDQoJPiAiTWFpbnRhaW5pbmcgU2Vjb25kYXJ5IEFkZHJlc3MgTGlzdHMi
IGluIHNlY3Rpb24gDQoJPiA0LjMuNC4gSSBhbSBub3QgcXVpdGUgY2xlYXIgd2h5IGRvIHdlIG5l
ZWQgdG8gbWFpbnRhaW4gc2Vjb25kYXJ5IA0KCT4gYWRkcmVzcyBsaXN0cyBpbiBmaXJzdCBwbGFj
ZS4gSXMgdGhpcyBoZWxwZnVsIG9ubHkgaW4gYWxlcnRpbmcgDQoJPiBhZG1pbnN0cmF0b3IgaW4g
Y2FzZSBvZiB3cm9uZyBjb25maWd1cmF0aW9ucz8gSXQgbG9va3MgbGlrZSwgbmV3IA0KCT4gb3B0
aW9uIGluY2x1ZGVkIGluIEhlbGxvIG1lc3NhZ2UgaXMgdG8gZGlzdGluZ3Vpc2ggYW5kIHRvIG1h
a2UgDQoJPiBpbmRlcGVuZGVudCBwcm9jZXNzaW5nIGNoZWNrcyBhdCBwcmltYXJ5IGFuZCBzZWNv
bmRhcnkgSVAuIEFueXdheSBJIGFtIA0KCT4gbm90IGNsZWFyLCBwbGVhc2Ugc2VuZCB5b3VyIGNv
bW1lbnRzIG9uIHRoaXMuIA0KCT4gIA0KCT4gVGhhbnggaW4gYWR2YW5jZSwgDQoJPiBHYW5hcGF0
aCANCgk+IC0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tIA0KCT4gRW5naW5lZXIs
IFByb3RvY29sIFRlYW0vUiZEIENlbnRlciANCgk+IENvcmVjZXNzIEluYywgDQoJPiA1MDAtMiwg
U2FuZ2RhZXdvbi1Eb25nLCBKdW5nd29uLUt1LCANCgk+IFNlb25nbmFtLWNpdHksIEt5dW5na2kt
ZG8sIA0KCT4gS29yZWEsIDQ2Mi0xMjAgDQoJPiBUZWwpIDgyLTMxLTczOS02OTA3IA0KCT4gRmF4
KSA4Mi0zMS03MzktNjg5OSANCgk+IHd3dy5jb3JlY2Vzcy5jb20gDQoJPiAtLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLSANCg0KDQoJX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX18gDQoJcGltIG1haWxpbmcgbGlzdCANCglwaW1AaWV0Zi5vcmcg
DQoJaHR0cHM6Ly93d3cxLmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vcGltIA0KDQogDQo=

------_=_NextPart_001_01C3B22D.4FF0771C
Content-Type: text/html;
	charset="utf-8"
Content-Transfer-Encoding: base64

PE1FVEEgSFRUUC1FUVVJVj0iQ29udGVudC1UeXBlIiBDT05URU5UPSJ0ZXh0L2h0bWw7IGNoYXJz
ZXQ9dXRmLTgiPgo8IURPQ1RZUEUgSFRNTCBQVUJMSUMgIi0vL1czQy8vRFREIEhUTUwgMy4yLy9F
TiI+CjxIVE1MPgo8SEVBRD4KCjxNRVRBIE5BTUU9IkdlbmVyYXRvciIgQ09OVEVOVD0iTVMgRXhj
aGFuZ2UgU2VydmVyIHZlcnNpb24gNi4wLjU3NjIuMyI+CjxUSVRMRT5SZTogW3BpbV0gcXVlcnkg
b24gbWFpbnRhaW5pbmcgc2Vjb25kYXJ5IGFkZHJlc3MgbGlzdDwvVElUTEU+CjwvSEVBRD4KPEJP
RFkgZGlyPWx0cj4KPERJVj5IaSw8L0RJVj4KPERJVj5JcyBpdCBub3Qgc2FtZSBldmVuIGluIElQ
djQ/IFRoZSBvbmx5IHVzZSBJIGNhbiBzZWUgZnJvbSBtYWludGFpbmluZyAKc2Vjb25kYXJ5IElQ
IGFkZHJlc3MgbGlzdCBpcywgd2UgY2FuIHNlbmQgUElNIGpvaW5zIGRpcmVjdGx5IHRvIHNlY29u
ZGFyeSAKYWRkcmVzcyhpbiBwbGFjZSBvZiB1cHN0cmVhbSBuZWlnaGJvcidzIGFkZHJlc3MpZXZl
biBpZiB3ZSBkb250IGhhdmUgcm91dGluZyAKZW50cnkoZm9yIHRoYXQgcGVydGljdWxhciBzZWNv
bmRhcnkgYWRkcmVzcykgaW4gb3VyIHVuaWNhc3Qgcm91dGluZyB0YWJsZS4gQnV0IAppcyB0aGlz
IHRoZSB3b3JrIHRvIGJlIGRvbmUgYnkgUElNPyBhbmQgSSBmZWVsIHRoaXMgaXMgbm90IHRoZSBw
dXJwb3NlIG9mIAptYWludGFpbmluZyBzZWNvbmRhcnkgYWRkcmVzcyBsaXN0cy4gU3RpbGwgSSBh
bSBub3QgY2xlYXIgYWJvdXQgaW5jbHVkaW5nIAphZGRyZXNzIGxpc3Qgb3B0aW9uIGluIEhlbGxv
IG1lc3NhZ2VzLjxCUj5QbGVhc2Ugc2VuZCB5b3VyIGNvbW1lbnRzIG9uIAp0aGlzLDwvRElWPgo8
RElWPjxCUj5SZWdhcmRzLDxCUj5HYW5hcGF0aDwvRElWPgo8QkxPQ0tRVU9URSBkaXI9bHRyIHN0
eWxlPSJNQVJHSU4tUklHSFQ6IDBweCI+CiAgPERJVj48Rk9OVCBzaXplPTI+LS0tLS1PcmlnaW5h
bCBNZXNzYWdlLS0tLS0gPEJSPjxCPkZyb206PC9CPiBNaWtlIERhdmlzb24gCiAgW21haWx0bzpk
YXZpc29uQGNzLnV0ay5lZHVdIDxCUj48Qj5TZW50OjwvQj4gRnJpIDExLzIxLzIwMDMgOTozMyBB
TSAKICA8QlI+PEI+VG86PC9CPiBwaW1AY2F0YXJpbmEudXNjLmVkdSA8QlI+PEI+Q2M6PC9CPiA8
QlI+PEI+U3ViamVjdDo8L0I+IFJlOiAKICBbcGltXSBxdWVyeSBvbiBtYWludGFpbmluZyBzZWNv
bmRhcnkgYWRkcmVzcyBsaXN0PEJSPjxCUj48L0ZPTlQ+PC9ESVY+PEJSPgogIDxQPjxGT05UIHNp
emU9Mj5UaGUgc2Vjb25kYXJ5IGFkZHJlc3MgbGlzdCBpcyBuZWVkZWQgZm9yIElQdjYgc3VwcG9y
dC4gUElNIAogIHVzZXMgYTwvRk9OVD4gPEJSPjxGT05UIHNpemU9Mj5saW5rLWxvY2FsIElQdjYg
YWRkcmVzcyB3aGVuIGNvbW11bmljYXRpbmcgd2l0aCAKICBuZWlnaGJvcnMgeWV0IGE8L0ZPTlQ+
IDxCUj48Rk9OVCBzaXplPTI+Z2xvYmFsLXNjb3BlIGFkZHJlc3MgaXMgYWxzbyAKICBuZWVkZWQu
PC9GT05UPiA8L1A+CiAgPFA+PEZPTlQgc2l6ZT0yPk1pa2U8L0ZPTlQ+IDwvUD48QlI+CiAgPFA+
PEZPTlQgc2l6ZT0yPk9uIFRodSwgMjAwMy0xMS0yMCBhdCAwMDo1NywgR2FuYXBhdGhhc2FhIHdy
b3RlOjwvRk9OVD4gCiAgPEJSPjxGT05UIHNpemU9Mj4mZ3Q7IEhpLDwvRk9OVD4gPEJSPjxGT05U
IHNpemU9Mj4mZ3Q7Jm5ic3A7IDwvRk9OVD48QlI+PEZPTlQgCiAgc2l6ZT0yPiZndDsgTmV3IFBJ
TS1TTSBkcmFmdCBkcmFmdC1pZXRmLXBpbS1zbS12Mi1uZXctMDgudHh0IG1lbnRpb25zIAogIGFi
b3V0PC9GT05UPiA8QlI+PEZPTlQgc2l6ZT0yPiZndDsgIk1haW50YWluaW5nIFNlY29uZGFyeSBB
ZGRyZXNzIExpc3RzIiBpbiAKICBzZWN0aW9uPC9GT05UPiA8QlI+PEZPTlQgc2l6ZT0yPiZndDsg
NC4zLjQuIEkgYW0gbm90IHF1aXRlIGNsZWFyIHdoeSBkbyB3ZSAKICBuZWVkIHRvIG1haW50YWlu
IHNlY29uZGFyeTwvRk9OVD4gPEJSPjxGT05UIHNpemU9Mj4mZ3Q7IGFkZHJlc3MgbGlzdHMgaW4g
Zmlyc3QgCiAgcGxhY2UuIElzIHRoaXMgaGVscGZ1bCBvbmx5IGluIGFsZXJ0aW5nPC9GT05UPiA8
QlI+PEZPTlQgc2l6ZT0yPiZndDsgCiAgYWRtaW5zdHJhdG9yIGluIGNhc2Ugb2Ygd3JvbmcgY29u
ZmlndXJhdGlvbnM/IEl0IGxvb2tzIGxpa2UsIG5ldzwvRk9OVD4gCiAgPEJSPjxGT05UIHNpemU9
Mj4mZ3Q7IG9wdGlvbiBpbmNsdWRlZCBpbiBIZWxsbyBtZXNzYWdlIGlzIHRvIGRpc3Rpbmd1aXNo
IGFuZCAKICB0byBtYWtlPC9GT05UPiA8QlI+PEZPTlQgc2l6ZT0yPiZndDsgaW5kZXBlbmRlbnQg
cHJvY2Vzc2luZyBjaGVja3MgYXQgcHJpbWFyeSAKICBhbmQgc2Vjb25kYXJ5IElQLiBBbnl3YXkg
SSBhbTwvRk9OVD4gPEJSPjxGT05UIHNpemU9Mj4mZ3Q7IG5vdCBjbGVhciwgcGxlYXNlIAogIHNl
bmQgeW91ciBjb21tZW50cyBvbiB0aGlzLjwvRk9OVD4gPEJSPjxGT05UIHNpemU9Mj4mZ3Q7Jm5i
c3A7IAogIDwvRk9OVD48QlI+PEZPTlQgc2l6ZT0yPiZndDsgVGhhbnggaW4gYWR2YW5jZSw8L0ZP
TlQ+IDxCUj48Rk9OVCBzaXplPTI+Jmd0OyAKICBHYW5hcGF0aDwvRk9OVD4gPEJSPjxGT05UIHNp
emU9Mj4mZ3Q7IAogIC0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tPC9GT05UPiA8
QlI+PEZPTlQgc2l6ZT0yPiZndDsgRW5naW5lZXIsIAogIFByb3RvY29sIFRlYW0vUiZhbXA7RCBD
ZW50ZXI8L0ZPTlQ+IDxCUj48Rk9OVCBzaXplPTI+Jmd0OyBDb3JlY2VzcyBJbmMsPC9GT05UPiAK
ICA8QlI+PEZPTlQgc2l6ZT0yPiZndDsgNTAwLTIsIFNhbmdkYWV3b24tRG9uZywgSnVuZ3dvbi1L
dSw8L0ZPTlQ+IDxCUj48Rk9OVCAKICBzaXplPTI+Jmd0OyBTZW9uZ25hbS1jaXR5LCBLeXVuZ2tp
LWRvLDwvRk9OVD4gPEJSPjxGT05UIHNpemU9Mj4mZ3Q7IEtvcmVhLCAKICA0NjItMTIwPC9GT05U
PiA8QlI+PEZPTlQgc2l6ZT0yPiZndDsgVGVsKSA4Mi0zMS03MzktNjkwNzwvRk9OVD4gPEJSPjxG
T05UIAogIHNpemU9Mj4mZ3Q7IEZheCkgODItMzEtNzM5LTY4OTk8L0ZPTlQ+IDxCUj48Rk9OVCBz
aXplPTI+Jmd0OyAKICB3d3cuY29yZWNlc3MuY29tPC9GT05UPiA8QlI+PEZPTlQgc2l6ZT0yPiZn
dDsgCiAgLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0gPC9GT05UPjwvUD48QlI+
CiAgPFA+PEZPTlQgc2l6ZT0yPl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fPC9GT05UPiAKICA8QlI+PEZPTlQgc2l6ZT0yPnBpbSBtYWlsaW5nIGxpc3Q8L0ZP
TlQ+IDxCUj48Rk9OVCBzaXplPTI+cGltQGlldGYub3JnPC9GT05UPiAKICA8QlI+PEZPTlQgc2l6
ZT0yPjxBIAogIGhyZWY9Imh0dHBzOi8vd3d3MS5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3Bp
bSI+aHR0cHM6Ly93d3cxLmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vcGltPC9BPjwvRk9OVD4g
CiAgPC9QPjwvQkxPQ0tRVU9URT4KPERJVj4mbmJzcDs8L0RJVj4KCjwvQk9EWT4KPC9IVE1MPg==

------_=_NextPart_001_01C3B22D.4FF0771C--

_______________________________________________
pim mailing list
pim@ietf.org
https://www1.ietf.org/mailman/listinfo/pim



From pim-admin@ietf.org  Sun Nov 23 21:12:26 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA07733
	for <pim-archive@lists.ietf.org>; Sun, 23 Nov 2003 21:12:26 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AO6Cm-00065B-PF; Sun, 23 Nov 2003 21:12:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AO6Bz-00064h-9T
	for pim@optimus.ietf.org; Sun, 23 Nov 2003 21:11:11 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA07707
	for <pim@ietf.org>; Sun, 23 Nov 2003 21:10:58 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AO6Bw-0002sv-00
	for pim@ietf.org; Sun, 23 Nov 2003 21:11:08 -0500
Received: from catarina.usc.edu ([204.57.0.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AO6Bw-0002sM-00
	for pim@ietf.org; Sun, 23 Nov 2003 21:11:08 -0500
Received: from dmz2.procket.com (dmz2.procket.com [65.174.124.37])
	by catarina.usc.edu (8.12.9/8.12.9) with ESMTP id hAO2Ac8A005762
	for <pim@catarina.usc.edu>; Sun, 23 Nov 2003 18:10:38 -0800 (PST)
	(envelope-from John.Zwiebel@procket.com)
Received: from miata.procket.com (zeus-d-1.procket.com [65.174.124.60])
	by dmz2.procket.com (8.12.8p1/8.12.1) with ESMTP id hAO4FYOt082723;
	Sun, 23 Nov 2003 20:15:34 -0800 (PST)
Received: from exchangefe2.na.procket.com (email.na.procket.com [10.1.7.252])
	by miata.procket.com (8.12.1/8.12.1) with ESMTP id hAO2ARYB003179;
	Sun, 23 Nov 2003 18:10:27 -0800 (PST)
Received: from [127.0.0.1] ([10.1.1.1]) by exchangefe2.na.procket.com with Microsoft SMTPSVC(5.0.2195.6713);
	 Sun, 23 Nov 2003 18:10:27 -0800
In-Reply-To: <37BAA3695E46C24A91128FB94F0CC3E06AC0D3@zeus>
References: <37BAA3695E46C24A91128FB94F0CC3E06AC0D3@zeus>
Mime-Version: 1.0 (Apple Message framework v606)
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Message-Id: <F9483361-1E22-11D8-AA86-0003936A6062@procket.com>
Content-Transfer-Encoding: quoted-printable
Cc: "Mike Davison" <davison@cs.utk.edu>, <pim@catarina.usc.edu>
From: John Zwiebel <jzwiebel@procket.com>
Subject: Re: [pim] query on maintaining secondary address list
Date: Sun, 23 Nov 2003 18:07:36 -0800
To: "Ganapathasaa" <ganapath@Corecess.com>
X-Mailer: Apple Mail (2.606)
X-OriginalArrivalTime: 24 Nov 2003 02:10:27.0605 (UTC) FILETIME=[20DD3C50:01C3B230]
Content-Transfer-Encoding: quoted-printable
Sender: pim-admin@ietf.org
Errors-To: pim-admin@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Id: Protocol Independent Multicast <pim.ietf.org>
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-Transfer-Encoding: quoted-printable

There's a suz (for suzuki) draft that explains this in detail,
but in summary, the IPv6 addresses are used quite differently than
IPv4 addresses.

All the IGP's I'm aware of use the link-local address for the
next hop.  This makes it easy for PIM to find the next
upstream router because PIM6 also uses link-local addresses.

But there is nothing 'illegal' with using a global address
as the next hop, most likely in a static route.  In such a case,
(and also in the case where the PIM-RP (a global address) is on the
LAN over which a router wants to send a pim join) the downstream
router has no way of translating the global address next hop
to a link-local pim neighbor.

You're going to find several interesting things when
trying to do pim over ipv6.

On Nov 23, 2003, at 5:50 PM, Ganapathasaa wrote:

> Hi,
> Is it not same even in IPv4? The only use I can see from maintaining=20=

> secondary IP address list is, we can send PIM joins directly to=20
> secondary address(in place of upstream neighbor's address)even if we=20=

> dont have routing entry(for that perticular secondary address) in our=20=

> unicast routing table. But is this the work to be done by PIM? and I=20=

> feel this is not the purpose of maintaining secondary address lists.=20=

> Still I am not clear about including address list option in Hello=20
> messages.
> Please send your comments on this,
>
> Regards,
> Ganapath
> -----Original Message-----
> From:Mike Davison [mailto:davison@cs.utk.edu]
> Sent:Fri 11/21/2003 9:33 AM
> To:pim@catarina.usc.edu
> Cc:
> Subject:Re: [pim] query on maintaining secondary address list
>
>
>
>
> The secondary address list is needed for IPv6 support. PIM uses a
> link-local IPv6 address when communicating with neighbors yet a
> global-scope address is also needed.
>
> Mike
>
>
>
> On Thu, 2003-11-20 at 00:57, Ganapathasaa wrote:
> > Hi,
> >=A0
> > New PIM-SM draft draft-ietf-pim-sm-v2-new-08.txt mentions about
> > "Maintaining Secondary Address Lists" in section
> > 4.3.4. I am not quite clear why do we need to maintain secondary
> > address lists in first place. Is this helpful only in alerting
> > adminstrator in case of wrong configurations? It looks like, new
> > option included in Hello message is to distinguish and to make
> > independent processing checks at primary and secondary IP. Anyway I=20=

> am
> > not clear, please send your comments on this.
> >=A0
> > Thanx in advance,
> > Ganapath
> > -----------------------------------
> > Engineer, Protocol Team/R&D Center
> > Corecess Inc,
> > 500-2, Sangdaewon-Dong, Jungwon-Ku,
> > Seongnam-city, Kyungki-do,
> > Korea, 462-120
> > Tel) 82-31-739-6907
> > Fax) 82-31-739-6899
> > www.corecess.com
> > -----------------------------------
>
>
>
> _______________________________________________
> pim mailing list
> pim@ietf.org
> https://www1.ietf.org/mailman/listinfo/pim
> =A0


_______________________________________________
pim mailing list
pim@ietf.org
https://www1.ietf.org/mailman/listinfo/pim


From exim@www1.ietf.org  Sun Nov 23 21:12:29 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA07751
	for <pim-archive@odin.ietf.org>; Sun, 23 Nov 2003 21:12:29 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AO6Cx-00066P-Up
	for pim-archive@odin.ietf.org; Sun, 23 Nov 2003 21:12:12 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAO2CBfO023454
	for pim-archive@odin.ietf.org; Sun, 23 Nov 2003 21:12:11 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AO6Cx-00066D-Ph
	for pim-web-archive@optimus.ietf.org; Sun, 23 Nov 2003 21:12:11 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA07720
	for <pim-web-archive@ietf.org>; Sun, 23 Nov 2003 21:11:58 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AO6Cv-0002tD-00
	for pim-web-archive@ietf.org; Sun, 23 Nov 2003 21:12:09 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AO6Cu-0002t8-00
	for pim-web-archive@ietf.org; Sun, 23 Nov 2003 21:12:08 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AO6Cm-00065B-PF; Sun, 23 Nov 2003 21:12:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AO6Bz-00064h-9T
	for pim@optimus.ietf.org; Sun, 23 Nov 2003 21:11:11 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA07707
	for <pim@ietf.org>; Sun, 23 Nov 2003 21:10:58 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AO6Bw-0002sv-00
	for pim@ietf.org; Sun, 23 Nov 2003 21:11:08 -0500
Received: from catarina.usc.edu ([204.57.0.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AO6Bw-0002sM-00
	for pim@ietf.org; Sun, 23 Nov 2003 21:11:08 -0500
Received: from dmz2.procket.com (dmz2.procket.com [65.174.124.37])
	by catarina.usc.edu (8.12.9/8.12.9) with ESMTP id hAO2Ac8A005762
	for <pim@catarina.usc.edu>; Sun, 23 Nov 2003 18:10:38 -0800 (PST)
	(envelope-from John.Zwiebel@procket.com)
Received: from miata.procket.com (zeus-d-1.procket.com [65.174.124.60])
	by dmz2.procket.com (8.12.8p1/8.12.1) with ESMTP id hAO4FYOt082723;
	Sun, 23 Nov 2003 20:15:34 -0800 (PST)
Received: from exchangefe2.na.procket.com (email.na.procket.com [10.1.7.252])
	by miata.procket.com (8.12.1/8.12.1) with ESMTP id hAO2ARYB003179;
	Sun, 23 Nov 2003 18:10:27 -0800 (PST)
Received: from [127.0.0.1] ([10.1.1.1]) by exchangefe2.na.procket.com with Microsoft SMTPSVC(5.0.2195.6713);
	 Sun, 23 Nov 2003 18:10:27 -0800
In-Reply-To: <37BAA3695E46C24A91128FB94F0CC3E06AC0D3@zeus>
References: <37BAA3695E46C24A91128FB94F0CC3E06AC0D3@zeus>
Mime-Version: 1.0 (Apple Message framework v606)
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Message-Id: <F9483361-1E22-11D8-AA86-0003936A6062@procket.com>
Content-Transfer-Encoding: quoted-printable
Cc: "Mike Davison" <davison@cs.utk.edu>, <pim@catarina.usc.edu>
From: John Zwiebel <jzwiebel@procket.com>
Subject: Re: [pim] query on maintaining secondary address list
Date: Sun, 23 Nov 2003 18:07:36 -0800
To: "Ganapathasaa" <ganapath@Corecess.com>
X-Mailer: Apple Mail (2.606)
X-OriginalArrivalTime: 24 Nov 2003 02:10:27.0605 (UTC) FILETIME=[20DD3C50:01C3B230]
Content-Transfer-Encoding: quoted-printable
Sender: pim-admin@ietf.org
Errors-To: pim-admin@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Id: Protocol Independent Multicast <pim.ietf.org>
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-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

There's a suz (for suzuki) draft that explains this in detail,
but in summary, the IPv6 addresses are used quite differently than
IPv4 addresses.

All the IGP's I'm aware of use the link-local address for the
next hop.  This makes it easy for PIM to find the next
upstream router because PIM6 also uses link-local addresses.

But there is nothing 'illegal' with using a global address
as the next hop, most likely in a static route.  In such a case,
(and also in the case where the PIM-RP (a global address) is on the
LAN over which a router wants to send a pim join) the downstream
router has no way of translating the global address next hop
to a link-local pim neighbor.

You're going to find several interesting things when
trying to do pim over ipv6.

On Nov 23, 2003, at 5:50 PM, Ganapathasaa wrote:

> Hi,
> Is it not same even in IPv4? The only use I can see from maintaining=20=

> secondary IP address list is, we can send PIM joins directly to=20
> secondary address(in place of upstream neighbor's address)even if we=20=

> dont have routing entry(for that perticular secondary address) in our=20=

> unicast routing table. But is this the work to be done by PIM? and I=20=

> feel this is not the purpose of maintaining secondary address lists.=20=

> Still I am not clear about including address list option in Hello=20
> messages.
> Please send your comments on this,
>
> Regards,
> Ganapath
> -----Original Message-----
> From:Mike Davison [mailto:davison@cs.utk.edu]
> Sent:Fri 11/21/2003 9:33 AM
> To:pim@catarina.usc.edu
> Cc:
> Subject:Re: [pim] query on maintaining secondary address list
>
>
>
>
> The secondary address list is needed for IPv6 support. PIM uses a
> link-local IPv6 address when communicating with neighbors yet a
> global-scope address is also needed.
>
> Mike
>
>
>
> On Thu, 2003-11-20 at 00:57, Ganapathasaa wrote:
> > Hi,
> >=A0
> > New PIM-SM draft draft-ietf-pim-sm-v2-new-08.txt mentions about
> > "Maintaining Secondary Address Lists" in section
> > 4.3.4. I am not quite clear why do we need to maintain secondary
> > address lists in first place. Is this helpful only in alerting
> > adminstrator in case of wrong configurations? It looks like, new
> > option included in Hello message is to distinguish and to make
> > independent processing checks at primary and secondary IP. Anyway I=20=

> am
> > not clear, please send your comments on this.
> >=A0
> > Thanx in advance,
> > Ganapath
> > -----------------------------------
> > Engineer, Protocol Team/R&D Center
> > Corecess Inc,
> > 500-2, Sangdaewon-Dong, Jungwon-Ku,
> > Seongnam-city, Kyungki-do,
> > Korea, 462-120
> > Tel) 82-31-739-6907
> > Fax) 82-31-739-6899
> > www.corecess.com
> > -----------------------------------
>
>
>
> _______________________________________________
> pim mailing list
> pim@ietf.org
> https://www1.ietf.org/mailman/listinfo/pim
> =A0


_______________________________________________
pim mailing list
pim@ietf.org
https://www1.ietf.org/mailman/listinfo/pim



From pim-admin@ietf.org  Sun Nov 23 22:48:24 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA10068
	for <pim-archive@lists.ietf.org>; Sun, 23 Nov 2003 22:48:24 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AO7hh-0001aq-9m; Sun, 23 Nov 2003 22:48:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AO7h5-0001aU-Fg
	for pim@optimus.ietf.org; Sun, 23 Nov 2003 22:47:25 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA10041
	for <pim@ietf.org>; Sun, 23 Nov 2003 22:47:09 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AO7h1-00045D-00
	for pim@ietf.org; Sun, 23 Nov 2003 22:47:20 -0500
Received: from catarina.usc.edu ([204.57.0.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AO7h1-000453-00
	for pim@ietf.org; Sun, 23 Nov 2003 22:47:19 -0500
Received: from tachyon.jinmei.org (kame207.kame.net [203.178.141.207] (may be forged))
	by catarina.usc.edu (8.12.9/8.12.9) with ESMTP id hAO3kj8A005973
	for <pim@catarina.usc.edu>; Sun, 23 Nov 2003 19:46:49 -0800 (PST)
	(envelope-from jinmei@isl.rdc.toshiba.co.jp)
Received: from ocean.jinmei.org (unknown [2001:200:0:4819:208:dff:fe40:3f37])
	by tachyon.jinmei.org (Postfix) with ESMTP
	id 140CF3504F; Mon, 24 Nov 2003 12:46:37 +0900 (JST)
Date: Mon, 24 Nov 2003 12:46:42 +0900
Message-ID: <y7vvfpae8d9.wl@ocean.jinmei.org>
From: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= <jinmei@isl.rdc.toshiba.co.jp>
To: "Ganapathasaa" <ganapath@Corecess.com>
Cc: "Mike Davison" <davison@cs.utk.edu>, <pim@catarina.usc.edu>
Subject: Re: [pim] query on maintaining secondary address list
In-Reply-To: <37BAA3695E46C24A91128FB94F0CC3E06AC0D3@zeus>
References: <37BAA3695E46C24A91128FB94F0CC3E06AC0D3@zeus>
User-Agent: Wanderlust/2.10.1 (Watching The Wheels) Emacs/21.3 Mule/5.0 (SAKAKI)
Organization: Research & Development Center, Toshiba Corp., Kawasaki, Japan.
MIME-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen")
Content-Type: text/plain; charset=US-ASCII
Sender: pim-admin@ietf.org
Errors-To: pim-admin@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Id: Protocol Independent Multicast <pim.ietf.org>
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>

>>>>> On Mon, 24 Nov 2003 10:50:18 +0900, 
>>>>> "Ganapathasaa" <ganapath@Corecess.com> said:

> Is it not same even in IPv4? The only use I can see from maintaining secondary IP address list is, we can send PIM joins directly to secondary address(in place of upstream neighbor's address)even if we dont have routing entry(for that perticular secondary address) in our unicast routing table. But is this the work to be done by PIM? and I feel this is not the purpose of maintaining secondary address lists. Still I am not clear about including address list option in Hello messages.
> Please send your comments on this,

draft-suz-pim-upstream-detection-00.txt described the background of
the address list and the hello option in more details.  The draft has
already expired, but you can get it, e.g., at:

ftp://ftp.kame.net/pub/internet-drafts/draft-suz-pim-upstream-detection-00.txt

There was a related discussion in this list around March 2003.  I
think you can find the discussion in the list archive.

					JINMEI, Tatuya
					Communication Platform Lab.
					Corporate R&D Center, Toshiba Corp.
					jinmei@isl.rdc.toshiba.co.jp

_______________________________________________
pim mailing list
pim@ietf.org
https://www1.ietf.org/mailman/listinfo/pim


From exim@www1.ietf.org  Sun Nov 23 22:48:26 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA10083
	for <pim-archive@odin.ietf.org>; Sun, 23 Nov 2003 22:48:26 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AO7hp-0001c6-TE
	for pim-archive@odin.ietf.org; Sun, 23 Nov 2003 22:48:10 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAO3m9dS006196
	for pim-archive@odin.ietf.org; Sun, 23 Nov 2003 22:48:09 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AO7hp-0001br-No
	for pim-web-archive@optimus.ietf.org; Sun, 23 Nov 2003 22:48:09 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA10049
	for <pim-web-archive@ietf.org>; Sun, 23 Nov 2003 22:47:55 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AO7hm-00045Z-00
	for pim-web-archive@ietf.org; Sun, 23 Nov 2003 22:48:06 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AO7hl-00045W-00
	for pim-web-archive@ietf.org; Sun, 23 Nov 2003 22:48:05 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AO7hh-0001aq-9m; Sun, 23 Nov 2003 22:48:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AO7h5-0001aU-Fg
	for pim@optimus.ietf.org; Sun, 23 Nov 2003 22:47:25 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA10041
	for <pim@ietf.org>; Sun, 23 Nov 2003 22:47:09 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AO7h1-00045D-00
	for pim@ietf.org; Sun, 23 Nov 2003 22:47:20 -0500
Received: from catarina.usc.edu ([204.57.0.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AO7h1-000453-00
	for pim@ietf.org; Sun, 23 Nov 2003 22:47:19 -0500
Received: from tachyon.jinmei.org (kame207.kame.net [203.178.141.207] (may be forged))
	by catarina.usc.edu (8.12.9/8.12.9) with ESMTP id hAO3kj8A005973
	for <pim@catarina.usc.edu>; Sun, 23 Nov 2003 19:46:49 -0800 (PST)
	(envelope-from jinmei@isl.rdc.toshiba.co.jp)
Received: from ocean.jinmei.org (unknown [2001:200:0:4819:208:dff:fe40:3f37])
	by tachyon.jinmei.org (Postfix) with ESMTP
	id 140CF3504F; Mon, 24 Nov 2003 12:46:37 +0900 (JST)
Date: Mon, 24 Nov 2003 12:46:42 +0900
Message-ID: <y7vvfpae8d9.wl@ocean.jinmei.org>
From: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= <jinmei@isl.rdc.toshiba.co.jp>
To: "Ganapathasaa" <ganapath@Corecess.com>
Cc: "Mike Davison" <davison@cs.utk.edu>, <pim@catarina.usc.edu>
Subject: Re: [pim] query on maintaining secondary address list
In-Reply-To: <37BAA3695E46C24A91128FB94F0CC3E06AC0D3@zeus>
References: <37BAA3695E46C24A91128FB94F0CC3E06AC0D3@zeus>
User-Agent: Wanderlust/2.10.1 (Watching The Wheels) Emacs/21.3 Mule/5.0 (SAKAKI)
Organization: Research & Development Center, Toshiba Corp., Kawasaki, Japan.
MIME-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen")
Content-Type: text/plain; charset=US-ASCII
Sender: pim-admin@ietf.org
Errors-To: pim-admin@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Id: Protocol Independent Multicast <pim.ietf.org>
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>

>>>>> On Mon, 24 Nov 2003 10:50:18 +0900, 
>>>>> "Ganapathasaa" <ganapath@Corecess.com> said:

> Is it not same even in IPv4? The only use I can see from maintaining secondary IP address list is, we can send PIM joins directly to secondary address(in place of upstream neighbor's address)even if we dont have routing entry(for that perticular secondary address) in our unicast routing table. But is this the work to be done by PIM? and I feel this is not the purpose of maintaining secondary address lists. Still I am not clear about including address list option in Hello messages.
> Please send your comments on this,

draft-suz-pim-upstream-detection-00.txt described the background of
the address list and the hello option in more details.  The draft has
already expired, but you can get it, e.g., at:

ftp://ftp.kame.net/pub/internet-drafts/draft-suz-pim-upstream-detection-00.txt

There was a related discussion in this list around March 2003.  I
think you can find the discussion in the list archive.

					JINMEI, Tatuya
					Communication Platform Lab.
					Corporate R&D Center, Toshiba Corp.
					jinmei@isl.rdc.toshiba.co.jp

_______________________________________________
pim mailing list
pim@ietf.org
https://www1.ietf.org/mailman/listinfo/pim



