From pim-bounces@ietf.org Mon Jan 08 07:00:30 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H3t9w-0005Cj-6E; Mon, 08 Jan 2007 06:59:24 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H3t9u-0005CV-PL
	for pim@ietf.org; Mon, 08 Jan 2007 06:59:22 -0500
Received: from ug-out-1314.google.com ([66.249.92.173])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H3t9f-0004Ji-9E
	for pim@ietf.org; Mon, 08 Jan 2007 06:59:22 -0500
Received: by ug-out-1314.google.com with SMTP id m3so6021427uge
	for <pim@ietf.org>; Mon, 08 Jan 2007 03:59:04 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:to:subject:mime-version:content-type;
	b=JpTsORaK8g1IuWzsvIXfK7c4ka4ZN4adwNUfa5ZRq8LIDQTDYqnIuP8vUt6HOmHU5CywLD8DirQw3bthYfRf+9bh/KUlfbafiYbrEIOSPnOChLOLkroABToSczUYGfCkW0tc2KQvgu7XWTs3kGV8JE8TPKia+bqjIxms8s2rxRQ=
Received: by 10.82.113.6 with SMTP id l6mr2738015buc.1168257544335;
	Mon, 08 Jan 2007 03:59:04 -0800 (PST)
Received: by 10.82.181.15 with HTTP; Mon, 8 Jan 2007 03:59:04 -0800 (PST)
Message-ID: <1d413a090701080359w7f3db055r56d77afec9c3cef5@mail.gmail.com>
Date: Mon, 8 Jan 2007 17:29:04 +0530
From: "Neeraj Prasad" <neeraj.prasad@gmail.com>
To: pim@ietf.org
MIME-Version: 1.0
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 4b800b1eab964a31702fa68f1ff0e955
Subject: [pim] BIDIR bit in PIM Join/Prune Message
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0695079012=="
Errors-To: pim-bounces@ietf.org

--===============0695079012==
Content-Type: multipart/alternative; 
	boundary="----=_Part_50709_23504827.1168257544272"

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

Hello,

I am facing a strange problem for CISCO

I have a topology like this -

TOPOLOGY
-------------------

T1-------D1,D2--------T2--------S1

CONFIGURATION
---------------------------
D1 and D2 are router interafces
S1 is in a different subnet that D1 and D2
A static route to S1 is configured through T2

S1 is configured as RPA for group G1 in bidir mode (ip pim rp-address <S1 IP
address> bidir)

T1 and T2 are established as BIDIR neighbor for the router i.e PIM Hello
with BIDIR option set is being sent out at hello interval period


Problem statement
---------------------------

I send one PIM Join/Prune message from T1 towards D1 with following values -

Upstream Nbr Address = D1's IP address
Multicast Address = G1
Joined Source Address = S1's IP address
RPT-bit=1
S-bit=1
WC-bit=1
Bidir-bit=1

I received a PIM Join/Prune message on T2 with desired parameters except
that the BIDIR-bit is unset.

QUERY
------------
Is this a valid behaviour. If 'yes' can anyone explain why this is
happening. If 'no' can any CISCO people explain why this is happening.

Please let me know if more information is required.

Thanks in advance,

Regards,
Neeraj.

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

Hello,<br><br>I am facing a strange problem for CISCO<br><br>I have a topology like this -<br><br>TOPOLOGY<br>-------------------<br><br>T1-------D1,D2--------T2--------S1<br><br>CONFIGURATION<br>---------------------------
<br>D1 and D2 are router interafces<br>S1 is in a different subnet that D1 and D2<br>A static route to S1 is configured through T2<br><br>S1 is configured as RPA for group G1 in bidir mode (ip pim rp-address &lt;S1 IP address&gt; bidir)
<br><br>T1 and T2 are established as BIDIR neighbor for the router i.e PIM Hello with BIDIR option set is being sent out at hello interval period<br><br><br>Problem statement<br>---------------------------<br><br>I send one PIM Join/Prune message from T1 towards D1 with following values -
<br><br>Upstream Nbr Address = D1&#39;s IP address<br>Multicast Address = G1<br>Joined Source Address = S1&#39;s IP address<br>RPT-bit=1<br>S-bit=1<br>WC-bit=1<br>Bidir-bit=1<br><br>I received a PIM Join/Prune message on T2 with desired parameters except that the 
<span style="font-weight: bold;">BIDIR-bit is unset.</span><br><br>QUERY<br>------------<br>Is this a valid behaviour. If &#39;yes&#39; can anyone explain why this is happening. If &#39;no&#39; can any CISCO people explain why this is happening.
<br><br>Please let me know if more information is required.<br><br>Thanks in advance,<br><br>Regards,<br>Neeraj.<br clear="all">

------=_Part_50709_23504827.1168257544272--


--===============0695079012==
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

--===============0695079012==--




From 888momo444@docomo.ne.jp Wed Jan 10 19:47:36 2007
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H4o6S-0006u3-Sk
	for pim-archive@lists.ietf.org; Wed, 10 Jan 2007 19:47:36 -0500
Received: from [220.194.46.198] (helo=kimu01.alpha.co.jp)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1H4o67-0005ZM-0o
	for pim-archive@lists.ietf.org; Wed, 10 Jan 2007 19:47:36 -0500
Subject: =?ISO-2022-JP?B?grGC8YLJgr+CzYFBU05TgWmXoIFqiV6JY46WlrGLx4LFgreBQg==?=
From: SNS（裏）運営事務局<luludesigano@yahoo.co.jp>
To: pim-archive@lists.ietf.org
Message-ID: 20070111094640
Content-Type: text/plain; charset="SHIFT_JIS"
Content-Transfer-Encoding: 7bit
MIME-Version: 1.0
Date: Thu, 11 Jan 2007 09:46:53 +0900 (JST)
X-Spam-Score: 1.6 (+)
X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793

アカネ　さんがあなたを 
セックスフレンドネットワーキングサイト SNS（裏）へ招待しています。 

メッセージ： 

『いろんな人と気軽にセックスをしたいとおもって、SNSに入りました。
ちょっと気になったのでよかったら友達追加してもらえると嬉しいです☆
セックスの事色々知ってそうなので、色々おしえてほしいです!
１月２０日あたりどうですかぁ？？』


下記のURLよりアカネさんの登録画面をご覧いただけます。 

↓こちらから招待者のsns（裏）トップページを見ることができます。 
http://for.egoism.jp/89498849.htm

■□■　コミュニティ・エンターテイメント　　　　　　　　　　　　■□■ 
□■□　セックスフレンドネットワーキングサイト　SNS（裏）って何？　□■□ 

SNS（裏）は、メンバーより招待された方のみで構成されている、 
日本初のセックスフレンドネットワーキングサイトです。 

■SNS（裏）ならこれまで以上にセフレ関係を活性化できる

信頼できる旧知の友人、お知り合いとのセックスライフの活性化を図るさまざまな 
ツールをご用意しています。 

■「友人の友人」と交流できる 

SNS（裏）を使えば友人同士のネットワークをたどって「友人の友人」との交流が 
簡単にできます。そこにはあなたの友人から繋がる信頼できるネットワークが 
形成されています。SNS（裏）はどこかで繋がっている人同士が集まるコミュニティ 
であり、これがソーシャルネットワーキングの特徴です。 

■SNS（裏）なら日記の読み書き、これまでご利用の日記の公開ができる 

みなさんは日記を公開することによって友人やSNS（裏）に登録している人々に多くの 
情報を発信することが可能です。さらにこれまで使用されていた他の日記・ブログ 
を使うか、SNS（裏）の日記を使うかを選択することができます。 


SNS（裏）へ参加↓ 
http://for.egoism.jp/89498849.htm

それでは、参加を心よりお待ちしております。 



― SNS（裏） ―――――――――――――――――――
コミュニティ・エンターテイメント SNS（裏） 
URL ：http://for.egoism.jp/
運営会社 ： 株式会社SNS
―――――――――――――――――――――――――



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

--===============1716395131==
Content-Type: multipart/alternative; boundary="0-1307222299-1168491975=:86504"
Content-Transfer-Encoding: 8bit

--0-1307222299-1168491975=:86504
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

Hi,

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

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

Please let me know if more information is required.

Thanks and regards,
Sumanta

 				
---------------------------------
 Here痴 a new way to find what you're looking for - Yahoo! Answers 
--0-1307222299-1168491975=:86504
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

Hi,<br><br>I have some confusion about one statement in the draft "draft-ietf-pim-sm-bsr-09". In section  3.3 (page 21), the draft says the following --<br>"<span style="font-weight: bold;">RP mappings may be included in the first group range of a BSM, just as for any other group range. After this group range, other group ranges for which there are RP mappings appear in any order </span>".<br><br>Suppose a situation where the BSR is configured with one scope, say <span style="font-weight: bold;">G</span> and it becomes the elected BSR for that scope. At the same time it is receiving one C-RP-Adv message for the same scope (i.e . another router wants to be the candidate RP for the same multicast group range G) with address  <span style="font-weight: bold;">X</span>. Now when the BSR will send BSM, G will always present in the first group-rp-set of the BSM (with Z bit 1). But will it include the RP address X in the first group-rp-set or it will add another group-rp-set with
 group address G ( Z bit 0) where it will include the RP address X. <br><br>Please let me know if more information is required.<br><br>Thanks and regards,<br>Sumanta<br><p>&#32;
	

	
		<hr size=1></hr> 
Here痴 a new way to find what you're looking for - <a href="http://us.rd.yahoo.com/mail/in/yanswers/*http://in.answers.yahoo.com/">Yahoo! Answers</a> 
--0-1307222299-1168491975=:86504--


--===============1716395131==
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

--===============1716395131==--




From pim-bounces@ietf.org Thu Jan 11 04:06:36 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H4vss-0008V7-M0; Thu, 11 Jan 2007 04:06:06 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H4vsq-0008V1-3s
	for pim@ietf.org; Thu, 11 Jan 2007 04:06:04 -0500
Received: from tyholt.uninett.no ([2001:700:1::eecb])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H4vso-0000cs-84
	for pim@ietf.org; Thu, 11 Jan 2007 04:06:04 -0500
Received: from localhost (localhost.localdomain [127.0.0.1])
	by tyholt.uninett.no (Postfix) with ESMTP id B351A87C07;
	Thu, 11 Jan 2007 10:05:54 +0100 (CET)
Received: from tyholt.uninett.no ([127.0.0.1])
	by localhost (tyholt.uninett.no [127.0.0.1]) (amavisd-new, port 10024)
	with LMTP id 06467-01-41; Thu, 11 Jan 2007 10:05:54 +0100 (CET)
Received: from [10.0.0.174] (unknown [217.206.93.210])
	by tyholt.uninett.no (Postfix) with ESMTP id 222ADB5A66;
	Thu, 11 Jan 2007 10:05:54 +0100 (CET)
Message-ID: <45A4CE26.4070409@uninett.no>
Date: Wed, 10 Jan 2007 12:29:42 +0100
From: Stig Venaas <stig.venaas@uninett.no>
User-Agent: Mozilla Thunderbird 1.0.7 (X11/20060616)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: sumanta seal <seal_sum@yahoo.co.in>
Subject: Re: [pim] Query about scoped Bootstrap Message
References: <932765.86504.qm@web8502.mail.in.yahoo.com>
In-Reply-To: <932765.86504.qm@web8502.mail.in.yahoo.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: quoted-printable
X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at uninett.no
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3
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

sumanta seal wrote:
> Hi,
>=20
> I have some confusion about one statement in the draft=20
> "draft-ietf-pim-sm-bsr-09". In section 3.3 (page 21), the draft says th=
e=20
> following --
> "RP mappings may be included in the first group range of a BSM, just as=
=20
> for any other group range. After this group range, other group ranges=20
> for which there are RP mappings appear in any order ".
>=20
> Suppose a situation where the BSR is configured with one scope, say G=20
> and it becomes the elected BSR for that scope. At the same time it is=20
> receiving one C-RP-Adv message for the same scope (i.e . another router=
=20
> wants to be the candidate RP for the same multicast group range G) with=
=20
> address X. Now when the BSR will send BSM, G will always present in the=
=20
> first group-rp-set of the BSM (with Z bit 1). But will it include the R=
P=20
> address X in the first group-rp-set or it will add another group-rp-set=
=20
> with group address G ( Z bit 0) where it will include the RP address X.=


You must only have each group range once with all the RPs for the range.
So if you have multiple RPs in the RP-set for G, you should include them
all there. If G is the scope, then you put G first in the BSM with Z bit
set as you wrote.

Stig

>=20
> Please let me know if more information is required.
>=20
> Thanks and regards,
> Sumanta
>=20
> -----------------------------------------------------------------------=
-
> Here=92s a new way to find what you're looking for - Yahoo! Answers=20
> <http://us.rd.yahoo.com/mail/in/yanswers/*http://in.answers.yahoo.com/>=

>=20
>=20
> -----------------------------------------------------------------------=
-
>=20
> _______________________________________________
> 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 Jan 11 14:37:22 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H55j0-00057g-Uj; Thu, 11 Jan 2007 14:36:34 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H55iy-00052P-7X; Thu, 11 Jan 2007 14:36:32 -0500
Received: from ns4.neustar.com ([156.154.24.139])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1H55iw-0003ov-VS; Thu, 11 Jan 2007 14:36:32 -0500
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns4.neustar.com (Postfix) with ESMTP id E199A2AC69;
	Thu, 11 Jan 2007 19:36:00 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1H55iS-00071m-M9; Thu, 11 Jan 2007 14:36:00 -0500
X-test-idtracker: no
To: IETF-Announce <ietf-announce@ietf.org>
From: The IESG <iesg-secretary@ietf.org>
Message-Id: <E1H55iS-00071m-M9@stiedprstage1.ietf.org>
Date: Thu, 11 Jan 2007 14:36:00 -0500
X-Spam-Score: -2.8 (--)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Cc: pim@ietf.org
Subject: [pim] Last Call: draft-ietf-pim-mib-v2 (Protocol Independent 
 Multicast MIB) to Proposed Standard 
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: ietf@ietf.org
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

The IESG has received a request from the Protocol Independent Multicast 
WG (pim) to consider the following document:

- 'Protocol Independent Multicast MIB '
   <draft-ietf-pim-mib-v2-09.txt> as a Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send substantive comments to the
ietf@ietf.org mailing lists by 2007-01-25. Exceptionally, 
comments may be sent to iesg@ietf.org instead. In either case, please 
retain the beginning of the Subject line to allow automated sorting.

The file can be obtained via
http://www.ietf.org/internet-drafts/draft-ietf-pim-mib-v2-09.txt


IESG discussion can be tracked via
https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=8944&rfc_flag=0


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



From pim-bounces@ietf.org Fri Jan 19 18:01:30 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H82ii-0007os-KB; Fri, 19 Jan 2007 18:00:28 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H82ih-0007on-AC
	for pim@ietf.org; Fri, 19 Jan 2007 18:00:27 -0500
Received: from mail.ipinfusion.com ([65.223.109.2] helo=gateway.ipinfusion.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H82ie-0003eo-Tz
	for pim@ietf.org; Fri, 19 Jan 2007 18:00:27 -0500
Received: from [10.10.0.156] ([65.223.109.250])
	by gateway.ipinfusion.com (8.11.6/8.11.6) with ESMTP id l0JMxaK31674
	for <pim@ietf.org>; Fri, 19 Jan 2007 14:59:36 -0800
From: Rishabh Parekh <rishabh@ipinfusion.com>
Organization: IP Infusion
To: pim@ietf.org
Date: Fri, 19 Jan 2007 15:00:31 -0800
User-Agent: KMail/1.9.1
MIME-Version: 1.0
Message-Id: <200701191500.31785.rishabh@ipinfusion.com>
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Subject: [pim] Use of BS_Min_Interval in BSR draft
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="===============0214055913=="
Errors-To: pim-bounces@ietf.org

--===============0214055913==
Content-Type: multipart/alternative; boundary="Boundary-00=_P2UsFPw4/czFqfW"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

--Boundary-00=_P2UsFPw4/czFqfW
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: 7bit

Hi,
The latest BSR draft states "There MUST however be a minimum of BS_Min_Interval between each time a BSM is sent." This is mentioned in the context of generating BSMs on C-RP set changes. 

However, the C-BSR state machine also originates BSMs in E-BSR state for the event "Recieve Non-Preferred BSM". This action is not limited by BS_Min_Interval. Should this action also be throttled by BS_Min_Interval value? If so, then the action should be to reduce BS Timer to BS_Min_Interval if it is greater than this interval.

Regards,
Rishabh.

--Boundary-00=_P2UsFPw4/czFqfW
Content-Type: text/html;
  charset="us-ascii"
Content-Transfer-Encoding: 7bit

<html><head><meta name="qrichtext" content="1" /></head><body style="font-size:10pt;font-family:Arial">
<p>Hi,</p>
<p>The latest BSR draft states &quot;<span style="font-weight:600">There MUST however be a minimum of BS_Min_Interval between each time a BSM is sent.</span>&quot; This is mentioned in the context of generating BSMs on C-RP set changes. </p>
<p></p>
<p>However, the C-BSR state machine also originates BSMs in E-BSR state for the event &quot;Recieve Non-Preferred BSM&quot;. This action is not limited by BS_Min_Interval. Should this action also be throttled by BS_Min_Interval value? If so, then the action should be to reduce BS Timer to BS_Min_Interval if it is greater than this interval.</p>
<p></p>
<p>Regards,</p>
<p>Rishabh.</p>
<p></p>
</body></html>
--Boundary-00=_P2UsFPw4/czFqfW--


--===============0214055913==
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

--===============0214055913==--




From pim-bounces@ietf.org Fri Jan 19 20:12:04 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H84km-0005m7-3F; Fri, 19 Jan 2007 20:10:44 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H84kk-0005m2-I5
	for pim@ietf.org; Fri, 19 Jan 2007 20:10:42 -0500
Received: from nf-out-0910.google.com ([64.233.182.190])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H84kj-0003Xz-4w
	for pim@ietf.org; Fri, 19 Jan 2007 20:10:42 -0500
Received: by nf-out-0910.google.com with SMTP id l36so641409nfa
	for <pim@ietf.org>; Fri, 19 Jan 2007 17:10:40 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:to:subject:mime-version:content-type;
	b=PN67dvfebYiWVEpW8ObF2yA5bYW115Ai53XvexflUls8kD8Ud6l1cdslzLaAesl5mk2oF/JcWYfoP9Vkx84Ha/bD6NjPkxH0yybuESenDeSNbUnEg+M+qJ5qZgCVFxdzSo9S7C6kjk/Ay4vgr4wrPRAGOdQq4lHVDeir2oMdvMg=
Received: by 10.49.58.13 with SMTP id l13mr2544729nfk.1169255438850;
	Fri, 19 Jan 2007 17:10:38 -0800 (PST)
Received: by 10.49.22.7 with HTTP; Fri, 19 Jan 2007 17:10:38 -0800 (PST)
Message-ID: <726917a70701191710x4e50ba0bodb06436d3c517efb@mail.gmail.com>
Date: Fri, 19 Jan 2007 17:10:38 -0800
From: "Rajesh Nataraja" <rbnataraja@gmail.com>
To: pim@ietf.org
MIME-Version: 1.0
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 10d3e4e3c32e363f129e380e644649be
Subject: [pim] CRP message processing, Priority down to Group prefix level?
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="===============0702853809=="
Errors-To: pim-bounces@ietf.org

--===============0702853809==
Content-Type: multipart/alternative; 
	boundary="----=_Part_72069_2972955.1169255438698"

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

Hi,

I had a question in CRP message processing.

If a CRP does not advertise a particular group prefix in a message,
Should the BSR treat that Group prefix as not configured for the CRP any
more and then adjust its BSR message to accomodate the removal of the group
prefix immediately?
or
Should it courteously wait until the Group prefix, which could be started
for the hold time the CRP advertised before, expire and then adjust its BSR
message?

Why Iam asking this is to see if it is legal to advertise group prefixes for
a CRP with granularity for the priority down to a group prefix level.
I have seen this in one of the implementations.

Thanks
Rajesh.


On 1/19/07, Rishabh Parekh <rishabh@ipinfusion.com> wrote:
>
>  Hi,
>
> The latest BSR draft states "There MUST however be a minimum of
> BS_Min_Interval between each time a BSM is sent." This is mentioned in the
> context of generating BSMs on C-RP set changes.
>
> However, the C-BSR state machine also originates BSMs in E-BSR state for
> the event "Recieve Non-Preferred BSM". This action is not limited by
> BS_Min_Interval. Should this action also be throttled by BS_Min_Interval
> value? If so, then the action should be to reduce BS Timer to
> BS_Min_Interval if it is greater than this interval.
>
> Regards,
>
> Rishabh.
>
>
> _______________________________________________
> pim mailing list
> pim@ietf.org
> https://www1.ietf.org/mailman/listinfo/pim
>
>
>

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

<div>Hi,</div>
<div>&nbsp;</div>
<div>I had a question in CRP message processing. </div>
<div>&nbsp;</div>
<div>If a CRP does not advertise a particular group prefix in a message,</div>
<div>Should the BSR treat that Group prefix as not configured for the CRP any more and then adjust its BSR message to accomodate the removal of the group prefix immediately?</div>
<div>or</div>
<div>Should it courteously wait until the Group prefix, which could be started for the hold time the CRP advertised before, expire and then adjust its BSR message?</div>
<div>&nbsp;</div>
<div>Why Iam asking this is to see if it is legal&nbsp;to advertise group prefixes for a&nbsp;CRP with granularity for the priority down to a group prefix level.</div>
<div>I have seen this in one of the implementations.</div>
<div>&nbsp;</div>
<div>Thanks</div>
<div>Rajesh.<br><br>&nbsp;</div>
<div><span class="gmail_quote">On 1/19/07, <b class="gmail_sendername">Rishabh Parekh</b> &lt;<a href="mailto:rishabh@ipinfusion.com">rishabh@ipinfusion.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 style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">
<p>Hi,</p>
<p>The latest BSR draft states &quot;<span style="FONT-WEIGHT: 600">There MUST however be a minimum of BS_Min_Interval between each time a BSM is sent.</span>&quot; This is mentioned in the context of generating BSMs on C-RP set changes. 
</p>
<p></p>
<p>However, the C-BSR state machine also originates BSMs in E-BSR state for the event &quot;Recieve Non-Preferred BSM&quot;. This action is not limited by BS_Min_Interval. Should this action also be throttled by BS_Min_Interval value? If so, then the action should be to reduce BS Timer to BS_Min_Interval if it is greater than this interval.
</p>
<p></p>
<p>Regards,</p>
<p>Rishabh.</p>
<p></p></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><br></blockquote></div><br>

------=_Part_72069_2972955.1169255438698--


--===============0702853809==
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

--===============0702853809==--




From pim-bounces@ietf.org Sat Jan 20 04:21:49 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H8CP7-0006Vw-R4; Sat, 20 Jan 2007 04:20:53 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H8CP6-0006Vr-PU
	for pim@ietf.org; Sat, 20 Jan 2007 04:20:52 -0500
Received: from web8512.mail.in.yahoo.com ([202.43.219.105])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1H8CP3-0007ha-7x
	for pim@ietf.org; Sat, 20 Jan 2007 04:20:52 -0500
Received: (qmail 19569 invoked by uid 60001); 20 Jan 2007 09:20:44 -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:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID;
	b=WIGgEhtLs72NQwIXfXyjA4ksGxRiwIQaKeqLc5U6jHzzl/1HuTScW1lw5BYy6bgmAk0N8h8decbSSj8Q4b0EltZGdi0bztmu4wdOsOSLUSZMp8c7vDuX9mliepKTk4Y+/HxgZHPHiDSuEnJQdPFBtpyg+tzHLwduoElZ9Jtj3GI=;
X-YMail-OSG: 7T8GnfUVM1nQVxXwZYNccdpm7pyl1nW7q1Kduw2pa2Oy9Nz59GJSsf_s_4JuOr4qomkaEiQhGepmzp_7sqIqnkCdQ9BGLpcHvPaHW4lztyJCgLXshuOA7QCSeemz1OyeJG8kkUTHcrrD8VE-
Received: from [203.197.124.190] by web8512.mail.in.yahoo.com via HTTP;
	Sat, 20 Jan 2007 09:20:44 GMT
Date: Sat, 20 Jan 2007 09:20:44 +0000 (GMT)
From: sumanta seal <seal_sum@yahoo.co.in>
Subject: Re: [pim] Use of BS_Min_Interval in BSR draft
To: Rishabh Parekh <rishabh@ipinfusion.com>
In-Reply-To: <200701191500.31785.rishabh@ipinfusion.com>
MIME-Version: 1.0
Message-ID: <598461.17918.qm@web8512.mail.in.yahoo.com>
X-Spam-Score: 0.7 (/)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
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="===============0579288158=="
Errors-To: pim-bounces@ietf.org

--===============0579288158==
Content-Type: multipart/alternative; boundary="0-1769955575-1169284844=:17918"
Content-Transfer-Encoding: 8bit

--0-1769955575-1169284844=:17918
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit



Rishabh Parekh <rishabh@ipinfusion.com> wrote:  Hi,
 The latest BSR draft states "There MUST however be a minimum of BS_Min_Interval between each time a BSM is sent." This is mentioned in the context of generating BSMs on C-RP set changes. 
 
 However, the C-BSR state machine also originates BSMs in E-BSR state for the event "Recieve Non-Preferred BSM". This action is not limited by BS_Min_Interval. Should this action also be throttled by BS_Min_Interval value?
 If so, then the action should be to reduce BS Timer to BS_Min_Interval if it is greater than this interval. 
BS_Min_Interval is applied to the case when there is a need of sending BSM due to some event. For example, when a BSR, elected as DR, receives a new Hello or a Hello with new Gen Id from a PIM neighbor, it will send a BSM with the stored copy of Bootstrap information in it. This BSM should be send after BS_Min_Interval from the previous BSM it send. In normal scenario, BSMs are send at an interval of BS_Period by the elected BSR.
Rgds,Sumanta

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



Thanks & Regards, 
************************************************** 
Sumanta Seal
Salt Lake City, Kolkata
West Bengal
**************************************************

 				
---------------------------------
 Here痴 a new way to find what you're looking for - Yahoo! Answers 
--0-1769955575-1169284844=:17918
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

<br><br><b><i>Rishabh Parekh &lt;rishabh@ipinfusion.com&gt;</i></b> wrote:<blockquote class="replbq" style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;"> <meta name="qrichtext" content="1"> <div>Hi,</div> <div>The latest BSR draft states "<span style="font-weight: 600;">There MUST however be a minimum of BS_Min_Interval between each time a BSM is sent.</span>" This is mentioned in the context of generating BSMs on C-RP set changes. </div> <div></div> <div>However, the C-BSR state machine also originates BSMs in E-BSR state for the event "Recieve Non-Preferred BSM". This action is not limited by BS_Min_Interval. Should this action also be throttled by BS_Min_Interval value?</div><div> If so, then the action should be to reduce BS Timer to BS_Min_Interval if it is greater than this interval. </div><div>BS_Min_Interval is applied to the case when there is a need of sending BSM due to some event. For example, when a BSR, elected as DR, receives
 a new Hello or a Hello with new Gen Id from a PIM neighbor, it will send a BSM with the stored copy of Bootstrap information in it. This BSM should be send after BS_Min_Interval from the previous BSM it send. In normal scenario, BSMs are send at an interval of BS_Period by the elected BSR.</div>Rgds,<div>Sumanta<br></div> <div></div> <div>Regards,</div> <div>Rishabh.</div> <div></div> _______________________________________________<br>pim mailing list<br>pim@ietf.org<br>https://www1.ietf.org/mailman/listinfo/pim<br></blockquote><br><BR><BR><div>Thanks &amp; Regards, <br>************************************************** <br><font color="#855a40" face="comic sans ms" size="4">Sumanta Seal</font><br>Salt Lake City, Kolkata<br>West Bengal<br>**************************************************</div><p>&#32;
	

	
		<hr size=1></hr> 
Here痴 a new way to find what you're looking for - <a href="http://us.rd.yahoo.com/mail/in/yanswers/*http://in.answers.yahoo.com/">Yahoo! Answers</a> 
--0-1769955575-1169284844=:17918--


--===============0579288158==
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

--===============0579288158==--




From pim-bounces@ietf.org Sat Jan 20 04:40:31 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H8Chn-0005TG-GJ; Sat, 20 Jan 2007 04:40:11 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H8Chl-0005TB-NB
	for pim@ietf.org; Sat, 20 Jan 2007 04:40:09 -0500
Received: from web8503.mail.in.yahoo.com ([202.43.219.165])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1H8Chj-0001fE-BV
	for pim@ietf.org; Sat, 20 Jan 2007 04:40:09 -0500
Received: (qmail 49790 invoked by uid 60001); 20 Jan 2007 09:40:05 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.co.in;
	h=Message-ID:X-YMail-OSG:Received:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding;
	b=CYot+HrSo6lKK41ugOoftcNo+APLZkpWmVyx486Ptihk4t4njWJNw4CTA4PIfpTwsu1ZHG2PVFmIS5nMdtWGJvynHAIZ4mh1xw+NNLm2/j5QqYKj/rjz0PXZsbTMUOYeRjIzMRfR4zTwvBUdIs/OLss2OscmuH6OeiKAeN0BRus=
	; 
Message-ID: <20070120094005.49784.qmail@web8503.mail.in.yahoo.com>
X-YMail-OSG: ErewzO4VM1ln7iq8tUBNMQzKDXJA5UbO.mYM5T_DRS_8Wmf1qkCVd49WG0xTPvAAS5F4Mr9HplKN0xgpTAE_l4L6nJ5LJpBKL0OvCSDRrR1xQ1yR.jHacKFdWQhyTAYYp6EkLopQd0rQUITlSo60jvVnWdyWdz2IqfsfMs9oSAFeyrAQWpU2v.fl68xq
Received: from [203.197.124.190] by web8503.mail.in.yahoo.com via HTTP;
	Sat, 20 Jan 2007 09:40:05 GMT
Date: Sat, 20 Jan 2007 09:40:05 +0000 (GMT)
From: sumanta seal <seal_sum@yahoo.co.in>
Subject: Re: [pim] CRP message processing, Priority down to Group prefix level?
To: Rajesh Nataraja <rbnataraja@gmail.com>
In-Reply-To: <726917a70701191710x4e50ba0bodb06436d3c517efb@mail.gmail.com>
MIME-Version: 1.0
X-Spam-Score: 0.3 (/)
X-Scan-Signature: d185fa790257f526fedfd5d01ed9c976
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="===============0363843190=="
Errors-To: pim-bounces@ietf.org

--===============0363843190==
Content-Type: multipart/alternative; boundary="0-430546337-1169286005=:48693"
Content-Transfer-Encoding: 8bit

--0-430546337-1169286005=:48693
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit



Rajesh Nataraja <rbnataraja@gmail.com> wrote: Hi,
  
 I had a question in CRP message processing. 
  
 If a CRP does not advertise a particular group prefix in a message,
 Should the BSR treat that Group prefix as not configured for the CRP any more and then adjust its BSR message to accomodate the removal of the group prefix immediately?
 or
 Should it courteously wait until the Group prefix, which could be started for the hold time the CRP advertised before, expire and then adjust its BSR message?
 

What I think is that, the BSR will not immediately adjust it's BSM to accomodate the removal of the group prefix, rather it will wait to expire GET associated with the group perfix, which is updated by the Holdtime of the received C-RP-Adv message. As per the standard (draft-ietf-pim-sm-bsr-09, section 3.3, page 19),If the holdtime is zero, the mapping is immediately removed from the C-RP-Set and when a CGET expires, the corresponding group-to-C-RP mapping is removed from the C-RP-Set.

 There are no other cases by which this mapping can be removed from C-RP-Set in the BSR.

Rgds,

Sumanta


Why Iam asking this is to see if it is legal to advertise group prefixes for a CRP with granularity for the priority down to a group prefix level.
 I have seen this in one of the implementations.
  
 Thanks
 Rajesh.

 
 On 1/19/07, Rishabh Parekh <rishabh@ipinfusion.com> wrote:   Hi,
 The latest BSR draft states "There MUST however be a minimum of BS_Min_Interval between each time a BSM is sent." This is mentioned in the context of generating BSMs on C-RP set changes.  
 
 However, the C-BSR state machine also originates BSMs in E-BSR state for the event "Recieve Non-Preferred BSM". This action is not limited by BS_Min_Interval. Should this action also be throttled by BS_Min_Interval value? If so, then the action should be to reduce BS Timer to BS_Min_Interval if it is greater than this interval. 
 
 Regards,
 Rishabh.
 


_______________________________________________
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



Thanks & Regards, 
************************************************** 
Sumanta Seal
Salt Lake City, Kolkata
West Bengal
**************************************************

 				
---------------------------------
 Here痴 a new way to find what you're looking for - Yahoo! Answers 
--0-430546337-1169286005=:48693
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

<br><br><b><i>Rajesh Nataraja &lt;rbnataraja@gmail.com&gt;</i></b> wrote:<blockquote class="replbq" style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;"> <div>Hi,</div> <div>&nbsp;</div> <div>I had a question in CRP message processing. </div> <div>&nbsp;</div> <div>If a CRP does not advertise a particular group prefix in a message,</div> <div>Should the BSR treat that Group prefix as not configured for the CRP any more and then adjust its BSR message to accomodate the removal of the group prefix immediately?</div> <div>or</div> <div>Should it courteously wait until the Group prefix, which could be started for the hold time the CRP advertised before, expire and then adjust its BSR message?</div> <div><br><br>What I think is that, the BSR will not immediately adjust it's BSM to accomodate the removal of the group prefix, rather it will wait to expire GET associated with the group perfix, which is updated by the Holdtime of the received
 C-RP-Adv message. As per the standard (<tt><tt>draft-ietf-pim-sm-bsr-09, section 3.3, page 19),<span style="font-weight: bold;">If the holdtime is zero, the mapping is immediately removed from the C-RP-Set</span> and <span style="font-weight: bold;">when a CGET expires, the corresponding group-to-C-RP mapping is removed from the C-RP-Set.</span></tt></tt><br></div> <div>There are no other cases by which this mapping can be removed from C-RP-Set in the BSR.<br><br>Rgds,<br><br>Sumanta<br><br><br>Why Iam asking this is to see if it is legal&nbsp;to advertise group prefixes for a&nbsp;CRP with granularity for the priority down to a group prefix level.</div> <div>I have seen this in one of the implementations.</div> <div>&nbsp;</div> <div>Thanks</div> <div>Rajesh.<br><br>&nbsp;</div> <div><span class="gmail_quote">On 1/19/07, <b class="gmail_sendername">Rishabh Parekh</b> &lt;<a href="mailto:rishabh@ipinfusion.com">rishabh@ipinfusion.com</a>&gt; wrote:</span> <blockquote
 class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0px 0px 0px 0.8ex; padding-left: 1ex;"> <div style="font-size: 10pt; font-family: Arial;"> <div>Hi,</div> <div>The latest BSR draft states "<span style="font-weight: 600;">There MUST however be a minimum of BS_Min_Interval between each time a BSM is sent.</span>" This is mentioned in the context of generating BSMs on C-RP set changes.  </div> <div></div> <div>However, the C-BSR state machine also originates BSMs in E-BSR state for the event "Recieve Non-Preferred BSM". This action is not limited by BS_Min_Interval. Should this action also be throttled by BS_Min_Interval value? If so, then the action should be to reduce BS Timer to BS_Min_Interval if it is greater than this interval. </div> <div></div> <div>Regards,</div> <div>Rishabh.</div> <div></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><br></blockquote></div><br> _______________________________________________<br>pim mailing list<br>pim@ietf.org<br>https://www1.ietf.org/mailman/listinfo/pim<br></blockquote><br><BR><BR><div>Thanks &amp; Regards, <br>************************************************** <br><font color="#855a40" face="comic sans ms" size="4">Sumanta Seal</font><br>Salt Lake City, Kolkata<br>West Bengal<br>**************************************************</div><p>&#32;
	

	
		<hr size=1></hr> 
Here痴 a new way to find what you're looking for - <a href="http://us.rd.yahoo.com/mail/in/yanswers/*http://in.answers.yahoo.com/">Yahoo! Answers</a> 
--0-430546337-1169286005=:48693--


--===============0363843190==
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

--===============0363843190==--




From pim-bounces@ietf.org Sun Jan 21 19:18:34 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H8mrj-0008L7-FH; Sun, 21 Jan 2007 19:16:51 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H8mrh-0008Jt-Of
	for pim@ietf.org; Sun, 21 Jan 2007 19:16:49 -0500
Received: from mail9.dslextreme.com ([66.51.199.94])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1H8mrf-0001vz-9d
	for pim@ietf.org; Sun, 21 Jan 2007 19:16:49 -0500
Received: (qmail 27733 invoked from network); 22 Jan 2007 00:16:42 -0000
Received: from unknown (HELO [192.168.10.110]) (rparekh@66.218.45.53)
	by mail9. with (EXP1024-RC4-SHA encrypted) SMTP;
	Sun, 21 Jan 2007 16:16:42 -0800
From: Rishabh Parekh <rishabh@ipinfusion.com>
Organization: IP Infusion
To: sumanta seal <seal_sum@yahoo.co.in>
Subject: Re: [pim] Use of BS_Min_Interval in BSR draft
Date: Sun, 21 Jan 2007 16:16:55 -0800
User-Agent: KMail/1.9.1
References: <598461.17918.qm@web8512.mail.in.yahoo.com>
In-Reply-To: <598461.17918.qm@web8512.mail.in.yahoo.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-6"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Message-Id: <200701211616.55705.rishabh@ipinfusion.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002
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

Sumanta,
Please fine my reply inline.

Rishabh.
On Saturday 20 January 2007 01:20, sumanta seal wrote:
> BS_Min_Interval is=20
> applied to the case when there is a need of sending BSM due to some event.
> For example, when a BSR, elected as DR, receives a new Hello or a Hello
> with new Gen Id from a PIM neighbor, it will send a BSM with the stored
> copy of Bootstrap information in it. This BSM should be send after
> BS_Min_Interval from the previous BSM it send. In normal scenario, BSMs a=
re
> send at an interval of BS_Period by the elected BSR. Rgds,Sumanta
>
You are referring to the "No Forward" or Unicast BSMs which refresh BSR sta=
te=20
at a new or re-starting neighbor. I don't think that these BSMs should be=20
limited by the BS_Min_Interval because doing so will defeat the very purpos=
e=20
of such BSM messages.
I was referring to the regular BSM generated by an E-BSR due to two differe=
nt=20
events. In one case (C-RP set changes), the origin of BSM is limited by=20
BS_Min_Interval while in other case (Recv Non-Preferred BSM) the origin is=
=20
not regulated. My question is whether the latter case should also be limite=
d=20
by BS_Min_Interval or not?
>
>  Regards,
>  Rishabh.
>
>  _______________________________________________
> pim mailing list
> pim@ietf.org
> https://www1.ietf.org/mailman/listinfo/pim
>
>
>
> Thanks & Regards,
> **************************************************
> Sumanta Seal
> Salt Lake City, Kolkata
> West Bengal
> **************************************************
>
>
> ---------------------------------
>  Here=92s a new way to find what you're looking for - Yahoo! Answers

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



From pim-bounces@ietf.org Mon Jan 22 10:21:23 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H90yA-0005se-9c; Mon, 22 Jan 2007 10:20:26 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H90y9-0005gD-6k
	for pim@ietf.org; Mon, 22 Jan 2007 10:20:25 -0500
Received: from hadron.switch.ch ([130.59.4.84])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1H90y1-0000sD-47
	for pim@ietf.org; Mon, 22 Jan 2007 10:20:18 -0500
Received: from hadron.switch.ch.switch.ch (localhost [IPv6:::1])
	by hadron.switch.ch (8.13.8+Sun/8.13.8) with ESMTP id l0MFEqqF011855;
	Mon, 22 Jan 2007 16:14:52 +0100 (CET)
From: Alexander Gall <gall@switch.ch>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <17844.54508.469863.275773@hadron.switch.ch>
Date: Mon, 22 Jan 2007 16:14:52 +0100
To: Rishabh Parekh <rishabh@ipinfusion.com>
Subject: Re: [pim] Use of BS_Min_Interval in BSR draft
In-Reply-To: <200701191500.31785.rishabh@ipinfusion.com>
References: <200701191500.31785.rishabh@ipinfusion.com>
X-Mailer: VM 7.18 under Emacs 21.3.3
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
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

On Fri, 19 Jan 2007 15:00:31 -0800, Rishabh Parekh <rishabh@ipinfusion.com> said:

> The latest BSR draft states "There MUST however be a minimum of
> BS_Min_Interval between each time a BSM is sent." This is mentioned
> in the context of generating BSMs on C-RP set changes.

> However, the C-BSR state machine also originates BSMs in E-BSR state
> for the event "Recieve Non-Preferred BSM". This action is not
> limited by BS_Min_Interval. Should this action also be throttled by
> BS_Min_Interval value? If so, then the action should be to reduce BS
> Timer to BS_Min_Interval if it is greater than this interval.

Throttling is not necessary in a stable network because a candidate
BSR does not generate any BSMs as long as it receives those from the
elected BSR (i.e. this particular event does not occur at all in this
case).  Thrashing during BSR (re-)election is prevented by
BS_Rand_Override, so this issue appears to be moot.

--
Alex


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



From pim-bounces@ietf.org Mon Jan 22 13:20:23 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H93l8-0007Ex-9m; Mon, 22 Jan 2007 13:19:10 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H93l7-0007Ek-FY
	for pim@ietf.org; Mon, 22 Jan 2007 13:19:09 -0500
Received: from mail.ipinfusion.com ([65.223.109.2] helo=gateway.ipinfusion.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H93l5-0005Ca-TO
	for pim@ietf.org; Mon, 22 Jan 2007 13:19:09 -0500
Received: from [10.10.0.156] ([65.223.109.250])
	by gateway.ipinfusion.com (8.11.6/8.11.6) with ESMTP id l0MIIwK01594;
	Mon, 22 Jan 2007 10:18:58 -0800
From: Rishabh Parekh <rishabh@ipinfusion.com>
Organization: IP Infusion
To: Alexander Gall <gall@switch.ch>
Subject: Re: [pim] Use of BS_Min_Interval in BSR draft
Date: Mon, 22 Jan 2007 10:19:12 -0800
User-Agent: KMail/1.9.1
References: <200701191500.31785.rishabh@ipinfusion.com>
	<17844.54508.469863.275773@hadron.switch.ch>
In-Reply-To: <17844.54508.469863.275773@hadron.switch.ch>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200701221019.12706.rishabh@ipinfusion.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
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

Alex,
On Monday 22 January 2007 07:14, Alexander Gall wrote:
> Throttling is not necessary in a stable network because a candidate
> BSR does not generate any BSMs as long as it receives those from the
> elected BSR (i.e. this particular event does not occur at all in this
> case).  Thrashing during BSR (re-)election is prevented by
> BS_Rand_Override, so this issue appears to be moot.
>
The BS_Rand_Override interval at a new C-BSR might not be large enough (and 
thereby contained within the 60 second BS_Period window at E-BSR) to prevent 
the C-BSR from transitioning to E-BSR from P-BSR state and sending out an 
empty BSM. In this case, the E-BSR will send out a BSM (if the new C-BSR is 
inferior) without waiting for BS_Min_Interval.

Even if throttling is not required in above case, I feel that the MUST 
statement in the spec should be modified to explicitly exclude "No Forward" 
BSMs and Unicast BSMs from BS_Min_Interval limit to prevent a 
misunderstanding as evident in earlier mail from Sumanta.

Rishabh.
      
> --
> Alex

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



From pim-bounces@ietf.org Tue Jan 23 11:50:10 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H9Opo-0004xQ-SI; Tue, 23 Jan 2007 11:49:24 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H9Opn-0004ur-5v
	for pim@ietf.org; Tue, 23 Jan 2007 11:49:23 -0500
Received: from hadron.switch.ch ([130.59.4.84])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1H9OpL-00066u-Fn
	for pim@ietf.org; Tue, 23 Jan 2007 11:48:56 -0500
Received: from hadron.switch.ch.switch.ch (localhost [IPv6:::1])
	by hadron.switch.ch (8.13.8+Sun/8.13.8) with ESMTP id l0NGhUUw022411;
	Tue, 23 Jan 2007 17:43:31 +0100 (CET)
From: Alexander Gall <gall@switch.ch>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <17846.15154.874413.240560@hadron.switch.ch>
Date: Tue, 23 Jan 2007 17:43:30 +0100
To: Rishabh Parekh <rishabh@ipinfusion.com>
Subject: Re: [pim] Use of BS_Min_Interval in BSR draft
In-Reply-To: <200701221019.12706.rishabh@ipinfusion.com>
References: <200701191500.31785.rishabh@ipinfusion.com>
	<17844.54508.469863.275773@hadron.switch.ch>
	<200701221019.12706.rishabh@ipinfusion.com>
X-Mailer: VM 7.18 under Emacs 21.3.3
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
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

On Mon, 22 Jan 2007 10:19:12 -0800, Rishabh Parekh <rishabh@ipinfusion.com> said:

> On Monday 22 January 2007 07:14, Alexander Gall wrote:
>> Throttling is not necessary in a stable network because a candidate
>> BSR does not generate any BSMs as long as it receives those from the
>> elected BSR (i.e. this particular event does not occur at all in this
>> case).  Thrashing during BSR (re-)election is prevented by
>> BS_Rand_Override, so this issue appears to be moot.
>> 
> The BS_Rand_Override interval at a new C-BSR might not be large enough (and 
> thereby contained within the 60 second BS_Period window at E-BSR) to prevent 
> the C-BSR from transitioning to E-BSR from P-BSR state and sending out an 
> empty BSM. In this case, the E-BSR will send out a BSM (if the new C-BSR is 
> inferior) without waiting for BS_Min_Interval.

Yes, this can happen, but it has no effect on the receiving routers
because the RP-set doesn't change.  I really don't think it matters.

> Even if throttling is not required in above case, I feel that the MUST 
> statement in the spec should be modified to explicitly exclude "No Forward" 
> BSMs and Unicast BSMs from BS_Min_Interval limit to prevent a 
> misunderstanding as evident in earlier mail from Sumanta.

Note that such BSMs are originated by the DR.  So this is only
relevant if it happens to be the E-BSR.  IMHO, a clarification for
this corner case is not needed.

--
Alex




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



From pim-bounces@ietf.org Wed Jan 24 10:15:25 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H9jpn-0008Ga-0N; Wed, 24 Jan 2007 10:14:47 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H9jpi-00087O-V3; Wed, 24 Jan 2007 10:14:42 -0500
Received: from ns4.neustar.com ([156.154.24.139])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1H9jpi-0005eZ-Ml; Wed, 24 Jan 2007 10:14:42 -0500
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns4.neustar.com (Postfix) with ESMTP id A1DCD2ACA4;
	Wed, 24 Jan 2007 15:14:12 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1H9jpE-0003yt-E2; Wed, 24 Jan 2007 10:14:12 -0500
X-test-idtracker: no
To: IETF-Announce <ietf-announce@ietf.org>
From: The IESG <iesg-secretary@ietf.org>
Message-Id: <E1H9jpE-0003yt-E2@stiedprstage1.ietf.org>
Date: Wed, 24 Jan 2007 10:14:12 -0500
X-Spam-Score: -2.8 (--)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Cc: pim@ietf.org
Subject: [pim] Last Call: draft-ietf-pim-bidir (Bi-directional Protocol 
 Independent Multicast (BIDIR-PIM)) to Proposed Standard 
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: ietf@ietf.org
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

The IESG has received a request from the Protocol Independent Multicast 
WG (pim) to consider the following document:

- 'Bi-directional Protocol Independent Multicast (BIDIR-PIM) '
   <draft-ietf-pim-bidir-08.txt> as a Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send substantive comments to the
ietf@ietf.org mailing lists by 2007-02-07. Exceptionally, 
comments may be sent to iesg@ietf.org instead. In either case, please 
retain the beginning of the Subject line to allow automated sorting.

The file can be obtained via
http://www.ietf.org/internet-drafts/draft-ietf-pim-bidir-08.txt


IESG discussion can be tracked via
https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=5178&rfc_flag=0


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



From pim-bounces@ietf.org Thu Jan 25 17:21:20 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HACxN-0008B5-JL; Thu, 25 Jan 2007 17:20:33 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HACxK-00089p-62; Thu, 25 Jan 2007 17:20:30 -0500
Received: from ns0.neustar.com ([156.154.16.158])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HACxJ-0003hy-W1; Thu, 25 Jan 2007 17:20:30 -0500
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns0.neustar.com (Postfix) with ESMTP id EBB8132A10;
	Thu, 25 Jan 2007 22:20:29 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1HACxJ-0004VZ-Rd; Thu, 25 Jan 2007 17:20:29 -0500
X-test-idtracker: no
To: IETF-Announce <ietf-announce@ietf.org>
From: The IESG <iesg-secretary@ietf.org>
Message-Id: <E1HACxJ-0004VZ-Rd@stiedprstage1.ietf.org>
Date: Thu, 25 Jan 2007 17:20:29 -0500
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Cc: pim@ietf.org
Subject: [pim] Last Call: draft-ietf-pim-mib-v2 (Protocol Independent
 Multicast MIB) to Proposed Standard 
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: ietf@ietf.org
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

The IESG has received a request from the Protocol Independent Multicast 
WG (pim) to consider the following document:

- 'Protocol Independent Multicast MIB '
   <draft-ietf-pim-mib-v2-09.txt> as a Proposed Standard

This Last Call is being repeated in order to call out the normative
reference to the PIM Dense Mode Spec (RFC 3973, an experimental
RFC).  The MIB was designed such that the PIM-DM objects are only
necessary on a system that implements PIM-DM; there is a seperate
MODULE-COMPLIANCE for PIM-DM (pimMIBComplianceDm) which is
only required for devices supporting PIM-DM.  Since the MIB is
sufficiently modular, the IESG would like to use the RFC 3967
mechanism to permit this normative reference.

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send substantive comments to the
ietf@ietf.org mailing lists by 2007-02-08. Exceptionally, 
comments may be sent to iesg@ietf.org instead. In either case, please 
retain the beginning of the Subject line to allow automated sorting.


The file can be obtained via
http://www.ietf.org/internet-drafts/draft-ietf-pim-mib-v2-09.txt


IESG discussion can be tracked via
https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=8944&rfc_flag=0


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



From pim-bounces@ietf.org Fri Jan 26 10:39:36 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HATA6-00085Q-85; Fri, 26 Jan 2007 10:38:46 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HATA5-00081k-Go
	for pim@ietf.org; Fri, 26 Jan 2007 10:38:45 -0500
Received: from mail-red.research.att.com ([192.20.225.110])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HATA2-00075M-AQ
	for pim@ietf.org; Fri, 26 Jan 2007 10:38:45 -0500
Received: from bright.research.att.com (bright.research.att.com
	[135.207.20.189])
	by mail-green.research.att.com (Postfix) with ESMTP id D22318690
	for <pim@ietf.org>; Fri, 26 Jan 2007 10:38:40 -0500 (EST)
Received: (from fenner@localhost)
	by bright.research.att.com (8.13.1/8.12.10/Submit) id l0QFceK6019242;
	Fri, 26 Jan 2007 07:38:40 -0800
From: Bill Fenner <fenner@research.att.com>
Message-Id: <200701261538.l0QFceK6019242@bright.research.att.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
To: pim@ietf.org
Subject: Re: [pim] Last Call: draft-ietf-pim-mib-v2 (Protocol Independent
	Multicast MIB) to Proposed Standard
Date: Fri, 26 Jan 2007 07:38:40 -0800
Versions: dmail (linux) 2.7/makemail 2.14
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 30ac594df0e66ffa5a93eb4c48bcb014
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


Sorry for having to repeat the Last Call.  It's just a
procedural glitch; I forgot to follow the rules for a
standards-track document that has normative references
to an experimental document like PIM-DM.  It will be back
on the telechat on February 8th and we expect it to be
approved then.

  Bill

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



From pim-bounces@ietf.org Fri Jan 26 14:44:24 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HAWz3-0007lU-Rb; Fri, 26 Jan 2007 14:43:37 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HAWz2-0007lP-Is
	for pim@ietf.org; Fri, 26 Jan 2007 14:43:36 -0500
Received: from perseverance-96.encs.concordia.ca ([132.205.96.94]
	helo=perseverance.services.encs.concordia.ca)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HAWz1-0002LJ-8l
	for pim@ietf.org; Fri, 26 Jan 2007 14:43:36 -0500
Received: from [127.0.0.1] (bill@fir.cs.concordia.ca [132.205.45.147])
	by perseverance.services.encs.concordia.ca (envelope-from
	bill@cse.concordia.ca) (8.13.7/8.13.7) with ESMTP id l0QJhXPA024652
	for <pim@ietf.org>; Fri, 26 Jan 2007 14:43:34 -0500
Message-ID: <45BA593A.30005@cse.concordia.ca>
Date: Fri, 26 Jan 2007 14:40:42 -0500
From: JW Atwood <bill@cse.concordia.ca>
Organization: Concordia University, Department of Computer Science and Software
	Engineering
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: pim@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.58 on perseverance.encs.concordia.ca at 2007/01/26
	14:43:34 EST
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 31247fb3be228bb596db9127becad0bc
Subject: [pim] Guaranteeing adjacency for PIM routers--some questions
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

As we have begun to investigate the details of how to secure the 
link-local messages for PIM-SM (see draft-ietf-pim-linklocal), a "more 
general" problem has appeared, which is how to ensure that the 
(supposedly) adjacent routers are

a) who they claim to be,

b) really adjacent.

A solution to this problem will be applicable to all exchanges with 
"adjacent" routers.  Thus, the work could be useful in securing PIM-SM 
link-local exchanges, OSPFv3 exchanges (see RFC 4552) and (possibly) 
other peer exchanges.

As noted in draft-ietf-pim-linklocal, link-local communication actually 
is in the form of a set of independent groups, each with one speaker and 
several listeners.  In each router, there is one incoming Security 
Association (SA) for each peer, plus one outgoing SA for this router as 
a sender.  Thus, in a specific region, there will be as many SSM groups 
as there are routers, and each SSM group will have one SA associated 
with it. The GCKS will maintain membership information of these groups, 
and will generate and distribute keys to all pertinent routers.

In reading the RFC on the Group Domain of Interpretation (RFC 3547), it 
is clear that the operation of any secure group (including the secure 
groups formed by adjacent routers) is going to have two phases: Phase 1 
establishes Security Associations between the Group Controller/Key 
Server (GCKS) and each of the individual routers.  Phase 2 establishes 
the Group Security Association and distributes the keys that will be 
used for the group communication. We expect to use either GDOI itself, 
or necessary parts of it, for phase 2.

The basic principle is simple: whenever a router will be added or 
joined, the GCKS will create a new SA for the SSM group for which the 
added or joined router will be the speaker, and distribute the necessary 
information to the listeners (all the adjacent routers).  The question 
to be resolved is how will the GCKS get the list of adjacent routers to 
the newly joined router?  Two options are possible:

a) Dynamic mode: Take the arrival of a message from a peer as prima 
facie evidence that the peer is adjacent.  (This implies two 
assumptions: 1) that routers will not forward link-local messages, and 
2) that no "rogue" router is on the subnet.)  In this case, the only 
property of the peer to be verified is whether the peer is "legitimate" 
(which should eliminate "rogue" routers). It permits only validating the 
router itself, not its adjacency matrix.  However, the "authority" 
(typically the GCKS) could build up dynamically an image of the topology 
by examining the requests for validation.

The "legitimacy" of a particular router could be based on some 
pre-configured secret, stored in a configuration file on the router, or 
in a unique hardware device associated with the router.

b) Static mode: The GCKS or "authority" will maintain an adjacency 
matrix (which in turn requires that the system administrator maintain 
the information in a machine-accessible format). However, it permits 
maintaining significantly more control over the router-to-router 
communication within the network.

Clearly the first option requires that less information be maintained by 
the "authority", whereas the second option may reduce the traffic flow.

Our primary question is, "Is it worthwhile exploring none, the first, 
the second, or both options?"  A secondary question is, "Will any of 
these options be operationally viable, or will they require the 
maintenance of information where the average systems administrator will 
find it difficult to justify the time expenditure?"

 

Any comments from the list will be most appreciated, and will guide us 
in our development of a solution to the link-local security problem.

-- 

Dr. J.W. Atwood, Eng.             tel:   +1 (514) 848-2424 x3046
Professor Emeritus                fax:   +1 (514) 848-2830
Department of Computer Science
   and Software Engineering
Concordia University EV 3.185     email: bill@cse.concordia.ca
1455 de Maisonneuve Blvd. West    http: //users.encs.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 Fri Jan 26 19:30:08 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HAbQi-0006iG-BL; Fri, 26 Jan 2007 19:28:28 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HAbQh-0006iA-1h
	for pim@ietf.org; Fri, 26 Jan 2007 19:28:27 -0500
Received: from sj-iport-6.cisco.com ([171.71.176.117])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HAbQc-00050L-IB
	for pim@ietf.org; Fri, 26 Jan 2007 19:28:27 -0500
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-6.cisco.com with ESMTP; 26 Jan 2007 16:28:22 -0800
X-IronPort-AV: i="4.13,245,1167638400"; 
	d="scan'208"; a="105960491:sNHT41648877"
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238])
	by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l0R0SLTx011297
	for <pim@ietf.org>; Fri, 26 Jan 2007 16:28:21 -0800
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com
	[128.107.191.63])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id l0R0SLUw023084
	for <pim@ietf.org>; Fri, 26 Jan 2007 16:28:21 -0800 (PST)
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by
	xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 26 Jan 2007 16:28:19 -0800
Received: from irp-view7.cisco.com ([171.70.65.144]) by
	xfe-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 26 Jan 2007 16:28:19 -0800
Date: Fri, 26 Jan 2007 16:28:19 -0800 (PST)
From: Mike McBride <mmcbride@cisco.com>
To: pim@ietf.org
Subject: [pim] New PIM Charter and milestones
Message-ID: <Pine.GSO.4.63.0701261621230.11346@irp-view7.cisco.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-OriginalArrivalTime: 27 Jan 2007 00:28:19.0603 (UTC)
	FILETIME=[0B785630:01C741AA]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1662; t=1169857701;
	x=1170721701; c=relaxed/simple; s=sjdkim2002;
	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]=20New=20PIM=20Charter=20and=20milestones
	|Sender:=20; bh=P7xkkYzXbkDiMnDCvr0AYzmMCed8JwYLjscahbdaxiw=;
	b=v/aexDOxnZ7sX/k+k531zlw/NPrlAHDMswT8VW2GS8LSn7O4XtGVwG8o9a/HHIysEOUOGwnL
	PIIWzQTxjtwzMtfX6C0pwKQgPiBsgGRjXByPULaEwYz5XXdY66hnDQbU;
Authentication-Results: sj-dkim-2; header.From=mmcbride@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim2002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
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

Here is a second pass at pimwg rechartering text. Please review. I added a 
'may' with BSR which 'may' satisfy Lenny's previous concern.

Description of Working Group:

The Protocol Independent Multicast (PIM) Working Group has completed the 
standardization of PIM with RFC 4601. The WG has determined there is 
additional work to be accomplished and is chartered to standardize 
extensions to RFC 4601 - Protocol Independent Multicast Version 2 - Sparse 
Mode. These PIM extensions could involve multipoint label switching, 
reliability, resiliency, scalability, management, security and VPNs. 
Additional work on PIM-BIDIR and BSR may also be necessary. The working 
group will continue to specify the MIBs required for PIM and its 
enhancements. The PIM WG will further enhance RFC4601 as an even more 
scalable, efficient and robust multicast routing protocol, which is 
capable of supporting thousands of groups, different types of multicast 
applications, and all major underlying layer-2 subnetwork technologies. 
The working group will determine if a Version 3 of PIM is required.

Goals and Milestones:

Mar    2006     Ratify new WG charter and milestones
Jul    2006     Submit the BSR MIB as a Proposed Standard
Jul    2006     Develop a reliable pim specification
Jul    2006     Submit a generic TLV PIM Join Attribute Proposed Standard 
draft
Jul    2006     Submit RPF Vector (use of PIM Join Attribute) as a 
Proposed Standard
Jul    2006     Submit a mechanism to authenticate PIM link local messages 
using AH as Proposed Standard
Jul    2006     Submit an Informational PIM last hop threats document.

-mike

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



From pim-bounces@ietf.org Sun Jan 28 14:38:34 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HBFp5-0003lM-QY; Sun, 28 Jan 2007 14:36:19 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HBFp4-0003lF-4O
	for pim@ietf.org; Sun, 28 Jan 2007 14:36:18 -0500
Received: from kremlin.juniper.net ([207.17.137.120])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HBFp2-0002z3-PV
	for pim@ietf.org; Sun, 28 Jan 2007 14:36:18 -0500
Received: from unknown (HELO beta.jnpr.net) ([172.24.18.109])
	by kremlin.juniper.net with ESMTP; 28 Jan 2007 11:36:16 -0800
X-IronPort-AV: i="4.13,248,1167638400"; 
	d="scan'208"; a="647244532:sNHT31327544"
Received: from sapphire.juniper.net ([172.17.28.108]) by beta.jnpr.net over
	TLS secured channel with Microsoft SMTPSVC(6.0.3790.1830); 
	Sun, 28 Jan 2007 11:36:16 -0800
Date: Sun, 28 Jan 2007 11:36:15 -0800 (PST)
From: Rahul Aggarwal <rahul@juniper.net>
To: Mike McBride <mmcbride@cisco.com>
Subject: Re: [pim] New PIM Charter and milestones
In-Reply-To: <Pine.GSO.4.63.0701261621230.11346@irp-view7.cisco.com>
Message-ID: <20070128113358.J85861@sapphire.juniper.net>
References: <Pine.GSO.4.63.0701261621230.11346@irp-view7.cisco.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-OriginalArrivalTime: 28 Jan 2007 19:36:16.0143 (UTC)
	FILETIME=[938009F0:01C74313]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44
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


Hi Mike,

Please see below:

On Fri, 26 Jan 2007, Mike McBride wrote:

> Here is a second pass at pimwg rechartering text. Please review. I added a
> 'may' with BSR which 'may' satisfy Lenny's previous concern.
>
> Description of Working Group:
>
> The Protocol Independent Multicast (PIM) Working Group has completed the
> standardization of PIM with RFC 4601. The WG has determined there is
> additional work to be accomplished and is chartered to standardize
> extensions to RFC 4601 - Protocol Independent Multicast Version 2 - Sparse
> Mode. These PIM extensions could involve multipoint label switching,

"multipoint label switching" is within the charter of the MPLS WG. This
shouldn't be a charter item in the PIM WG.

> reliability, resiliency, scalability, management, security and VPNs.

Multicast in L2VPNs is in the charter of L2VPN WG, and multicast
in L3VPNs is in the charter of L3VPN WG. VPNs shouldn't be a charter item
in the PIM WG.

rahul


> Additional work on PIM-BIDIR and BSR may also be necessary. The working
> group will continue to specify the MIBs required for PIM and its
> enhancements. The PIM WG will further enhance RFC4601 as an even more
> scalable, efficient and robust multicast routing protocol, which is
> capable of supporting thousands of groups, different types of multicast
> applications, and all major underlying layer-2 subnetwork technologies.
> The working group will determine if a Version 3 of PIM is required.
>
> Goals and Milestones:
>
> Mar    2006     Ratify new WG charter and milestones
> Jul    2006     Submit the BSR MIB as a Proposed Standard
> Jul    2006     Develop a reliable pim specification
> Jul    2006     Submit a generic TLV PIM Join Attribute Proposed Standard
> draft
> Jul    2006     Submit RPF Vector (use of PIM Join Attribute) as a
> Proposed Standard
> Jul    2006     Submit a mechanism to authenticate PIM link local messages
> using AH as Proposed Standard
> Jul    2006     Submit an Informational PIM last hop threats document.
>
> -mike
>
> _______________________________________________
> 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 Mon Jan 29 00:11:43 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HBOn7-00053x-IH; Mon, 29 Jan 2007 00:10:53 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HBOn6-00053k-Bz
	for pim@ietf.org; Mon, 29 Jan 2007 00:10:52 -0500
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HBOn4-0000F7-VN
	for pim@ietf.org; Mon, 29 Jan 2007 00:10:52 -0500
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
	by sj-iport-5.cisco.com with ESMTP; 28 Jan 2007 21:10:50 -0800
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254])
	by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l0T5AkOf025952; 
	Sun, 28 Jan 2007 21:10:46 -0800
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com
	[128.107.191.100])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l0T5AlGk018798;
	Sun, 28 Jan 2007 21:10:47 -0800 (PST)
Received: from xmb-sjc-216.amer.cisco.com ([171.70.151.184]) by
	xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Sun, 28 Jan 2007 21:10:46 -0800
Received: from 10.21.97.11 ([10.21.97.11]) by xmb-sjc-216.amer.cisco.com
	([171.70.151.184]) with Microsoft Exchange Server HTTP-DAV ; 
	Mon, 29 Jan 2007 05:10:46 +0000
User-Agent: Microsoft-Entourage/11.3.3.061214
Date: Sun, 28 Jan 2007 21:10:46 -0800
Subject: Re: [pim] New PIM Charter and milestones
From: ycai <ycai@cisco.com>
To: Rahul Aggarwal <rahul@juniper.net>, Mike McBride <mmcbride@cisco.com>
Message-ID: <C1E2C1D6.1079D%ycai@cisco.com>
Thread-Topic: [pim] New PIM Charter and milestones
Thread-Index: AcdDY9UiE2beY69XEduqmwARJHYecA==
In-Reply-To: <20070128113358.J85861@sapphire.juniper.net>
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 29 Jan 2007 05:10:46.0778 (UTC)
	FILETIME=[D59985A0:01C74363]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2752; t=1170047446;
	x=1170911446; c=relaxed/simple; s=sjdkim1004;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=ycai@cisco.com;
	z=From:=20ycai=20<ycai@cisco.com>
	|Subject:=20Re=3A=20[pim]=20New=20PIM=20Charter=20and=20milestones
	|Sender:=20 |To:=20Rahul=20Aggarwal=20<rahul@juniper.net>,
	=20Mike=20McBride=20<mmcbri de@cisco.com>
	|Content-Type:=20text/plain=3B=0A=09charset=3D=22US-ASCII=22
	|Content-Transfer-Encoding:=207bit |MIME-Version:=201.0;
	bh=aMvz17b0tbMmzkCFDHIkFX7bWjaTyjd5JffI8vP1JzE=;
	b=STjT6eygNXBsntHWknNBrJ0rEUzknw+dO2HjKseUFHtIs1jsW5QqE8bwYT2e6Oi6cZuQ4kzR
	9GIjUtSY5Ae8pdkk8INsifOv8yyF+shkLGVIeI5pl6Da3qI7ZL2Km9u912uwt/OY2wfd7v+MJ4
	bJ6dRiEZe4R0PoV/8QVJ8euJ4=;
Authentication-Results: sj-dkim-1; header.From=ycai@cisco.com; dkim=pass (si
	g from cisco.com/sjdkim1004 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bdc523f9a54890b8a30dd6fd53d5d024
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




On 1/28/07 11:36 AM, "Rahul Aggarwal" <rahul@juniper.net> wrote:

> 
> Hi Mike,
> 
> Please see below:
> 
> On Fri, 26 Jan 2007, Mike McBride wrote:
> 
>> Here is a second pass at pimwg rechartering text. Please review. I added a
>> 'may' with BSR which 'may' satisfy Lenny's previous concern.
>> 
>> Description of Working Group:
>> 
>> The Protocol Independent Multicast (PIM) Working Group has completed the
>> standardization of PIM with RFC 4601. The WG has determined there is
>> additional work to be accomplished and is chartered to standardize
>> extensions to RFC 4601 - Protocol Independent Multicast Version 2 - Sparse
>> Mode. These PIM extensions could involve multipoint label switching,
> 
> "multipoint label switching" is within the charter of the MPLS WG. This
> shouldn't be a charter item in the PIM WG.
> 
>> reliability, resiliency, scalability, management, security and VPNs.
> 
> Multicast in L2VPNs is in the charter of L2VPN WG, and multicast
> in L3VPNs is in the charter of L3VPN WG. VPNs shouldn't be a charter item
> in the PIM WG.
> 
> rahul
> 

I think you missed the words "PIM extensions".

And I also did a search of "PIM" in the charters of the three WGs you
mentioned, and didn't come up with any relevant text mentioning possible
modification to PIM.


> 
>> Additional work on PIM-BIDIR and BSR may also be necessary. The working
>> group will continue to specify the MIBs required for PIM and its
>> enhancements. The PIM WG will further enhance RFC4601 as an even more
>> scalable, efficient and robust multicast routing protocol, which is
>> capable of supporting thousands of groups, different types of multicast
>> applications, and all major underlying layer-2 subnetwork technologies.
>> The working group will determine if a Version 3 of PIM is required.
>> 
>> Goals and Milestones:
>> 
>> Mar    2006     Ratify new WG charter and milestones
>> Jul    2006     Submit the BSR MIB as a Proposed Standard
>> Jul    2006     Develop a reliable pim specification
>> Jul    2006     Submit a generic TLV PIM Join Attribute Proposed Standard
>> draft
>> Jul    2006     Submit RPF Vector (use of PIM Join Attribute) as a
>> Proposed Standard
>> Jul    2006     Submit a mechanism to authenticate PIM link local messages
>> using AH as Proposed Standard
>> Jul    2006     Submit an Informational PIM last hop threats document.
>> 
>> -mike
>> 
>> _______________________________________________
>> 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


-- 
Yiqun

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



From pim-bounces@ietf.org Mon Jan 29 10:57:00 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HBYre-0000Dg-7p; Mon, 29 Jan 2007 10:56:14 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HBYrd-0000C7-5a
	for pim@ietf.org; Mon, 29 Jan 2007 10:56:13 -0500
Received: from sj-iport-6.cisco.com ([171.71.176.117])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HBYr9-0005VI-Ky
	for pim@ietf.org; Mon, 29 Jan 2007 10:56:13 -0500
Received: from sj-dkim-3.cisco.com ([171.71.179.195])
	by sj-iport-6.cisco.com with ESMTP; 29 Jan 2007 07:54:44 -0800
X-IronPort-AV: i="4.13,253,1167638400"; 
	d="scan'208"; a="106570937:sNHT46859877"
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254])
	by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id l0TFsgH8017219; 
	Mon, 29 Jan 2007 07:54:42 -0800
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com
	[128.107.191.100])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l0TFsOH4014469;
	Mon, 29 Jan 2007 07:54:41 -0800 (PST)
Received: from xmb-sjc-228.amer.cisco.com ([128.107.191.125]) by
	xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 29 Jan 2007 07:54:34 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
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] New PIM Charter and milestones
Date: Mon, 29 Jan 2007 07:54:33 -0800
Message-ID: <D7889EF97F07A0458785320F43C43B6B02C16C2A@xmb-sjc-228.amer.cisco.com>
In-Reply-To: <20070128113358.J85861@sapphire.juniper.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [pim] New PIM Charter and milestones
Thread-Index: AcdDFCysY/EWD9GxS2imZGXo3tzJegAp6JYA
References: <Pine.GSO.4.63.0701261621230.11346@irp-view7.cisco.com>
	<20070128113358.J85861@sapphire.juniper.net>
From: "John Meylor \(jmeylor\)" <jmeylor@cisco.com>
To: "Rahul Aggarwal" <rahul@juniper.net>,
	"Michael McBride \(mmcbride\)" <mmcbride@cisco.com>
X-OriginalArrivalTime: 29 Jan 2007 15:54:34.0600 (UTC)
	FILETIME=[C5936680:01C743BD]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=3171; t=1170086082;
	x=1170950082; c=relaxed/simple; s=sjdkim3002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=jmeylor@cisco.com;
	z=From:=20=22John=20Meylor=20\(jmeylor\)=22=20<jmeylor@cisco.com>
	|Subject:=20RE=3A=20[pim]=20New=20PIM=20Charter=20and=20milestones
	|Sender:=20; bh=NcHvHoiMbrYbsvKZ5oxzSV/A1z0MyRXhJHrEpCmfSbM=;
	b=rudhG0iA1o85KsVeI1vV9L4QIe4NB76Wk1TajyF8i90cV4HBnquVKjY6XLM90xt2tFBPXNUv
	NTT33pmlJGjsTGCR1hd6PaIVVupf1pKQUP79K5yWDJ/cKEJ7qL8HVqKR;
Authentication-Results: sj-dkim-3; header.From=jmeylor@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim3002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf3becbbd6d1a45acbe2ffd4ab88bdc2
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

Rahul,=20

> -----Original Message-----
> From: Rahul Aggarwal [mailto:rahul@juniper.net]=20
> Sent: Sunday, January 28, 2007 11:36 AM
> To: Michael McBride (mmcbride)
> Cc: pim@ietf.org
> Subject: Re: [pim] New PIM Charter and milestones
>=20
>=20
> Hi Mike,
>=20
> Please see below:
>=20
> On Fri, 26 Jan 2007, Mike McBride wrote:
>=20
> > Here is a second pass at pimwg rechartering text. Please review. I=20
> > added a 'may' with BSR which 'may' satisfy Lenny's previous concern.
> >
> > Description of Working Group:
> >
> > The Protocol Independent Multicast (PIM) Working Group has=20
> completed=20
> > the standardization of PIM with RFC 4601. The WG has=20
> determined there=20
> > is additional work to be accomplished and is chartered to=20
> standardize=20
> > extensions to RFC 4601 - Protocol Independent Multicast Version 2 -=20
> > Sparse Mode. These PIM extensions could involve multipoint label=20
> > switching,
>=20
> "multipoint label switching" is within the charter of the=20
> MPLS WG. This shouldn't be a charter item in the PIM WG.

PIM WG should address any/all pim enhancement
work necessary to support ongoing multipoint label switching

btw, its logical to expect that a system effecting several protocols
has work in more than one working group

> > reliability, resiliency, scalability, management, security and VPNs.
>=20
> Multicast in L2VPNs is in the charter of L2VPN WG, and=20
> multicast in L3VPNs is in the charter of L3VPN WG. VPNs=20
> shouldn't be a charter item in the PIM WG.

again, PIM WG should address PIM related components of *VPN
systems. =20


 john


>=20
> rahul
>=20
>=20
> > Additional work on PIM-BIDIR and BSR may also be necessary. The=20
> > working group will continue to specify the MIBs required=20
> for PIM and=20
> > its enhancements. The PIM WG will further enhance RFC4601=20
> as an even=20
> > more scalable, efficient and robust multicast routing=20
> protocol, which=20
> > is capable of supporting thousands of groups, different types of=20
> > multicast applications, and all major underlying layer-2=20
> subnetwork technologies.
> > The working group will determine if a Version 3 of PIM is required.
> >
> > Goals and Milestones:
> >
> > Mar    2006     Ratify new WG charter and milestones
> > Jul    2006     Submit the BSR MIB as a Proposed Standard
> > Jul    2006     Develop a reliable pim specification
> > Jul    2006     Submit a generic TLV PIM Join Attribute=20
> Proposed Standard
> > draft
> > Jul    2006     Submit RPF Vector (use of PIM Join Attribute) as a
> > Proposed Standard
> > Jul    2006     Submit a mechanism to authenticate PIM link=20
> local messages
> > using AH as Proposed Standard
> > Jul    2006     Submit an Informational PIM last hop=20
> threats document.
> >
> > -mike
> >
> > _______________________________________________
> > pim mailing list
> > pim@ietf.org
> > https://www1.ietf.org/mailman/listinfo/pim
> >
>=20
> _______________________________________________
> pim mailing list
> pim@ietf.org
> https://www1.ietf.org/mailman/listinfo/pim
>=20

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



From pim-bounces@ietf.org Mon Jan 29 11:18:46 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HBZD4-0002gg-JQ; Mon, 29 Jan 2007 11:18:22 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HBZD3-0002ev-H2
	for pim@ietf.org; Mon, 29 Jan 2007 11:18:21 -0500
Received: from colo-dns-ext1.juniper.net ([207.17.137.57])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HBZCx-0000sq-IC
	for pim@ietf.org; Mon, 29 Jan 2007 11:18:21 -0500
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 l0TGICX93782; 
	Mon, 29 Jan 2007 08:18:14 -0800 (PST)
	(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 l0TGI7B23317;
	Mon, 29 Jan 2007 08:18:07 -0800 (PST)
	(envelope-from yakov@juniper.net)
Message-Id: <200701291618.l0TGI7B23317@merlot.juniper.net>
To: "John Meylor \(jmeylor\)" <jmeylor@cisco.com>
Subject: Re: [pim] New PIM Charter and milestones 
In-Reply-To: Your message of "Mon, 29 Jan 2007 07:54:33 PST."
	<D7889EF97F07A0458785320F43C43B6B02C16C2A@xmb-sjc-228.amer.cisco.com> 
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <67275.1170087487.1@juniper.net>
Date: Mon, 29 Jan 2007 08:18:07 -0800
From: Yakov Rekhter <yakov@juniper.net>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
Cc: Rahul Aggarwal <rahul@juniper.net>, pim@ietf.org,
	"Michael McBride \(mmcbride\)" <mmcbride@cisco.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>
Errors-To: pim-bounces@ietf.org

John,

> > -----Original Message-----
> > From: Rahul Aggarwal [mailto:rahul@juniper.net] 
> > Sent: Sunday, January 28, 2007 11:36 AM
> > To: Michael McBride (mmcbride)
> > Cc: pim@ietf.org
> > Subject: Re: [pim] New PIM Charter and milestones
> > 
> > 
> > Hi Mike,
> > 
> > Please see below:
> > 
> > On Fri, 26 Jan 2007, Mike McBride wrote:
> > 
> > > Here is a second pass at pimwg rechartering text. Please review. I 
> > > added a 'may' with BSR which 'may' satisfy Lenny's previous concern.
> > >
> > > Description of Working Group:
> > >
> > > The Protocol Independent Multicast (PIM) Working Group has 
> > > completed 
> > > the standardization of PIM with RFC 4601. The WG has 
> > > determined there 
> > > is additional work to be accomplished and is chartered to 
> > > standardize 
> > > extensions to RFC 4601 - Protocol Independent Multicast Version 2 - 
> > > Sparse Mode. These PIM extensions could involve multipoint label 
> > > switching,
> > 
> > "multipoint label switching" is within the charter of the 
> > MPLS WG. This shouldn't be a charter item in the PIM WG.
> 
> PIM WG should address any/all pim enhancement
> work necessary to support ongoing multipoint label switching

To support multipoint label switching *no* PIM enhancement work is
necessary. This is because multipoint label switching is supported
with either RSVP-TE, or with mLDP, and neither of these require any
PIM enhancement work.
  
Yakov.

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



From pim-bounces@ietf.org Mon Jan 29 14:04:39 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HBbn9-00073A-KM; Mon, 29 Jan 2007 14:03:47 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HBbn9-000735-3V
	for pim@ietf.org; Mon, 29 Jan 2007 14:03:47 -0500
Received: from colo-dns-ext1.juniper.net ([207.17.137.57])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HBbn7-00061v-Ni
	for pim@ietf.org; Mon, 29 Jan 2007 14:03:47 -0500
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 l0TJ3jX98788; 
	Mon, 29 Jan 2007 11:03:45 -0800 (PST)
	(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 l0TJ3eB69638;
	Mon, 29 Jan 2007 11:03:40 -0800 (PST)
	(envelope-from yakov@juniper.net)
Message-Id: <200701291903.l0TJ3eB69638@merlot.juniper.net>
To: "John Meylor \(jmeylor\)" <jmeylor@cisco.com>
Subject: Re: [pim] New PIM Charter and milestones 
In-Reply-To: Your message of "Mon, 29 Jan 2007 07:54:33 PST."
	<D7889EF97F07A0458785320F43C43B6B02C16C2A@xmb-sjc-228.amer.cisco.com> 
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <90902.1170097420.1@juniper.net>
Date: Mon, 29 Jan 2007 11:03:40 -0800
From: Yakov Rekhter <yakov@juniper.net>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f607d15ccc2bc4eaf3ade8ffa8af02a0
Cc: Rahul Aggarwal <rahul@juniper.net>, pim@ietf.org,
	"Michael McBride \(mmcbride\)" <mmcbride@cisco.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>
Errors-To: pim-bounces@ietf.org

John,

> > -----Original Message-----
> > From: Rahul Aggarwal [mailto:rahul@juniper.net] 
> > Sent: Sunday, January 28, 2007 11:36 AM
> > To: Michael McBride (mmcbride)
> > Cc: pim@ietf.org
> > Subject: Re: [pim] New PIM Charter and milestones
> > 
> > 
> > Hi Mike,
> > 
> > Please see below:
> > 
> > On Fri, 26 Jan 2007, Mike McBride wrote:
> > 
> > > Here is a second pass at pimwg rechartering text. Please review. I 
> > > added a 'may' with BSR which 'may' satisfy Lenny's previous concern.
> > >
> > > Description of Working Group:
> > >
> > > The Protocol Independent Multicast (PIM) Working Group has 
> > completed 
> > > the standardization of PIM with RFC 4601. The WG has 
> > determined there 
> > > is additional work to be accomplished and is chartered to 
> > standardize 
> > > extensions to RFC 4601 - Protocol Independent Multicast Version 2 - 
> > > Sparse Mode. These PIM extensions could involve multipoint label 
> > > switching,
> > 
> > "multipoint label switching" is within the charter of the 
> > MPLS WG. This shouldn't be a charter item in the PIM WG.
> 
> PIM WG should address any/all pim enhancement
> work necessary to support ongoing multipoint label switching
> 
> btw, its logical to expect that a system effecting several protocols
> has work in more than one working group
> 
> > > reliability, resiliency, scalability, management, security and VPNs.
> > 
> > Multicast in L2VPNs is in the charter of L2VPN WG, and 
> > multicast in L3VPNs is in the charter of L3VPN WG. VPNs 
> > shouldn't be a charter item in the PIM WG.
> 
> again, PIM WG should address PIM related components of *VPN
> systems.  

Yes, assuming that multicast in L2VPNs and L3VPNs require extensions
to PIM. Whether such extensions are required is to be determined
by L2VPN and L3VPN WGs. With this in mind the charter instead of
saying that "These PIM extensions could involved... VPNs" should
say the following:

   If L2VPN or L3VPN WGs determine that support for multicast
   in L2VPNs and/or L3VPNs requires extensions to PIM, then such 
   extensions could be developed within the PIM WG.

Yakov.

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



From pim-bounces@ietf.org Mon Jan 29 15:42:35 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HBdK9-0004Jh-61; Mon, 29 Jan 2007 15:41:57 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HBdK7-0004IG-CS
	for pim@ietf.org; Mon, 29 Jan 2007 15:41:55 -0500
Received: from sj-iport-4.cisco.com ([171.68.10.86])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HBdK6-0005GH-2Q
	for pim@ietf.org; Mon, 29 Jan 2007 15:41:55 -0500
Received: from sj-dkim-5.cisco.com ([171.68.10.79])
	by sj-iport-4.cisco.com with ESMTP; 29 Jan 2007 12:41:53 -0800
Received: from sj-core-4.cisco.com (sj-core-4.cisco.com [171.68.223.138])
	by sj-dkim-5.cisco.com (8.12.11/8.12.11) with ESMTP id l0TKfrYg026960; 
	Mon, 29 Jan 2007 12:41:53 -0800
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com
	[128.107.191.63])
	by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id l0TKfinT025911;
	Mon, 29 Jan 2007 12:41:53 -0800 (PST)
Received: from xmb-sjc-228.amer.cisco.com ([128.107.191.125]) by
	xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 29 Jan 2007 12:41:51 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
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] New PIM Charter and milestones 
Date: Mon, 29 Jan 2007 12:41:50 -0800
Message-ID: <D7889EF97F07A0458785320F43C43B6B02C16E17@xmb-sjc-228.amer.cisco.com>
In-Reply-To: <200701291618.l0TGI7B23317@merlot.juniper.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [pim] New PIM Charter and milestones 
Thread-Index: AcdDwRt0YPXvsF0MQduK443+4UFjAQAHhQsw
References: Your message of "Mon, 29 Jan 2007 07:54:33 PST."
	<D7889EF97F07A0458785320F43C43B6B02C16C2A@xmb-sjc-228.amer.cisco.com>
	<200701291618.l0TGI7B23317@merlot.juniper.net>
From: "John Meylor \(jmeylor\)" <jmeylor@cisco.com>
To: "Yakov Rekhter" <yakov@juniper.net>
X-OriginalArrivalTime: 29 Jan 2007 20:41:51.0271 (UTC)
	FILETIME=[E76EAB70:01C743E5]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2190; t=1170103313;
	x=1170967313; c=relaxed/simple; s=sjdkim5002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=jmeylor@cisco.com;
	z=From:=20=22John=20Meylor=20\(jmeylor\)=22=20<jmeylor@cisco.com>
	|Subject:=20RE=3A=20[pim]=20New=20PIM=20Charter=20and=20milestones=20
	|Sender:=20; bh=McMXdfSIsiC37OZo2t+t9AAo3R3208NIznL/o+4oUXc=;
	b=c8bYSUskmzqxDtu7m/N/8VUdE/MZIItOWs92mUsoMy5QXh59w80oUXBJF2K1gVytqY7irDR/
	2cuPYGh9GIaWCH8WXS/3nND8ksS9tCrry1ZD5F3rftx465HAN2fc+SdC;
Authentication-Results: sj-dkim-5; header.From=jmeylor@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim5002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15
Cc: Rahul Aggarwal <rahul@juniper.net>, pim@ietf.org,
	"Michael McBride \(mmcbride\)" <mmcbride@cisco.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>
Errors-To: pim-bounces@ietf.org

Yakov,

> -----Original Message-----
> From: Yakov Rekhter [mailto:yakov@juniper.net]=20
> Sent: Monday, January 29, 2007 8:18 AM
> To: John Meylor (jmeylor)
> Cc: Rahul Aggarwal; Michael McBride (mmcbride); pim@ietf.org
> Subject: Re: [pim] New PIM Charter and milestones=20
>=20
> John,
>=20
> > > -----Original Message-----
> > > From: Rahul Aggarwal [mailto:rahul@juniper.net]
> > > Sent: Sunday, January 28, 2007 11:36 AM
> > > To: Michael McBride (mmcbride)
> > > Cc: pim@ietf.org
> > > Subject: Re: [pim] New PIM Charter and milestones
> > >=20
> > >=20
> > > Hi Mike,
> > >=20
> > > Please see below:
> > >=20
> > > On Fri, 26 Jan 2007, Mike McBride wrote:
> > >=20
> > > > Here is a second pass at pimwg rechartering text.=20
> Please review. I=20
> > > > added a 'may' with BSR which 'may' satisfy Lenny's=20
> previous concern.
> > > >
> > > > Description of Working Group:
> > > >
> > > > The Protocol Independent Multicast (PIM) Working Group has=20
> > > > completed the standardization of PIM with RFC 4601. The WG has=20
> > > > determined there is additional work to be accomplished and is=20
> > > > chartered to standardize extensions to RFC 4601 - Protocol=20
> > > > Independent Multicast Version 2 - Sparse Mode. These PIM=20
> > > > extensions could involve multipoint label switching,
> > >=20
> > > "multipoint label switching" is within the charter of the=20
> MPLS WG.=20
> > > This shouldn't be a charter item in the PIM WG.
> >=20
> > PIM WG should address any/all pim enhancement work necessary to=20
> > support ongoing multipoint label switching
>=20
> To support multipoint label switching *no* PIM enhancement=20
> work is necessary. This is because multipoint label switching=20
> is supported with either RSVP-TE, or with mLDP, and neither=20
> of these require any PIM enhancement work.

PIM WG should consider implication of VPN service on PIM whether its
a component of that service (as in widely deployed mVPN GRE solution
described in L3VPN drafts) or whether it interfaces with that service
at VPN edge (as it can with multipoint label switched solutions)

 john


>  =20
> Yakov.
>=20

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



From pim-bounces@ietf.org Tue Jan 30 09:34:22 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HBu2J-0002Uh-CE; Tue, 30 Jan 2007 09:32:39 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HBu2H-0002UL-Rt
	for pim@ietf.org; Tue, 30 Jan 2007 09:32:37 -0500
Received: from colo-dns-ext1.juniper.net ([207.17.137.57])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HBu1s-0006Og-8k
	for pim@ietf.org; Tue, 30 Jan 2007 09:32:37 -0500
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 l0UEWBX14335; 
	Tue, 30 Jan 2007 06:32:11 -0800 (PST)
	(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 l0UEW6B09831;
	Tue, 30 Jan 2007 06:32:06 -0800 (PST)
	(envelope-from yakov@juniper.net)
Message-Id: <200701301432.l0UEW6B09831@merlot.juniper.net>
To: "John Meylor \(jmeylor\)" <jmeylor@cisco.com>
Subject: Re: [pim] New PIM Charter and milestones 
In-Reply-To: Your message of "Mon, 29 Jan 2007 12:41:50 PST."
	<D7889EF97F07A0458785320F43C43B6B02C16E17@xmb-sjc-228.amer.cisco.com> 
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <3767.1170167526.1@juniper.net>
Date: Tue, 30 Jan 2007 06:32:06 -0800
From: Yakov Rekhter <yakov@juniper.net>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d0bdc596f8dd1c226c458f0b4df27a88
Cc: Rahul Aggarwal <rahul@juniper.net>, pim@ietf.org,
	"Michael McBride \(mmcbride\)" <mmcbride@cisco.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>
Errors-To: pim-bounces@ietf.org

John,

> Yakov,
> 
> > -----Original Message-----
> > From: Yakov Rekhter [mailto:yakov@juniper.net] 
> > Sent: Monday, January 29, 2007 8:18 AM
> > To: John Meylor (jmeylor)
> > Cc: Rahul Aggarwal; Michael McBride (mmcbride); pim@ietf.org
> > Subject: Re: [pim] New PIM Charter and milestones 
> > 
> > John,
> > 
> > > > -----Original Message-----
> > > > From: Rahul Aggarwal [mailto:rahul@juniper.net]
> > > > Sent: Sunday, January 28, 2007 11:36 AM
> > > > To: Michael McBride (mmcbride)
> > > > Cc: pim@ietf.org
> > > > Subject: Re: [pim] New PIM Charter and milestones
> > > > 
> > > > 
> > > > Hi Mike,
> > > > 
> > > > Please see below:
> > > > 
> > > > On Fri, 26 Jan 2007, Mike McBride wrote:
> > > > 
> > > > > Here is a second pass at pimwg rechartering text. 
> > > > > Please review. I 
> > > > > added a 'may' with BSR which 'may' satisfy Lenny's 
> > > > > previous concern.
> > > > >
> > > > > Description of Working Group:
> > > > >
> > > > > The Protocol Independent Multicast (PIM) Working Group has 
> > > > > completed the standardization of PIM with RFC 4601. The WG has 
> > > > > determined there is additional work to be accomplished and is 
> > > > > chartered to standardize extensions to RFC 4601 - Protocol 
> > > > > Independent Multicast Version 2 - Sparse Mode. These PIM 
> > > > > extensions could involve multipoint label switching,
> > > > 
> > > > "multipoint label switching" is within the charter of the 
> > > > MPLS WG. This shouldn't be a charter item in the PIM WG.
> > > 
> > > PIM WG should address any/all pim enhancement work necessary to 
> > > support ongoing multipoint label switching
> > 
> > To support multipoint label switching *no* PIM enhancement 
> > work is necessary. This is because multipoint label switching 
> > is supported with either RSVP-TE, or with mLDP, and neither 
> > of these require any PIM enhancement work.
> 
> PIM WG should consider implication of VPN service on PIM whether its
> a component of that service (as in widely deployed mVPN GRE solution
> described in L3VPN drafts) or whether it interfaces with that service
> at VPN edge (as it can with multipoint label switched solutions)

With this in mind replace

   These PIM extensions could involve multipoint label switching, 
   reliability, resiliency, scalability, management, security and VPNs.

with the following:

   These PIM extensions could involve reliability, resiliency, 
   scalability, management, and security.
   
   If L2VPN or L3VPN WGs determine that support for multicast
   in L2VPNs and/or L3VPNs requires extensions to PIM, then such 
   extensions could be developed within the PIM WG.

Yakov.

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



