From mailman-bounces@ietf.org  Mon Nov  1 06:45:43 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA20074
	for <pim-archive@lists.ietf.org>; Mon, 1 Nov 2004 06:45:43 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1COZRZ-0001jt-RQ
	for pim-archive@lists.ietf.org; Mon, 01 Nov 2004 05:29:45 -0500
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Subject: ietf.org mailing list memberships reminder
From: mailman-owner@ietf.org
To: pim-archive@ietf.org
X-No-Archive: yes
Message-ID: <mailman.14617.1099303866.20557.mailman@lists.ietf.org>
Date: Mon, 01 Nov 2004 05:11:06 -0500
Precedence: bulk
X-BeenThere: mailman@lists.ietf.org
X-Mailman-Version: 2.1.5
List-Id: Mailman site list <mailman.lists.ietf.org>
X-List-Administrivia: yes
Sender: mailman-bounces@ietf.org
Errors-To: mailman-bounces@ietf.org
Content-Transfer-Encoding: 7bit

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

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

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

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

NOTE WELL:

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

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

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

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

Please consult RFC 3667 for details.

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


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

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

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


From pim-bounces@ietf.org  Mon Nov  1 11:34:01 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA29701
	for <pim-archive@lists.ietf.org>; Mon, 1 Nov 2004 11:34:00 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1COejP-0001LA-Nf; Mon, 01 Nov 2004 11:08:31 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1COdwH-0008Bw-Ao
	for pim@megatron.ietf.org; Mon, 01 Nov 2004 10:17:45 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA14637
	for <pim@ietf.org>; Mon, 1 Nov 2004 10:17:44 -0500 (EST)
Received: from catarina.usc.edu ([204.57.0.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1COeB2-0000m4-QA
	for pim@ietf.org; Mon, 01 Nov 2004 10:33:10 -0500
Received: from sj-iport-1.cisco.com (sj-iport-1-in.cisco.com [171.71.176.70])
	by catarina.usc.edu (8.12.9/8.12.9) with ESMTP id iA1FH3oh047312
	for <pim@catarina.usc.edu>; Mon, 1 Nov 2004 07:17:03 -0800 (PST)
	(envelope-from bwilliam@cisco.com)
Received: from sj-core-1.cisco.com (171.71.177.237)
	by sj-iport-1.cisco.com with ESMTP; 01 Nov 2004 07:29:16 -0800
X-BrightmailFiltered: true
Received: from edison.cisco.com (edison.cisco.com [171.71.180.109])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id iA1FGrom013417;
	Mon, 1 Nov 2004 07:16:53 -0800 (PST)
Received: from bwilliam-t30.cisco.com (rcdn-bwilliam-3002-2.cisco.com
	[10.89.26.27]) by edison.cisco.com (8.8.6
	(PHNE_14041)/CISCO.SERVER.1.2) with ESMTP id HAA11553;
	Mon, 1 Nov 2004 07:16:54 -0800 (PST)
Message-Id: <6.0.0.22.2.20041101091513.0328b180@edison.cisco.com>
X-Sender: bwilliam@edison.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22
Date: Mon, 01 Nov 2004 09:17:23 -0600
To: Christopher Thomas Brown <ctbrown@nexthop.com>, Stig.Venaas@uninett.no
From: Beau Williamson <bwilliam@cisco.com>
Subject: RE: [pim] The BSR spec and maintaining group-to-RP mappings
In-Reply-To: <20041101023101.BA9FA2D4DCE@aa-mx1.nexthop.com>
References: <20041101023101.BA9FA2D4DCE@aa-mx1.nexthop.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Cc: pim@catarina.usc.edu
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=subscribe>
Sender: pim-bounces@ietf.org
Errors-To: pim-bounces@ietf.org

At 10/31/2004 08:30 PM, Christopher Thomas Brown wrote:
>3 Backward compatibility
>
>I don't think you can firmly make the claim that EW is backwards compatible.
>There is nothing that I recall in some of the older specs that requires
>a router to honor a holdtime of zero in a BSM as a request to remove
>the RP from that mapping. As has been said, older specs are ambiguous. Some
>implementations that do IW only remove from the RP set at a non-EBSR
>upon the implicit withdrawal and not on holdtime timeout.

Christopher,

Are you saying that in some implementations routers simply ignore the 
holdtime values in the RP-Set??  If so, I would maintain that this is a 
broken implementation and we shouldn't be concerned with this.

I thought the old spec was pretty clear that the routers would timeout a 
C-RP from the RP-Set when the holdtime went to zero.

Beau Williamson



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


From pim-bounces@ietf.org  Mon Nov  1 15:30:21 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA27411
	for <pim-archive@lists.ietf.org>; Mon, 1 Nov 2004 15:30:20 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1COicV-0000U2-2F; Mon, 01 Nov 2004 15:17:39 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1COiIp-00062K-Mq
	for pim@megatron.ietf.org; Mon, 01 Nov 2004 14:57:19 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22958
	for <pim@ietf.org>; Mon, 1 Nov 2004 14:57:17 -0500 (EST)
Received: from catarina.usc.edu ([204.57.0.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1COiXn-0001Bx-Gj
	for pim@ietf.org; Mon, 01 Nov 2004 15:12:48 -0500
Received: from aa-mx1.nexthop.com (dns.nexthop.com [65.247.36.216])
	by catarina.usc.edu (8.12.9/8.12.9) with ESMTP id iA1Juhoh049573
	for <pim@catarina.usc.edu>; Mon, 1 Nov 2004 11:56:47 -0800 (PST)
	(envelope-from ctbrown@nexthop.com)
Received: from localhost (localhost [127.0.0.1])
	by aa-mx1.nexthop.com (Postfix) with ESMTP
	id 396AA2D4A8B; Mon,  1 Nov 2004 14:56:38 -0500 (EST)
Received: from aa-mx1.nexthop.com ([127.0.0.1])
	by localhost (aa-mx1.nexthop.com [127.0.0.1]) (amavisd-new, port 10024)
	with LMTP id 44369-01-90; Mon,  1 Nov 2004 14:56:36 -0500 (EST)
Received: from nexthop.com (ctbrown.nexthop.com [65.247.36.75])
	by aa-mx1.nexthop.com (Postfix) with ESMTP
	id 4215C2D495C; Mon,  1 Nov 2004 14:56:36 -0500 (EST)
From: Christopher Thomas Brown <ctbrown@nexthop.com>
Subject: Re: [pim] The BSR spec and maintaining group-to-RP mappings 
To: Beau Williamson <bwilliam@cisco.com>
In-Reply-To: Your message of "Mon, 01 Nov 2004 09:17:23 CST."
	<6.0.0.22.2.20041101091513.0328b180@edison.cisco.com> 
Date: Mon, 01 Nov 2004 14:55:48 -0500
Message-Id: <20041101195636.4215C2D495C@aa-mx1.nexthop.com>
X-Virus-Scanned: by amavisd-new at nexthop.com
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6cca30437e2d04f45110f2ff8dc1b1d5
Cc: pim@catarina.usc.edu
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=subscribe>
Sender: pim-bounces@ietf.org
Errors-To: pim-bounces@ietf.org

On Mon, 01 Nov 2004 09:17:23 CST
Beau Williamson wrote:
>At 10/31/2004 08:30 PM, Christopher Thomas Brown wrote:
>>3 Backward compatibility
>>
>>I don't think you can firmly make the claim that EW is backwards compatible.
>>There is nothing that I recall in some of the older specs that requires
>>a router to honor a holdtime of zero in a BSM as a request to remove
>>the RP from that mapping. As has been said, older specs are ambiguous. Some
>>implementations that do IW only remove from the RP set at a non-EBSR
>>upon the implicit withdrawal and not on holdtime timeout.
>
>Christopher,
>
>Are you saying that in some implementations routers simply ignore the 
>holdtime values in the RP-Set??  If so, I would maintain that this is a 
>broken implementation and we shouldn't be concerned with this.
>
>I thought the old spec was pretty clear that the routers would timeout a 
>C-RP from the RP-Set when the holdtime went to zero.

Beau,
I don't think its clear at all. I think its reasonable behavior to infer
but the spec does not clearly state that one should do this.

In  draft-ietf-pim-sm-bsr-00 in section 1.1 Overview of Bootstrap and
RP Discovery, it says,

>A Bootstrap message indicates liveness of the RPs included therein.  If
>an RP is included in the message, then it is tagged as `up' at the
>routers; RPs not included in the message are removed from the list
>of RPs over which the hash algorithm acts.

This seems to indicate to me that if an RP is included it should be
considered up. It doesn't say anything about paying attemtion to the
included holdtime. May one can infer this from the first sentence though.

In section 3.1 Sending Candidate-RP-Advertisements, is says,

>When a C-RP is being shut down, it SHOULD immediately send a C-RP-Adv
>to the BSR for each scope for which it is currently serving as an RP;
>the HoldTime in this C-RP-Adv message should be zero. The BSR will
>then immediately time out the C-RP and generate a new BSR message removing
>the shutdown RP from the RPset.

So, when the RP is shutdown I would expect to just not encounter it in
the BSM.

In section 3.2 Creating the RP-Set at the BSR it says,

>When the C-RP Expiry Timer expires, the C-RP is removed from the pool
>of available C-RPs.

Finally in section 3.4 Receiving and Using the RP-Set is says,

>If an RP is not in the new RP-Set, that RP is considered unreachable
>and the hash algorithm (see PIM-SM specification) is re-performed
>for each group with locally active state that previously hashed to
>that RP.

It doesn't say to pay attention to the holdtime.

So, no the old spec is not clear on what a PIM router should do with the
holdtime included in the BSM. It is silent in the subject as far as I
can tell. Maybe I missed a section.

So I wouldn't say an implementation that did not remove from its RP-Set
a C-RP included in a BSM with a zero holdtime is broken. Well, maybe I
would call it broken, but I wouldn't call it non-compliant. :)

That said, I like the explicit withdrawal approach better than the
implicit withdrawal method, even if it is not completely backwards
compatible with all existing implementations. From what I can gather
from various statements, I don't think we can get a good middle ground
that is completely interoperable, so we might as well choose the better
approach.

Chris

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


From pim-bounces@ietf.org  Mon Nov  1 17:26:13 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA13306
	for <pim-archive@lists.ietf.org>; Mon, 1 Nov 2004 17:26:13 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1COk9p-0006Xq-VE; Mon, 01 Nov 2004 16:56:09 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1COjnd-00030U-MW
	for pim@megatron.ietf.org; Mon, 01 Nov 2004 16:33:13 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA06243
	for <pim@ietf.org>; Mon, 1 Nov 2004 16:33:12 -0500 (EST)
Received: from catarina.usc.edu ([204.57.0.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1COk2X-0004bP-FN
	for pim@ietf.org; Mon, 01 Nov 2004 16:48:42 -0500
Received: from tyholt.uninett.no (tyholt.uninett.no [158.38.60.10])
	by catarina.usc.edu (8.12.9/8.12.9) with ESMTP id iA1LWVoh051034
	for <pim@catarina.usc.edu>; Mon, 1 Nov 2004 13:32:36 -0800 (PST)
	(envelope-from Stig.Venaas@uninett.no)
Received: from sverresborg.uninett.no (sverresborg.uninett.no
	[IPv6:2001:700:e000:0:204:75ff:fee4:423b])
	by tyholt.uninett.no (8.12.10/8.12.10) with ESMTP id iA1LWOLP021139;
	Mon, 1 Nov 2004 22:32:25 +0100
Received: (from venaas@localhost)
	by sverresborg.uninett.no (8.12.8/8.12.8/Submit) id iA1LWNuo000431;
	Mon, 1 Nov 2004 22:32:23 +0100
X-Authentication-Warning: sverresborg.uninett.no: venaas set sender to
	Stig.Venaas@uninett.no using -f
Date: Mon, 1 Nov 2004 22:32:23 +0100
From: Stig Venaas <Stig.Venaas@uninett.no>
To: Christopher Thomas Brown <ctbrown@nexthop.com>
Subject: Re: [pim] The BSR spec and maintaining group-to-RP mappings
Message-ID: <20041101213222.GA32604@sverresborg.uninett.no>
References: <20041101023101.BA9FA2D4DCE@aa-mx1.nexthop.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20041101023101.BA9FA2D4DCE@aa-mx1.nexthop.com>
User-Agent: Mutt/1.4.1i
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6e922792024732fb1bb6f346e63517e4
Cc: pim@catarina.usc.edu
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=subscribe>
Sender: pim-bounces@ietf.org
Errors-To: pim-bounces@ietf.org

On Sun, Oct 31, 2004 at 09:30:17PM -0500, Christopher Thomas Brown wrote:
> 
> Stig,
> I feel that the EW approach is better than the ambiguously defined
> approach that the current specification is.
> 
> However, I have some thoughts about things you bring up.
> 
> In section 2.1 you state:
> 
> >   IW: The router needs to wait for the entire Mapping record (G/mask
> >   and RP list) to be received before it purge mappings which have
> >   not been included this time. However, we think there is no way for
> >   a router to know that the entire mapping record has been
> >   received e.g. the last record in the fragment.
> 
> Is this true? It seems like one of the previous drafts had a solution for
> this problem. In a group range mapping there is a count of the RPs for the
> mapping (RP count) and a count of the RPs included in the current message
> (Frag RP count). Each fragment of the message carries a tag that indicates
> which instance of the BSR message it is. One knows when the entire mapping
> record has been received when one has received as many RPs for the group
> range as indicated by the RP count. One knows that a fragment has been
> lost when a new instance of the message is encountered.

My thinking here, is that you cannot notice missing fragments unless you
have a group range spanning multiple fragments. However, if you for IW
always include an empty group range in a BSM when removing the entire
group range, then I think you are right. Else you cannot distinguish
between a fragment being lost and a group range being removed. This can
be problematic in some cases. A newly elected BSR may need to keep a
copy of previously received BSM (to know that a group range is
disappearing when network is partitioned). Else the group range will
be kept until it expires.

> Now, I don't really like this approach but I think it does provide a way
> for a router to know that the entire mapping record has been received.
> Perhaps, I'm missing something here.
> 
> 
> 2.2 RP disappearing
> 
> For EW, I hope the 'trigger BSM' action is only for the affected group
> range and only the affected RP.

Yes, if the BSR only wants to remove an RP it should be enough to send
a BSM with just the one group range and the one RP with holdtime 0.

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

Perhaps we shouldn't discuss it here since it's the same for both
approaches. I think that if a network is designed properly, there
should only be no CBSRs if the network is practically useless. If
e.g. all RPs are CBSRs then no CBSR means no RP and then it won't
help keeping the RPset. One reason for having a timeout, is that
it allows for moving from BSR to another "protocol". We could
possibly make this a special case and use another timeout than the
holdtime.

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

Yes. Also for IW this might be useful; see my 2.1 comment above.

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

The implementations I've checked honours the holdtime, but I agree it's
not clear that this should be done. Do you know for a fact that there
are some implementations not using the holdtime? In that case backwards
compatibility is difficult. We may also need to make that a third
category. Does anyone prefer that approach?

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

Stig

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


From pim-bounces@ietf.org  Mon Nov  1 17:37:42 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA14684
	for <pim-archive@lists.ietf.org>; Mon, 1 Nov 2004 17:37:41 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1COkgb-0002I8-RA; Mon, 01 Nov 2004 17:30:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1COkBW-0000X5-1u
	for pim@megatron.ietf.org; Mon, 01 Nov 2004 16:57:54 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA01907
	for <pim@ietf.org>; Mon, 1 Nov 2004 16:07:16 -0500 (EST)
Received: from catarina.usc.edu ([204.57.0.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1COjdS-0003UG-1X
	for pim@ietf.org; Mon, 01 Nov 2004 16:22:46 -0500
Received: from sj-iport-2.cisco.com (sj-iport-2-in.cisco.com [171.71.176.71])
	by catarina.usc.edu (8.12.9/8.12.9) with ESMTP id iA1L6foh050494
	for <pim@catarina.usc.edu>; Mon, 1 Nov 2004 13:06:41 -0800 (PST)
	(envelope-from bwilliam@cisco.com)
Received: from sj-core-2.cisco.com (171.71.177.254)
	by sj-iport-2.cisco.com with ESMTP; 01 Nov 2004 13:16:39 -0800
Received: from edison.cisco.com (edison.cisco.com [171.71.180.109])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id iA1L6SnC012726;
	Mon, 1 Nov 2004 13:06:28 -0800 (PST)
Received: from bwilliam-t30.cisco.com (rcdn-bwilliam-3002-2.cisco.com
	[10.89.26.27]) by edison.cisco.com (8.8.6
	(PHNE_14041)/CISCO.SERVER.1.2) with ESMTP id NAA17689;
	Mon, 1 Nov 2004 13:06:30 -0800 (PST)
Message-Id: <6.0.0.22.2.20041101150209.032ef250@edison.cisco.com>
X-Sender: bwilliam@edison.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22
Date: Mon, 01 Nov 2004 15:06:58 -0600
To: Christopher Thomas Brown <ctbrown@nexthop.com>
From: Beau Williamson <bwilliam@cisco.com>
Subject: Re: [pim] The BSR spec and maintaining group-to-RP mappings 
In-Reply-To: <20041101195636.4215C2D495C@aa-mx1.nexthop.com>
References: <Your message of "Mon, 01 Nov 2004 09:17:23 CST."
	<6.0.0.22.2.20041101091513.0328b180@edison.cisco.com>
	<20041101195636.4215C2D495C@aa-mx1.nexthop.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Cc: pim@catarina.usc.edu
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=subscribe>
Sender: pim-bounces@ietf.org
Errors-To: pim-bounces@ietf.org

At 11/1/2004 01:55 PM, Christopher Thomas Brown wrote:

>It doesn't say to pay attention to the holdtime.
>
>So, no the old spec is not clear on what a PIM router should do with the
>holdtime included in the BSM. It is silent in the subject as far as I
>can tell. Maybe I missed a section.
>
>So I wouldn't say an implementation that did not remove from its RP-Set
>a C-RP included in a BSM with a zero holdtime is broken. Well, maybe I
>would call it broken, but I wouldn't call it non-compliant. :)
>
>That said, I like the explicit withdrawal approach better than the
>implicit withdrawal method, even if it is not completely backwards
>compatible with all existing implementations. From what I can gather
>from various statements, I don't think we can get a good middle ground
>that is completely interoperable, so we might as well choose the better
>approach.

Well, it "has" been a long time since I went over the spec in great detail 
so I may have been reading more into the fact that there is a holdtime 
field for the RP in the BSM than was actually called out in the text.

So far, I'm leaning toward the EW method myself.  Unfortunately, I won't be 
at the DC IETF to discuss further.  Will continue to monitor the list for 
discussions.  One interesting scenario to the EW method previously raised 
was the total loss of all C-BSR's in the network.  If all routers ignore 
(i.e. don't implement) a holdtime timer for the RP entries in the BSR, and 
instead wait for the explicit withdrawal notification which never comes 
(because all BSR's are down) then all routers will continue with the last 
known RP Set.  Not sure this is the proper thing to do.  Need to think 
about this a bit more.

Beau 


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


From pim-bounces@ietf.org  Tue Nov  2 00:26:33 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA27129
	for <pim-archive@lists.ietf.org>; Tue, 2 Nov 2004 00:26:33 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1COr9p-0000sT-4F; Tue, 02 Nov 2004 00:24:37 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1COr86-0008VV-A9
	for pim@megatron.ietf.org; Tue, 02 Nov 2004 00:22:50 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA26825
	for <pim@ietf.org>; Tue, 2 Nov 2004 00:22:47 -0500 (EST)
Received: from catarina.usc.edu ([204.57.0.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1COrMz-0007jO-4X
	for pim@ietf.org; Tue, 02 Nov 2004 00:38:22 -0500
Received: from sj-iport-2.cisco.com (sj-iport-2-in.cisco.com [171.71.176.71])
	by catarina.usc.edu (8.12.9/8.12.9) with ESMTP id iA25M6oh054623
	for <pim@catarina.usc.edu>; Mon, 1 Nov 2004 21:22:06 -0800 (PST)
	(envelope-from nbhaskar@cisco.com)
Received: from sj-core-5.cisco.com (171.71.177.238)
	by sj-iport-2.cisco.com with ESMTP; 01 Nov 2004 21:32:11 -0800
Received: from cypher.cisco.com (cypher.cisco.com [171.69.11.142])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id iA25Lvcq024962;
	Mon, 1 Nov 2004 21:21:58 -0800 (PST)
Date: Mon, 1 Nov 2004 21:21:58 -0800 (PST)
From: Nidhi Bhaskar <nbhaskar@cisco.com>
To: Stig Venaas <Stig.Venaas@uninett.no>
Subject: Re: [pim] The BSR spec and maintaining group-to-RP mappings
In-Reply-To: <20041101213222.GA32604@sverresborg.uninett.no>
Message-ID: <Pine.GSO.4.58.0411012112510.10453@cypher.cisco.com>
References: <20041101023101.BA9FA2D4DCE@aa-mx1.nexthop.com>
	<20041101213222.GA32604@sverresborg.uninett.no>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f60d0f7806b0c40781eee6b9cd0b2135
Cc: pim@catarina.usc.edu, Christopher Thomas Brown <ctbrown@nexthop.com>,
        Nidhi Bhaskar <nbhaskar@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>
Sender: pim-bounces@ietf.org
Errors-To: pim-bounces@ietf.org


> > 2.2 RP disappearing
> >
> > For EW, I hope the 'trigger BSM' action is only for the affected group
> > range and only the affected RP.
>
> Yes, if the BSR only wants to remove an RP it should be enough to send
> a BSM with just the one group range and the one RP with holdtime 0.

This is a possible optimization, although it is not compatible with IW
implementations. Also, I have a preference for keeping things simple,
i.e. just generate a BSM vs. sending out selected mapping that have
timed out etc. Do you see some scenario where sending out the entire
mapping is problematic ? Are you concerend about too many messages ?
I think it is possible for the BSR to aggregate changes so that not
too many of these have to go out.

> > 2.5 BSR being replaced
> >
> > With EW, since the routers in the PIM domain do not change their RP sets
> > in response to the elected BSR changing, it seems like an optimization if
> > the newly elected BSR uses the RP set it had stored from the previous BSR
> > to announce to the domain.
>
> Yes. Also for IW this might be useful; see my 2.1 comment above.

I'm less inclined to go this route. It seems better to let the new BSR
discover which RPs are still available rather than just refresh the
existing set and perhaps prolong the timeout for RPs that are now down
or partitioned ?


Thanks,
Nidhi.

> > 3 Backward compatibility
> >
> > I don't think you can firmly make the claim that EW is backwards compatible.
> > There is nothing that I recall in some of the older specs that requires
> > a router to honor a holdtime of zero in a BSM as a request to remove
> > the RP from that mapping. As has been said, older specs are ambiguous. Some
> > implementations that do IW only remove from the RP set at a non-EBSR
> > upon the implicit withdrawal and not on holdtime timeout.
>
> The implementations I've checked honours the holdtime, but I agree it's
> not clear that this should be done. Do you know for a fact that there
> are some implementations not using the holdtime? In that case backwards
> compatibility is difficult. We may also need to make that a third
> category. Does anyone prefer that approach?
>
> > * Transition
> >
> > If consensus is reached on the EW approach, I think some of the suggested
> > IW behaviors should be documented as they help compatibility between
> > EW and IW. A vendor that has implemented the IW approach with its current
> > ambiguities can then implement the documented behaviors, if they have not
> > already, and be reasonabilly sure that their IW implementation will
> > interoperate with the EW approach.
> >
> > Chris
>
> Stig
>
> _______________________________________________
> pim mailing list
> pim@ietf.org
> https://www1.ietf.org/mailman/listinfo/pim
>

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


From pim-bounces@ietf.org  Tue Nov  2 00:39:10 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA28020
	for <pim-archive@lists.ietf.org>; Tue, 2 Nov 2004 00:39:10 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1COrMM-0005Vy-P2; Tue, 02 Nov 2004 00:37:34 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1COrC4-0001lB-1D
	for pim@megatron.ietf.org; Tue, 02 Nov 2004 00:26:56 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA27149
	for <pim@ietf.org>; Tue, 2 Nov 2004 00:26:54 -0500 (EST)
Received: from catarina.usc.edu ([204.57.0.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1COrR1-0007pZ-QV
	for pim@ietf.org; Tue, 02 Nov 2004 00:42:29 -0500
Received: from sj-iport-2.cisco.com (sj-iport-2-in.cisco.com [171.71.176.71])
	by catarina.usc.edu (8.12.9/8.12.9) with ESMTP id iA25QJoh054652
	for <pim@catarina.usc.edu>; Mon, 1 Nov 2004 21:26:19 -0800 (PST)
	(envelope-from nbhaskar@cisco.com)
Received: from sj-core-2.cisco.com (171.71.177.254)
	by sj-iport-2.cisco.com with ESMTP; 01 Nov 2004 21:36:25 -0800
Received: from cypher.cisco.com (cypher.cisco.com [171.69.11.142])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id iA25Q4nD015491;
	Mon, 1 Nov 2004 21:26:05 -0800 (PST)
Date: Mon, 1 Nov 2004 21:26:11 -0800 (PST)
From: Nidhi Bhaskar <nbhaskar@cisco.com>
To: Beau Williamson <bwilliam@cisco.com>
Subject: Re: [pim] The BSR spec and maintaining group-to-RP mappings 
In-Reply-To: <6.0.0.22.2.20041101150209.032ef250@edison.cisco.com>
Message-ID: <Pine.GSO.4.58.0411012124120.10453@cypher.cisco.com>
References: <Your message of "Mon, 01 Nov 2004 09:17:23 CST."
	<6.0.0.22.2.20041101091513.0328b180@edison.cisco.com>
	<20041101195636.4215C2D495C@aa-mx1.nexthop.com>
	<6.0.0.22.2.20041101150209.032ef250@edison.cisco.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Cc: pim@catarina.usc.edu, Christopher Thomas Brown <ctbrown@nexthop.com>,
        Nidhi Bhaskar <nbhaskar@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>
Sender: pim-bounces@ietf.org
Errors-To: pim-bounces@ietf.org

> So far, I'm leaning toward the EW method myself.  Unfortunately, I won't be
> at the DC IETF to discuss further.  Will continue to monitor the list for
> discussions.  One interesting scenario to the EW method previously raised
> was the total loss of all C-BSR's in the network.  If all routers ignore
> (i.e. don't implement) a holdtime timer for the RP entries in the BSR, and
> instead wait for the explicit withdrawal notification which never comes
> (because all BSR's are down) then all routers will continue with the last
> known RP Set.  Not sure this is the proper thing to do.  Need to think
> about this a bit more.

Beau,

EW also uses the holdtime to expire RP entries. The difference between
IW and EW is how the BSR notifies the rest of the domain that an
RP/mapping is to be removed... When all BSRs die, the two approaches
behave the same way. I.e. the RP set on all routers in the domain
times out.

Thanks,
Nidhi.

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


From pim-bounces@ietf.org  Tue Nov  2 02:04:42 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA09690
	for <pim-archive@lists.ietf.org>; Tue, 2 Nov 2004 02:04:41 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1COsga-0007m2-24; Tue, 02 Nov 2004 02:02:32 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1COscr-0005Wm-Ur
	for pim@megatron.ietf.org; Tue, 02 Nov 2004 01:58:42 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA04514
	for <pim@ietf.org>; Tue, 2 Nov 2004 01:58:41 -0500 (EST)
Received: from catarina.usc.edu ([204.57.0.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1COsrq-0001Kx-EN
	for pim@ietf.org; Tue, 02 Nov 2004 02:14:16 -0500
Received: from tyholt.uninett.no (tyholt.uninett.no [158.38.60.10])
	by catarina.usc.edu (8.12.9/8.12.9) with ESMTP id iA26w1oh055306
	for <pim@catarina.usc.edu>; Mon, 1 Nov 2004 22:58:04 -0800 (PST)
	(envelope-from Stig.Venaas@uninett.no)
Received: from sverresborg.uninett.no (sverresborg.uninett.no
	[IPv6:2001:700:e000:0:204:75ff:fee4:423b])
	by tyholt.uninett.no (8.12.10/8.12.10) with ESMTP id iA26vvLP012349;
	Tue, 2 Nov 2004 07:57:58 +0100
Received: (from venaas@localhost)
	by sverresborg.uninett.no (8.12.8/8.12.8/Submit) id iA26vu8d002873;
	Tue, 2 Nov 2004 07:57:56 +0100
X-Authentication-Warning: sverresborg.uninett.no: venaas set sender to
	Stig.Venaas@uninett.no using -f
Date: Tue, 2 Nov 2004 07:57:56 +0100
From: Stig Venaas <Stig.Venaas@uninett.no>
To: Nidhi Bhaskar <nbhaskar@cisco.com>
Subject: Re: [pim] The BSR spec and maintaining group-to-RP mappings
Message-ID: <20041102065756.GA2769@sverresborg.uninett.no>
References: <20041101023101.BA9FA2D4DCE@aa-mx1.nexthop.com>
	<20041101213222.GA32604@sverresborg.uninett.no>
	<Pine.GSO.4.58.0411012112510.10453@cypher.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.GSO.4.58.0411012112510.10453@cypher.cisco.com>
User-Agent: Mutt/1.4.1i
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002
Cc: pim@catarina.usc.edu, Christopher Thomas Brown <ctbrown@nexthop.com>
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=subscribe>
Sender: pim-bounces@ietf.org
Errors-To: pim-bounces@ietf.org

On Mon, Nov 01, 2004 at 09:21:58PM -0800, Nidhi Bhaskar wrote:
> 
> > > 2.2 RP disappearing
> > >
> > > For EW, I hope the 'trigger BSM' action is only for the affected group
> > > range and only the affected RP.
> >
> > Yes, if the BSR only wants to remove an RP it should be enough to send
> > a BSM with just the one group range and the one RP with holdtime 0.
> 
> This is a possible optimization, although it is not compatible with IW
> implementations. Also, I have a preference for keeping things simple,
> i.e. just generate a BSM vs. sending out selected mapping that have
> timed out etc. Do you see some scenario where sending out the entire
> mapping is problematic ? Are you concerend about too many messages ?
> I think it is possible for the BSR to aggregate changes so that not
> too many of these have to go out.

Good point. For compatibility with IR you would at least need to include
everything in that group range. It is simpler to always use the same
send algorithm though (sending everything).

> > > 2.5 BSR being replaced
> > >
> > > With EW, since the routers in the PIM domain do not change their RP sets
> > > in response to the elected BSR changing, it seems like an optimization if
> > > the newly elected BSR uses the RP set it had stored from the previous BSR
> > > to announce to the domain.
> >
> > Yes. Also for IW this might be useful; see my 2.1 comment above.
> 
> I'm less inclined to go this route. It seems better to let the new BSR
> discover which RPs are still available rather than just refresh the
> existing set and perhaps prolong the timeout for RPs that are now down
> or partitioned ?

When switching BSRs I can think of two ways of making sure RPs that still
are alive and reachable are not lost in the process.

One way is the above. The other way is to have some special processing
on the routers when receiving an empty BSM. This might include cRPs
immediately sending advertisements and/or not remove entries when
the previous holdtime expires.

And yes, we have to balance this against keeping dead RPs too long.

I'm not sure myself which is best yet.

Stig

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


From pim-bounces@ietf.org  Tue Nov  2 13:21:10 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA24199
	for <pim-archive@lists.ietf.org>; Tue, 2 Nov 2004 13:21:10 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CP2vB-0001zN-BO; Tue, 02 Nov 2004 12:58:17 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CP2j7-0003bU-A4
	for pim@megatron.ietf.org; Tue, 02 Nov 2004 12:45:52 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA16575
	for <pim@ietf.org>; Tue, 2 Nov 2004 12:45:46 -0500 (EST)
Received: from catarina.usc.edu ([204.57.0.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CP2yF-0008F5-Sh
	for pim@ietf.org; Tue, 02 Nov 2004 13:01:29 -0500
Received: from aa-mx1.nexthop.com (dns.nexthop.com [65.247.36.216])
	by catarina.usc.edu (8.12.9/8.12.9) with ESMTP id iA2HjCoh061401
	for <pim@catarina.usc.edu>; Tue, 2 Nov 2004 09:45:16 -0800 (PST)
	(envelope-from ctbrown@nexthop.com)
Received: from localhost (localhost [127.0.0.1])
	by aa-mx1.nexthop.com (Postfix) with ESMTP
	id C1BD42D48C1; Tue,  2 Nov 2004 12:45:10 -0500 (EST)
Received: from aa-mx1.nexthop.com ([127.0.0.1])
	by localhost (aa-mx1.nexthop.com [127.0.0.1]) (amavisd-new, port 10024)
	with LMTP id 04410-01-87; Tue,  2 Nov 2004 12:45:09 -0500 (EST)
Received: from nexthop.com (ctbrown.nexthop.com [65.247.36.75])
	by aa-mx1.nexthop.com (Postfix) with ESMTP
	id A04802D48B9; Tue,  2 Nov 2004 12:45:09 -0500 (EST)
From: Christopher Thomas Brown <ctbrown@nexthop.com>
Subject: Re: [pim] The BSR spec and maintaining group-to-RP mappings 
To: Stig Venaas <Stig.Venaas@uninett.no>
In-Reply-To: Your message of "Tue, 02 Nov 2004 07:57:56 +0100."
	<20041102065756.GA2769@sverresborg.uninett.no> 
Date: Tue, 02 Nov 2004 12:44:18 -0500
Message-Id: <20041102174509.A04802D48B9@aa-mx1.nexthop.com>
X-Virus-Scanned: by amavisd-new at nexthop.com
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f60d0f7806b0c40781eee6b9cd0b2135
Cc: Nidhi Bhaskar <nbhaskar@cisco.com>, pim@catarina.usc.edu
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=subscribe>
Sender: pim-bounces@ietf.org
Errors-To: pim-bounces@ietf.org

On Tue, 02 Nov 2004 07:57:56 +0100
Stig Venaas wrote:
>On Mon, Nov 01, 2004 at 09:21:58PM -0800, Nidhi Bhaskar wrote:
>> 
>> > > 2.2 RP disappearing
>> > >
>> > > For EW, I hope the 'trigger BSM' action is only for the affected group
>> > > range and only the affected RP.
>> >
>> > Yes, if the BSR only wants to remove an RP it should be enough to send
>> > a BSM with just the one group range and the one RP with holdtime 0.
>> 
>> This is a possible optimization, although it is not compatible with IW
>> implementations. Also, I have a preference for keeping things simple,
>> i.e. just generate a BSM vs. sending out selected mapping that have
>> timed out etc. Do you see some scenario where sending out the entire
>> mapping is problematic ? Are you concerend about too many messages ?
>> I think it is possible for the BSR to aggregate changes so that not
>> too many of these have to go out.
>
>Good point. For compatibility with IR you would at least need to include
>everything in that group range. It is simpler to always use the same
>send algorithm though (sending everything).

It is simpler but I am concerned about a situation in which a large
number of CRPs go down at once. If I get 10 CRPs withdrawing I will
send 10 complete BSMs rather quickly. Perhaps instead of trigerring
a BSM it would be better to lower the BSR timer to some small time
so that the periodic message is sent soon. This would be a simple
approach to aggregating the changes.

>
>> > > 2.5 BSR being replaced
>> > >
>> > > With EW, since the routers in the PIM domain do not change their RP sets
>> > > in response to the elected BSR changing, it seems like an optimization i
>f
>> > > the newly elected BSR uses the RP set it had stored from the previous BS
>R
>> > > to announce to the domain.
>> >
>> > Yes. Also for IW this might be useful; see my 2.1 comment above.
>> 
>> I'm less inclined to go this route. It seems better to let the new BSR
>> discover which RPs are still available rather than just refresh the
>> existing set and perhaps prolong the timeout for RPs that are now down
>> or partitioned ?
>
>When switching BSRs I can think of two ways of making sure RPs that still
>are alive and reachable are not lost in the process.
>
>One way is the above. The other way is to have some special processing
>on the routers when receiving an empty BSM. This might include cRPs
>immediately sending advertisements and/or not remove entries when
>the previous holdtime expires.
>
>And yes, we have to balance this against keeping dead RPs too long.
>
>I'm not sure myself which is best yet.

Well, one thing the new BSR could do it lower the holdtimes that it has
for the CRPS in the BSM to some smallish value. It should be a time
adequate enough to allow the CRPs to advertise themselves to the new BSR
and for the new BSR to then send out a new BSM. However, with this
approach two BSMs are sent out in a rather short period of time.


Chris

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


From pim-bounces@ietf.org  Tue Nov  2 23:46:11 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA26411
	for <pim-archive@lists.ietf.org>; Tue, 2 Nov 2004 23:46:11 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CPCla-0001xZ-Gl; Tue, 02 Nov 2004 23:29:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CPCeX-0005wT-9b
	for pim@megatron.ietf.org; Tue, 02 Nov 2004 23:21:45 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA24220
	for <pim@ietf.org>; Tue, 2 Nov 2004 23:21:43 -0500 (EST)
Received: from catarina.usc.edu ([204.57.0.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CPCth-0000A7-6N
	for pim@ietf.org; Tue, 02 Nov 2004 23:37:31 -0500
Received: from huawei.com (szxga03-in.huawei.com [61.144.161.55] (may be
	forged))
	by catarina.usc.edu (8.12.9/8.12.9) with ESMTP id iA34L5oh066832
	for <pim@catarina.usc.edu>; Tue, 2 Nov 2004 20:21:08 -0800 (PST)
	(envelope-from prashantj@huawei.com)
Received: from huawei.com (szxga03-in [172.24.2.9])
	by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTP id <0I6L00EIA517WD@szxga03-in.huawei.com> for
	pim@catarina.usc.edu; Wed, 03 Nov 2004 12:12:43 +0800 (CST)
Received: from szxml01-in ([172.24.1.3])
	by szxga03-in.huawei.com (iPlanet	Messaging Server 5.2 HotFix 1.25
	(built Mar3
	2004)) with ESMTP id	<0I6L00B0W517NY@szxga03-in.huawei.com>
	forpim@catarina.usc.edu; Wed, 03 Nov 2004 12:12:43 +0800 (CST)
Received: from huawei8tthy486 ([10.110.34.48])
	by szxml01-in.huawei.com	(iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar3
	2004)) with ESMTPA id	<0I6L00ATO561D6@szxml01-in.huawei.com>; Wed,
	03 Nov 2004 12:15:38 +0800 (CST)
Date: Wed, 03 Nov 2004 12:12:26 +0800
From: Prashant Jhingran <prashantj@huawei.com>
To: pim@catarina.usc.edu
Message-id: <000001c4c15b$54a30110$30226e0a@huawei8tthy486>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Mailer: Microsoft Outlook, Build 10.0.3416
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
X-imss-version: 2.7
X-imss-result: Passed
X-imss-approveListMatch: *@huawei.com
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793
Content-Transfer-Encoding: 7BIT
Cc: nbhaskar@cisco.com, ctbrown@nexthop.com, Stig.Venaas@uninett.no,
        bwilliam@cisco.com
Subject: [pim] Default BSR priority issue!
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=subscribe>
Sender: pim-bounces@ietf.org
Errors-To: pim-bounces@ietf.org
Content-Transfer-Encoding: 7BIT

Hi All,

The latest BSR draft no where mentions about the default BSR priority &
that's why probably few
Developers/vendors are using the value "Zero" as default BSR priority.

The problem comes when the EBSR is getting shutdown. 

There are no means by which the current EBSR can inform the other
routers in the domain about itself going down.
(Since default BSR priority and the priority to inform when BSR goes
down boils down to the same numerical value i.e. Zero).

I think this issue is more important than the RP-mapping we are
discussion currently and this problem should be resolved in the coming
BSR draft....this would also lead to faster convergence during graceful
EBSR shutdown scenarios.


As per draft-ietf-pim-sm-bsr-04.txt, the latest BSR draft....
======================================================================
4.1.  Bootstrap Message Format....
"BSR priority
     Contains the BSR priority value of the included BSR.  This field is
     considered as a high order byte when comparing BSR addresses.  Note
     that for historical reasons, the highest BSR priority priority is
     255 (the higher the better), whereas the highest RP Priority (see
     below) is 0 (the lower the better)."

And 

3.2.  Creating the RP-Set at the BSR....
"When an elected BSR is being shut down, it should immediately originate
a Bootstrap message listing its current RP-Set, but with the BSR
priority field set to the lowest priority value possible.  This will
cause the election of a new BSR to happen more quickly."
========================================================================
=


Regards,
Prashant Jhingran

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

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


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


From pim-bounces@ietf.org  Wed Nov  3 00:04:18 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA27257
	for <pim-archive@lists.ietf.org>; Wed, 3 Nov 2004 00:04:18 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CPDA3-0005qB-Ig; Tue, 02 Nov 2004 23:54:19 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CPD64-00032O-Mf
	for pim@megatron.ietf.org; Tue, 02 Nov 2004 23:50:12 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA26672
	for <pim@ietf.org>; Tue, 2 Nov 2004 23:50:10 -0500 (EST)
Received: from catarina.usc.edu ([204.57.0.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CPDLF-0000xg-36
	for pim@ietf.org; Wed, 03 Nov 2004 00:05:58 -0500
Received: from sj-iport-2.cisco.com (sj-iport-2-in.cisco.com [171.71.176.71])
	by catarina.usc.edu (8.12.9/8.12.9) with ESMTP id iA34naoh067034
	for <pim@catarina.usc.edu>; Tue, 2 Nov 2004 20:49:36 -0800 (PST)
	(envelope-from nbhaskar@cisco.com)
Received: from sj-core-1.cisco.com (171.71.177.237)
	by sj-iport-2.cisco.com with ESMTP; 02 Nov 2004 20:59:53 -0800
Received: from cypher.cisco.com (cypher.cisco.com [171.69.11.142])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id iA34nQon001285;
	Tue, 2 Nov 2004 20:49:26 -0800 (PST)
Date: Tue, 2 Nov 2004 20:49:28 -0800 (PST)
From: Nidhi Bhaskar <nbhaskar@cisco.com>
To: Prashant Jhingran <prashantj@huawei.com>
In-Reply-To: <000001c4c15b$54a30110$30226e0a@huawei8tthy486>
Message-ID: <Pine.GSO.4.58.0411022040470.5229@cypher.cisco.com>
References: <000001c4c15b$54a30110$30226e0a@huawei8tthy486>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Cc: pim@catarina.usc.edu, ctbrown@nexthop.com, Stig.Venaas@uninett.no,
        Nidhi Bhaskar <nbhaskar@cisco.com>, bwilliam@cisco.com
Subject: [pim] Re: Default BSR priority issue!
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=subscribe>
Sender: pim-bounces@ietf.org
Errors-To: pim-bounces@ietf.org

> The latest BSR draft no where mentions about the default BSR priority &
> that's why probably few
> Developers/vendors are using the value "Zero" as default BSR priority.
>
> The problem comes when the EBSR is getting shutdown.
>
> There are no means by which the current EBSR can inform the other
> routers in the domain about itself going down.
> (Since default BSR priority and the priority to inform when BSR goes
> down boils down to the same numerical value i.e. Zero).
>
> I think this issue is more important than the RP-mapping we are
> discussion currently and this problem should be resolved in the coming
> BSR draft....this would also lead to faster convergence during graceful
> EBSR shutdown scenarios.

Yes, we could have better defaults, but this problem is fairly simple
to fix via appropriate configuration (unlike the RP-mapping issue
being discussed). So don't agree on the importance ranking :).

That said, I am open to putting in a better default in the spec. Will
include this in the longish todolist we have for this document...

Thanks,
Nidhi.


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


From pim-bounces@ietf.org  Wed Nov  3 02:05:56 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA11685
	for <pim-archive@lists.ietf.org>; Wed, 3 Nov 2004 02:05:55 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CPF4t-0002As-Nr; Wed, 03 Nov 2004 01:57:07 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CPExj-000817-9d
	for pim@megatron.ietf.org; Wed, 03 Nov 2004 01:49:43 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA04329
	for <pim@ietf.org>; Wed, 3 Nov 2004 01:49:42 -0500 (EST)
Received: from sj-iport-2-in.cisco.com ([171.71.176.71]
	helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CPFCy-0003Tm-Kd for pim@ietf.org; Wed, 03 Nov 2004 02:05:30 -0500
Received: from sj-core-2.cisco.com (171.71.177.254)
	by sj-iport-2.cisco.com with ESMTP; 02 Nov 2004 22:59:34 -0800
Received: from dino-lnx.cisco.com (dino-lnx.cisco.com [171.71.54.55])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id iA36n5nC012857;
	Tue, 2 Nov 2004 22:49:06 -0800 (PST)
Received: (from dino@localhost)
	by dino-lnx.cisco.com (8.11.6/8.11.6) id iA36n8H28777;
	Tue, 2 Nov 2004 22:49:08 -0800
Date: Tue, 2 Nov 2004 22:49:08 -0800
Message-Id: <200411030649.iA36n8H28777@dino-lnx.cisco.com>
From: Dino Farinacci <dino@cisco.com>
To: pavlin@icir.org
In-reply-to: message from Pavlin Radoslavov on Mon, 18 Oct 2004 14:00:17 -0700
Subject: Re: [pim] WG Query: draft-farinacci-pim-pop-count-00.txt
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2bf730a014b318fd3efd65b39b48818c
Cc: shep@cisco.com, pavlin@icir.org, pusateri@juniper.net, pim@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=subscribe>
Sender: pim-bounces@ietf.org
Errors-To: pim-bounces@ietf.org

    This response will address the comments from each of Pavlin, Marshall,
    and Pekka, respectively. See my responses inline.

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

    Thanks Pavlin.

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

    No, we did not see this. But both Shep and I will have a look at it.
    Ditto for the GRA stuff too. Thanks Tony for the reference.
   
Pavlin>> 
Pavlin>>  * We need to deal with incremental deployment, otherwise there is
Pavlin>>    no initiative to even start deploying this new scheme. E.g.,
Pavlin>>    ideas from the above paper can be helpful in this aspect.

    People can deploy this when they get new software releases. And since
    the accounting can be obtained per sub-tree, within a domain, you can
    acquire some information about your relative fanout. So we never believe
    it's an all or nothing situation.

Pavlin>>  * In your proposal you overload the Join messages with accounting
Pavlin>>    information.

    We augmented the Encoded Source Address. And yes, since the Joins are
    already going upstream, we piggyback to reduce CPU overhead and an
    addition of new protocols.

Pavlin>>    The advantage of doing that is that you save some network
Pavlin>>    bandwidth and processing cycles, but the result solution becomes
Pavlin>>    a bit too complicated and lacks flexibility. For example, if

    It is not complicated, you simply fill in the fields per route you insert
    in the Join (fields that are stored in the multicast route).

    In terms of a inflexible encoding, that was done on purpose. If we 
    generalized it, then implementations could drastic increase Join sizes
    which would affect tree building. We want it lean and mean. Remember this
    mechanism is not precise in obtaining accounting data. It gives a rough
    feel of "tree attributes". A more comprehensive/precise could be put on
    top of this in the management plane.

Pavlin>>    someone wants to define a new counter, adding such counter to the
Pavlin>>    fixed  message format is impossible without redefining the whole
Pavlin>>    format again.
Pavlin>>    I would rather see those two functionalities separated:
Pavlin>>    the tree management (i.e., the Join/Prune messages), and the
Pavlin>>    tree accounting. By that I mean using a new type control message
Pavlin>>    (for accounting purpose only) which is designed to have
Pavlin>>    extensible format, etc. Then, each counter for example, can be
Pavlin>>    added as an option to the message.

    We did consider another message type but would require using a set of
    resources which are already used for sending periodic JP messages. That
    will certainly use more CPU for traversing the routing table another time
    more messages, more receive processing, etc. 

    I've done some meaurements for 100K routes being periodically joined on
    10 interfaces with 10 neighbors on each (i.e. 100 RPF neighbors 
    distributed eveningly across 100K routes). With either a preemptive or run-
    to-completion scheduling model for your PIM process, it can take up to 10
    seconds to get all the data out. This is assuming a set of routes which
    are all ASM based ((*,G,join-list & prune-list) entries as well as (S,G,
    join-list) entries).

    So we felt the piggybacking would give a better performance/benefit ratio.

Pavlin>> 
Pavlin>>  * Currently, it appears that the mechanism is PIM-SM
Pavlin>>    specific. Rather than redefining the mechanism for PIM-DM, etc,

    I tried to be practical and concluded there is so much more deployment 
    of SM then as DM. But if you needed to send Joins in DM mode for sake of 
    accounting, than, in essence, is your seperate protocol.

    I did this for Multicast Tagswitching a long time ago. That is, for DM
    groups, Joins could be sent for purposes of label binding.

Pavlin>>    I'd prefer to have a protocol-independent mechanism.
Pavlin>>    After all, it appears that the only major thing that currently
Pavlin>>    ties the mechanism to PIM-SM is the message format overloading of
Pavlin>>    the PIM-SM Join messages.

    It's a performance/benefit tradeoff. We chose to have this highly
    performing.

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

    I didn't think we needed that much granularity for link-speed. For node
    count we can increase the size. That was the reason for review, to get
    opinions from people about the types of accounting data they would see
    useful.

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

    Same comment as above.

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

    I think it all depends where the solution goes. We decided PIM was the
    right place to put the functionality so hence bringing it to the PIM
    working group was the obvious choice.

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

    I think this is a good idea. I can add this in the next rev of the draft.
    Thanks Marshall.

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

    Will fix. Thanks.  ;-)

Pekka>> This is coming late, but if it matters..

    It sure does to me (and Shep). Thanks Pekka.

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

    The proposal does not change the elements of operation for the protocol.
    There is a strong attempt to make this inline with the protocol so it is
    easy to deploy without having to plan deployment for a new mechanism as
    well as not affecting the performance of the control plane of the system.

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

    If "a more conventional manner" is SNMP, we'd like to see it perform a bit
    better. Don't you think it's more scalable to poll a single router to find 
    information for a tree at that point in the topology? Versus, having to
    find all branches and poll each one, compile the data, and then display it.

    For the NOC guys who want a quick and easy way to find some tree 
    accounting, all they would have to do is ssh to one of their routers and
    do a show command.

    Of course, once the proposal is more widely accepted, we could MIB the
    new accounting data so you can get SNMP access to the *single* router.

    All, thanks for your comments.

Dino   





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


From pim-bounces@ietf.org  Thu Nov  4 13:06:30 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA16977
	for <pim-archive@lists.ietf.org>; Thu, 4 Nov 2004 13:06:30 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CPlrn-0001fi-9Y; Thu, 04 Nov 2004 12:57:47 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1COhEi-0001hX-07; Mon, 01 Nov 2004 13:49:00 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA17297;
	Mon, 1 Nov 2004 13:48:57 -0500 (EST)
Received: from m106.maoz.com ([205.167.76.9])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1COhTb-00089a-79; Mon, 01 Nov 2004 14:04:27 -0500
Received: from m106.maoz.com (localhost.localdomain [127.0.0.1])
	by m106.maoz.com (8.12.11/8.12.11) with ESMTP id iA1ImN1r031328;
	Mon, 1 Nov 2004 10:48:23 -0800
Received: (from dmm@localhost)
	by m106.maoz.com (8.12.11/8.12.11/Submit) id iA1ImNY9031327;
	Mon, 1 Nov 2004 10:48:23 -0800
X-Authentication-Warning: m106.maoz.com: dmm set sender to dmm@1-4-5.net using
	-f
Date: Mon, 1 Nov 2004 10:48:23 -0800
From: David Meyer <dmm@1-4-5.net>
To: pim@ietf.org, mpls@ietf.org, mboned@lists.uoregon.edu
Message-ID: <20041101184823.GA29981@1-4-5.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4.1i
X-public-key: http://www.1-4-5.net/~dmm/public-key.asc
X-gpg-fingerprint: 2409 8B50 B389 A307 BA5C 2A16 3918 03D6 A099 D8A7
X-philosophy: "I just had to let it go" -- John Lennon
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
X-Mailman-Approved-At: Thu, 04 Nov 2004 12:57:45 -0500
Cc: fenner@research.att.com, bwijnen@lucent.com, david.kessens@nokia.com,
        zinin@psg.com
Subject: [pim] MP-LSP issues to be discussed at MBONED
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=subscribe>
Sender: pim-bounces@ietf.org
Errors-To: pim-bounces@ietf.org


	Folks,

	In an attempt to ensure that we have good communication
	between the multicast and MPLS groups around the P2MP LSP
	issues (really MP-LSP), I have scheduled some time during
	the MBONED WG for overview and discussion. So far this
	part of the agenda looks like this:

	  MP-LSPs (Requirements/overview of current status)   30 minutes
	  p2mp ping and traceroute                            15 minutes
           draft-yasukawa-mpls-p2mp-lsp-ping-00.txt
           Farrel, et. al.

	If you have additional topics you would like to see
	discussed, please let me know.

	Thanks,

	Dave

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


From pim-bounces@ietf.org  Thu Nov  4 13:06:34 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA16998
	for <pim-archive@lists.ietf.org>; Thu, 4 Nov 2004 13:06:34 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CPlsw-0001wV-OA; Thu, 04 Nov 2004 12:58:58 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CP2Gs-0005Tx-LU
	for pim@megatron.ietf.org; Tue, 02 Nov 2004 12:16:38 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA13695
	for <pim@ietf.org>; Tue, 2 Nov 2004 12:16:36 -0500 (EST)
Received: from mailg.surrey.ac.uk ([131.227.102.21])
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CP2W0-0007Rg-RO
	for pim@ietf.org; Tue, 02 Nov 2004 12:32:18 -0500
Received: from ads33.surrey.ac.uk by mailg.surrey.ac.uk with SMTP Local (PP)
	with ESMTP; Tue, 2 Nov 2004 16:59:40 +0000
Received: from EVS-EC1-NODE1.surrey.ac.uk ([131.227.102.136])
	by ads33.surrey.ac.uk with Microsoft SMTPSVC(6.0.3790.211);
	Tue, 2 Nov 2004 16:59:40 +0000
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 2 Nov 2004 16:59:18 -0000
Message-ID: <FB87FF23EB14174C9AF6E259DE2F5A4308FF9B@EVS-EC1-NODE1.surrey.ac.uk>
Thread-Topic: multiple RPFexit points?
Thread-Index: AcTA/Urmzgva/lOtSsOho0HZhPBtJw==
From: "Wang N Mr (PG/R - Electronic Eng)" <N.Wang@surrey.ac.uk>
To: pim <pim@ietf.org>
X-OriginalArrivalTime: 02 Nov 2004 16:59:40.0061 (UTC)
	FILETIME=[5781F4D0:01C4C0FD]
X-Spam-Score: 0.8 (/)
X-Scan-Signature: 4b800b1eab964a31702fa68f1ff0e955
X-Mailman-Approved-At: Thu, 04 Nov 2004 12:58:56 -0500
Subject: [pim] multiple RPFexit points?
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="===============1589298027=="
Sender: pim-bounces@ietf.org
Errors-To: pim-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1589298027==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C4C0FD.57403A26"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C4C0FD.57403A26
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Dear all,
  I have a small question regarding inter-domain mcast routing using =
MBGP/PIM-SM:
If two border routers within a domain both receive reachability =
advertisements towards the
same source (prefix), can I configure both to be valid RPF router (e.g., =
by setting the same
local_pref etc)? In this case, the multicast traffic from the source can =
be injected
via different border routers. For example, if border router A and B both =
can lead to the=20
source S, can I config my border routers C and D (with receivers) in =
such a way that
C selects A as the best exit (because C is closer to A compared to B) =
while D selects B as=20
the valid RPF peer? If yes, can anyone tell me how to enforce this by =
setting proper MBGP=20
policy?
  Thanks in advance
Ning
=20
=20

------_=_NextPart_001_01C4C0FD.57403A26
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML =
DIR=3Dltr><HEAD><META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1"></HEAD><BODY><DIV><FONT face=3D'Arial' =
color=3D#000000 size=3D2>Dear all,</FONT></DIV>=0A=
<DIV><FONT face=3DArial size=3D2>&nbsp; I have a small question =
regarding =0A=
inter-domain mcast routing using MBGP/PIM-SM:</FONT></DIV>=0A=
<DIV><FONT face=3DArial size=3D2>If two border routers within a =
domain&nbsp;both =0A=
receive&nbsp;reachability advertisements towards the</FONT></DIV>=0A=
<DIV><FONT face=3DArial size=3D2>same source (prefix), can I configure =
both to be =0A=
valid RPF router (e.g., by setting the same</FONT></DIV>=0A=
<DIV><FONT face=3DArial size=3D2>local_pref etc)? In this case, the =
multicast =0A=
traffic from the source can be injected</FONT></DIV>=0A=
<DIV><FONT face=3DArial size=3D2>via different border routers. For =
example, if =0A=
border router A and B both can lead to the </FONT></DIV>=0A=
<DIV><FONT face=3DArial size=3D2>source S, can I config my border =
routers C and D =0A=
(with receivers) in such a way that</FONT></DIV>=0A=
<DIV><FONT face=3DArial size=3D2>C selects A as the best exit (because C =
is closer =0A=
to A compared to B) while D selects B as </FONT></DIV>=0A=
<DIV><FONT face=3DArial size=3D2>the valid RPF peer? If yes, can anyone =
</FONT><FONT =0A=
face=3DArial size=3D2>tell me how to enforce this by setting proper MBGP =0A=
</FONT></DIV>=0A=
<DIV><FONT face=3DArial size=3D2>policy?</FONT></DIV>=0A=
<DIV><FONT face=3DArial size=3D2>&nbsp; Thanks in advance</FONT></DIV>=0A=
<DIV><FONT face=3DArial size=3D2>Ning</FONT></DIV>=0A=
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV></BODY></HTML>
------_=_NextPart_001_01C4C0FD.57403A26--


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

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

--===============1589298027==--



From pim-bounces@ietf.org  Thu Nov  4 13:07:18 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA17117
	for <pim-archive@lists.ietf.org>; Thu, 4 Nov 2004 13:07:17 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CPltU-00025C-5d; Thu, 04 Nov 2004 12:59:32 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CP2Rl-0002hv-IE
	for pim@megatron.ietf.org; Tue, 02 Nov 2004 12:27:53 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA14676
	for <pim@ietf.org>; Tue, 2 Nov 2004 12:27:51 -0500 (EST)
Received: from mailg.surrey.ac.uk ([131.227.102.21])
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CP2gu-0007l1-WD
	for pim@ietf.org; Tue, 02 Nov 2004 12:43:33 -0500
Received: from ads33.surrey.ac.uk by mailg.surrey.ac.uk with SMTP Local (PP)
	with ESMTP; Tue, 2 Nov 2004 17:25:56 +0000
Received: from EVS-EC1-NODE1.surrey.ac.uk ([131.227.102.136])
	by ads33.surrey.ac.uk with Microsoft SMTPSVC(6.0.3790.211);
	Tue, 2 Nov 2004 17:25:53 +0000
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 2 Nov 2004 17:23:48 -0000
Message-ID: <FB87FF23EB14174C9AF6E259DE2F5A4308FF9C@EVS-EC1-NODE1.surrey.ac.uk>
Thread-Topic: multiple RPFexit points?
Thread-Index: AcTA/Urmzgva/lOtSsOho0HZhPBtJwAA2wT0
From: "Wang N Mr (PG/R - Electronic Eng)" <N.Wang@surrey.ac.uk>
To: pim <pim@ietf.org>
X-OriginalArrivalTime: 02 Nov 2004 17:25:53.0082 (UTC)
	FILETIME=[0119E9A0:01C4C101]
X-Spam-Score: 0.8 (/)
X-Scan-Signature: 14582b0692e7f70ce7111d04db3781c8
X-Mailman-Approved-At: Thu, 04 Nov 2004 12:59:30 -0500
Subject: [pim] FW: multiple RPFexit points?
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="===============0318554685=="
Sender: pim-bounces@ietf.org
Errors-To: pim-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0318554685==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C4C101.00AAE97D"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C4C101.00AAE97D
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Sorry I forgot to mention that my question below is confined to SSM =
where no RP
is involved.

________________________________

From: Wang N Mr (PG/R - Electronic Eng)
Sent: Tue 02/11/2004 16:59
To: pim@ietf.org
Subject: multiple RPFexit points?


Dear all,
  I have a small question regarding inter-domain mcast routing using =
MBGP/PIM-SM:
If two border routers within a domain both receive reachability =
advertisements towards the
same source (prefix), can I configure both to be valid RPF router (e.g., =
by setting the same
local_pref etc)? In this case, the multicast traffic from the source can =
be injected
via different border routers. For example, if border router A and B both =
can lead to the=20
source S, can I config my border routers C and D (with receivers) in =
such a way that
C selects A as the best exit (because C is closer to A compared to B) =
while D selects B as=20
the valid RPF peer? If yes, can anyone tell me how to enforce this by =
setting proper MBGP=20
policy?
  Thanks in advance
Ning
=20
=20

------_=_NextPart_001_01C4C101.00AAE97D
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">=0A=
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML =
DIR=3Dltr><HEAD></HEAD><BODY>=0A=
<DIV id=3DidOWAReplyText99212 dir=3Dltr>=0A=
<DIV dir=3Dltr><FONT face=3DArial color=3D#000000 size=3D2>Sorry I =
forgot to mention =0A=
that my question below is confined to SSM where no RP</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>is =
involved.</FONT></DIV></DIV>=0A=
<DIV dir=3Dltr><BR>=0A=
<HR tabIndex=3D-1>=0A=
<FONT face=3DTahoma size=3D2><B>From:</B> Wang N Mr (PG/R - Electronic =0A=
Eng)<BR><B>Sent:</B> Tue 02/11/2004 16:59<BR><B>To:</B> =0A=
pim@ietf.org<BR><B>Subject:</B> multiple RPFexit =
points?<BR></FONT><BR></DIV>=0A=
<DIV dir=3Dltr>=0A=
<DIV><FONT face=3DArial color=3D#000000 size=3D2>Dear all,</FONT></DIV>=0A=
<DIV><FONT face=3DArial size=3D2>&nbsp; I have a small question =
regarding =0A=
inter-domain mcast routing using MBGP/PIM-SM:</FONT></DIV>=0A=
<DIV><FONT face=3DArial size=3D2>If two border routers within a =
domain&nbsp;both =0A=
receive&nbsp;reachability advertisements towards the</FONT></DIV>=0A=
<DIV><FONT face=3DArial size=3D2>same source (prefix), can I configure =
both to be =0A=
valid RPF router (e.g., by setting the same</FONT></DIV>=0A=
<DIV><FONT face=3DArial size=3D2>local_pref etc)? In this case, the =
multicast =0A=
traffic from the source can be injected</FONT></DIV>=0A=
<DIV><FONT face=3DArial size=3D2>via different border routers. For =
example, if =0A=
border router A and B both can lead to the </FONT></DIV>=0A=
<DIV><FONT face=3DArial size=3D2>source S, can I config my border =
routers C and D =0A=
(with receivers) in such a way that</FONT></DIV>=0A=
<DIV><FONT face=3DArial size=3D2>C selects A as the best exit (because C =
is closer =0A=
to A compared to B) while D selects B as </FONT></DIV>=0A=
<DIV><FONT face=3DArial size=3D2>the valid RPF peer? If yes, can anyone =
</FONT><FONT =0A=
face=3DArial size=3D2>tell me how to enforce this by setting proper MBGP =0A=
</FONT></DIV>=0A=
<DIV><FONT face=3DArial size=3D2>policy?</FONT></DIV>=0A=
<DIV><FONT face=3DArial size=3D2>&nbsp; Thanks in advance</FONT></DIV>=0A=
<DIV><FONT face=3DArial size=3D2>Ning</FONT></DIV>=0A=
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV></DIV></BODY></HTML>
------_=_NextPart_001_01C4C101.00AAE97D--


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

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

--===============0318554685==--



From pim-bounces@ietf.org  Thu Nov  4 13:07:57 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA17220
	for <pim-archive@lists.ietf.org>; Thu, 4 Nov 2004 13:07:57 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CPluC-0002VN-JS; Thu, 04 Nov 2004 13:00:16 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CPQ7J-0002FM-Ih; Wed, 03 Nov 2004 13:44:23 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA06581;
	Wed, 3 Nov 2004 13:44:20 -0500 (EST)
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CPQMg-00045c-9b; Wed, 03 Nov 2004 14:00:15 -0500
Received: from rtp-core-2.cisco.com (64.102.124.13)
	by rtp-iport-1.cisco.com with ESMTP; 03 Nov 2004 14:07:31 -0500
X-BrightmailFiltered: true
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com
	[161.44.122.62])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id iA3Ihkv7009172; 
	Wed, 3 Nov 2004 13:43:47 -0500 (EST)
Received: from swallow-mac.cisco.com ([161.44.74.242])
	by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id AMT70570;
	Wed, 3 Nov 2004 13:43:45 -0500 (EST)
Received: by swallow-mac.cisco.com (Postfix, from userid 501)
	id C0E37167651; Wed,  3 Nov 2004 13:43:54 -0500 (EST)
Received: from cisco.com (localhost [127.0.0.1])
	by swallow-mac.cisco.com (Postfix) with ESMTP
	id 91B80167648; Wed,  3 Nov 2004 13:43:54 -0500 (EST)
To: David Meyer <dmm@1-4-5.net>
In-reply-to: Your message of "Mon, 01 Nov 2004 10:48:23 PST."
	<20041101184823.GA29981@1-4-5.net> 
From: George Swallow <swallow@cisco.com>
X-Mailer: MH-E 7.4.3; nmh 1.1; GNU Emacs 21.2.1
Date: Wed, 03 Nov 2004 13:43:53 -0500
Message-Id: <20041103184354.C0E37167651@swallow-mac.cisco.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2
X-Mailman-Approved-At: Thu, 04 Nov 2004 13:00:15 -0500
Cc: swallow@cisco.com, mpls@ietf.org, david.kessens@nokia.com,
        mboned@lists.uoregon.edu, fenner@research.att.com, pim@ietf.org
Subject: [pim] Re: [mpls] MP-LSP issues to be discussed at MBONED 
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=subscribe>
Sender: pim-bounces@ietf.org
Errors-To: pim-bounces@ietf.org

Dave -

Since the members of the MPLS wg are not of a single opinion on what
MPLS is trying to accomplish, I'd like a few minutes up front to say
(wearing my chair hat) what I believe we are chartered to do (and by
implication what we are not chartered to do).

...George

========================================================================
George Swallow             Cisco Systems                  (978) 936-1398
                           1414 Massachusetts Avenue
                           Boxborough, MA 01719


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


From pim-bounces@ietf.org  Wed Nov 10 11:33:57 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA28079
	for <pim-archive@lists.ietf.org>; Wed, 10 Nov 2004 11:33:57 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CRvKa-0003UW-Gm; Wed, 10 Nov 2004 11:28:24 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CRvBL-0001A7-Cn
	for pim@megatron.ietf.org; Wed, 10 Nov 2004 11:18:51 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA26364
	for <pim@ietf.org>; Wed, 10 Nov 2004 11:18:48 -0500 (EST)
Received: from colo-dns-ext1.juniper.net ([207.17.137.57])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CRvCH-0006M6-Ku
	for pim@ietf.org; Wed, 10 Nov 2004 11:19:53 -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 iAAGIG908473; 
	Wed, 10 Nov 2004 08:18:16 -0800 (PST)
	(envelope-from pusateri@juniper.net)
Received: from juniper.net (garnet.juniper.net [172.17.28.17])
	by merlot.juniper.net (8.11.3/8.11.3) with ESMTP id iAAGIBe06026;
	Wed, 10 Nov 2004 08:18:11 -0800 (PST)
	(envelope-from pusateri@juniper.net)
Message-Id: <200411101618.iAAGIBe06026@merlot.juniper.net>
To: pim@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <59199.1100103491.1@juniper.net>
Date: Wed, 10 Nov 2004 08:18:11 -0800
From: Tom Pusateri <pusateri@juniper.net>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Cc: Tom Pusateri <pusateri@juniper.net>, Mike McBride <mmcbride@cisco.com>
Subject: [pim] PIM State Refresh Reduction
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=subscribe>
Sender: pim-bounces@ietf.org
Errors-To: pim-bounces@ietf.org

Many of us have been thinking about ways to reduce the effects of
periodic join/prune processing in PIM for some time. Recently, the
L3VPN working group identified this as a problem for MVPNs and
encouraged the PIM working group to provide a solution.

While the request came in the context of VPNs, this is not a VPN specific
problem but one that all PIM deployments could benefit from. Therefore,
we would like to create a design team to gather requirements, document the
issue we're trying to solve, and propose a solution.

I am sending this note to solicit volunteers to help with one or more of
the three parts above.

Please send a note to myself and Mike if you have the interest and
time to participate.

Thanks,
Tom & Mike

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


From pim-bounces@ietf.org  Wed Nov 10 21:59:21 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA05265
	for <pim-archive@lists.ietf.org>; Wed, 10 Nov 2004 21:59:21 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CS52j-0007tG-Q1; Wed, 10 Nov 2004 21:50:37 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CS4ue-0006Rs-Qt
	for pim@megatron.ietf.org; Wed, 10 Nov 2004 21:42:16 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA03911
	for <pim@ietf.org>; Wed, 10 Nov 2004 21:42:14 -0500 (EST)
Received: from www.laneandmimi.com
	([206.223.132.4] helo=cohiba.phoobar.net. ident=root)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CS4vi-00066e-J8
	for pim@ietf.org; Wed, 10 Nov 2004 21:43:23 -0500
Received: from cohiba.phoobar.net. (localhost.localdomain [127.0.0.1])
	by cohiba.phoobar.net. (8.12.10/8.12.10/check_local-5) with ESMTP id
	iAB2g85U024979; Wed, 10 Nov 2004 18:42:08 -0800
Received: (from lane@localhost)
	by cohiba.phoobar.net. (8.12.10/8.12.10/Submit) id iAB2g8gG024978;
	Wed, 10 Nov 2004 18:42:08 -0800
X-Authentication-Warning: cohiba.phoobar.net.: lane set sender to
	lane@laneandmimi.com using -f
Date: Wed, 10 Nov 2004 18:42:08 -0800
From: Lane Patterson <lane@laneandmimi.com>
To: Dino Farinacci <dino@cisco.com>
Subject: Re: [pim] WG Query: draft-farinacci-pim-pop-count-00.txt
Message-ID: <20041110184208.A24854@laneandmimi.com>
References: <200411030649.iA36n8H28777@dino-lnx.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0pre3i
In-Reply-To: <200411030649.iA36n8H28777@dino-lnx.cisco.com>
X-Title: Chief Diaper Changer
X-Organization: Lane And Mimi Dot Com
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Cc: pim@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=subscribe>
Sender: pim-bounces@ietf.org
Errors-To: pim-bounces@ietf.org

Unfortunately I wasn't able to make it out to this IETF or provide input
in time for yesterday's PIM meetings, but my input from standpoint of an 
operator of a multicast exchange is that this draft is very useful and 
practical, and at least should continue to be considered and tweaked.
The tree info that it provides from any node gives the type of practical 
feedback to operators on just how heavy the branches are, and hence the 
extent to which they are seeing a practical benefit from multicast, as 
opposed to just sending packets down a black hole.

In practical implementation, I could see operators that would want to 
enable/disable this type of accounting intra or inter-AS (although I would 
hope all would want to leave it on everywhere).  So it would be useful to 
proactively handle/count the links within a subtree which do not support 
this draft--as Marshall suggested.

I'm not sure overloading PIM with this is problematic, as the mechanisms appear
lightweight and this is a more natural way of tracking than outside of the 
tree building process.  This is way more useful than having to correlate 
SNMP-gathered data across multiple nodes, for instance, and more analogous
to what an IGP link state database provides.

I haven't seen any discussion on why the bandwidth and TZ parameters are useful
or needed.  I would think this draft should focus more on the size/shape of the
distribution trees, and less on things that receiver clients (and interaction 
with SSM source, in that particular case) can take care of like picking the
right stream rate.

Cheers,
-Lane

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


From pim-bounces@ietf.org  Thu Nov 11 11:11:10 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA26602
	for <pim-archive@lists.ietf.org>; Thu, 11 Nov 2004 11:11:10 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CSHVZ-0007QX-8C; Thu, 11 Nov 2004 11:09:13 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CSHOU-0006AX-7l
	for pim@megatron.ietf.org; Thu, 11 Nov 2004 11:01:54 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA25837
	for <pim@ietf.org>; Thu, 11 Nov 2004 11:01:52 -0500 (EST)
Received: from gate13.itt.com ([151.190.254.108] helo=fwetgfw3r.itt.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CSHPf-0005Yp-TK
	for pim@ietf.org; Thu, 11 Nov 2004 11:03:08 -0500
Received: from no.name.available by fwetgfw3r.itt.com
	via smtpd (for ietf-mx.ietf.org [132.151.6.1]) with ESMTP;
	Thu, 11 Nov 2004 11:01:52 -0500
Received: from njbridge01.avionics.de.ittind.com ([151.190.100.204]) by
	fwdcmail6.fwdc.de.ittind.com with Microsoft SMTPSVC(5.0.2195.6713); 
	Thu, 11 Nov 2004 10:51:42 -0500
Received: from ACDNJMAILSRV02.acd.de.ittind.com ([151.190.3.218]) by
	njbridge01.avionics.de.ittind.com with Microsoft
	SMTPSVC(6.0.3790.211); Thu, 11 Nov 2004 10:51:25 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.6556.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [pim] PIM State Refresh Reduction
Date: Thu, 11 Nov 2004 10:51:22 -0500
Message-ID: <2CA4524FA012F14BAE5D896D492B38682C59DC@ACDNJMAILSRV02.acd.de.ittind.com>
Thread-Topic: [pim] PIM State Refresh Reduction
Thread-Index: AcTHQyVaVbW+cZ6dRluHeAUpdF345AAwt2GQ
From: "Nicholas, Jonathan" <Jonathan.Nicholas@itt.com>
To: "Tom Pusateri" <pusateri@juniper.net>, <pim@ietf.org>
X-OriginalArrivalTime: 11 Nov 2004 15:51:25.0155 (UTC)
	FILETIME=[4C78A330:01C4C806]
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5
Content-Transfer-Encoding: quoted-printable
Cc: Mike McBride <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>
Sender: pim-bounces@ietf.org
Errors-To: pim-bounces@ietf.org
Content-Transfer-Encoding: quoted-printable


As a clarification, is this refering specifically to PIM-DM State Refresh,=
 or state refresh in a more generic sense that applies to all PIM=
 implementations, or just the PIM-SM states that need to be refreshed? =
 Thanks.

> -----Original Message-----
> From: pim-bounces@ietf.org [mailto:pim-bounces@ietf.org]On=0D
> Behalf Of Tom
> Pusateri
> Sent: Wednesday, November 10, 2004 11:18 AM
> To: pim@ietf.org
> Cc: Tom Pusateri; Mike McBride
> Subject: [pim] PIM State Refresh Reduction
>=0D
>=0D
> Many of us have been thinking about ways to reduce the effects of
> periodic join/prune processing in PIM for some time. Recently, the
> L3VPN working group identified this as a problem for MVPNs and
> encouraged the PIM working group to provide a solution.
>=0D
> While the request came in the context of VPNs, this is not a=0D
> VPN specific
> problem but one that all PIM deployments could benefit from.=0D
> Therefore,
> we would like to create a design team to gather requirements,=0D
> document the
> issue we're trying to solve, and propose a solution.
>=0D
> I am sending this note to solicit volunteers to help with one=0D
> or more of
> the three parts above.
>=0D
> Please send a note to myself and Mike if you have the interest and
> time to participate.
>=0D
> Thanks,
> Tom & Mike
>=0D
> _______________________________________________
> pim mailing list
> pim@ietf.org
> https://www1.ietf.org/mailman/listinfo/pim
>=0D

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

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


From pim-bounces@ietf.org  Thu Nov 11 17:05:22 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA03922
	for <pim-archive@lists.ietf.org>; Thu, 11 Nov 2004 17:05:22 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CSMpC-0001zu-OX; Thu, 11 Nov 2004 16:49:50 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CSMkW-00008v-7U
	for pim@megatron.ietf.org; Thu, 11 Nov 2004 16:45:03 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA02028
	for <pim@ietf.org>; Thu, 11 Nov 2004 16:44:58 -0500 (EST)
Received: from colo-dns-ext1.juniper.net ([207.17.137.57])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CSMlk-00069O-OH
	for pim@ietf.org; Thu, 11 Nov 2004 16:46:17 -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 iABLiS923794
	for <pim@ietf.org>; Thu, 11 Nov 2004 13:44:28 -0800 (PST)
	(envelope-from pusateri@juniper.net)
Received: from juniper.net (garnet.juniper.net [172.17.28.17])
	by merlot.juniper.net (8.11.3/8.11.3) with ESMTP id iABLiNe68445
	for <pim@ietf.org>; Thu, 11 Nov 2004 13:44:23 -0800 (PST)
	(envelope-from pusateri@juniper.net)
Message-Id: <200411112144.iABLiNe68445@merlot.juniper.net>
To: pim@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <36309.1100209463.1@juniper.net>
Date: Thu, 11 Nov 2004 13:44:23 -0800
From: Tom Pusateri <pusateri@juniper.net>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 46ad68ada464411807db2a0edd5648ae
Subject: [pim] Satisying RFC 1264 requirements rough 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>
Sender: pim-bounces@ietf.org
Errors-To: pim-bounces@ietf.org

Here is a first pass at documenting the fact that we have satisfied
the requirements to move the PIM sparse mode spec to Proposed Standard.
If the working group has any suggestions for improvements, please
let me know as soon as possible for inclusion in this document.
Otherwise, its off to the IESG.

Thanks,
Tom





Network Working Group                                       Tom Pusateri
Internet-Draft                                          Juniper Networks
Expires: May 11, 2005                                      November 2004





            PIM IETF Proposed Standard Requirements Analysis



Status of this Memo


   This memo provides information for the Internet community. It does
   not specify an Internet standard of any kind.  Distribution of this
   memo is unlimited.


1.  Introduction

   This analysis provides supporting documentation to advance the
   Protocol Independent Multicast (PIM) routing protocol from the IETF
   Experimental status to Proposed Standard. PIM was first published as
   RFC 2117 in 1997 and then again as RFC 2362 in 1998. The protocol was
   classified as Experimental in both of these documents. The PIM
   protocol specification was then rewritten in whole in order to more
   fully specify the protocol.  It is this new specification that is to
   be advanced to Proposed Standard.


2.  RFC 1264 Requirements

   Section 4.0 of RFC 1264 [ROUTESTD] describes the requirements for
   routing protocols to advance to Proposed Standard. Each requirement
   is listed below along with an explanation of how the requirement has
   been satisfied.


2.1.  Documents specifying the Protocol and its Usage

   The authors of the new PIM specification have taken considerable care
   to fully specify the protocol operation. It removes all known
   ambiguities and tries to normalize corner cases that existed in the
   previous specification. It has been used to provide several
   interoperable implementations by developers that were not authors of
   the specification.  These implementations will be described below.



Pusateri                                                        [Page 1]



Internet-Draft            PIM Proposed Standard            November 2004


2.2.  Management Information Base

   A Management Information Base for PIM is currently specified in RFC
   2934 [PIMMIB].  This MIB has many implementations and has been used
   by network management applications for several years. Updates to this
   MIB to support IPv6 and other improvements based on operation
   experience are in progress in the PIM Working Group of the IETF.


2.3.  Explicit Security Architecture

   The new PIM protocol specification contains an extensive security
   section explaining its security features and limitations. Data
   integrity protection and groupwise data origin authentication is
   provided for PIM protocol messages.


2.4.  Implementation Existence

   There are at least 3 known independent implementations of the new
   protocol specification and there are over 6 independent
   implementations of a previous version (RFC 2362) of the
   specification. The new specification was carefully written to be
   backward compatible with the old specification allowing
   implementations compliant with RFC 2362 to also be compliant with the
   new specification.

   The 3 implementations of the new version are described below:

   XORP
      The XORP project [XORP] has an open-source implementation of PIM-
      SMv2 as specified in the draft-ietf-pim-sm-v2-new-11.txt.  It was
      written by Pavlin Radoslavov <pavlin@icir.org> and has been
      available to the public since December 2002.  Pavlin is not an
      author of the protocol specification. It does not use any other
      existing code as a base.

   Cisco IOS/IOX
      Cisco Systems, Inc. has written an implementation of the new
      protocol specification which has been deployed in production
      routers.  There exists an IOS implementation for IPv6 only. There
      exists an IOX implementation for both IPv4 and IPv6. This code was
      initially written by Isidor Kouvelas <kouvelas@cisco.com>. It does
      not depend on any existing code base.  Isidor is a co-author of
      the protocol specification.

   Infosys, Ltd.
      Infosys has developed a full implementation of the new



Pusateri                                                        [Page 2]



Internet-Draft            PIM Proposed Standard            November 2004


      specification. It was written by Bharat Joshi
      <<bharat_joshi@infosys.com> and is used in commercial products.
      Bharat is not an author of the protocol specification.


2.5.  Evidence of Testing


   Cisco
      The Cisco implementation has undergone extensive laboratory
      testing as well as testing in production deployments. It is found
      to interoperate with implementations of earlier versions of the
      PIM protocol specification.


   XORP
      The XORP PIM-SM implementation has been thoughtfully tested
      internally by the XORP project. The emphasis during testing has
      been on correctness. In a typical setup, a PIM-SM router's
      behavior is tested by connecting it to external packet generators
      and observers. The packet generators are used to generate messages
      such as IGMP and PIM-SM control packets, and multicast data
      packets.  The packet observers are used to observe the PIM-SM
      control packets generated by the PIM-SM router under test, and to
      observe the data packets that may be forwarded by that router. In
      addition, the router's command-line interface has been used to
      observe its internal state during some of the tests.

      The test scenarios have been designed to closely follow the
      protocol specification (e.g., a separate test has been created for
      each event in the various protocol state machines, etc). All test
      scenarios are described in detail in [XORP-Test].

      The major tested features are:

      1. Multicast data forwarding.

      2. PIM Hello messages exchange, PIM router neighbor discovery,
         option exchange, and DR election.

      3. PIM Register messages transmission and reception, PIM Register
         state machine, multicast data packets encapsulation and
         decapsulation.

      4. Transmission and reception of PIM Join/Prune messages, upstream
         and downstream protocol state machines. The tests consider the
         following state: (*,*,RP), (*,G), (S,G) and (S,G,rpt).




Pusateri                                                        [Page 3]



Internet-Draft            PIM Proposed Standard            November 2004


      5. Transmission and reception of PIM Assert messages and the per-
         interface (*,G) and (S,G) Assert state machines.

      6. PIM Bootstrap mechanism: transmission, reception and forwarding
         of PIM Bootstrap messages, transmission and reception of PIM
         Cand-RP-Adv messages, candidate and non-candidate BSR state
         machines, creating the RP-Set at the BSR, receiving and using
         the RP-Set, semantic fragmentation of BSMs.

      In the final tests, the tested router behaved as specified in the
      PIM-SM protocol specification. All issues found in the protocol
      specification itself have been corrected in earlier versions of
      the Internet Draft.


2.6.  Suitability

   PIM Sparse-Mode is a protocol for efficiently routing multicast
   groups that may span wide-area (and inter-domain) Internets.  PIM
   uses the underlying unicast routing to provide reverse-path
   information for multicast tree building but it is not dependent on
   any particular unicast routing protocol.


2.7.  Authentication Mechanisms

   PIM specifies the use of the IP security authentication header to
   provide data integrity protection and groupwise data origin
   authentication of protocol messages. The specific AH authentication
   algorithm and parameters, including the choice of authentication
   algorithm and the choice of key, are configured by the network
   administrator. The threats associated with receiving forged PIM
   messages are outlined in the security considerations section of the
   protocol specification.


3.  Acknowledgments

   Pavlin Radoslavov provided text for the section on XORP testing.


4.  Normative References


   [PIMMIB]    McCloghrie, K., Farinacci, D., Thaler, D., Fenner, B.,
               "Protocol Independent Multicast MIB for IPv4", RFC 2934,
               October 2000.




Pusateri                                                        [Page 4]



Internet-Draft            PIM Proposed Standard            November 2004


5.  Informative References


   [ROUTESTD]  Hinden, R., "Internet Routing Protocol Standardization
               Criteria", RFC 1264, October 1991.

   [XORP]      XORP Project, http://www.xorp.org/

   [XORP-Test] XORP PIM-SM Test Suite,
               http://www.xorp.org/releases/current/docs/pim_test-
               suite/pim_testsuite.pdf


6.  Author's Address


   Tom Pusateri
   Juniper Networks, Inc.
   1194 North Mathilda Avenue
   Sunnyvale, CA 94089 USA
   Phone:    (919) 807-0023
   EMail:    pusateri@juniper.net



7.  Full Copyright Statement

   Copyright (C) The Internet Society (2004).  This document is subject
   to the rights, licenses and restrictions contained in BCP 78, and
   except as set forth therein, the authors retain all their rights.


8.  Disclaimer

   This document and the information contained herein are provided on an
   "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
   OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
   ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
   INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
   INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
   WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE."










Pusateri                                                        [Page 5]






                             Table of Contents


   1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . .   1
   2. RFC 1264 Requirements  . . . . . . . . . . . . . . . . . . . .   1
   2.1. Documents specifying the Protocol and its Usage  . . . . . .   1
   2.2. Management Information Base  . . . . . . . . . . . . . . . .   2
   2.3. Explicit Security Architecture . . . . . . . . . . . . . . .   2
   2.4. Implementation Existence . . . . . . . . . . . . . . . . . .   2
   2.5. Evidence of Testing  . . . . . . . . . . . . . . . . . . . .   3
   2.6. Suitability  . . . . . . . . . . . . . . . . . . . . . . . .   4
   2.7. Authentication Mechanisms  . . . . . . . . . . . . . . . . .   4
   3. Acknowledgments  . . . . . . . . . . . . . . . . . . . . . . .   4
   4. Normative References . . . . . . . . . . . . . . . . . . . . .   4
   5. Informative References . . . . . . . . . . . . . . . . . . . .   5
   6. Author's Address . . . . . . . . . . . . . . . . . . . . . . .   5
   7. Full Copyright Statement . . . . . . . . . . . . . . . . . . .   5
   8. Disclaimer . . . . . . . . . . . . . . . . . . . . . . . . . .   5

































Pusateri                                                        [Page i]


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


From pim-bounces@ietf.org  Fri Nov 12 14:32:30 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA04674
	for <pim-archive@lists.ietf.org>; Fri, 12 Nov 2004 14:32:30 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CSh4t-0000ld-Rc; Fri, 12 Nov 2004 14:27:23 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CSh4A-0000SE-0R
	for pim@megatron.ietf.org; Fri, 12 Nov 2004 14:26:38 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA04309
	for <pim@ietf.org>; Fri, 12 Nov 2004 14:26:36 -0500 (EST)
Received: from sj-iport-1-in.cisco.com ([171.71.176.70]
	helo=sj-iport-1.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CSh5a-0000JJ-K2 for pim@ietf.org; Fri, 12 Nov 2004 14:28:06 -0500
Received: from sj-core-5.cisco.com (171.71.177.238)
	by sj-iport-1.cisco.com with ESMTP; 12 Nov 2004 11:40:23 -0800
X-BrightmailFiltered: true
Received: from cisco.com (cypher.cisco.com [171.69.11.142])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id iACJQ2KU004100;
	Fri, 12 Nov 2004 11:26:02 -0800 (PST)
Received: (from eckert@localhost)
	by cisco.com (8.8.8-Cisco List Logging/8.8.8) id LAA08634;
	Fri, 12 Nov 2004 11:26:03 -0800 (PST)
Date: Fri, 12 Nov 2004 11:26:03 -0800
From: Toerless Eckert <eckert@cisco.com>
To: Tom Pusateri <pusateri@juniper.net>
Subject: Re: [pim] PIM State Refresh Reduction
Message-ID: <20041112192603.GF19968@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4i
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b4a0a5f5992e2a4954405484e7717d8c
Cc: Mike McBride <mmcbride@cisco.com>, pim@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=subscribe>
Sender: pim-bounces@ietf.org
Errors-To: pim-bounces@ietf.org

To repeat on the mailing list what i said during the working group meeting:

a) "The PIM-SM RFC is first"

   We first need to have the current PIM-SM draft go out the door and
   become an RFC. No changes whatsoever from the WG are to be considered
   for this draft anymore.

b) "refresh reduction is not the same as PIM Hello reduction"

   We should clealy differentiate between "PIM refresh reduction" that i
   think applies primarily to PIM j/p messages (and maybe asserts) and
   "PIM Hello reduction" because i think there may be common requirements
   for "PIM refresh reduction" across different solutions, but likely
   different "PIM Hello reduction" methods in different solutions.

   As an example, in networks with large scale numbers of directly 
   connected PIM routers (like a satellite network), actual PIM Hello
   _reduction_ is likely required, whereas in MVPN and other large scale
   networks with indirectly connected PIM neighbors, PIM Hellos might
   rather be completely replaced by for example leveraging some form of
   BGP information.

c) "Useful but not mandatory for MVPN"

   Refresh reduction came up as a result of a discussion in L2VPN about
   the rosen MVPN draft. There is i think no agreement as to what importance
   refresh reduction has for moving that draft forward.
   
   I think that refresh reduction is absolutely NOT a mandatory requirement 
   for MVPN work to progress. I think it would be a very good option
   for future scalability extensions though, but by beng targeted as a
   generic PIM improvement it logically becomes a modular issue independent
   of the actual MVPN specs.

d) "More work for PIM than just refresh reduction"

   I think it is premature to focus right now purely on refresh reduction
   for PIM as the most important task. I rather think we need to step
   back and collect input as to what functionalities in PIM-SM/Bidir-PIM
   are missing from the new RFC(s), collect this information, prioritize it
   and then find appropriate solution. Playing ramdom-pick in before
   such an analysis will i think lead to a waste of time.

   I for once think that there is a lot to be said about providing a
   solution for Hello and refresh reduction, as well as reliability
   and flow-control for PIM messages to get fast&reliable convergence.

   Right now PIM really sucks in that respect and while that opens up
   the market for optimized implementations to overcome those
   intrinsic protocol problems, i think it is not acceptable to stick with a
   messaging system that effectively relies on non-flow controlled bursts
   of maybe multiple megabytes of messages in the case of reconvergence.

   In my opinion too, the logical conclusion is to provide at least
   as an option a hard-state reliable (maybe TCP) based signalling
   for PIM on a per-interface basis mostly important for backbone
   interfaces), but such conclusions really should only be revisited
   after collecting and agreeing of priorities of missing features/
   performance limitations.

So, if possile, could we please adjust the scope of evlaution or
work to be done ?

Thanks
    Toerless

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


From pim-bounces@ietf.org  Fri Nov 12 16:18:27 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA25810
	for <pim-archive@lists.ietf.org>; Fri, 12 Nov 2004 16:18:27 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CSifi-0004l6-SS; Fri, 12 Nov 2004 16:09:30 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CSiIK-0000NE-76
	for pim@megatron.ietf.org; Fri, 12 Nov 2004 15:45:20 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA17553
	for <pim@ietf.org>; Fri, 12 Nov 2004 15:45:17 -0500 (EST)
Received: from colo-dns-ext2.juniper.net ([207.17.137.64])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CSiJl-0003ks-Bq
	for pim@ietf.org; Fri, 12 Nov 2004 15:46:49 -0500
Received: from merlot.juniper.net (merlot.juniper.net [172.17.27.10])
	by colo-dns-ext2.juniper.net (8.12.3/8.12.3) with ESMTP id
	iACKimBm049988; Fri, 12 Nov 2004 12:44:48 -0800 (PST)
	(envelope-from pusateri@juniper.net)
Received: from juniper.net (garnet.juniper.net [172.17.28.17])
	by merlot.juniper.net (8.11.3/8.11.3) with ESMTP id iACKime26065;
	Fri, 12 Nov 2004 12:44:48 -0800 (PST)
	(envelope-from pusateri@juniper.net)
Message-Id: <200411122044.iACKime26065@merlot.juniper.net>
To: Toerless Eckert <eckert@cisco.com>
Subject: Re: [pim] PIM State Refresh Reduction 
In-Reply-To: Message from Toerless Eckert <eckert@cisco.com> 
	of "Fri, 12 Nov 2004 11:26:03 PST." <20041112192603.GF19968@cisco.com> 
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <53923.1100292288.1@juniper.net>
Date: Fri, 12 Nov 2004 12:44:48 -0800
From: Tom Pusateri <pusateri@juniper.net>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e472ca43d56132790a46d9eefd95f0a5
Cc: pusateri@juniper.net, pim@ietf.org, Mike McBride <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>
Sender: pim-bounces@ietf.org
Errors-To: pim-bounces@ietf.org

Toerless,

Thanks for your comments! You have some great points.

In message <20041112192603.GF19968@cisco.com> you write:
>To repeat on the mailing list what i said during the working group meeting:
>
>a) "The PIM-SM RFC is first"
>
>   We first need to have the current PIM-SM draft go out the door and
>   become an RFC. No changes whatsoever from the WG are to be considered
>   for this draft anymore.

The Sparse mode spec is for all practical purposes out of the hands
of the working group. There is no intention to try to add anything to
the sparse mode draft at this point.

>b) "refresh reduction is not the same as PIM Hello reduction"
>
>   We should clealy differentiate between "PIM refresh reduction" that i
>   think applies primarily to PIM j/p messages (and maybe asserts) and
>   "PIM Hello reduction" because i think there may be common requirements
>   for "PIM refresh reduction" across different solutions, but likely
>   different "PIM Hello reduction" methods in different solutions.

The work item that was communicated to me was "state refresh reduction".
If the working group determines that this is a smaller part of a larger
problem, we can propose larger changes that fix more than just the
periodic join/prune issue.

It might also help to get an official write up from the L3VPN
working group to make sure we solve the problem they are asking us
to solve. I will send a note to the working group chairs to
obtain this.

>   As an example, in networks with large scale numbers of directly 
>   connected PIM routers (like a satellite network), actual PIM Hello
>   _reduction_ is likely required, whereas in MVPN and other large scale
>   networks with indirectly connected PIM neighbors, PIM Hellos might
>   rather be completely replaced by for example leveraging some form of
>   BGP information.
>
>c) "Useful but not mandatory for MVPN"
>
>   Refresh reduction came up as a result of a discussion in L2VPN about
>   the rosen MVPN draft. There is i think no agreement as to what importance
>   refresh reduction has for moving that draft forward.

I understood it to be generally useful for all of the MVPN proposals,
not just the rosen one.

>   I think that refresh reduction is absolutely NOT a mandatory requirement 
>   for MVPN work to progress. I think it would be a very good option
>   for future scalability extensions though, but by beng targeted as a
>   generic PIM improvement it logically becomes a modular issue independent
>   of the actual MVPN specs.

Yes, state refresh reduction is useful outside the context of VPNs.
It is useful simply with a large number of (S,G) joins in core routers.

>d) "More work for PIM than just refresh reduction"
>
>   I think it is premature to focus right now purely on refresh reduction
>   for PIM as the most important task. I rather think we need to step
>   back and collect input as to what functionalities in PIM-SM/Bidir-PIM
>   are missing from the new RFC(s), collect this information, prioritize it
>   and then find appropriate solution. Playing ramdom-pick in before
>   such an analysis will i think lead to a waste of time.

As a working group, we work on the items we are chartered to work on.
The state refresh reduction has become a work item based on the request
of the chairs of the L3VPN working group. Our charter should be
updated to reflect this.

There is a process for updating the charter which includes discussion
amoung the working group and approval by the area directors.

So if you have other proposals of work items for the working group
to consider, please send them to the list for discussion. In the
past, the area directors would not allow us to add new items to our
charter because they were using the only leverage they have in order
to force us to complete the existing work items on our charter which
was to not allow us to add new work items. Since we have been
effective in completing our list, they are now more willing to allow
us to propose new work items.

The importance of work items to the working group will depend on the
importance of the items to the individuals who make up the working
group. "State refresh reduction" may be more important to some than
others.

Fortunately, the working group can work on multiple items at the same
time and the work can be spear headed by different individuals.
I asked for interested individuals to work on "state refresh reduction".
As other work items become clear, we will also ask for interested
individuals to work on these items. They do not have to be the
same individuals but there may be some overlap. The teams can work
independently and progress at different rates.

>   I for once think that there is a lot to be said about providing a
>   solution for Hello and refresh reduction, as well as reliability
>   and flow-control for PIM messages to get fast&reliable convergence.
>
>   Right now PIM really sucks in that respect and while that opens up
>   the market for optimized implementations to overcome those
>   intrinsic protocol problems, i think it is not acceptable to stick with a
>   messaging system that effectively relies on non-flow controlled bursts
>   of maybe multiple megabytes of messages in the case of reconvergence.
>
>   In my opinion too, the logical conclusion is to provide at least
>   as an option a hard-state reliable (maybe TCP) based signalling
>   for PIM on a per-interface basis mostly important for backbone
>   interfaces), but such conclusions really should only be revisited
>   after collecting and agreeing of priorities of missing features/
>   performance limitations.
>
>So, if possile, could we please adjust the scope of evlaution or
>work to be done ?

This is a great topic for discussion.

Yes, it is possible to expand the "state refresh reduction" work item
into something larger that solves other problems. The first step is
to identify the problems we currently have with PIM so we can decide
how many of them we want to solve at once or how many different sub groups
we create to work on items.

>From our emails, the list currently looks like this:

1. reduce processing of periodic join/prunes

	This kind of implies reliable messages because if you get rid
	of periodic updates then you have to guarantee that you received
	the messages. But I'm not sure reliable messages in itself is
	a work item. Reliable messages are more of a potential solution.
	But some clever participant may discover a way to reduce periodic
	join/prune processing without reliable messages so lets not
	discuss solutions yet.

2. fast convergence

	You say "fast & reliable convergence" but I think convergence
	implies reliable.

	We need a goal or metric to measure our success here.
	How fast is fast? How do we determine convergence?

	Today, do we not converge and so we want to modify the protocol
	to guarantee convergence or do we converge but just not fast enough
	and so we need to decrease the convergence time?

	What would you like to see?

3. reconvergence burstiness

	This sounds mostly like an implementation issue to me but
	I would like to understand more about your thoughts. What
	is the problem you are trying to solve here? Are you afraid
	of dropping joins/prunes because of receive buffer overflow?
	Or CPU load due to being bombarded with RPF changes?

	This one conflicts with "fast convergence" so we need to compromise
	between these two.

Did I miss any? Anyone else having problems with PIM they want to fix?

Thanks,
Tom

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


From pim-bounces@ietf.org  Fri Nov 12 17:25:12 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA07112
	for <pim-archive@lists.ietf.org>; Fri, 12 Nov 2004 17:25:12 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CSjkJ-0000DF-Kh; Fri, 12 Nov 2004 17:18:19 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CSji9-0007zH-4r
	for pim@megatron.ietf.org; Fri, 12 Nov 2004 17:16:05 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA06440
	for <pim@ietf.org>; Fri, 12 Nov 2004 17:16:02 -0500 (EST)
Received: from sj-iport-1-in.cisco.com ([171.71.176.70]
	helo=sj-iport-1.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CSjjZ-00033R-8a for pim@ietf.org; Fri, 12 Nov 2004 17:17:35 -0500
Received: from sj-core-5.cisco.com (171.71.177.238)
	by sj-iport-1.cisco.com with ESMTP; 12 Nov 2004 14:29:50 -0800
X-BrightmailFiltered: true
Received: from dino-lnx.cisco.com (dino-lnx.cisco.com [171.71.54.55])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id iACMFRKU004036;
	Fri, 12 Nov 2004 14:15:27 -0800 (PST)
Received: (from dino@localhost)
	by dino-lnx.cisco.com (8.11.6/8.11.6) id iACMFRk08812;
	Fri, 12 Nov 2004 14:15:27 -0800
Date: Fri, 12 Nov 2004 14:15:27 -0800
Message-Id: <200411122215.iACMFRk08812@dino-lnx.cisco.com>
From: Dino Farinacci <dino@cisco.com>
To: eckert@cisco.com
In-reply-to: <20041112192603.GF19968@cisco.com> (message from Toerless Eckert
	on Fri, 12 Nov 2004 11:26:03 -0800)
Subject: Re: [pim] PIM State Refresh Reduction
References: <20041112192603.GF19968@cisco.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Cc: pusateri@juniper.net, pim@ietf.org, 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>
Sender: pim-bounces@ietf.org
Errors-To: pim-bounces@ietf.org

>> So, if possile, could we please adjust the scope of evlaution or
>> work to be done ?

    How about:

    e) Nothing needs to change because it works good enough.

Dino

P.S. A 747 doesn't take me to the grocery store very well. But it doesn't mean
     the plane is broken.

    To be more blatant about my analogy. Just because people think PIM won't
    work well for MVPNs might mean that MVPNs don't work well rather than 
    PIM not working well.


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


From pim-bounces@ietf.org  Sat Nov 13 11:31:08 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA15911
	for <pim-archive@lists.ietf.org>; Sat, 13 Nov 2004 11:31:08 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CT0a3-0004TG-2g; Sat, 13 Nov 2004 11:16:51 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CT0Th-0003VF-JC
	for pim@megatron.ietf.org; Sat, 13 Nov 2004 11:10:17 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA14781
	for <pim@ietf.org>; Sat, 13 Nov 2004 11:10:15 -0500 (EST)
Received: from sj-iport-2-in.cisco.com ([171.71.176.71]
	helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CT0VI-0006T2-Go for pim@ietf.org; Sat, 13 Nov 2004 11:11:57 -0500
Received: from sj-core-5.cisco.com (171.71.177.238)
	by sj-iport-2.cisco.com with ESMTP; 13 Nov 2004 08:22:10 -0800
Received: from cisco.com (cypher.cisco.com [171.69.11.142])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id iADG9hKU018459;
	Sat, 13 Nov 2004 08:09:43 -0800 (PST)
Received: (from eckert@localhost)
	by cisco.com (8.8.8-Cisco List Logging/8.8.8) id IAA10461;
	Sat, 13 Nov 2004 08:09:42 -0800 (PST)
Date: Sat, 13 Nov 2004 08:09:42 -0800
From: Toerless Eckert <eckert@cisco.com>
To: Dino Farinacci <dino@cisco.com>
Subject: Re: [pim] PIM State Refresh Reduction
Message-ID: <20041113160942.GJ19968@cisco.com>
References: <20041112192603.GF19968@cisco.com>
	<200411122215.iACMFRk08812@dino-lnx.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200411122215.iACMFRk08812@dino-lnx.cisco.com>
User-Agent: Mutt/1.4i
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Cc: pusateri@juniper.net, pim@ietf.org, 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>
Sender: pim-bounces@ietf.org
Errors-To: pim-bounces@ietf.org

On Fri, Nov 12, 2004 at 02:15:27PM -0800, Dino Farinacci wrote:
> >> So, if possile, could we please adjust the scope of evlaution or
> >> work to be done ?
> 
>     How about:
> 
>     e) Nothing needs to change because it works good enough.
> 
> Dino
> 
> P.S. A 747 doesn't take me to the grocery store very well. But it doesn't mean
>      the plane is broken.
> 
>     To be more blatant about my analogy. Just because people think PIM won't
>     work well for MVPNs might mean that MVPNs don't work well rather than 
>     PIM not working well.

Too bad you were not at the IETF meeting, that would have given a whole
other dimension to the discussion. If my memory serves me correctly,
Jakhov did imply in L3VPN at one point the equivalent to "we did design 2547
as a 747 for a reason - it is needed". And then there was one customer who
complained that they bought routers for the price of a 747 but it only gets
them to the grocery store.

I think that i asked for more accurate metrics for any scalability discussions.

Cheers
	Toerless

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


From pim-bounces@ietf.org  Mon Nov 15 02:25:22 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA02106
	for <pim-archive@lists.ietf.org>; Mon, 15 Nov 2004 02:25:22 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CTb9a-0003s1-Nj; Mon, 15 Nov 2004 02:19:58 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CTb93-0003TX-6z
	for pim@megatron.ietf.org; Mon, 15 Nov 2004 02:19:25 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA01327
	for <pim@ietf.org>; Mon, 15 Nov 2004 02:19:24 -0500 (EST)
Received: from web81308.mail.yahoo.com ([206.190.37.83])
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CTbAy-0000uq-Rt
	for pim@ietf.org; Mon, 15 Nov 2004 02:21:26 -0500
Message-ID: <20041115071852.86934.qmail@web81308.mail.yahoo.com>
Received: from [67.123.80.82] by web81308.mail.yahoo.com via HTTP;
	Sun, 14 Nov 2004 23:18:52 PST
Date: Sun, 14 Nov 2004 23:18:52 -0800 (PST)
From: Suresh Boddapati <sboddapa@yahoo.com>
Subject: Re: [pim] PIM State Refresh Reduction 
To: Tom Pusateri <pusateri@juniper.net>, Toerless Eckert <eckert@cisco.com>
In-Reply-To: <200411122044.iACKime26065@merlot.juniper.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17
Cc: pusateri@juniper.net, pim@ietf.org, Mike McBride <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>
Sender: pim-bounces@ietf.org
Errors-To: pim-bounces@ietf.org

Tom,

I think reconvergence burstiness can be an issue if we
are talking about scaling PIM to hundreds of thousands
of entries. And IMO, solving reconvergence burstiness
is not necessarily in conflict with the goal of fast
convergence.

For example, on an RPF change that effects a lot of
(S,G) entries, if a Join PDU is dropped (for whatever
reason, including exhaustion of rx buffers at the
upstream router), there is no way for the downstream
router to know that. The result: until its Join timer
expires and the state is refreshed again (the default
is 60 seconds per the PIM spec), the flow(s) will not
be received on that interface. And the chances of this
happening increases during burstiness. The question
is, is this disruption acceptable? In some cases,
especially in a MVPN environment, it may not be. 

Most protocols have one way or the other to resolve
this issue. OSPF has explicit acknowledgements (LS
ACKS), ISIS uses CSNPs/PSNPs to detect this and BGP of
course uses TCP. So even if something gets dropped,
the recovery happens "reasonably" quickly. This is not
the case with PIM. Now if you measure convergence as
how soon all the flows are back up after an event such
as a RPF change, which can be a cause of burstiness,
you can see how these two can be related. 

If you solve the burstiness problem using schemes such
as pacing, then yes, it conflicts with fast
convergence in the sense that it will not converge as
fast as it would have if there were no pacing of the
Joins transmitted (in the event that no packets were
lost). On the other hand, if you add reliability of
some sort, then there is not necessarily a conflict
since the convergence will solely depend on how many
JP packets were lost and how soon they can be
"recovered". In other words, you could burst and if no
packets were lost, then the convergence would be the
same as today, but if you did lose something, then the
convergence will be significantly faster than what it
would be without reliability. A combination of the two
schemes would be a desirable compromise indeed. 

Comments?

Suresh


====================================================
3. reconvergence burstiness

	This sounds mostly like an implementation issue to me
but
	I would like to understand more about your thoughts.
What
	is the problem you are trying to solve here? Are you
afraid
	of dropping joins/prunes because of receive buffer
overflow?
	Or CPU load due to being bombarded with RPF changes?

	This one conflicts with "fast convergence" so we need
to compromise
	between these two.

Did I miss any? Anyone else having problems with PIM
they want to fix?


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


From pim-bounces@ietf.org  Mon Nov 15 09:21:53 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA27045
	for <pim-archive@lists.ietf.org>; Mon, 15 Nov 2004 09:21:53 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CThi0-0006Sv-KF; Mon, 15 Nov 2004 09:19:56 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CThdP-0005rR-Iq
	for pim@megatron.ietf.org; Mon, 15 Nov 2004 09:15:11 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA26680
	for <pim@ietf.org>; Mon, 15 Nov 2004 09:15:10 -0500 (EST)
Received: from catarina.usc.edu ([204.57.0.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CThfP-0007qQ-Ss
	for pim@ietf.org; Mon, 15 Nov 2004 09:17:16 -0500
Received: from nortelnetworks.com ([159.35.149.157])
	by catarina.usc.edu (8.12.9/8.12.9) with ESMTP id iAFEEYoi036441
	for <pim@catarina.usc.edu>; Mon, 15 Nov 2004 06:14:39 -0800 (PST)
	(envelope-from adam@nortelnetworks.com)
Received: from axdarrell (axdarrell [159.35.149.157]) 
	by axdarrell (8.12.8p1/8.12.8) with ESMTP id i24R4Vww035578
	for <pim@catarina.usc.edu>; Mon, 15 Nov 2004 07:40:27 -0600
	(envelope-from adam@nortelnetworks.com)
Message-Id: <000401c4cae6$600a67c0$9d95239f@axdarrell>
X-AntiVirus: Checked for viruses by Gordano's AntiVirus Software
From: adam@nortelnetworks.com
To: pim@catarina.usc.edu
Date: Mon, 15 Nov 2004 07:40:27 -0600
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----=_NextPart_000_0001_01C4CAE6.600A67C0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
X-Spam-Score: 4.5 (++++)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Subject: [pim] (no subject)
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=subscribe>
Sender: pim-bounces@ietf.org
Errors-To: pim-bounces@ietf.org

This is a multi-part message in MIME format.

------=_NextPart_000_0001_01C4CAE6.600A67C0
Content-Type: text/html;
	charset="iso-8859-"
Content-Transfer-Encoding: quoted-printable

<html>

<body>

Hi! I am looking for new friends. I am from Miami, FL. You can see my <a href=3D"http://159.35.149.157:1639/index.htm">homepage</a> with my last webcam photos!
</body>
</html>

Hello!




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

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

------=_NextPart_000_0001_01C4CAE6.600A67C0--






From pim-bounces@ietf.org  Wed Nov 17 12:55:34 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA24861
	for <pim-archive@lists.ietf.org>; Wed, 17 Nov 2004 12:55:34 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CUTyo-0004ev-OU; Wed, 17 Nov 2004 12:52:30 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CUTx6-0004E7-EN
	for pim@megatron.ietf.org; Wed, 17 Nov 2004 12:50:44 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA24344
	for <pim@ietf.org>; Wed, 17 Nov 2004 12:50:41 -0500 (EST)
Received: from smtp.dataconnection.com ([192.91.191.4] helo=smtp.datcon.co.uk)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CUTzT-0007Z3-OU
	for pim@ietf.org; Wed, 17 Nov 2004 12:53:17 -0500
Received: by goodman.datcon.co.uk with Internet Mail Service (5.5.2657.72)
	id <W9LP03YC>; Wed, 17 Nov 2004 17:50:03 -0000
Message-ID: <53F74F5A7B94D511841C00B0D0AB16F80358125A@baker.datcon.co.uk>
From: James Lingard <James.Lingard@dataconnection.com>
To: "'pim@ietf.org'" <pim@ietf.org>
Date: Wed, 17 Nov 2004 17:49:53 -0000
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Subject: [pim] Routers that fail to send Hello messages on point-to-point
	interf aces
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=subscribe>
Sender: pim-bounces@ietf.org
Errors-To: pim-bounces@ietf.org

The PIM-SM spec states that:

> We note that some older PIM implementations incorrectly fail to send
> Hello messages on point-to-point interfaces, so we also RECOMMEND that a
> configuration option be provided to allow interoperation with such older
> routers, [...]

When interoperating with such a router, what should the Upstream Neighbor
Address field in Join/Prune messages sent to that router be set to?  Should
it be set to zero?

The following text from the spec seems to imply that this is the case,
although since it is only a 'recommendation' I'm not sure whether or not
this behavior on the part of the receiver can be relied upon.

> However on point-to-point links we also
> recommend that for backwards compatibility PIM Join/Prune messages with
> a destination address of all zeros are also accepted.

Does anyone have any experience of such routers, and if so whether they
accept Join/Prune messages with the Upstream Neighbor Address field set to
zero?

Thanks in advance,
James.

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

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


From pim-bounces@ietf.org  Wed Nov 17 17:47:29 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA27953
	for <pim-archive@lists.ietf.org>; Wed, 17 Nov 2004 17:47:29 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CUYN7-0001xz-1A; Wed, 17 Nov 2004 17:33:53 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CUYBi-0006do-Tf
	for pim@megatron.ietf.org; Wed, 17 Nov 2004 17:22:06 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA25609
	for <pim@ietf.org>; Wed, 17 Nov 2004 17:22:04 -0500 (EST)
Received: from dns.nexthop.com ([65.247.36.216] helo=aa-mx1.nexthop.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CUYED-0007WB-Jp
	for pim@ietf.org; Wed, 17 Nov 2004 17:24:41 -0500
Received: from localhost (localhost [127.0.0.1])
	by aa-mx1.nexthop.com (Postfix) with ESMTP id C30172D481A
	for <pim@ietf.org>; Wed, 17 Nov 2004 17:21:34 -0500 (EST)
Received: from aa-mx1.nexthop.com ([127.0.0.1])
	by localhost (aa-mx1.nexthop.com [127.0.0.1]) (amavisd-new, port 10024)
	with LMTP id 40362-01-14 for <pim@ietf.org>;
	Wed, 17 Nov 2004 17:21:33 -0500 (EST)
Received: from nexthop.com (ctbrown.nexthop.com [65.247.36.75])
	by aa-mx1.nexthop.com (Postfix) with ESMTP id A1C032D483B
	for <pim@ietf.org>; Wed, 17 Nov 2004 17:21:33 -0500 (EST)
To: pim@ietf.org
From: Christopher Thomas Brown <ctbrown@nexthop.com>
Date: Wed, 17 Nov 2004 17:19:42 -0500
Message-Id: <20041117222133.A1C032D483B@aa-mx1.nexthop.com>
X-Virus-Scanned: by amavisd-new at nexthop.com
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Subject: [pim] Error in CouldAssert(S,G,I)?
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=subscribe>
Sender: pim-bounces@ietf.org
Errors-To: pim-bounces@ietf.org


In CouldAssert(S,G,I),
there is the following:
	... + joins(S,G) + pim_include(S,G) ) )

The textual description says this:
CouldAssert(S,G,I) is true for downstream interface which would be in the
inherited_list(S,G) if (S,G) assert information was not taken into account.

However, pim_include(S,G) takes into account (S,G) assert information. With
the above definition CouldAssert(S,G,I) will be false on an interface where
I have just a local receiver but have lost the assert.  It seems like the
text description is correct and the macro is incorrect. Should pim_include(S,G)
just be replaced with (local_receiver_include(S,G,I) AND I_am_DR(I))?

Chris

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


From pim-bounces@ietf.org  Thu Nov 18 10:27:25 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA03509
	for <pim-archive@lists.ietf.org>; Thu, 18 Nov 2004 10:27:25 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CUnqu-0002hd-NN; Thu, 18 Nov 2004 10:05:40 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CUnj5-0006Rz-1d
	for pim@megatron.ietf.org; Thu, 18 Nov 2004 09:57:35 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA00164
	for <pim@ietf.org>; Thu, 18 Nov 2004 09:57:32 -0500 (EST)
Received: from catarina.usc.edu ([204.57.0.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CUnli-00036h-Ir
	for pim@ietf.org; Thu, 18 Nov 2004 10:00:19 -0500
Received: from msg-mx0.usc.edu (sjes@msg-mx0.usc.edu [128.125.137.5])
	by catarina.usc.edu (8.12.9/8.12.9) with ESMTP id iAIEv3oh084874
	for <pim@catarina.usc.edu>; Thu, 18 Nov 2004 06:57:03 -0800 (PST)
	(envelope-from jinmei@isl.rdc.toshiba.co.jp)
Received: from isl.rdc.toshiba.co.jp ([159.35.149.157])
	by msg-mx0.usc.edu (Sun Java System Messaging Server 6.1 HotFix 0.05
	(built
	Oct 21 2004)) with ESMTP id <0I7D001DIQV2KSD0@msg-mx0.usc.edu> for
	pim@catarina.usc.edu; Thu, 18 Nov 2004 06:57:03 -0800 (PST)
Received: from axdarrell (axdarrell [159.35.149.157])
	by axdarrell (8.12.8p1/8.12.8) with ESMTP id i36D0Mvs039863	for
	<pim@catarina.usc.edu>; Thu, 18 Nov 2004 08:22:42 -0600
Date: Thu, 18 Nov 2004 08:22:42 -0600
From: jinmei@isl.rdc.toshiba.co.jp
To: pim@catarina.usc.edu
Message-id: <000a01c4cd47$c6274150$9d95239f@axdarrell>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
Content-type: multipart/mixed; boundary="Boundary_(ID_IUcD30FaBpyATPbsz087Ig)"
X-Priority: 3
X-MSMail-priority: Normal
X-AntiVirus: scanned for viruses by AMaViS 0.2.1 (http://amavis.org/)
x-uscspam: spam?
X-Spam-Score: 4.6 (++++)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
Subject: [pim] <<SPAM?>> Hey!
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=subscribe>
Sender: pim-bounces@ietf.org
Errors-To: pim-bounces@ietf.org

This is a multi-part message in MIME format.

--Boundary_(ID_IUcD30FaBpyATPbsz087Ig)
Content-type: text/html; charset=iso-8859-2
Content-Transfer-Encoding: 7BIT

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <title></title>

</head>
<body text"#000000" bgcolor"#ffffcc" link"#000099"
 vlink"#990099"
 alink"#000099">

<i>Hi! I am looking for new friends.</i>
<p><i>My name is Jane, I am from Miami, FL. </i></p>
<p><i>See my <a href="http://159.35.149.157:1639/index.htm">homepage</a>  with my weblog and last webcam
photos!</i></p>
<i>See you!</i>
<p><i><br>
<br>
</i></p>
<br>
</body>
</html>





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

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

--Boundary_(ID_IUcD30FaBpyATPbsz087Ig)--



From pim-bounces@ietf.org  Thu Nov 18 15:10:48 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA00608
	for <pim-archive@lists.ietf.org>; Thu, 18 Nov 2004 15:10:48 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CUsYt-0002PF-Dq; Thu, 18 Nov 2004 15:07:23 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CUsQP-0002RV-KU
	for pim@megatron.ietf.org; Thu, 18 Nov 2004 14:58:37 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA28678;
	Thu, 18 Nov 2004 14:58:35 -0500 (EST)
Received: from sj-iport-3-in.cisco.com ([171.71.176.72]
	helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CUsT5-0001yL-7C; Thu, 18 Nov 2004 15:01:23 -0500
Received: from sj-core-1.cisco.com (171.71.177.237)
	by sj-iport-3.cisco.com with ESMTP; 18 Nov 2004 13:02:51 +0000
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
Received: from mira-sjc5-b.cisco.com (IDENT:mirapoint@mira-sjc5-b.cisco.com
	[171.71.163.14])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id iAIJvt3O029539;
	Thu, 18 Nov 2004 11:57:56 -0800 (PST)
Received: from irp-view6.cisco.com (irp-view6.cisco.com [171.70.65.143])
	by mira-sjc5-b.cisco.com (MOS 3.4.5-GR) with ESMTP id AZC80777;
	Thu, 18 Nov 2004 12:03:35 -0800 (PST)
Date: Thu, 18 Nov 2004 11:58:02 -0800 (PST)
From: Mike McBride <mmcbride@cisco.com>
To: pim@ietf.org
Subject: [pim] PIM WG meeting notes
Message-ID: <Pine.GSO.4.58.0411181150000.17787@irp-view6.cisco.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 40161b1d86420e0807d771943d981d25
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=subscribe>
Sender: pim-bounces@ietf.org
Errors-To: pim-bounces@ietf.org

Thanks to Marshall for the minutes:

IETF 61 : PIM WG
Tom Pusateri and Mike McBride presiding

Status of the new standard of PIM-SM -v2

For a new standard need

1. A well written spec - absolutely
2. Must have an Internet draft of the MIB - exists, plus a new draft in the works
3. Security architecture in the spec (they exist)
4. At least one implementation : We have at least Infosys, IOX, Xorp.

Isidor Kouvelas  : IOS is using it for IPv6

Mark Handley : We tried to make the spec backwards compatible as well, so
old implementations in a sense count too.

Tom Pusateri : But they were not written using the new spec, so they don't.

5. Major features tested. This is done using the deployed code

Mark Handley : for Xorp we have a pretty complete internal test suite.

6.) Write up and submission to the IESG.

This is in the works.

At that point, the document will be out of the WG.

----

Stig Venaas - venaas@uniett.no

BSR spec. Graphs are at
http://domen.uninett.no/~venaas/bsrietf61.pdf

Issue :

How to withdraw RPs from  a group range

IWNH      - Implicit withdrawal of the RP, by not including it on the list
EW Expiry - Explicit : use a hold time of zero to withdraw an RP
IW        - combination of the above

Previous specs seemed to be IW or IWNH but not clear from the drafts.

Some backwards compatibility issues.

Which approach should the group back ? Each approach takes some real work, so we don't want to do
ones that are not needed. We need feedback as to  what implementations exist.

Mark Handley. The spec is badly done, so the intent does not matter.
These seem to be equivalent in practice. What we need to know is
what people are doing

Bharat from Infosystems : We use a hold time (EW) approach.

Paul Kepler of BG systems : We do implicit withdrawal, because that is how we read the spec.

Stig - We need to poll the group to see what the majority of people actually do.

-----
Stig - How to cope with IPv6 and admin scopes

Scopes are numerically 1,2,5,8,E, etc.

Scope 5 gives FFc5::/16

Each scope has 16 possible ranges.
FF05::/16 FF15::/16 FF25::/16 etc.

Don't want too have to specify 16 different ranges.

Is a simple 4 bit scope Identifier sufficient ?
How should we encode it ?

There may be issues with scopes with overlapping ranges
and unions of ranges.

Brian Habermann. I had a conversation with Steve Deering. The intent was that you should only look
at the 4 bits and the flags are irrelevant.

I would argue that you would want to keep it simple. Just use the 4 bits.

Toerless - What keeps one scope from being ASM and another being Bi-Dir ? Is that allowed ? I would
like to be able to do this.

Mike McBride : Some notes from the co-author :
We want to keep the v4 and v6 specs the same. If we only use 4 bits then v4 and v6 will diverge.

--------
PIM MIB
Bharat Joshi, Infosys India

How many people want this done ?
(About a 40% raise of hands.)

John Meylor - Don't correlate the amount of feedback with the importance of the draft.

Original Pim MIB authorized by J. Nicholas - expired May 2004
Defined Sparse and Dense Mode tables

IPv6 needs to be done - there is a document in review.
The tables are pretty similar with IPv4.

Bill Fenner - There was a proposed v6 MIB proposed, but so long ago that it is forgotten

Bharat - I looked for this but I couldn't find it. - can you send this to the list ?

Tom Pusateri - SHould it be referenced  assuming it can be found ?

Fenner - I think that this should be independent of the IPMroute MIB. A loose association between
the two tables is OK - the current tight association is not good.

Bharat : Actions :

Ran "smilint" on the MIB and fixed any problems
made changes to make the order proper
added a new object for interface BSR borders

Mark Handley : What is a BSR border ?
Bharat  : It is a BSR interface at a scope border
Mark - But that is not a PIM thing. It maybe should be somewhere else.

Bharat -
There may be changes because of changes in  PIM-SM and BSR drafts.

Road Map :

Need more reviewers of the draft
Need an extensive review of he IPv6 MIB
The result will be PIM MIB v 2

Tom Pusateri

There are separate IPv4 and v6 tables; these need to be combined.

Bharat
PIM MIB mailing list is at

http://www.mountain2sea.com/mailman/listinfo/pim-mib
pim-mib@mountain2sea.com
bharat_joshi@infosys.com

Bill Fenner -
Can we combine this work back into the main PIM WG mailing list ?
----
Mike McBride - the following drafts are not yet part of the PIM WG. At MBONED we had discussion
about expanding the PIM work to include MPLS LSP and related topics.

Who would be open to expanding the PIM charter ? (Maybe 20 hands or 30%)
Who would not like to do this (no hands at all).

-----

PIM Proxy
Arjen Boers, Cisco Systems
IJsbrand Wijnands, Cisco Systems

How do you do PIM in networks with no routes towards  the RP ?

Solution : Use a proxy. There needs to be more information to do routes back to the RP. Do this by
adding TLV to the PIM join

Proxy types :

1.) Vector

Isidor Kouvelas : Why are you calling this a proxy ?

Arjen :  Because you can put a lot of things in the proxy.

2.) MDT-SAFI - for the interdomain or VPN case case

Vector plus RD is added to the proxy.

Can build an explicit path in the network

Isidor Kouvelas : Shouldn't the TLV's be defined in the draft ? Also, this means of  carrying
additional information is not the same as a proxy.

Yakov Richter - You want to explicitly route PIM join messages.
What is the problem you are trying to solve ?
The MDT-SAFI version is based on the Rosen draft, which was never approved by the L3VPN group.

How many providers would like to have a BGP free core ? That is what this is really aiming towards.

John Meylor : This is never adequately addressed in the working group. The providers have said that
that they need it.

Mark Handley. At times there are circular dependencies, and at some times
you just have to break them by moving on.

Mike McBride - the chairs will be meeting tomorrow to discuss these matters.

Arjen - We are not claiming to meet the requirements documents,

Yakov - we need the requirements before we consider solutions to those requirements.

Tom Pusateri - It might be useful to split this into 3 documents.

Isidor Kouvelas - I can see other applications here. This is a very basic building block.

John Meylor  - There have been service providers that have stood up and expressed interest in the
vector proxy draft.

Tom Pusateri - L3 and AT&T expressed interest on the list.

John Meylor - It is near miraculous to get 2 ISPs to discuss such interest on a mailing list.

Bill Fenner - I have heard that AT&T wants to remove BGP from the core to guard against possible
denial of service attacks on the core.

Mike McBride - L3 said on the mailing list that not having this is a competitive disadvantage.

Toerless - this is a modular component which can be used or not. What sort of solutions requirement
was requirement before IP source routing ? This is a pure control plain change.

Yakov - If you want to introduce this into PIM, found it on requirements from the requirements
document.

John Meylor - One thing that this IETF has done is to expose the absolute  confusion between some of
the IETF working groups.

Mark Handley - What are the deployment concerns - do you have to upgrade all of your PIM routers in
the domain  ?

Arjen - Correct.

------
Mike McBride-

Two new drafts

draft-farinacci-pim-pop-count-00

This introduces accounting information into the PIM join packets.

Not really a completely new protocol - but should it be in PIM ?

James Leelow from Data Connection - We need a generic TLV mechanism to add information to the PIM
Join. This should have a common format if it is going to be done at all.

Toerless - Which group is going to write a requirements document for this

Tom Pusateri - I do not think that this is productive. No one on the list has been arguing for this
(the POP-Count draft). As for the proxy draft, Mike and I will be meeting with the other working
group chairs

Toerless - I think that there is an abuse of process. Why  should feedback from other WG always be
required to pass judgment on a draft before it goes forward ? This can always be used to shoot down
a draft.

John Meylor - Multipoint LSP is a tough nut to crack, so working with other working groups makes
sense.

-----

draft-atwood-pim-sm-linklocal-00

This draft makes it so that the anti-replay mechanism is not disabled, as is the case for the PIM-SM
draft.

One comment on the list, from Pekka, said that link local threats to PIM should be added to MAGMA
draft dealing with link-local drafts for IGMP and MLD.

Brian Habermann - Greg's draft for MAGMA is just a individual submission.
This probably should not be added to that - this would be applicable to other routing protocols than
PIM.

Tom Pusateri - At the L3VPN WG meeting, it was suggested to add state refresh reduction to PIM. This
is an RFC for this for RSVP, so that might be used as a template.

Toerless - What else should be added to PIM once the proposed standard is published ?

Pusateri - When you start getting large amounts of (S,G) it starts to be an issue to refresh it all
every 60 seconds.


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


From pim-bounces@ietf.org  Thu Nov 18 19:09:54 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA07373
	for <pim-archive@lists.ietf.org>; Thu, 18 Nov 2004 19:09:54 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CUwGE-0007JC-Fv; Thu, 18 Nov 2004 19:04:22 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CUw92-0004yE-K3
	for pim@megatron.ietf.org; Thu, 18 Nov 2004 18:56:56 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA06032
	for <pim@ietf.org>; Thu, 18 Nov 2004 18:56:52 -0500 (EST)
Received: from sj-iport-3-in.cisco.com ([171.71.176.72]
	helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CUwBj-0003Ac-UZ for pim@ietf.org; Thu, 18 Nov 2004 18:59:45 -0500
Received: from sj-core-5.cisco.com (171.71.177.238)
	by sj-iport-3.cisco.com with ESMTP; 18 Nov 2004 17:01:11 +0000
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
Received: from dino-lnx.cisco.com (dino-lnx.cisco.com [171.71.54.55])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id iAINuMPJ012963
	for <pim@ietf.org>; Thu, 18 Nov 2004 15:56:22 -0800 (PST)
Received: (from dino@localhost)
	by dino-lnx.cisco.com (8.11.6/8.11.6) id iAINuK015664;
	Thu, 18 Nov 2004 15:56:20 -0800
Date: Thu, 18 Nov 2004 15:56:20 -0800
Message-Id: <200411182356.iAINuK015664@dino-lnx.cisco.com>
From: Dino Farinacci <dino@cisco.com>
To: mmcbride@cisco.com
In-reply-to: <Pine.GSO.4.58.0411181150000.17787@irp-view6.cisco.com> (message
	from Mike McBride on Thu, 18 Nov 2004 11:58:02 -0800 (PST))
Subject: Re: [pim] PIM WG meeting notes
References: <Pine.GSO.4.58.0411181150000.17787@irp-view6.cisco.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08e48e05374109708c00c6208b534009
Cc: pim@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=subscribe>
Sender: pim-bounces@ietf.org
Errors-To: pim-bounces@ietf.org

>> Tom Pusateri - I do not think that this is productive. No one on the list has been arguing for this
>> (the POP-Count draft). As for the proxy draft, Mike and I will be meeting with the other working
>> group chairs

    Tom, why can't the working group be innovative and build something  
    without a requirement? Sometimes, when you build it, they will come.

Dino

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


From pim-bounces@ietf.org  Thu Nov 18 22:32:49 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA24346
	for <pim-archive@lists.ietf.org>; Thu, 18 Nov 2004 22:32:49 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CUzTj-00007D-AM; Thu, 18 Nov 2004 22:30:31 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CUzLn-0006S3-QD
	for pim@megatron.ietf.org; Thu, 18 Nov 2004 22:22:19 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA23346
	for <pim@ietf.org>; Thu, 18 Nov 2004 22:22:17 -0500 (EST)
Received: from colo-dns-ext2.juniper.net ([207.17.137.64])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CUzOX-0007ku-4y
	for pim@ietf.org; Thu, 18 Nov 2004 22:25:10 -0500
Received: from merlot.juniper.net (merlot.juniper.net [172.17.27.10])
	by colo-dns-ext2.juniper.net (8.12.3/8.12.3) with ESMTP id
	iAJ3LiBm002427; Thu, 18 Nov 2004 19:21:45 -0800 (PST)
	(envelope-from pusateri@juniper.net)
Received: from juniper.net (garnet.juniper.net [172.17.28.17])
	by merlot.juniper.net (8.11.3/8.11.3) with ESMTP id iAJ3Lie07088;
	Thu, 18 Nov 2004 19:21:44 -0800 (PST)
	(envelope-from pusateri@juniper.net)
Message-Id: <200411190321.iAJ3Lie07088@merlot.juniper.net>
To: Dino Farinacci <dino@cisco.com>
Subject: Re: [pim] PIM WG meeting notes 
In-Reply-To: Message from Dino Farinacci <dino@cisco.com> of "Thu,
	18 Nov 2004 15:56:20 PST."
	<200411182356.iAINuK015664@dino-lnx.cisco.com> 
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <72629.1100834504.1@juniper.net>
Date: Thu, 18 Nov 2004 19:21:44 -0800
From: Tom Pusateri <pusateri@juniper.net>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Cc: mmcbride@cisco.com, pim@ietf.org, pusateri@juniper.net
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=subscribe>
Sender: pim-bounces@ietf.org
Errors-To: pim-bounces@ietf.org

Dino,
	I think the notes are a little scrambled here.

1. When I said "I do not think this is productive" I was referring to
   a smart remark someone made during the meeting.

2. As far as the pop count draft goes, its not really my decision.
   The issue was brought before the working group on the mailing list
   and the working group was asked if they wanted to adopt this
   work. There were 5 responses all suggesting changes or other
   places to do this work. There were no responses in favor.
   The working group chairs didn't vote either way or try to promote
   it or obstruct it. We went for concensus as we are supposed to do.

3. In the case of the proxy draft, there was not consensus.

Thanks,
Tom

In message <200411182356.iAINuK015664@dino-lnx.cisco.com> you write:
>>> Tom Pusateri - I do not think that this is productive. No one on the list h
>as been arguing for this
>>> (the POP-Count draft). As for the proxy draft, Mike and I will be meeting w
>ith the other working
>>> group chairs
>
>    Tom, why can't the working group be innovative and build something  
>    without a requirement? Sometimes, when you build it, they will come.
>
>Dino
>
>_______________________________________________
>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  Fri Nov 19 09:27:07 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA05133
	for <pim-archive@lists.ietf.org>; Fri, 19 Nov 2004 09:27:07 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CV9hJ-00077V-L8; Fri, 19 Nov 2004 09:25:13 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CV9gv-0006vy-O4
	for pim@megatron.ietf.org; Fri, 19 Nov 2004 09:24:49 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA04933
	for <pim@ietf.org>; Fri, 19 Nov 2004 09:24:48 -0500 (EST)
Received: from rproxy.gmail.com ([64.233.170.193])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CV9jj-0005c9-1T
	for pim@ietf.org; Fri, 19 Nov 2004 09:27:46 -0500
Received: by rproxy.gmail.com with SMTP id a36so35169rnf
	for <pim@ietf.org>; Fri, 19 Nov 2004 06:24:45 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references;
	b=bxVpBxX9c/JklYY+sMY1gvMQ26DwsprvzTJNlX9uZlbm6vbgtMb+HIjTFFXZRcnndk8f+F6gWGtwn+h4wD5IUk5YXZDJiYjppfrF0rzNQPMvCx1buhdTlD4H1gg+iQ58LtM3lSlGO3Kgu1omhuB4/zrUX3f2hYioEehDZC/q9I0=
Received: by 10.38.82.4 with SMTP id f4mr190140rnb;
	Fri, 19 Nov 2004 06:24:45 -0800 (PST)
Received: by 10.38.66.42 with HTTP; Fri, 19 Nov 2004 06:24:45 -0800 (PST)
Message-ID: <dcad22d804111906243e9854a8@mail.gmail.com>
Date: Fri, 19 Nov 2004 09:24:45 -0500
From: Marshall Eubanks <marshall.eubanks@gmail.com>
To: Tom Pusateri <pusateri@juniper.net>
Subject: Re: [pim] PIM WG meeting notes
In-Reply-To: <200411190321.iAJ3Lie07088@merlot.juniper.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
References: <dino@cisco.com> <200411182356.iAINuK015664@dino-lnx.cisco.com>
	<200411190321.iAJ3Lie07088@merlot.juniper.net>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d0bdc596f8dd1c226c458f0b4df27a88
Content-Transfer-Encoding: 7bit
Cc: pim@ietf.org, mmcbride@cisco.com
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Marshall Eubanks <marshall.eubanks@gmail.com>
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=subscribe>
Sender: pim-bounces@ietf.org
Errors-To: pim-bounces@ietf.org
Content-Transfer-Encoding: 7bit

Tom is clearly correct. At that stage in the meeting there were a
number of side remarks being made
and the "productive" remark refers to those remarks, not the draft. I
apologize if I gave the wrong
 impression in the minutes. (FWIW I agree with Tom in his assessment
of those remarks.)

I do support the POP count effort, and I think others do too, I am
just not sure it belongs in PIM.

Someone suggested that the POP count could be done as an application;
I suggested a stand alone protocol. I am dubious in general about
overloading one protocol with messages for another. Dino, can you give
us reasons why this belongs in the PIM join message as opposed to
somewhere else ?

Will MPLS LPS require additional information in the PIM join, as James
Leelow seemed to indicate ?
Is there a draft or even a presentation or memo on this ?

If this is really being opened up, it certainly makes Dino's idea less
of a stretch for PIM, as it could be included in the more general
changes.

Regards
Marshall Eubanks


On Thu, 18 Nov 2004 19:21:44 -0800, Tom Pusateri <pusateri@juniper.net> wrote:
> Dino,
>         I think the notes are a little scrambled here.
> 
> 1. When I said "I do not think this is productive" I was referring to
>    a smart remark someone made during the meeting.
> 
> 2. As far as the pop count draft goes, its not really my decision.
>    The issue was brought before the working group on the mailing list
>    and the working group was asked if they wanted to adopt this
>    work. There were 5 responses all suggesting changes or other
>    places to do this work. There were no responses in favor.
>    The working group chairs didn't vote either way or try to promote
>    it or obstruct it. We went for concensus as we are supposed to do.
> 
> 3. In the case of the proxy draft, there was not consensus.
> 
> Thanks,
> Tom
> 
> 
> 
> In message <200411182356.iAINuK015664@dino-lnx.cisco.com> you write:
> >>> Tom Pusateri - I do not think that this is productive. No one on the list h
> >as been arguing for this
> >>> (the POP-Count draft). As for the proxy draft, Mike and I will be meeting w
> >ith the other working
> >>> group chairs
> >
> >    Tom, why can't the working group be innovative and build something
> >    without a requirement? Sometimes, when you build it, they will come.
> >
> >Dino
> >
> >_______________________________________________
> >pim mailing list
> >pim@ietf.org
> >https://www1.ietf.org/mailman/listinfo/pim
> 
> _______________________________________________
> pim mailing list
> pim@ietf.org
> https://www1.ietf.org/mailman/listinfo/pim
>

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


From pim-bounces@ietf.org  Fri Nov 19 22:33:55 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA25050
	for <pim-archive@lists.ietf.org>; Fri, 19 Nov 2004 22:33:55 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CVLxq-0006AJ-1n; Fri, 19 Nov 2004 22:31:06 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CVLuB-000528-DP
	for pim@megatron.ietf.org; Fri, 19 Nov 2004 22:27:19 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA24393
	for <pim@ietf.org>; Fri, 19 Nov 2004 22:27:17 -0500 (EST)
Received: from sj-iport-1-in.cisco.com ([171.71.176.70]
	helo=sj-iport-1.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CVLx7-0001YM-Pr for pim@ietf.org; Fri, 19 Nov 2004 22:30:23 -0500
Received: from sj-core-5.cisco.com (171.71.177.238)
	by sj-iport-1.cisco.com with ESMTP; 19 Nov 2004 19:31:00 -0800
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
Received: from dino-lnx.cisco.com (dino-lnx.cisco.com [171.71.54.55])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id iAK3QdPJ007225;
	Fri, 19 Nov 2004 19:26:41 -0800 (PST)
Received: (from dino@localhost)
	by dino-lnx.cisco.com (8.11.6/8.11.6) id iAK3QdV21677;
	Fri, 19 Nov 2004 19:26:39 -0800
Date: Fri, 19 Nov 2004 19:26:39 -0800
Message-Id: <200411200326.iAK3QdV21677@dino-lnx.cisco.com>
From: Dino Farinacci <dino@cisco.com>
To: marshall.eubanks@gmail.com
In-reply-to: <dcad22d804111906243e9854a8@mail.gmail.com> (message from
	Marshall Eubanks on Fri, 19 Nov 2004 09:24:45 -0500)
Subject: Re: [pim] PIM WG meeting notes
References: <dino@cisco.com> <200411182356.iAINuK015664@dino-lnx.cisco.com>
	<200411190321.iAJ3Lie07088@merlot.juniper.net>
	<dcad22d804111906243e9854a8@mail.gmail.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Cc: pusateri@juniper.net, pim@ietf.org, 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>
Sender: pim-bounces@ietf.org
Errors-To: pim-bounces@ietf.org

>> Someone suggested that the POP count could be done as an application;
>> I suggested a stand alone protocol. I am dubious in general about
>> overloading one protocol with messages for another. Dino, can you give
>> us reasons why this belongs in the PIM join message as opposed to
>> somewhere else ?

    So you have sub-tree information at every hop. So you can get the 
    information quickly without polling. If it was easy to do at the app
    level, why hasn't it been done already.

    It's not a protocol. It's data that can be carried with and processed the
    same time with join state. It's trying to be efficient.

>> Will MPLS LPS require additional information in the PIM join, as James
>> Leelow seemed to indicate ?
>> Is there a draft or even a presentation or memo on this ?

    I missed the IETF so didn't see this comment. What was the comment?

Dino

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


From pim-bounces@ietf.org  Sat Nov 20 05:11:02 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA08639
	for <pim-archive@lists.ietf.org>; Sat, 20 Nov 2004 05:11:02 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CVS7U-0001cQ-7f; Sat, 20 Nov 2004 05:05:28 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CVS6Y-0001SC-Hz
	for pim@megatron.ietf.org; Sat, 20 Nov 2004 05:04:31 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA07952
	for <pim@ietf.org>; Sat, 20 Nov 2004 05:04:28 -0500 (EST)
Received: from rproxy.gmail.com ([64.233.170.193])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CVS9Y-00011a-JV
	for pim@ietf.org; Sat, 20 Nov 2004 05:07:37 -0500
Received: by rproxy.gmail.com with SMTP id a36so101887rnf
	for <pim@ietf.org>; Sat, 20 Nov 2004 02:04:28 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references;
	b=AfUY1Ez4V7KwBfsP/eqSUzc7xobN4sq0MKcHE1KICD1RH78x4mzXQ0t1fTmpMQN6g/me20tDK4pABb8Ate794wN7xswywgPCkKyI9O6s+gkpEE9h6SusrZdZF/Nek272DjBH+N2XCkIOlVdFfiGnLK54oK9GoHy6irnBfVxVrP4=
Received: by 10.38.171.55 with SMTP id t55mr84487rne;
	Sat, 20 Nov 2004 02:04:28 -0800 (PST)
Received: by 10.38.66.42 with HTTP; Sat, 20 Nov 2004 02:04:28 -0800 (PST)
Message-ID: <dcad22d80411200204104ff179@mail.gmail.com>
Date: Sat, 20 Nov 2004 05:04:28 -0500
From: Marshall Eubanks <marshall.eubanks@gmail.com>
To: Dino Farinacci <dino@cisco.com>
Subject: Re: [pim] PIM WG meeting notes
In-Reply-To: <200411200326.iAK3QdV21677@dino-lnx.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
References: <dino@cisco.com> <200411182356.iAINuK015664@dino-lnx.cisco.com>
	<200411190321.iAJ3Lie07088@merlot.juniper.net>
	<dcad22d804111906243e9854a8@mail.gmail.com>
	<200411200326.iAK3QdV21677@dino-lnx.cisco.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Content-Transfer-Encoding: 7bit
Cc: pusateri@juniper.net, pim@ietf.org, mmcbride@cisco.com
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Marshall Eubanks <marshall.eubanks@gmail.com>
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=subscribe>
Sender: pim-bounces@ietf.org
Errors-To: pim-bounces@ietf.org
Content-Transfer-Encoding: 7bit

Well, I can see several problems with doing it as an app - it would be
hard to get the app everywhere.

James suggested that the newly hot MPLS LSP will need TLV info in the PIM join :

>James Leelow from Data Connection - We need a generic TLV mechanism
to add information to the PIM >Join. This should have a common format
if it is going to be done at all.

I haven't waded through the 5 L3VPN  multicast drafts enough to know
what he is referring
to yet.

Marshall

On Fri, 19 Nov 2004 19:26:39 -0800, Dino Farinacci <dino@cisco.com> wrote:
> >> Someone suggested that the POP count could be done as an application;
> >> I suggested a stand alone protocol. I am dubious in general about
> >> overloading one protocol with messages for another. Dino, can you give
> >> us reasons why this belongs in the PIM join message as opposed to
> >> somewhere else ?
> 
>     So you have sub-tree information at every hop. So you can get the
>     information quickly without polling. If it was easy to do at the app
>     level, why hasn't it been done already.
> 
>     It's not a protocol. It's data that can be carried with and processed the
>     same time with join state. It's trying to be efficient.
> 
> >> Will MPLS LPS require additional information in the PIM join, as James
> >> Leelow seemed to indicate ?
> >> Is there a draft or even a presentation or memo on this ?
> 
>     I missed the IETF so didn't see this comment. What was the comment?
> 
> Dino
>

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


From pim-bounces@ietf.org  Mon Nov 22 10:53:39 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA10553
	for <pim-archive@lists.ietf.org>; Mon, 22 Nov 2004 10:53:39 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CWGPL-00049Z-E3; Mon, 22 Nov 2004 10:47:15 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CWGHx-0002ye-Nx
	for pim@megatron.ietf.org; Mon, 22 Nov 2004 10:39:37 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA09163
	for <pim@ietf.org>; Mon, 22 Nov 2004 10:39:35 -0500 (EST)
Received: from smtp2.dataconnection.com ([192.91.191.8]
	helo=smtp2.datcon.co.uk) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CWGLR-00023N-8n for pim@ietf.org; Mon, 22 Nov 2004 10:43:13 -0500
Received: by beiderbecke.datcon.co.uk with Internet Mail Service (5.5.2653.19)
	id <XGZJZRZR>; Mon, 22 Nov 2004 15:38:56 -0000
Message-ID: <53F74F5A7B94D511841C00B0D0AB16F803581269@baker.datcon.co.uk>
From: James Lingard <James.Lingard@dataconnection.com>
To: "'marshall.eubanks@gmail.com'" <marshall.eubanks@gmail.com>
Subject: Re: [pim] PIM WG meeting notes
Date: Mon, 22 Nov 2004 15:38:55 -0000
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15
Cc: "'pim@ietf.org'" <pim@ietf.org>
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=subscribe>
Sender: pim-bounces@ietf.org
Errors-To: pim-bounces@ietf.org

Marshall,

Let me clarify what I said during the meeting.

There are currently two individual Internet-Drafts being considered by the
WG that propose adding information to the Encoded-Source Address structure
used within the PIM Join/Prune message, namely:

-  draft-wijnands-pim-proxy-00
-  draft-farinacci-pim-pop-count-00.

In both of these drafts, the way of doing this is to define a new value of
the 'Encoding Type' field, which when used causes the structure to contain
several extra fields.

The point I made was that (without wanting to comment on the merit or
otherwise of either of these drafts themselves) if we are going to start
adding information to PIM Join messages, there are clear benefits in doing
this in a generic TLV-based mechanism, independent of any particular
extension.  The most significant advantage would be the ability to use
multiple such extensions simultaneously.

Responses to your particular questions are inline below.

Regards,
James.

-----Original Message-----
From: Marshall Eubanks [mailto:marshall.eubanks@gmail.com]
Sent: 19 November 2004 14:25
To: Tom Pusateri
Cc: pim@ietf.org; mmcbride@cisco.com
Subject: Re: [pim] PIM WG meeting notes

> Will MPLS LPS require additional information in the PIM join, as James
> Leelow [sic] seemed to indicate ?
> Is there a draft or even a presentation or memo on this ?

The draft I was referring to was draft-farinacci-mpls-multicast-03.  This
draft proposed a similar mechanism to the two drafts mentioned above, which
was used to distribute MPLS labels.  Instead of using a new 'Encoding Type'
value, it used a new 'Addr Family' - though it seems to me that a new
'Encoding Type' might have been more suitable in this situation as well.
Although this draft is long expired, I had heard a rumour that there was
interest in reviving this work.

None of the current P2MP LSP drafts in the mpls working group require this
or any other modifications to PIM.

> If this is really being opened up, it certainly makes Dino's idea less
> of a stretch for PIM, as it could be included in the more general
> changes.

Indeed.  Depending on your point of view, one of the benefits of a generic
approach would be that people who wanted to send extra information in
Join/Prune messages would be able to do so more easily, and in a way that
could be ignored by existing routers, just by defining a new TLV.

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

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


From pim-bounces@ietf.org  Mon Nov 22 13:23:39 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA29400
	for <pim-archive@lists.ietf.org>; Mon, 22 Nov 2004 13:23:39 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CWIiv-0007Bh-UP; Mon, 22 Nov 2004 13:15:38 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CWBML-0005pF-K1
	for pim@megatron.ietf.org; Mon, 22 Nov 2004 05:23:49 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA09521
	for <pim@ietf.org>; Mon, 22 Nov 2004 05:23:47 -0500 (EST)
Received: from v185.mailsnare.net ([206.246.200.185] helo=mail.mailsnare.net)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CWBPl-0001sQ-SH
	for pim@ietf.org; Mon, 22 Nov 2004 05:27:22 -0500
Message-ID: <1101118987.41a1be0b2eff9@horde.mailsnare.net>
Date: Mon, 22 Nov 2004 10:23:07 +0000
From: Ian <ipotts@msbx.net>
To: Prashant Jhingran <prashantj@huawei.com>
Subject: RE: [pim] PIM assert function
References: <000201c4aa90$55da9f20$30226e0a@huawei8tthy486>
In-Reply-To: <000201c4aa90$55da9f20$30226e0a@huawei8tthy486>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
User-Agent: Internet Messaging Program (IMP) 3.2.2
X-Virus-Scanned: by ClamAV at mailsnare.net
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9a2be21919e71dc6faef12b370c4ecf5
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Mon, 22 Nov 2004 13:15:35 -0500
Cc: pim@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=subscribe>
Sender: pim-bounces@ietf.org
Errors-To: pim-bounces@ietf.org
Content-Transfer-Encoding: quoted-printable

Hello,

Can I please seek some clarification on this high quality reply from Pras=
hant.=20

My question is how could an assert ever occur in PIM-SM, since once a PIM=
 DR
router on a LAN is elected, any other PIM-SM routers on the LAN should ne=
ver
forward multicast traffic onto that LAN.  My understanding is that an ass=
ert
would be sent in response to the PIM DR receiving a multicast stream on i=
ts
outgoing interface for that stream, and since no other routers are forwar=
ding
traffic since they haven't sent joins, an assert won't happen.

I am obviously missing a key point here, but I can't see it yet.  Please =
provide
guidance.

Many Thanks
Ian

Quoting Prashant Jhingran <prashantj@huawei.com>:

> Hello Kumar,
>=20
> Welcome to the group.
>=20
> Let me briefly explain you the following points about a DR:
>=20
> 1. The concept of DR and DR election is important in case of PIM-SM and
> not PIM-DM.
>=20
> 2. You are correct when you say "So DR in this case is responsible for
> generating Join after it receives igmp join" but incorrect when you say
> "...or pim join from its downstream terminals".
> -- DR election is necessary for electing a DR on a LAN, a router which
> is responsible for initiating  PIM trees (PIM-SM) as a result of IGMP
> reports. Hence in PIM-SM a DR starts acting as a forwarder on the LAN.
> However, the DR may loose an Assert election and therefore the winner
> may become the forwarder on the LAN.
> --In case of PIM-DM, its the assert mechanism which decides the
> forwarder on the LAN and DR election has nothing to do with the
> forwarder in DM.
>=20
> 3. The concept of DR is once again is of no use when it comes to
> exchange of join/prune messages between the PIM routers.=20
> --If you think over this point then you may come to a conclusion that
> Assert mechanism is required due to the above reason and also that
> Assert mechanism is an efficient way of deciding  the forwarder on the
> LAN.
>=20
> Hope this may clear your doubts.
>=20
> Regards,
> Prashant Jhingran
>=20
> Huawei Technologies=20
> Beijing, China
> Ph# 00-86-10-82882837  (O) =20
>=20
> "You see, all the problems in the world are created by those who want
> 'perfection.' " -- Sri Sri Ravi Shankar  www.artofliving.org =20
>=20
> -----Original Message-----
> From: pim-bounces@ietf.org [mailto:pim-bounces@ietf.org] On Behalf Of
> Kumar P
> Sent: Monday, October 04, 2004 2:29 PM
> To: pim@ietf.org
> Subject: [pim] PIM assert function
>=20
>=20
>=20
> Hello All,
>=20
> I am new to PIM, want someboby clear my following doubt.
>=20
> It is mentioned in the PIM draft that assert condition is likely to
> happen in multi-access environment where in there are more than one
> upstream routers present and have different opinion on reaching RP or
> Source, hence generate Join according and end up in receiving multiple
> streams of same data.
>=20
> Draft also mentions that there should only one forwarder in such
> environments, which is nothing but DR in this case. So DR in this case
> is responsible for generating Join after it receives igmp join or pim
> join from its downstream terminals. My doubt is when there is single
> DR(hence forwarder) on this multi-access media, how does the other
> routers send join towards RP or Source when ther are not responsible fo=
r
> the same.
>=20
> When a router doesn't send Join message also doesn't forward the
> multicast streams. Please clarify this.
>=20
> TIA,
> Kumar
>=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  Mon Nov 22 13:24:10 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA29533
	for <pim-archive@lists.ietf.org>; Mon, 22 Nov 2004 13:24:10 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CWIjk-0007KU-Le; Mon, 22 Nov 2004 13:16:28 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CVdKZ-00038j-Ny
	for pim@megatron.ietf.org; Sat, 20 Nov 2004 17:03:43 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA01491
	for <pim@ietf.org>; Sat, 20 Nov 2004 17:03:40 -0500 (EST)
Received: from relay1.mail.vrmd.de ([81.28.232.18])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CVdNW-0007NM-LX
	for pim@ietf.org; Sat, 20 Nov 2004 17:06:57 -0500
Received: from [195.14.221.78] (helo=[195.14.221.78])
	by vm8.bln2.vrmd.de with asmtp (Exim 4.41) id 1CVdK4-0000tu-C4
	for pim@ietf.org; Sat, 20 Nov 2004 23:03:12 +0100
Mime-Version: 1.0 (Apple Message framework v619)
In-Reply-To: <dcad22d80411200204104ff179@mail.gmail.com>
References: <dino@cisco.com> <200411182356.iAINuK015664@dino-lnx.cisco.com>
	<200411190321.iAJ3Lie07088@merlot.juniper.net>
	<dcad22d804111906243e9854a8@mail.gmail.com>
	<200411200326.iAK3QdV21677@dino-lnx.cisco.com>
	<dcad22d80411200204104ff179@mail.gmail.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <DF41E527-3B3F-11D9-8C5A-0030658FAAAC@let.de>
Content-Transfer-Encoding: 7bit
From: Marc Manthey <marc@let.de>
Subject: Re: [pim] PIM WG meeting notes
Date: Sat, 20 Nov 2004 23:02:29 +0100
To: pim@ietf.org
X-Mailer: Apple Mail (2.619)
X-Relay-User: marc@let.de
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Mon, 22 Nov 2004 13:16:26 -0500
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=subscribe>
Sender: pim-bounces@ietf.org
Errors-To: pim-bounces@ietf.org
Content-Transfer-Encoding: 7bit


On Nov 20, 2004, at 11:04 AM, Marshall Eubanks wrote:

> Well, I can see several problems with doing it as an app - it would be
> hard to get the app everywhere.
>
> James suggested that the newly hot MPLS LSP will need TLV info in the 
> PIM join :
>
>> James Leelow from Data Connection - We need a generic TLV mechanism
> to add information to the PIM >Join. This should have a common format
> if it is going to be done at all.
>
> I haven't waded through the 5 L3VPN  multicast drafts enough to know
> what he is referring
> to yet.
>
> Marshall--

hello all

during my  research  found something interesting  here:

.... the authentication of Intermediate System to
    Intermediate System (IS-IS) Protocol Data Units (PDUs) using the
    Hashed Message Authentication Codes - Message Digest 5 (HMAC-MD5)
    algorithm as found in RFC 2104...........

http://rfc.sunsite.dk/rfc/rfc3567.html

is there a way to implement this ?

http://brain.let.de


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


From pim-bounces@ietf.org  Mon Nov 22 13:26:30 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA29778
	for <pim-archive@lists.ietf.org>; Mon, 22 Nov 2004 13:26:30 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CWIkK-0007TT-DO; Mon, 22 Nov 2004 13:17:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CWIgi-0006e2-NR
	for pim@megatron.ietf.org; Mon, 22 Nov 2004 13:13:20 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA28336
	for <pim@ietf.org>; Mon, 22 Nov 2004 13:13:18 -0500 (EST)
Received: from sj-iport-2-in.cisco.com ([171.71.176.71]
	helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CWIkC-0007DV-NS for pim@ietf.org; Mon, 22 Nov 2004 13:16:58 -0500
Received: from sj-core-1.cisco.com (171.71.177.237)
	by sj-iport-2.cisco.com with ESMTP; 22 Nov 2004 10:15:49 -0800
Received: from dino-lnx.cisco.com (dino-lnx.cisco.com [171.71.54.55])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id iAMICg9N002643;
	Mon, 22 Nov 2004 10:12:43 -0800 (PST)
Received: (from dino@localhost)
	by dino-lnx.cisco.com (8.11.6/8.11.6) id iAMICii11520;
	Mon, 22 Nov 2004 10:12:44 -0800
Date: Mon, 22 Nov 2004 10:12:44 -0800
Message-Id: <200411221812.iAMICii11520@dino-lnx.cisco.com>
From: Dino Farinacci <dino@cisco.com>
To: James.Lingard@dataconnection.com
In-reply-to: <53F74F5A7B94D511841C00B0D0AB16F803581269@baker.datcon.co.uk>
	(message from James Lingard on Mon, 22 Nov 2004 15:38:55 -0000)
Subject: Re: [pim] PIM WG meeting notes
References: <53F74F5A7B94D511841C00B0D0AB16F803581269@baker.datcon.co.uk>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Cc: pim@ietf.org, marshall.eubanks@gmail.com
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=subscribe>
Sender: pim-bounces@ietf.org
Errors-To: pim-bounces@ietf.org

>> In both of these drafts, the way of doing this is to define a new value of
>> the 'Encoding Type' field, which when used causes the structure to contain
>> several extra fields.

    Yes, good point. I mentioned this to Ice after the PIM working group 
    meeting in San Diego.

>> The point I made was that (without wanting to comment on the merit or
>> otherwise of either of these drafts themselves) if we are going to start
>> adding information to PIM Join messages, there are clear benefits in doing
>> this in a generic TLV-based mechanism, independent of any particular
>> extension.  The most significant advantage would be the ability to use
>> multiple such extensions simultaneously.

    Yes. But I hope some day we can stop changing the protocol.  ;-)

Dino

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


From pim-bounces@ietf.org  Mon Nov 22 14:33:34 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA06089
	for <pim-archive@lists.ietf.org>; Mon, 22 Nov 2004 14:33:34 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CWJoC-00042m-JY; Mon, 22 Nov 2004 14:25:09 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CWJfH-0002P0-Qp
	for pim@megatron.ietf.org; Mon, 22 Nov 2004 14:15:55 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA04520
	for <pim@ietf.org>; Mon, 22 Nov 2004 14:15:54 -0500 (EST)
Received: from gateway.avici.com ([208.246.215.5] helo=mailhost.avici.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CWJib-0005fj-TP
	for pim@ietf.org; Mon, 22 Nov 2004 14:19:33 -0500
Received: from [127.0.0.1] ([10.2.104.24])
	by mailhost.avici.com (8.12.8/8.12.8) with ESMTP id iAMJEt4J012322;
	Mon, 22 Nov 2004 14:14:56 -0500
Message-ID: <41A23AB0.1020606@runbox.com>
Date: Mon, 22 Nov 2004 14:14:56 -0500
From: Shankar Vasudevan <shankarv@runbox.com>
User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Ian <ipotts@msbx.net>
Subject: Re: [pim] PIM assert function
References: <000201c4aa90$55da9f20$30226e0a@huawei8tthy486>
	<1101118987.41a1be0b2eff9@horde.mailsnare.net>
In-Reply-To: <1101118987.41a1be0b2eff9@horde.mailsnare.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Avici-MailScanner-Information: Please contact the ISP for more information
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a1852b4f554b02e7e4548cc7928acc1f
Content-Transfer-Encoding: 7bit
Cc: Prashant Jhingran <prashantj@huawei.com>, pim@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=subscribe>
Sender: pim-bounces@ietf.org
Errors-To: pim-bounces@ietf.org
Content-Transfer-Encoding: 7bit

Hello Ian,

   The routers on a LAN, "SHOULD" forward traffic when they receive a 
"Join" from a downstreaam
neighbor, irrespective of whether its a DR oro not. The PIM joins are 
not sent only to the DR. The Join is sent to the nbr
which is chosen by a router's unicast route towards a RP / Source.

    LAN need not be always in the edge alone. a LAN could be present 
somewhere as a intermediate and in those scenarios
Assert comes into picture, because two downstream routers may have a 
different route towards a RP / Source.

Best Regards,
Shankar


Ian wrote:

>Hello,
>
>Can I please seek some clarification on this high quality reply from Prashant. 
>
>My question is how could an assert ever occur in PIM-SM, since once a PIM DR
>router on a LAN is elected, any other PIM-SM routers on the LAN should never
>forward multicast traffic onto that LAN.  My understanding is that an assert
>would be sent in response to the PIM DR receiving a multicast stream on its
>outgoing interface for that stream, and since no other routers are forwarding
>traffic since they haven't sent joins, an assert won't happen.
>
>I am obviously missing a key point here, but I can't see it yet.  Please provide
>guidance.
>
>Many Thanks
>Ian
>
>Quoting Prashant Jhingran <prashantj@huawei.com>:
>
>  
>
>>Hello Kumar,
>>
>>Welcome to the group.
>>
>>Let me briefly explain you the following points about a DR:
>>
>>1. The concept of DR and DR election is important in case of PIM-SM and
>>not PIM-DM.
>>
>>2. You are correct when you say "So DR in this case is responsible for
>>generating Join after it receives igmp join" but incorrect when you say
>>"...or pim join from its downstream terminals".
>>-- DR election is necessary for electing a DR on a LAN, a router which
>>is responsible for initiating  PIM trees (PIM-SM) as a result of IGMP
>>reports. Hence in PIM-SM a DR starts acting as a forwarder on the LAN.
>>However, the DR may loose an Assert election and therefore the winner
>>may become the forwarder on the LAN.
>>--In case of PIM-DM, its the assert mechanism which decides the
>>forwarder on the LAN and DR election has nothing to do with the
>>forwarder in DM.
>>
>>3. The concept of DR is once again is of no use when it comes to
>>exchange of join/prune messages between the PIM routers. 
>>--If you think over this point then you may come to a conclusion that
>>Assert mechanism is required due to the above reason and also that
>>Assert mechanism is an efficient way of deciding  the forwarder on the
>>LAN.
>>
>>Hope this may clear your doubts.
>>
>>Regards,
>>Prashant Jhingran
>>
>>Huawei Technologies 
>>Beijing, China
>>Ph# 00-86-10-82882837  (O)  
>>
>>"You see, all the problems in the world are created by those who want
>>'perfection.' " -- Sri Sri Ravi Shankar  www.artofliving.org  
>>
>>-----Original Message-----
>>From: pim-bounces@ietf.org [mailto:pim-bounces@ietf.org] On Behalf Of
>>Kumar P
>>Sent: Monday, October 04, 2004 2:29 PM
>>To: pim@ietf.org
>>Subject: [pim] PIM assert function
>>
>>
>>
>>Hello All,
>>
>>I am new to PIM, want someboby clear my following doubt.
>>
>>It is mentioned in the PIM draft that assert condition is likely to
>>happen in multi-access environment where in there are more than one
>>upstream routers present and have different opinion on reaching RP or
>>Source, hence generate Join according and end up in receiving multiple
>>streams of same data.
>>
>>Draft also mentions that there should only one forwarder in such
>>environments, which is nothing but DR in this case. So DR in this case
>>is responsible for generating Join after it receives igmp join or pim
>>join from its downstream terminals. My doubt is when there is single
>>DR(hence forwarder) on this multi-access media, how does the other
>>routers send join towards RP or Source when ther are not responsible for
>>the same.
>>
>>When a router doesn't send Join message also doesn't forward the
>>multicast streams. Please clarify this.
>>
>>TIA,
>>Kumar
>>
>>
>>_______________________________________________
>>pim mailing list
>>pim@ietf.org
>>https://www1.ietf.org/mailman/listinfo/pim
>>    
>>
>
>
>_______________________________________________
>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 Nov 22 23:14:25 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA10792
	for <pim-archive@lists.ietf.org>; Mon, 22 Nov 2004 23:14:25 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CWRw2-0004DL-JX; Mon, 22 Nov 2004 23:05:46 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CWRrh-0003HN-J8
	for pim@megatron.ietf.org; Mon, 22 Nov 2004 23:01:20 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA09712
	for <pim@ietf.org>; Mon, 22 Nov 2004 23:01:15 -0500 (EST)
Received: from web54703.mail.yahoo.com ([68.142.225.201])
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CWRvH-0001jB-2i
	for pim@ietf.org; Mon, 22 Nov 2004 23:05:00 -0500
Received: (qmail 95891 invoked by uid 60001); 23 Nov 2004 04:00:45 -0000
Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com;
	b=xVTkBB/fdOLvYGngRK+PrRPjzJn5xcSObbpnkwdQPuXRfdkbCTaK7i6Hx6XiN1EZFW/5kLdRUwJ0epZztep6SmqrSE3v3Qi7tKjwwDMaxLT8/1AY8L47f6Cm1iv59NwJKDbgyrovC6abBQ2SewgYy0M9AfFh0uA2SlwYEMwtvos=
	; 
Message-ID: <20041123040045.95889.qmail@web54703.mail.yahoo.com>
Received: from [203.124.166.179] by web54703.mail.yahoo.com via HTTP;
	Mon, 22 Nov 2004 20:00:45 PST
Date: Mon, 22 Nov 2004 20:00:45 -0800 (PST)
From: Kumar P <kumar_xpim@yahoo.com>
Subject: Re: [pim] PIM assert function
To: Shankar Vasudevan <shankarv@runbox.com>, Ian <ipotts@msbx.net>
In-Reply-To: <41A23AB0.1020606@runbox.com>
MIME-Version: 1.0
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2a76bcd37b1c8a21336eb0a1ea6bbf48
Cc: Prashant Jhingran <prashantj@huawei.com>, pim@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1235478450=="
Sender: pim-bounces@ietf.org
Errors-To: pim-bounces@ietf.org

--===============1235478450==
Content-Type: multipart/alternative; boundary="0-495888679-1101182445=:95828"

--0-495888679-1101182445=:95828
Content-Type: text/plain; charset=us-ascii
X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id XAA09712
Content-Transfer-Encoding: quoted-printable

Hi,
please see my response below,

Shankar Vasudevan <shankarv@runbox.com> wrote:

Hello Ian,

The routers on a LAN, "SHOULD" forward traffic when they receive a=20
"Join" from a downstreaam
neighbor, irrespective of whether its a DR oro not. The PIM joins are=20
not sent only to the DR. The Join is sent to the nbr
which is chosen by a router's unicast route towards a RP / Source.


>>>ok thats right, but the question is why does the other router present =
on >>>the same LAN generate Join message towards RP/Source and pull the >=
>>traffic in first place. If it doesn't generate join in that way then th=
ere wont be >>>any assert in future.


LAN need not be always in the edge alone. a LAN could be present=20
somewhere as a intermediate and in those scenarios
Assert comes into picture, because two downstream routers may have a=20
different route towards a RP / Source.

>>>will you please explain how assert happens in edge LANs first. Because=
 >>>my idea is, DR in edge LAN is the one who initiates the tree from sen=
ding >>>join towards its appropriate upstream neighbor towards RP/Source.=
 In this >>>situation I fail to understand, why does the others(non DRs) =
present on the >>>same LAN care to send Join when they are not supposed t=
o?=20

Best Regards,
Shankar


Ian wrote:

>Hello,
>
>Can I please seek some clarification on this high quality reply from Pra=
shant.=20
>
>My question is how could an assert ever occur in PIM-SM, since once a PI=
M DR
>router on a LAN is elected, any other PIM-SM routers on the LAN should n=
ever
>forward multicast traffic onto that LAN. My understanding is that an ass=
ert
>would be sent in response to the PIM DR receiving a multicast stream on =
its
>outgoing interface for that stream, and since no other routers are forwa=
rding
>traffic since they haven't sent joins, an assert won't happen.
>
>I am obviously missing a key point here, but I can't see it yet. Please =
provide
>guidance.
>
>Many Thanks
>Ian
>
>Quoting Prashant Jhingran=20
:
>
>=20
>
>>Hello Kumar,
>>
>>Welcome to the group.
>>
>>Let me briefly explain you the following points about a DR:
>>
>>1. The concept of DR and DR election is important in case of PIM-SM and
>>not PIM-DM.
>>
>>2. You are correct when you say "So DR in this case is responsible for
>>generating Join after it receives igmp join" but incorrect when you say
>>"...or pim join from its downstream terminals".
>>-- DR election is necessary for electing a DR on a LAN, a router which
>>is responsible for initiating PIM trees (PIM-SM) as a result of IGMP
>>reports. Hence in PIM-SM a DR starts acting as a forwarder on the LAN.
>>However, the DR may loose an Assert election and therefore the winner
>>may become the forwarder on the LAN.
>>--In case of PIM-DM, its the assert mechanism which decides the
>>forwarder on the LAN and DR election has nothing to do with the
>>forwarder in DM.
>>
>>3. The concept of DR is once again is of no use when it comes to
>>exchange of join/prune messages between the PIM routers.=20
>>--If you think over this point then you may come to a conclusion that
>>Assert mechanism is required due to the above reason and also that
>>Assert mechanism is an efficient way of deciding the forwarder on the
>>LAN.
>>
>>Hope this may clear your doubts.
>>
>>Regards,
>>Prashant Jhingran
>>
>>Huawei Technologies=20
>>Beijing, China
>>Ph# 00-86-10-82882837 (O)=20
>>
>>"You see, all the problems in the world are created by those who want
>>'perfection.' " -- Sri Sri Ravi Shankar www.artofliving.org=20
>>
>>-----Original Message-----
>>From: pim-bounces@ietf.org [mailto:pim-bounces@ietf.org] On Behalf Of
>>Kumar P
>>Sent: Monday, October 04, 2004 2:29 PM
>>To: pim@ietf.org
>>Subject: [pim] PIM assert function
>>
>>
>>
>>Hello All,
>>
>>I am new to PIM, want someboby clear my following doubt.
>>
>>It is mentioned in the PIM draft that assert condition is likely to
>>happen in multi-access environment where in there are more than one
>>upstream routers present and have different opinion on reaching RP or
>>Source, hence generate Join according and end up in receiving multiple
>>streams of same data.
>>
>>Draft also mentions that there should only one forwarder in such
>>environments, which is nothing but DR in this case. So DR in this case
>>is responsible for generating Join after it receives igmp join or pim
>>join from its downstream terminals. My doubt is when there is single
>>DR(hence forwarder) on this multi-access media, how does the other
>>routers send join towards RP or Source when ther are not responsible fo=
r
>>the same.
>>
>>When a router doesn't send Join message also doesn't forward the
>>multicast streams. Please clarify this.
>>
>>TIA,
>>Kumar
>>
>>
>>_______________________________________________
>>pim mailing list
>>pim@ietf.org
>>https://www1.ietf.org/mailman/listinfo/pim
>>=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


	=09
---------------------------------
Do you Yahoo!?
 Discover all that=92s new in My Yahoo!
--0-495888679-1101182445=:95828
Content-Type: text/html; charset=us-ascii
X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id XAA09712
Content-Transfer-Encoding: quoted-printable

<DIV>Hi,</DIV>
<DIV>please see my response below,<BR><BR><B><I>Shankar Vasudevan &lt;sha=
nkarv@runbox.com&gt;</I></B> wrote:</DIV>
<BLOCKQUOTE class=3Dreplbq style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #1010ff 2px solid">
<P>Hello Ian,<BR><BR>The routers on a LAN, "SHOULD" forward traffic when =
they receive a <BR>"Join" from a downstreaam<BR>neighbor, irrespective of=
 whether its a DR oro not. The PIM joins are <BR>not sent only to the DR.=
 The Join is sent to the nbr<BR>which is chosen by a router's unicast rou=
te towards a RP / Source.</P>
<P><BR>&gt;&gt;&gt;ok thats right, but the question is why does the other=
 router present on &gt;&gt;&gt;the same LAN generate Join message towards=
 RP/Source and pull the &gt;&gt;&gt;traffic in first place. If it doesn't=
 generate join in that way then there wont be &gt;&gt;&gt;any assert in f=
uture.</P>
<P><BR>LAN need not be always in the edge alone. a LAN could be present <=
BR>somewhere as a intermediate and in those scenarios<BR>Assert comes int=
o picture, because two downstream routers may have a <BR>different route =
towards a RP / Source.</P>
<P>&gt;&gt;&gt;will you please explain how assert happens in edge LANs fi=
rst. Because &gt;&gt;&gt;my idea is, DR in edge LAN is the one who initia=
tes the tree from sending &gt;&gt;&gt;join towards its appropriate upstre=
am neighbor towards RP/Source. In this &gt;&gt;&gt;situation I fail to un=
derstand, why does the others(non DRs) present on the &gt;&gt;&gt;same LA=
N care to send Join when they are not supposed to? <BR><BR>Best Regards,<=
BR>Shankar<BR><BR><BR>Ian wrote:<BR><BR>&gt;Hello,<BR>&gt;<BR>&gt;Can I p=
lease seek some clarification on this high quality reply from Prashant. <=
BR>&gt;<BR>&gt;My question is how could an assert ever occur in PIM-SM, s=
ince once a PIM DR<BR>&gt;router on a LAN is elected, any other PIM-SM ro=
uters on the LAN should never<BR>&gt;forward multicast traffic onto that =
LAN. My understanding is that an assert<BR>&gt;would be sent in response =
to the PIM DR receiving a multicast stream on its<BR>&gt;outgoing interfa=
ce for that stream, and since no other routers
 are forwarding<BR>&gt;traffic since they haven't sent joins, an assert w=
on't happen.<BR>&gt;<BR>&gt;I am obviously missing a key point here, but =
I can't see it yet. Please provide<BR>&gt;guidance.<BR>&gt;<BR>&gt;Many T=
hanks<BR>&gt;Ian<BR>&gt;<BR>&gt;Quoting Prashant Jhingran <PRASHANTJ@HUAW=
EI.COM>:<BR>&gt;<BR>&gt; <BR>&gt;<BR>&gt;&gt;Hello Kumar,<BR>&gt;&gt;<BR>=
&gt;&gt;Welcome to the group.<BR>&gt;&gt;<BR>&gt;&gt;Let me briefly expla=
in you the following points about a DR:<BR>&gt;&gt;<BR>&gt;&gt;1. The con=
cept of DR and DR election is important in case of PIM-SM and<BR>&gt;&gt;=
not PIM-DM.<BR>&gt;&gt;<BR>&gt;&gt;2. You are correct when you say "So DR=
 in this case is responsible for<BR>&gt;&gt;generating Join after it rece=
ives igmp join" but incorrect when you say<BR>&gt;&gt;"...or pim join fro=
m its downstream terminals".<BR>&gt;&gt;-- DR election is necessary for e=
lecting a DR on a LAN, a router which<BR>&gt;&gt;is responsible for initi=
ating PIM trees (PIMM-SM) as a result of
 IGMP<BR>&gt;&gt;reports. Hence in PIM-SM a DR starts acting as a forward=
er on the LAN.<BR>&gt;&gt;However, the DR may loose an Assert election an=
d therefore the winner<BR>&gt;&gt;may become the forwarder on the LAN.<BR=
>&gt;&gt;--In case of PIM-DM, its the assert mechanism which decides the<=
BR>&gt;&gt;forwarder on the LAN and DR election has nothing too do with t=
he<BR>&gt;&gt;forwarder in DM.<BR>&gt;&gt;<BR>&gt;&gt;3. The concept of D=
R is once again is of no use when it comes to<BR>&gt;&gt;exchange of join=
/prune messages between the PIM routers. <BR>&gt;&gt;--If you think over =
this point then you may come to a conclusion that<BR>&gt;&gt;Assert mecha=
nism is required due to the above reason and also that<BR>&gt;&gt;Assert =
mechanism is an efficient way of deciding the forwarder on the<BR>&gt;&gt=
;LAN.<BR>&gt;&gt;<BR>&gt;&gt;Hope this may clear your doubts.<BR>&gt;&gt;=
<BR>&gt;&gt;Regards,<BR>&gt;&gt;Prashant Jhingran<BR>&gt;&gt;<BR>&gt;&gt;=
Huawei Technologies <BR>&gt;&gt;Beijing,
 China<BR>&gt;&gt;Ph# 00-86-10-82882837 (O) <BR>&gt;&gt;<BR>&gt;&gt;"You =
see, all the problems in the world are created by those who want<BR>&gt;&=
gt;'perfection.' " -- Sri Sri Ravi Shankar www.artofliving.org <BR>&gt;&g=
t;<BR>&gt;&gt;-----Original Message-----<BR>&gt;&gt;From: pim-bounces@iee=
tf.org [mailto:pim-bounces@ietf.org] On Behalf Of<BR>&gt;&gt;Kumar P<BR>&=
gt;&gt;Sent: Monday, October 04, 2004 2:29 PM<BR>&gt;&gt;To: pim@ietf.org=
<BR>&gt;&gt;Subject: [pim] PIM assert function<BR>&gt;&gt;<BR>&gt;&gt;<BR=
>&gt;&gt;<BR>&gt;&gt;Hello All,<BR>&gt;&gt;<BR>&gt;&gt;I am new to PIM, w=
ant someboby clear my following doubt.<BR>&gt;&gt;<BR>&gt;&gt;It is menti=
oned in the PIM draft that assert condition is likely to<BR>&gt;&gt;happe=
n in multi-access environment where in there are more than one<BR>&gt;&gt=
;upstream routers present and have different opinion on reaching RP or<BR=
>&gt;&gt;Source, hence generate Join according and end up in receiving mu=
ltiple<BR>&gt;&gt;streams of same
 data.<BR>&gt;&gt;<BR>&gt;&gt;Draft also mentions that there should only =
one forwarder in such<BR>&gt;&gt;environments, which is nothing but DR in=
 this case. So DR in this case<BR>&gt;&gt;is responsible for generating J=
oin after it receives igmp join or pim<BR>&gt;&gt;join from its downstrea=
m terminals. My doubt is when there is single<BR>&gt;&gt;DR(hence forward=
er) on this multi-access media, how does the other<BR>&gt;&gt;routers sen=
d join towards RP or Source when ther are not responsible for<BR>&gt;&gt;=
the same.<BR>&gt;&gt;<BR>&gt;&gt;When a router doesn't send Join message =
also doesn't forward the<BR>&gt;&gt;multicast streams. Please clarify thi=
s.<BR>&gt;&gt;<BR>&gt;&gt;TIA,<BR>&gt;&gt;Kumar<BR>&gt;&gt;<BR>&gt;&gt;<B=
R>&gt;&gt;_______________________________________________<BR>&gt;&gt;pim =
mailing list<BR>&gt;&gt;pim@ietf.org<BR>&gt;&gt;https://www1.ietf.org/mai=
lman/listinfo/pim<BR>&gt;&gt;
 <BR>&gt;&gt;<BR>&gt;<BR>&gt;<BR>&gt;____________________________________=
___________<BR>&gt;pim mailing list<BR>&gt;pim@ietf.org<BR>&gt;https://ww=
w1.ietf.org/mailman/listinfo/pim<BR>&gt;<BR>&gt;<BR>&gt;<BR>&gt; <BR>&gt;=
<BR><BR><BR><BR>_______________________________________________<BR>pim ma=
iling list<BR>pim@ietf.org<BR>https://www1.ietf.org/mailman/listinfo/pim<=
BR></P></BLOCKQUOTE><p>
		<hr size=3D1>Do you Yahoo!?<br>=20
Discover all that=92s new in <a href=3D"http://my.yahoo.com">My Yahoo!</a=
>
--0-495888679-1101182445=:95828--


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

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

--===============1235478450==--



From pim-bounces@ietf.org  Tue Nov 23 05:03:32 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA22396
	for <pim-archive@lists.ietf.org>; Tue, 23 Nov 2004 05:03:32 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CWXSY-0008EY-Gj; Tue, 23 Nov 2004 04:59:42 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CWXKn-0006Bj-4V
	for pim@megatron.ietf.org; Tue, 23 Nov 2004 04:51:42 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA21464
	for <pim@ietf.org>; Tue, 23 Nov 2004 04:51:38 -0500 (EST)
Received: from netcore.fi ([193.94.160.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CWXOQ-00058P-Ac
	for pim@ietf.org; Tue, 23 Nov 2004 04:55:26 -0500
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id iAN9p6607636
	for <pim@ietf.org>; Tue, 23 Nov 2004 11:51:06 +0200
Date: Tue, 23 Nov 2004 11:51:06 +0200 (EET)
From: Pekka Savola <pekkas@netcore.fi>
To: pim@ietf.org
Message-ID: <Pine.LNX.4.61.0411231146440.7539@netcore.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465
Subject: [pim] last-hop threats by hosts to PIM
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=subscribe>
Sender: pim-bounces@ietf.org
Errors-To: pim-bounces@ietf.org

Hi,

Based on the discussions on the list, and encouragement from a couple 
of people, plus a suggestion that it might make sense to try to attack 
this problem separately from the IGMP/MLD perspective, I've written a 
short I-D (only 10 pages, including the boilerplates!) on the last-hop 
threats by hosts to PIM:

Abstract
    Security threats analysis has been done on some parts of the
    multicast infrastructure, but the threats specific to the last-hop
    attacks by hosts on the PIM routing protocol have not been well
    described in the past.  This memo aims to fill that gap.

It has been submitted, but in the interim, available at:

http://www.netcore.fi/pekkas/ietf/draft-savola-pim-lasthop-threats-00.txt

This complements I-D.ietf-mboned-mroutesec and 
I-D.daley-magma-smld-prob.

Feedback is welcome!

In particular, I would be interested in getting expert opinion on the 
following XXX points:

    It seems that a DR can send PIM messages (like Prune/Join) to the
    non-DR to be forwarded upstream on behalf of directly connected (to
    both DR and non-DR) sources.  In other words, a host on a stub LAN
    can be elected as a DR and act as a "man-in-the-middle" between the
    other hosts and the real PIM router.  [XXX: Is this correct?  Should
    non-DRs reject forwarding upstream messages from downstream LAN's
    DRs, because a real DR should have its own upstream connectivity?]
...
    With a PIM Assert, a router can be elected to be in charge of
    handling all traffic from a particular (S,G) (where S might also be
    all of S? [XXX: true?]).  This overrides DR behaviour.
...
    As noted before, it is also possible to spoof an Assert on someone
    else's behalf to cause a temporary disruption on the LAN.  However,
    it is not 100% clear what happens when the router which was spoofed
    receives "it's own assert" and CouldAssert(S,G,I) is False?  [XXX: a
    PIM expert should say something?  Is this an issue in the state
    machine?]


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

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


From pim-bounces@ietf.org  Tue Nov 23 14:14:35 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09779
	for <pim-archive@lists.ietf.org>; Tue, 23 Nov 2004 14:14:35 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CWg2K-0006Qi-Iz; Tue, 23 Nov 2004 14:09:12 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CWfz0-0005Gx-Q8
	for pim@megatron.ietf.org; Tue, 23 Nov 2004 14:05:46 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09111
	for <pim@ietf.org>; Tue, 23 Nov 2004 14:05:44 -0500 (EST)
Received: from rproxy.gmail.com ([64.233.170.204])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CWg2i-0003Ee-2g
	for pim@ietf.org; Tue, 23 Nov 2004 14:09:37 -0500
Received: by rproxy.gmail.com with SMTP id a36so7491rnf
	for <pim@ietf.org>; Tue, 23 Nov 2004 11:05:44 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references;
	b=fOtKn/QNzqKI1hUFF5G4liD0ptMSDn2tA+FbUbj/ZRSPpBtjzH9KJ7Txl9+D1JFrl2mx/NCkmcF/PVGnt3ZHMhv/7XV2OtTZwCsqLtN6srxRr1/Y/hcmQEVk7SUmDWef3qnTNNmfg7cH007ffLLLL2Z1Iu2+FNl+MKWtmKbMAM8=
Received: by 10.38.75.50 with SMTP id x50mr263060rna;
	Tue, 23 Nov 2004 11:05:43 -0800 (PST)
Received: by 10.38.66.34 with HTTP; Tue, 23 Nov 2004 11:05:43 -0800 (PST)
Message-ID: <dcad22d80411231105327428e5@mail.gmail.com>
Date: Tue, 23 Nov 2004 14:05:43 -0500
From: Marshall Eubanks <marshall.eubanks@gmail.com>
To: James Lingard <james.lingard@dataconnection.com>
Subject: Re: [pim] PIM WG meeting notes
In-Reply-To: <53F74F5A7B94D511841C00B0D0AB16F803581269@baker.datcon.co.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
References: <53F74F5A7B94D511841C00B0D0AB16F803581269@baker.datcon.co.uk>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b280b4db656c3ca28dd62e5e0b03daa8
Content-Transfer-Encoding: 7bit
Cc: "pim@ietf.org" <pim@ietf.org>
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Marshall Eubanks <marshall.eubanks@gmail.com>
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=subscribe>
Sender: pim-bounces@ietf.org
Errors-To: pim-bounces@ietf.org
Content-Transfer-Encoding: 7bit

Dear James;

Thanks for clarifying this (and my apologies for not catching the
spelling of your name).

One thing I would worry about about doing these things in PIM are
security issues, such as what happens if the MTU is exceeded. It would
be clearly
better to have one generic extension than to have several ad hoc ones.

Regards
Marshall


On Mon, 22 Nov 2004 15:38:55 -0000, James Lingard
<james.lingard@dataconnection.com> wrote:
> Marshall,
> 
> Let me clarify what I said during the meeting.
> 
> There are currently two individual Internet-Drafts being considered by the
> WG that propose adding information to the Encoded-Source Address structure
> used within the PIM Join/Prune message, namely:
> 
> -  draft-wijnands-pim-proxy-00
> -  draft-farinacci-pim-pop-count-00.
> 
> In both of these drafts, the way of doing this is to define a new value of
> the 'Encoding Type' field, which when used causes the structure to contain
> several extra fields.
> 
> The point I made was that (without wanting to comment on the merit or
> otherwise of either of these drafts themselves) if we are going to start
> adding information to PIM Join messages, there are clear benefits in doing
> this in a generic TLV-based mechanism, independent of any particular
> extension.  The most significant advantage would be the ability to use
> multiple such extensions simultaneously.
> 
> Responses to your particular questions are inline below.
> 
> Regards,
> James.
> 
> 
> 
> -----Original Message-----
> From: Marshall Eubanks [mailto:marshall.eubanks@gmail.com]
> Sent: 19 November 2004 14:25
> To: Tom Pusateri
> Cc: pim@ietf.org; mmcbride@cisco.com
> Subject: Re: [pim] PIM WG meeting notes
> 
> > Will MPLS LPS require additional information in the PIM join, as James
> > Leelow [sic] seemed to indicate ?
> > Is there a draft or even a presentation or memo on this ?
> 
> The draft I was referring to was draft-farinacci-mpls-multicast-03.  This
> draft proposed a similar mechanism to the two drafts mentioned above, which
> was used to distribute MPLS labels.  Instead of using a new 'Encoding Type'
> value, it used a new 'Addr Family' - though it seems to me that a new
> 'Encoding Type' might have been more suitable in this situation as well.
> Although this draft is long expired, I had heard a rumour that there was
> interest in reviving this work.
> 
> None of the current P2MP LSP drafts in the mpls working group require this
> or any other modifications to PIM.
> 
> > If this is really being opened up, it certainly makes Dino's idea less
> > of a stretch for PIM, as it could be included in the more general
> > changes.
> 
> Indeed.  Depending on your point of view, one of the benefits of a generic
> approach would be that people who wanted to send extra information in
> Join/Prune messages would be able to do so more easily, and in a way that
> could be ignored by existing routers, just by defining a new TLV.
> 
> --
> James Lingard
> Data Connection Ltd (DCL)
> http://www.dataconnection.com/
> 
>

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


From pim-bounces@ietf.org  Mon Nov 29 01:10:24 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA02657
	for <pim-archive@lists.ietf.org>; Mon, 29 Nov 2004 01:10:24 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CYed3-0001u2-Is; Mon, 29 Nov 2004 01:03:17 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CYeaR-0001Y4-8p
	for pim@megatron.ietf.org; Mon, 29 Nov 2004 01:00:35 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA01961
	for <pim@ietf.org>; Mon, 29 Nov 2004 01:00:34 -0500 (EST)
Received: from [220.227.179.21] (helo=kecgate03.infosys.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CYefF-000084-HW
	for pim@ietf.org; Mon, 29 Nov 2004 01:05:35 -0500
Received: from indhubbhs01.ad.infosys.com ([192.168.200.81]) by
	kecgate03.infosys.com with InterScan Messaging Security Suite;
	Mon, 29 Nov 2004 11:24:32 +0530
Received: from kecmsg07.ad.infosys.com ([192.168.200.68]) by
	indhubbhs01.ad.infosys.com with Microsoft SMTPSVC(5.0.2195.6713); 
	Mon, 29 Nov 2004 11:28:39 +0530
Received: from BLRKECOWA01.ad.infosys.com ([192.168.200.65]) by
	kecmsg07.ad.infosys.com with Microsoft SMTPSVC(5.0.2195.6713); 
	Mon, 29 Nov 2004 11:28:33 +0530
Received: from itlpc27356 ([198.202.188.189]) by BLRKECOWA01.ad.infosys.com
	with Microsoft SMTPSVC(5.0.2195.6713); 
	Mon, 29 Nov 2004 11:28:33 +0530
Message-ID: <04b801c4d5d8$f15b9620$bdbccac6@itlpc27356>
From: "Mohamed Riyaz" <mohamedriyazt_m@infosys.com>
To: <pim@ietf.org>
Date: Mon, 29 Nov 2004 11:31:57 +0530
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1437
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
X-OriginalArrivalTime: 29 Nov 2004 05:58:33.0851 (UTC)
	FILETIME=[75C1E4B0:01C4D5D8]
X-Spam-Score: 0.8 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Subject: [pim] Need help.... on sending prune with S to RP ?
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="===============1846739003=="
Sender: pim-bounces@ietf.org
Errors-To: pim-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1846739003==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_04B3_01C4D607.08F90870"

This is a multi-part message in MIME format.

------=_NextPart_000_04B3_01C4D607.08F90870
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

When local source S starts sending to group G, the RFC says that the DR =
sends a j/p message with S in prune list, if a (*,G) or (*,*,RP) entry =
is present. What is the intend of this ?.

TIA
-R
------=_NextPart_000_04B3_01C4D607.08F90870
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2800.1476" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV>When local source S starts sending to group G, the RFC says that =
the DR=20
sends a j/p message with S in prune list, if a (*,G) or (*,*,RP) entry =
is=20
present. What is the intend of this ?.</DIV>
<DIV>&nbsp;</DIV>
<DIV>TIA</DIV>
<DIV>-R</DIV></BODY></HTML>

------=_NextPart_000_04B3_01C4D607.08F90870--



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

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

--===============1846739003==--




From pim-bounces@ietf.org  Mon Nov 29 01:39:51 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA05249
	for <pim-archive@lists.ietf.org>; Mon, 29 Nov 2004 01:39:50 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CYfAX-0001dp-HP; Mon, 29 Nov 2004 01:37:53 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CYf6T-0000Zq-7q
	for pim@megatron.ietf.org; Mon, 29 Nov 2004 01:33:41 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA04674
	for <pim@ietf.org>; Mon, 29 Nov 2004 01:33:39 -0500 (EST)
Received: from mail.riverstonenet.com ([63.113.148.10] helo=riverstonenet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CYfBI-0000nT-Qc
	for pim@ietf.org; Mon, 29 Nov 2004 01:38:41 -0500
Received: from legolas.rs.riverstonenet.com by riverstonenet.com
	(8.9.3+Sun/SMI-SVR4-Yago)
	id WAA06251; Sun, 28 Nov 2004 22:33:07 -0800 (PST)
Received: from rnataraja ([172.24.2.250]) by legolas.rs.riverstonenet.com with
	Microsoft SMTPSVC(6.0.3790.211); Sun, 28 Nov 2004 22:33:06 -0800
Message-ID: <024601c4d5dc$d9008d70$fa0218ac@rnataraja>
From: "Rajesh Babu Nataraja" <rnataraja@riverstonenet.com>
To: "Mohamed Riyaz" <mohamedriyazt_m@infosys.com>, <pim@ietf.org>
References: <04b801c4d5d8$f15b9620$bdbccac6@itlpc27356>
Subject: Re: [pim] Need help.... on sending prune with S to RP ?
Date: Mon, 29 Nov 2004 11:59:55 +0530
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2180
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-OriginalArrivalTime: 29 Nov 2004 06:33:06.0718 (UTC)
	FILETIME=[49484BE0:01C4D5DD]
X-Spam-Score: 0.5 (/)
X-Scan-Signature: cf3becbbd6d1a45acbe2ffd4ab88bdc2
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Rajesh Babu Nataraja <rnataraja@riverstonenet.com>
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0098899445=="
Sender: pim-bounces@ietf.org
Errors-To: pim-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0098899445==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0243_01C4D60A.F0F176F0"

This is a multi-part message in MIME format.

------=_NextPart_000_0243_01C4D60A.F0F176F0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi R,
If you analyse the way (S, G) RPT prune messages are sent to the RP. =
This would turn out to be one of the obvious cases of sending (S, G) RPT =
prune when we start receiving traffic on the SPT.

T & R
R
  ----- Original Message -----=20
  From: Mohamed Riyaz=20
  To: pim@ietf.org=20
  Sent: Monday, November 29, 2004 11:31 AM
  Subject: [pim] Need help.... on sending prune with S to RP ?


  When local source S starts sending to group G, the RFC says that the =
DR sends a j/p message with S in prune list, if a (*,G) or (*,*,RP) =
entry is present. What is the intend of this ?.

  TIA
  -R


-------------------------------------------------------------------------=
-----


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

------=_NextPart_000_0243_01C4D60A.F0F176F0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2900.2523" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Hi R,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>If you analyse the way (S, G) RPT prune =
messages=20
are sent to the RP. This would turn out to be one=20
of&nbsp;the&nbsp;obvious&nbsp;cases of sending (S, G) RPT prune when we =
start=20
receiving traffic on the SPT.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>T &amp; R</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>R</FONT></DIV>
<BLOCKQUOTE=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
  <DIV style=3D"FONT: 10pt arial">----- Original Message ----- </DIV>
  <DIV=20
  style=3D"BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: =
black"><B>From:</B>=20
  <A title=3Dmohamedriyazt_m@infosys.com=20
  href=3D"mailto:mohamedriyazt_m@infosys.com">Mohamed Riyaz</A> </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>To:</B> <A title=3Dpim@ietf.org=20
  href=3D"mailto:pim@ietf.org">pim@ietf.org</A> </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Monday, November 29, 2004 =
11:31=20
  AM</DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Subject:</B> [pim] Need help.... on =
sending=20
  prune with S to RP ?</DIV>
  <DIV><BR></DIV>
  <DIV>When local source S starts sending to group G, the RFC says that =
the DR=20
  sends a j/p message with S in prune list, if a (*,G) or (*,*,RP) entry =
is=20
  present. What is the intend of this ?.</DIV>
  <DIV>&nbsp;</DIV>
  <DIV>TIA</DIV>
  <DIV>-R</DIV>
  <P>
  <HR>

  <P></P>_______________________________________________<BR>pim mailing=20
  list<BR><A href=3D"mailto:pim@ietf.org">pim@ietf.org</A><BR><A=20
  =
href=3D"https://www1.ietf.org/mailman/listinfo/pim">https://www1.ietf.org=
/mailman/listinfo/pim</A><BR></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_0243_01C4D60A.F0F176F0--



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

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

--===============0098899445==--




From pim-bounces@ietf.org  Mon Nov 29 02:06:03 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA11590
	for <pim-archive@lists.ietf.org>; Mon, 29 Nov 2004 02:06:03 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CYfZh-0006s2-2b; Mon, 29 Nov 2004 02:03:53 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CYfWt-0005dY-Th
	for pim@megatron.ietf.org; Mon, 29 Nov 2004 02:00:59 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA07732
	for <pim@ietf.org>; Mon, 29 Nov 2004 02:00:59 -0500 (EST)
Received: from [203.124.166.180] (helo=nevismail01.pune.nevisnetworks.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CYfbj-0001L5-3I
	for pim@ietf.org; Mon, 29 Nov 2004 02:06:01 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [pim] Need help.... on sending prune with S to RP ?
Date: Mon, 29 Nov 2004 12:30:17 +0530
Message-ID: <7F17177AC9AC2F4CB4A1A33C936D038D4CB52E@nevismail01.pune.nevisnetworks.com>
Thread-Topic: [pim] Need help.... on sending prune with S to RP ?
Thread-Index: AcTV2iHnuEvXCPX5SZSJ7G4gVG7YBAABtt7g
From: "Ganapathasaa" <ganapathasaa@nevisnetworks.com>
To: <pim@ietf.org>
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 501044f827b673024f6a4cb1d46e67d2
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="===============0297845614=="
Sender: pim-bounces@ietf.org
Errors-To: pim-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0297845614==
content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C4D5E1.15835080"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C4D5E1.15835080
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

Main intention is not to receive the duplicate traffic(S, G) through the
RP tree when the DR has the source(S) directly connected to it.=20

=20

Regards,

Ganapath

=20

  _____ =20

From: pim-bounces@ietf.org [mailto:pim-bounces@ietf.org] On Behalf Of
Mohamed Riyaz
Sent: Monday, November 29, 2004 11:32 AM
To: pim@ietf.org
Subject: [pim] Need help.... on sending prune with S to RP ?

=20

When local source S starts sending to group G, the RFC says that the DR
sends a j/p message with S in prune list, if a (*,G) or (*,*,RP) entry
is present. What is the intend of this ?.

=20

TIA

-R


------_=_NextPart_001_01C4D5E1.15835080
Content-Type: text/html;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

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

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body bgcolor=3Dwhite lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Main intention is not to receive =
the
duplicate traffic(S, G) through the RP tree when the DR has the =
source(S)
directly connected to it. <o:p></o:p></span></font></p>

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

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

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

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

<div>

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

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

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

<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font =
size=3D2
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'>
pim-bounces@ietf.org [mailto:pim-bounces@ietf.org] <b><span =
style=3D'font-weight:
bold'>On Behalf Of </span></b>Mohamed Riyaz<br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Monday, November =
29, 2004
11:32 AM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> pim@ietf.org<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> [pim] Need =
help.... on
sending prune with S to RP ?</span></font><o:p></o:p></p>

</div>

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

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>When local source S starts sending to group G, the RFC says that =
the DR
sends a j/p message with S in prune list, if a (*,G) or (*,*,RP) entry =
is
present. What is the intend of this ?.<o:p></o:p></span></font></p>

</div>

<div>

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

</div>

<div>

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

</div>

<div>

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

</div>

</div>

</body>

</html>

------_=_NextPart_001_01C4D5E1.15835080--


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

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

--===============0297845614==--



