From mailman-bounces@ietf.org  Wed Dec  1 07:44:23 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA23527
	for <pim-archive@lists.ietf.org>; Wed, 1 Dec 2004 07:44:23 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CZSLi-0001XC-6N
	for pim-archive@lists.ietf.org; Wed, 01 Dec 2004 06:08:42 -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.14745.1101897635.3553.mailman@lists.ietf.org>
Date: Wed, 01 Dec 2004 05:40:35 -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 Dec  6 12:28:47 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA02272
	for <pim-archive@lists.ietf.org>; Mon, 6 Dec 2004 12:28:46 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CbMUG-0002Kc-3g; Mon, 06 Dec 2004 12:17:24 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CbMGa-0006Vv-SR
	for pim@megatron.ietf.org; Mon, 06 Dec 2004 12:03: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 MAA00067
	for <pim@ietf.org>; Mon, 6 Dec 2004 12:03:14 -0500 (EST)
Received: from mail1.telekom.de ([62.225.183.202])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CbMMz-0001Jz-4J
	for pim@ietf.org; Mon, 06 Dec 2004 12:09:53 -0500
Received: from g9jbr.mgb01.telekom.de by G8SBV.dmz.telekom.de with ESMTP for
	pim@ietf.org; Mon, 6 Dec 2004 18:02:43 +0100
Received: by G9JBR.mgb01.telekom.de with Internet Mail Service (5.5.2653.19)
	id <YK83QPDY>; Mon, 6 Dec 2004 18:02:42 +0100
Message-Id: <BCF8A2A01F82504694BCB0CC61C5B1D901006FD4@E9JDG.mgb01.telekom.de>
From: "Leymann, Nicolai" <Nicolai.Leymann@t-systems.com>
To: pim@ietf.org
Subject: Re: [pim] PIM WG meeting notes / PIM-Proxy draft
Date: Mon, 6 Dec 2004 18:02:39 +0100 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
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,

> 3. In the case of the proxy draft, there was not consensus.
> 
What does this mean for the draft and the working group? As far as
I know it was planned (according to the minutes) to discuss the
topic with the chairs. Are there any news about how to proceed?

The draft provides a solution for a BGP free core for Multicast
which is a topic which has to be addressed from my point of view.
Several ISPs are deploying a BGP free core for unicast and want
to keep it BGP free if multicast is enabled in the network.

  best regards

     Nic

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


From pim-bounces@ietf.org  Mon Dec  6 12:54:40 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 MAA04521
	for <pim-archive@lists.ietf.org>; Mon, 6 Dec 2004 12:54:40 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CbN32-0002Fc-TD; Mon, 06 Dec 2004 12:53:20 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CbMwJ-0001J4-Fl
	for pim@megatron.ietf.org; Mon, 06 Dec 2004 12:46: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 MAA03923
	for <pim@ietf.org>; Mon, 6 Dec 2004 12:46:20 -0500 (EST)
Received: from central.switch.ch ([130.59.11.11])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CbN2i-0002Gp-8w
	for pim@ietf.org; Mon, 06 Dec 2004 12:53:00 -0500
Received: from hadron ([130.59.4.84] helo=hadron.switch.ch)
	by central.switch.ch with esmtp (Exim 3.20 #1) id 1CbMvg-0003K1-00
	for pim@ietf.org; Mon, 06 Dec 2004 18:45:44 +0100
Received: from hadron.switch.ch.switch.ch (localhost [IPv6:::1])
	by hadron.switch.ch (8.12.10+Sun/8.12.10) with ESMTP id iB6HjiVd007510
	for <pim@ietf.org>; Mon, 6 Dec 2004 18:45:44 +0100 (CET)
From: Alexander Gall <gall@switch.ch>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <16820.39624.453744.190706@hadron.switch.ch>
Date: Mon, 6 Dec 2004 18:45:44 +0100
To: pim@ietf.org
X-Mailer: VM 7.18 under Emacs 21.3.3
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Content-Transfer-Encoding: 7bit
Subject: [pim] BSR implementation questionnaire
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


In order to determine the requirements for backwards compatibility of
future revisions of draft-ietf-pim-sm-bsr, the current authors would
like to ask the following questions about existing implementations of
the BSR protocol.  Partial information (e.g. vendor only) is also
appreciated.  Feel free to relay this message to anyone who can
provide useful input.

1. Vendor, version

2. Implemented specification (RFC2362/draft-ietf-pim-sm-bsr-xx)

3. Uses RP Holdtime for expiring RP-mappings on non-BSR routers
   (Yes/No)

4. Removes existing RP-mappings if RP is not included in the covering
   group range of the most recent BSM (Yes/No)

5. Removes existing RP-mappings immediately if RP is included with a
   holdtime of 0 in the BSM (Yes/No).  If no, please state briefly
   what action is taken upon reception of such a mapping.

Thanks,

--
Alex


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


From pim-bounces@ietf.org  Mon Dec  6 14:57:00 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA18721
	for <pim-archive@lists.ietf.org>; Mon, 6 Dec 2004 14:57: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 1CbOps-0008Pl-7j; Mon, 06 Dec 2004 14:47:52 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CbOks-0005ab-Iw
	for pim@megatron.ietf.org; Mon, 06 Dec 2004 14:42: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 OAA16884
	for <pim@ietf.org>; Mon, 6 Dec 2004 14:42:41 -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 1CbOrG-0005Wl-E5 for pim@ietf.org; Mon, 06 Dec 2004 14:49:20 -0500
Received: from sj-core-2.cisco.com (171.71.177.254)
	by sj-iport-1.cisco.com with ESMTP; 06 Dec 2004 11:49:24 -0800
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-2.cisco.com (8.12.10/8.12.6) with ESMTP id iB6Jg4IT028487;
	Mon, 6 Dec 2004 11:42:04 -0800 (PST)
Received: from irp-view7.cisco.com (irp-view7.cisco.com [171.70.65.144])
	by mira-sjc5-b.cisco.com (MOS 3.4.5-GR) with ESMTP id AZO53288;
	Mon, 6 Dec 2004 11:50:28 -0800 (PST)
Date: Mon, 6 Dec 2004 11:42:05 -0800 (PST)
From: Mike McBride <mmcbride@cisco.com>
To: "Leymann, Nicolai" <Nicolai.Leymann@t-systems.com>
Subject: Re: [pim] PIM WG meeting notes / PIM-Proxy draft
In-Reply-To: <BCF8A2A01F82504694BCB0CC61C5B1D901006FD4@E9JDG.mgb01.telekom.de>
Message-ID: <Pine.GSO.4.58.0412061108570.22906@irp-view7.cisco.com>
References: <BCF8A2A01F82504694BCB0CC61C5B1D901006FD4@E9JDG.mgb01.telekom.de>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
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

Nic,

> > 3. In the case of the proxy draft, there was not consensus.
> >
> What does this mean for the draft and the working group? As far as
> I know it was planned (according to the minutes) to discuss the
> topic with the chairs. Are there any news about how to proceed?
>
> The draft provides a solution for a BGP free core for Multicast
> which is a topic which has to be addressed from my point of view.
> Several ISPs are deploying a BGP free core for unicast and want
> to keep it BGP free if multicast is enabled in the network.

The authors of the draft have agreed to break out the rpf vector portion
of the existing draft-wijnands-pim-proxy-00 and create a new one. This new
draft will address the bgp free core solution that you and others support.
Those opposed to the draft have indicated they will support the draft as
it will no longer address the VPN services.

As far as the Chairs meeting is concerned, we basically agreed to do much
better at communicating with each other. Drafts that are presented to us
in the pim wg that deal with mpls tree building will be discussed between
the wg chairs to decide how to proceed. Same with pim related drafts
presented to mpls and l3vpn wgs.

The p2mp framework draft, that the mboned wg agreed to work on, should
help to provide us all with more understanding of the multipoint service
components and wg's roles. Additionally, Tom and I have an action to
expand our charter and request review from the pim wg.

mike

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


From pim-bounces@ietf.org  Mon Dec  6 20:22: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 UAA15009
	for <pim-archive@lists.ietf.org>; Mon, 6 Dec 2004 20:22: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 1CbU1l-0000g2-EY; Mon, 06 Dec 2004 20:20:29 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CbU18-0000Ve-MX
	for pim@megatron.ietf.org; Mon, 06 Dec 2004 20:19: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 UAA14869
	for <pim@ietf.org>; Mon, 6 Dec 2004 20:19:49 -0500 (EST)
Received: from kecgate03.infosys.com ([220.227.179.21])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CbU7Q-0004WA-NC
	for pim@ietf.org; Mon, 06 Dec 2004 20:26:31 -0500
Received: from indhubbhs03.ad.infosys.com ([192.168.18.90]) by
	kecgate03.infosys.com with InterScan Messaging Security Suite;
	Tue, 07 Dec 2004 06:43:35 +0530
Received: from BLRKECIMR01.ad.infosys.com ([192.168.200.58]) by
	indhubbhs03.ad.infosys.com with Microsoft SMTPSVC(5.0.2195.6713); 
	Tue, 7 Dec 2004 06:47:46 +0530
Received: from kecmsg06.ad.infosys.com ([192.168.200.75]) by
	BLRKECIMR01.ad.infosys.com with Microsoft SMTPSVC(5.0.2195.6713); 
	Tue, 7 Dec 2004 06:47:46 +0530
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [pim] BSR implementation questionnaire
Date: Tue, 7 Dec 2004 06:47:45 +0530
Message-ID: <56E2573C375A414191118970BDE06A1512887B31@kecmsg06.ad.infosys.com>
Thread-Topic: [pim] BSR implementation questionnaire
Thread-Index: AcTbvH6K/Tpe+BKmTkCU0GQWQZG2PAAPM/Z9
From: "bharat_joshi" <bharat_joshi@infosys.com>
To: "Alexander Gall" <gall@switch.ch>, <pim@ietf.org>
X-OriginalArrivalTime: 07 Dec 2004 01:17:46.0564 (UTC)
	FILETIME=[8F4BE840:01C4DBFA]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
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="===============1768630192=="
Sender: pim-bounces@ietf.org
Errors-To: pim-bounces@ietf.org

--===============1768630192==
content-class: urn:content-classes:message
Content-Type: text/plain;
	charset="UTF-8"
Content-Transfer-Encoding: base64

SGksDQogDQogICAgIFdlIGRpZCBhbiBpbXBsZW1lbnRhdGlvbiBvZiBCU1IgZnVuY3Rpb25hbGl0
eSBzb21lIHRpbWUgYmFjay4gUGxlYXNlIHNlZSBpbiBsaW5lDQpmb3IgbW9yZSBkZXRhaWxzLg0K
IA0KVGhhbmtzICYgUmVnYXJkcywNCkJoYXJhdA0KDQoJLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0t
LS0gDQoJRnJvbTogcGltLWJvdW5jZXNAaWV0Zi5vcmcgb24gYmVoYWxmIG9mIEFsZXhhbmRlciBH
YWxsIA0KCVNlbnQ6IE1vbiAxMi82LzIwMDQgMTE6MTUgUE0gDQoJVG86IHBpbUBpZXRmLm9yZyAN
CglDYzogDQoJU3ViamVjdDogW3BpbV0gQlNSIGltcGxlbWVudGF0aW9uIHF1ZXN0aW9ubmFpcmUN
CgkNCgkNCg0KDQoJSW4gb3JkZXIgdG8gZGV0ZXJtaW5lIHRoZSByZXF1aXJlbWVudHMgZm9yIGJh
Y2t3YXJkcyBjb21wYXRpYmlsaXR5IG9mDQoJZnV0dXJlIHJldmlzaW9ucyBvZiBkcmFmdC1pZXRm
LXBpbS1zbS1ic3IsIHRoZSBjdXJyZW50IGF1dGhvcnMgd291bGQNCglsaWtlIHRvIGFzayB0aGUg
Zm9sbG93aW5nIHF1ZXN0aW9ucyBhYm91dCBleGlzdGluZyBpbXBsZW1lbnRhdGlvbnMgb2YNCgl0
aGUgQlNSIHByb3RvY29sLiAgUGFydGlhbCBpbmZvcm1hdGlvbiAoZS5nLiB2ZW5kb3Igb25seSkg
aXMgYWxzbw0KCWFwcHJlY2lhdGVkLiAgRmVlbCBmcmVlIHRvIHJlbGF5IHRoaXMgbWVzc2FnZSB0
byBhbnlvbmUgd2hvIGNhbg0KCXByb3ZpZGUgdXNlZnVsIGlucHV0Lg0KCQ0KCTEuIFZlbmRvciwg
dmVyc2lvbg0KDQoJPEJoYXJhdD46IFdlLCBJbmZvc3lzIFRlY2hub2xvZ2llcyBMdGQgSW5kaWEs
ICBkaWQgaXQgZm9yIG9uZSBvZiBvdXIgY3VzdG9tZXIuIA0KCQ0KCTIuIEltcGxlbWVudGVkIHNw
ZWNpZmljYXRpb24gKFJGQzIzNjIvZHJhZnQtaWV0Zi1waW0tc20tYnNyLXh4KQ0KDQoJPEJoYXJh
dD46IFRoaXMgaW1wbGVtZW50YXRpb24gaXMgYmFzZWQgb24gZHJhZnQgImRyYWZ0LWlldGYtcGlt
LXNtLWJzci0wMy50eHQiLg0KCQ0KCTMuIFVzZXMgUlAgSG9sZHRpbWUgZm9yIGV4cGlyaW5nIFJQ
LW1hcHBpbmdzIG9uIG5vbi1CU1Igcm91dGVycw0KCSAgIChZZXMvTm8pDQoNCgk8QmhhcmF0Pjog
WWVzLg0KDQoJNC4gUmVtb3ZlcyBleGlzdGluZyBSUC1tYXBwaW5ncyBpZiBSUCBpcyBub3QgaW5j
bHVkZWQgaW4gdGhlIGNvdmVyaW5nDQoJICAgZ3JvdXAgcmFuZ2Ugb2YgdGhlIG1vc3QgcmVjZW50
IEJTTSAoWWVzL05vKQ0KDQoJPEJoYXJhdD46IFllcy4NCgkNCgk1LiBSZW1vdmVzIGV4aXN0aW5n
IFJQLW1hcHBpbmdzIGltbWVkaWF0ZWx5IGlmIFJQIGlzIGluY2x1ZGVkIHdpdGggYQ0KCSAgIGhv
bGR0aW1lIG9mIDAgaW4gdGhlIEJTTSAoWWVzL05vKS4gIElmIG5vLCBwbGVhc2Ugc3RhdGUgYnJp
ZWZseQ0KCSAgIHdoYXQgYWN0aW9uIGlzIHRha2VuIHVwb24gcmVjZXB0aW9uIG9mIHN1Y2ggYSBt
YXBwaW5nLg0KDQoJPEJoYXJhdD46IFllcw0KDQoJDQoJDQoJVGhhbmtzLA0KCQ0KCS0tDQoJQWxl
eA0KCQ0KCQ0KCV9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
DQoJcGltIG1haWxpbmcgbGlzdA0KCXBpbUBpZXRmLm9yZw0KCWh0dHBzOi8vd3d3MS5pZXRmLm9y
Zy9tYWlsbWFuL2xpc3RpbmZvL3BpbSA8aHR0cHM6Ly93d3cxLmlldGYub3JnL21haWxtYW4vbGlz
dGluZm8vcGltPiANCgkNCg0K


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

--===============1768630192==--


From pim-bounces@ietf.org  Mon Dec 13 07:40: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 HAA00738
	for <pim-archive@lists.ietf.org>; Mon, 13 Dec 2004 07:40: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 1CdpPX-00027u-4k; Mon, 13 Dec 2004 07:34:43 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CdpOB-0001hk-AM
	for pim@megatron.ietf.org; Mon, 13 Dec 2004 07:33: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 HAA29720
	for <pim@ietf.org>; Mon, 13 Dec 2004 07:33:18 -0500 (EST)
Received: from mail1.telekom.de ([62.225.183.202])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CdpVz-0003vL-9a
	for pim@ietf.org; Mon, 13 Dec 2004 07:41:23 -0500
Received: from g9jbq.mgb01.telekom.de by G8SBV.dmz.telekom.de with ESMTP for
	pim@ietf.org; Mon, 13 Dec 2004 13:32:42 +0100
Received: by G9JBQ.mgb01.telekom.de with Internet Mail Service (5.5.2653.19)
	id <YZK05KN1>; Mon, 13 Dec 2004 13:32:42 +0100
Message-Id: <BCF8A2A01F82504694BCB0CC61C5B1D901006FF1@E9JDG.mgb01.telekom.de>
From: "Leymann, Nicolai" <Nicolai.Leymann@t-systems.com>
To: pim@ietf.org
Date: Mon, 13 Dec 2004 13:32:40 +0100
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: 798b2e660f1819ae38035ac1d8d5e3ab
Subject: [pim] PIM Scalability / PIM-Neighbors in mVPN 
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,

With the growing interest in mVPN solutions the scalability of
PIM becomes more and more important. Two main topics were al-
ready mentioned on the PIM maling list: PIM Hello messages and
PIM refresh reduction.

>From todays point of view, are the any informations available
about the current state of scalability?  How many PIM neigbors
can be handled today without any negative impact on the network
and where are the practical limitations? 

  best regards

     Nic

--
Nicolai Leymann                          EMail: nicolai.leymann@t-systems.com                    
T-Systems System Integration, Berlin     Tel/Fax: ++49-30-3497-3570/-3571
Abteilung ET52                           Mobil: ++49-170-2275345
Senior Experte IP-Technologien           Goslarer Ufer 35, 10589 Berlin, Germany


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


From pim-bounces@ietf.org  Tue Dec 14 07:04:19 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA17066
	for <pim-archive@lists.ietf.org>; Tue, 14 Dec 2004 07:04:19 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CeBJL-0006W7-Fa; Tue, 14 Dec 2004 06: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 1CeBHc-0006JY-TM
	for pim@megatron.ietf.org; Tue, 14 Dec 2004 06:56: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 GAA16312
	for <pim@ietf.org>; Tue, 14 Dec 2004 06:55:58 -0500 (EST)
Received: from filter4.kt.co.kr ([147.6.45.68])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CeBPR-0005j2-Oz
	for pim@ietf.org; Tue, 14 Dec 2004 07:04:17 -0500
Received: from external ([147.6.70.104]) by filter4 (1.0) id iBEBvWQ00BF7;
	Tue, 14 Dec 2004 20:57:32 +0900
X-SMF-UNIQ33B8657C0E4123ECDBACEB8E52847943: iBEBvWQ00BF7
Message-ID: <41BED49C.6020708@kt.co.kr>
Date: Tue, 14 Dec 2004 20:55:08 +0900
From: Ji-Eon KIM <jekim@kt.co.kr>
User-Agent: Mozilla Thunderbird 0.7.3 (Windows/20040803)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: pim@ietf.org
Subject: [pim]group-to-rp mapping : static RP vs. BSR
Content-Type: text/plain; charset=EUC-KR
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id GAA16312
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

Hi! My name is Ji-Eon Kim from KT.

In draft-ietf-pim-sm-v2-new-11.txt, follwoing group-to-rp mapping
algorithm is sugested

1 Perform longest match on group-range to obtain a list of RPs.
2 From this list of matching RPs, find the one with highest priority.
Eliminate any RPs from the list that have lower priorities.
3 If only one RP remains in the list, use that RP.
4 If multiple RPs are in the list, use the PIM hash function to
choose one.

But, if we configure static RP address and receive C-RP addresses from
BSR for same group address with same mask length, which address does the
router select as RP?
For example, Router A has static RP information, RP address 10.1.1.1 for
group 238.1.1.0/24
and has C-RP information from BSR, RP address 10.0.0.1 for group
238.1.1.0/24.
In this case, which RP address will be selected?

With above algothrithm, some router select 10.1.1.1 as RP address and
other routers select 10.0.0.1, even if static RP and BSR RP have same
priority value.
In current state, some vender select RP from BSR, some vender select
Static RP and som vender uses hash function with static RP and RP from
BSR..

So, I think router sould have administrative distance(priority) about
the way the router gets RP address.
This is the similar case as routing protocol. Each router has the
administrative distnace for each routing protocol.





--=20
Ji-Eon Kim  =B1=E8 =C1=F6 =BE=F0
Backbone Network Architecture Division
Telecommunication Network Laboratory
KT Corporation

463-1 Jeonmin-dong, Yuseong-gu, Daejeon 305-811, KOREA
Direct: +82-42-870-8334
Fax: +82-42-870-8339
e-mail: jekim@kt.co.kr
=20


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


From pim-bounces@ietf.org  Tue Dec 14 14:58:47 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10976
	for <pim-archive@lists.ietf.org>; Tue, 14 Dec 2004 14:58:47 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CeImj-0006Qr-6R; Tue, 14 Dec 2004 14:56:37 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CeIkz-0006Ev-Q7
	for pim@megatron.ietf.org; Tue, 14 Dec 2004 14:54: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 OAA10503
	for <pim@ietf.org>; Tue, 14 Dec 2004 14:54:48 -0500 (EST)
Received: from sj-iport-4.cisco.com ([171.68.10.86])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CeIt2-00040f-5z
	for pim@ietf.org; Tue, 14 Dec 2004 15:03:10 -0500
Received: from sj-core-4.cisco.com (171.68.223.138)
	by sj-iport-4.cisco.com with ESMTP; 14 Dec 2004 11:54:19 -0800
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
Received: from cisco.com (cypher.cisco.com [171.69.11.142])
	by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id iBEJsCA4005035;
	Tue, 14 Dec 2004 11:54:12 -0800 (PST)
Received: (from eckert@localhost)
	by cisco.com (8.8.8-Cisco List Logging/8.8.8) id LAA27598;
	Tue, 14 Dec 2004 11:54:12 -0800 (PST)
Date: Tue, 14 Dec 2004 11:54:12 -0800
From: Toerless Eckert <eckert@cisco.com>
To: Ji-Eon KIM <jekim@kt.co.kr>
Subject: Re: [pim]group-to-rp mapping : static RP vs. BSR
Message-ID: <20041214195412.GP4963@cisco.com>
References: <41BED49C.6020708@kt.co.kr>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <41BED49C.6020708@kt.co.kr>
User-Agent: Mutt/1.4i
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0fa76816851382eb71b0a882ccdc29ac
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

On Tue, Dec 14, 2004 at 08:55:08PM +0900, Ji-Eon KIM wrote:
> Hi! My name is Ji-Eon Kim from KT.
> 
> In draft-ietf-pim-sm-v2-new-11.txt, follwoing group-to-rp mapping
> algorithm is sugested
> 
> 1 Perform longest match on group-range to obtain a list of RPs.
> 2 From this list of matching RPs, find the one with highest priority.
> Eliminate any RPs from the list that have lower priorities.
> 3 If only one RP remains in the list, use that RP.
> 4 If multiple RPs are in the list, use the PIM hash function to
> choose one.
> 
> But, if we configure static RP address and receive C-RP addresses from
> BSR for same group address with same mask length, which address does the
> router select as RP?
> For example, Router A has static RP information, RP address 10.1.1.1 for
> group 238.1.1.0/24
> and has C-RP information from BSR, RP address 10.0.0.1 for group
> 238.1.1.0/24.
> In this case, which RP address will be selected?

Yes, the PIM spec is pretty sneakish here, just talking about priorities
from different sources of information (AutoRP, BSR, static, EmbeddedRP, ...)
and leaving out the piece as to how priorities should be compared.

> With above algothrithm, some router select 10.1.1.1 as RP address and
> other routers select 10.0.0.1, even if static RP and BSR RP have same
> priority value.
> In current state, some vender select RP from BSR, some vender select
> Static RP and som vender uses hash function with static RP and RP from
> BSR..
> 
> So, I think router sould have administrative distance(priority) about
> the way the router gets RP address.
> This is the similar case as routing protocol. Each router has the
> administrative distnace for each routing protocol.

The more fundamental problem is that there is no IETF architecture for 
IP multicast group-range mode selection, where mode includes choice
of tree building protocol to use, choice of protocol parameters (eg: RP)
and choice of service mode (ASM or SSM). This is a problem that is outside
the scope of the PIM-SM spec. Because there is no other draft/rfc
for that, the PIM-SM spec took it upon itself to include as much about this
problem as the authors felt was appropriate. The wording used now does
definitely allow for a distance based implementation (it's just a matter
of constructing the "priority" mentioned), but it is of course completely
non-obvious.

I agree that a prefix-length->distance->priority based architecture
is what we need, but i would be careful demanding the flexibility unicast
has because there are too many differences: non-aggregation, non-interdomain
group mapping protocols, RP selection consistency requirements, total
number of prefixes to map, etc.,....

Cisco IOS for example has a mostly fixed distance based architecture,
and it may well satisfy deployment requirement better than a more
flexible (freely reconfigurable distance) approach because of the simplicity
in design and consistency in behavior of routers it enforces.

Given that interdomain RP mapping (except for Embedded-RP) is outside
the scope, intradomain problems (between routers from different vendors) can
typically well be solved by simple best current practices like using only
non-overlapping prefixes such as 239.x/16. All this of course is only
necessary if you can not simply use a single protocol across your domain,
and then my first question is always "why not a single protocol".

If you want to raise this issue further, i would recommend to have this
done in mboned instead of pim: write a problem statement explaining
specific cases where you think there is current underspecification of
cross-vendor interoperability. If the cases are persuasive enough that
they can not be argued away with for example the BCP from the last 
paragraph, then that should lead to the recognized need to improve on
this architectural piece. 

Cheers
	Toerless

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


