From mailman-bounces@ietf.org  Fri Oct  1 07:45:17 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA20546
	for <pim-archive@lists.ietf.org>; Fri, 1 Oct 2004 07:45:17 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CDJrf-0002iA-Et
	for pim-archive@lists.ietf.org; Fri, 01 Oct 2004 05:38:11 -0400
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Subject: ietf.org mailing list memberships reminder
From: mailman-owner@ietf.org
To: pim-archive@ietf.org
X-No-Archive: yes
Message-ID: <mailman.14479.1096622166.3166.mailman@lists.ietf.org>
Date: Fri, 01 Oct 2004 05:16:06 -0400
Precedence: bulk
X-BeenThere: mailman@lists.ietf.org
X-Mailman-Version: 2.1.5
List-Id: Mailman site list <mailman.lists.ietf.org>
X-List-Administrivia: yes
Sender: mailman-bounces@ietf.org
Errors-To: mailman-bounces@ietf.org
Content-Transfer-Encoding: 7bit

This is a reminder, sent out once a month, about your ietf.org mailing
list memberships.  It includes your subscription info and how to use
it to change it or unsubscribe from a list.

You can visit the URLs to change your membership status or
configuration, including unsubscribing, setting digest-style delivery
or disabling delivery altogether (e.g., for a vacation), and so on.

In addition to the URL interfaces, you can also use email to make such
changes.  For more info, send a message to the '-request' address of
the list (for example, mailman-request@ietf.org) containing just the
word 'help' in the message body, and an email message will be sent to
you with instructions.

**********************************************************************

NOTE WELL:

Any submission to the IETF intended by the Contributor for publication
as all or part of an IETF Internet-Draft or RFC and any statement made
within the context of an IETF activity is considered an "IETF
Contribution". Such statements include oral statements in IETF
sessions, as well as written and electronic communications made at any
time or place, which are addressed to:

o the IETF plenary session, o any IETF working group or portion
thereof, o the IESG, or any member thereof on behalf of the IESG, o
the IAB or any member thereof on behalf of the IAB, o any IETF mailing
list, including the IETF list itself, any working group
  or design team list, or any other list functioning under IETF
auspices,
o the RFC Editor or the Internet-Drafts function

All IETF Contributions are subject to the rules of RFC 3667 and RFC
3668.

Statements made outside of an IETF session, mailing list or other
function, that are clearly not intended to be input to an IETF
activity, group or function, are not IETF Contributions in the context
of this notice.

Please consult RFC 3667 for details.

*******************************************************************************


If you have questions, problems, comments, etc, send them to
mailman-owner@ietf.org.  Thanks!

Passwords for pim-archive@lists.ietf.org:

List                                     Password // URL
----                                     --------  
pim@ietf.org                             urahne    
https://www1.ietf.org/mailman/options/pim/pim-archive%40lists.ietf.org


From pim-bounces@ietf.org  Mon Oct  4 02:39:56 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA02525
	for <pim-archive@lists.ietf.org>; Mon, 4 Oct 2004 02:39:55 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CEMTK-0001V3-Uf; Mon, 04 Oct 2004 02:37:22 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CEMLU-0000RZ-9g
	for pim@megatron.ietf.org; Mon, 04 Oct 2004 02:29:16 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA01498
	for <pim@ietf.org>; Mon, 4 Oct 2004 02:29:14 -0400 (EDT)
Received: from web90005.mail.scd.yahoo.com ([66.218.94.63])
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CEMUU-00034v-CU
	for pim@ietf.org; Mon, 04 Oct 2004 02:38:36 -0400
Message-ID: <20041004062843.22275.qmail@web90005.mail.scd.yahoo.com>
Received: from [218.147.97.129] by web90005.mail.scd.yahoo.com via HTTP;
	Sun, 03 Oct 2004 23:28:43 PDT
Date: Sun, 3 Oct 2004 23:28:43 -0700 (PDT)
From: Kumar P <kumar_xpim@yahoo.com>
To: pim@ietf.org
MIME-Version: 1.0
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
Subject: [pim] PIM assert function
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1895428652=="
Sender: pim-bounces@ietf.org
Errors-To: pim-bounces@ietf.org

--===============1895428652==
Content-Type: multipart/alternative; boundary="0-1729137435-1096871323=:20022"

--0-1729137435-1096871323=:20022
Content-Type: text/plain; charset=us-ascii

 
Hello All,
 
I am new to PIM, want someboby clear my following doubt.
 
It is mentioned in the PIM draft that assert condition is likely to happen in multi-access environment where in there are more than one upstream routers present and have different opinion on reaching RP or Source, hence generate Join according and end up in receiving multiple streams of same data.
 
Draft also mentions that there should only one forwarder in such environments, which is nothing but DR in this case. So DR in this case is responsible for generating Join after it receives igmp join or pim join from its downstream terminals. My doubt is when there is single DR(hence forwarder) on this multi-access media, how does the other routers send join towards RP or Source when ther are not responsible for the same.
 
When a router doesn't send Join message also doesn't forward the multicast streams. Please clarify this.
 
TIA,
Kumar

		
---------------------------------
Do you Yahoo!?
vote.yahoo.com - Register online to vote today!
--0-1729137435-1096871323=:20022
Content-Type: text/html; charset=us-ascii

<DIV>&nbsp;</DIV>
<DIV>Hello All,</DIV>
<DIV>&nbsp;</DIV>
<DIV>I am new to PIM, want someboby clear my following doubt.</DIV>
<DIV>&nbsp;</DIV>
<DIV>It is mentioned in the PIM draft that assert condition is likely to happen in multi-access environment where in there are more than one upstream routers present and have different opinion on reaching RP or Source, hence generate Join according and end up in receiving multiple streams of same data.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Draft also mentions that there should only one forwarder in such environments, which is nothing but DR in this case. So DR in this case is responsible for generating Join after it receives igmp join or pim join from its downstream terminals. My doubt is when there is single DR(hence forwarder) on this multi-access media, how does the other routers send join towards RP or Source when ther are not responsible for the same.</DIV>
<DIV>&nbsp;</DIV>
<DIV>When a router doesn't send Join message also doesn't forward the multicast streams. Please clarify this.</DIV>
<DIV>&nbsp;</DIV>
<DIV>TIA,</DIV>
<DIV>Kumar</DIV><p>
		<hr size=1>Do you Yahoo!?<br><a
href="http://vote.yahoo.com">vote.yahoo.com</a> - Register online to vote today!
--0-1729137435-1096871323=:20022--


--===============1895428652==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--===============1895428652==--



From pim-bounces@ietf.org  Mon Oct  4 02:47:32 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA03921
	for <pim-archive@lists.ietf.org>; Mon, 4 Oct 2004 02:47:32 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CEMUE-0001f3-Fc; Mon, 04 Oct 2004 02:38:18 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CEMT6-0001Ng-Sc
	for pim@megatron.ietf.org; Mon, 04 Oct 2004 02:37:08 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA02326
	for <pim@ietf.org>; Mon, 4 Oct 2004 02:37:07 -0400 (EDT)
Received: from web90006.mail.scd.yahoo.com ([66.218.94.64])
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CEMc8-0003OC-F2
	for pim@ietf.org; Mon, 04 Oct 2004 02:46:28 -0400
Message-ID: <20041004063637.25501.qmail@web90006.mail.scd.yahoo.com>
Received: from [218.147.97.129] by web90006.mail.scd.yahoo.com via HTTP;
	Sun, 03 Oct 2004 23:36:37 PDT
Date: Sun, 3 Oct 2004 23:36:37 -0700 (PDT)
From: Kumar P <kumar_xpim@yahoo.com>
To: pim@ietf.org
MIME-Version: 1.0
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
Subject: [pim] PIM assert function
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0996047964=="
Sender: pim-bounces@ietf.org
Errors-To: pim-bounces@ietf.org

--===============0996047964==
Content-Type: multipart/alternative; boundary="0-684607375-1096871797=:23854"

--0-684607375-1096871797=:23854
Content-Type: text/plain; charset=us-ascii

 
 
Hello All,
 
I am new to PIM, want someboby clear my following doubt.
 
It is mentioned in the PIM draft that assert condition is likely to happen in multi-access environment where in there are more than one upstream routers present and have different opinion on reaching RP or Source, hence generate Join according and end up in receiving multiple streams of same data.
 
Draft also mentions that there should only one forwarder in such environments, which is nothing but DR in this case. So DR in this case is responsible for generating Join after it receives igmp join or pim join from its downstream terminals. My doubt is when there is single DR(hence forwarder) on this multi-access media, how does the other routers send join towards RP or Source when ther are not responsible for the same.
 
When a router doesn't send Join message also doesn't forward the multicast streams. Please clarify this.
 
TIA,
Kumar



		
---------------------------------
Do you Yahoo!?
Yahoo! Mail - 50x more storage than other providers!
--0-684607375-1096871797=:23854
Content-Type: text/html; charset=us-ascii

<DIV>
<DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>Hello All,</DIV>
<DIV>&nbsp;</DIV>
<DIV>I am new to PIM, want someboby clear my following doubt.</DIV>
<DIV>&nbsp;</DIV>
<DIV>It is mentioned in the PIM draft that assert condition is likely to happen in multi-access environment where in there are more than one upstream routers present and have different opinion on reaching RP or Source, hence generate Join according and end up in receiving multiple streams of same data.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Draft also mentions that there should only one forwarder in such environments, which is nothing but DR in this case. So DR in this case is responsible for generating Join after it receives igmp join or pim join from its downstream terminals. My doubt is when there is single DR(hence forwarder) on this multi-access media, how does the other routers send join towards RP or Source when ther are not responsible for the same.</DIV>
<DIV>&nbsp;</DIV>
<DIV>When a router doesn't send Join message also doesn't forward the multicast streams. Please clarify this.</DIV>
<DIV>&nbsp;</DIV>
<DIV>TIA,</DIV>
<DIV>Kumar</DIV></DIV></DIV><p>
		<hr size=1>Do you Yahoo!?<br>
<a href="http://us.rd.yahoo.com/mail_us/taglines/50x/*http://promotions.yahoo.com/new_mail/static/efficiency.html">Yahoo! Mail</a> - 50x more storage than other providers!
--0-684607375-1096871797=:23854--


--===============0996047964==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--===============0996047964==--



From pim-bounces@ietf.org  Tue Oct  5 00:09:48 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA28960
	for <pim-archive@lists.ietf.org>; Tue, 5 Oct 2004 00:09:48 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CEgcA-0003yQ-7x; Tue, 05 Oct 2004 00:07:50 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CEgbD-0003mc-19
	for pim@megatron.ietf.org; Tue, 05 Oct 2004 00:06:51 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA28726
	for <pim@ietf.org>; Tue, 5 Oct 2004 00:06:47 -0400 (EDT)
Received: from mta0.huawei.com ([61.144.161.41] helo=huawei.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CEgkL-00056l-Qn
	for pim@ietf.org; Tue, 05 Oct 2004 00:16:22 -0400
Received: from huawei8tthy486 (mta1.huawei.com [172.17.1.60])
	by mta1.huawei.com
	(iPlanet Messaging Server 5.2 HotFix 1.16 (built May 14 2003))
	with ESMTPA id <0I53008I8ERYDZ@mta1.huawei.com> for pim@ietf.org; Tue,
	05 Oct 2004 11:52:47 +0800 (CST)
Date: Tue, 05 Oct 2004 12:03:55 +0800
From: Prashant Jhingran <prashantj@huawei.com>
Subject: RE: [pim] PIM assert function
In-reply-to: <20041004062843.22275.qmail@web90005.mail.scd.yahoo.com>
To: "'Kumar P'" <kumar_xpim@yahoo.com>, pim@ietf.org
Message-id: <000201c4aa90$55da9f20$30226e0a@huawei8tthy486>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Mailer: Microsoft Outlook, Build 10.0.3416
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
X-imss-version: 2.7
X-imss-result: Passed
X-imss-approveListMatch: *@huawei.com
X-Spam-Score: 0.1 (/)
X-Scan-Signature: fb6060cb60c0cea16e3f7219e40a0a81
Content-Transfer-Encoding: 7BIT
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=subscribe>
Sender: pim-bounces@ietf.org
Errors-To: pim-bounces@ietf.org
Content-Transfer-Encoding: 7BIT

Hello Kumar,

Welcome to the group.

Let me briefly explain you the following points about a DR:

1. The concept of DR and DR election is important in case of PIM-SM and
not PIM-DM.

2. You are correct when you say "So DR in this case is responsible for
generating Join after it receives igmp join" but incorrect when you say
"...or pim join from its downstream terminals".
-- DR election is necessary for electing a DR on a LAN, a router which
is responsible for initiating  PIM trees (PIM-SM) as a result of IGMP
reports. Hence in PIM-SM a DR starts acting as a forwarder on the LAN.
However, the DR may loose an Assert election and therefore the winner
may become the forwarder on the LAN.
--In case of PIM-DM, its the assert mechanism which decides the
forwarder on the LAN and DR election has nothing to do with the
forwarder in DM.

3. The concept of DR is once again is of no use when it comes to
exchange of join/prune messages between the PIM routers. 
--If you think over this point then you may come to a conclusion that
Assert mechanism is required due to the above reason and also that
Assert mechanism is an efficient way of deciding  the forwarder on the
LAN.

Hope this may clear your doubts.

Regards,
Prashant Jhingran

Huawei Technologies 
Beijing, China
Ph# 00-86-10-82882837  (O)  

"You see, all the problems in the world are created by those who want
'perfection.' " -- Sri Sri Ravi Shankar  www.artofliving.org  

-----Original Message-----
From: pim-bounces@ietf.org [mailto:pim-bounces@ietf.org] On Behalf Of
Kumar P
Sent: Monday, October 04, 2004 2:29 PM
To: pim@ietf.org
Subject: [pim] PIM assert function



Hello All,

I am new to PIM, want someboby clear my following doubt.

It is mentioned in the PIM draft that assert condition is likely to
happen in multi-access environment where in there are more than one
upstream routers present and have different opinion on reaching RP or
Source, hence generate Join according and end up in receiving multiple
streams of same data.

Draft also mentions that there should only one forwarder in such
environments, which is nothing but DR in this case. So DR in this case
is responsible for generating Join after it receives igmp join or pim
join from its downstream terminals. My doubt is when there is single
DR(hence forwarder) on this multi-access media, how does the other
routers send join towards RP or Source when ther are not responsible for
the same.

When a router doesn't send Join message also doesn't forward the
multicast streams. Please clarify this.

TIA,
Kumar


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


From pim-bounces@ietf.org  Tue Oct  5 02:15:00 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA21436
	for <pim-archive@lists.ietf.org>; Tue, 5 Oct 2004 02:15:00 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CEiZS-0003ax-EL; Tue, 05 Oct 2004 02:13:10 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CEiXD-00029f-J9
	for pim@megatron.ietf.org; Tue, 05 Oct 2004 02:10:51 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA17550
	for <pim@ietf.org>; Tue, 5 Oct 2004 02:10:50 -0400 (EDT)
Received: from web90004.mail.scd.yahoo.com ([66.218.94.62])
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CEigR-0002Dh-5h
	for pim@ietf.org; Tue, 05 Oct 2004 02:20:24 -0400
Message-ID: <20041005061019.40287.qmail@web90004.mail.scd.yahoo.com>
Received: from [218.147.97.129] by web90004.mail.scd.yahoo.com via HTTP;
	Mon, 04 Oct 2004 23:10:19 PDT
Date: Mon, 4 Oct 2004 23:10:19 -0700 (PDT)
From: Kumar P <kumar_xpim@yahoo.com>
Subject: RE: [pim] PIM assert function
To: Prashant Jhingran <prashantj@huawei.com>, pim@ietf.org
In-Reply-To: <000201c4aa90$55da9f20$30226e0a@huawei8tthy486>
MIME-Version: 1.0
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 5d7a7e767f20255fce80fa0b77fb2433
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1640725123=="
Sender: pim-bounces@ietf.org
Errors-To: pim-bounces@ietf.org

--===============1640725123==
Content-Type: multipart/alternative; boundary="0-1763963512-1096956619=:40261"

--0-1763963512-1096956619=:40261
Content-Type: text/plain; charset=us-ascii

Hello Prashant, 
 
Please see my inline response...

Prashant Jhingran <prashantj@huawei.com> wrote:

Hello Kumar,

Welcome to the group.

Let me briefly explain you the following points about a DR:

1. The concept of DR and DR election is important in case of PIM-SM and
not PIM-DM.

2. You are correct when you say "So DR in this case is responsible for
generating Join after it receives igmp join" but incorrect when you say
"...or pim join from its downstream terminals".

>> OK agreed, in this case downstream routers put it's immediate upstream neighbour's address in join message, hence nexthop might not be the DR here. But in "Multi-access Transit LANs" (draft-ietf-pim-sm-v2-new-09.txt), how does PIM join state is maintained in other router(even if they have routing inconsistency) when the downstream router sends the PIM join message to a particular upstream router? and resulting two seperate join messages towards their respective upstream neighbours?. My understanding is that, since join message is sent to a particular upstream router(even though its destination address is Multicast address), or atleast downstream router is saying that "this PIM join message is supposed to be processed by the router which I have included in this message as -upstream neighbor address". When such is the situation, why does the other routers which are present in the same "Multi-access Transit LAN" process this message to create Join state and propagate join to!
 wards its
 final destination?


-- DR election is necessary for electing a DR on a LAN, a router which
is responsible for initiating PIM trees (PIM-SM) as a result of IGMP
reports. Hence in PIM-SM a DR starts acting as a forwarder on the LAN.
However, the DR may loose an Assert election and therefore the winner
may become the forwarder on the LAN.

>> Here again similar situation, when DR is supposed to take care of sending PIM join, why does the other router sending Join and pulling the multicast data? If the other router(other than DR) doesn't initiate the the PIM join, then there wouldn't be Assert I guess.


--In case of PIM-DM, its the assert mechanism which decides the
forwarder on the LAN and DR election has nothing to do with the
forwarder in DM.

3. The concept of DR is once again is of no use when it comes to
exchange of join/prune messages between the PIM routers. 


--If you think over this point then you may come to a conclusion that
Assert mechanism is required due to the above reason and also that
Assert mechanism is an efficient way of deciding the forwarder on the
LAN.

>> Sorry, I am still unable to understand. 


Hope this may clear your doubts.

Regards,
Prashant Jhingran

Huawei Technologies 
Beijing, China
Ph# 00-86-10-82882837 (O) 

"You see, all the problems in the world are created by those who want
'perfection.' " -- Sri Sri Ravi Shankar www.artofliving.org 

-----Original Message-----
From: pim-bounces@ietf.org [mailto:pim-bounces@ietf.org] On Behalf Of
Kumar P
Sent: Monday, October 04, 2004 2:29 PM
To: pim@ietf.org
Subject: [pim] PIM assert function



Hello All,

I am new to PIM, want someboby clear my following doubt.

It is mentioned in the PIM draft that assert condition is likely to
happen in multi-access environment where in there are more than one
upstream routers present and have different opinion on reaching RP or
Source, hence generate Join according and end up in receiving multiple
streams of same data.

Draft also mentions that there should only one forwarder in such
environments, which is nothing but DR in this case. So DR in this case
is responsible for generating Join after it receives igmp join or pim
join from its downstream terminals. My doubt is when there is single
DR(hence forwarder) on this multi-access media, how does the other
routers send join towards RP or Source when ther are not responsible for
the same.

When a router doesn't send Join message also doesn't forward the
multicast streams. Please clarify this.

TIA,
Kumar



		
---------------------------------
Do you Yahoo!?
vote.yahoo.com - Register online to vote today!
--0-1763963512-1096956619=:40261
Content-Type: text/html; charset=us-ascii

<DIV>Hello Prashant, </DIV>
<DIV>&nbsp;</DIV>
<DIV>Please see my inline response...<BR><BR><B><I>Prashant Jhingran &lt;prashantj@huawei.com&gt;</I></B> wrote:</DIV>
<BLOCKQUOTE class=replbq style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #1010ff 2px solid">
<P>Hello Kumar,<BR><BR>Welcome to the group.<BR><BR>Let me briefly explain you the following points about a DR:<BR><BR>1. The concept of DR and DR election is important in case of PIM-SM and<BR>not PIM-DM.<BR><BR>2. You are correct when you say "So DR in this case is responsible for<BR>generating Join after it receives igmp join" but incorrect when you say<BR>"...or pim join from its downstream terminals".</P>
<P>&gt;&gt; OK agreed, in this case downstream routers put it's immediate upstream neighbour's address in join message, hence nexthop might not be the DR here. But in "Multi-access Transit LANs" (draft-ietf-pim-sm-v2-new-09.txt), how does PIM join state is maintained in other router(even if they have routing inconsistency) when the downstream router sends the PIM join message to a particular upstream router? and resulting two seperate join messages towards their respective upstream neighbours?. My understanding is that, since join message is sent to a particular upstream router(even though its destination address&nbsp;is Multicast address), or atleast downstream router is saying that "this PIM join message is supposed to be processed by the router which I have included in this message as -upstream neighbor address". When such is the situation, why does the other routers which are present in the same "Multi-access Transit LAN" process this message to create Join state and pro!
 pagate
 join towards its final destination?</P>
<P><BR>-- DR election is necessary for electing a DR on a LAN, a router which<BR>is responsible for initiating PIM trees (PIM-SM) as a result of IGMP<BR>reports. Hence in PIM-SM a DR starts acting as a forwarder on the LAN.<BR>However, the DR may loose an Assert election and therefore the winner<BR>may become the forwarder on the LAN.</P>
<P>&gt;&gt; Here again similar situation, when DR is supposed to take care of sending PIM join, why does the other router sending Join and pulling the multicast data? If the other router(other than DR) doesn't initiate the the PIM join, then there wouldn't be Assert I guess.</P>
<P><BR>--In case of PIM-DM, its the assert mechanism which decides the<BR>forwarder on the LAN and DR election has nothing to do with the<BR>forwarder in DM.<BR><BR>3. The concept of DR is once again is of no use when it comes to<BR>exchange of join/prune messages between the PIM routers. </P>
<P><BR>--If you think over this point then you may come to a conclusion that<BR>Assert mechanism is required due to the above reason and also that<BR>Assert mechanism is an efficient way of deciding the forwarder on the<BR>LAN.</P>
<P>&gt;&gt; Sorry, I am still unable to understand. </P>
<P><BR>Hope this may clear your doubts.<BR><BR>Regards,<BR>Prashant Jhingran<BR><BR>Huawei Technologies <BR>Beijing, China<BR>Ph# 00-86-10-82882837 (O) <BR><BR>"You see, all the problems in the world are created by those who want<BR>'perfection.' " -- Sri Sri Ravi Shankar www.artofliving.org <BR><BR>-----Original Message-----<BR>From: pim-bounces@ietf.org [mailto:pim-bounces@ietf.org] On Behalf Of<BR>Kumar P<BR>Sent: Monday, October 04, 2004 2:29 PM<BR>To: pim@ietf.org<BR>Subject: [pim] PIM assert function<BR><BR><BR><BR>Hello All,<BR><BR>I am new to PIM, want someboby clear my following doubt.<BR><BR>It is mentioned in the PIM draft that assert condition is likely to<BR>happen in multi-access environment where in there are more than one<BR>upstream routers present and have different opinion on reaching RP or<BR>Source, hence generate Join according and end up in receiving multiple<BR>streams of same data.<BR><BR>Draft also mentions that there should only one forwarder in
 such<BR>environments, which is nothing but DR in this case. So DR in this case<BR>is responsible for generating Join after it receives igmp join or pim<BR>join from its downstream terminals. My doubt is when there is single<BR>DR(hence forwarder) on this multi-access media, how does the other<BR>routers send join towards RP or Source when ther are not responsible for<BR>the same.<BR><BR>When a router doesn't send Join message also doesn't forward the<BR>multicast streams. Please clarify this.<BR><BR>TIA,<BR>Kumar<BR><BR></P></BLOCKQUOTE><p>
		<hr size=1>Do you Yahoo!?<br><a
href="http://vote.yahoo.com">vote.yahoo.com</a> - Register online to vote today!
--0-1763963512-1096956619=:40261--


--===============1640725123==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--===============1640725123==--



From pim-bounces@ietf.org  Tue Oct  5 13:25:47 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA18030
	for <pim-archive@lists.ietf.org>; Tue, 5 Oct 2004 13:25:47 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CEsw5-0002hX-He; Tue, 05 Oct 2004 13:17:13 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CEsqM-0001GG-21
	for pim@megatron.ietf.org; Tue, 05 Oct 2004 13:11:18 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA16372
	for <pim@ietf.org>; Tue, 5 Oct 2004 13:11:15 -0400 (EDT)
Received: from iramx2.ira.uni-karlsruhe.de ([141.3.10.81])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CEszf-0002BR-S1
	for pim@ietf.org; Tue, 05 Oct 2004 13:20:56 -0400
Received: from iraspam.ira.uni-karlsruhe.de ([141.3.10.6]
	helo=spamhost.ira.uka.de)
	by iramx2.ira.uni-karlsruhe.de with esmtp (Exim 3.30 #10)
	id 1CEsq1-0002St-00; Tue, 05 Oct 2004 19:10:57 +0200
Received: from amavis by spamhost.ira.uka.de with scanned-ok (Exim 3.30 #3)
	id 1CEsq0-00047R-00; Tue, 05 Oct 2004 19:10:56 +0200
Received: from irams1.ira.uni-karlsruhe.de ([141.3.10.5]
	helo=irams1.ira.uka.de)
	by spamhost.ira.uka.de with esmtp (Exim 3.30 #3)
	id 1CEspk-000468-00; Tue, 05 Oct 2004 19:10:40 +0200
Received: from i72ms1.tm.uni-karlsruhe.de
	([141.3.70.16] helo=smtp.ipv6.tm.uni-karlsruhe.de ident=8)
	by irams1.ira.uka.de with esmtp (Exim 3.30 #7 )
	id 1CEspk-0007nZ-00; Tue, 05 Oct 2004 19:10:40 +0200
Received: from borg.ipv6.tm.uni-karlsruhe.de
	([2001:638:204:6:202:b3ff:feab:632e])
	by smtp.ipv6.tm.uni-karlsruhe.de with esmtp (TLSv1:DES-CBC3-SHA:168)
	(Exim 4.12) id 1CEsph-0002N8-00; Tue, 05 Oct 2004 19:10:37 +0200
Received: from localhost ([127.0.0.1])
	by borg.ipv6.tm.uni-karlsruhe.de with esmtp (Exim 4.30)
	id 1CEsph-0002fa-6Q; Tue, 05 Oct 2004 19:10:37 +0200
Message-ID: <4162D58C.2040406@tm.uka.de>
Date: Tue, 05 Oct 2004 19:10:36 +0200
From: Mark Doll <doll@tm.uka.de>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
	rv:1.7) Gecko/20040803 Thunderbird/0.7.3 Mnenhy/0.6.0.104
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Yi Zhao <edrt@citiz.net>
Subject: Re: [pim] some questions/comments to PIM-SM draft-10
References: <E1C8eES-0004ib-00@iramx1.ira.uni-karlsruhe.de>
In-Reply-To: <E1C8eES-0004ib-00@iramx1.ira.uni-karlsruhe.de>
X-Enigmail-Version: 0.85.0.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 48472a944c87678fcfe8db15ffecdfff
Content-Transfer-Encoding: 7bit
Cc: "pim@ietf.org" <pim@ietf.org>
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=subscribe>
Sender: pim-bounces@ietf.org
Errors-To: pim-bounces@ietf.org
Content-Transfer-Encoding: 7bit

Hi Yi!

Venu Hemige pointed out to me, that (parts of) the Update_SPTbit macro 
would be executed out of band, thus one loses some packets if the 
forwarding rule is changed the way you've proposed:

Venu Hemige wrote (personal email):
 > Besides, changing the definition of the pseudo-code for forwarding per
 > Yi Zhao's suggestion may be theoretically correct, but one should
 > realize that only a portion of the pseudo-code can be implemented in
 > the forwarding plane of most implementations that use hardware-based
 > forwarding. By changing the definition per Yi Zhao, the first few
 > packets coming down the source-specific tree will not be forwarded
 > since (in most implementations) Update_SPTbit happens out-of-band. I
 > think the current definition is fine to handle most of the common
 > cases.

So both, the draft's version and your version (augmented with the fix 
below) have (different) drawbacks.

For SSM (at least with the fix below) no data packets are ever lost in 
both versions.

For ASM, one has to decide what might be worse: interrupting traffic on 
the RPT for (*,G) receivers (if SPT and RPT intersect two times) or 
losing some packets at the very beginning for the new (S,G) receivers 
(when injecting RPT traffic into SPT). And/or what might be more 
probable: SPT and RPT intersecting two times or the existence of shared 
LANs as transit networks.

Or in other words:

How should the case "both SPT and RPT upstream neighbors are on the same 
shared LAN" (aka RPF_interface(S) == RPF_interface(RP(G)) AND RPF'(S,G) 
!= RPF'(*,G)) be handled correctly:

Draft's version: inject RPT traffic into SPT as it arrives and risk 
blackholing all receivers for some short time if SPT and RPT intersect 
two times.

Your version (with my fix): wait for the Assert(S,G) to occur on the 
upstream shared LAN an miss forwarding some packets at the very 
beginning to new (S,G) receivers, starting with the packet that triggers 
the assert until the assert has been processed and SPTbit(S,G) has been 
updated.

I dont't know what's more appropriate.

If Update_SPTbit can be executed on every data packet, your version 
(without my fix) is superior, of course, since it has no drawbacks while 
the draft version's drawback still remains.

- Mark.



------------------------------------------------------------------------
P.S.: Here is my fix to your proposed change to the forwarding rule.

If we asume Update_SPTbit(S,G,iif) is too costly to be executed on every 
data packet arrival (which I think it is), one should use a data traffic 
independend variant Update_SPTbit(S,G) instead. The new version is the 
same as the old version except that the two conditions iif == 
RPF_interface(S) and RPF_interface(S) != RPF_interface(RP(G)) are omitted.

There are two cases where we might lose some packets during switchover 
from RPT to SPT:

In the first case RPF_interface(S) != RPF_interface(RP(G)), the RPF 
check between SPTbit == TRUE and SPTbit == FALSE differs, so we do not 
accept traffic correctly arriving via the SPT. This can be handled by 
another if clause in the forwarding rule (see the end of my email), 
which resembles the condition from Update_SPTbit(S,G,iif) that 
Update_SPTbit(S,G) omits.

The second is the case where we have to wait for an upstream Assert(S,G) 
to occur (I_Am_Assert_Loser(S,G,RPF_interface(S) == TRUE). Here, we will 
still loose some packets (at least the packet, that triggers the 
Assert(S,G)). This can't be changed if we want to prevent RPF traffic to 
be sent onto the SPT.

The SPTbit would be updated whenever one of the preconditions changes 
(becomes TRUE), thus not on data packet arrival:

void
Update_SPTbit(S,G) {
         if ( JoinDesired(S,G) == TRUE
	     AND ( DirectlyConnected(S) == TRUE
	           OR inherited_olist(S,G,rpt) == NULL
	           OR ( RPF'(S,G) == RPF'(*,G) AND RPF'(S,G) != NULL )
	           OR I_Am_Assert_Loser(S,G,RPF_interface(S) == TRUE ) {
		set SPTbit(S,G) to TRUE
	}
}

To sum up:

o If the RTT between the router and the sender is (considerably) smaller 
  via SPT than via RPT, we will loose packets anyway since we 
Prune(S,G,rpt) directly after receiving the first SPT data packet. So we 
miss to forward a number of packets (equivalent of what the senders 
sends during the span of time RTT(RPT)-RTT(SPT)).

o In the draft's version, we risc blackholing RPT traffic when SPT and 
RPT intersect two times - for both (*,G) and (S,G) downstream neighbors.

o In the new version, we miss to forward the first data packets via SPT 
on downstream interfaces with (S,G) state in one case:
- we have (*,G) state on other downstream interfaces
- we have no (*,G) state on the respective (S,G) downstream interface
- RPF_interface(S) == RPF_interface(RP(G)) and RPF'(S,G) != RPF'(*,G) 
(both SPT and RPT upstream neighbors are on the same upstream LAN)

So for SSM, no data packets are ever lost since we never have (*,G) state.

For ASM, we have to decide what is worse: interrupting traffic on the 
RPT for (*,G) receivers or losing some packets at the beginning for 
(S,G) receivers.

The complete forwarding rule (changes to my last email are marked with "|"):

if ( DirectlyConnected(S) == TRUE AND iif == RPF_interface(S))
         set KeepaliveTimer(S,G) to Keepalive_Period
}
| # Note: no UpdateSPTbit(S,G,iif) any more; replaced by UpdateSPTbit(S,G)
   oiflist = inherited_olist(S,G,rpt)
   if ( SPTbit(S,G) == TRUE ) {
|	Label "SPT"
         # Note: start KAT only on nodes that have downstream RPT state
         if ( inherited_olist(S,G,rpt) != NULL ) {
                 set KeepaliveTimer(S,G) to KeepalivePeriod
         }
         # Note: set oiflist to inherited_olist(S,G)
         oiflist = oiflist (+) immediate_olist(S,G)
         if ( iif == RPF_interface(S) ) {
                 forward packet to oiflist (-) iif
         } else if ( iif in oiflist ) {
                 send Assert(S,G) on iif
         }
   } else {
         if ( iif == RPF_interface(RP(G)) ) {
                 # Note: Checking KAT is optional
                 if ( KeepaliveTimer is not running ) {
                         CheckSwitchToSpt(S,G)
                 }
                 forward packet to oiflist (-) iif
| 	} else if ( iif == RPF_interface(S) AND JoinDesired(S,G) == TRUE ) {
|		# Note: RPF_interface(S) != RPF_interface(RP(G))
|		#       transition from RPT to SPT completed
|		set SPTbit(S,G) to TRUE
|		goto Label "SPT"
         } else if ( iif in oiflist ) {
                 send Assert(*,G) on iif
         }
   }

   void
   CheckSwitchToSpt(S,G) {
         if ( pim_include(*,G) (-) pim_exclude(S,G) != NULL
              AND SwitchToSptDesired(S,G) == TRUE ) {
                 set KeepaliveTimer(S,G) to KeepalivePeriod
   }

#
# SPTbit(S,G) should be updated (aka Update_SPTbit(S,G) is called)
# whenever any of the included prerequisites changes from FALSE to TRUE
# (and SPTbit is still FALSE): So Update_SPTbit(S,G) is not data driven
# any more as Update_SPTbit(S,G,iif) was.
#
   void
| Update_SPTbit(S,G) {
|	# Note: "iif == RPF_interface(S)" omitted
         if ( JoinDesired(S,G) == TRUE
	     AND ( DirectlyConnected(S) == TRUE
|	           # Note: "RPF_interface(S) != RPF_interface(RP(G)" omitted
	           OR inherited_olist(S,G,rpt) == NULL
	           OR ( RPF'(S,G) == RPF'(*,G) AND RPF'(S,G) != NULL )
	           OR I_Am_Assert_Loser(S,G,RPF_interface(S) == TRUE ) {
		set SPTbit(S,G) to TRUE
	}
   }

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


From pim-bounces@ietf.org  Wed Oct  6 08:50:00 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA20102
	for <pim-archive@lists.ietf.org>; Wed, 6 Oct 2004 08:50:00 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CFBD3-0007Kl-HT; Wed, 06 Oct 2004 08:47:57 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CFB4a-0006TT-PQ
	for pim@megatron.ietf.org; Wed, 06 Oct 2004 08:39:14 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA19409
	for <pim@ietf.org>; Wed, 6 Oct 2004 08:39:11 -0400 (EDT)
Message-Id: <200410061239.IAA19409@ietf.org>
Received: from [218.1.66.104] (helo=mail.citiz.net)
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CFBDj-00075G-6v
	for pim@ietf.org; Wed, 06 Oct 2004 08:49:01 -0400
Received: (umta 29971 invoked by alias); 6 Oct 2004 12:37:50 -0000
X-Lasthop: 61.172.253.50
Received: from unknown (HELO a) (unknown@61.172.253.50)
	by localhost with SMTP; 6 Oct 2004 12:37:50 -0000
Date: Wed, 6 Oct 2004 20:50:36 +0800
From: "edrt"<edrt@citiz.net>
To: "Mark Doll" <doll@tm.uka.de>
Subject: Re: Re: [pim] some questions/comments to PIM-SM draft-10
X-mailer: Foxmail 5.0 beta1 [cn]
Mime-Version: 1.0
Content-Type: text/plain;
	charset="gb2312"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 1.9 (+)
X-Scan-Signature: a1f9797ba297220533cb8c3f4bc709a8
Content-Transfer-Encoding: 7bit
Cc: "pim@ietf.org" <pim@ietf.org>
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=subscribe>
Sender: pim-bounces@ietf.org
Errors-To: pim-bounces@ietf.org
Content-Transfer-Encoding: 7bit

Hi Mark,


First, I want to make sure I correctly understand the problem Venu pointed out.
Take FreeBSD+pimd as example, when kernel saw data comming from SPT

a. If it is the first time kernel saw this multicast flow :
   After kernel send NOCACHE notification to pimd, and before pimd 
   calculate & install the MFC into kernel, kernel will cache the
   multicast packets coming from SPT.

b. If kernel already forwarding this multicast flow using upstream RPT
   branch, and if RPF_interface(S) != RPF_interface(RP(G)) :
   After kernel send WRONGVIF notification to pimd, and before pimd
   update SPTbit & refresh MFC in the kernel, kernel will continue forwarding
   traffic only to inherited_olist(S,G,rpt). 

c. If kernel already forwarding this multicast flow using upstream RPT
   branch, and if (RPF_interface(S) == RPF_interface(RP(G))) AND (RPF'(S,G) != RPF'(*,G)) :
   After Assert happens, and before pimd update SPTbit & refresh MFC
   in the kernel, kernel will continue forwarding traffic only to 
   inherited_olist(S,G,rpt). 


To sum up, with the new pseudo-code, and with the current FreeBSD+pimd 
synchronization mechanismin, in case b & c, the first few packets
coming from SPT won't be delivered to SSM state only downstream branches,
until after the data & control plane is synchronized.


And I doubt that with the current FreeBSD+pimd syhchronization mechanism,
kernel will lost first few packets from SPT in case b, even if we implement
user space pimd with the current draft forwarding pseudo-code. 


And your proposed patch
	>| 	} else if ( iif == RPF_interface(S) AND JoinDesired(S,G) == TRUE ) {
	>|		# Note: RPF_interface(S) != RPF_interface(RP(G))
	>|		#       transition from RPT to SPT completed
	>|		set SPTbit(S,G) to TRUE
	>|		goto Label "SPT"
seems won't solve the problem in case b on FreeBSD. Because packets triggered
WRONGVIF notifications to pimd still get dropped in kernel, and it also take 
time to let user space pimd recalc and refresh MFC in the kernel using this 
piece of pseudo-code, so the synchronization problem still there. 


Different implemenation might use different data & control plane synchronization 
model, may be on some platform this won't be a issue. So my personal opinion is to
leave this synchroniaztion issue to the implementor of the protocol and platform 
rather than changing the protocol.


Point out if I'm missing something.


Thanks
Yi Zhao



>Hi Yi!
>
>Venu Hemige pointed out to me, that (parts of) the Update_SPTbit macro 
>would be executed out of band, thus one loses some packets if the 
>forwarding rule is changed the way you've proposed:
>
>Venu Hemige wrote (personal email):
> > Besides, changing the definition of the pseudo-code for forwarding per
> > Yi Zhao's suggestion may be theoretically correct, but one should
> > realize that only a portion of the pseudo-code can be implemented in
> > the forwarding plane of most implementations that use hardware-based
> > forwarding. By changing the definition per Yi Zhao, the first few
> > packets coming down the source-specific tree will not be forwarded
> > since (in most implementations) Update_SPTbit happens out-of-band. I
> > think the current definition is fine to handle most of the common
> > cases.
>
>So both, the draft's version and your version (augmented with the fix 
>below) have (different) drawbacks.
>
>For SSM (at least with the fix below) no data packets are ever lost in 
>both versions.
>
>For ASM, one has to decide what might be worse: interrupting traffic on 
>the RPT for (*,G) receivers (if SPT and RPT intersect two times) or 
>losing some packets at the very beginning for the new (S,G) receivers 
>(when injecting RPT traffic into SPT). And/or what might be more 
>probable: SPT and RPT intersecting two times or the existence of shared 
>LANs as transit networks.
>
>Or in other words:
>
>How should the case "both SPT and RPT upstream neighbors are on the same 
>shared LAN" (aka RPF_interface(S) == RPF_interface(RP(G)) AND RPF'(S,G) 
>!= RPF'(*,G)) be handled correctly:
>
>Draft's version: inject RPT traffic into SPT as it arrives and risk 
>blackholing all receivers for some short time if SPT and RPT intersect 
>two times.
>
>Your version (with my fix): wait for the Assert(S,G) to occur on the 
>upstream shared LAN an miss forwarding some packets at the very 
>beginning to new (S,G) receivers, starting with the packet that triggers 
>the assert until the assert has been processed and SPTbit(S,G) has been 
>updated.
>
>I dont't know what's more appropriate.
>
>If Update_SPTbit can be executed on every data packet, your version 
>(without my fix) is superior, of course, since it has no drawbacks while 
>the draft version's drawback still remains.
>
>- Mark.
>
>
>
>------------------------------------------------------------------------
>P.S.: Here is my fix to your proposed change to the forwarding rule.
>
>If we asume Update_SPTbit(S,G,iif) is too costly to be executed on every 
>data packet arrival (which I think it is), one should use a data traffic 
>independend variant Update_SPTbit(S,G) instead. The new version is the 
>same as the old version except that the two conditions iif == 
>RPF_interface(S) and RPF_interface(S) != RPF_interface(RP(G)) are omitted.
>
>There are two cases where we might lose some packets during switchover 
>from RPT to SPT:
>
>In the first case RPF_interface(S) != RPF_interface(RP(G)), the RPF 
>check between SPTbit == TRUE and SPTbit == FALSE differs, so we do not 
>accept traffic correctly arriving via the SPT. This can be handled by 
>another if clause in the forwarding rule (see the end of my email), 
>which resembles the condition from Update_SPTbit(S,G,iif) that 
>Update_SPTbit(S,G) omits.
>
>The second is the case where we have to wait for an upstream Assert(S,G) 
>to occur (I_Am_Assert_Loser(S,G,RPF_interface(S) == TRUE). Here, we will 
>still loose some packets (at least the packet, that triggers the 
>Assert(S,G)). This can't be changed if we want to prevent RPF traffic to 
>be sent onto the SPT.
>
>The SPTbit would be updated whenever one of the preconditions changes 
>(becomes TRUE), thus not on data packet arrival:
>
>void
>Update_SPTbit(S,G) {
>         if ( JoinDesired(S,G) == TRUE
>	     AND ( DirectlyConnected(S) == TRUE
>	           OR inherited_olist(S,G,rpt) == NULL
>	           OR ( RPF'(S,G) == RPF'(*,G) AND RPF'(S,G) != NULL )
>	           OR I_Am_Assert_Loser(S,G,RPF_interface(S) == TRUE ) {
>		set SPTbit(S,G) to TRUE
>	}
>}
>
>To sum up:
>
>o If the RTT between the router and the sender is (considerably) smaller 
>  via SPT than via RPT, we will loose packets anyway since we 
>Prune(S,G,rpt) directly after receiving the first SPT data packet. So we 
>miss to forward a number of packets (equivalent of what the senders 
>sends during the span of time RTT(RPT)-RTT(SPT)).
>
>o In the draft's version, we risc blackholing RPT traffic when SPT and 
>RPT intersect two times - for both (*,G) and (S,G) downstream neighbors.
>
>o In the new version, we miss to forward the first data packets via SPT 
>on downstream interfaces with (S,G) state in one case:
>- we have (*,G) state on other downstream interfaces
>- we have no (*,G) state on the respective (S,G) downstream interface
>- RPF_interface(S) == RPF_interface(RP(G)) and RPF'(S,G) != RPF'(*,G) 
>(both SPT and RPT upstream neighbors are on the same upstream LAN)
>
>So for SSM, no data packets are ever lost since we never have (*,G) state.
>
>For ASM, we have to decide what is worse: interrupting traffic on the 
>RPT for (*,G) receivers or losing some packets at the beginning for 
>(S,G) receivers.
>
>The complete forwarding rule (changes to my last email are marked with "|"):
>
>if ( DirectlyConnected(S) == TRUE AND iif == RPF_interface(S))
>         set KeepaliveTimer(S,G) to Keepalive_Period
>}
>| # Note: no UpdateSPTbit(S,G,iif) any more; replaced by UpdateSPTbit(S,G)
>   oiflist = inherited_olist(S,G,rpt)
>   if ( SPTbit(S,G) == TRUE ) {
>|	Label "SPT"
>         # Note: start KAT only on nodes that have downstream RPT state
>         if ( inherited_olist(S,G,rpt) != NULL ) {
>                 set KeepaliveTimer(S,G) to KeepalivePeriod
>         }
>         # Note: set oiflist to inherited_olist(S,G)
>         oiflist = oiflist (+) immediate_olist(S,G)
>         if ( iif == RPF_interface(S) ) {
>                 forward packet to oiflist (-) iif
>         } else if ( iif in oiflist ) {
>                 send Assert(S,G) on iif
>         }
>   } else {
>         if ( iif == RPF_interface(RP(G)) ) {
>                 # Note: Checking KAT is optional
>                 if ( KeepaliveTimer is not running ) {
>                         CheckSwitchToSpt(S,G)
>                 }
>                 forward packet to oiflist (-) iif
>| 	} else if ( iif == RPF_interface(S) AND JoinDesired(S,G) == TRUE ) {
>|		# Note: RPF_interface(S) != RPF_interface(RP(G))
>|		#       transition from RPT to SPT completed
>|		set SPTbit(S,G) to TRUE
>|		goto Label "SPT"
>         } else if ( iif in oiflist ) {
>                 send Assert(*,G) on iif
>         }
>   }
>
>   void
>   CheckSwitchToSpt(S,G) {
>         if ( pim_include(*,G) (-) pim_exclude(S,G) != NULL
>              AND SwitchToSptDesired(S,G) == TRUE ) {
>                 set KeepaliveTimer(S,G) to KeepalivePeriod
>   }
>
>#
># SPTbit(S,G) should be updated (aka Update_SPTbit(S,G) is called)
># whenever any of the included prerequisites changes from FALSE to TRUE
># (and SPTbit is still FALSE): So Update_SPTbit(S,G) is not data driven
># any more as Update_SPTbit(S,G,iif) was.
>#
>   void
>| Update_SPTbit(S,G) {
>|	# Note: "iif == RPF_interface(S)" omitted
>         if ( JoinDesired(S,G) == TRUE
>	     AND ( DirectlyConnected(S) == TRUE
>|	           # Note: "RPF_interface(S) != RPF_interface(RP(G)" omitted
>	           OR inherited_olist(S,G,rpt) == NULL
>	           OR ( RPF'(S,G) == RPF'(*,G) AND RPF'(S,G) != NULL )
>	           OR I_Am_Assert_Loser(S,G,RPF_interface(S) == TRUE ) {
>		set SPTbit(S,G) to TRUE
>	}
>   }
>



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


From pim-bounces@ietf.org  Mon Oct 11 11:11:19 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA13229
	for <pim-archive@lists.ietf.org>; Mon, 11 Oct 2004 11:11:18 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CH1nx-0000pf-Eq; Mon, 11 Oct 2004 11:09:41 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CH1jk-0008Mc-WC
	for pim@megatron.ietf.org; Mon, 11 Oct 2004 11:05:21 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA12766
	for <pim@ietf.org>; Mon, 11 Oct 2004 11:05:18 -0400 (EDT)
Received: from qfe1.f10207-20.atlanta2.level3.net ([67.72.93.25]
	helo=f10207-20.adc1.level3.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CH1uG-00017k-6x
	for pim@ietf.org; Mon, 11 Oct 2004 11:16:15 -0400
Received: from scanner5.level3.com (qfe0.f10212-07.adc1.oss.level3.com
	[10.2.1.102])
	by f10207-20.adc1.level3.com (8.12.10/8.12.10) with ESMTP id
	i9BF5DsO001237; Mon, 11 Oct 2004 15:05:13 GMT
Received: from scanner5.level3.com (localhost [127.0.0.1])
	by localhost.level3.com (Postfix) with ESMTP
	id 8972D124804; Mon, 11 Oct 2004 15:05:12 +0000 (GMT)
Received: from idc1exc0001.corp.global.level3.com
	(idc1exc0001.corp.global.level3.com [10.1.7.194])
	by scanner5.level3.com (Postfix) with SMTP
	id 41ED4124801; Mon, 11 Oct 2004 15:05:12 +0000 (GMT)
Received: from idc1exc0002.corp.global.level3.com ([10.1.8.18]) by
	idc1exc0001.corp.global.level3.com with Microsoft
	SMTPSVC(6.0.3790.0); Mon, 11 Oct 2004 09:05:11 -0600
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: Re: [pim] draft-wijnands-pim-proxy
Date: Mon, 11 Oct 2004 09:05:11 -0600
Message-ID: <38981BF5940A464E9533848104308D1003F47C08@idc1exc0002.corp.global.level3.com>
Thread-Topic: Re: [pim] draft-wijnands-pim-proxy
Thread-Index: AcSvo7RE01pljK4MSbqmDLHTJDF+uA==
From: "Spessard, Kirk" <Kirk.Spessard@Level3.com>
To: <mmcbride@cisco.com>
X-OriginalArrivalTime: 11 Oct 2004 15:05:11.0988 (UTC)
	FILETIME=[B4BAAF40:01C4AFA3]
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 17e5edc4dfd335965c1d21372171c01c
Cc: pim@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0557118121=="
Sender: pim-bounces@ietf.org
Errors-To: pim-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0557118121==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C4AFA3.B45C4E11"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C4AFA3.B45C4E11
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Due to IPVPN customer requirements, Level 3 is actively pursuing an MPLS
BGP free core by end of 2005.  (Note: Some of our large customers
perceive BGP and mBGP on our MPLS core as a security concern.)  For this
reason, Level 3 is very interested in this draft.
=20
Kirk
=20
> On Tue, 31 Aug 2004, Mike McBride wrote:
> > In San Diego, Ice presented draft-wijnands-pim-proxy-00 and
requested that
> > the PIM WG adopt it as a working group document. At the time, we
felt that
> > we needed to modify our WG charter before considering such
documents. Upon
> > further review we will proceed and let your voice (hands) be heard.
Please
> > review the following document and provide opinions on whether we
should
> > adopt it:
> >=20
> > http://www.ietf.org/internet-drafts/draft-wijnands-pim-proxy-00.txt
>=20
> Because there is IPR on it, my default answer would be "no, unless=20
> proven otherwise".
>=20
> In this case the proof would probably consist one or more of the
> following:
>=20
> 1. multiple other vendors indicating that they'd intend to implement=20
> the the option, and would desire it to be put on Standards Track.
>=20
> 2. there being strong usage case for it.  I don't see it.  BGP-free
> cores or L3VPN's were given as examples, but that doesn't give any
> hint why anyone would like to do a BGP-free core in the first place. =20
> If they want to do it, that's fine, but that doesn't necessarily mean
> we'll have to support it.  And the L3VPN case being still open was
> already mentioned.
>=20
> --=20
> Pekka Savola                 "You each name yourselves king, yet the
> Netcore Oy                    kingdom bleeds."
> Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings

=20


------_=_NextPart_001_01C4AFA3.B45C4E11
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html>

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered)">

<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"\@SimSun";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:#606420;
	text-decoration:underline;}
pre
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
span.EmailStyle17
	{font-family:Arial;
	color:windowtext;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3D"#606420">

<div class=3DSection1><pre><font size=3D2 face=3D"Courier New"><span
style=3D'font-size:10.0pt'>Due to IPVPN customer requirements, Level 3 =
is actively pursuing an MPLS BGP free core by end of 2005.&nbsp; (Note: =
Some of our large customers perceive BGP and mBGP on our MPLS core as a =
security concern.) &nbsp;For this reason, Level 3 is very interested in =
this draft.</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>Kirk</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>&gt; On =
Tue, 31 Aug 2004, Mike McBride wrote:</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>&gt; &gt; =
In San Diego, Ice presented draft-wijnands-pim-proxy-00 and requested =
that</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>&gt; &gt; =
the PIM WG adopt it as a working group document. At the time, we felt =
that</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>&gt; &gt; =
we needed to modify our WG charter before considering such documents. =
Upon</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>&gt; &gt; =
further review we will proceed and let your voice (hands) be heard. =
Please</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>&gt; &gt; =
review the following document and provide opinions on whether we =
should</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>&gt; &gt; =
adopt it:</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>&gt; &gt; =
</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>&gt; &gt; =
<a
href=3D"http://www.ietf.org/internet-drafts/draft-wijnands-pim-proxy-00.t=
xt">http://www.ietf.org/internet-drafts/draft-wijnands-pim-proxy-00.txt</=
a></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&gt;&nbsp;</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>&gt; =
Because there is IPR on it, my default answer would be &quot;no, unless =
</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>&gt; =
proven otherwise&quot;.</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>&gt; =
</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>&gt; In =
this case the proof would probably consist one or more of =
the</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>&gt; =
following:</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>&gt; =
</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>&gt; 1. =
multiple other vendors indicating that they'd intend to implement =
</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>&gt; the =
the option, and would desire it to be put on Standards =
Track.</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&gt;&nbsp;</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>&gt; 2. =
there being strong usage case for it.&nbsp; I don't see it.&nbsp; =
BGP-free</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>&gt; =
cores or L3VPN's were given as examples, but that doesn't give =
any</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>&gt; hint =
why anyone would like to do a BGP-free core in the first place.&nbsp; =
</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>&gt; If =
they want to do it, that's fine, but that doesn't necessarily =
mean</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>&gt; =
we'll have to support it.&nbsp; And the L3VPN case being still open =
was</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>&gt; =
already mentioned.</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&gt;&nbsp;</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>&gt; -- =
</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>&gt; =
Pekka =
Savola&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &quot;You each name yourselves king, yet =
the</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>&gt; =
Netcore =
Oy&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; kingdom =
bleeds.&quot;</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>&gt; =
Systems. Networks. Security. -- George R.R. Martin: A Clash of =
Kings</span></font></pre>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;</span></font></p>

</div>

</body>

</html>

------_=_NextPart_001_01C4AFA3.B45C4E11--


--===============0557118121==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--===============0557118121==--



From pim-bounces@ietf.org  Mon Oct 11 23:35:30 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA26109
	for <pim-archive@lists.ietf.org>; Mon, 11 Oct 2004 23:35:30 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CHDLP-0007pd-51; Mon, 11 Oct 2004 23:28:59 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CH3yH-0001pw-Rj
	for pim@megatron.ietf.org; Mon, 11 Oct 2004 13:28:29 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA24793
	for <pim@ietf.org>; Mon, 11 Oct 2004 13:28:26 -0400 (EDT)
Received: from rproxy.gmail.com ([64.233.170.206] helo=mproxy.gmail.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CH48r-00043e-KV
	for pim@ietf.org; Mon, 11 Oct 2004 13:39:25 -0400
Received: by mproxy.gmail.com with SMTP id 79so374490rnl
	for <pim@ietf.org>; Mon, 11 Oct 2004 10:27:33 -0700 (PDT)
Received: by 10.38.65.2 with SMTP id n2mr402832rna;
	Mon, 11 Oct 2004 10:27:33 -0700 (PDT)
Received: by 10.38.99.28 with HTTP; Mon, 11 Oct 2004 10:27:33 -0700 (PDT)
Message-ID: <fd9988fc04101110276b1953dd@mail.gmail.com>
Date: Mon, 11 Oct 2004 10:27:33 -0700
From: Sridhar Komandur <komandur@gmail.com>
To: pim@ietf.org
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Mon, 11 Oct 2004 23:28:49 -0400
Subject: [pim] bidir pim open source ...
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: komandur@pobox.com
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=subscribe>
Sender: pim-bounces@ietf.org
Errors-To: pim-bounces@ietf.org
Content-Transfer-Encoding: 7bit

Hi,

Is there a open source version of bidir pim available ? 
If yes, what is the status of its interop with router implementations ?

[please copy a reply to me as I don't subscribe to this group]

Thanks
Regards
- Sri

-- 
Please use "Reply-To" address, your email client should pick this

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


From pim-bounces@ietf.org  Mon Oct 11 23:37:37 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA26239
	for <pim-archive@lists.ietf.org>; Mon, 11 Oct 2004 23:37:37 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CHDN5-0008SX-R0; Mon, 11 Oct 2004 23:30:43 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CH9DI-0004Fa-6o
	for pim@megatron.ietf.org; Mon, 11 Oct 2004 19:04:20 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA08402
	for <pim@ietf.org>; Mon, 11 Oct 2004 19:04:16 -0400 (EDT)
Received: from almso2.att.com ([192.128.166.71] helo=almso2.proxy.att.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CH9Nq-0007Mx-AD
	for pim@ietf.org; Mon, 11 Oct 2004 19:15:18 -0400
Received: from attrh0i.attrh.att.com ([135.37.94.54])
	by almso2.proxy.att.com (AT&T IPNS/MSO-5.5) with ESMTP id
	i9BN3N0R024257 for <pim@ietf.org>; Mon, 11 Oct 2004 19:03:43 -0400
Received: from ACCLUST02EVS1.ugd.att.com (135.37.16.8) by
	attrh0i.attrh.att.com (7.1.006)
	id 4160235C0015DD06; Mon, 11 Oct 2004 19:03:35 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: Re: [pim] draft-wijnands-pim-proxy
Date: Mon, 11 Oct 2004 19:03:35 -0400
Message-ID: <34DA635B184A644DA4588E260EC0A25A086AF50B@ACCLUST02EVS1.ugd.att.com>
Thread-Topic: Re: [pim] draft-wijnands-pim-proxy
Thread-Index: AcSv5oU6UMJXz2BnQayUch4zoZyNZA==
From: "Saad, Samir S, ALABS" <samirs@att.com>
To: <mmcbride@cisco.com>
X-Spam-Score: 0.3 (/)
X-Scan-Signature: a4e5f67c5e230eddf754446d1a2201a4
X-Mailman-Approved-At: Mon, 11 Oct 2004 23:30:36 -0400
Cc: "Fenner, William C \(Bill\), ALABS" <wfenner@att.com>, dheidric@cisco.com,
        Kirk.Spessard@Level3.com, pim@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0761467031=="
Sender: pim-bounces@ietf.org
Errors-To: pim-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0761467031==
content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C4AFE6.8951C1F8"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C4AFE6.8951C1F8
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

AT&T is implementing an Internet route-free core based on MPLS. AT&T is
very interested in the functionality provided by this draft for
stability and security concerns among other reasons.

Samir Saad



Date: Mon, 11 Oct 2004 09:05:11=20
From: "Spessard, Kirk" <Kirk.Spessard@Level3.com>
To: mmcbride@cisco.com
Cc: pim@ietf.org=09
Subject: Re: [pim] draft-wijnands-pim-proxy

Due to IPVPN customer requirements, Level 3 is actively pursuing an MPLS
BGP free core by end of 2005.  (Note: Some of our large customers
perceive BGP and mBGP on our MPLS core as a security concern.)  For this
reason, Level 3 is very interested in this draft.

Kirk

> On Tue, 31 Aug 2004, Mike McBride wrote:
> > In San Diego, Ice presented draft-wijnands-pim-proxy-00 and
requested that
> > the PIM WG adopt it as a working group document. At the time, we
felt that
> > we needed to modify our WG charter before considering such
documents. Upon
> > further review we will proceed and let your voice (hands) be heard.
Please
> > review the following document and provide opinions on whether we
should
> > adopt it:
> >
> > http://www.ietf.org/internet-drafts/draft-wijnands-pim-proxy-00.txt
>
> Because there is IPR on it, my default answer would be "no, unless=20
> proven otherwise".
>
> In this case the proof would probably consist one or more of the
> following:
>
> 1. multiple other vendors indicating that they'd intend to implement=20
> the the option, and would desire it to be put on Standards Track.
>
> 2. there being strong usage case for it.  I don't see it.  BGP-free=20
> cores or L3VPN's were given as examples, but that doesn't give any=20
> hint why anyone would like to do a BGP-free core in the first place.
> If they want to do it, that's fine, but that doesn't necessarily mean=20
> we'll have to support it.  And the L3VPN case being still open was=20
> already mentioned.
>
> --
> Pekka Savola                 "You each name yourselves king, yet the
> Netcore Oy                    kingdom bleeds."
> Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings




------_=_NextPart_001_01C4AFE6.8951C1F8
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.0.6603.0">
<TITLE>Re: [pim] draft-wijnands-pim-proxy</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Arial">AT</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">&amp;T is =
implementing an Internet route-free core based on MPLS. AT&amp;T is very =
interested in the functionality provided by this draft for stability and =
security concerns among other reasons.</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Arial">Samir Saad</FONT></SPAN></P>
<BR>
<BR>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">Date: Mon, 11 Oct 2004 09:05:11 </FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">From: &quot;Spessard, Kirk&quot; &lt;</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><A HREF=3D"mailto:Kirk.Spessard@Level3.com"><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><U><FONT COLOR=3D"#0000FF" =
SIZE=3D2 FACE=3D"Courier =
New">Kirk.Spessard@Level3.com</FONT></U></SPAN><SPAN =
LANG=3D"en-us"></SPAN></A><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">&gt;</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">To:</FONT></SPAN><SPAN LANG=3D"en-us"> </SPAN><A =
HREF=3D"mailto:mmcbride@cisco.com"><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><U><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Courier =
New">mmcbride@cisco.com</FONT></U></SPAN><SPAN =
LANG=3D"en-us"></SPAN></A><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">Cc:</FONT></SPAN><SPAN LANG=3D"en-us"> </SPAN><A =
HREF=3D"mailto:pim@ietf.org"><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><U><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Courier =
New">pim@ietf.org</FONT></U></SPAN><SPAN LANG=3D"en-us"></SPAN></A><SPAN =
LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">Subject: Re: [pim] draft-wijnands-pim-proxy</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">Due to IPVPN customer requirements, Level 3 is actively pursuing an =
MPLS BGP free core by end of 2005.&nbsp; (Note: Some of our large =
customers perceive BGP and mBGP on our MPLS core as a security =
concern.)&nbsp; For this reason, Level 3 is very interested in this =
draft.</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">Kirk</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">&gt; On Tue, 31 Aug 2004, Mike McBride wrote:</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">&gt; &gt; In San Diego, Ice presented draft-wijnands-pim-proxy-00 =
and</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">requested that</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">&gt; &gt; the PIM WG adopt it as a working group document. At the =
time, we</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">felt that</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">&gt; &gt; we needed to modify our WG charter before considering =
such</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">documents. Upon</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">&gt; &gt; further review we will proceed and let your voice (hands) =
be heard.</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">Please</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">&gt; &gt; review the following document and provide opinions on =
whether we</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">should</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">&gt; &gt; adopt it:</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">&gt; &gt;</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">&gt; &gt;</FONT></SPAN><SPAN LANG=3D"en-us"> </SPAN><A =
HREF=3D"http://www.ietf.org/internet-drafts/draft-wijnands-pim-proxy-00.t=
xt"><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><U><FONT =
COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Courier =
New">http://www.ietf.org/internet-drafts/draft-wijnands-pim-proxy-00.txt<=
/FONT></U></SPAN><SPAN LANG=3D"en-us"></SPAN></A><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">&gt;</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">&gt; Because there is IPR on it, my default answer would be =
&quot;no, unless </FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">&gt; proven otherwise&quot;.</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">&gt;</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">&gt; In this case the proof would probably consist one or more of =
the</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">&gt; following:</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">&gt;</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">&gt; 1. multiple other vendors indicating that they'd intend to =
implement </FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">&gt; the the option, and would desire it to be put on Standards =
Track.</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">&gt;</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">&gt; 2. there being strong usage case for it.&nbsp; I don't see =
it.&nbsp; BGP-free </FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">&gt; cores or L3VPN's were given as examples, but that doesn't give =
any </FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">&gt; hint why anyone would like to do a BGP-free core in the first =
place.</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">&gt; If they want to do it, that's fine, but that doesn't =
necessarily mean </FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">&gt; we'll have to support it.&nbsp; And the L3VPN case being still =
open was </FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">&gt; already mentioned.</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">&gt;</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">&gt; --</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">&gt; Pekka =
Savola&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &quot;You each name yourselves king, yet =
the</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">&gt; Netcore =
Oy&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; kingdom =
bleeds.&quot;</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">&gt; Systems. Networks. Security. -- George R.R. Martin: A Clash of =
Kings</FONT></SPAN></P>
<BR>
<BR>

</BODY>
</HTML>
------_=_NextPart_001_01C4AFE6.8951C1F8--


--===============0761467031==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--===============0761467031==--



From pim-bounces@ietf.org  Mon Oct 11 23:59:06 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA27271
	for <pim-archive@lists.ietf.org>; Mon, 11 Oct 2004 23:59:06 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CHDdt-0006eT-6t; Mon, 11 Oct 2004 23:48:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CHDX2-0004bK-BS
	for pim@megatron.ietf.org; Mon, 11 Oct 2004 23:41:00 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA26347
	for <pim@ietf.org>; Mon, 11 Oct 2004 23:40:57 -0400 (EDT)
Received: from possum.icir.org ([192.150.187.67])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CHDhe-0003X1-9Y
	for pim@ietf.org; Mon, 11 Oct 2004 23:52:01 -0400
Received: from possum.icir.org (localhost [127.0.0.1])
	by possum.icir.org (8.12.9p1/8.12.8) with ESMTP id i9C3etwK015083;
	Mon, 11 Oct 2004 20:40:55 -0700 (PDT)
	(envelope-from pavlin@possum.icir.org)
Message-Id: <200410120340.i9C3etwK015083@possum.icir.org>
To: komandur@pobox.com
Subject: Re: [pim] bidir pim open source ... 
In-Reply-To: Message from Sridhar Komandur <komandur@gmail.com> of "Mon,
	11 Oct 2004 10:27:33 PDT." <fd9988fc04101110276b1953dd@mail.gmail.com> 
Date: Mon, 11 Oct 2004 20:40:55 -0700
From: Pavlin Radoslavov <pavlin@icir.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Cc: pim@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=subscribe>
Sender: pim-bounces@ietf.org
Errors-To: pim-bounces@ietf.org

> Is there a open source version of bidir pim available ? 

I believe the answer is no :(

At least, if there is any, I haven't seen any public announcements on
the relevant mailing lists.

Regards,
Pavlin

> If yes, what is the status of its interop with router implementations ?
> 
> [please copy a reply to me as I don't subscribe to this group]
> 
> Thanks
> Regards
> - Sri
> 
> -- 
> Please use "Reply-To" address, your email client should pick this
> 
> _______________________________________________
> 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-bounces@ietf.org  Tue Oct 12 01:48:05 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA05612
	for <pim-archive@lists.ietf.org>; Tue, 12 Oct 2004 01:48:05 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CHFO5-0000Nc-1o; Tue, 12 Oct 2004 01:39:53 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CHFLC-0007QU-KM
	for pim@megatron.ietf.org; Tue, 12 Oct 2004 01:36:54 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA04812
	for <pim@ietf.org>; Tue, 12 Oct 2004 01:36:54 -0400 (EDT)
Received: from netcore.fi ([193.94.160.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CHFVs-0005bE-CF
	for pim@ietf.org; Tue, 12 Oct 2004 01:47:56 -0400
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id i9C5aFb28775;
	Tue, 12 Oct 2004 08:36:15 +0300
Date: Tue, 12 Oct 2004 08:36:15 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: "Spessard, Kirk" <Kirk.Spessard@Level3.com>
Subject: Re: [pim] draft-wijnands-pim-proxy
In-Reply-To: <38981BF5940A464E9533848104308D1003F47C08@idc1exc0002.corp.global.level3.com>
Message-ID: <Pine.LNX.4.44.0410120834330.28237-100000@netcore.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Cc: mmcbride@cisco.com, pim@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=subscribe>
Sender: pim-bounces@ietf.org
Errors-To: pim-bounces@ietf.org

On Mon, 11 Oct 2004, Spessard, Kirk wrote:
> Due to IPVPN customer requirements, Level 3 is actively pursuing an MPLS
> BGP free core by end of 2005.  (Note: Some of our large customers
> perceive BGP and mBGP on our MPLS core as a security concern.)  For this
> reason, Level 3 is very interested in this draft.

I'd be very interested if you could elaborate on these customers' 
perceived "BGP and MBGP in MPLS core .. security concerns".

Seems rather like that there needs to happen either protocol
development, different kind of deployment, or customer education.

-- 
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings


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


From pim-bounces@ietf.org  Tue Oct 12 05:06:51 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA01640
	for <pim-archive@lists.ietf.org>; Tue, 12 Oct 2004 05:06:51 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CHIWs-0006jw-TD; Tue, 12 Oct 2004 05:01:11 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CHIRb-0005C6-Ez
	for pim@megatron.ietf.org; Tue, 12 Oct 2004 04:55:43 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA00900
	for <pim@ietf.org>; Tue, 12 Oct 2004 04:55:41 -0400 (EDT)
Received: from sj-iport-1-in.cisco.com ([171.71.176.70]
	helo=sj-iport-1.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CHIcI-0000Ik-SF for pim@ietf.org; Tue, 12 Oct 2004 05:06:47 -0400
Received: from sj-core-2.cisco.com (171.71.177.254)
	by sj-iport-1.cisco.com with ESMTP; 12 Oct 2004 02:03:53 -0700
X-BrightmailFiltered: true
Received: from mira-sjc5-b.cisco.com (IDENT:mirapoint@mira-sjc5-b.cisco.com
	[171.71.163.14])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id i9C8t5YJ018730;
	Tue, 12 Oct 2004 01:55:05 -0700 (PDT)
Received: from [10.10.10.78] (sjc-rraszuk-vpn1.cisco.com [10.25.90.226])
	by mira-sjc5-b.cisco.com (MOS 3.4.5-GR) with SMTP id AXY71814;
	Tue, 12 Oct 2004 01:55:24 -0700 (PDT)
Message-ID: <416B9BE7.60006@cisco.com>
Date: Tue, 12 Oct 2004 01:55:03 -0700
From: Robert Raszuk <raszuk@cisco.com>
Organization: Signature: http://www.employees.org/~raszuk/sig/
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Pekka Savola <pekkas@netcore.fi>
Subject: Re: [pim] draft-wijnands-pim-proxy
References: <Pine.LNX.4.44.0410120834330.28237-100000@netcore.fi>
In-Reply-To: <Pine.LNX.4.44.0410120834330.28237-100000@netcore.fi>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c
Content-Transfer-Encoding: 7bit
Cc: pim@ietf.org, mmcbride@cisco.com,
        "Spessard,
	Kirk" <Kirk.Spessard@Level3.com>
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: raszuk@cisco.com
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=subscribe>
Sender: pim-bounces@ietf.org
Errors-To: pim-bounces@ietf.org
Content-Transfer-Encoding: 7bit

Hi Pekka,

Putting my own personal opinion aside you have to realize that majority 
of 2547/MPLS customers today are those who migrated from L2 world 
essentially ATM & FR PVCs. Some of them have migrated from dedicated 
leased lines as well. Those were for number of years preferred methods 
of choice for WAN connectivity.

Now no matter how much education you do, how many reports you show 
indicating MPLS security to be the same as of frame relay circuits you 
can't beat the fact that once you have full IP routing table in the core 
DDoS can target your P/PE routers. On the other hand I am yet to see 
DDoS attack successfully targeting and bringing down a frame relay or 
ATM switch. DDoS attack is just not the only example. Today AFAIK 
between all L3VPN vendors once you get even level1 access to the PE you 
can telnet/ping/traceroute/ssh at will to any private VPN network. From 
frame relay or ATM switch that would not be that easy :).

While I know that there could be multiple ways to protect more core/edge 
boxes, react to attacks much faster I suspect that for the number of 
years to come providers who will claim IP route free core will gain more 
trust in the VPN services among their customers then those who don't.

Cheers,
R.

PS. My personal opinion is that what we are going via currently of a 
mixed IP/MPLS core is just a transition phase. The network of tomorrow 
clearly seems to be migrating into intelligent edge, out of band 
signaling and WDM based optical core. Therefor any protocol enhancement 
which will allow to move in this direction - just like pim-proxy draft 
does - is IMHO a very positive thing. Therefor I strongly vote that we 
should accept it as a WG document here.


 > Pekka Savola wrote:
 >
> On Mon, 11 Oct 2004, Spessard, Kirk wrote:
> 
>>Due to IPVPN customer requirements, Level 3 is actively pursuing an MPLS
>>BGP free core by end of 2005.  (Note: Some of our large customers
>>perceive BGP and mBGP on our MPLS core as a security concern.)  For this
>>reason, Level 3 is very interested in this draft.
> 
> 
> I'd be very interested if you could elaborate on these customers' 
> perceived "BGP and MBGP in MPLS core .. security concerns".
> 
> Seems rather like that there needs to happen either protocol
> development, different kind of deployment, or customer education.
> 

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


From pim-bounces@ietf.org  Tue Oct 12 11:12:13 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA29112
	for <pim-archive@lists.ietf.org>; Tue, 12 Oct 2004 11:12:13 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CHO47-0001R3-Kr; Tue, 12 Oct 2004 10:55:51 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CHO0S-00008L-8j
	for pim@megatron.ietf.org; Tue, 12 Oct 2004 10:52:04 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA26699
	for <pim@ietf.org>; Tue, 12 Oct 2004 10:52:02 -0400 (EDT)
Received: from qfe1.f10207-20.atlanta2.level3.net ([67.72.93.25]
	helo=f10207-20.adc1.level3.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CHOBB-0006uE-U6
	for pim@ietf.org; Tue, 12 Oct 2004 11:03:11 -0400
Received: from scanner3.l3.com (qfe0.f4ff49-08.idc1.oss.level3.com
	[10.1.156.103])
	by f10207-20.adc1.level3.com (8.12.10/8.12.10) with ESMTP id
	i9CEp8sO027854; Tue, 12 Oct 2004 14:51:09 GMT
Received: from scanner3.l3.com (localhost [127.0.0.1])
	by localhost.l3.com (Postfix) with ESMTP
	id 6B52778B407; Tue, 12 Oct 2004 14:51:08 +0000 (GMT)
Received: from idc1exc0001.corp.global.level3.com
	(idc1exc0001.corp.global.level3.com [10.1.7.194])
	by scanner3.l3.com (Postfix) with SMTP
	id 4267A78B405; Tue, 12 Oct 2004 14:51:08 +0000 (GMT)
Received: from idc1exc0002.corp.global.level3.com ([10.1.8.18]) by
	idc1exc0001.corp.global.level3.com with Microsoft
	SMTPSVC(6.0.3790.0); Tue, 12 Oct 2004 08:51:08 -0600
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [pim] draft-wijnands-pim-proxy
Date: Tue, 12 Oct 2004 08:51:07 -0600
Message-ID: <38981BF5940A464E9533848104308D1003F47C13@idc1exc0002.corp.global.level3.com>
Thread-Topic: [pim] draft-wijnands-pim-proxy
Thread-Index: AcSwHWimFqSUQz84Qca+aG51eteSlQATGDDQ
From: "Spessard, Kirk" <Kirk.Spessard@Level3.com>
To: "Pekka Savola" <pekkas@netcore.fi>
X-OriginalArrivalTime: 12 Oct 2004 14:51:08.0065 (UTC)
	FILETIME=[E8200110:01C4B06A]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Content-Transfer-Encoding: quoted-printable
Cc: mmcbride@cisco.com, pim@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=subscribe>
Sender: pim-bounces@ietf.org
Errors-To: pim-bounces@ietf.org
Content-Transfer-Encoding: quoted-printable

Level 3 is selling MPLS services, i.e.  RFC2547, Martini, etc.  The
issue is that these customers are paying for premium services and have
voiced concerns that Internet issues could impact their services.
Granted if the MPLS core is properly designed this is a non-issue, and
yes we are educating our customers on this point.  But when you are
competing with traditional services, this is a competitive disadvantage.

Kirk =20

-----Original Message-----
From: Pekka Savola [mailto:pekkas@netcore.fi]=20
Sent: Monday, October 11, 2004 11:36 PM
To: Spessard, Kirk
Cc: mmcbride@cisco.com; pim@ietf.org
Subject: Re: [pim] draft-wijnands-pim-proxy

On Mon, 11 Oct 2004, Spessard, Kirk wrote:
> Due to IPVPN customer requirements, Level 3 is actively pursuing an
MPLS
> BGP free core by end of 2005.  (Note: Some of our large customers
> perceive BGP and mBGP on our MPLS core as a security concern.)  For
this
> reason, Level 3 is very interested in this draft.

I'd be very interested if you could elaborate on these customers'=20
perceived "BGP and MBGP in MPLS core .. security concerns".

Seems rather like that there needs to happen either protocol
development, different kind of deployment, or customer education.

--=20
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings


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


From pim-bounces@ietf.org  Tue Oct 12 13:07:37 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09455
	for <pim-archive@lists.ietf.org>; Tue, 12 Oct 2004 13:07:37 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CHPsk-0006hi-IM; Tue, 12 Oct 2004 12:52:14 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CHPjh-00044L-Mc
	for pim@megatron.ietf.org; Tue, 12 Oct 2004 12:42:58 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA07413
	for <pim@ietf.org>; Tue, 12 Oct 2004 12:42:51 -0400 (EDT)
Received: from iramx2.ira.uni-karlsruhe.de ([141.3.10.81])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CHPuT-0001oq-T4
	for pim@ietf.org; Tue, 12 Oct 2004 12:54:02 -0400
Received: from iraspam.ira.uni-karlsruhe.de ([141.3.10.6]
	helo=spamhost.ira.uka.de)
	by iramx2.ira.uni-karlsruhe.de with esmtp (Exim 3.30 #10)
	id 1CHPjW-0006LX-00; Tue, 12 Oct 2004 18:42:42 +0200
Received: from amavis by spamhost.ira.uka.de with scanned-ok (Exim 3.30 #3)
	id 1CHPjW-0005Lj-00; Tue, 12 Oct 2004 18:42:42 +0200
Received: from irams1.ira.uni-karlsruhe.de ([141.3.10.5]
	helo=irams1.ira.uka.de)
	by spamhost.ira.uka.de with esmtp (Exim 3.30 #3)
	id 1CHPjP-0005Kx-00; Tue, 12 Oct 2004 18:42:35 +0200
Received: from i72ms1.tm.uni-karlsruhe.de
	([141.3.70.16] helo=smtp.ipv6.tm.uni-karlsruhe.de ident=8)
	by irams1.ira.uka.de with esmtp (Exim 3.30 #7 )
	id 1CHPjP-00045a-00; Tue, 12 Oct 2004 18:42:35 +0200
Received: from borg.ipv6.tm.uni-karlsruhe.de
	([2001:638:204:6:202:b3ff:feab:632e])
	by smtp.ipv6.tm.uni-karlsruhe.de with esmtp (TLSv1:DES-CBC3-SHA:168)
	(Exim 4.12) id 1CHPjH-00018H-00; Tue, 12 Oct 2004 18:42:27 +0200
Received: from localhost ([127.0.0.1])
	by borg.ipv6.tm.uni-karlsruhe.de with esmtp (Exim 4.30)
	id 1CHPjH-00059p-8Q; Tue, 12 Oct 2004 18:42:27 +0200
Message-ID: <416C0973.6070805@tm.uka.de>
Date: Tue, 12 Oct 2004 18:42:27 +0200
From: Mark Doll <doll@tm.uka.de>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
	rv:1.7) Gecko/20040803 Thunderbird/0.7.3 Mnenhy/0.6.0.104
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: edrt <edrt@citiz.net>
Subject: Re: [pim] some questions/comments to PIM-SM draft-10
References: <mp-m2n.ietf.pim_200410061239.IAA19409@ietf.org>
In-Reply-To: <mp-m2n.ietf.pim_200410061239.IAA19409@ietf.org>
X-Enigmail-Version: 0.85.0.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Content-Transfer-Encoding: 7bit
Cc: "pim@ietf.org" <pim@ietf.org>
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=subscribe>
Sender: pim-bounces@ietf.org
Errors-To: pim-bounces@ietf.org
Content-Transfer-Encoding: 7bit

Hi Yi,

edrt wrote:
> Different implemenation might use different data & control plane synchronization 
> model, may be on some platform this won't be a issue. So my personal opinion is to
> leave this synchroniaztion issue to the implementor of the protocol and platform 
> rather than changing the protocol.

I agree, leaving it to the implementation is better, of course. But when 
specifying something that's not efficiently implementable, the statement
"A PIM-SM implementation [...] will still be comformant with this 
specification so long as it results in the same externally visible 
protocol behavior [...]" will render all those efficient implementations 
non-conformant. So it should be made explicit in the draft that, 
regarding the data forwarding rule, this requirement can be relaxed and 
it's up to the implementation how to relax it. Then I'm fine with an 
unimplementable abstract forwarding rule.

- Mark.

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


From pim-bounces@ietf.org  Tue Oct 12 15:11:10 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA20430
	for <pim-archive@lists.ietf.org>; Tue, 12 Oct 2004 15:11:10 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CHRzw-0003Ke-U7; Tue, 12 Oct 2004 15:07:48 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CHRui-0007GH-Vp
	for pim@megatron.ietf.org; Tue, 12 Oct 2004 15:02:25 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA19434
	for <pim@ietf.org>; Tue, 12 Oct 2004 15:02:24 -0400 (EDT)
Received: from netcore.fi ([193.94.160.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CHS5V-0004ro-G7
	for pim@ietf.org; Tue, 12 Oct 2004 15:13:34 -0400
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id i9CJ1Wl15813;
	Tue, 12 Oct 2004 22:01:32 +0300
Date: Tue, 12 Oct 2004 22:01:32 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: Robert Raszuk <raszuk@cisco.com>
Subject: Re: [pim] draft-wijnands-pim-proxy
In-Reply-To: <416B9BE7.60006@cisco.com>
Message-ID: <Pine.LNX.4.44.0410122146430.15185-100000@netcore.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f607d15ccc2bc4eaf3ade8ffa8af02a0
Cc: pim@ietf.org, mmcbride@cisco.com,
        "Spessard,
	Kirk" <Kirk.Spessard@Level3.com>
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=subscribe>
Sender: pim-bounces@ietf.org
Errors-To: pim-bounces@ietf.org

This is getting off-topic so maybe we should drop the discussion..

On Tue, 12 Oct 2004, Robert Raszuk wrote:
> Now no matter how much education you do, how many reports you show 
> indicating MPLS security to be the same as of frame relay circuits you 
> can't beat the fact that once you have full IP routing table in the core 
> DDoS can target your P/PE routers. 

I must be missing something.  You don't need full BGP table in the 
core to be able to attack the core.  It just requires that there is a 
route to the edge network, and from the edge network to the BGP-free 
core network.  Granted, the BGP-free core (if they didn't have a 
default route) couldn't send return packets, but the boxes would be 
just as dead.

The above can be easily achieved as well with just putting in access
lists blocking any access to the infrastructure boxes except from
specific IP address ranges at the edges.

> DDoS attack successfully targeting and bringing down a frame relay or 
> ATM switch. 

[well, we've had some issues when the management ethernet of the ATM 
switch was attacked when it wasn't properly protected using access 
lists..]

If we were talking about 'IP-free core', then the analogy would be
more to the point.. but AFAICS we aren't, so omitting BGP brings very
little, unless you believe there is an inherent problem with BGP as
such.

> DDoS attack is just not the only example. Today AFAIK 
> between all L3VPN vendors once you get even level1 access to the PE you 
> can telnet/ping/traceroute/ssh at will to any private VPN network. From 
> frame relay or ATM switch that would not be that easy :).

Do you really think that's preventable?  If one can compromise a
router, you naturally can do all kinds of Man-in-the-middle fun.  And
because one can set up MPLS LSP's in any manner one wants in inside
the provider core, there's little one can do here.

The only alternatives are 1) protecting the PE box from the attackers, 
and 2) using CE-CE (-like IPsec).  BGP-free core does not help with 1) 
-- IP-free core would though -- but this can be achieved with access 
lists etc.
 
> While I know that there could be multiple ways to protect more core/edge 
> boxes, react to attacks much faster I suspect that for the number of 
> years to come providers who will claim IP route free core will gain more 
> trust in the VPN services among their customers then those who don't.

You mention IP free core.  But the argument was about BGP-free core, 
not about IP-free core, unless I'm missing something ?

-- 
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings



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


From pim-bounces@ietf.org  Tue Oct 12 15:34:49 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA23082
	for <pim-archive@lists.ietf.org>; Tue, 12 Oct 2004 15:34:49 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CHSHE-0005SB-JE; Tue, 12 Oct 2004 15:25:40 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CHSA6-0000XR-K4
	for pim@megatron.ietf.org; Tue, 12 Oct 2004 15:18:18 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA21471
	for <pim@ietf.org>; Tue, 12 Oct 2004 15:18:17 -0400 (EDT)
Received: from sj-iport-2-in.cisco.com ([171.71.176.71]
	helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CHSKt-0005AV-EL for pim@ietf.org; Tue, 12 Oct 2004 15:29:28 -0400
Received: from sj-core-5.cisco.com (171.71.177.238)
	by sj-iport-2.cisco.com with ESMTP; 12 Oct 2004 12:23:57 -0700
Received: from mira-sjc5-b.cisco.com (IDENT:mirapoint@mira-sjc5-b.cisco.com
	[171.71.163.14])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id i9CJHhOE012298;
	Tue, 12 Oct 2004 12:17:44 -0700 (PDT)
Received: from [10.10.10.78] (sjc-rraszuk-vpn1.cisco.com [10.25.90.226])
	by mira-sjc5-b.cisco.com (MOS 3.4.5-GR) with SMTP id AXZ11976;
	Tue, 12 Oct 2004 12:18:04 -0700 (PDT)
Message-ID: <416C2DD4.9030200@cisco.com>
Date: Tue, 12 Oct 2004 12:17:40 -0700
From: Robert Raszuk <raszuk@cisco.com>
Organization: Signature: http://www.employees.org/~raszuk/sig/
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Pekka Savola <pekkas@netcore.fi>
Subject: Re: [pim] draft-wijnands-pim-proxy
References: <Pine.LNX.4.44.0410122146430.15185-100000@netcore.fi>
In-Reply-To: <Pine.LNX.4.44.0410122146430.15185-100000@netcore.fi>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Content-Transfer-Encoding: 7bit
Cc: pim@ietf.org, mmcbride@cisco.com,
        "Spessard,
	Kirk" <Kirk.Spessard@Level3.com>
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: raszuk@cisco.com
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=subscribe>
Sender: pim-bounces@ietf.org
Errors-To: pim-bounces@ietf.org
Content-Transfer-Encoding: 7bit

Pekka,

> This is getting off-topic so maybe we should drop the discussion..

As you wish. I just hope that in the same time we can drop the equally 
off-topic arguments against pim-proxy draft ;).

> The above can be easily achieved as well with just putting in access
> lists blocking any access to the infrastructure boxes except from
> specific IP address ranges at the edges.

Ever heard about spoofing ?

> You mention IP free core.  But the argument was about BGP-free core, 
> not about IP-free core, unless I'm missing something ?

In particular the argument is not about BGP free core, it is not about 
IP free core ... it is in almost in all SP customers I interact with 
about Internet routes free core.

Cheers,
R.


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


From pim-bounces@ietf.org  Tue Oct 12 20:35:23 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA02725
	for <pim-archive@lists.ietf.org>; Tue, 12 Oct 2004 20:35:23 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CHWyh-0001m5-82; Tue, 12 Oct 2004 20:26:51 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CHWuo-0006Nb-Ht
	for pim@megatron.ietf.org; Tue, 12 Oct 2004 20:22:50 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA01480
	for <pim@ietf.org>; Tue, 12 Oct 2004 20:22:49 -0400 (EDT)
Received: from web12308.mail.yahoo.com ([216.136.173.106])
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CHX5d-0007Ud-3u
	for pim@ietf.org; Tue, 12 Oct 2004 20:34:02 -0400
Message-ID: <20041013002246.81626.qmail@web12308.mail.yahoo.com>
Received: from [63.86.107.226] by web12308.mail.yahoo.com via HTTP;
	Tue, 12 Oct 2004 17:22:46 PDT
Date: Tue, 12 Oct 2004 17:22:46 -0700 (PDT)
From: Jonathan Day <imipak@yahoo.com>
To: pim@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 25620135586de10c627e3628c432b04a
Cc: komandur@pobox.com
Subject: [pim] PIM-BI and the state of multicasting in general
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=subscribe>
Sender: pim-bounces@ietf.org
Errors-To: pim-bounces@ietf.org

Unfortunately, there seem to be no Open Source PIM
implementations under active development. By far the
most common(!) version of PIM out there is PIM-SM.
There's an excellent stand-alone router for that, plus
an implementation in Xorp. These are the only versions
of PIM I've managed to get running on recent
platforms.

A stand-alone PIM-DM router exists, based on an early
version of the stand-alone PIM-SM router, but it does
not seem to compile on recent versions of Linux. A
partial PIM-DM implementation exists for MRT, an
abandoned modular router, but I've no information on
whether it's usable.

There are no PIM implementations (AFAICT) for Zebra
(apparently abandoned), Quagga (based on Zebra and
also apparently abandoned) or Click (the only Open
Source software router that appears to still be
maintained).

On the kernel side, Linux supports PIM-SM only. I
don't know about the *BSDs. Linux is not exactly fast
on the uptake on multicasting, only recently adding
the basic portions of IGMPv3, so I'm not expecting
anything dramatic to happen there with PIM. Any new
support is likely to be user-side only.

Unfortunately, as noted above, the user-side
development seems to be in not much better shape. A
quick glance at directories such as Freshmeat.net
shows that there's no shortage of developers with
time, but multicasting doesn't seem to be an area that
is attracting much interest.

Slightly off-topic, but related, it's not just
multicast routing that's taking a beating. A lot of
multicast end-user tools, such as SDR, VIC, RAT, etc,
are also unmaintained. I'm getting just a little
concerned that multicasting is heading the way of the
dodo. A few announcement services optionally use it,
but you hardly need PIMv2 (Bidirectional) +
Source-Specific Multicasting + Authentication to
support things like RIPv2 or SIP, or packages such as
the Squid web cache.

Just a thought, but maybe there needs to be a little
more awareness amongst users (and probably admins) on
what's out there and why they might want to use it.

> From: Sridhar Komandur <komandur@gmail.com>
> Subject: [pim] bidir pim open source ...
> To: pim@ietf.org
> Message-ID:
> <fd9988fc04101110276b1953dd@mail.gmail.com>
> Content-Type: text/plain; charset=US-ASCII
> 
> Hi,
> 
> Is there a open source version of bidir pim
> available ? 
> If yes, what is the status of its interop with
> router implementations ?
> 
> [please copy a reply to me as I don't subscribe to
> this group]



		
__________________________________
Do you Yahoo!?
Yahoo! Mail Address AutoComplete - You start. We finish.
http://promotions.yahoo.com/new_mail 

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


From pim-bounces@ietf.org  Wed Oct 13 01:45:56 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA23670
	for <pim-archive@lists.ietf.org>; Wed, 13 Oct 2004 01:45:56 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CHbuE-0006PC-Pn; Wed, 13 Oct 2004 01:42:34 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CHbtH-00063N-4H
	for pim@megatron.ietf.org; Wed, 13 Oct 2004 01:41:35 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA23365
	for <pim@ietf.org>; Wed, 13 Oct 2004 01:41:33 -0400 (EDT)
Received: from netcore.fi ([193.94.160.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CHc47-0004bu-HH
	for pim@ietf.org; Wed, 13 Oct 2004 01:52:48 -0400
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id i9D5equ29620;
	Wed, 13 Oct 2004 08:40:52 +0300
Date: Wed, 13 Oct 2004 08:40:52 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: Robert Raszuk <raszuk@cisco.com>
Subject: Re: [pim] draft-wijnands-pim-proxy
In-Reply-To: <416C2DD4.9030200@cisco.com>
Message-ID: <Pine.LNX.4.44.0410130835210.28603-100000@netcore.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Cc: pim@ietf.org, mmcbride@cisco.com,
        "Spessard,
	Kirk" <Kirk.Spessard@Level3.com>
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=subscribe>
Sender: pim-bounces@ietf.org
Errors-To: pim-bounces@ietf.org

On Tue, 12 Oct 2004, Robert Raszuk wrote:
> > The above can be easily achieved as well with just putting in access
> > lists blocking any access to the infrastructure boxes except from
> > specific IP address ranges at the edges.
> 
> Ever heard about spoofing ?

Yes.  We disallow our internal prefixes (especially the management
ones, but actually all of them) to be used as source addresses in
packets coming at us from peers and upstreams.  Customers are also
prevented from spoofing by the use of strict uRPF. That disallows
anyone spoofing the management access from the outside.

If we wanted to block DoS attacks, we could just additionally put in
an ACL which would block access to specific destinations (the routing
infrastructure) except from a few specific IP addresses.

I guess your assumptions stem from the fact that many SP's don't
bother to do ingress filtering on their edges, or protect their
infrastructure addresses from being spoofed properly.  That brings a
LOT of pain, and I don't think removing 'IP' from the core is
necessarily the right way to fix these problems.

-- 
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings


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


From pim-bounces@ietf.org  Wed Oct 13 03:45:03 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA28546
	for <pim-archive@lists.ietf.org>; Wed, 13 Oct 2004 03:45:02 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CHdlx-0006Uf-5K; Wed, 13 Oct 2004 03:42:09 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CHdhO-000508-E8
	for pim@megatron.ietf.org; Wed, 13 Oct 2004 03:37:26 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA27826
	for <pim@ietf.org>; Wed, 13 Oct 2004 03:37:23 -0400 (EDT)
Received: from tyholt.uninett.no ([158.38.60.10])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CHdsF-0006Pk-3K
	for pim@ietf.org; Wed, 13 Oct 2004 03:48:39 -0400
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 i9D7an60012029;
	Wed, 13 Oct 2004 09:36:49 +0200
Received: (from venaas@localhost)
	by sverresborg.uninett.no (8.12.8/8.12.8/Submit) id i9D7amhf021422;
	Wed, 13 Oct 2004 09:36:48 +0200
X-Authentication-Warning: sverresborg.uninett.no: venaas set sender to
	Stig.Venaas@uninett.no using -f
Date: Wed, 13 Oct 2004 09:36:48 +0200
From: Stig Venaas <Stig.Venaas@uninett.no>
To: Jonathan Day <imipak@yahoo.com>
Subject: Re: [pim] PIM-BI and the state of multicasting in general
Message-ID: <20041013073648.GB21364@sverresborg.uninett.no>
References: <20041013002246.81626.qmail@web12308.mail.yahoo.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20041013002246.81626.qmail@web12308.mail.yahoo.com>
User-Agent: Mutt/1.4.1i
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 00e94c813bef7832af255170dca19e36
Cc: komandur@pobox.com, pim@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=subscribe>
Sender: pim-bounces@ietf.org
Errors-To: pim-bounces@ietf.org

On Tue, Oct 12, 2004 at 05:22:46PM -0700, Jonathan Day wrote:
> Unfortunately, there seem to be no Open Source PIM
> implementations under active development. By far the
> most common(!) version of PIM out there is PIM-SM.
> There's an excellent stand-alone router for that, plus
> an implementation in Xorp. These are the only versions
> of PIM I've managed to get running on recent
> platforms.

I'm mostly involved with IPv6. I've run Xorp and also "pim6sd".
With the latter you can do IPv6 multicast routing on at least
FreeBSD, NetBSD and Linux. The IPv6 multicast support in the
Linux kernel has just been added.

I thought there was both working pimsd and also gated to do
IPv4 PIM-SM on Linux, but I've never tried myself.

> A stand-alone PIM-DM router exists, based on an early
> version of the stand-alone PIM-SM router, but it does
> not seem to compile on recent versions of Linux. A
> partial PIM-DM implementation exists for MRT, an
> abandoned modular router, but I've no information on
> whether it's usable.
> 
> There are no PIM implementations (AFAICT) for Zebra
> (apparently abandoned), Quagga (based on Zebra and
> also apparently abandoned) or Click (the only Open
> Source software router that appears to still be
> maintained).
> 
> On the kernel side, Linux supports PIM-SM only. I
> don't know about the *BSDs. Linux is not exactly fast

At least some of the *BSDs do both IPv4 and IPv6 PIM-SM.

> on the uptake on multicasting, only recently adding
> the basic portions of IGMPv3, so I'm not expecting
> anything dramatic to happen there with PIM. Any new
> support is likely to be user-side only.

Linux also got MLDv2.

> Unfortunately, as noted above, the user-side
> development seems to be in not much better shape. A
> quick glance at directories such as Freshmeat.net
> shows that there's no shortage of developers with
> time, but multicasting doesn't seem to be an area that
> is attracting much interest.

At least for IPv6 there are some developments. There's
also some development of IPv4 AMT on misc platforms.

> Slightly off-topic, but related, it's not just
> multicast routing that's taking a beating. A lot of
> multicast end-user tools, such as SDR, VIC, RAT, etc,
> are also unmaintained. I'm getting just a little

UCL does at least some maintenance of the tools.

> concerned that multicasting is heading the way of the
> dodo. A few announcement services optionally use it,
> but you hardly need PIMv2 (Bidirectional) +
> Source-Specific Multicasting + Authentication to
> support things like RIPv2 or SIP, or packages such as
> the Squid web cache.
> 
> Just a thought, but maybe there needs to be a little
> more awareness amongst users (and probably admins) on
> what's out there and why they might want to use it.

I agree that not enough is happening but it's not quite
as bad as you say. And in particular for IPv6 I see some
activities. One example of large IPv6 multicast deployment
is M6Bone, http://www.m6bone.net/

Stig

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


From pim-bounces@ietf.org  Wed Oct 13 11:16:41 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA07172
	for <pim-archive@lists.ietf.org>; Wed, 13 Oct 2004 11:16:41 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CHklC-0007YL-9p; Wed, 13 Oct 2004 11:09:50 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CHkcb-0005CM-0A
	for pim@megatron.ietf.org; Wed, 13 Oct 2004 11:00:57 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA05494
	for <pim@ietf.org>; Wed, 13 Oct 2004 11:00:50 -0400 (EDT)
Received: from colo-dns-ext1.juniper.net ([207.17.137.57])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CHknS-0006rM-0t
	for pim@ietf.org; Wed, 13 Oct 2004 11:12:11 -0400
Received: from merlot.juniper.net (merlot.juniper.net [172.17.27.10])
	by colo-dns-ext1.juniper.net (8.11.3/8.9.3) with ESMTP id i9DF0H985651
	for <pim@ietf.org>; Wed, 13 Oct 2004 08:00:17 -0700 (PDT)
	(envelope-from yakov@juniper.net)
Received: from juniper.net (sapphire.juniper.net [172.17.28.108])
	by merlot.juniper.net (8.11.3/8.11.3) with ESMTP id i9DF0Ce57868
	for <pim@ietf.org>; Wed, 13 Oct 2004 08:00:12 -0700 (PDT)
	(envelope-from yakov@juniper.net)
Message-Id: <200410131500.i9DF0Ce57868@merlot.juniper.net>
To: pim@ietf.org
Subject: Re: [pim] draft-wijnands-pim-proxy 
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <29228.1097679611.1@juniper.net>
Date: Wed, 13 Oct 2004 08:00:12 -0700
From: Yakov Rekhter <yakov@juniper.net>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=subscribe>
Sender: pim-bounces@ietf.org
Errors-To: pim-bounces@ietf.org

Folks,

So far the discussion about draft-wijnands-pim-proxy seems to be
focused on one particular problem that this draft is intended to solve
- BGP-free core or Internet routes free core.

However, I'd like to point out that the solution proposed in
draft-wijnands-pim-proxy is *not* limited to that particular problem,
but is also claimed to support traffic engineering with PIM (see
section 2.4.2 of the draft).

I think that prior to extending PIM with traffic engineering
capabilities, the authors of draft-wijnands-pim-proxy need to answer
the question whether adding vector stack to PIM would be adequate
to match the requirements for p2mp traffic engineering.

Yakov.

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


From pim-bounces@ietf.org  Wed Oct 13 16:42:27 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA04464
	for <pim-archive@lists.ietf.org>; Wed, 13 Oct 2004 16:42:27 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CHpoq-00017b-3P; Wed, 13 Oct 2004 16:33:56 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CHphq-00070b-90
	for pim@megatron.ietf.org; Wed, 13 Oct 2004 16:26:42 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA03318
	for <pim@ietf.org>; Wed, 13 Oct 2004 16:26:42 -0400 (EDT)
Received: from rproxy.gmail.com ([64.233.170.195] helo=mproxy.gmail.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CHpso-0005YG-Tr
	for pim@ietf.org; Wed, 13 Oct 2004 16:38:06 -0400
Received: by mproxy.gmail.com with SMTP id 77so17895rnk
	for <pim@ietf.org>; Wed, 13 Oct 2004 13:26:35 -0700 (PDT)
Received: by 10.38.82.45 with SMTP id f45mr3069587rnb;
	Wed, 13 Oct 2004 13:26:34 -0700 (PDT)
Received: by 10.38.74.62 with HTTP; Wed, 13 Oct 2004 13:26:34 -0700 (PDT)
Message-ID: <1e0d9731041013132634525f0d@mail.gmail.com>
Date: Wed, 13 Oct 2004 13:26:34 -0700
From: Ashish Ranjan <hiashu@gmail.com>
To: pim@ietf.org
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Content-Transfer-Encoding: 7bit
Subject: [pim] Dense mode leaf node detection
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Ashish Ranjan <hiashu@gmail.com>
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=subscribe>
Sender: pim-bounces@ietf.org
Errors-To: pim-bounces@ietf.org
Content-Transfer-Encoding: 7bit

Hi,

   Based on new PIM-DM draft (dm-new-v2-05.txt), in a topology where
there are 2 routers on leaf, how does they prune the oif. The draft
has no mention of assert winner to go into prune state (in the absence
of a listener) unlike the older pim-dm draft.

For example.

              |                          |
             \ /                        \ /     
        +-----------+              +-----------+    
        |     A     |              |     B     | 
        |           |              |           |       
        +-----------+              +-----------+
  10.1.1.1/24|                           |  10.1.1.2/24
             +---------------------------+

In the above topology either of the router could be assert winner on
down i/f. Assuming A is assert winner and no listener for the stream
on the downstream i/f, how does A decide on pruning the upstream tree.
How would A's olist would be NULL. Or A would keep forwarding.   What
am I missing here.
 
Any clarification would be appreciated. I did not find any discussion
on this in this list.

thanks
-Ashish

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


From pim-bounces@ietf.org  Thu Oct 14 07:57:16 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA06101
	for <pim-archive@lists.ietf.org>; Thu, 14 Oct 2004 07:57:16 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CI464-0000vz-2E; Thu, 14 Oct 2004 07:48:40 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CI3yH-0007gK-F4
	for pim@megatron.ietf.org; Thu, 14 Oct 2004 07:40:38 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA04653
	for <pim@ietf.org>; Thu, 14 Oct 2004 07:40:36 -0400 (EDT)
Received: from gate12.itt.com ([151.190.254.107] helo=fwetgfw2r.itt.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CI49Q-0007zw-Sb
	for pim@ietf.org; Thu, 14 Oct 2004 07:52:09 -0400
Received: from no.name.available by fwetgfw2r.itt.com
	via smtpd (for ietf-mx.ietf.org [132.151.6.1]) with ESMTP;
	Thu, 14 Oct 2004 06:40:35 -0500
Received: from njbridge.avionics.de.ittind.com ([151.190.100.204]) by
	fwdcmail6.fwdc.de.ittind.com with Microsoft SMTPSVC(5.0.2195.6713); 
	Thu, 14 Oct 2004 06:40:19 -0500
Received: from ACDNJMAILSRV02.acd.de.ittind.com ([151.190.3.218]) by
	njbridge.avionics.de.ittind.com with Microsoft
	SMTPSVC(5.0.2195.6713); Thu, 14 Oct 2004 07:40:25 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.0.6556.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [pim] Dense mode leaf node detection
Date: Thu, 14 Oct 2004 07:40:24 -0400
Message-ID: <2CA4524FA012F14BAE5D896D492B38682C5997@ACDNJMAILSRV02.acd.de.ittind.com>
Thread-Topic: [pim] Dense mode leaf node detection
Thread-Index: AcSxZT3ZSchse+pZT926DzSyymT9QgAfItbQ
From: "Nicholas, Jonathan" <Jonathan.Nicholas@itt.com>
To: "Ashish Ranjan" <hiashu@gmail.com>, <pim@ietf.org>
X-OriginalArrivalTime: 14 Oct 2004 11:40:25.0013 (UTC)
	FILETIME=[985C5650:01C4B1E2]
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 244a2fd369eaf00ce6820a760a3de2e8
Content-Transfer-Encoding: quoted-printable
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=subscribe>
Sender: pim-bounces@ietf.org
Errors-To: pim-bounces@ietf.org
Content-Transfer-Encoding: quoted-printable


When transitioning to an Assert Loser state on a downstream interface, a=
 router sends a Prune on that interface to resolve the problem described. =
 Since there are no other routers on the net, no Join will be sent and the=
 assert winner will transition to a Pruned state.

Jonathan Nicholas
Network Systems Engineer
ITT Aerospace/Communications Division

> -----Original Message-----
> From: pim-bounces@ietf.org [mailto:pim-bounces@ietf.org]On Behalf Of
> Ashish Ranjan
> Sent: Wednesday, October 13, 2004 4:27 PM
> To: pim@ietf.org
> Subject: [pim] Dense mode leaf node detection
>=0D
>=0D
> Hi,
>=0D
>    Based on new PIM-DM draft (dm-new-v2-05.txt), in a topology where
> there are 2 routers on leaf, how does they prune the oif. The draft
> has no mention of assert winner to go into prune state (in the absence
> of a listener) unlike the older pim-dm draft.
>=0D
> For example.
>=0D
>               |                          |
>              \ /                        \ /    =0D
>         +-----------+              +-----------+   =0D
>         |     A     |              |     B     |=0D
>         |           |              |           |      =0D
>         +-----------+              +-----------+
>   10.1.1.1/24|                           |  10.1.1.2/24
>              +---------------------------+
>=0D
> In the above topology either of the router could be assert winner on
> down i/f. Assuming A is assert winner and no listener for the stream
> on the downstream i/f, how does A decide on pruning the upstream tree.
> How would A's olist would be NULL. Or A would keep forwarding.   What
> am I missing here.
> =0D
> Any clarification would be appreciated. I did not find any discussion
> on this in this list.
>=0D
> thanks
> -Ashish
>=0D
> _______________________________________________
> pim mailing list
> pim@ietf.org
> https://www1.ietf.org/mailman/listinfo/pim
>=0D

************************************
This e-mail and any files transmitted with it are proprietary and intended=
 solely for the use of the individual or entity to whom they are addressed.=
 If you have received this e-mail in error please notify the sender. Please=
 note that any views or opinions presented in this e-mail are solely those=
 of the author and do not necessarily represent those of ITT Industries,=
 Inc. The recipient should check this e-mail and any attachments for the=
 presence of viruses. ITT Industries accepts no liability for any damage=
 caused by any virus transmitted by this e-mail.
************************************

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


From pim-bounces@ietf.org  Thu Oct 14 15:31:30 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA18865
	for <pim-archive@lists.ietf.org>; Thu, 14 Oct 2004 15:31:30 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CIBGd-0000iU-Mp; Thu, 14 Oct 2004 15:28:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CIBGD-0000T8-5W
	for pim@megatron.ietf.org; Thu, 14 Oct 2004 15:27:37 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA18680
	for <pim@ietf.org>; Thu, 14 Oct 2004 15:27:35 -0400 (EDT)
Received: from smtp.dataconnection.com ([192.91.191.4] helo=smtp.datcon.co.uk)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CIBRQ-0001Cb-HW
	for pim@ietf.org; Thu, 14 Oct 2004 15:39:13 -0400
Received: by goodman.datcon.co.uk with Internet Mail Service (5.5.2657.72)
	id <47GB0C19>; Thu, 14 Oct 2004 20:26:45 +0100
Message-ID: <53F74F5A7B94D511841C00B0D0AB16F8035811EA@baker.datcon.co.uk>
From: James Lingard <James.Lingard@dataconnection.com>
To: "'Mark Doll'" <doll@tm.uka.de>
Subject: RE: [pim] PIM-SM: timer value computation for join suppression
Date: Thu, 14 Oct 2004 20:26:29 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1b0e72ff1bbd457ceef31828f216a86
Cc: "'pim@ietf.org'" <pim@ietf.org>
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=subscribe>
Sender: pim-bounces@ietf.org
Errors-To: pim-bounces@ietf.org

Mark,

I've just come across this old email of yours which doesn't seem to have had
any further discussion on the mailing list.  My responses are inline.

PIM-SM authors,

I think that Mark has a good point about the potential Join message
implosion if t_joinsuppress is determined by the received Holdtime.  It
would be nice to see this addressed in the draft.

Regards,
James.

> -----Original Message-----
> From: pim-bounces@ietf.org [mailto:pim-bounces@ietf.org]On Behalf Of
> Mark Doll
> Sent: 12 August 2004 13:41
> To: pim@ietf.org
> Subject: [pim] PIM-SM: timer value computation for join suppression
> 
> I'm confused about the Join(*,*,RP)/(*,G)/(S,G) timer value 
> computation when suppressing joins.
> 
> The spec states:
> 
>            Let t_joinsuppress be the minimum of t_suppressed and the
>            HoldTime from the Join/Prune message triggering this event.
>            If the Join Timer is set to expire in less than 
>            t_joinsuppress
>            seconds, reset it so that it expires after t_joinsuppress
>            seconds.  If the Join Timer is set to expire in more than
>            t_joinsuppress seconds, leave it unchanged.
> 
> 
> Let's assume HoldTime is small enough to determine the value of 
> t_joinsuppress (presumably the routers on the link have been 
> configured with a different t_periodic) and the router sending this
> Join message stops sending periodic Joins (i.e. the router has gone
> down or a subsequent Prune message has been lost). Since the
> upstream router sets its Expiry Timer to exactly the same value,
> this seems to be a race condition.

If the Holdtime of the message is small enough to determine the value of
t_joinsuppress, it must be less than 1.1 * t_periodic for those routers, and
so it must be (much) less than those routers' Holdtimes.  Therefore, in the
normal case, the upstream router won't set its Expiry Timer to the Holdtime
of the message, since its Expiry Timer will already be running with a larger
period.  So there in no race condition.

Admittedly, if the previous two Join messages from the router with the
larger Holdtime have been lost, then a race condition could arise.  However,
I suspect that this is not a case that the authors had considered important.

> And this might also cause a Join
> message implosion if there are more than two downstream routers with
> Join state.

I agree that this looks like a problem.  I think better definitions of
t_suppressed and t_joinsuppress would be something like:

  t_suppressed = t_periodic when Suppression_Enabled(I) is true, 0 otherwise
  t_joinsuppress = rand(1.0 * min(t_periodic, Holdtime), 1.4 *
min(t_periodic, Holdtime)) 

so that the randomization takes place in every case.

> And of course there is no protection against lost Join messages any
> more as it is the case when the Join Timer periodically fires 3.5
> times during a HoldTime period allowing for two Join messages to be
> lost.
> 
> And what's the motivation behind leaving the Join Timer 
> unchanged when its value is greater than t_joinsuppress? If, again
> the router sending periodic Joins stops doing so, the Expiry Timer
> at the upstream router expires after Holdtime. So the upstream
> router loses Join state since the Join is still suppressed, because
> the Join Timer has not been reduced to HoldTime = t_joinsuppress.

This is not true, because the upstream router can never decrease its Expiry
Timer as a result of receiving a Join message.  Inevitably, the protection
against lost Join messages is marginally weakened by Join suppression, but
it is not removed.

> So why not specifying something like:
> 
>            Reset the Join Timer to the minimum of t_suppressed and
>            HoldTime/3.5*rand(1.1,1.4), where HoldTime is the HoldTime
>            from the Join/Prune message triggering this event.
> 
> Since I'm not a PIM guru I might have overlooked something really 
> important and all the above can never happen. In this case I'm sorry 
> for bothering you with all this...
> 
> Sincerly, Mark Doll.

-- 
James Lingard
Data Connection Ltd (DCL)
http://www.dataconnection.com/

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


From pim-bounces@ietf.org  Thu Oct 14 15:49:57 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA22070
	for <pim-archive@lists.ietf.org>; Thu, 14 Oct 2004 15:49:57 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CIBQ9-0005GA-K6; Thu, 14 Oct 2004 15:37:53 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CIBND-0003qn-6g
	for pim@megatron.ietf.org; Thu, 14 Oct 2004 15:34:51 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA19179
	for <pim@ietf.org>; Thu, 14 Oct 2004 15:34:49 -0400 (EDT)
Received: from smtp2.dataconnection.com ([192.91.191.8]
	helo=smtp2.datcon.co.uk) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CIBYQ-0001KY-QW for pim@ietf.org; Thu, 14 Oct 2004 15:46:27 -0400
Received: by beiderbecke.datcon.co.uk with Internet Mail Service (5.5.2653.19)
	id <45CQTNX3>; Thu, 14 Oct 2004 20:34:01 +0100
Message-ID: <53F74F5A7B94D511841C00B0D0AB16F8035811EB@baker.datcon.co.uk>
From: James Lingard <James.Lingard@dataconnection.com>
To: "'pim@ietf.org'" <pim@ietf.org>
Subject: RE: [pim] Hello HoldTime and Assert questions
Date: Thu, 14 Oct 2004 20:33:43 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c0bedb65cce30976f0bf60a0a39edea4
Cc: "'Venugopal Hemige'" <vhemige@yahoo.com>
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=subscribe>
Sender: pim-bounces@ietf.org
Errors-To: pim-bounces@ietf.org

All,

This post made to the mailing list in July seems never to have had any
responses; my thoughts are inline below.

I think that Venu has pointed out a genuine problem with infinite Assert
metrics, which ought to be addressed in the draft.  Does anyone else have
any thoughts on this?

Regards,
James.

-----Original Message-----
From: pim-bounces@ietf.org [mailto:pim-bounces@ietf.org] On Behalf Of
Venugopal Hemige
Sent: 09 July 2004 19:45
To: pim@ietf.org
Subject: [pim] Hello HoldTime and Assert questions

> I have noticed a couple of issues with the spec and need some
> clarification:
> 
> 1. Hello HoldTime:
> 
> In section 4.3.2, neighbor.timeout is defined to be Hello_HoldTime
> whenever it is present in the received hello, or
> Default_Hello_Holdtime if the Hello message does not contain the
> Holdtime option.
> 
> In section 4.10.2 (last para of this section), it says that
> "Holdtime option MUST be implemented".
> 
> It is a bit confusing to interpret from this what the receiving
> router should do. Section 4.10.2 leads me to believe that the
> receiving router should not form an adjacency if the option is not
> present. Section 4.3.2 says the opposite. What is the expected
> behavior here?

My interpretation of this is that if a received Hello message contains the
Holdtime option, the receiving router MUST recognize and use the Holdtime
from that option, as described in section 4.3.2.  However, I don't think the
router should be prevented from forming an adjacency just because the Hello
message it receives doesn't contain the Holdtime option.

> 2. Assert cancel received on RPF-interface.
> 
> If there were an assert situation on the RPF-interface, the
> interface will be in assert-loser state. Could-Assert would be
> FALSE on the RPF-interface. So our interface metric to the source
> will be infinite-metric. If an assert cancel is received from
> the assert-winner, per the current definition of
> inferior/preferred/acceptable metrics, it will be treated as an
> acceptable metric. So the RPF-interface would remain in
> assert-loser state and retain the wrong upstream neighbor as
> RPF-neighbor, while infact it should have transitioned to
> assert-no-info.
> 
> I think "inferior metric" should be defined to as a metric lower
> than my metric OR infinite-metric. That should take care of it.
> Comments?

I agree with you that there is a problem here.  In addition, the definition
of Preferred and Acceptable metrics would need to exclude any infinite
metrics.

> Regards,
> -Venu

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


From pim-bounces@ietf.org  Fri Oct 15 05:25:09 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA08738
	for <pim-archive@lists.ietf.org>; Fri, 15 Oct 2004 05:25:09 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CIOFS-0005n2-Ma; Fri, 15 Oct 2004 05:19:42 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CIODV-0005Tb-Nw
	for pim@megatron.ietf.org; Fri, 15 Oct 2004 05:17:41 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA08272
	for <pim@ietf.org>; Fri, 15 Oct 2004 05:17:38 -0400 (EDT)
Received: from iramx2.ira.uni-karlsruhe.de ([141.3.10.81])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CIOOq-0001jP-0W
	for pim@ietf.org; Fri, 15 Oct 2004 05:29:24 -0400
Received: from iraspam.ira.uni-karlsruhe.de ([141.3.10.6]
	helo=spamhost.ira.uka.de)
	by iramx2.ira.uni-karlsruhe.de with esmtp (Exim 3.30 #10)
	id 1CIODR-00075b-00; Fri, 15 Oct 2004 11:17:37 +0200
Received: from amavis by spamhost.ira.uka.de with scanned-ok (Exim 3.30 #3)
	id 1CIODQ-0007NC-00; Fri, 15 Oct 2004 11:17:36 +0200
Received: from irams1.ira.uni-karlsruhe.de ([141.3.10.5]
	helo=irams1.ira.uka.de)
	by spamhost.ira.uka.de with esmtp (Exim 3.30 #3)
	id 1CIODN-0007N6-00; Fri, 15 Oct 2004 11:17:33 +0200
Received: from i72ms1.tm.uni-karlsruhe.de
	([141.3.70.16] helo=smtp.ipv6.tm.uni-karlsruhe.de ident=8)
	by irams1.ira.uka.de with esmtp (Exim 3.30 #7 )
	id 1CIODN-0000LQ-00; Fri, 15 Oct 2004 11:17:33 +0200
Received: from borg.ipv6.tm.uni-karlsruhe.de
	([2001:638:204:6:202:b3ff:feab:632e])
	by smtp.ipv6.tm.uni-karlsruhe.de with esmtp (TLSv1:DES-CBC3-SHA:168)
	(Exim 4.12) id 1CIODM-0007y3-00; Fri, 15 Oct 2004 11:17:32 +0200
Received: from localhost ([127.0.0.1])
	by borg.ipv6.tm.uni-karlsruhe.de with esmtp (Exim 4.30)
	id 1CIODN-0002v4-JY; Fri, 15 Oct 2004 11:17:33 +0200
Message-ID: <416F95AD.2080704@tm.uka.de>
Date: Fri, 15 Oct 2004 11:17:33 +0200
From: Mark Doll <doll@tm.uka.de>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
	rv:1.7) Gecko/20040803 Thunderbird/0.7.3 Mnenhy/0.6.0.104
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: James Lingard <James.Lingard@dataconnection.com>
Subject: Re: [pim] PIM-SM: timer value computation for join suppression
References: <53F74F5A7B94D511841C00B0D0AB16F8035811EA@baker.datcon.co.uk>
In-Reply-To: <53F74F5A7B94D511841C00B0D0AB16F8035811EA@baker.datcon.co.uk>
X-Enigmail-Version: 0.85.0.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
Content-Transfer-Encoding: 7bit
Cc: "'pim@ietf.org'" <pim@ietf.org>
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=subscribe>
Sender: pim-bounces@ietf.org
Errors-To: pim-bounces@ietf.org
Content-Transfer-Encoding: 7bit

Hi James,

thanks for your answer!

James Lingard wrote:
> This is not true, because the upstream router can never decrease its Expiry
> Timer as a result of receiving a Join message.  [...]

Yes, I've missed that cruical point at that time. So this was never a 
problem. What remains is the join message implosion problem, as you've 
pointed out. But I think that my proposal

>>So why not specifying something like:
>>
>>           Reset the Join Timer to the minimum of t_suppressed and
>>           HoldTime/3.5*rand(1.1,1.4), where HoldTime is the HoldTime
>>           from the Join/Prune message triggering this event.

amended by (since the upstream neighbor never decreases it's Exiry Timer 
due to a join message)

              If the Join Timer is set to expire in more
              than t_joinsuppress seconds, leave it unchanged.

is more appropriate than your proposal

> I agree that this looks like a problem.  I think better definitions of
> t_suppressed and t_joinsuppress would be something like:
> 
>   t_suppressed = t_periodic when Suppression_Enabled(I) is true, 0 otherwise
>   t_joinsuppress = rand(1.0 * min(t_periodic, Holdtime), 1.4 *
> min(t_periodic, Holdtime)) 
> 
> so that the randomization takes place in every case.

I think, t_joinsuppress must not be greater than Holdtime from the 
message, as it is the case with your proposal. Otherwise we risk losing 
join state at our upstream neighbor, because we might send our join 
message too late.

- Mark.

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


From pim-bounces@ietf.org  Mon Oct 18 03:31:18 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA23267
	for <pim-archive@lists.ietf.org>; Mon, 18 Oct 2004 03:31:18 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CJRxC-0004di-8q; Mon, 18 Oct 2004 03:29:14 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CJRwB-0004XD-T3
	for pim@megatron.ietf.org; Mon, 18 Oct 2004 03:28:12 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA22965
	for <pim@ietf.org>; Mon, 18 Oct 2004 03:28:10 -0400 (EDT)
Received: from web26007.mail.ukl.yahoo.com ([217.12.10.218])
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CJS7w-0001uH-TE
	for pim@ietf.org; Mon, 18 Oct 2004 03:40:32 -0400
Message-ID: <20041018072728.26259.qmail@web26007.mail.ukl.yahoo.com>
Received: from [62.8.24.95] by web26007.mail.ukl.yahoo.com via HTTP;
	Mon, 18 Oct 2004 09:27:28 CEST
Date: Mon, 18 Oct 2004 09:27:28 +0200 (CEST)
From: Bousquet Laurent <bousquet_l2000@yahoo.fr>
To: pim@ietf.org
MIME-Version: 1.0
X-Spam-Score: 3.1 (+++)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Subject: [pim] Both source and receiver in PIM-SM
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0672185479=="
Sender: pim-bounces@ietf.org
Errors-To: pim-bounces@ietf.org

--===============0672185479==
Content-Type: multipart/alternative; boundary="0-131390013-1098084448=:25702"

--0-131390013-1098084448=:25702
Content-Type: text/plain; charset=iso-8859-1
X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id DAA22965
Content-Transfer-Encoding: quoted-printable

Hello all,
=20
I am new to PIM and I need some help.
=20
I need a protocol in which the hosts will be both source and receiver for=
 the same Xcast group(interaction between the different hosts like in a c=
onference - application Many-to-Many). I think BIDIR-PIM is the best solu=
tion but I wonder if PIM-SM is possible : can a host be both a source and=
 a receiver for the same Xcast group in PIM-SM ?
=20
I am not sure but I think it can work like this. Each host (host A, host =
B and host C) which wants to participate in the conference will send Join=
 Messages with IGMP : so, the three hosts belong to the same shared tree.=
 When the host A wants to speak, it creates a source-specific tree toward=
s the RP which distributes the packets to the others participants (the ho=
st B and the host C). After, when the host B wants to speak, it also crea=
tes a source-specific tree toward the RP which distributes the packets to=
 the hosts A and C. In a nutshell, each host creates its own source-speci=
fic tree but uses the same shared tree.
=20
Please, could anybody clarify this ?
=20
Best regards,
L. Bousquet


	=09
---------------------------------
Cr=E9ez gratuitement votre Yahoo! Mail avec 100 Mo de stockage !
Cr=E9ez votre Yahoo! Mail

Le nouveau Yahoo! Messenger est arriv=E9 ! D=E9couvrez toutes les nouveau=
t=E9s pour dialoguer instantan=E9ment avec vos amis.T=E9l=E9chargez GRATU=
ITEMENT ici !
--0-131390013-1098084448=:25702
Content-Type: text/html; charset=iso-8859-1
X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id DAA22965
Content-Transfer-Encoding: quoted-printable

<DIV>
<DIV>Hello all,</DIV>
<DIV>&nbsp;</DIV>
<DIV>I am new to PIM and I need some help.</DIV>
<DIV>&nbsp;</DIV>
<DIV>I need a protocol in which the hosts will be both source and receive=
r for the same Xcast group(interaction between the different hosts like i=
n a conference - application Many-to-Many). I think BIDIR-PIM is the best=
 solution but I&nbsp;wonder if PIM-SM&nbsp;is possible :&nbsp;can a host =
be both a source and a receiver for the same Xcast group in PIM-SM ?</DIV=
>
<DIV>&nbsp;</DIV>
<DIV>I am not sure but I think it can work like this.&nbsp;Each host (hos=
t A, host B and host C) which wants to participate&nbsp;in the conference=
 will send Join Messages with IGMP : so, the three hosts belong to the sa=
me&nbsp;shared tree. When the&nbsp;host A wants to speak, it creates a so=
urce-specific tree towards the RP which distributes the packets to the ot=
hers participants (the host B and the host C). After, when the host B wan=
ts to speak,&nbsp;it also creates a source-specific tree toward the RP wh=
ich distributes the packets to the hosts A and C. In a nutshell, each hos=
t creates its own source-specific tree but uses the same shared tree.</DI=
V>
<DIV>&nbsp;</DIV>
<DIV>Please, could anybody clarify this ?</DIV>
<DIV>&nbsp;</DIV>
<DIV>Best regards,</DIV>
<DIV>L. Bousquet</DIV></DIV><p>
		<hr size=3D1>
Cr=E9ez gratuitement votre Yahoo! Mail avec <font color=3D"red"><b>100 Mo=
 de stockage !</b></font>
<br><a href=3D"http://fr.rd.yahoo.com/mail/taglines/*http://fr.rd.yahoo.c=
om/evt=3D25917/*http://fr.rd.yahoo.com/mail/mail_taglines_100/default/*ht=
tp://fr.benefits.yahoo.com/">Cr=E9ez votre Yahoo! Mail</a><br><br>
<font color=3D"red"><b>Le nouveau Yahoo! Messenger est arriv=E9 !</b></fo=
nt> D=E9couvrez toutes les nouveaut=E9s pour dialoguer instantan=E9ment a=
vec vos amis.
<a href=3D"http://fr.rd.yahoo.com/mail/taglines/*http://fr.rd.yahoo.com/e=
vt=3D26111/*http://fr.rd.yahoo.com/messenger/mail_taglines/default/*http:=
//fr.messenger.yahoo.com">T=E9l=E9chargez GRATUITEMENT ici !</a>
--0-131390013-1098084448=:25702--


--===============0672185479==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--===============0672185479==--



From pim-bounces@ietf.org  Mon Oct 18 04:18:20 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA26485
	for <pim-archive@lists.ietf.org>; Mon, 18 Oct 2004 04:18:20 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CJSfy-0000TB-2O; Mon, 18 Oct 2004 04:15:30 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CJScH-0008QZ-E4
	for pim@megatron.ietf.org; Mon, 18 Oct 2004 04:11:41 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA26035
	for <pim@ietf.org>; Mon, 18 Oct 2004 04:11:39 -0400 (EDT)
Received: from mta0.huawei.com ([61.144.161.41] helo=huawei.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CJSo9-0002ml-Fd
	for pim@ietf.org; Mon, 18 Oct 2004 04:24:02 -0400
Received: from huawei8tthy486 (mta1.huawei.com [172.17.1.60])
	by mta1.huawei.com
	(iPlanet Messaging Server 5.2 HotFix 1.16 (built May 14 2003))
	with ESMTPA id <0I5R00KD9S20V8@mta1.huawei.com> for pim@ietf.org; Mon,
	18 Oct 2004 15:42:01 +0800 (CST)
Date: Mon, 18 Oct 2004 15:53:05 +0800
From: Prashant Jhingran <prashantj@huawei.com>
Subject: RE: [pim] Both source and receiver in PIM-SM
In-reply-to: <20041018072728.26259.qmail@web26007.mail.ukl.yahoo.com>
To: "'Bousquet Laurent'" <bousquet_l2000@yahoo.fr>, pim@ietf.org
Message-id: <000a01c4b4e7$80719930$30226e0a@huawei8tthy486>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Mailer: Microsoft Outlook, Build 10.0.3416
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
X-imss-version: 2.7
X-imss-result: Passed
X-imss-approveListMatch: *@huawei.com
X-Spam-Score: 0.8 (/)
X-Scan-Signature: 7e439b86d3292ef5adf93b694a43a576
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1299903954=="
Sender: pim-bounces@ietf.org
Errors-To: pim-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1299903954==
Content-type: multipart/alternative;
	boundary="Boundary_(ID_CcEO/TjvVRVMUTXPI3P+6w)"

This is a multi-part message in MIME format.

--Boundary_(ID_CcEO/TjvVRVMUTXPI3P+6w)
Content-type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

Hi,
    Yes you are on the right path.
     PIM-SM itself can be used and your thinking is correct.
    According to the PIM-SM protocol, a sender (sourse) may or maynot be
a receiver.
    For creating receivers you need to run IGMP between hosts and the
first hop router's to the hosts.
regards,
Prashant
-----Original Message-----
From: pim-bounces@ietf.org [mailto:pim-bounces@ietf.org] On Behalf Of
Bousquet Laurent
Sent: Monday, October 18, 2004 3:27 PM
To: pim@ietf.org
Subject: [pim] Both source and receiver in PIM-SM


Hello all,
=20
I am new to PIM and I need some help.
=20
I need a protocol in which the hosts will be both source and receiver
for the same Xcast group(interaction between the different hosts like in
a conference - application Many-to-Many). I think BIDIR-PIM is the best
solution but I wonder if PIM-SM is possible : can a host be both a
source and a receiver for the same Xcast group in PIM-SM ?
=20
I am not sure but I think it can work like this. Each host (host A, host
B and host C) which wants to participate in the conference will send
Join Messages with IGMP : so, the three hosts belong to the same shared
tree. When the host A wants to speak, it creates a source-specific tree
towards the RP which distributes the packets to the others participants
(the host B and the host C). After, when the host B wants to speak, it
also creates a source-specific tree toward the RP which distributes the
packets to the hosts A and C. In a nutshell, each host creates its own
source-specific tree but uses the same shared tree.
=20
Please, could anybody clarify this ?
=20
Best regards,
L. Bousquet


  _____ =20

Cr=E9ez gratuitement votre Yahoo! Mail avec 100 Mo de stockage !=20
Cr=E9ez
<http://fr.rd.yahoo.com/mail/taglines/*http://fr.rd.yahoo.com/evt=3D25917=
/
*http://fr.rd.yahoo.com/mail/mail_taglines_100/default/*http://fr.benefi
ts.yahoo.com/> votre Yahoo! Mail

Le nouveau Yahoo! Messenger est arriv=E9 ! D=E9couvrez toutes les =
nouveaut=E9s
pour dialoguer instantan=E9ment avec vos amis. T=E9l=E9chargez
<http://fr.rd.yahoo.com/mail/taglines/*http://fr.rd.yahoo.com/evt=3D26111=
/
*http://fr.rd.yahoo.com/messenger/mail_taglines/default/*http://fr.messe
nger.yahoo.com> GRATUITEMENT ici !

--Boundary_(ID_CcEO/TjvVRVMUTXPI3P+6w)
Content-type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<TITLE>Message</TITLE>

<META content=3D"MSHTML 6.00.2800.1106" name=3DGENERATOR></HEAD>
<BODY>
<DIV>
<DIV><SPAN class=3D718194707-18102004><FONT color=3D#0000ff=20
size=3D2>Hi,</FONT></SPAN></DIV>
<DIV><SPAN class=3D718194707-18102004><FONT color=3D#0000ff=20
size=3D2>&nbsp;&nbsp;&nbsp; Yes you are on the right =
path.</FONT></SPAN></DIV>
<DIV><SPAN class=3D718194707-18102004><FONT color=3D#0000ff=20
size=3D2>&nbsp;&nbsp;&nbsp;&nbsp; PIM-SM itself can be used and your =
thinking is=20
correct.</FONT></SPAN></DIV>
<DIV><SPAN class=3D718194707-18102004><FONT color=3D#0000ff=20
size=3D2>&nbsp;&nbsp;&nbsp; According to the PIM-SM protocol, a sender =
(sourse)=20
may or maynot be a receiver.</FONT></SPAN></DIV>
<DIV><SPAN class=3D718194707-18102004><FONT color=3D#0000ff=20
size=3D2>&nbsp;&nbsp;&nbsp; For creating receivers you need to run IGMP =
between=20
hosts and the first hop router's to the hosts.</FONT></SPAN></DIV>
<DIV><SPAN class=3D718194707-18102004><FONT color=3D#0000ff=20
size=3D2>regards,</FONT></SPAN></DIV>
<DIV><SPAN class=3D718194707-18102004><FONT color=3D#0000ff=20
size=3D2>Prashant</FONT></SPAN></DIV></DIV>
<DIV></DIV>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft><FONT face=3DTahoma=20
size=3D2>-----Original Message-----<BR><B>From:</B> pim-bounces@ietf.org =

[mailto:pim-bounces@ietf.org] <B>On Behalf Of </B>Bousquet=20
Laurent<BR><B>Sent:</B> Monday, October 18, 2004 3:27 PM<BR><B>To:</B>=20
pim@ietf.org<BR><B>Subject:</B> [pim] Both source and receiver in=20
PIM-SM<BR><BR></FONT></DIV>
<DIV>
<DIV>Hello all,</DIV>
<DIV>&nbsp;</DIV>
<DIV>I am new to PIM and I need some help.</DIV>
<DIV>&nbsp;</DIV>
<DIV>I need a protocol in which the hosts will be both source and =
receiver for=20
the same Xcast group(interaction between the different hosts like in a=20
conference - application Many-to-Many). I think BIDIR-PIM is the best =
solution=20
but I&nbsp;wonder if PIM-SM&nbsp;is possible :&nbsp;can a host be both a =
source=20
and a receiver for the same Xcast group in PIM-SM ?</DIV>
<DIV>&nbsp;</DIV>
<DIV>I am not sure but I think it can work like this.&nbsp;Each host =
(host A,=20
host B and host C) which wants to participate&nbsp;in the conference =
will send=20
Join Messages with IGMP : so, the three hosts belong to the =
same&nbsp;shared=20
tree. When the&nbsp;host A wants to speak, it creates a source-specific =
tree=20
towards the RP which distributes the packets to the others participants =
(the=20
host B and the host C). After, when the host B wants to speak,&nbsp;it =
also=20
creates a source-specific tree toward the RP which distributes the =
packets to=20
the hosts A and C. In a nutshell, each host creates its own =
source-specific tree=20
but uses the same shared tree.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Please, could anybody clarify this ?</DIV>
<DIV>&nbsp;</DIV>
<DIV>Best regards,</DIV>
<DIV>L. Bousquet</DIV></DIV>
<P>
<HR SIZE=3D1>
Cr=E9ez gratuitement votre Yahoo! Mail avec <FONT color=3Dred><B>100 Mo =
de stockage=20
!</B></FONT> <BR><A=20
href=3D"http://fr.rd.yahoo.com/mail/taglines/*http://fr.rd.yahoo.com/evt=3D=
25917/*http://fr.rd.yahoo.com/mail/mail_taglines_100/default/*http://fr.b=
enefits.yahoo.com/">Cr=E9ez=20
votre Yahoo! Mail</A><BR><BR><FONT color=3Dred><B>Le nouveau Yahoo! =
Messenger est=20
arriv=E9 !</B></FONT> D=E9couvrez toutes les nouveaut=E9s pour dialoguer =

instantan=E9ment avec vos amis. <A=20
href=3D"http://fr.rd.yahoo.com/mail/taglines/*http://fr.rd.yahoo.com/evt=3D=
26111/*http://fr.rd.yahoo.com/messenger/mail_taglines/default/*http://fr.=
messenger.yahoo.com">T=E9l=E9chargez=20
GRATUITEMENT ici !</A></BODY></HTML>

--Boundary_(ID_CcEO/TjvVRVMUTXPI3P+6w)--


--===============1299903954==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--===============1299903954==--



From pim-bounces@ietf.org  Mon Oct 18 09:43:45 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA17073
	for <pim-archive@lists.ietf.org>; Mon, 18 Oct 2004 09:43:45 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CJXin-0001eF-CN; Mon, 18 Oct 2004 09:38:45 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CJXbi-00010G-Gc
	for pim@megatron.ietf.org; Mon, 18 Oct 2004 09:31:27 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA15744
	for <pim@ietf.org>; Mon, 18 Oct 2004 09:31:24 -0400 (EDT)
Received: from rproxy.gmail.com ([64.233.170.196] helo=mproxy.gmail.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CJXni-0000Cw-3I
	for pim@ietf.org; Mon, 18 Oct 2004 09:43:50 -0400
Received: by mproxy.gmail.com with SMTP id 79so187649rnl
	for <pim@ietf.org>; Mon, 18 Oct 2004 06:31:20 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references;
	b=AeVyjR2N8y+a30Ngursn0GBGGPsC4rmTj6QEAWSIvwU9fmgTaqbrvNNmY3pA39Y6ptAnXFJRdweeV+E4UD8WApToTb/xqSP5cRXCQv7H41XXC/3PQNLkvO3dDaQkFvH8SOLi5eUJPrwjRiccjv/da9psWhcdpCRODL0GyU5AfvY
Received: by 10.38.78.27 with SMTP id a27mr492193rnb;
	Mon, 18 Oct 2004 06:31:20 -0700 (PDT)
Received: by 10.38.66.53 with HTTP; Mon, 18 Oct 2004 06:31:19 -0700 (PDT)
Message-ID: <dcad22d804101806313e1c504d@mail.gmail.com>
Date: Mon, 18 Oct 2004 09:31:19 -0400
From: Marshall Eubanks <marshall.eubanks@gmail.com>
To: Bousquet Laurent <bousquet_l2000@yahoo.fr>
Subject: Re: [pim] Both source and receiver in PIM-SM
In-Reply-To: <20041018072728.26259.qmail@web26007.mail.ukl.yahoo.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
References: <20041018072728.26259.qmail@web26007.mail.ukl.yahoo.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 00e94c813bef7832af255170dca19e36
Content-Transfer-Encoding: quoted-printable
Cc: pim@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Marshall Eubanks <marshall.eubanks@gmail.com>
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=subscribe>
Sender: pim-bounces@ietf.org
Errors-To: pim-bounces@ietf.org
Content-Transfer-Encoding: quoted-printable

Dear Laurent;

Remember, hosts do not create trees - routers do that. Whether or not
source based trees
are created in ASM depends on the PIM routing cinfiguration in use in
the domain - generally, they
are, but they may not be. In any case, this will not generally be
controllable by the host. Standard
ASM configurations would have true source based trees (not from the
source to the RP but
from the source to the receivers) set up immediately, but this can be
modified if you can set routing  policy or if BiDir routing is
available.

It sounds to me like BiDir may be what you want IF you are not planning to=
=20
cross a domain boundary (i.e., if all of the multicasts are kept
within one autonomous system).
What you describe is very similar to BiDir in operation. If you do have to =
cross
domain boundaries and use MBGP, you cannot use BiDir, and you should
investigate using SSM.

Regards
Marshall Eubanks


On Mon, 18 Oct 2004 09:27:28 +0200 (CEST), Bousquet Laurent
<bousquet_l2000@yahoo.fr> wrote:
>=20
> =20
> Hello all,=20
>  =20
> I am new to PIM and I need some help.=20
>  =20
> I need a protocol in which the hosts will be both source and receiver for
> the same Xcast group(interaction between the different hosts like in a
> conference - application Many-to-Many). I think BIDIR-PIM is the best
> solution but I wonder if PIM-SM is possible : can a host be both a source
> and a receiver for the same Xcast group in PIM-SM ?=20
>  =20
> I am not sure but I think it can work like this. Each host (host A, host =
B
> and host C) which wants to participate in the conference will send Join
> Messages with IGMP : so, the three hosts belong to the same shared tree.
> When the host A wants to speak, it creates a source-specific tree towards
> the RP which distributes the packets to the others participants (the host=
 B
> and the host C). After, when the host B wants to speak, it also creates a
> source-specific tree toward the RP which distributes the packets to the
> hosts A and C. In a nutshell, each host creates its own source-specific t=
ree
> but uses the same shared tree.=20
>  =20
> Please, could anybody clarify this ?=20
>  =20
> Best regards,=20
> L. Bousquet
>=20
>  ________________________________
>  Cr=E9ez gratuitement votre Yahoo! Mail avec 100 Mo de stockage !=20
> Cr=E9ez votre Yahoo! Mail
>=20
>  Le nouveau Yahoo! Messenger est arriv=E9 ! D=E9couvrez toutes les nouvea=
ut=E9s
> pour dialoguer instantan=E9ment avec vos amis. T=E9l=E9chargez GRATUITEME=
NT ici !=20
>=20
>=20
> _______________________________________________
> pim mailing list
> pim@ietf.org
> https://www1.ietf.org/mailman/listinfo/pim
>=20
>=20
>

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


From pim-bounces@ietf.org  Mon Oct 18 15:17:17 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA14876
	for <pim-archive@lists.ietf.org>; Mon, 18 Oct 2004 15:17:17 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CJcWg-0007of-53; Mon, 18 Oct 2004 14:46:34 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CJcK1-00053D-6B
	for pim@megatron.ietf.org; Mon, 18 Oct 2004 14:33:29 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10349
	for <pim@ietf.org>; Mon, 18 Oct 2004 14:33:22 -0400 (EDT)
Received: from colo-dns-ext1.juniper.net ([207.17.137.57])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CJcVx-0006ai-Iw
	for pim@ietf.org; Mon, 18 Oct 2004 14:45:51 -0400
Received: from merlot.juniper.net (merlot.juniper.net [172.17.27.10])
	by colo-dns-ext1.juniper.net (8.11.3/8.9.3) with ESMTP id i9IIWo936358
	for <pim@ietf.org>; Mon, 18 Oct 2004 11:32:50 -0700 (PDT)
	(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 i9IIWje85048
	for <pim@ietf.org>; Mon, 18 Oct 2004 11:32:45 -0700 (PDT)
	(envelope-from pusateri@juniper.net)
Message-Id: <200410181832.i9IIWje85048@merlot.juniper.net>
To: pim@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <79753.1098124365.1@juniper.net>
Date: Mon, 18 Oct 2004 11:32:45 -0700
From: Tom Pusateri <pusateri@juniper.net>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2
Subject: [pim] WG Query: draft-farinacci-pim-pop-count-00.txt
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=subscribe>
Sender: pim-bounces@ietf.org
Errors-To: pim-bounces@ietf.org

Dino had asked at the last IETF meeting if we would accept
the following draft, draft-farinacci-pim-pop-count-00.txt as a PIM
working group document.

I never sent out the question to the mailing list and Mike reminded
me today.

Please read the draft if you haven't and send your thoughts to
the list by next Monday, Oct. 25th at 5:00 pm PST.

Justification for your opinion is preferred.

Thanks,
Tom

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


From pim-bounces@ietf.org  Mon Oct 18 16:23:01 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA19923
	for <pim-archive@lists.ietf.org>; Mon, 18 Oct 2004 16:23:01 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CJdck-0006r2-0I; Mon, 18 Oct 2004 15:56:54 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CJdPP-0003j6-1A
	for pim@megatron.ietf.org; Mon, 18 Oct 2004 15:43:07 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA17021
	for <pim@ietf.org>; Mon, 18 Oct 2004 15:43:00 -0400 (EDT)
Received: from possum.icir.org ([192.150.187.67])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CJdbM-00085M-6t
	for pim@ietf.org; Mon, 18 Oct 2004 15:55:29 -0400
Received: from possum.icir.org (localhost [127.0.0.1])
	by possum.icir.org (8.12.9p1/8.12.8) with ESMTP id i9IJgvwK085222;
	Mon, 18 Oct 2004 12:42:57 -0700 (PDT)
	(envelope-from pavlin@possum.icir.org)
Message-Id: <200410181942.i9IJgvwK085222@possum.icir.org>
To: Tom Pusateri <pusateri@juniper.net>
Subject: Re: [pim] WG Query: draft-farinacci-pim-pop-count-00.txt 
In-Reply-To: Message from Tom Pusateri <pusateri@juniper.net> of "Mon,
	18 Oct 2004 11:32:45 PDT."
	<200410181832.i9IIWje85048@merlot.juniper.net> 
Date: Mon, 18 Oct 2004 12:42:57 -0700
From: Pavlin Radoslavov <pavlin@icir.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Cc: pim@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=subscribe>
Sender: pim-bounces@ietf.org
Errors-To: pim-bounces@ietf.org

> Dino had asked at the last IETF meeting if we would accept
> the following draft, draft-farinacci-pim-pop-count-00.txt as a PIM
> working group document.
> 
> I never sent out the question to the mailing list and Mike reminded
> me today.
> 
> Please read the draft if you haven't and send your thoughts to
> the list by next Monday, Oct. 25th at 5:00 pm PST.
> 
> Justification for your opinion is preferred.

Few months ago I sent an email to the list with some comments about
the I-D, but so far I haven't seen any replies. Shall I resend them?

Pavlin

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


From pim-bounces@ietf.org  Mon Oct 18 17:43:17 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA26509
	for <pim-archive@lists.ietf.org>; Mon, 18 Oct 2004 17:43:16 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CJevf-000657-7s; Mon, 18 Oct 2004 17:20:31 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CJeTj-0000nP-QA
	for pim@megatron.ietf.org; Mon, 18 Oct 2004 16:51:39 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA22131
	for <pim@ietf.org>; Mon, 18 Oct 2004 16:51:32 -0400 (EDT)
Received: from sj-iport-2-in.cisco.com ([171.71.176.71]
	helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CJefh-0001G8-Bg for pim@ietf.org; Mon, 18 Oct 2004 17:04:02 -0400
Received: from sj-core-1.cisco.com (171.71.177.237)
	by sj-iport-2.cisco.com with ESMTP; 18 Oct 2004 13:58:23 -0700
Received: from dino-lnx.cisco.com (dino-lnx.cisco.com [171.71.54.55])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id i9IKoxk2019125;
	Mon, 18 Oct 2004 13:50:59 -0700 (PDT)
Received: (from dino@localhost)
	by dino-lnx.cisco.com (8.11.6/8.11.6) id i9IKoxk20422;
	Mon, 18 Oct 2004 13:50:59 -0700
Date: Mon, 18 Oct 2004 13:50:59 -0700
Message-Id: <200410182050.i9IKoxk20422@dino-lnx.cisco.com>
From: Dino Farinacci <dino@cisco.com>
To: pavlin@icir.org
In-reply-to: <200410181942.i9IJgvwK085222@possum.icir.org> (message from
	Pavlin Radoslavov on Mon, 18 Oct 2004 12:42:57 -0700)
Subject: Re: [pim] WG Query: draft-farinacci-pim-pop-count-00.txt
References: <200410181942.i9IJgvwK085222@possum.icir.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aefe408d50e9c7c47615841cb314bed
Cc: pusateri@juniper.net, pim@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=subscribe>
Sender: pim-bounces@ietf.org
Errors-To: pim-bounces@ietf.org

>> Few months ago I sent an email to the list with some comments about
>> the I-D, but so far I haven't seen any replies. Shall I resend them?

    I probably missed them since I was in corporate transition. Can you please
    resend them. Thanks. I had no idea.

Dino

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


From pim-bounces@ietf.org  Mon Oct 18 17:50:15 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA27195
	for <pim-archive@lists.ietf.org>; Mon, 18 Oct 2004 17:50:15 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CJewF-0006F9-NX; Mon, 18 Oct 2004 17:21:07 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CJecN-0002Lm-Nb
	for pim@megatron.ietf.org; Mon, 18 Oct 2004 17:00:36 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA22903
	for <pim@ietf.org>; Mon, 18 Oct 2004 17:00:28 -0400 (EDT)
Received: from possum.icir.org ([192.150.187.67])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CJeoJ-0001Qp-0E
	for pim@ietf.org; Mon, 18 Oct 2004 17:12:58 -0400
Received: from possum.icir.org (localhost [127.0.0.1])
	by possum.icir.org (8.12.9p1/8.12.8) with ESMTP id i9IL0HwK085783;
	Mon, 18 Oct 2004 14:00:17 -0700 (PDT)
	(envelope-from pavlin@possum.icir.org)
Message-Id: <200410182100.i9IL0HwK085783@possum.icir.org>
To: Dino Farinacci <dino@cisco.com>
Subject: Re: [pim] WG Query: draft-farinacci-pim-pop-count-00.txt 
In-Reply-To: Message from Dino Farinacci <dino@cisco.com> of "Mon,
	18 Oct 2004 13:50:59 PDT."
	<200410182050.i9IKoxk20422@dino-lnx.cisco.com> 
Date: Mon, 18 Oct 2004 14:00:17 -0700
From: Pavlin Radoslavov <pavlin@icir.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5a9a1bd6c2d06a21d748b7d0070ddcb8
Cc: pavlin@icir.org, pusateri@juniper.net, pim@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=subscribe>
Sender: pim-bounces@ietf.org
Errors-To: pim-bounces@ietf.org

> >> Few months ago I sent an email to the list with some comments about
> >> the I-D, but so far I haven't seen any replies. Shall I resend them?
> 
>     I probably missed them since I was in corporate transition. Can you please
>     resend them. Thanks. I had no idea.

Original comments from July 26 2004 included below.

Thanks,
Pavlin

====================
At the very high level I think it is a very good idea of having a
mechanism for multicast tree accounting, etc.

Implementation/design-wise I have few comments:

 * Have you looked into related work such as the following paper:
   "Tracetree: A Scalable Mechanism to Discover Multicast Tree
   Topologies in the Internet" by Kamil Sarac and Kevin Almeroth:
   http://www.nmsl.cs.ucsb.edu/publications.html
   It has a number of interesting ideas including a mechanism to
   deal with incremental deployment, it is not protocol-specific,
   etc.

 * We need to deal with incremental deployment, otherwise there is
   no initiative to even start deploying this new scheme. E.g.,
   ideas from the above paper can be helpful in this aspect.

 * In your proposal you overload the Join messages with accounting
   information.
   The advantage of doing that is that you save some network
   bandwidth and processing cycles, but the result solution becomes
   a bit too complicated and lacks flexibility. For example, if
   someone wants to define a new counter, adding such counter to the
   fixed  message format is impossible without redefining the whole
   format again.
   I would rather see those two functionalities separated:
   the tree management (i.e., the Join/Prune messages), and the
   tree accounting. By that I mean using a new type control message
   (for accounting purpose only) which is designed to have
   extensible format, etc. Then, each counter for example, can be
   added as an option to the message.

 * Currently, it appears that the mechanism is PIM-SM
   specific. Rather than redefining the mechanism for PIM-DM, etc,
   I'd prefer to have a protocol-independent mechanism.
   After all, it appears that the only major thing that currently
   ties the mechanism to PIM-SM is the message format overloading of
   the PIM-SM Join messages.

 * Some of the fields are probably not large enough. E.g.,
   max. value of 255 for "Node Count" is one that comes to mind.
   Another example is the link speed where everything below 1Mbps
   becomes 0. If we are to consider the last-mile multicast, then we
   need better granularity.
====================

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


From pim-bounces@ietf.org  Thu Oct 21 08:17:19 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA13491
	for <pim-archive@lists.ietf.org>; Thu, 21 Oct 2004 08:17:18 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CKavy-0003ZO-Bl; Thu, 21 Oct 2004 07:16:42 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CKOl7-0002RB-Cf
	for pim@megatron.ietf.org; Wed, 20 Oct 2004 18:16:41 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA04650
	for <pim@ietf.org>; Wed, 20 Oct 2004 18:16:33 -0400 (EDT)
Received: from syd-iport-1.cisco.com ([64.104.193.196])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CKOxV-0007kV-My
	for pim@ietf.org; Wed, 20 Oct 2004 18:29:31 -0400
Received: from syd-core-1.cisco.com (64.104.193.198)
	by syd-iport-1.cisco.com with ESMTP; 21 Oct 2004 08:31:59 +1000
X-BrightmailFiltered: true
Received: from mira-sjc5-b.cisco.com (IDENT:mirapoint@mira-sjc5-b.cisco.com
	[171.71.163.14])
	by syd-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id i9KMFlv7026228; 
	Thu, 21 Oct 2004 08:15:48 +1000 (EST)
Received: from irp-view6.cisco.com (irp-view6.cisco.com [171.70.65.143])
	by mira-sjc5-b.cisco.com (MOS 3.4.5-GR) with ESMTP id AYG10469;
	Wed, 20 Oct 2004 15:16:55 -0700 (PDT)
Date: Wed, 20 Oct 2004 15:15:55 -0700 (PDT)
From: Mike McBride <mmcbride@cisco.com>
To: Yakov Rekhter <yakov@juniper.net>
Subject: Re: [pim] draft-wijnands-pim-proxy 
In-Reply-To: <200410131500.i9DF0Ce57868@merlot.juniper.net>
Message-ID: <Pine.GSO.4.58.0410201446160.3173@irp-view6.cisco.com>
References: <200410131500.i9DF0Ce57868@merlot.juniper.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
Cc: pim@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=subscribe>
Sender: pim-bounces@ietf.org
Errors-To: pim-bounces@ietf.org

It doesn't appear we've reached consensus on the acceptance of this draft
within the PIM WG. There are a majority of individuals, however, who have
expressed support for the adoption of the draft. But majority doesn't
rule here. We need better WG agreement if we are going to proceed.

If the authors of this draft were to remove references to traffic
engineering, would those who have voiced opposition, then be supportive of
adopting this draft within the PIM WG? Would the authors of the draft be
open to removing TE?

Let's try to get this resolved before D.C.

thanks,
mike

On Wed, 13 Oct 2004, Yakov Rekhter wrote:

> Folks,
>
> So far the discussion about draft-wijnands-pim-proxy seems to be
> focused on one particular problem that this draft is intended to solve
> - BGP-free core or Internet routes free core.
>
> However, I'd like to point out that the solution proposed in
> draft-wijnands-pim-proxy is *not* limited to that particular problem,
> but is also claimed to support traffic engineering with PIM (see
> section 2.4.2 of the draft).
>
> I think that prior to extending PIM with traffic engineering
> capabilities, the authors of draft-wijnands-pim-proxy need to answer
> the question whether adding vector stack to PIM would be adequate
> to match the requirements for p2mp traffic engineering.
>
> Yakov.
>
> _______________________________________________
> 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-bounces@ietf.org  Thu Oct 21 08:48:27 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA19836
	for <pim-archive@lists.ietf.org>; Thu, 21 Oct 2004 08:48:27 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CKbNR-0004bJ-W1; Thu, 21 Oct 2004 07:45:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CKXPq-0004vZ-3K
	for pim@megatron.ietf.org; Thu, 21 Oct 2004 03:31:18 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA17311
	for <pim@ietf.org>; Thu, 21 Oct 2004 03:31:11 -0400 (EDT)
Received: from odd-brew.cisco.com ([144.254.15.119]
	helo=strange-brew.cisco.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CKXcJ-0008KA-IM
	for pim@ietf.org; Thu, 21 Oct 2004 03:44:12 -0400
Received: from cisco.com (ams-stealth-iwijnand-2.cisco.com [10.61.255.122])
	by strange-brew.cisco.com (8.11.7p1+Sun/8.8.8) with ESMTP id
	i9L7Ub119474; Thu, 21 Oct 2004 09:30:37 +0200 (CEST)
Message-ID: <4177657B.5000406@cisco.com>
Date: Thu, 21 Oct 2004 09:30:03 +0200
From: IJsbrand Wijnands <ice@cisco.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
	rv:1.6b) Gecko/20031205 Thunderbird/0.4
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Mike McBride <mmcbride@cisco.com>
Subject: Re: [pim] draft-wijnands-pim-proxy
References: <200410131500.i9DF0Ce57868@merlot.juniper.net>
	<Pine.GSO.4.58.0410201446160.3173@irp-view6.cisco.com>
In-Reply-To: <Pine.GSO.4.58.0410201446160.3173@irp-view6.cisco.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
Content-Transfer-Encoding: 7bit
Cc: pim@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=subscribe>
Sender: pim-bounces@ietf.org
Errors-To: pim-bounces@ietf.org
Content-Transfer-Encoding: 7bit

Mike, Yakov,

> It doesn't appear we've reached consensus on the acceptance of this draft
> within the PIM WG. There are a majority of individuals, however, who have
> expressed support for the adoption of the draft. But majority doesn't
> rule here. We need better WG agreement if we are going to proceed.
> 
> If the authors of this draft were to remove references to traffic
> engineering, would those who have voiced opposition, then be supportive of
> adopting this draft within the PIM WG? Would the authors of the draft be
> open to removing TE?

Maybe the reference to Traffic Engineering in section 2.4.2 is a bit to 
optimistic. I've no problem removing that. What about if we name it 'explicit 
routed path' using a stack with multiple vectors.

Thx,

Ice.

> Let's try to get this resolved before D.C.
> 
> thanks,
> mike
> 
> On Wed, 13 Oct 2004, Yakov Rekhter wrote:
> 
> 
>>Folks,
>>
>>So far the discussion about draft-wijnands-pim-proxy seems to be
>>focused on one particular problem that this draft is intended to solve
>>- BGP-free core or Internet routes free core.
>>
>>However, I'd like to point out that the solution proposed in
>>draft-wijnands-pim-proxy is *not* limited to that particular problem,
>>but is also claimed to support traffic engineering with PIM (see
>>section 2.4.2 of the draft).
>>
>>I think that prior to extending PIM with traffic engineering
>>capabilities, the authors of draft-wijnands-pim-proxy need to answer
>>the question whether adding vector stack to PIM would be adequate
>>to match the requirements for p2mp traffic engineering.

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


From pim-bounces@ietf.org  Thu Oct 21 10:32:24 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06269
	for <pim-archive@lists.ietf.org>; Thu, 21 Oct 2004 10:32:24 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CKdqz-0001tP-T9; Thu, 21 Oct 2004 10:23:45 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CKdjG-00052W-7e
	for pim@megatron.ietf.org; Thu, 21 Oct 2004 10:15:47 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA03595
	for <pim@ietf.org>; Thu, 21 Oct 2004 10:15:43 -0400 (EDT)
Received: from perseverance-96.encs.concordia.ca
	([132.205.96.94] helo=perseverance.encs.concordia.ca ident=root)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CKdvs-00042P-ED
	for pim@ietf.org; Thu, 21 Oct 2004 10:28:49 -0400
Received: from cse.concordia.ca (root@fir.cs.concordia.ca [132.205.45.147])
	by perseverance.encs.concordia.ca (8.12.11/8.12.11) with ESMTP id
	i9LEFh8D025126 for <pim@ietf.org>; Thu, 21 Oct 2004 10:15:43 -0400
Message-ID: <4177C48F.6090906@cse.concordia.ca>
Date: Thu, 21 Oct 2004 10:15:43 -0400
From: JW Atwood <bill@cse.concordia.ca>
Organization: Concordia University, Department of Computer Science and Software
	Engineering
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: pim@ietf.org
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.43 on perseverance.encs.concordia.ca at 2004/10/21
	10:15:43 EDT
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69
Content-Transfer-Encoding: 7bit
Subject: [pim] WG Query: draft-atwood-pim-sm-linklocal-00.txt
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=subscribe>
Sender: pim-bounces@ietf.org
Errors-To: pim-bounces@ietf.org
Content-Transfer-Encoding: 7bit

An Internet-Draft titled "Security Issues in PIM-SM Link-local Messages"
has been posted to the Internet-Drafts directory.  We believe that the
issues discussed in this draft are pertinent to the current
Internet-Draft for PIM-SM, and to the PIM-SM Working Group.  The PIM-SM
draft has acquired a significant amount of material on security issues,
but is hampered by prohibitions in RFC 2402.  Correct and meaningful use
of IPsec AH for PIM-SM link-local messages will have to be addressed
either within the current Internet-Draft, or as soon as the proposed
modifications to the Authentication Header (draft-ietf-ipsec-rfc2402bis)
are accepted by the IESG.

We therefore respectfully request that the draft be made a Working Group
document.

Bill Atwood
Salekul Islam

The abstract is as follows:

This document proposes some modifications to the Internet-Draft for
    Protocol Independent Multicast - Sparse Mode (PIM-SM) Protocol
    regarding security issues of its link-local messages. To protect
    these link-local messages, in the Internet-Draft for PIM-SM a
    security mechanism has been proposed that uses the IPsec
    Authentication Header (AH) protocol. While using IPsec AH protocol,
    the anti-replay mechanism has been disabled. This compromise makes
    PIM-SM vulnerable to Denial of Service (DoS) attack. In this
    document, a new proposal is presented to protect PIM link-local
    messages while activating the anti-replay mechanism as well. This
    proposal builds on the new Security Association lookup method that
    has been specified in the Internet-Draft that revises the AH
    protocol.


-- 

Dr. J.W. Atwood, Eng., Professor  tel:   +1 (514) 848-2424 x3046
Department of Computer Science    fax:   +1 (514) 848-2830
   and Software Engineering
Concordia University LB927-9      email: bill@cse.Concordia.ca
1455 de Maisonneuve Blvd. West    http: //www.cse.Concordia.ca/~bill
Montreal, Quebec Canada H3G 1M8




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


From pim-bounces@ietf.org  Thu Oct 21 12:43:15 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA21444
	for <pim-archive@lists.ietf.org>; Thu, 21 Oct 2004 12:43:15 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CKfla-0000d9-1A; Thu, 21 Oct 2004 12:26:18 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CKfgG-0006cZ-M2
	for pim@megatron.ietf.org; Thu, 21 Oct 2004 12:20:48 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA19182
	for <pim@ietf.org>; Thu, 21 Oct 2004 12:20:45 -0400 (EDT)
Received: from rproxy.gmail.com ([64.233.170.192])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CKfss-0007HR-06
	for pim@ietf.org; Thu, 21 Oct 2004 12:33:53 -0400
Received: by rproxy.gmail.com with SMTP id 79so52352rnl
	for <pim@ietf.org>; Thu, 21 Oct 2004 09:20:44 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references;
	b=foqmeHw9Fj0hWdACIO3+H/Kaeqe9wkV/jf8/X/GDZPxdIG/py/1NZkLhgkmudM+1WWc4Gpy9N4gcuyMOqf1bq/qNV7agSaMI4VsIGLhOI19QSZUxoyYRK7lo5ej+Aptf7YycYe3VqivIFN9NZ50HAjra41M3Y6ia3IkPsb3TFvY=
Received: by 10.38.14.9 with SMTP id 9mr2846927rnn;
	Thu, 21 Oct 2004 09:20:44 -0700 (PDT)
Received: by 10.38.66.53 with HTTP; Thu, 21 Oct 2004 09:20:44 -0700 (PDT)
Message-ID: <dcad22d8041021092019f877b4@mail.gmail.com>
Date: Thu, 21 Oct 2004 12:20:44 -0400
From: Marshall Eubanks <marshall.eubanks@gmail.com>
To: Pavlin Radoslavov <pavlin@icir.org>
Subject: Re: [pim] WG Query: draft-farinacci-pim-pop-count-00.txt
In-Reply-To: <200410182100.i9IL0HwK085783@possum.icir.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
References: <dino@cisco.com> <200410182050.i9IKoxk20422@dino-lnx.cisco.com>
	<200410182100.i9IL0HwK085783@possum.icir.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 34d35111647d654d033d58d318c0d21a
Content-Transfer-Encoding: 7bit
Cc: pim@ietf.org, pusateri@juniper.net
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Marshall Eubanks <marshall.eubanks@gmail.com>
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=subscribe>
Sender: pim-bounces@ietf.org
Errors-To: pim-bounces@ietf.org
Content-Transfer-Encoding: 7bit

Hello;

I would basically agree with Pavlin - should this really be a PIM-SM
overlay, or a separate
protocol describing accounting messages and use ?

And, of course, if its decided NOT to overlay the PIM join message,
shouldn't  this
be done by a separate WG, such as MAGMA ? So I would support moving this
forward, but maybe not in PIM.

A suggestion

- I did not see a mechanism to provide feedback if certain trees
downstream do NOT support the protocol.
There should be a flag propagated upstream, I think, to indicate that
"this tree has partial
information because routers below me do not support accounting."
This would be very useful I think in real world partial deployment
scenarios (and
in debugging deployments), and is only a bit.

Also, (a pet peeve) " it's Join/Prune messages" and "it's accounting"
should be "its".

Regards
Marshall Eubanks


On Mon, 18 Oct 2004 14:00:17 -0700, Pavlin Radoslavov <pavlin@icir.org> wrote:
> > >> Few months ago I sent an email to the list with some comments about
> > >> the I-D, but so far I haven't seen any replies. Shall I resend them?
> >
> >     I probably missed them since I was in corporate transition. Can you please
> >     resend them. Thanks. I had no idea.
> 
> Original comments from July 26 2004 included below.
> 
> Thanks,
> Pavlin
> 
> ====================
> At the very high level I think it is a very good idea of having a
> mechanism for multicast tree accounting, etc.
> 
> Implementation/design-wise I have few comments:
> 
>  * Have you looked into related work such as the following paper:
>    "Tracetree: A Scalable Mechanism to Discover Multicast Tree
>    Topologies in the Internet" by Kamil Sarac and Kevin Almeroth:
>    http://www.nmsl.cs.ucsb.edu/publications.html
>    It has a number of interesting ideas including a mechanism to
>    deal with incremental deployment, it is not protocol-specific,
>    etc.
> 
>  * We need to deal with incremental deployment, otherwise there is
>    no initiative to even start deploying this new scheme. E.g.,
>    ideas from the above paper can be helpful in this aspect.
> 
>  * In your proposal you overload the Join messages with accounting
>    information.
>    The advantage of doing that is that you save some network
>    bandwidth and processing cycles, but the result solution becomes
>    a bit too complicated and lacks flexibility. For example, if
>    someone wants to define a new counter, adding such counter to the
>    fixed  message format is impossible without redefining the whole
>    format again.
>    I would rather see those two functionalities separated:
>    the tree management (i.e., the Join/Prune messages), and the
>    tree accounting. By that I mean using a new type control message
>    (for accounting purpose only) which is designed to have
>    extensible format, etc. Then, each counter for example, can be
>    added as an option to the message.
> 
>  * Currently, it appears that the mechanism is PIM-SM
>    specific. Rather than redefining the mechanism for PIM-DM, etc,
>    I'd prefer to have a protocol-independent mechanism.
>    After all, it appears that the only major thing that currently
>    ties the mechanism to PIM-SM is the message format overloading of
>    the PIM-SM Join messages.
> 
>  * Some of the fields are probably not large enough. E.g.,
>    max. value of 255 for "Node Count" is one that comes to mind.
>    Another example is the link speed where everything below 1Mbps
>    becomes 0. If we are to consider the last-mile multicast, then we
>    need better granularity.
> ====================
> 
> 
> 
> _______________________________________________
> 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-bounces@ietf.org  Thu Oct 21 15:17:00 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA08670
	for <pim-archive@lists.ietf.org>; Thu, 21 Oct 2004 15:17:00 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CKiBN-0004Si-ED; Thu, 21 Oct 2004 15:01:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CKhsw-0007YO-Tx
	for pim@megatron.ietf.org; Thu, 21 Oct 2004 14:42:03 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA04526
	for <pim@ietf.org>; Thu, 21 Oct 2004 14:42:00 -0400 (EDT)
Received: from netcore.fi ([193.94.160.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CKi5b-0002xW-4j
	for pim@ietf.org; Thu, 21 Oct 2004 14:55:08 -0400
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id i9LIf3r24287;
	Thu, 21 Oct 2004 21:41:04 +0300
Date: Thu, 21 Oct 2004 21:41:03 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: JW Atwood <bill@cse.concordia.ca>
Subject: Re: [pim] WG Query: draft-atwood-pim-sm-linklocal-00.txt
In-Reply-To: <4177C48F.6090906@cse.concordia.ca>
Message-ID: <Pine.LNX.4.44.0410212127100.23743-100000@netcore.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002
Cc: greg.daley@eng.monash.edu.au, pim@ietf.org,
        gopakumar.kurup@eng.monash.edu.au
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=subscribe>
Sender: pim-bounces@ietf.org
Errors-To: pim-bounces@ietf.org

Hi,

(Cc:ing two people who are probably not on this particular list.)

On Thu, 21 Oct 2004, JW Atwood wrote:
> An Internet-Draft titled "Security Issues in PIM-SM Link-local Messages"
> has been posted to the Internet-Drafts directory.  We believe that the
> issues discussed in this draft are pertinent to the current
> Internet-Draft for PIM-SM, and to the PIM-SM Working Group.  The PIM-SM
> draft has acquired a significant amount of material on security issues,
> but is hampered by prohibitions in RFC 2402.  Correct and meaningful use
> of IPsec AH for PIM-SM link-local messages will have to be addressed
> either within the current Internet-Draft, or as soon as the proposed
> modifications to the Authentication Header (draft-ietf-ipsec-rfc2402bis)
> are accepted by the IESG.

This looks interesting, and I'll have a look at this.

I'll, observe, however, that this is just one (technical solution) 
piece in the larger puzzle of securing multicast-related protocols 
when you're on the same link as a router.

The interdomain security analysis has been done in
draft-ietf-mboned-mroutesec-04.txt [the document is approved and
practically in the RFC-editor's queue now].  That points out that
we'll need to figure out the threats in the local link, in other
words, relating to MLD/IGMP and PIM (solvable e.g. with
IPsec-protecting the messages).

There has been IMHO excellent start on analyzing the threats with 
MLD/IGMP in draft-daley-magma-smld-prob-00.txt (which I hope will go 
forward), and now I think the critical question is:

 Should the on-link threats to PIM-SM be analyzed and discussed in the 
 same document as the on-link threats to MLD/IGMP?

 And regardless of that, what would be the correct place for such 
 analysis document(s)?  MBONED?  MAGMA?  PIM?  Invidiual submission?
 (If both are in the same document, I guess that would argue for 
 MBONED.)

-- 
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings





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


From pim-bounces@ietf.org  Thu Oct 21 16:10:37 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA15249
	for <pim-archive@lists.ietf.org>; Thu, 21 Oct 2004 16:10:37 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CKiu2-00013m-24; Thu, 21 Oct 2004 15:47:14 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CKigX-0006Yu-CO
	for pim@megatron.ietf.org; Thu, 21 Oct 2004 15:33:17 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA10840
	for <pim@ietf.org>; Thu, 21 Oct 2004 15:33:15 -0400 (EDT)
Received: from colo-dns-ext1.juniper.net ([207.17.137.57])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CKitC-0004II-EB
	for pim@ietf.org; Thu, 21 Oct 2004 15:46:23 -0400
Received: from merlot.juniper.net (merlot.juniper.net [172.17.27.10])
	by colo-dns-ext1.juniper.net (8.11.3/8.9.3) with ESMTP id i9LJWi968603; 
	Thu, 21 Oct 2004 12:32:44 -0700 (PDT)
	(envelope-from yakov@juniper.net)
Received: from juniper.net (sapphire.juniper.net [172.17.28.108])
	by merlot.juniper.net (8.11.3/8.11.3) with ESMTP id i9LJWde79359;
	Thu, 21 Oct 2004 12:32:39 -0700 (PDT)
	(envelope-from yakov@juniper.net)
Message-Id: <200410211932.i9LJWde79359@merlot.juniper.net>
To: IJsbrand Wijnands <ice@cisco.com>
Subject: Re: [pim] draft-wijnands-pim-proxy 
In-Reply-To: Your message of "Thu, 21 Oct 2004 09:30:03 +0200."
	<4177657B.5000406@cisco.com> 
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <46361.1098387159.1@juniper.net>
Date: Thu, 21 Oct 2004 12:32:39 -0700
From: Yakov Rekhter <yakov@juniper.net>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465
Cc: Mike McBride <mmcbride@cisco.com>, pim@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=subscribe>
Sender: pim-bounces@ietf.org
Errors-To: pim-bounces@ietf.org

Ice,

> Mike, Yakov,
> 
> > It doesn't appear we've reached consensus on the acceptance of this draft
> > within the PIM WG. There are a majority of individuals, however, who have
> > expressed support for the adoption of the draft. But majority doesn't
> > rule here. We need better WG agreement if we are going to proceed.
> > 
> > If the authors of this draft were to remove references to traffic
> > engineering, would those who have voiced opposition, then be supportive of
> > adopting this draft within the PIM WG? Would the authors of the draft be
> > open to removing TE?
> 
> Maybe the reference to Traffic Engineering in section 2.4.2 is a bit to 
> optimistic. I've no problem removing that. What about if we name it 'explicit
> routed path' using a stack with multiple vectors.

If the stack of vectors is not intended for traffic engineering,
then what are the applications for the stack of vectors ?

Yakov.

> Thx,
> 
> Ice.
> 
> > Let's try to get this resolved before D.C.
> > 
> > thanks,
> > mike
> > 
> > On Wed, 13 Oct 2004, Yakov Rekhter wrote:
> > 
> > 
> >>Folks,
> >>
> >>So far the discussion about draft-wijnands-pim-proxy seems to be
> >>focused on one particular problem that this draft is intended to solve
> >>- BGP-free core or Internet routes free core.
> >>
> >>However, I'd like to point out that the solution proposed in
> >>draft-wijnands-pim-proxy is *not* limited to that particular problem,
> >>but is also claimed to support traffic engineering with PIM (see
> >>section 2.4.2 of the draft).
> >>
> >>I think that prior to extending PIM with traffic engineering
> >>capabilities, the authors of draft-wijnands-pim-proxy need to answer
> >>the question whether adding vector stack to PIM would be adequate
> >>to match the requirements for p2mp traffic engineering.

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


From pim-bounces@ietf.org  Thu Oct 21 21:10:54 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA19896
	for <pim-archive@lists.ietf.org>; Thu, 21 Oct 2004 21:10:54 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CKlJ3-0000zO-Nm; Thu, 21 Oct 2004 18:21:13 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CKjlp-0001cB-3P
	for pim@megatron.ietf.org; Thu, 21 Oct 2004 16:42:50 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA22499
	for <pim@ietf.org>; Thu, 21 Oct 2004 16:42:46 -0400 (EDT)
Received: from sj-iport-2-in.cisco.com ([171.71.176.71]
	helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CKjyU-0007fC-NP for pim@ietf.org; Thu, 21 Oct 2004 16:55:56 -0400
Received: from sj-core-5.cisco.com (171.71.177.238)
	by sj-iport-2.cisco.com with ESMTP; 21 Oct 2004 13:50:14 -0700
Received: from cisco.com (cypher.cisco.com [171.69.11.142])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id i9LKgD6s025694;
	Thu, 21 Oct 2004 13:42:13 -0700 (PDT)
Received: (from eckert@localhost)
	by cisco.com (8.8.8-Cisco List Logging/8.8.8) id NAA19176;
	Thu, 21 Oct 2004 13:42:14 -0700 (PDT)
Date: Thu, 21 Oct 2004 13:42:14 -0700
From: Toerless Eckert <eckert@cisco.com>
To: Yakov Rekhter <yakov@juniper.net>
Subject: Re: [pim] draft-wijnands-pim-proxy
Message-ID: <20041021204213.GW3254@cisco.com>
References: <4177657B.5000406@cisco.com>
	<200410211932.i9LJWde79359@merlot.juniper.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200410211932.i9LJWde79359@merlot.juniper.net>
User-Agent: Mutt/1.4i
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c
Cc: Mike McBride <mmcbride@cisco.com>, pim@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=subscribe>
Sender: pim-bounces@ietf.org
Errors-To: pim-bounces@ietf.org

On Thu, Oct 21, 2004 at 12:32:39PM -0700, Yakov Rekhter wrote:
> Ice,
> 
> > Mike, Yakov,
> > 
> > > It doesn't appear we've reached consensus on the acceptance of this draft
> > > within the PIM WG. There are a majority of individuals, however, who have
> > > expressed support for the adoption of the draft. But majority doesn't
> > > rule here. We need better WG agreement if we are going to proceed.
> > > 
> > > If the authors of this draft were to remove references to traffic
> > > engineering, would those who have voiced opposition, then be supportive of
> > > adopting this draft within the PIM WG? Would the authors of the draft be
> > > open to removing TE?
> > 
> > Maybe the reference to Traffic Engineering in section 2.4.2 is a bit to 
> > optimistic. I've no problem removing that. What about if we name it 'explicit
> > routed path' using a stack with multiple vectors.
> 
> If the stack of vectors is not intended for traffic engineering,
> then what are the applications for the stack of vectors ?

Let's try to understand what is in dispute here. Traffic Engineering
is a highly overloaded word that can imply functions like fast reroute, 
bandwidth reservation or explicit path selection and where people seem
to have fery fixed expectations about the framework on how or whether
this is delivered.

The RPF-vector-stack allows only to influence path selection in a form
which has also been common even in the most basic IP (or SNA ?) architectures
via loose and strict source routes. 

The RPF-vector transports this idea into the path selection of the control
plane message. Whether or not you want to consider this to be part of
some future traffic engineering architecture or not is a matter of
interpretation and future profile of applicability specification and
not really something the draft needs to cover. I think for this reason
others proposed to remove references to the word traffic engineering
and any implications of how this path selection might fit any type of
future traffic engineering solutions or not.

The RPF-vector-stack can be called a loose source-route mechanism in
the draft, which can be used for example to better control the SPF selection
during re-convergence, to have ASBR path selection or the like, and of
course also the potential for explicit path selection for P router paths.
It's really kinda like the loose source route in IP, only that because it
is in the control plane, it does not suffer from the IP loose source routes
HW dependencies but causes the selection per flow of course (not per packet).

Cheers
	Toerless

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


From pim-bounces@ietf.org  Sun Oct 24 15:10:13 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA22863
	for <pim-archive@lists.ietf.org>; Sun, 24 Oct 2004 15:10:13 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CLniN-0000Ja-7c; Sun, 24 Oct 2004 15:07:39 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CLniB-00006D-Vg
	for pim@megatron.ietf.org; Sun, 24 Oct 2004 15:07:28 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA22527
	for <pim@ietf.org>; Sun, 24 Oct 2004 15:07:26 -0400 (EDT)
Received: from colo-dns-ext2.juniper.net ([207.17.137.64])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CLnvU-0003JX-Bg
	for pim@ietf.org; Sun, 24 Oct 2004 15:21:12 -0400
Received: from merlot.juniper.net (merlot.juniper.net [172.17.27.10])
	by colo-dns-ext2.juniper.net (8.12.3/8.12.3) with ESMTP id
	i9OJ6uBm062541; Sun, 24 Oct 2004 12:06:56 -0700 (PDT)
	(envelope-from yakov@juniper.net)
Received: from juniper.net (sapphire.juniper.net [172.17.28.108])
	by merlot.juniper.net (8.11.3/8.11.3) with ESMTP id i9OJ6ue30426;
	Sun, 24 Oct 2004 12:06:56 -0700 (PDT)
	(envelope-from yakov@juniper.net)
Message-Id: <200410241906.i9OJ6ue30426@merlot.juniper.net>
To: Toerless Eckert <eckert@cisco.com>
Subject: Re: [pim] draft-wijnands-pim-proxy 
In-Reply-To: Your message of "Thu, 21 Oct 2004 13:42:14 PDT."
	<20041021204213.GW3254@cisco.com> 
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <90362.1098644816.1@juniper.net>
Date: Sun, 24 Oct 2004 12:06:56 -0700
From: Yakov Rekhter <yakov@juniper.net>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c0bedb65cce30976f0bf60a0a39edea4
Cc: Mike McBride <mmcbride@cisco.com>, pim@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=subscribe>
Sender: pim-bounces@ietf.org
Errors-To: pim-bounces@ietf.org

Toerless,

> > > 
> > > > It doesn't appear we've reached consensus on the acceptance of this dra
ft
> > > > within the PIM WG. There are a majority of individuals, however, who ha
ve
> > > > expressed support for the adoption of the draft. But majority doesn't
> > > > rule here. We need better WG agreement if we are going to proceed.
> > > > 
> > > > If the authors of this draft were to remove references to traffic
> > > > engineering, would those who have voiced opposition, then be supportive
 of
> > > > adopting this draft within the PIM WG? Would the authors of the draft b
e
> > > > open to removing TE?
> > > 
> > > Maybe the reference to Traffic Engineering in section 2.4.2 is a bit to 
> > > optimistic. I've no problem removing that. What about if we name it 'expl
icit
> > > routed path' using a stack with multiple vectors.
> > 
> > If the stack of vectors is not intended for traffic engineering,
> > then what are the applications for the stack of vectors ?
> 
> Let's try to understand what is in dispute here. Traffic Engineering
> is a highly overloaded word that can imply functions like fast reroute, 
> bandwidth reservation or explicit path selection and where people seem
> to have fery fixed expectations about the framework on how or whether
> this is delivered.
> 
> The RPF-vector-stack allows only to influence path selection in a form
> which has also been common even in the most basic IP (or SNA ?) architectures
> via loose and strict source routes. 
> 
> The RPF-vector transports this idea into the path selection of the control
> plane message. Whether or not you want to consider this to be part of
> some future traffic engineering architecture or not is a matter of
> interpretation and future profile of applicability specification and
> not really something the draft needs to cover. I think for this reason
> others proposed to remove references to the word traffic engineering
> and any implications of how this path selection might fit any type of
> future traffic engineering solutions or not.

Adding a new mechanism to a protocol for the sake of some nebulous
"future traffic engineering architecture" is clearly broken. First
you need to finalize this future traffic engineering architecture,
and *then* add the appropriate mechanism(s) to the protocol.

> The RPF-vector-stack can be called a loose source-route mechanism in
> the draft, which can be used for example to better control the SPF selection
> during re-convergence, to have ASBR path selection or the like, and of
> course also the potential for explicit path selection for P router paths.
> It's really kinda like the loose source route in IP, only that because it
> is in the control plane, it does not suffer from the IP loose source routes
> HW dependencies but causes the selection per flow of course (not per packet).

All this looks like a plenty of hand-waiving, and little/no specifics
on how the RPF-vector-stack is intended to be used. As I said before,
if there are any specific problem(s) that you think would require
the use the RPF-vector-stack, then document how the
RPF-vector-stack would be used to solve these problems, and whether
such solutions would meet the requirements.
 
Cheers

Yakov.

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


From pim-bounces@ietf.org  Sun Oct 24 17:33:34 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA01806
	for <pim-archive@lists.ietf.org>; Sun, 24 Oct 2004 17:33:33 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CLpxh-0004Oj-Im; Sun, 24 Oct 2004 17:31:37 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CLpxW-0004MD-L1
	for pim@megatron.ietf.org; Sun, 24 Oct 2004 17:31:26 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA01745
	for <pim@ietf.org>; Sun, 24 Oct 2004 17:31:24 -0400 (EDT)
Received: from sj-iport-1-in.cisco.com ([171.71.176.70]
	helo=sj-iport-1.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CLqAq-0005ow-CN for pim@ietf.org; Sun, 24 Oct 2004 17:45:12 -0400
Received: from sj-core-1.cisco.com (171.71.177.237)
	by sj-iport-1.cisco.com with ESMTP; 24 Oct 2004 14:41:50 -0700
X-BrightmailFiltered: true
Received: from cisco.com (cypher.cisco.com [171.69.11.142])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id i9OLUqk2024316;
	Sun, 24 Oct 2004 14:30:52 -0700 (PDT)
Received: (from eckert@localhost)
	by cisco.com (8.8.8-Cisco List Logging/8.8.8) id OAA07424;
	Sun, 24 Oct 2004 14:30:52 -0700 (PDT)
Date: Sun, 24 Oct 2004 14:30:52 -0700
From: Toerless Eckert <eckert@cisco.com>
To: Yakov Rekhter <yakov@juniper.net>
Subject: Re: [pim] draft-wijnands-pim-proxy
Message-ID: <20041024213052.GP3254@cisco.com>
References: <20041021204213.GW3254@cisco.com>
	<200410241906.i9OJ6ue30426@merlot.juniper.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200410241906.i9OJ6ue30426@merlot.juniper.net>
User-Agent: Mutt/1.4i
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b4a0a5f5992e2a4954405484e7717d8c
Cc: Mike McBride <mmcbride@cisco.com>, pim@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=subscribe>
Sender: pim-bounces@ietf.org
Errors-To: pim-bounces@ietf.org

On Sun, Oct 24, 2004 at 12:06:56PM -0700, Yakov Rekhter wrote:
> > Let's try to understand what is in dispute here. Traffic Engineering
> > is a highly overloaded word that can imply functions like fast reroute, 
> > bandwidth reservation or explicit path selection and where people seem
> > to have fery fixed expectations about the framework on how or whether
> > this is delivered.
> > 
> > The RPF-vector-stack allows only to influence path selection in a form
> > which has also been common even in the most basic IP (or SNA ?)
> > architectures via loose and strict source routes. 
> > 
> > The RPF-vector transports this idea into the path selection of the control
> > plane message. Whether or not you want to consider this to be part of
> > some future traffic engineering architecture or not is a matter of
> > interpretation and future profile of applicability specification and
> > not really something the draft needs to cover. I think for this reason
> > others proposed to remove references to the word traffic engineering
> > and any implications of how this path selection might fit any type of
> > future traffic engineering solutions or not.
> 
> Adding a new mechanism to a protocol for the sake of some nebulous
> "future traffic engineering architecture" is clearly broken. First
> you need to finalize this future traffic engineering architecture,
> and *then* add the appropriate mechanism(s) to the protocol.

You choose to ignore what i ways saying. I said that "Traffic Engineering"
may be a nebulous term, but there is no need to rathole a very specific and
well defined functionality by asking for a whole universe to be built
around it in before. Explicit path selection via a hop-by-hop specification is
an easily understood clear functionality and can be taken advantage of without
necessarily having defined what "Traffic Engineering" means.

> > The RPF-vector-stack can be called a loose source-route mechanism in
> > the draft, which can be used for example to better control the SPF selection
> > during re-convergence, to have ASBR path selection or the like, and of
> > course also the potential for explicit path selection for P router paths.
> > It's really kinda like the loose source route in IP, only that because it
> > is in the control plane, it does not suffer from the IP loose source routes
> > HW dependencies but causes the selection per flow of course (not per packet).
> All this looks like a plenty of hand-waiving,

I am not familiar with that expression. Did you not understand the
explanations that i tried to provide in the paragraph or are you trying to
avoid a start of a technical discussion by dismissing it with fancy terms ?

> and little/no specifics on how the RPF-vector-stack is intended to be used.

True. I was assuming that the possible applications are pretty obvious
to you as an author of USP#6,078,590. Are you telling me you can not
think of how it is to be used and i need to explain that to you ?

> As I said before,
> if there are any specific problem(s) that you think would require
> the use the RPF-vector-stack, then document how the  RPF-vector-stack
> would be used to solve these problems, and whether such solutions would
> meet the requirements.

I am not quite sure what you are asking here:
First of all, i do not speak for the authors of the draft, i am
just relaying my personal opinions here. Are you asking the authors to
encumber a protocol specification submission with the inclusion of
additional requirements or solution architecture text in the actual
protocol spec document ?

Cheers
	Toerless

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


From pim-bounces@ietf.org  Mon Oct 25 12:56:57 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA13649
	for <pim-archive@lists.ietf.org>; Mon, 25 Oct 2004 12:56:57 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CM87T-0003X2-QI; Mon, 25 Oct 2004 12:54:55 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CM7rH-0007Aj-Oz
	for pim@megatron.ietf.org; Mon, 25 Oct 2004 12:38:11 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA12421
	for <pim@ietf.org>; Mon, 25 Oct 2004 12:38:08 -0400 (EDT)
Received: from sj-iport-4.cisco.com ([171.68.10.86])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CM84l-0002SC-25
	for pim@ietf.org; Mon, 25 Oct 2004 12:52:07 -0400
Received: from sj-core-4.cisco.com (171.68.223.138)
	by sj-iport-4.cisco.com with ESMTP; 25 Oct 2004 09:39:01 -0700
X-BrightmailFiltered: true
Received: from [128.107.163.136] (dhcp-128-107-163-136.cisco.com
	[128.107.163.136])
	by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id i9PGbaHn010950;
	Mon, 25 Oct 2004 09:37:37 -0700 (PDT)
Message-ID: <417D2BD0.3040404@cisco.com>
Date: Mon, 25 Oct 2004 09:37:36 -0700
From: Tony Speakman <speakman@cisco.com>
User-Agent: Mozilla Thunderbird 0.8 (Macintosh/20040913)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Marshall Eubanks <marshall.eubanks@gmail.com>
Subject: Re: [pim] WG Query: draft-farinacci-pim-pop-count-00.txt
References: <dino@cisco.com>
	<200410182050.i9IKoxk20422@dino-lnx.cisco.com>	<200410182100.i9IL0HwK085783@possum.icir.org>
	<dcad22d8041021092019f877b4@mail.gmail.com>
In-Reply-To: <dcad22d8041021092019f877b4@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5ebbf074524e58e662bc8209a6235027
Content-Transfer-Encoding: 7bit
Cc: Pavlin Radoslavov <pavlin@icir.org>, pusateri@juniper.net, pim@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=subscribe>
Sender: pim-bounces@ietf.org
Errors-To: pim-bounces@ietf.org
Content-Transfer-Encoding: 7bit


> I would basically agree with Pavlin - should this really be a PIM-SM
> overlay, or a separate
> protocol describing accounting messages and use ?
> 
> And, of course, if its decided NOT to overlay the PIM join message,
> shouldn't  this
> be done by a separate WG, such as MAGMA ? So I would support moving this
> forward, but maybe not in PIM.

RMT did some related work which was a lot of fun, but
is currently inactive:

http://www.ietf.org/proceedings/01aug/I-D/draft-ietf-rmt-gra-arch-02.txt
http://www.ietf.org/proceedings/01aug/I-D/draft-ietf-rmt-gra-fspec-00.txt
http://www.ietf.org/proceedings/03jul/I-D/draft-ietf-rmt-bb-gra-signalling-01.txt

Tony S


> 
> A suggestion
> 
> - I did not see a mechanism to provide feedback if certain trees
> downstream do NOT support the protocol.
> There should be a flag propagated upstream, I think, to indicate that
> "this tree has partial
> information because routers below me do not support accounting."
> This would be very useful I think in real world partial deployment
> scenarios (and
> in debugging deployments), and is only a bit.
> 
> Also, (a pet peeve) " it's Join/Prune messages" and "it's accounting"
> should be "its".
> 
> Regards
> Marshall Eubanks
> 
> 
> On Mon, 18 Oct 2004 14:00:17 -0700, Pavlin Radoslavov <pavlin@icir.org> wrote:
> 
>>>>>Few months ago I sent an email to the list with some comments about
>>>>>the I-D, but so far I haven't seen any replies. Shall I resend them?
>>>
>>>    I probably missed them since I was in corporate transition. Can you please
>>>    resend them. Thanks. I had no idea.
>>
>>Original comments from July 26 2004 included below.
>>
>>Thanks,
>>Pavlin
>>
>>====================
>>At the very high level I think it is a very good idea of having a
>>mechanism for multicast tree accounting, etc.
>>
>>Implementation/design-wise I have few comments:
>>
>> * Have you looked into related work such as the following paper:
>>   "Tracetree: A Scalable Mechanism to Discover Multicast Tree
>>   Topologies in the Internet" by Kamil Sarac and Kevin Almeroth:
>>   http://www.nmsl.cs.ucsb.edu/publications.html
>>   It has a number of interesting ideas including a mechanism to
>>   deal with incremental deployment, it is not protocol-specific,
>>   etc.
>>
>> * We need to deal with incremental deployment, otherwise there is
>>   no initiative to even start deploying this new scheme. E.g.,
>>   ideas from the above paper can be helpful in this aspect.
>>
>> * In your proposal you overload the Join messages with accounting
>>   information.
>>   The advantage of doing that is that you save some network
>>   bandwidth and processing cycles, but the result solution becomes
>>   a bit too complicated and lacks flexibility. For example, if
>>   someone wants to define a new counter, adding such counter to the
>>   fixed  message format is impossible without redefining the whole
>>   format again.
>>   I would rather see those two functionalities separated:
>>   the tree management (i.e., the Join/Prune messages), and the
>>   tree accounting. By that I mean using a new type control message
>>   (for accounting purpose only) which is designed to have
>>   extensible format, etc. Then, each counter for example, can be
>>   added as an option to the message.
>>
>> * Currently, it appears that the mechanism is PIM-SM
>>   specific. Rather than redefining the mechanism for PIM-DM, etc,
>>   I'd prefer to have a protocol-independent mechanism.
>>   After all, it appears that the only major thing that currently
>>   ties the mechanism to PIM-SM is the message format overloading of
>>   the PIM-SM Join messages.
>>
>> * Some of the fields are probably not large enough. E.g.,
>>   max. value of 255 for "Node Count" is one that comes to mind.
>>   Another example is the link speed where everything below 1Mbps
>>   becomes 0. If we are to consider the last-mile multicast, then we
>>   need better granularity.
>>====================
>>
>>
>>
>>_______________________________________________
>>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
> 

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


From pim-bounces@ietf.org  Tue Oct 26 18:11:01 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA06679
	for <pim-archive@lists.ietf.org>; Tue, 26 Oct 2004 18:11:01 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CMYnb-0007jE-00; Tue, 26 Oct 2004 17:24:11 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CMXm9-0007Tx-Gg
	for pim@megatron.ietf.org; Tue, 26 Oct 2004 16:18:37 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11797
	for <pim@ietf.org>; Tue, 26 Oct 2004 16:18:35 -0400 (EDT)
Received: from sj-iport-2-in.cisco.com ([171.71.176.71]
	helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CMXzs-0004UT-EU for pim@ietf.org; Tue, 26 Oct 2004 16:32:48 -0400
Received: from sj-core-5.cisco.com (171.71.177.238)
	by sj-iport-2.cisco.com with ESMTP; 26 Oct 2004 13:27:02 -0700
Received: from mira-sjc5-b.cisco.com (IDENT:mirapoint@mira-sjc5-b.cisco.com
	[171.71.163.14])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id i9QKI46s015849
	for <pim@ietf.org>; Tue, 26 Oct 2004 13:18:04 -0700 (PDT)
Received: from irp-view7.cisco.com (irp-view7.cisco.com [171.70.65.144])
	by mira-sjc5-b.cisco.com (MOS 3.4.5-GR) with ESMTP id AYK27334;
	Tue, 26 Oct 2004 13:19:56 -0700 (PDT)
Date: Tue, 26 Oct 2004 13:17:59 -0700 (PDT)
From: Mike McBride <mmcbride@cisco.com>
To: pim@ietf.org
Subject: [pim] PIM WG Agenda for IETF 61
Message-ID: <Pine.GSO.4.58.0410261259100.3349@irp-view7.cisco.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=subscribe>
Sender: pim-bounces@ietf.org
Errors-To: pim-bounces@ietf.org

Please let us know if there are other drafts we need to discuss during the
meeting. We are currently scheduled for Tuesday, Nov. 9th, 1545-1645,
although they are trying to find us a slot with more time.

Brief pim wg drafts status         Mike
Standards req's and Charter        Tom
draft-ietf-pim-sm-bsr-04           Stig
draft-ietf-pim-mib-v2-02           Bharat
draft-wijnands-pim-proxy-00        Arjen
draft-farinacci-pim-pop-count-00   Mike
draft-atwood-pim-sm-linklocal-00   Mike

thanks,
mike

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


From pim-bounces@ietf.org  Wed Oct 27 09:40:56 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA03806
	for <pim-archive@lists.ietf.org>; Wed, 27 Oct 2004 09:40:56 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CMnym-0005zg-RU; Wed, 27 Oct 2004 09:36:44 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CMnwB-0003jm-9U
	for pim@megatron.ietf.org; Wed, 27 Oct 2004 09:34:03 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA03541
	for <pim@ietf.org>; Wed, 27 Oct 2004 09:34:01 -0400 (EDT)
Received: from colo-dns-ext1.juniper.net ([207.17.137.57])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CMoA1-0005Kg-W9
	for pim@ietf.org; Wed, 27 Oct 2004 09:48:23 -0400
Received: from merlot.juniper.net (merlot.juniper.net [172.17.27.10])
	by colo-dns-ext1.juniper.net (8.11.3/8.9.3) with ESMTP id i9RDXR928902; 
	Wed, 27 Oct 2004 06:33:27 -0700 (PDT)
	(envelope-from yakov@juniper.net)
Received: from juniper.net (sapphire.juniper.net [172.17.28.108])
	by merlot.juniper.net (8.11.3/8.11.3) with ESMTP id i9RDXMe88204;
	Wed, 27 Oct 2004 06:33:22 -0700 (PDT)
	(envelope-from yakov@juniper.net)
Message-Id: <200410271333.i9RDXMe88204@merlot.juniper.net>
To: Toerless Eckert <eckert@cisco.com>
Subject: Re: [pim] draft-wijnands-pim-proxy 
In-Reply-To: Your message of "Sun, 24 Oct 2004 14:30:52 PDT."
	<20041024213052.GP3254@cisco.com> 
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <74305.1098884001.1@juniper.net>
Date: Wed, 27 Oct 2004 06:33:22 -0700
From: Yakov Rekhter <yakov@juniper.net>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Cc: Mike McBride <mmcbride@cisco.com>, pim@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=subscribe>
Sender: pim-bounces@ietf.org
Errors-To: pim-bounces@ietf.org

Toerless,

> > > The RPF-vector-stack can be called a loose source-route mechanism in
> > > the draft, which can be used for example to better control the SPF select
ion
> > > during re-convergence, to have ASBR path selection or the like, and of
> > > course also the potential for explicit path selection for P router paths.
> > > It's really kinda like the loose source route in IP, only that because it
> > > is in the control plane, it does not suffer from the IP loose source rout
es
> > > HW dependencies but causes the selection per flow of course (not per pack
et).
> > All this looks like a plenty of hand-waiving,
> 
> I am not familiar with that expression. Did you not understand the
> explanations that i tried to provide in the paragraph or are you trying to
> avoid a start of a technical discussion by dismissing it with fancy terms ?
> 
> > and little/no specifics on how the RPF-vector-stack is intended to be used.
> 
> True. I was assuming that the possible applications are pretty obvious
> to you as an author of USP#6,078,590. Are you telling me you can not
> think of how it is to be used and i need to explain that to you ?

If you would read the patent, you would realize that this patent 
does *not* use the RPF-vector-stack, but just a single address. 

Yakov.

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


From pim-bounces@ietf.org  Wed Oct 27 10:49:31 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA10683
	for <pim-archive@lists.ietf.org>; Wed, 27 Oct 2004 10:49:31 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CMoyG-0008FL-HG; Wed, 27 Oct 2004 10:40:16 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CMotG-0005mc-9R
	for pim@megatron.ietf.org; Wed, 27 Oct 2004 10:35:06 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA08833
	for <pim@ietf.org>; Wed, 27 Oct 2004 10:35:03 -0400 (EDT)
Received: from catarina.usc.edu ([204.57.0.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CMp78-0006TI-DK
	for pim@ietf.org; Wed, 27 Oct 2004 10:49:27 -0400
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 i9REYSoh079558
	for <pim@catarina.usc.edu>; Wed, 27 Oct 2004 07:34:33 -0700 (PDT)
	(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 i9REYOLP021489
	for <pim@catarina.usc.edu>; Wed, 27 Oct 2004 16:34:25 +0200
Received: (from venaas@localhost)
	by sverresborg.uninett.no (8.12.8/8.12.8/Submit) id i9REYNAt032625
	for pim@catarina.usc.edu; Wed, 27 Oct 2004 16:34:23 +0200
X-Authentication-Warning: sverresborg.uninett.no: venaas set sender to
	Stig.Venaas@uninett.no using -f
Date: Wed, 27 Oct 2004 16:34:23 +0200
From: Stig Venaas <Stig.Venaas@uninett.no>
To: pim@catarina.usc.edu
Message-ID: <20041027143423.GA32349@sverresborg.uninett.no>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="vkogqOf2sHV7VnPd"
Content-Disposition: inline
User-Agent: Mutt/1.4.1i
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7a0494a0224ca59418dd8f92694c1fdb
Subject: [pim] The BSR spec and maintaining group-to-RP mappings
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=subscribe>
Sender: pim-bounces@ietf.org
Errors-To: pim-bounces@ietf.org


--vkogqOf2sHV7VnPd
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

In the last update of the BSR spec, draft-ietf-pim-sm-bsr-04, we changed
the way group-to-RP mappings are maintained.

In the draft update we propose ONLY using the hold-time to expire the RP
mappings. Each time a new BSM is received the timers are reset.  A hold-
time of 0 means immediate removal. If a BSM is received which does not
contain a previously learnt RP-mapping, routers will still *wait* for
the mapping's holdtime to expire before removing it. We call this
approach "Explicit withdrawal" (EW) because the BSR has to explicitly
include RPs to be deleted with a holdtime of 0.

Another approach, is that in addition to using holdtime for RP
maintenance, an RP is *also* removed when a BSM not containing the RP is
received. We call this the "Implicit withdrawal" (IW) approach. IW
because not including an RP, implicitly implies that it is to be removed.

We think the old PIM RFC and the previous BSR drafts both are ambiguous
but lean towards the IW approach. However, there are implementations of
both approaches.

We would like to resolve this in the latest specification to pick the
approach that works better and also see if we can find a transition
strategy for implementations to go from one to the other. Or for mixed
networks until they are upgraded eventually to a common approach.

Stig

--vkogqOf2sHV7VnPd
Content-Type: text/plain; charset=us-ascii
Content-Disposition: attachment; filename="bsr-writeup.txt"

                Maintaining BSR group-to-RP mappings

1. Introduction

   We're trying to compare two ways of doing this.  One way is using
   ONLY the holdtime to expire the RP mappings. Each time a new BSM
   is received the timers are reset.  A holdtime of 0 means immediate
   removal. If a BSM is received which does not contain a previously
   learnt RP-mapping, routers will still *wait* for the mapping's
   holdtime to expire before removing it. We call this approach
   "Explicit withdrawal" (EW below) because the BSR has to explicitly
   include RPs to be deleted with a holdtime of 0.

   In the second approach, in addition to using holdtime for RP
   maintenance, an RP is *also* removed when a BSM not containing the
   RP is received. We call this the "Implicit withdrawal" (IW below)
   approach. IW because not including an RP implicitly implies that it
   is to be removed.

   The old PIM RFC and the existing specification both are ambiguous
   but lean towards the IW approach.  However, implementations are
   known to use both. We would like to resolve this in the latest
   specification to pick the approach that works better and also see
   if we can find a transition strategy for implementations to go from
   one to the other. Or for mixed networks until they are upgraded
   eventually to a common approach.

   Note, we assume that the holdtime field in the BSM is always used
   for RP-Mapping maintenance. The only difference between the two is
   whether an RP is to be removed by specifying a holdtime of 0 or by
   not including it in the RP set.


2. In order to compare them we will try to go through how one can cope
   with different types of events.

2.1 Fragmented BSMs and fragments getting lost

    EW: The mappings corresponding to the BSM fragments that have been
    received have their holdtime updated. In addition, the mappings for
    which the fragments are lost are not immediately deleted. They are
    kept around until their holdtime timer expires. If the next BSM is
    tuned to arrive before this holdtime expiry, the mappings are
    updated by it.

    Entries that have to be explicitly timed out are included with a
    holdtime of 0. So they are distinct from mappings that just happen
    to not arrive due to a lost fragment.

    IW: The router needs to wait for the entire Mapping record (G/mask
    and RP list) to be received before it purge mappings which have
    not been included this time. However, we think there is no way for
    a router to know that the entire mapping record has been
    received e.g. the last record in the fragment.

    You cannot distinguish between mappings that have been explicitly
    removed vs. those which are in the lost fragment.

2.2 RP disappearing

   A group range has one less RP or no RP.  If all RPs for a range
   disappears there may still be a wider range with an RP, so that
   for all the groups there is still some RP.

   RP Times out at the BSR
   RP unconfigured and sends C-RP advertisement with holdtime 0.
   EW:
   Trigger a BSM, set holdtime to 0 for RP. Routers remove the RP and
   move to the next best.
   IW:
   Trigger a BSM without the RP. If there are no other RPs for the group
   range, include group range in BSM without any RPs (*). Rest same as EW.

   (*) This is a new enhancement to make IW behave better than how it is
   specified in existing documents.

2.3 RP being replaced

   An RP disappears and is replaced by a candidate, or a new candidate
   arrives and being preferred.

   Disappears:

   EW:
   BSR triggers BSM, sets holdtime for old RP = 0 and includes new
   RP. Other routers remove the RP with holdtime 0 and add the new
   mapping.
   IW:
   BSR triggers BSM including new RP. All other routers remove the RP
   which is not included in the BSM and add new mapping.

   New candidate RP:
   No difference between EW/IW. Advertised in the BSM in addition to
   older one. All routers use some algo. to pick best RP.


2.4 BSR disappearing

    EW/IW: RP sets timeout using the holdtime.


2.5 BSR being replaced

    EW:
    The new BSR sends out an empty BSM advertising itself. All other
    routers simply update the known BSR. Mappings don't have their
    holdtimes updated, but are not removed either.

    As C-RPs advertise themselves to the new BSR, additional BSMs
    containing the latest version of the RP set at the EBSR are
    received and update the appr. holdtimes. Until the new EBSR learns
    all previously known mappings and send a "complete" BSM. At which
    point holdtimes for all mappings are updated.

    If some previously known C-RPs are not heard from, the mappings
    advertised by them will take "Holdtime" seconds to timeout. This
    causes slower convergence if these (now unreachable) C-RPs are
    being preferred over reachable ones.

    IW:
    The new BSR sends out an empty BSM advertising itself. All routers
    notice that this is an empty BSM and do not use it to purge the RP
    set but only to learn the new BSR.

    As C-RPs advertise themselves to the new BSR, additional BSMs are
    sent. However, these partial BSMs will disrupt the RP set on the
    other routers. C-RPs for which advertisements hadn't been received
    when the BSM was originated will be purged. There is the
    possibility of applying a heuristic to delay sending the BSM until
    most/all C-RP advertisements would have been received. But there
    is no way to know for sure that the complete set has been
    determined before originating the BSM.

    If some previously known C-RPs are not heard from, the mappings
    are removed immediately (because they are no included in the
    BSM). This results in faster convergence for the case where some
    C-RPs are partitioned from BSR.

    Note - in this section we assume that C-RPs trigger advertisements
    to a newly elected BSR. They do so with a small random delay which
    is much smaller than the default periodic message. 

2.6 Change in the group ranges that map to a given RP.

    EW/IW: No difference here. The older ranges will be
    replaced with the new ones.

3. Backward compatibility

   EW: Is backward compatible with IW. Because holdtime 0 will be
   respected by IW routers.

   IW: Not compatible... The incompatibility implies that some
   parts of the network will take longer to converge to newer RPs
   because they are waiting for the holdtime on those mappings to
   expire.


--vkogqOf2sHV7VnPd
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--vkogqOf2sHV7VnPd--



From pim-bounces@ietf.org  Wed Oct 27 11:58:18 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA18004
	for <pim-archive@lists.ietf.org>; Wed, 27 Oct 2004 11:58:17 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CMq2R-000267-FU; Wed, 27 Oct 2004 11:48:39 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CMpvH-0000Wb-9a
	for pim@megatron.ietf.org; Wed, 27 Oct 2004 11:41:15 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16667
	for <pim@ietf.org>; Wed, 27 Oct 2004 11:41:09 -0400 (EDT)
Received: from sj-iport-1-in.cisco.com ([171.71.176.70]
	helo=sj-iport-1.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CMq96-00007r-Jv for pim@ietf.org; Wed, 27 Oct 2004 11:55:33 -0400
Received: from sj-core-5.cisco.com (171.71.177.238)
	by sj-iport-1.cisco.com with ESMTP; 27 Oct 2004 08:52:04 -0700
X-BrightmailFiltered: true
Received: from cisco.com (cypher.cisco.com [171.69.11.142])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id i9RFeb6s000385;
	Wed, 27 Oct 2004 08:40:37 -0700 (PDT)
Received: (from eckert@localhost)
	by cisco.com (8.8.8-Cisco List Logging/8.8.8) id IAA11663;
	Wed, 27 Oct 2004 08:40:37 -0700 (PDT)
Date: Wed, 27 Oct 2004 08:40:37 -0700
From: Toerless Eckert <eckert@cisco.com>
To: Yakov Rekhter <yakov@juniper.net>
Subject: Re: [pim] draft-wijnands-pim-proxy
Message-ID: <20041027154037.GJ6005@cisco.com>
References: <20041024213052.GP3254@cisco.com>
	<200410271333.i9RDXMe88204@merlot.juniper.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200410271333.i9RDXMe88204@merlot.juniper.net>
User-Agent: Mutt/1.4i
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 30ac594df0e66ffa5a93eb4c48bcb014
Cc: Mike McBride <mmcbride@cisco.com>, pim@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=subscribe>
Sender: pim-bounces@ietf.org
Errors-To: pim-bounces@ietf.org

On Wed, Oct 27, 2004 at 06:33:22AM -0700, Yakov Rekhter wrote:
> > True. I was assuming that the possible applications are pretty obvious
> > to you as an author of USP#6,078,590. Are you telling me you can not
> > think of how it is to be used and i need to explain that to you ?
> 
> If you would read the patent, you would realize that this patent 
> does *not* use the RPF-vector-stack, but just a single address. 

Yes, so what ?

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


From pim-bounces@ietf.org  Wed Oct 27 12:18:34 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA19595
	for <pim-archive@lists.ietf.org>; Wed, 27 Oct 2004 12:18:34 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CMqU4-0000Wk-Ca; Wed, 27 Oct 2004 12:17:12 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CMqLh-000640-8M
	for pim@megatron.ietf.org; Wed, 27 Oct 2004 12:08:33 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA18911
	for <pim@ietf.org>; Wed, 27 Oct 2004 12:08:30 -0400 (EDT)
Received: from colo-dns-ext2.juniper.net ([207.17.137.64])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CMqZZ-0000hf-O5
	for pim@ietf.org; Wed, 27 Oct 2004 12:22:55 -0400
Received: from merlot.juniper.net (merlot.juniper.net [172.17.27.10])
	by colo-dns-ext2.juniper.net (8.12.3/8.12.3) with ESMTP id
	i9RG6sBm093236; Wed, 27 Oct 2004 09:06:55 -0700 (PDT)
	(envelope-from yakov@juniper.net)
Received: from juniper.net (sapphire.juniper.net [172.17.28.108])
	by merlot.juniper.net (8.11.3/8.11.3) with ESMTP id i9RG6se05705;
	Wed, 27 Oct 2004 09:06:54 -0700 (PDT)
	(envelope-from yakov@juniper.net)
Message-Id: <200410271606.i9RG6se05705@merlot.juniper.net>
To: Toerless Eckert <eckert@cisco.com>
Subject: Re: [pim] draft-wijnands-pim-proxy 
In-Reply-To: Your message of "Wed, 27 Oct 2004 08:40:37 PDT."
	<20041027154037.GJ6005@cisco.com> 
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <81718.1098893214.1@juniper.net>
Date: Wed, 27 Oct 2004 09:06:54 -0700
From: Yakov Rekhter <yakov@juniper.net>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
Cc: Mike McBride <mmcbride@cisco.com>, pim@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=subscribe>
Sender: pim-bounces@ietf.org
Errors-To: pim-bounces@ietf.org

> On Wed, Oct 27, 2004 at 06:33:22AM -0700, Yakov Rekhter wrote:
> > > True. I was assuming that the possible applications are pretty obvious
> > > to you as an author of USP#6,078,590. Are you telling me you can not
> > > think of how it is to be used and i need to explain that to you ?
> > 
> > If you would read the patent, you would realize that this patent 
> > does *not* use the RPF-vector-stack, but just a single address. 
> 
> Yes, so what ?

So, the application you mentioned *does not* need the RPF-vector-stack.

Yakov.

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


From pim-bounces@ietf.org  Wed Oct 27 12:33:02 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA20570
	for <pim-archive@lists.ietf.org>; Wed, 27 Oct 2004 12:33:02 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CMqhE-0003zL-Ix; Wed, 27 Oct 2004 12:30:48 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CMqel-0003La-5M
	for pim@megatron.ietf.org; Wed, 27 Oct 2004 12:28:15 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA20337
	for <pim@ietf.org>; Wed, 27 Oct 2004 12:28:11 -0400 (EDT)
Received: from netcore.fi ([193.94.160.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CMqsd-00016z-On
	for pim@ietf.org; Wed, 27 Oct 2004 12:42:37 -0400
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id i9RGRZL19803;
	Wed, 27 Oct 2004 19:27:35 +0300
Date: Wed, 27 Oct 2004 19:27:35 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: Tom Pusateri <pusateri@juniper.net>
Subject: Re: [pim] WG Query: draft-farinacci-pim-pop-count-00.txt
In-Reply-To: <200410181832.i9IIWje85048@merlot.juniper.net>
Message-ID: <Pine.LNX.4.61.0410271925310.19728@netcore.fi>
References: <200410181832.i9IIWje85048@merlot.juniper.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Cc: pim@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=subscribe>
Sender: pim-bounces@ietf.org
Errors-To: pim-bounces@ietf.org

Hi,

On Mon, 18 Oct 2004, Tom Pusateri wrote:
> Dino had asked at the last IETF meeting if we would accept
> the following draft, draft-farinacci-pim-pop-count-00.txt as a PIM
> working group document.
>
> I never sent out the question to the mailing list and Mike reminded
> me today.
>
> Please read the draft if you haven't and send your thoughts to
> the list by next Monday, Oct. 25th at 5:00 pm PST.

This is coming late, but if it matters..

I'm uncomfortable with the approach.  We need to make multicast 
routing less, not more complex.  This seems to be putting a external, 
though useful, function in the protocol where it shouldn't be.

Hence, I'd rather see that we tried to address the problems in a more 
'conventional' manner.

-- 
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings

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


From pim-bounces@ietf.org  Wed Oct 27 13:45:23 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA26489
	for <pim-archive@lists.ietf.org>; Wed, 27 Oct 2004 13:45:22 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CMrnX-0003aX-Ss; Wed, 27 Oct 2004 13:41:23 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CMrii-0002Ap-Oh
	for pim@megatron.ietf.org; Wed, 27 Oct 2004 13:36:24 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA25367
	for <pim@ietf.org>; Wed, 27 Oct 2004 13:36:23 -0400 (EDT)
Received: from sj-iport-1-in.cisco.com ([171.71.176.70]
	helo=sj-iport-1.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CMrwb-0002YC-R1 for pim@ietf.org; Wed, 27 Oct 2004 13:50:47 -0400
Received: from sj-core-2.cisco.com (171.71.177.254)
	by sj-iport-1.cisco.com with ESMTP; 27 Oct 2004 10:47:17 -0700
X-BrightmailFiltered: true
Received: from cisco.com (cypher.cisco.com [171.69.11.142])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id i9RHZlYJ012524;
	Wed, 27 Oct 2004 10:35:47 -0700 (PDT)
Received: (from eckert@localhost)
	by cisco.com (8.8.8-Cisco List Logging/8.8.8) id KAA24138;
	Wed, 27 Oct 2004 10:35:49 -0700 (PDT)
Date: Wed, 27 Oct 2004 10:35:49 -0700
From: Toerless Eckert <eckert@cisco.com>
To: Yakov Rekhter <yakov@juniper.net>
Subject: Re: [pim] draft-wijnands-pim-proxy
Message-ID: <20041027173549.GO6005@cisco.com>
References: <20041027154037.GJ6005@cisco.com>
	<200410271606.i9RG6se05705@merlot.juniper.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200410271606.i9RG6se05705@merlot.juniper.net>
User-Agent: Mutt/1.4i
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Cc: Mike McBride <mmcbride@cisco.com>, pim@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=subscribe>
Sender: pim-bounces@ietf.org
Errors-To: pim-bounces@ietf.org

On Wed, Oct 27, 2004 at 09:06:54AM -0700, Yakov Rekhter wrote:
> > On Wed, Oct 27, 2004 at 06:33:22AM -0700, Yakov Rekhter wrote:
> > > > True. I was assuming that the possible applications are pretty obvious
> > > > to you as an author of USP#6,078,590. Are you telling me you can not
> > > > think of how it is to be used and i need to explain that to you ?
> > > 
> > > If you would read the patent, you would realize that this patent 
> > > does *not* use the RPF-vector-stack, but just a single address. 
> > 
> > Yes, so what ?
> 
> So, the application you mentioned *does not* need the RPF-vector-stack.

Yes, did i ever dispute that ? I was purely stating about my expectations
against your insight into the problem space as a SME, not about the actual
details of the patented application.

Cheers
	Toerless

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


From pim-bounces@ietf.org  Thu Oct 28 07:50:27 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA04106
	for <pim-archive@lists.ietf.org>; Thu, 28 Oct 2004 07:50:27 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CN8gz-0001Z8-81; Thu, 28 Oct 2004 07:43:45 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CN8fx-0001ID-KO
	for pim@megatron.ietf.org; Thu, 28 Oct 2004 07:42:41 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA03504
	for <pim@ietf.org>; Thu, 28 Oct 2004 07:42:41 -0400 (EDT)
Received: from catarina.usc.edu ([204.57.0.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CN8u0-000788-Dw
	for pim@ietf.org; Thu, 28 Oct 2004 07:57:13 -0400
Received: from msg-mx4.usc.edu (sjes@msg-mx4.usc.edu [128.125.137.9])
	by catarina.usc.edu (8.12.9/8.12.9) with ESMTP id i9SBg4oh089661
	for <pim@catarina.usc.edu>; Thu, 28 Oct 2004 04:42:09 -0700 (PDT)
	(envelope-from bharat_joshi@infosys.com)
Received: from kecgate03.infosys.com ([220.227.179.21])
	by msg-mx4.usc.edu (Sun Java System Messaging Server 6.1 HotFix 0.02
	(built
	Aug 25 2004)) with ESMTP id <0I6A008BVLU2ZRD0@msg-mx4.usc.edu> for
	pim@catarina.usc.edu; Thu, 28 Oct 2004 04:42:04 -0700 (PDT)
Received: from INDHUBBHS02.ad.infosys.com ([192.168.200.82])
	by kecgate03.infosys.com with InterScan Messaging Security Suite; Thu,
	28 Oct 2004 17:06:47 +0530
Received: from kecmsg07.ad.infosys.com ([192.168.200.68])
	by INDHUBBHS02.ad.infosys.com with Microsoft SMTPSVC(5.0.2195.6713);
	Thu, 28 Oct 2004 17:10:40 +0530
Received: from kecmsg06.ad.infosys.com ([192.168.200.75])
	by kecmsg07.ad.infosys.com with Microsoft SMTPSVC(5.0.2195.6713); Thu,
	28 Oct 2004 17:10:39 +0530
Date: Thu, 28 Oct 2004 17:10:38 +0530
From: bharat_joshi <bharat_joshi@infosys.com>
Subject: RE: [pim] The BSR spec and maintaining group-to-RP mappings
To: Stig Venaas <Stig.Venaas@uninett.no>
Message-id: <56E2573C375A414191118970BDE06A1512887A53@kecmsg06.ad.infosys.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft Exchange V6.0.6487.1
Content-type: text/plain; charset=Windows-1252
Content-transfer-encoding: 7BIT
Content-class: urn:content-classes:message
Thread-topic: [pim] The BSR spec and maintaining group-to-RP mappings
Thread-index: AcS8NDwpCIgKpmf3QAqPjVDEShNbFAAqe8n4
X-OriginalArrivalTime: 28 Oct 2004 11:40:39.0980 (UTC)
	FILETIME=[F3109EC0:01C4BCE2]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793
Content-Transfer-Encoding: 7BIT
Cc: pim@catarina.usc.edu
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=subscribe>
Sender: pim-bounces@ietf.org
Errors-To: pim-bounces@ietf.org
Content-Transfer-Encoding: 7BIT

Hi Stig,

   I think we should go with EW.

   There are certain advantages with EW.

   * Backward compatibility
   * If fragmented BSM packet get lost, a router will still wait for 
     holdtime timer to expire before it removes the RP set which have lost.
   * This will also help when EBSR changes and new EBSR has not received all
     the C-RP messages and send out a partial BSM. All routers will keep
     their RP set for RP holdtime which are not available in this BSM. Which
     may be available in next BSM before RP holdtime expires.


Thanks & Regards,
Bharat

-----Original Message-----
From:	pim-bounces@ietf.org on behalf of Stig Venaas
Sent:	Wed 10/27/2004 8:04 PM
To:	pim@catarina.usc.edu
Cc:	
Subject:	[pim] The BSR spec and maintaining group-to-RP mappings
In the last update of the BSR spec, draft-ietf-pim-sm-bsr-04, we changed
the way group-to-RP mappings are maintained.

In the draft update we propose ONLY using the hold-time to expire the RP
mappings. Each time a new BSM is received the timers are reset.  A hold-
time of 0 means immediate removal. If a BSM is received which does not
contain a previously learnt RP-mapping, routers will still *wait* for
the mapping's holdtime to expire before removing it. We call this
approach "Explicit withdrawal" (EW) because the BSR has to explicitly
include RPs to be deleted with a holdtime of 0.

Another approach, is that in addition to using holdtime for RP
maintenance, an RP is *also* removed when a BSM not containing the RP is
received. We call this the "Implicit withdrawal" (IW) approach. IW
because not including an RP, implicitly implies that it is to be removed.

We think the old PIM RFC and the previous BSR drafts both are ambiguous
but lean towards the IW approach. However, there are implementations of
both approaches.

We would like to resolve this in the latest specification to pick the
approach that works better and also see if we can find a transition
strategy for implementations to go from one to the other. Or for mixed
networks until they are upgraded eventually to a common approach.

Stig




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


From pim-bounces@ietf.org  Thu Oct 28 14:26:16 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09119
	for <pim-archive@lists.ietf.org>; Thu, 28 Oct 2004 14:26:16 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CNCm0-000520-La; Thu, 28 Oct 2004 12:05:12 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CNBpu-00078p-Ss; Thu, 28 Oct 2004 11:05:11 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA22295;
	Thu, 28 Oct 2004 11:05:09 -0400 (EDT)
Message-Id: <200410281505.LAA22295@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Date: Thu, 28 Oct 2004 11:05:09 -0400
Cc: pim@ietf.org
Subject: [pim] I-D ACTION:draft-ietf-pim-sm-v2-new-11.txt
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=subscribe>
Sender: pim-bounces@ietf.org
Errors-To: pim-bounces@ietf.org

--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		: Protocol Independent Multicast - Sparse Mode PIM-SM): 
			  Protocol Specification (Revised)
	Author(s)	: B. Fenner, et al.
	Filename	: draft-ietf-pim-sm-v2-new-11.txt,.ps
	Pages		: 148
	Date		: 2004-10-27
	
This document specifies Protocol Independent Multicast -
Sparse Mode (PIM-SM).  PIM-SM is a multicast routing protocol
that can use the underlying unicast routing information base
or a separate multicast-capable routing information base.  It
builds unidirectional shared trees rooted at a Rendezvous
Point (RP) per group, and optionally creates shortest-path
trees per source.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pim-sm-v2-new-11.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of the message.  
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.


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-sm-v2-new-11.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-sm-v2-new-11.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: <2004-10-28110215.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-pim-sm-v2-new-11.txt

--OtherAccess
Content-Type: Message/External-body; name="draft-ietf-pim-sm-v2-new-11.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2004-10-28110215.I-D@ietf.org>


--OtherAccess--

--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--NextPart--





From pim-bounces@ietf.org  Fri Oct 29 22:07:56 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA04472
	for <pim-archive@lists.ietf.org>; Fri, 29 Oct 2004 22:07:56 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CNiSg-0006bO-C3; Fri, 29 Oct 2004 21:55:22 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CNiPk-00049B-Ej
	for pim@megatron.ietf.org; Fri, 29 Oct 2004 21:52:22 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA03626
	for <pim@ietf.org>; Fri, 29 Oct 2004 21:52:18 -0400 (EDT)
Received: from catarina.usc.edu ([204.57.0.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNie2-0007nU-8h
	for pim@ietf.org; Fri, 29 Oct 2004 22:07:13 -0400
Received: from huawei.com (mta0.huawei.com [61.144.161.41])
	by catarina.usc.edu (8.12.9/8.12.9) with ESMTP id i9U1pcoh012690
	for <pim@catarina.usc.edu>; Fri, 29 Oct 2004 18:51:41 -0700 (PDT)
	(envelope-from prashantj@huawei.com)
Received: from huawei8tthy486 (mta1.huawei.com [172.17.1.60])
	by mta1.huawei.com
	(iPlanet Messaging Server 5.2 HotFix 1.16 (built May 14 2003))
	with ESMTPA id <0I6D00B2AIXG1P@mta1.huawei.com> for
	pim@catarina.usc.edu; Sat, 30 Oct 2004 09:32:12 +0800 (CST)
Date: Sat, 30 Oct 2004 09:43:04 +0800
From: Prashant Jhingran <prashantj@huawei.com>
Subject: RE: [pim] The BSR spec and maintaining group-to-RP mappings
In-reply-to: <56E2573C375A414191118970BDE06A1512887A53@kecmsg06.ad.infosys.c	om>
To: "'bharat_joshi'" <bharat_joshi@infosys.com>,
        "'Stig Venaas'" <Stig.Venaas@uninett.no>
Message-id: <001401c4be21$d05f9620$30226e0a@huawei8tthy486>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Mailer: Microsoft Outlook, Build 10.0.3416
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
X-imss-version: 2.7
X-imss-result: Passed
X-imss-approveListMatch: *@huawei.com
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1a1bf7677bfe77d8af1ebe0e91045c5b
Content-Transfer-Encoding: 7BIT
Cc: pim@catarina.usc.edu
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=subscribe>
Sender: pim-bounces@ietf.org
Errors-To: pim-bounces@ietf.org
Content-Transfer-Encoding: 7BIT

Hi All,

Regarding the strategy adopted to expire the RP mappings...
Its better for the routers in the domain not to remove RP if not
included in the RP set of the latest BSM, EW can be used instead.

Consider the case when CRP goes down. 
The CRP timer would definitely expire at EBSR. 
Hence the next BSM may be sent with a holdtime of 0 and as a result all
the routers in the domain can synchronize there database with latest
BSM.

However we need to counter act the loss of RP-set during BSR election
and also situations when a CRP and EBSR goes down at the same time....
In such scenarios holdtime of Zero may not be helpful.

Regards,
Prashant Jhingran

Huawei Technologies 
Beijing, China
Ph# 00-86-10-82882837  (O)  
        00-86-10-62983443  (R)
www.huawei.com

"You see, all the problems in the world are created by those who want
'perfection.' "
   -- Sri Sri Ravi Shankar  www.artofliving.org  


-----Original Message-----
From: pim-bounces@ietf.org [mailto:pim-bounces@ietf.org] On Behalf Of
bharat_joshi
Sent: Thursday, October 28, 2004 7:41 PM
To: Stig Venaas
Cc: pim@catarina.usc.edu
Subject: RE: [pim] The BSR spec and maintaining group-to-RP mappings


Hi Stig,

   I think we should go with EW.

   There are certain advantages with EW.

   * Backward compatibility
   * If fragmented BSM packet get lost, a router will still wait for 
     holdtime timer to expire before it removes the RP set which have
lost.
   * This will also help when EBSR changes and new EBSR has not received
all
     the C-RP messages and send out a partial BSM. All routers will keep
     their RP set for RP holdtime which are not available in this BSM.
Which
     may be available in next BSM before RP holdtime expires.


Thanks & Regards,
Bharat

-----Original Message-----
From:	pim-bounces@ietf.org on behalf of Stig Venaas
Sent:	Wed 10/27/2004 8:04 PM
To:	pim@catarina.usc.edu
Cc:	
Subject:	[pim] The BSR spec and maintaining group-to-RP mappings
In the last update of the BSR spec, draft-ietf-pim-sm-bsr-04, we changed
the way group-to-RP mappings are maintained.

In the draft update we propose ONLY using the hold-time to expire the RP
mappings. Each time a new BSM is received the timers are reset.  A hold-
time of 0 means immediate removal. If a BSM is received which does not
contain a previously learnt RP-mapping, routers will still *wait* for
the mapping's holdtime to expire before removing it. We call this
approach "Explicit withdrawal" (EW) because the BSR has to explicitly
include RPs to be deleted with a holdtime of 0.

Another approach, is that in addition to using holdtime for RP
maintenance, an RP is *also* removed when a BSM not containing the RP is
received. We call this the "Implicit withdrawal" (IW) approach. IW
because not including an RP, implicitly implies that it is to be
removed.

We think the old PIM RFC and the previous BSR drafts both are ambiguous
but lean towards the IW approach. However, there are implementations of
both approaches.

We would like to resolve this in the latest specification to pick the
approach that works better and also see if we can find a transition
strategy for implementations to go from one to the other. Or for mixed
networks until they are upgraded eventually to a common approach.

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-bounces@ietf.org  Sun Oct 31 21:43:00 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA26601
	for <pim-archive@lists.ietf.org>; Sun, 31 Oct 2004 21:43:00 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1COS7s-0005sU-Cy; Sun, 31 Oct 2004 21:40:56 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1COS4H-0005QL-Ed
	for pim@megatron.ietf.org; Sun, 31 Oct 2004 21:37:13 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA26159
	for <pim@ietf.org>; Sun, 31 Oct 2004 21:37:11 -0500 (EST)
Received: from catarina.usc.edu ([204.57.0.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1COSJ1-0002au-Ev
	for pim@ietf.org; Sun, 31 Oct 2004 21:52:32 -0500
Received: from aa-mx1.nexthop.com (dns.nexthop.com [65.247.36.216])
	by catarina.usc.edu (8.12.9/8.12.9) with ESMTP id iA12aaoh040192
	for <pim@catarina.usc.edu>; Sun, 31 Oct 2004 18:36:37 -0800 (PST)
	(envelope-from ctbrown@nexthop.com)
Received: from localhost (localhost [127.0.0.1])
	by aa-mx1.nexthop.com (Postfix) with ESMTP
	id DABE42D4E09; Sun, 31 Oct 2004 21:31:02 -0500 (EST)
Received: from aa-mx1.nexthop.com ([127.0.0.1])
	by localhost (aa-mx1.nexthop.com [127.0.0.1]) (amavisd-new, port 10024)
	with LMTP id 98891-01-3; Sun, 31 Oct 2004 21:31:01 -0500 (EST)
Received: from nexthop.com (ctbrown.nexthop.com [65.247.36.75])
	by aa-mx1.nexthop.com (Postfix) with ESMTP
	id BA9FA2D4DCE; Sun, 31 Oct 2004 21:31:01 -0500 (EST)
To: Stig.Venaas@uninett.no
Subject: RE: [pim] The BSR spec and maintaining group-to-RP mappings
From: Christopher Thomas Brown <ctbrown@nexthop.com>
Date: Sun, 31 Oct 2004 21:30:17 -0500
Message-Id: <20041101023101.BA9FA2D4DCE@aa-mx1.nexthop.com>
X-Virus-Scanned: by amavisd-new at nexthop.com
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17
Cc: pim@catarina.usc.edu
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=subscribe>
Sender: pim-bounces@ietf.org
Errors-To: pim-bounces@ietf.org


Stig,
I feel that the EW approach is better than the ambiguously defined
approach that the current specification is.

However, I have some thoughts about things you bring up.

In section 2.1 you state:

>   IW: The router needs to wait for the entire Mapping record (G/mask
>   and RP list) to be received before it purge mappings which have
>   not been included this time. However, we think there is no way for
>   a router to know that the entire mapping record has been
>   received e.g. the last record in the fragment.

Is this true? It seems like one of the previous drafts had a solution for
this problem. In a group range mapping there is a count of the RPs for the
mapping (RP count) and a count of the RPs included in the current message
(Frag RP count). Each fragment of the message carries a tag that indicates
which instance of the BSR message it is. One knows when the entire mapping
record has been received when one has received as many RPs for the group
range as indicated by the RP count. One knows that a fragment has been
lost when a new instance of the message is encountered.

Now, I don't really like this approach but I think it does provide a way
for a router to know that the entire mapping record has been received.
Perhaps, I'm missing something here.


2.2 RP disappearing

For EW, I hope the 'trigger BSM' action is only for the affected group
range and only the affected RP.


2.4 BSR disappearing

Is it really desirable to not have an RP set at all? Wouldn't using
a previously available mapping be better than not having a mapping at all?
Of course this should only occur if all of the CBSRs are down. How
likely is it that all domain's CBSRs will be down? Is it worth trying
to handle that or is going to an empty RPset OK.


2.5 BSR being replaced

With EW, since the routers in the PIM domain do not change their RP sets
in response to the elected BSR changing, it seems like an optimization if
the newly elected BSR uses the RP set it had stored from the previous BSR
to announce to the domain.


3 Backward compatibility

I don't think you can firmly make the claim that EW is backwards compatible.
There is nothing that I recall in some of the older specs that requires
a router to honor a holdtime of zero in a BSM as a request to remove
the RP from that mapping. As has been said, older specs are ambiguous. Some
implementations that do IW only remove from the RP set at a non-EBSR
upon the implicit withdrawal and not on holdtime timeout.

* Transition

If consensus is reached on the EW approach, I think some of the suggested 
IW behaviors should be documented as they help compatibility between
EW and IW. A vendor that has implemented the IW approach with its current
ambiguities can then implement the documented behaviors, if they have not
already, and be reasonabilly sure that their IW implementation will
interoperate with the EW approach.

Chris

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


