From pim-bounces@ietf.org Thu Apr 19 18:05:46 2007
Return-path: <pim-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HeekK-00037n-Co; Thu, 19 Apr 2007 18:04:56 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HeekJ-00037f-CC
	for pim@ietf.org; Thu, 19 Apr 2007 18:04:55 -0400
Received: from sj-iport-3-in.cisco.com ([171.71.176.72]
	helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HeekH-0004Fr-N4 for pim@ietf.org; Thu, 19 Apr 2007 18:04:55 -0400
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
	by sj-iport-3.cisco.com with ESMTP; 19 Apr 2007 15:04:53 -0700
X-IronPort-AV: i="4.14,429,1170662400"; 
	d="scan'208"; a="479747006:sNHT56501168"
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238])
	by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l3JM4rAb032085
	for <pim@ietf.org>; Thu, 19 Apr 2007 15:04:53 -0700
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com
	[128.107.191.100])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id l3JM4qEi022309
	for <pim@ietf.org>; Thu, 19 Apr 2007 22:04:53 GMT
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by
	xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 19 Apr 2007 15:04:52 -0700
Received: from irp-view7.cisco.com ([171.70.65.144]) by
	xfe-sjc-212.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 19 Apr 2007 15:04:52 -0700
Date: Thu, 19 Apr 2007 15:04:52 -0700 (PDT)
From: Mike McBride <mmcbride@cisco.com>
To: pim@ietf.org
Subject: [pim] IETF68 pimwg mtg minutes
Message-ID: <Pine.GSO.4.63.0704191501400.27909@irp-view7.cisco.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-OriginalArrivalTime: 19 Apr 2007 22:04:52.0383 (UTC)
	FILETIME=[C1740AF0:01C782CE]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=6472; t=1177020293;
	x=1177884293; c=relaxed/simple; s=sjdkim1004;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=mmcbride@cisco.com;
	z=From:=20Mike=20McBride=20<mmcbride@cisco.com>
	|Subject:=20[pim]=20IETF68=20pimwg=20mtg=20minutes |Sender:=20;
	bh=CjsfdsR2NN+98fOfUpboVcWGl0652zERLUpNvJ9Y9I4=;
	b=dGEyzVnKhMTVU4iseURPxbPYY45y6a6WAjzZd9z9hSGCLqyADaphWDXk3pDM2Jw/akjgDCju
	8tFLF1a5G+BqtvBHUYStovjw/5MgY+q5h3PkOhW+oI282a0MI9MaIcOsnon3Z9zHT72mjKOih2
	BP9mavafkpU3noqdZ0T0jFwrw=;
Authentication-Results: sj-dkim-1; header.From=mmcbride@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim1004 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 36b1f8810cb91289d885dc8ab4fc8172
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=subscribe>
Errors-To: pim-bounces@ietf.org

pimwg meeting minutes
Prague, Czech Republic
Tuesday, March 20th, 2007

Created the summarized notes from the pimwg audio archive which can be 
listened to in its entirety at: 
http://limestone.uoregon.edu/ftp/pub/videolab/media/ietf68/ietf68-ch6-tue-pm.mp3

Mike: Welcome, agenda bashing

Bill: AD for few more hours. Both bidir and pim mib approved by iesg in last 
few weeks. Getting stuff off books that have been languishing. BSR is almost 
complete as well.

Mike: Thanks to Bill for all his hard work as AD

BSR Draft:

Alex: Received few comments from last rev of bsr draft from Eric Gray and Sandy 
Murphy. Will talk to Sandy this week, few issues she came up with, will take 
to list. Lars Eggert: are you allowed to say document updates 2362? It has 
been obsoleted by new pimsm spec which doesn't contain the bsr. Alex thinks its 
correct that we say we obsolete 2362.

Bill: Those relationships don't have the meanings we'd like them to. Since its 
obsolete it may be that it just doesn't matter, you should take out obsolete 
comments, just pretend this is new.

Alex: Eric Gray had valid issues with bsr state machine and I will update draft 
to clarify things a bit. Describe the no info state better.

Alex: Eric has issue that scopes could expire before bootstrap timer expires 
unless timers were constrained in certain way. Have a constraint that its not 
allowed to happen. State machine is correct. Scopes on timer always has to be 
higher than bootstrap timer. Scopes will expire a little bit later than if 
implemented then with default timers specified in current spec.

Alex: There is a timer assoc with group to rp mapping and when that timer 
expires that mapping is deleted. its not explicitely mentioned anywhere. It 
could be added to a section that describes how the rp set is received and used 
by a router.

Alex: Would like to published one more revision then get draft approved.

RPF vector and join attribute drafts:

Arjen: join attributes passed last call, one last Stig comment about adding 
IANA registry then off to iesg. rpf vector has a few more improvements and 
corrections then we'll go to last call.

last hop threats draft:

Pekka:recap in hopes to generate feedback. It identifies last hop 
vulnerabilities and attacks that can be done with vulnerabilities. Last hop 
between router and host is the concern. Could send unauthorized register 
message to RPs that may contain spoofed messages and create nasty state. Host 
may also become unauthorized neighbor. Routers may accept unauthorized 
messages from neighbors. Unauthorized node could be elected as DR. Mitigation 
methods: pim passive mode (able to receive and send multicast but router 
doesn't send hellos on that interface or process pim messages). Possible when 
you have a single router on a link. Also could use IPsec on a link. If just 
one router also possible to filter out all pim messages. When multiple valid 
pim routers on a link, you'll have to use IPsec.

Not much changed since last rev except minor editorial updates. pim spec has 
been published so this can now proceed. pim passive has been implemented in 
Junos. Should we go for wglc or have people review doc.

Derek: could you also have pim filter which filters on sources.

Pekka: yes, but you could also spoof the source. The host could send source 
messages with router. So that might not be good enough.

Derek: we have the capability to filter on source but should also combine that 
with lockdown of addresses.

Dino: How about having a switch between host and routers. If a switch is 
connected to a particular host port don't accept pim messages on that port, so 
router never sees the pim message.

Pekka: yes, that could also be mentioned in the doc.

Pekka: How to procede with the doc?

Mike: revise the doc based upon these comments then we'll issue wglc.

Mike: authors for linklocal draft not able to attend but they are activity 
working on it and have been seeking and receiving advice from msec.

Mike: rechartering/milestones discussion. sent a proposed new charter, all 
comments have been incorporated in text of new charter and milestones. Will 
email ADS and secretariat in a week if I don't hear anything.

Mike: One milestone worth discussion is reducing the messaging of pim. We did 
have a design team to look into ways to reduce pim messaging. at that time it 
appeared that a j/p ack proposal was most agreed upon but since then the 
urgency of it has dissipated and it was thought that it was a bit too complex. 
There have been other thoughts on how to handle this. We have had plenty of 
requests to come up with some sort of solution from operators and l3vpn.

Maria: Nothing has been completed on this in pimwg?

Mike:  correct

Maria: Something has to be done in this area, particularly in context of 2547 
multicast. refresh reduction is critical for scalability purposes. Dont see 
the problem yet for scalability of mvpns but it may show up and need some sort 
of solution. Receiver explicit tracking needs to be a part of the solution for 
aggregation purposes of trees in the core. It has to scale.

Mike: how does wg want to proceed to solve this?

Dino: Do people think this is important for non mvpn environments

Maria: yes. definitely need in core for vpn context, but also needed towards 
the CE. native ip multicast needs it. biggest impact is in the core.

Dino: let me restate: do you think solution is necessary for a non pe box.

Greg: Marias explanation is still mvpn context. PE to CE is still mvpn 
environment. The solution would have to be on both ends of the PE.

Dino: If there is too much traffic on the PE-CE link, there is probably too 
much state on one hop downstream as well. Do your customers have a concern?

Maria: not yey. They do have the choice of bidir to reduce state.

Maria: Only PE, which has many interfaces, is of most importance.

Mike: We have a milestone to get something submitted by end of year. If that 
doesn't happen, we'll probably need to create a design team.

Mike: drafts have been submitted (not in time to discuss for ietf) to offer 
other enhancements to pim which fit into our new charter.

Pekka: One clarification needed in the charter which says provide a "more 
reliable" solution. Propose to whom and by whom.

Mike: I'll change "propose" to "submit".

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



From pim-bounces@ietf.org Sat Apr 21 12:07:58 2007
Return-path: <pim-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HfI7q-0006yv-Va; Sat, 21 Apr 2007 12:07:50 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HfI7q-0006yq-4X
	for pim@ietf.org; Sat, 21 Apr 2007 12:07:50 -0400
Received: from web8804.mail.in.yahoo.com ([203.84.221.13])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1HfI7o-0007xr-7v
	for pim@ietf.org; Sat, 21 Apr 2007 12:07:50 -0400
Received: (qmail 16679 invoked by uid 60001); 21 Apr 2007 16:07:46 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.co.in;
	h=X-YMail-OSG:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID;
	b=j1h9wLnrzUJ6faa0nASkwp3YqftXiCzLuXeTzawcBkOJsbSkYXbf80wSGjpv/35iCfw5bqEVZ42Z4UMeCNfshjIKMA0l28h+3Vtmf1+5S9KCTC7kg6NCaHBYPVNpoxhF1PMiJQft9b3wfN/IefYJoXkT1/TxqZTVoImzabTU5BI=;
X-YMail-OSG: Z5tY.bQVM1l0gGblI_dm_0hiJC4AgjNxpIflbAsgI4yWiZd.j4juVuKMwGkDgR9JOI8U_ZkEyQPzrf3b1nAcpzsfimUd.KUgfvleBlmBQ8edZnRlUmpSh1deqQ48.g--
Received: from [59.92.33.216] by web8804.mail.in.yahoo.com via HTTP;
	Sat, 21 Apr 2007 09:07:46 PDT
Date: Sat, 21 Apr 2007 09:07:46 -0700 (PDT)
From: Binu TN <tnbinu@yahoo.co.in>
To: pim@ietf.org
MIME-Version: 1.0
Message-ID: <223775.16676.qm@web8804.mail.in.yahoo.com>
X-Spam-Score: 1.5 (+)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
Subject: [pim] pim-sm router transitions from DR to non-DR
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="===============0525508711=="
Errors-To: pim-bounces@ietf.org

--===============0525508711==
Content-Type: multipart/alternative; boundary="0-1897751459-1177171666=:16676"
Content-Transfer-Encoding: 8bit

--0-1897751459-1177171666=:16676
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

Hi,

  I have a basic doubt in the pim-sm router transition from DR to non-DR. Let's assume a scenario where a sm router (e.g., RT1) is DR in a LAN and it has multicast route entry and it is trigerring Join messages to RP (it is in some other network) as it has some interesting hosts. If another sm router (e.g.RT2) with higher IP address comes into the LAN of RT1, as per my understanding RT2 will become DR and RT1 will become non-DR to that LAN. My doubts are,

1) whether the multicast route entries that are present in RT1 before entry of  RT2 will be removed?

2) Will RT1 stops trigerring Join messages to RP? Or RT1 will be trigerring Join messages for existing entries and RT2 will be trigerring for any new entries?

Please clear my doubts.
Thank you in advance.

Regards,
Binu.

       
---------------------------------
Ahhh...imagining that irresistible "new car" smell?
 Check outnew cars at Yahoo! Autos.
--0-1897751459-1177171666=:16676
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

Hi,<br><br>&nbsp; I have a basic doubt in the pim-sm router transition from DR to non-DR. Let's assume a scenario where a sm router (e.g., RT1) is DR in a LAN and it has multicast route entry and it is trigerring Join messages to RP (it is in some other network) as it has some interesting hosts. If another sm router (e.g.RT2) with higher IP address comes into the LAN of RT1, as per my understanding RT2 will become DR and RT1 will become non-DR to that LAN. My doubts are,<br><br>1) whether the multicast route entries that are present in RT1 before entry of&nbsp; RT2 will be removed?<br><br>2) Will RT1 stops trigerring Join messages to RP? Or RT1 will be trigerring Join messages for existing entries and RT2 will be trigerring for any new entries?<br><br>Please clear my doubts.<br>Thank you in advance.<br><br>Regards,<br>Binu.<br><p>&#32;

      <hr size=1>Ahhh...imagining that irresistible "new car" smell?<br> Check out
<a href="http://us.rd.yahoo.com/evt=48245/*http://autos.yahoo.com/new_cars.html;_ylc=X3oDMTE1YW1jcXJ2BF9TAzk3MTA3MDc2BHNlYwNtYWlsdGFncwRzbGsDbmV3LWNhcnM-">new cars at Yahoo! Autos.</a>

--0-1897751459-1177171666=:16676--


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

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

--===============0525508711==--




From pim-bounces@ietf.org Mon Apr 23 13:25:48 2007
Return-path: <pim-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hg2IE-00017v-Kf; Mon, 23 Apr 2007 13:25:38 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hfbs9-0000ju-M3
	for pim@ietf.org; Sun, 22 Apr 2007 09:12:57 -0400
Received: from mx2.lvl7.com ([66.192.95.83] helo=lvl7-trend01.lvl7.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hfbs7-0004lo-V4
	for pim@ietf.org; Sun, 22 Apr 2007 09:12:57 -0400
Received: from lvl7in-mail01.lvl7.com ([10.240.1.18]) by lvl7-trend01.lvl7.com
	with InterScan VirusWall; Sun, 22 Apr 2007 09:12:54 -0400
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [pim] pim-sm router transitions from DR to non-DR
X-MimeOLE: Produced By Microsoft Exchange V6.5
Date: Sun, 22 Apr 2007 18:42:50 +0530
Message-ID: <FE7FB54DCB7C6949A1D3F9FF22DA6C13509202@lvl7in-mail01.lvl7.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [pim] pim-sm router transitions from DR to non-DR
Thread-Index: AceEL0KzeHC2GTFyQz+7QJS8UhuvrAAsEhDw
From: "Satyanarayana Dillikar" <dsatyana@broadcom.com>
To: "Binu TN" <tnbinu@yahoo.co.in>,
	<pim@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3be09dac38eaa50f02d21c7fcee1128c
X-Mailman-Approved-At: Mon, 23 Apr 2007 13:25:36 -0400
Cc: 
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="===============1866383548=="
Errors-To: pim-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1866383548==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C784DF.ED9F661A"

This is a multi-part message in MIME format.

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

Hi Binu,

 See inline

=20

________________________________

From: Binu TN [mailto:tnbinu@yahoo.co.in]=20
Sent: Saturday, April 21, 2007 9:38 PM
To: pim@ietf.org
Subject: [pim] pim-sm router transitions from DR to non-DR

=20

Hi,

  I have a basic doubt in the pim-sm router transition from DR to
non-DR. Let's assume a scenario where a sm router (e.g., RT1) is DR in a
LAN and it has multicast route entry and it is trigerring Join messages
to RP (it is in some other network) as it has some interesting hosts. If
another sm router (e.g.RT2) with higher IP address comes into the LAN of
RT1, as per my understanding RT2 will become DR and RT1 will become
non-DR to that LAN. My doubts are,

1) whether the multicast route entries that are present in RT1 before
entry of  RT2 will be removed?



[dsatya] Not necessarily, those entries will changed based on the
unicast route change to RP. (due to insertion of RT2)


2) Will RT1 stops trigerring Join messages to RP? Or RT1 will be
trigerring Join messages for existing entries and RT2 will be trigerring
for any new entries?



[dsatya] RT1 should not trigger Join Msgs to RP and RT2 should take up
the job.

Thanks

Satya


Please clear my doubts.
Thank you in advance.

Regards,
Binu.

 =20

________________________________

Ahhh...imagining that irresistible "new car" smell?
Check out new cars at Yahoo! Autos.
<http://us.rd.yahoo.com/evt=3D48245/*http:/autos.yahoo.com/new_cars.html;=
_
ylc=3DX3oDMTE1YW1jcXJ2BF9TAzk3MTA3MDc2BHNlYwNtYWlsdGFncwRzbGsDbmV3LWNhcnM=
-
> =20


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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:st1=3D"urn:schemas-microsoft-com:office:smarttags" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]--><o:SmartTagType
 namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" =
name=3D"place"
 downloadurl=3D"http://www.5iantlavalamp.com/"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"City" =
downloadurl=3D"http://www.5iamas-microsoft-com:office:smarttags"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"State" =
downloadurl=3D"http://www.5iamas-microsoft-com:office:smarttags"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* 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:blue;
	text-decoration:underline;}
p
	{mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman";}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@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=3Dblue>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Hi =
Binu,<o:p></o:p></span></font></p>

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

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

<div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>

<hr size=3D2 width=3D"100%" align=3Dcenter tabindex=3D-1>

</span></font></div>

<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font =
size=3D2
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'> =
<st1:place
w:st=3D"on"><st1:City w:st=3D"on">Binu</st1:City> <st1:State =
w:st=3D"on">TN</st1:State></st1:place>
[mailto:tnbinu@yahoo.co.in] <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Saturday, April 21, =
2007
9:38 PM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> pim@ietf.org<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> [pim] pim-sm =
router
transitions from DR to non-DR</span></font><o:p></o:p></p>

</div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>Hi,<br>
<br>
&nbsp; I have a basic doubt in the pim-sm router transition from DR to =
non-DR.
Let's assume a scenario where a sm router (e.g., RT1) is DR in a LAN and =
it has
multicast route entry and it is trigerring Join messages to RP (it is in =
some
other network) as it has some interesting hosts. If another sm router =
(e.g.RT2)
with higher IP address comes into the LAN of RT1, as per my =
understanding RT2
will become DR and RT1 will become non-DR to that LAN. My doubts =
are,<br>
<br>
1) whether the multicast route entries that are present in RT1 before =
entry
of&nbsp; RT2 will be removed?<br>
<br>
<font color=3Dnavy><span =
style=3D'color:navy'><o:p></o:p></span></font></span></font></p>

<p class=3DMsoNormal><b><i><font size=3D2 color=3Dnavy =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:navy;font-weight:bold;
font-style:italic'>[dsatya] Not necessarily, those entries will changed =
based
on the unicast route change to RP. (due to insertion of =
RT2)<o:p></o:p></span></font></i></b></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><br>
2) Will RT1 stops trigerring Join messages to RP? Or RT1 will be =
trigerring
Join messages for existing entries and RT2 will be trigerring for any =
new
entries?<br>
<br>
<font color=3Dnavy><span =
style=3D'color:navy'><o:p></o:p></span></font></span></font></p>

<p class=3DMsoNormal><b><i><font size=3D2 color=3Dnavy =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:navy;font-weight:bold;
font-style:italic'>[dsatya] RT1 should not trigger Join Msgs to RP and =
RT2
should take up the job.<o:p></o:p></span></font></i></b></p>

<p class=3DMsoNormal><b><i><font size=3D2 color=3Dnavy =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:navy;font-weight:bold;
font-style:italic'>Thanks<o:p></o:p></span></font></i></b></p>

<p class=3DMsoNormal><b><i><font size=3D2 color=3Dnavy =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:navy;font-weight:bold;
font-style:italic'>Satya<o:p></o:p></span></font></i></b></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><br>
Please clear my doubts.<br>
Thank you in advance.<br>
<br>
Regards,<br>
Binu.<o:p></o:p></span></font></p>

<p><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>&nbsp; <o:p></o:p></span></font></p>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>

<hr size=3D1 width=3D"100%" align=3Dcenter>

</span></font></div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>Ahhh...imagining that irresistible &quot;new car&quot; =
smell?<br>
Check out <a
href=3D"http://us.rd.yahoo.com/evt=3D48245/*http:/autos.yahoo.com/new_car=
s.html;_ylc=3DX3oDMTE1YW1jcXJ2BF9TAzk3MTA3MDc2BHNlYwNtYWlsdGFncwRzbGsDbmV=
3LWNhcnM-">new
cars at Yahoo! Autos.</a> <o:p></o:p></span></font></p>

</div>

</body>

</html>

------_=_NextPart_001_01C784DF.ED9F661A--


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

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

--===============1866383548==--




From pim-bounces@ietf.org Mon Apr 23 16:49:56 2007
Return-path: <pim-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hg5Tv-0007wy-1x; Mon, 23 Apr 2007 16:49:55 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hg5Tt-0007wa-Vw
	for pim@ietf.org; Mon, 23 Apr 2007 16:49:54 -0400
Received: from nz-out-0506.google.com ([64.233.162.231])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hg5Tt-00036J-9l
	for pim@ietf.org; Mon, 23 Apr 2007 16:49:53 -0400
Received: by nz-out-0506.google.com with SMTP id z6so1543060nzd
	for <pim@ietf.org>; Mon, 23 Apr 2007 13:49:53 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references;
	b=oST8gr3o2oKDHRx5GDTGAXowJinlBhYpsSNatlyuW1KkjMkDkbQjPa3+DxRGUlwju7A3PCll6xs0NIKzKV3PYMa0AOsvoSA+jzv5gx1+YoH0egeUkvoO2JF7JqQI0Q/WibHCSJCckkYpz9b1o6l5ucD6sJhlSJqRm+MyCjqhdg0=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references;
	b=po/MW+Q/BokqKprZtQHLskkTxRFqHxIlLj6y9iYQjpRj6xgTYE/HofKO/AwS4RKgq7Dt4ppwKITmPQ3rZvvat3/MpqBxgxCm3VQSo9vRNE/8IbHUrYF+dSsCZ0sDAZj0OOJd8b67eHba8bkhUT2PohAIxhFfHvCDeiEMHd4rEv8=
Received: by 10.114.173.15 with SMTP id v15mr2728781wae.1177361392249;
	Mon, 23 Apr 2007 13:49:52 -0700 (PDT)
Received: by 10.114.200.11 with HTTP; Mon, 23 Apr 2007 13:49:52 -0700 (PDT)
Message-ID: <1d413a090704231349w4ad47ccv495a4da87a5c62c8@mail.gmail.com>
Date: Tue, 24 Apr 2007 02:19:52 +0530
From: "Neeraj Prasad" <neeraj.prasad@gmail.com>
To: pim@ietf.org
In-Reply-To: <E1HfeU4-0006OA-M1@megatron.ietf.org>
MIME-Version: 1.0
References: <E1HfeU4-0006OA-M1@megatron.ietf.org>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 5d7a7e767f20255fce80fa0b77fb2433
Subject: [pim] Re: pim Digest, Vol 36, Issue 2
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="===============1989993714=="
Errors-To: pim-bounces@ietf.org

--===============1989993714==
Content-Type: multipart/alternative; 
	boundary="----=_Part_129216_33050560.1177361392181"

------=_Part_129216_33050560.1177361392181
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

1. Interesting host information is stored in all routers whether DR or
non-DR. So at any if a router becomes DR it will send the Join Information
towards RP and the tree will be maintained. So packets will come to host
irrespective who the DR is.

2. It may retain the information or delete it, that is implementation
dependent. The router up the tree will timeout the state, if they do not
receive any JOIN information without taking any action.

Regards,
Neeraj.

On 4/22/07, pim-request@ietf.org <pim-request@ietf.org> wrote:
>
> Send pim mailing list submissions to
>         pim@ietf.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         https://www1.ietf.org/mailman/listinfo/pim
> or, via email, send a message with subject or body 'help' to
>        pim-request@ietf.org
>
> You can reach the person managing the list at
>         pim-owner@ietf.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of pim digest..."
>
>
> Today's Topics:
>
>    1. pim-sm router transitions from DR to non-DR (Binu TN)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Sat, 21 Apr 2007 09:07:46 -0700 (PDT)
> From: Binu TN <tnbinu@yahoo.co.in>
> Subject: [pim] pim-sm router transitions from DR to non-DR
> To: pim@ietf.org
> Message-ID: <223775.16676.qm@web8804.mail.in.yahoo.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Hi,
>
>   I have a basic doubt in the pim-sm router transition from DR to non-DR.
> Let's assume a scenario where a sm router (e.g., RT1) is DR in a LAN and
> it has multicast route entry and it is trigerring Join messages to RP (it is
> in some other network) as it has some interesting hosts. If another sm
> router (e.g.RT2) with higher IP address comes into the LAN of RT1, as per
> my understanding RT2 will become DR and RT1 will become non-DR to that LAN.
> My doubts are,
>
> 1) whether the multicast route entries that are present in RT1 before
> entry of  RT2 will be removed?
>
> 2) Will RT1 stops trigerring Join messages to RP? Or RT1 will be
> trigerring Join messages for existing entries and RT2 will be trigerring for
> any new entries?
>
> Please clear my doubts.
> Thank you in advance.
>
> Regards,
> Binu.
>
>
> ---------------------------------
> Ahhh...imagining that irresistible "new car" smell?
> Check outnew cars at Yahoo! Autos.
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> http://www1.ietf.org/pipermail/pim/attachments/20070421/39ab31a5/attachment.html
>
> ------------------------------
>
> _______________________________________________
> pim mailing list
> pim@ietf.org
> https://www1.ietf.org/mailman/listinfo/pim
>
>
> End of pim Digest, Vol 36, Issue 2
> **********************************
>



-- 
Thanks and Regards,
Neeraj Prasad

------=_Part_129216_33050560.1177361392181
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

1. Interesting host information is stored in all routers whether DR or non-DR. So at any if a router becomes DR it will send the Join Information towards RP and the tree will be maintained. So packets will come to host irrespective who the DR is.
<br><br>2. It may retain the information or delete it, that is implementation dependent. The router up the tree will timeout the state, if they do not receive any JOIN information without taking any action.<br><br>Regards,
<br>Neeraj.<br><br><div><span class="gmail_quote">On 4/22/07, <b class="gmail_sendername"><a href="mailto:pim-request@ietf.org">pim-request@ietf.org</a></b> &lt;<a href="mailto:pim-request@ietf.org">pim-request@ietf.org</a>
&gt; wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Send pim mailing list submissions to<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="mailto:pim@ietf.org">
pim@ietf.org</a><br><br>To subscribe or unsubscribe via the World Wide Web, visit<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="https://www1.ietf.org/mailman/listinfo/pim">https://www1.ietf.org/mailman/listinfo/pim</a><br>or, via email, send a message with subject or body &#39;help&#39; to
<br>&nbsp; &nbsp;&nbsp;&nbsp;&nbsp; <a href="mailto:pim-request@ietf.org">pim-request@ietf.org</a><br><br>You can reach the person managing the list at<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="mailto:pim-owner@ietf.org">pim-owner@ietf.org</a><br><br>When replying, please edit your Subject line so it is more specific
<br>than &quot;Re: Contents of pim digest...&quot;<br><br><br>Today&#39;s Topics:<br><br>&nbsp;&nbsp; 1. pim-sm router transitions from DR to non-DR (Binu TN)<br><br><br>----------------------------------------------------------------------
<br><br>Message: 1<br>Date: Sat, 21 Apr 2007 09:07:46 -0700 (PDT)<br>From: Binu TN &lt;<a href="mailto:tnbinu@yahoo.co.in">tnbinu@yahoo.co.in</a>&gt;<br>Subject: [pim] pim-sm router transitions from DR to non-DR<br>To: <a href="mailto:pim@ietf.org">
pim@ietf.org</a><br>Message-ID: &lt;<a href="mailto:223775.16676.qm@web8804.mail.in.yahoo.com">223775.16676.qm@web8804.mail.in.yahoo.com</a>&gt;<br>Content-Type: text/plain; charset=&quot;iso-8859-1&quot;<br><br>Hi,<br><br>
&nbsp;&nbsp;I have a basic doubt in the pim-sm router transition from DR to non-DR. Let&#39;s assume a scenario where a sm router (e.g., RT1) is DR in a LAN and it has multicast route entry and it is trigerring Join messages to RP (it is in some other network) as it has some interesting hosts. If another sm router (
e.g.RT2) with higher IP address comes into the LAN of RT1, as per my understanding RT2 will become DR and RT1 will become non-DR to that LAN. My doubts are,<br><br>1) whether the multicast route entries that are present in RT1 before entry of&nbsp;&nbsp;RT2 will be removed?
<br><br>2) Will RT1 stops trigerring Join messages to RP? Or RT1 will be trigerring Join messages for existing entries and RT2 will be trigerring for any new entries?<br><br>Please clear my doubts.<br>Thank you in advance.
<br><br>Regards,<br>Binu.<br><br><br>---------------------------------<br>Ahhh...imagining that irresistible &quot;new car&quot; smell?<br> Check outnew cars at Yahoo! Autos.<br>-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>URL: <a href="http://www1.ietf.org/pipermail/pim/attachments/20070421/39ab31a5/attachment.html">http://www1.ietf.org/pipermail/pim/attachments/20070421/39ab31a5/attachment.html</a><br>
<br>------------------------------<br><br>_______________________________________________<br>pim mailing list<br><a href="mailto:pim@ietf.org">pim@ietf.org</a><br><a href="https://www1.ietf.org/mailman/listinfo/pim">https://www1.ietf.org/mailman/listinfo/pim
</a><br><br><br>End of pim Digest, Vol 36, Issue 2<br>**********************************<br></blockquote></div><br><br clear="all"><br>-- <br>Thanks and Regards,<br>Neeraj Prasad

------=_Part_129216_33050560.1177361392181--


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

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

--===============1989993714==--




From osanai789@yahoo.com.cn Mon Apr 23 22:20:28 2007
Return-path: <osanai789@yahoo.com.cn>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HgAdo-0006ep-BQ
	for pim-archive@lists.ietf.org; Mon, 23 Apr 2007 22:20:28 -0400
Received: from [122.43.127.43] (helo=mail)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HgAdm-0007b2-SB
	for pim-archive@lists.ietf.org; Mon, 23 Apr 2007 22:20:28 -0400
Received: by mail (Postfix, from userid 48)
	id 6ADD44CE3FF; Mon, 23 Apr 2007 12:56:50 +0900 (KST)
To: pim-archive@lists.ietf.org
Subject: =?ISO-2022-JP?B?kIKC6oK9k/uBQY2VgqKT+5fWgUGDdYOIg3WDiILMibqUvJBngUmCsYLxgsiPbo+XgqqNRIKrgsiV+4LNgUk==?=
From: <osanai789@yahoo.com.cn>
Resent-Sender: osanai789@yahoo.com.cn
Message-ID: <20070423125650.17508@yahoo.com.cn>
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-2022-JP"
Content-Transfer-Encoding: 7bit
Resent-Message-Id: <20070423062240.6ADD44CE3FF@mail>
Resent-Date: Mon, 23 Apr 2007 12:56:50 +0900 (KST)
Resent-From: osanai789@yahoo.com.cn (Apache)
X-Spam-Score: 3.2 (+++)
X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b


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

当サイトは40代〜50代の肉体関係を求めている人妻・熟女

が集まる日本最大の肉体関係コミュニティーサイトです。

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



《ご利用に関してのご注意》-------------------------------



�T　ご利用は男女共に40歳以上の方のみとさせて頂きます。



�U　男女共にお相手に要求する事は肉体関係のみです。



�V　ホテル代に関してはお互いで決めて下さい。





《ご利用方法について》-----------------------------------



�T　ご希望の地域・メールアドレス・パスワードを設定して頂きます。



�U　次に簡単な自己PRを設定して頂きます。



�V　肉体関係を希望するお相手を検索して頂きます。



�W　ご利用されている人妻・熟女さんは全て自己PR内に携帯番号又は

　　直アドレスが表示されておりますのでその時点で直接ご連絡を

　　して頂いても結構ですし、サイト内からメールにて連絡を取る

　　事も可能ですのでお好きな連絡方法で交渉して下さい。



【注意】自己PR内に連絡先の表示が無い人妻・熟女さんは

　　　　交渉が成立し肉体関係中ですので連絡先の表示が

　　　　復活後、再度交渉をお願い致します。



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

●本日、熟れた人妻・熟女と肉体関係を希望される40歳以上の男性は

　http://cjbjj.com:112/ddd/40-navi-sp/



●本日、火照った体を満たして欲しい40歳以上の女性は

　http://cjbjj.com:112/ddd/40-navi-sp/

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

★待合わせの場所をリアルタイムでやり取り確認されたい方は

　モバイル（携帯電話）での設定をオススメ致します。

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







From pim-bounces@ietf.org Tue Apr 24 07:19:08 2007
Return-path: <pim-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HgJ32-0000Sp-Av; Tue, 24 Apr 2007 07:19:04 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HgJ31-0000Sk-J2
	for pim@ietf.org; Tue, 24 Apr 2007 07:19:03 -0400
Received: from szxga04-in.huawei.com ([61.144.161.7])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HgJ2x-0005Bt-Ul
	for pim@ietf.org; Tue, 24 Apr 2007 07:19:03 -0400
Received: from huawei.com (szxga04-in [172.24.2.12])
	by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0JH0003BR22CW9@szxga04-in.huawei.com> for
	pim@ietf.org; Tue, 24 Apr 2007 19:18:12 +0800 (CST)
Received: from szxmp02-in.huawei.com ([172.24.2.32])
	by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0JH00084X2286D@szxga04-in.huawei.com> for
	pim@ietf.org; Tue, 24 Apr 2007 19:18:12 +0800 (CST)
Received: from 172.24.1.24 (EHLO huawei.com) ([172.24.1.24])
	by szxmp02-in.huawei.com (MOS 3.8.4-GA FastPath queued)
	with ESMTP id AHL16961; Wed, 25 Apr 2007 19:17:40 +0800 (CST)
Received: from s33630C ([10.111.68.36])
	by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTPA id <0JH0004QU223LQ@szxml04-in.huawei.com> for
	pim@ietf.org; Tue, 24 Apr 2007 19:18:08 +0800 (CST)
Date: Tue, 24 Apr 2007 19:18:03 +0800
From: Su Haiyang <suhaiyang@huawei.com>
In-reply-to: <1d413a090704231349w4ad47ccv495a4da87a5c62c8@mail.gmail.com>
To: 'Neeraj Prasad' <neeraj.prasad@gmail.com>, pim@ietf.org
Message-id: <001b01c78662$3a274e80$df010264@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Mailer: Microsoft Office Outlook 11
Thread-index: AceF6Pc5rlteph6ZQeORroTyTsNMqgAdiGEQ
X-Junkmail-IP-Whitelist: YES (by domain ip whitelist at szxmp02-in.huawei.com)
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 94ddbad0060c343c23e74ba9bbebbccf
Cc: pim@ietf.org
Subject: [pim] Strongly recommend that there should be some transition
 mechanism between old DR and new DR
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="===============0561398735=="
Errors-To: pim-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0561398735==
Content-type: multipart/alternative;
	boundary="Boundary_(ID_IMAMKLLIq2BIeO6dfQHEww)"

This is a multi-part message in MIME format.

--Boundary_(ID_IMAMKLLIq2BIeO6dfQHEww)
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT

Dear All,

   I strongly recommend that there should be some transition mechanism
between old DR and new DR.

The reason is that even though the lately booted DR keep the GMP join group
membership and already learned source,

The new DR still need time to reestablish SPT or RPT tree depending whether
the group is SM or SSM. Considering generally deployed PIM scenario, there
will be two last-hop routers connecting the clouds of hosts or layer2
switches. If the link between DR and backup DR is unstable, there will be
data loss and vibration of PIM state maintained on all the routers.

 

You may say that static group join may be configured at last-hop DR. But it
take some time for new DR to updated all the downstreams if there are more
than 10K level of groups.

 

So I strongly recommend that transition mechanism should be considered on
the new PIM draft.

One of my suggestions is that, a new timer DR switch delay timer should be
introduced. Before this timer expires,

Old DR won't give up the DR responsibility. To avoid the duplicated data, a
unique forwarder is elected between Old DR and New DR

by using assert mechanism.

 

Request for your comments

Best regards

Su Haiyang

 

  _____  

From: Neeraj Prasad [mailto:neeraj.prasad@gmail.com] 
Sent: Tuesday, April 24, 2007 4:50 AM
To: pim@ietf.org
Subject: [pim] Re: pim Digest, Vol 36, Issue 2

 

1. Interesting host information is stored in all routers whether DR or
non-DR. So at any if a router becomes DR it will send the Join Information
towards RP and the tree will be maintained. So packets will come to host
irrespective who the DR is. 

2. It may retain the information or delete it, that is implementation
dependent. The router up the tree will timeout the state, if they do not
receive any JOIN information without taking any action.

Regards, 
Neeraj.

On 4/22/07, pim-request@ietf.org <pim-request@ietf.org > wrote:

Send pim mailing list submissions to
         <mailto:pim@ietf.org>  pim@ietf.org

To subscribe or unsubscribe via the World Wide Web, visit
        https://www1.ietf.org/mailman/listinfo/pim
or, via email, send a message with subject or body 'help' to 
       pim-request@ietf.org

You can reach the person managing the list at
        pim-owner@ietf.org

When replying, please edit your Subject line so it is more specific 
than "Re: Contents of pim digest..."


Today's Topics:

   1. pim-sm router transitions from DR to non-DR (Binu TN)


---------------------------------------------------------------------- 

Message: 1
Date: Sat, 21 Apr 2007 09:07:46 -0700 (PDT)
From: Binu TN <tnbinu@yahoo.co.in>
Subject: [pim] pim-sm router transitions from DR to non-DR
To: pim@ietf.org
Message-ID: <223775.16676.qm@web8804.mail.in.yahoo.com>
Content-Type: text/plain; charset="iso-8859-1"

Hi,

  I have a basic doubt in the pim-sm router transition from DR to non-DR.
Let's assume a scenario where a sm router (e.g., RT1) is DR in a LAN and it
has multicast route entry and it is trigerring Join messages to RP (it is in
some other network) as it has some interesting hosts. If another sm router (
e.g.RT2) with higher IP address comes into the LAN of RT1, as per my
understanding RT2 will become DR and RT1 will become non-DR to that LAN. My
doubts are,

1) whether the multicast route entries that are present in RT1 before entry
of  RT2 will be removed? 

2) Will RT1 stops trigerring Join messages to RP? Or RT1 will be trigerring
Join messages for existing entries and RT2 will be trigerring for any new
entries?

Please clear my doubts.
Thank you in advance. 

Regards,
Binu.


---------------------------------
Ahhh...imagining that irresistible "new car" smell?
Check outnew cars at Yahoo! Autos.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://www1.ietf.org/pipermail/pim/attachments/20070421/39ab31a5/attachment.
html

------------------------------

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


End of pim Digest, Vol 36, Issue 2
**********************************




-- 
Thanks and Regards,
Neeraj Prasad 


--Boundary_(ID_IMAMKLLIq2BIeO6dfQHEww)
Content-type: text/html; charset=us-ascii
Content-transfer-encoding: 7BIT

<html>

<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="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:Dotum;
	panose-1:2 11 6 0 0 1 1 1 1 1;}
@font-face
	{font-family:SimHei;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"MS UI Gothic";
	panose-1:2 11 6 0 7 2 5 8 2 4;}
@font-face
	{font-family:DotumChe;
	panose-1:2 11 6 9 0 1 1 1 1 1;}
@font-face
	{font-family:KaiTi_GB2312;
	panose-1:2 1 6 9 3 1 1 1 1 1;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"\@Dotum";
	panose-1:2 11 6 0 0 1 1 1 1 1;}
@font-face
	{font-family:"\@MS UI Gothic";
	panose-1:2 11 6 0 7 2 5 8 2 4;}
@font-face
	{font-family:"\@DotumChe";
	panose-1:2 11 6 9 0 1 1 1 1 1;}
@font-face
	{font-family:KaiTi_GB2312;
	panose-1:2 1 6 9 3 1 1 1 1 1;}
@font-face
	{font-family:SimHei;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
h1
	{margin-top:12.0pt;
	margin-right:0cm;
	margin-bottom:12.0pt;
	margin-left:21.6pt;
	text-align:justify;
	text-justify:inter-ideograph;
	text-indent:-21.6pt;
	page-break-after:avoid;
	font-size:16.0pt;
	font-family:Arial;}
h2
	{margin-top:12.0pt;
	margin-right:0cm;
	margin-bottom:12.0pt;
	margin-left:28.8pt;
	text-align:justify;
	text-justify:inter-ideograph;
	text-indent:-28.8pt;
	page-break-after:avoid;
	font-size:12.0pt;
	font-family:Arial;
	font-weight:normal;}
h3
	{margin-top:13.0pt;
	margin-right:0cm;
	margin-bottom:13.0pt;
	margin-left:36.0pt;
	text-align:justify;
	text-justify:inter-ideograph;
	text-indent:-36.0pt;
	line-height:173%;
	page-break-after:avoid;
	font-size:12.0pt;
	font-family:"Times New Roman";
	font-weight:normal;}
p.MsoHeader, li.MsoHeader, div.MsoHeader
	{margin:0cm;
	margin-bottom:.0001pt;
	text-align:justify;
	text-justify:inter-ideograph;
	layout-grid-mode:char;
	font-size:9.0pt;
	font-family:Arial;}
p.MsoFooter, li.MsoFooter, div.MsoFooter
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:9.0pt;
	font-family:Arial;}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:blue;
	text-decoration:underline;}
p.a, li.a, div.a
	{margin-top:12.0pt;
	margin-right:0cm;
	margin-bottom:0cm;
	margin-left:54.45pt;
	margin-bottom:.0001pt;
	text-align:center;
	text-indent:-18.45pt;
	font-size:9.0pt;
	font-family:Arial;}
p.a0, li.a0, div.a0
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Arial;}
p.a1, li.a1, div.a1
	{margin:0cm;
	margin-bottom:.0001pt;
	text-align:center;
	font-size:10.5pt;
	font-family:Arial;
	font-weight:bold;}
p.a2, li.a2, div.a2
	{margin-top:0cm;
	margin-right:0cm;
	margin-bottom:12.0pt;
	margin-left:54.45pt;
	text-align:center;
	text-indent:-18.45pt;
	font-size:9.0pt;
	font-family:Arial;}
p.a3, li.a3, div.a3
	{margin-top:4.0pt;
	margin-right:0cm;
	margin-bottom:4.0pt;
	margin-left:0cm;
	text-align:center;
	line-height:150%;
	page-break-after:avoid;
	text-autospace:none;
	font-size:10.5pt;
	font-family:"Times New Roman";
	layout-grid-mode:line;}
p.a4, li.a4, div.a4
	{margin-top:15.0pt;
	margin-right:0cm;
	margin-bottom:15.0pt;
	margin-left:0cm;
	text-align:center;
	font-size:18.0pt;
	font-family:Arial;}
p.a5, li.a5, div.a5
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
p.a6, li.a6, div.a6
	{margin:0cm;
	margin-bottom:.0001pt;
	text-align:justify;
	text-justify:inter-ideograph;
	border:none;
	padding:0cm;
	font-size:9.0pt;
	font-family:Arial;}
p.a7, li.a7, div.a7
	{margin:0cm;
	margin-bottom:.0001pt;
	text-align:justify;
	text-justify:inter-ideograph;
	text-indent:18.0pt;
	border:none;
	padding:0cm;
	font-size:9.0pt;
	font-family:Arial;}
p.a8, li.a8, div.a8
	{margin:0cm;
	margin-bottom:.0001pt;
	text-indent:21.0pt;
	font-size:12.0pt;
	font-family:Arial;
	color:blue;
	font-style:italic;}
span.a9
	{font-family:SimSun;
	color:black;
	font-weight:bold;}
span.aa
	{font-family:SimSun;
	color:black;
	font-weight:bold;}
span.EmailStyle34
	{font-family:Arial;
	color:navy;}
 /* Page Definitions */
 @page Section1
	{size:595.3pt 841.9pt;
	margin:65.6pt 90.0pt 72.0pt 90.0pt;}
div.Section1
	{page:Section1;}
 /* List Definitions */
 ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
-->
</style>

</head>

<body lang=ZH-CN link=blue vlink=blue>

<div class=Section1>

<p class=MsoNormal><font size=3 color=navy face=Arial><span lang=EN-US
style='font-size:12.0pt;font-family:Arial;color:navy'>Dear All,</span></font></p>

<p class=MsoNormal><font size=3 color=navy face=Arial><span lang=EN-US
style='font-size:12.0pt;font-family:Arial;color:navy'>&nbsp;&nbsp; I strongly recommend
that there should be some transition mechanism between old DR and new DR.</span></font></p>

<p class=MsoNormal><font size=3 color=navy face=Arial><span lang=EN-US
style='font-size:12.0pt;font-family:Arial;color:navy'>The reason is that even though
the lately booted DR keep the GMP join group membership and already learned source,</span></font></p>

<p class=MsoNormal><font size=3 color=navy face=Arial><span lang=EN-US
style='font-size:12.0pt;font-family:Arial;color:navy'>The new DR still need time
to reestablish SPT or RPT tree depending whether the group is SM or SSM. Considering
generally deployed PIM scenario, there will be two last-hop routers connecting the
clouds of hosts or layer2 switches. If the link between DR and backup DR is unstable,
there will be data loss and vibration of PIM state maintained on all the routers.</span></font></p>

<p class=MsoNormal><font size=3 color=navy face=Arial><span lang=EN-US
style='font-size:12.0pt;font-family:Arial;color:navy'>&nbsp;</span></font></p>

<p class=MsoNormal><font size=3 color=navy face=Arial><span lang=EN-US
style='font-size:12.0pt;font-family:Arial;color:navy'>You may say that static group
join may be configured at last-hop DR. But it take some time for new DR to updated
all the downstreams if there are more than 10K level of groups.</span></font></p>

<p class=MsoNormal><font size=3 color=navy face=Arial><span lang=EN-US
style='font-size:12.0pt;font-family:Arial;color:navy'>&nbsp;</span></font></p>

<p class=MsoNormal><font size=3 color=navy face=Arial><span lang=EN-US
style='font-size:12.0pt;font-family:Arial;color:navy'>So I strongly recommend that
transition mechanism should be considered on the new PIM draft.</span></font></p>

<p class=MsoNormal><font size=3 color=navy face=Arial><span lang=EN-US
style='font-size:12.0pt;font-family:Arial;color:navy'>One of my suggestions is that,
a new timer DR switch delay timer should be introduced. Before this timer expires,</span></font></p>

<p class=MsoNormal><font size=3 color=navy face=Arial><span lang=EN-US
style='font-size:12.0pt;font-family:Arial;color:navy'>Old DR won&#8217;t give up
the DR responsibility. To avoid the duplicated data, a unique forwarder is elected
between Old DR and New DR</span></font></p>

<p class=MsoNormal><font size=3 color=navy face=Arial><span lang=EN-US
style='font-size:12.0pt;font-family:Arial;color:navy'>by using assert mechanism.</span></font></p>

<p class=MsoNormal><font size=3 color=navy face=Arial><span lang=EN-US
style='font-size:12.0pt;font-family:Arial;color:navy'>&nbsp;</span></font></p>

<p class=MsoNormal><font size=3 color=navy face=Arial><span lang=EN-US
style='font-size:12.0pt;font-family:Arial;color:navy'>Request for your comments</span></font></p>

<p class=MsoNormal><font size=3 color=navy face=Arial><span lang=EN-US
style='font-size:12.0pt;font-family:Arial;color:navy'>Best regards</span></font></p>

<p class=MsoNormal><font size=3 color=navy face=Arial><span lang=EN-US
style='font-size:12.0pt;font-family:Arial;color:navy'>Su Haiyang</span></font></p>

<p class=MsoNormal><font size=1 color=navy face=Arial><span lang=EN-US
style='font-size:9.0pt;font-family:Arial;color:navy'>&nbsp;</span></font></p>

<div>

<div class=MsoNormal align=center style='text-align:center'><font size=3
face="Times New Roman"><span lang=EN-US style='font-size:12.0pt'>

<hr size=3 width="100%" align=center tabindex=-1>

</span></font></div>

<p class=MsoNormal><b><font size=2 face=Tahoma><span lang=EN-US
style='font-size:10.0pt;font-family:Tahoma;font-weight:bold'>From:</span></font></b><font
size=2 face=Tahoma><span lang=EN-US style='font-size:10.0pt;font-family:Tahoma'>
Neeraj Prasad [mailto:neeraj.prasad@gmail.com] <br>
<b><span style='font-weight:bold'>Sent:</span></b> Tuesday, April 24, 2007 4:50
AM<br>
<b><span style='font-weight:bold'>To:</span></b> pim@ietf.org<br>
<b><span style='font-weight:bold'>Subject:</span></b> [pim] Re: pim Digest, Vol
36, Issue 2</span></font></p>

</div>

<p class=MsoNormal><font size=3 face="Times New Roman"><span lang=EN-US
style='font-size:12.0pt'>&nbsp;</span></font></p>

<p class=MsoNormal style='margin-bottom:12.0pt'><font size=3
face="Times New Roman"><span lang=EN-US style='font-size:12.0pt'>1. Interesting
host information is stored in all routers whether DR or non-DR. So at any if a
router becomes DR it will send the Join Information towards RP and the tree
will be maintained. So packets will come to host irrespective who the DR is. <br>
<br>
2. It may retain the information or delete it, that is implementation
dependent. The router up the tree will timeout the state, if they do not
receive any JOIN information without taking any action.<br>
<br>
Regards, <br>
Neeraj.</span></font></p>

<div>

<p class=MsoNormal><span class=gmailquote><font size=3 face="Times New Roman"><span
lang=EN-US style='font-size:12.0pt'>On 4/22/07, <b><span style='font-weight:bold'><a href="mailto:pim-request@ietf.org">pim-request@ietf.org</a></span></b>
&lt;<a href="mailto:pim-request@ietf.org">pim-request@ietf.org</a> &gt; wrote:</span></font></span></p>

<p class=MsoNormal><font size=3 face="Times New Roman"><span lang=EN-US
style='font-size:12.0pt'>Send pim mailing list submissions to<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="mailto:pim@ietf.org">
pim@ietf.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a
href="https://www1.ietf.org/mailman/listinfo/pim">https://www1.ietf.org/mailman/listinfo/pim</a><br>
or, via email, send a message with subject or body 'help' to <br>
&nbsp; &nbsp;&nbsp;&nbsp;&nbsp; <a href="mailto:pim-request@ietf.org">pim-request@ietf.org</a><br>
<br>
You can reach the person managing the list at<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a
href="mailto:pim-owner@ietf.org">pim-owner@ietf.org</a><br>
<br>
When replying, please edit your Subject line so it is more specific <br>
than &quot;Re: Contents of pim digest...&quot;<br>
<br>
<br>
Today's Topics:<br>
<br>
&nbsp;&nbsp; 1. pim-sm router transitions from DR to non-DR (Binu TN)<br>
<br>
<br>
---------------------------------------------------------------------- <br>
<br>
Message: 1<br>
Date: Sat, 21 Apr 2007 09:07:46 -0700 (PDT)<br>
From: Binu TN &lt;<a href="mailto:tnbinu@yahoo.co.in">tnbinu@yahoo.co.in</a>&gt;<br>
Subject: [pim] pim-sm router transitions from DR to non-DR<br>
To: <a href="mailto:pim@ietf.org">pim@ietf.org</a><br>
Message-ID: &lt;<a href="mailto:223775.16676.qm@web8804.mail.in.yahoo.com">223775.16676.qm@web8804.mail.in.yahoo.com</a>&gt;<br>
Content-Type: text/plain; charset=&quot;iso-8859-1&quot;<br>
<br>
Hi,<br>
<br>
&nbsp;&nbsp;I have a basic doubt in the pim-sm router transition from DR to
non-DR. Let's assume a scenario where a sm router (e.g., RT1) is DR in a LAN
and it has multicast route entry and it is trigerring Join messages to RP (it
is in some other network) as it has some interesting hosts. If another sm
router ( e.g.RT2) with higher IP address comes into the LAN of RT1, as per my
understanding RT2 will become DR and RT1 will become non-DR to that LAN. My
doubts are,<br>
<br>
1) whether the multicast route entries that are present in RT1 before entry
of&nbsp;&nbsp;RT2 will be removed? <br>
<br>
2) Will RT1 stops trigerring Join messages to RP? Or RT1 will be trigerring
Join messages for existing entries and RT2 will be trigerring for any new
entries?<br>
<br>
Please clear my doubts.<br>
Thank you in advance. <br>
<br>
Regards,<br>
Binu.<br>
<br>
<br>
---------------------------------<br>
Ahhh...imagining that irresistible &quot;new car&quot; smell?<br>
Check outnew cars at Yahoo! Autos.<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <a
href="http://www1.ietf.org/pipermail/pim/attachments/20070421/39ab31a5/attachment.html">http://www1.ietf.org/pipermail/pim/attachments/20070421/39ab31a5/attachment.html</a><br>
<br>
------------------------------<br>
<br>
_______________________________________________<br>
pim mailing list<br>
<a href="mailto:pim@ietf.org">pim@ietf.org</a><br>
<a href="https://www1.ietf.org/mailman/listinfo/pim">https://www1.ietf.org/mailman/listinfo/pim
</a><br>
<br>
<br>
End of pim Digest, Vol 36, Issue 2<br>
**********************************</span></font></p>

</div>

<p class=MsoNormal><font size=3 face="Times New Roman"><span lang=EN-US
style='font-size:12.0pt'><br>
<br clear=all>
<br>
-- <br>
Thanks and Regards,<br>
Neeraj Prasad </span></font></p>

</div>

</body>

</html>

--Boundary_(ID_IMAMKLLIq2BIeO6dfQHEww)--


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

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

--===============0561398735==--




From pim-bounces@ietf.org Tue Apr 24 07:23:07 2007
Return-path: <pim-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HgJ6x-0003X2-Aj; Tue, 24 Apr 2007 07:23:07 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HgJ6v-0003Wv-LP
	for pim@ietf.org; Tue, 24 Apr 2007 07:23:05 -0400
Received: from szxga01-in.huawei.com ([61.144.161.53])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HgJ6s-0007Uq-5d
	for pim@ietf.org; Tue, 24 Apr 2007 07:23:05 -0400
Received: from huawei.com (szxga01-in [172.24.2.3])
	by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTP id <0JH00099Z2954O@szxga01-in.huawei.com> for
	pim@ietf.org; Tue, 24 Apr 2007 19:22:17 +0800 (CST)
Received: from huawei.com ([172.24.1.18])
	by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTP id <0JH000JKH293KC@szxga01-in.huawei.com> for
	pim@ietf.org; Tue, 24 Apr 2007 19:22:17 +0800 (CST)
Received: from s33630C ([10.111.68.36])
	by szxml03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTPA id <0JH0001FL290N4@szxml03-in.huawei.com> for
	pim@ietf.org; Tue, 24 Apr 2007 19:22:15 +0800 (CST)
Date: Tue, 24 Apr 2007 19:22:12 +0800
From: Su Haiyang <suhaiyang@huawei.com>
Subject: RE: [pim] IETF68 pimwg mtg minutes
In-reply-to: <Pine.GSO.4.63.0704191501400.27909@irp-view7.cisco.com>
To: 'Mike McBride' <mmcbride@cisco.com>
Message-id: <002001c78662$ce1b96a0$df010264@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Thread-index: AceCzyOSpaP2M0FxSjW1409vPc9QIQDk139A
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ccfb4541e989aa743998098cd315d0fd
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>
Errors-To: pim-bounces@ietf.org

Dear All,
 Where can I find any progress about periodic state refresh reduction on SM
draft?
Thanks
Su haiyang 

-----Original Message-----
From: Mike McBride [mailto:mmcbride@cisco.com] 
Sent: Friday, April 20, 2007 6:05 AM
To: pim@ietf.org
Subject: [pim] IETF68 pimwg mtg minutes

pimwg meeting minutes
Prague, Czech Republic
Tuesday, March 20th, 2007

Created the summarized notes from the pimwg audio archive which can be 
listened to in its entirety at: 
http://limestone.uoregon.edu/ftp/pub/videolab/media/ietf68/ietf68-ch6-tue-pm
.mp3

Mike: Welcome, agenda bashing

Bill: AD for few more hours. Both bidir and pim mib approved by iesg in last

few weeks. Getting stuff off books that have been languishing. BSR is almost

complete as well.

Mike: Thanks to Bill for all his hard work as AD

BSR Draft:

Alex: Received few comments from last rev of bsr draft from Eric Gray and
Sandy 
Murphy. Will talk to Sandy this week, few issues she came up with, will take

to list. Lars Eggert: are you allowed to say document updates 2362? It has 
been obsoleted by new pimsm spec which doesn't contain the bsr. Alex thinks
its 
correct that we say we obsolete 2362.

Bill: Those relationships don't have the meanings we'd like them to. Since
its 
obsolete it may be that it just doesn't matter, you should take out obsolete

comments, just pretend this is new.

Alex: Eric Gray had valid issues with bsr state machine and I will update
draft 
to clarify things a bit. Describe the no info state better.

Alex: Eric has issue that scopes could expire before bootstrap timer expires

unless timers were constrained in certain way. Have a constraint that its
not 
allowed to happen. State machine is correct. Scopes on timer always has to
be 
higher than bootstrap timer. Scopes will expire a little bit later than if 
implemented then with default timers specified in current spec.

Alex: There is a timer assoc with group to rp mapping and when that timer 
expires that mapping is deleted. its not explicitely mentioned anywhere. It 
could be added to a section that describes how the rp set is received and
used 
by a router.

Alex: Would like to published one more revision then get draft approved.

RPF vector and join attribute drafts:

Arjen: join attributes passed last call, one last Stig comment about adding 
IANA registry then off to iesg. rpf vector has a few more improvements and 
corrections then we'll go to last call.

last hop threats draft:

Pekka:recap in hopes to generate feedback. It identifies last hop 
vulnerabilities and attacks that can be done with vulnerabilities. Last hop 
between router and host is the concern. Could send unauthorized register 
message to RPs that may contain spoofed messages and create nasty state.
Host 
may also become unauthorized neighbor. Routers may accept unauthorized 
messages from neighbors. Unauthorized node could be elected as DR.
Mitigation 
methods: pim passive mode (able to receive and send multicast but router 
doesn't send hellos on that interface or process pim messages). Possible
when 
you have a single router on a link. Also could use IPsec on a link. If just 
one router also possible to filter out all pim messages. When multiple valid

pim routers on a link, you'll have to use IPsec.

Not much changed since last rev except minor editorial updates. pim spec has

been published so this can now proceed. pim passive has been implemented in 
Junos. Should we go for wglc or have people review doc.

Derek: could you also have pim filter which filters on sources.

Pekka: yes, but you could also spoof the source. The host could send source 
messages with router. So that might not be good enough.

Derek: we have the capability to filter on source but should also combine
that 
with lockdown of addresses.

Dino: How about having a switch between host and routers. If a switch is 
connected to a particular host port don't accept pim messages on that port,
so 
router never sees the pim message.

Pekka: yes, that could also be mentioned in the doc.

Pekka: How to procede with the doc?

Mike: revise the doc based upon these comments then we'll issue wglc.

Mike: authors for linklocal draft not able to attend but they are activity 
working on it and have been seeking and receiving advice from msec.

Mike: rechartering/milestones discussion. sent a proposed new charter, all 
comments have been incorporated in text of new charter and milestones. Will 
email ADS and secretariat in a week if I don't hear anything.

Mike: One milestone worth discussion is reducing the messaging of pim. We
did 
have a design team to look into ways to reduce pim messaging. at that time
it 
appeared that a j/p ack proposal was most agreed upon but since then the 
urgency of it has dissipated and it was thought that it was a bit too
complex. 
There have been other thoughts on how to handle this. We have had plenty of 
requests to come up with some sort of solution from operators and l3vpn.

Maria: Nothing has been completed on this in pimwg?

Mike:  correct

Maria: Something has to be done in this area, particularly in context of
2547 
multicast. refresh reduction is critical for scalability purposes. Dont see 
the problem yet for scalability of mvpns but it may show up and need some
sort 
of solution. Receiver explicit tracking needs to be a part of the solution
for 
aggregation purposes of trees in the core. It has to scale.

Mike: how does wg want to proceed to solve this?

Dino: Do people think this is important for non mvpn environments

Maria: yes. definitely need in core for vpn context, but also needed towards

the CE. native ip multicast needs it. biggest impact is in the core.

Dino: let me restate: do you think solution is necessary for a non pe box.

Greg: Marias explanation is still mvpn context. PE to CE is still mvpn 
environment. The solution would have to be on both ends of the PE.

Dino: If there is too much traffic on the PE-CE link, there is probably too 
much state on one hop downstream as well. Do your customers have a concern?

Maria: not yey. They do have the choice of bidir to reduce state.

Maria: Only PE, which has many interfaces, is of most importance.

Mike: We have a milestone to get something submitted by end of year. If that

doesn't happen, we'll probably need to create a design team.

Mike: drafts have been submitted (not in time to discuss for ietf) to offer 
other enhancements to pim which fit into our new charter.

Pekka: One clarification needed in the charter which says provide a "more 
reliable" solution. Propose to whom and by whom.

Mike: I'll change "propose" to "submit".

_______________________________________________
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 Apr 24 15:59:35 2007
Return-path: <pim-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HgRA0-0000Mu-4e; Tue, 24 Apr 2007 15:58:48 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HgR9y-0000Mb-Lk
	for pim@ietf.org; Tue, 24 Apr 2007 15:58:46 -0400
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HgR9w-0006Wr-Ta
	for pim@ietf.org; Tue, 24 Apr 2007 15:58:46 -0400
Received: from sj-dkim-7.cisco.com ([171.68.10.88])
	by sj-iport-5.cisco.com with ESMTP; 24 Apr 2007 12:58:44 -0700
X-IronPort-AV: i="4.14,448,1170662400"; 
	d="scan'208"; a="415183654:sNHT3363698994"
Received: from sj-core-3.cisco.com (sj-core-3.cisco.com [171.68.223.137])
	by sj-dkim-7.cisco.com (8.12.11/8.12.11) with ESMTP id l3OJwhrJ019508; 
	Tue, 24 Apr 2007 12:58:43 -0700
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com
	[171.70.151.144])
	by sj-core-3.cisco.com (8.12.10/8.12.6) with ESMTP id l3OJwNAS001584;
	Tue, 24 Apr 2007 19:58:43 GMT
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by
	xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 24 Apr 2007 12:58:38 -0700
Received: from irp-view7.cisco.com ([171.70.65.144]) by
	xfe-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 24 Apr 2007 12:58:38 -0700
Date: Tue, 24 Apr 2007 12:58:38 -0700 (PDT)
From: Mike McBride <mmcbride@cisco.com>
To: suhaiyang@huawei.com
Subject: RE: [pim] IETF68 pimwg mtg minutes
In-Reply-To: <002001c78662$ce1b96a0$df010264@china.huawei.com>
Message-ID: <Pine.GSO.4.63.0704241023040.4824@irp-view7.cisco.com>
References: <002001c78662$ce1b96a0$df010264@china.huawei.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-OriginalArrivalTime: 24 Apr 2007 19:58:38.0130 (UTC)
	FILETIME=[F2E98120:01C786AA]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=8023; t=1177444723;
	x=1178308723; c=relaxed/simple; s=sjdkim7002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=mmcbride@cisco.com;
	z=From:=20Mike=20McBride=20<mmcbride@cisco.com>
	|Subject:=20RE=3A=20[pim]=20IETF68=20pimwg=20mtg=20minutes
	|Sender:=20; bh=rY/n6CxqfKFEhl4BoR0OJlimYXbO9Kv7ecBPq3v8w4o=;
	b=ofFPHSAJn2VLRSuPkIw0QMKUaXCatNR4hHKnZcSnRENUpebeRIzpKrg1PutDo7ksE26zZzoz
	tr+Lv3xw7yK2VVHGf22eH9lSHuCBZl215cZTTpj75z4FtxyDK/4VzUg9;
Authentication-Results: sj-dkim-7; header.From=mmcbride@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim7002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 926f893f9bbbfa169f045f85f0cdb955
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>
Errors-To: pim-bounces@ietf.org

> Where can I find any progress about periodic state refresh reduction on SM
> draft?

We had a pim refresh reduction mailing list which is now discontinued. I 
do have the email archive which I'll post somewhere soon. Basically, we 
came up with three solutions:

1) J/P Ack extension to PIM
   - New JP-Ack with identical JP format
   - New JP-Ack hello option
   - Minimal change to pim
   - Complicated?

2) Hard state (TCP)
   - No need to reinvent message flow control
   - Reliability during congestion
   - No refresh necessary
   - Mesh of TCP connections
   - Significant(?) change to pim

3) Do nothing
   - Perhaps use long holdtimes
   - Monitor to see if this effort is necessary

At the time, we had rough consensus with #1. But we've basically been 
following #3. But enough operators have voiced concern about future 
scalability, particularly in PE-PE context, that we've added it to our new 
charter.

mike

> -----Original Message-----
> From: Mike McBride [mailto:mmcbride@cisco.com]
> Sent: Friday, April 20, 2007 6:05 AM
> To: pim@ietf.org
> Subject: [pim] IETF68 pimwg mtg minutes
>
> pimwg meeting minutes
> Prague, Czech Republic
> Tuesday, March 20th, 2007
>
> Created the summarized notes from the pimwg audio archive which can be
> listened to in its entirety at:
> http://limestone.uoregon.edu/ftp/pub/videolab/media/ietf68/ietf68-ch6-tue-pm
> .mp3
>
> Mike: Welcome, agenda bashing
>
> Bill: AD for few more hours. Both bidir and pim mib approved by iesg in last
>
> few weeks. Getting stuff off books that have been languishing. BSR is almost
>
> complete as well.
>
> Mike: Thanks to Bill for all his hard work as AD
>
> BSR Draft:
>
> Alex: Received few comments from last rev of bsr draft from Eric Gray and
> Sandy
> Murphy. Will talk to Sandy this week, few issues she came up with, will take
>
> to list. Lars Eggert: are you allowed to say document updates 2362? It has
> been obsoleted by new pimsm spec which doesn't contain the bsr. Alex thinks
> its
> correct that we say we obsolete 2362.
>
> Bill: Those relationships don't have the meanings we'd like them to. Since
> its
> obsolete it may be that it just doesn't matter, you should take out obsolete
>
> comments, just pretend this is new.
>
> Alex: Eric Gray had valid issues with bsr state machine and I will update
> draft
> to clarify things a bit. Describe the no info state better.
>
> Alex: Eric has issue that scopes could expire before bootstrap timer expires
>
> unless timers were constrained in certain way. Have a constraint that its
> not
> allowed to happen. State machine is correct. Scopes on timer always has to
> be
> higher than bootstrap timer. Scopes will expire a little bit later than if
> implemented then with default timers specified in current spec.
>
> Alex: There is a timer assoc with group to rp mapping and when that timer
> expires that mapping is deleted. its not explicitely mentioned anywhere. It
> could be added to a section that describes how the rp set is received and
> used
> by a router.
>
> Alex: Would like to published one more revision then get draft approved.
>
> RPF vector and join attribute drafts:
>
> Arjen: join attributes passed last call, one last Stig comment about adding
> IANA registry then off to iesg. rpf vector has a few more improvements and
> corrections then we'll go to last call.
>
> last hop threats draft:
>
> Pekka:recap in hopes to generate feedback. It identifies last hop
> vulnerabilities and attacks that can be done with vulnerabilities. Last hop
> between router and host is the concern. Could send unauthorized register
> message to RPs that may contain spoofed messages and create nasty state.
> Host
> may also become unauthorized neighbor. Routers may accept unauthorized
> messages from neighbors. Unauthorized node could be elected as DR.
> Mitigation
> methods: pim passive mode (able to receive and send multicast but router
> doesn't send hellos on that interface or process pim messages). Possible
> when
> you have a single router on a link. Also could use IPsec on a link. If just
> one router also possible to filter out all pim messages. When multiple valid
>
> pim routers on a link, you'll have to use IPsec.
>
> Not much changed since last rev except minor editorial updates. pim spec has
>
> been published so this can now proceed. pim passive has been implemented in
> Junos. Should we go for wglc or have people review doc.
>
> Derek: could you also have pim filter which filters on sources.
>
> Pekka: yes, but you could also spoof the source. The host could send source
> messages with router. So that might not be good enough.
>
> Derek: we have the capability to filter on source but should also combine
> that
> with lockdown of addresses.
>
> Dino: How about having a switch between host and routers. If a switch is
> connected to a particular host port don't accept pim messages on that port,
> so
> router never sees the pim message.
>
> Pekka: yes, that could also be mentioned in the doc.
>
> Pekka: How to procede with the doc?
>
> Mike: revise the doc based upon these comments then we'll issue wglc.
>
> Mike: authors for linklocal draft not able to attend but they are activity
> working on it and have been seeking and receiving advice from msec.
>
> Mike: rechartering/milestones discussion. sent a proposed new charter, all
> comments have been incorporated in text of new charter and milestones. Will
> email ADS and secretariat in a week if I don't hear anything.
>
> Mike: One milestone worth discussion is reducing the messaging of pim. We
> did
> have a design team to look into ways to reduce pim messaging. at that time
> it
> appeared that a j/p ack proposal was most agreed upon but since then the
> urgency of it has dissipated and it was thought that it was a bit too
> complex.
> There have been other thoughts on how to handle this. We have had plenty of
> requests to come up with some sort of solution from operators and l3vpn.
>
> Maria: Nothing has been completed on this in pimwg?
>
> Mike:  correct
>
> Maria: Something has to be done in this area, particularly in context of
> 2547
> multicast. refresh reduction is critical for scalability purposes. Dont see
> the problem yet for scalability of mvpns but it may show up and need some
> sort
> of solution. Receiver explicit tracking needs to be a part of the solution
> for
> aggregation purposes of trees in the core. It has to scale.
>
> Mike: how does wg want to proceed to solve this?
>
> Dino: Do people think this is important for non mvpn environments
>
> Maria: yes. definitely need in core for vpn context, but also needed towards
>
> the CE. native ip multicast needs it. biggest impact is in the core.
>
> Dino: let me restate: do you think solution is necessary for a non pe box.
>
> Greg: Marias explanation is still mvpn context. PE to CE is still mvpn
> environment. The solution would have to be on both ends of the PE.
>
> Dino: If there is too much traffic on the PE-CE link, there is probably too
> much state on one hop downstream as well. Do your customers have a concern?
>
> Maria: not yey. They do have the choice of bidir to reduce state.
>
> Maria: Only PE, which has many interfaces, is of most importance.
>
> Mike: We have a milestone to get something submitted by end of year. If that
>
> doesn't happen, we'll probably need to create a design team.
>
> Mike: drafts have been submitted (not in time to discuss for ietf) to offer
> other enhancements to pim which fit into our new charter.
>
> Pekka: One clarification needed in the charter which says provide a "more
> reliable" solution. Propose to whom and by whom.
>
> Mike: I'll change "propose" to "submit".
>
> _______________________________________________
> 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 Apr 26 15:10:08 2007
Return-path: <pim-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hh9Ls-0007H3-Fh; Thu, 26 Apr 2007 15:10:00 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hh9Lr-0007Gn-A3
	for pim@ietf.org; Thu, 26 Apr 2007 15:09:59 -0400
Received: from wr-out-0506.google.com ([64.233.184.232])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Hh9Lo-0007ma-Oo
	for pim@ietf.org; Thu, 26 Apr 2007 15:09:59 -0400
Received: by wr-out-0506.google.com with SMTP id 71so706455wri
	for <pim@ietf.org>; Thu, 26 Apr 2007 12:09:56 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references;
	b=rVZW0QFgHpUZf0EnsdHWUG5v2VSewkw2L1GryddA6f9caDk+Mfv/BnHY0wmlchsJ2qYi1UfGs87UaAUKuv8HnyDqATJCpZuvOSNuSpOKrHE0WZL4Blp7Pkct7uu1Z/6IJhfDyAgJDlNuwpC24/Injm935U0/yrIMnLoC2SwOwCU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references;
	b=b63atPPKTtQY3QldLdmjCFMEpzdsTAZ5BU9nFcPlm1Ig1HBGutpNkws6qaNQdaWYXNw/n2QU2FDB3YNuWKqb/vF8mIYFBm2xQ2+Zg1Sh9Q/S5BGiBmLFRy+VMtY55SNI6XlcLb2cONKqFnJeCOX7QmTPobkJ8+28bB+GPxDITRo=
Received: by 10.115.16.1 with SMTP id t1mr693387wai.1177614595485;
	Thu, 26 Apr 2007 12:09:55 -0700 (PDT)
Received: by 10.114.210.4 with HTTP; Thu, 26 Apr 2007 12:09:55 -0700 (PDT)
Message-ID: <726917a70704261209g1947ec74v9d6d5165907c3a01@mail.gmail.com>
Date: Thu, 26 Apr 2007 12:09:55 -0700
From: "Rajesh Nataraja" <rbnataraja@gmail.com>
To: "Satyanarayana Dillikar" <dsatyana@broadcom.com>
Subject: Re: [pim] pim-sm router transitions from DR to non-DR
In-Reply-To: <FE7FB54DCB7C6949A1D3F9FF22DA6C13509202@lvl7in-mail01.lvl7.com>
MIME-Version: 1.0
References: <AceEL0KzeHC2GTFyQz+7QJS8UhuvrAAsEhDw>
	<FE7FB54DCB7C6949A1D3F9FF22DA6C13509202@lvl7in-mail01.lvl7.com>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: b22590c27682ace61775ee7b453b40d3
Cc: pim@ietf.org, Binu TN <tnbinu@yahoo.co.in>
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="===============0811942837=="
Errors-To: pim-bounces@ietf.org

--===============0811942837==
Content-Type: multipart/alternative; 
	boundary="----=_Part_64403_29594194.1177614595340"

------=_Part_64403_29594194.1177614595340
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hello,

I think the better way to do is to not care about being a DR or not, and
just  handle it based on what would happen if someone asserts, are there
compatability issues here? What do authors say?

Thanks
Rajesh.


On 4/22/07, Satyanarayana Dillikar <dsatyana@broadcom.com> wrote:
>
>  Hi Binu,
>
>  See inline
>
>
>  ------------------------------
>
> *From:* Binu TN [mailto:tnbinu@yahoo.co.in]
> *Sent:* Saturday, April 21, 2007 9:38 PM
> *To:* pim@ietf.org
> *Subject:* [pim] pim-sm router transitions from DR to non-DR
>
>
>
> Hi,
>
>   I have a basic doubt in the pim-sm router transition from DR to non-DR.
> Let's assume a scenario where a sm router (e.g., RT1) is DR in a LAN and
> it has multicast route entry and it is trigerring Join messages to RP (it is
> in some other network) as it has some interesting hosts. If another sm
> router (e.g.RT2) with higher IP address comes into the LAN of RT1, as per
> my understanding RT2 will become DR and RT1 will become non-DR to that LAN.
> My doubts are,
>
> 1) whether the multicast route entries that are present in RT1 before
> entry of  RT2 will be removed?
>
> *[dsatya] Not necessarily, those entries will changed based on the unicast
> route change to RP. (due to insertion of RT2)*
>
>
> 2) Will RT1 stops trigerring Join messages to RP? Or RT1 will be
> trigerring Join messages for existing entries and RT2 will be trigerring for
> any new entries?
>
> *[dsatya] RT1 should not trigger Join Msgs to RP and RT2 should take up
> the job.*
>
> *Thanks*
>
> *Satya*
>
>
> Please clear my doubts.
> Thank you in advance.
>
> Regards,
> Binu.
>
>
>  ------------------------------
>
> Ahhh...imagining that irresistible "new car" smell?
> Check out new cars at Yahoo! Autos.<http://us.rd.yahoo.com/evt=48245/*http:/autos.yahoo.com/new_cars.html;_ylc=X3oDMTE1YW1jcXJ2BF9TAzk3MTA3MDc2BHNlYwNtYWlsdGFncwRzbGsDbmV3LWNhcnM->
>
> _______________________________________________
> pim mailing list
> pim@ietf.org
> https://www1.ietf.org/mailman/listinfo/pim
>
>

------=_Part_64403_29594194.1177614595340
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

<div>Hello,</div>
<div>&nbsp;</div>
<div>I think the better way to do is to not care about being a DR or not, and just&nbsp; handle it based on what would happen if someone asserts, are there compatability issues here?&nbsp;What do authors say?</div>
<div>&nbsp;</div>
<div>Thanks</div>
<div>Rajesh.<br><br>&nbsp;</div>
<div><span class="gmail_quote">On 4/22/07, <b class="gmail_sendername">Satyanarayana Dillikar</b> &lt;<a href="mailto:dsatyana@broadcom.com">dsatyana@broadcom.com</a>&gt; wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div lang="EN-US" vlink="blue" link="blue">
<div>
<p><font face="Arial" color="navy" size="2"><span style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">Hi Binu,</span></font></p>
<p><font face="Arial" color="navy" size="2"><span style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">&nbsp;See inline</span></font></p>
<p><font face="Arial" color="navy" size="2"><span style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">&nbsp;</span></font></p>
<div>
<div style="TEXT-ALIGN: center" align="center"><font face="Times New Roman" size="3"><span style="FONT-SIZE: 12pt">
<hr align="center" width="100%" size="2">
</span></font></div>
<p><b><font face="Tahoma" size="2"><span style="FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">From:</span></font></b><font face="Tahoma" size="2"><span style="FONT-SIZE: 10pt; FONT-FAMILY: Tahoma"> Binu TN [mailto:
<a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:tnbinu@yahoo.co.in" target="_blank">tnbinu@yahoo.co.in</a>] <br><b><span style="FONT-WEIGHT: bold">Sent:</span></b> Saturday, April 21, 2007 9:38 PM<br>
<b><span style="FONT-WEIGHT: bold">To:</span></b> <a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:pim@ietf.org" target="_blank">pim@ietf.org</a><br><b><span style="FONT-WEIGHT: bold">Subject:</span>
</b> [pim] pim-sm router transitions from DR to non-DR</span></font></p></div><span class="q">
<p><font face="Times New Roman" size="3"><span style="FONT-SIZE: 12pt">&nbsp;</span></font></p>
<p><font face="Times New Roman" size="3"><span style="FONT-SIZE: 12pt">Hi,<br><br>&nbsp; I have a basic doubt in the pim-sm router transition from DR to non-DR. Let&#39;s assume a scenario where a sm router (e.g., RT1) is DR in a LAN and it has multicast route entry and it is trigerring Join messages to RP (it is in some other network) as it has some interesting hosts. If another sm router (
e.g.RT2) with higher IP address comes into the LAN of RT1, as per my understanding RT2 will become DR and RT1 will become non-DR to that LAN. My doubts are,<br><br>1) whether the multicast route entries that are present in RT1 before entry of&nbsp; RT2 will be removed?
<br><br><font color="navy"><span style="COLOR: navy"></span></font></span></font></p></span>
<p><b><i><font face="Arial" color="navy" size="2"><span style="FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: navy; FONT-STYLE: italic; FONT-FAMILY: Arial">[dsatya] Not necessarily, those entries will changed based on the unicast route change to RP. (due to insertion of RT2)
</span></font></i></b></p><span class="q">
<p><font face="Times New Roman" size="3"><span style="FONT-SIZE: 12pt"><br>2) Will RT1 stops trigerring Join messages to RP? Or RT1 will be trigerring Join messages for existing entries and RT2 will be trigerring for any new entries?
<br><br><font color="navy"><span style="COLOR: navy"></span></font></span></font></p></span>
<p><b><i><font face="Arial" color="navy" size="2"><span style="FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: navy; FONT-STYLE: italic; FONT-FAMILY: Arial">[dsatya] RT1 should not trigger Join Msgs to RP and RT2 should take up the job.
</span></font></i></b></p>
<p><b><i><font face="Arial" color="navy" size="2"><span style="FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: navy; FONT-STYLE: italic; FONT-FAMILY: Arial">Thanks</span></font></i></b></p>
<p><b><i><font face="Arial" color="navy" size="2"><span style="FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: navy; FONT-STYLE: italic; FONT-FAMILY: Arial">Satya</span></font></i></b></p><span class="q">
<p><font face="Times New Roman" size="3"><span style="FONT-SIZE: 12pt"><br>Please clear my doubts.<br>Thank you in advance.<br><br>Regards,<br>Binu.</span></font></p>
<p><font face="Times New Roman" size="3"><span style="FONT-SIZE: 12pt">&nbsp; </span></font></p>
<div style="TEXT-ALIGN: center" align="center"><font face="Times New Roman" size="3"><span style="FONT-SIZE: 12pt">
<hr align="center" width="100%" size="1">
</span></font></div>
<p><font face="Times New Roman" size="3"><span style="FONT-SIZE: 12pt">Ahhh...imagining that irresistible &quot;new car&quot; smell?<br>Check out <a onclick="return top.js.OpenExtLink(window,event,this)" href="http://us.rd.yahoo.com/evt=48245/*http:/autos.yahoo.com/new_cars.html;_ylc=X3oDMTE1YW1jcXJ2BF9TAzk3MTA3MDc2BHNlYwNtYWlsdGFncwRzbGsDbmV3LWNhcnM-" target="_blank">
new cars at Yahoo! Autos.</a> </span></font></p></span></div></div><br>_______________________________________________<br>pim mailing list<br><a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:pim@ietf.org">
pim@ietf.org</a><br><a onclick="return top.js.OpenExtLink(window,event,this)" href="https://www1.ietf.org/mailman/listinfo/pim" target="_blank">https://www1.ietf.org/mailman/listinfo/pim</a><br><br></blockquote></div><br>

------=_Part_64403_29594194.1177614595340--


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

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

--===============0811942837==--




