From mailman-admin@ietf.org  Sat May  1 10:17:53 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA18836
	for <pim-archive@lists.ietf.org>; Sat, 1 May 2004 10:17:53 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJuFb-0006zg-Ts
	for pim-archive@lists.ietf.org; Sat, 01 May 2004 09:09:51 -0400
Date: Sat, 01 May 2004 09:09:51 -0400
Message-ID: <20040501130951.27207.68926.Mailman@www1.ietf.org>
Subject: ietf.org mailing list memberships reminder
From: mailman-owner@www1.ietf.org
To: pim-archive@ietf.org
X-No-Archive: yes
X-Ack: no
Sender: mailman-admin@ietf.org
Errors-To: mailman-admin@ietf.org
X-BeenThere: mailman@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk

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, pim-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

All statements related to the activities of the IETF and addressed to
the IETF are subject to all provisions of Section 10 of RFC 2026,
which grants to the IETF and its participants certain licenses and
rights in such statements. Such statements include verbal statements
in IETF meetings, as well as written and electronic communications
made at any time or place, which are addressed to

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

Statements made outside of an IETF meeting, mailing list or other
function, that are clearly not intended to be input to an IETF
activity, group or function, are not subject to these provisions.

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


If you have questions, problems, comments, etc, send them to
mailman-owner@www1.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-admin@ietf.org  Tue May  4 02:09:34 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA06696
	for <pim-archive@lists.ietf.org>; Tue, 4 May 2004 02:09:34 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BKt45-0000wx-EU; Tue, 04 May 2004 02:06:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BKt2S-0008UA-VE
	for pim@optimus.ietf.org; Tue, 04 May 2004 02:04:20 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA01598
	for <pim@ietf.org>; Tue, 4 May 2004 02:04:18 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BKt2P-0007Rt-BG
	for pim@ietf.org; Tue, 04 May 2004 02:04:17 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BKt1S-0007Is-00
	for pim@ietf.org; Tue, 04 May 2004 02:03:19 -0400
Received: from netcore.fi ([193.94.160.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BKt0m-00071G-00
	for pim@ietf.org; Tue, 04 May 2004 02:02:36 -0400
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id i44625o29204
	for <pim@ietf.org>; Tue, 4 May 2004 09:02:05 +0300
Date: Tue, 4 May 2004 09:02:05 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: pim@ietf.org
Message-ID: <Pine.LNX.4.44.0405040901150.29174-100000@netcore.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Subject: [pim] mboned: WGLC on draft-ietf-mboned-mroutesec-00.txt (fwd)
Sender: pim-admin@ietf.org
Errors-To: pim-admin@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Id: Protocol Independent Multicast <pim.ietf.org>
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>

FYI --

As this is WGLC'd for Informational, this is about the last chance to 
comment!

And as a co-author, I dare to say it still needs a lot of commenting 
:-)

Please provide feedback!

---------- Forwarded message ----------
Date: Wed, 28 Apr 2004 06:45:49 -0700
From: David Meyer <dmm@1-4-5.net>
To: mboned@lists.uoregon.edu
Subject: mboned: WGLC on draft-ietf-mboned-mroutesec-00.txt

	Folks

	This note starts the WG Last Call for comments on
	draft-ietf-mboned-mroutesec-00.txt, "PIM-SM Multicast
	Routing Security Issues and Enhancements". It can be
	found on 
	
	ftp://ftp.ietf.org/internet-drafts/draft-ietf-mboned-mroutesec-00.txt

	Please review the document carefully, and send your
	feedback to the list.  Please also indicate whether or
	not you believe that this document is ready to go to the
	IESG. 

	This Last Call will end on 12 May 2004 at 1500 PDT (UTC/GMT-7).

	Thanks,

	Dave








_______________________________________________________________
user interface: http://darkwing.uoregon.edu/~llynch/mboned.html
web archive:  http://darkwing.uoregon.edu/~llynch/mboned/


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


From exim@www1.ietf.org  Tue May  4 02:15:13 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA10402
	for <pim-archive@odin.ietf.org>; Tue, 4 May 2004 02:15:13 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BKt9B-0003t9-NF
	for pim-archive@odin.ietf.org; Tue, 04 May 2004 02:11:17 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i446BHuZ014946
	for pim-archive@odin.ietf.org; Tue, 4 May 2004 02:11:17 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BKt8M-0003UD-G0
	for pim-web-archive@optimus.ietf.org; Tue, 04 May 2004 02:10:26 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA07539
	for <pim-web-archive@ietf.org>; Tue, 4 May 2004 02:10:23 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BKt8I-0000Zs-R9
	for pim-web-archive@ietf.org; Tue, 04 May 2004 02:10:22 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BKt7L-0000Qn-00
	for pim-web-archive@ietf.org; Tue, 04 May 2004 02:09:23 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BKt71-0000HO-00
	for pim-web-archive@ietf.org; Tue, 04 May 2004 02:09:03 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BKt45-0000wx-EU; Tue, 04 May 2004 02:06:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BKt2S-0008UA-VE
	for pim@optimus.ietf.org; Tue, 04 May 2004 02:04:20 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA01598
	for <pim@ietf.org>; Tue, 4 May 2004 02:04:18 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BKt2P-0007Rt-BG
	for pim@ietf.org; Tue, 04 May 2004 02:04:17 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BKt1S-0007Is-00
	for pim@ietf.org; Tue, 04 May 2004 02:03:19 -0400
Received: from netcore.fi ([193.94.160.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BKt0m-00071G-00
	for pim@ietf.org; Tue, 04 May 2004 02:02:36 -0400
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id i44625o29204
	for <pim@ietf.org>; Tue, 4 May 2004 09:02:05 +0300
Date: Tue, 4 May 2004 09:02:05 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: pim@ietf.org
Message-ID: <Pine.LNX.4.44.0405040901150.29174-100000@netcore.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [pim] mboned: WGLC on draft-ietf-mboned-mroutesec-00.txt (fwd)
Sender: pim-admin@ietf.org
Errors-To: pim-admin@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Id: Protocol Independent Multicast <pim.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60

FYI --

As this is WGLC'd for Informational, this is about the last chance to 
comment!

And as a co-author, I dare to say it still needs a lot of commenting 
:-)

Please provide feedback!

---------- Forwarded message ----------
Date: Wed, 28 Apr 2004 06:45:49 -0700
From: David Meyer <dmm@1-4-5.net>
To: mboned@lists.uoregon.edu
Subject: mboned: WGLC on draft-ietf-mboned-mroutesec-00.txt

	Folks

	This note starts the WG Last Call for comments on
	draft-ietf-mboned-mroutesec-00.txt, "PIM-SM Multicast
	Routing Security Issues and Enhancements". It can be
	found on 
	
	ftp://ftp.ietf.org/internet-drafts/draft-ietf-mboned-mroutesec-00.txt

	Please review the document carefully, and send your
	feedback to the list.  Please also indicate whether or
	not you believe that this document is ready to go to the
	IESG. 

	This Last Call will end on 12 May 2004 at 1500 PDT (UTC/GMT-7).

	Thanks,

	Dave








_______________________________________________________________
user interface: http://darkwing.uoregon.edu/~llynch/mboned.html
web archive:  http://darkwing.uoregon.edu/~llynch/mboned/


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



From pim-admin@ietf.org  Mon May 10 18:39:32 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA13173
	for <pim-archive@lists.ietf.org>; Mon, 10 May 2004 18:39:32 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNJIa-0004Dz-Lm; Mon, 10 May 2004 18:31:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BMoPB-0001Iz-HT
	for pim@optimus.ietf.org; Sun, 09 May 2004 09:31:45 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA03503
	for <pim@ietf.org>; Sun, 9 May 2004 09:31:43 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BMoP9-0004fC-Qs
	for pim@ietf.org; Sun, 09 May 2004 09:31:43 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BMoOH-0004LB-00
	for pim@ietf.org; Sun, 09 May 2004 09:30:49 -0400
Received: from smtp10.wanadoo.fr ([193.252.22.21] helo=mwinf1002.wanadoo.fr)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BMoNS-0003hL-00
	for pim@ietf.org; Sun, 09 May 2004 09:29:58 -0400
Received: from scanpc (ARennes-303-1-20-101.w81-51.abo.wanadoo.fr [81.51.125.101])
	by mwinf1002.wanadoo.fr (SMTP Server) with SMTP id 3EE791C00047
	for <pim@ietf.org>; Sun,  9 May 2004 15:29:27 +0200 (CEST)
Message-ID: <004b01c435d7$d1494fe0$a900a8c0@scanpc>
From: =?iso-8859-1?Q?Famille_B=E9asse?= <beasse.pordic@wanadoo.fr>
To: <pim@ietf.org>
Date: Sun, 9 May 2004 17:10:49 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
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-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id JAA03504
Subject: [pim] Very simple pimd multicast configuration
Sender: pim-admin@ietf.org
Errors-To: pim-admin@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Id: Protocol Independent Multicast <pim.ietf.org>
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-Transfer-Encoding: quoted-printable

Hi,

Can someone can help-me to make a very simple multicast configuration.

Here is my test configuration  (With just one Router):

Server ----------------Multicast Router ----------------------Client
[192.168.1.1        192.168.1.250]   [192.168.0.250         192.168.0.1]

Netmask is 255.255.255.0
/proc/sys/net/ipv4/ip_forward is set to1
Router is Linux Fedora Core 1 With Pimd-2.1.0-alpha29-18
IP_Multicast PIM-SM etc is activate by default in kernel.

My router is ok for unicast. I can communicate from server to client.

But When i want to make Multicast from Server to Client, traffic is not
forward by the router.When i do a "ping -t 5 224.0.0.1" on Linux Client,
packets are not forwards to Linux Server and vice-versa.

What tools can i use to see if configuration is OK ?
What's about pimd.conf configuration file ?

When i do a "ip mroute show" there is nothing to see is it normal ?

Do you have any idea.
Thanks for your help.

Best regards

Christophe B=E9asse
France




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


From exim@www1.ietf.org  Mon May 10 18:59:14 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA14802
	for <pim-archive@odin.ietf.org>; Mon, 10 May 2004 18:59:14 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNJfV-0001KX-Fx
	for pim-archive@odin.ietf.org; Mon, 10 May 2004 18:54:42 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4AMsfAA005114
	for pim-archive@odin.ietf.org; Mon, 10 May 2004 18:54:41 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNJSS-0007Ap-3P
	for pim-web-archive@optimus.ietf.org; Mon, 10 May 2004 18:41:12 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA13375
	for <pim-web-archive@ietf.org>; Mon, 10 May 2004 18:41:07 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BNJSP-0000bj-4K
	for pim-web-archive@ietf.org; Mon, 10 May 2004 18:41:09 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNJRN-0000Dk-00
	for pim-web-archive@ietf.org; Mon, 10 May 2004 18:40:06 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNJQO-0007Zt-00
	for pim-web-archive@ietf.org; Mon, 10 May 2004 18:39:04 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNJIa-0004Dz-Lm; Mon, 10 May 2004 18:31:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BMoPB-0001Iz-HT
	for pim@optimus.ietf.org; Sun, 09 May 2004 09:31:45 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA03503
	for <pim@ietf.org>; Sun, 9 May 2004 09:31:43 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BMoP9-0004fC-Qs
	for pim@ietf.org; Sun, 09 May 2004 09:31:43 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BMoOH-0004LB-00
	for pim@ietf.org; Sun, 09 May 2004 09:30:49 -0400
Received: from smtp10.wanadoo.fr ([193.252.22.21] helo=mwinf1002.wanadoo.fr)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BMoNS-0003hL-00
	for pim@ietf.org; Sun, 09 May 2004 09:29:58 -0400
Received: from scanpc (ARennes-303-1-20-101.w81-51.abo.wanadoo.fr [81.51.125.101])
	by mwinf1002.wanadoo.fr (SMTP Server) with SMTP id 3EE791C00047
	for <pim@ietf.org>; Sun,  9 May 2004 15:29:27 +0200 (CEST)
Message-ID: <004b01c435d7$d1494fe0$a900a8c0@scanpc>
From: =?iso-8859-1?Q?Famille_B=E9asse?= <beasse.pordic@wanadoo.fr>
To: <pim@ietf.org>
Date: Sun, 9 May 2004 17:10:49 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
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
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id JAA03504
Subject: [pim] Very simple pimd multicast configuration
Sender: pim-admin@ietf.org
Errors-To: pim-admin@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Id: Protocol Independent Multicast <pim.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Hi,

Can someone can help-me to make a very simple multicast configuration.

Here is my test configuration  (With just one Router):

Server ----------------Multicast Router ----------------------Client
[192.168.1.1        192.168.1.250]   [192.168.0.250         192.168.0.1]

Netmask is 255.255.255.0
/proc/sys/net/ipv4/ip_forward is set to1
Router is Linux Fedora Core 1 With Pimd-2.1.0-alpha29-18
IP_Multicast PIM-SM etc is activate by default in kernel.

My router is ok for unicast. I can communicate from server to client.

But When i want to make Multicast from Server to Client, traffic is not
forward by the router.When i do a "ping -t 5 224.0.0.1" on Linux Client,
packets are not forwards to Linux Server and vice-versa.

What tools can i use to see if configuration is OK ?
What's about pimd.conf configuration file ?

When i do a "ip mroute show" there is nothing to see is it normal ?

Do you have any idea.
Thanks for your help.

Best regards

Christophe B=E9asse
France




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



From pim-admin@ietf.org  Mon May 10 22:06:57 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA23354
	for <pim-archive@lists.ietf.org>; Mon, 10 May 2004 22:06:57 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNMV2-00053x-4N; Mon, 10 May 2004 21:56:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNMTQ-0004bD-Be
	for pim@optimus.ietf.org; Mon, 10 May 2004 21:54:24 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA22049
	for <pim@ietf.org>; Mon, 10 May 2004 21:54:20 -0400 (EDT)
From: paras@juniper.net
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BNMTN-0004C0-EH
	for pim@ietf.org; Mon, 10 May 2004 21:54:21 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNMSP-0003qz-00
	for pim@ietf.org; Mon, 10 May 2004 21:53:22 -0400
Received: from natint2.juniper.net ([207.17.136.150] helo=garnet.juniper.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNMRW-0003DK-00
	for pim@ietf.org; Mon, 10 May 2004 21:52:26 -0400
Received: from garnet.juniper.net (localhost [127.0.0.1])
	by garnet.juniper.net (8.12.8p1/8.12.3) with ESMTP id i4B1pudp078781;
	Mon, 10 May 2004 18:51:56 -0700 (PDT)
	(envelope-from paras@garnet.juniper.net)
Received: (from paras@localhost)
	by garnet.juniper.net (8.12.8p1/8.12.3/Submit) id i4B1pukP078779;
	Mon, 10 May 2004 18:51:56 -0700 (PDT)
Message-Id: <200405110151.i4B1pukP078779@garnet.juniper.net>
Subject: Re: [pim] Very simple pimd multicast configuration
To: beasse.pordic@wanadoo.fr (=?iso-8859-1?Q?Famille_B=E9asse?=)
Date: Mon, 10 May 2004 18:51:56 -0700 (PDT)
Cc: pim@ietf.org
In-Reply-To: <004b01c435d7$d1494fe0$a900a8c0@scanpc> from "=?iso-8859-1?Q?Famille_B=E9asse?=" at May 09, 2004 05:10:49 PM
MIME-Version: 1.0
Content-Type: text/plain; charset=DISPLAY
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by garnet.juniper.net id i4B1pudp078781
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=NO_REAL_NAME autolearn=no 
	version=2.60
Content-Transfer-Encoding: quoted-printable
Sender: pim-admin@ietf.org
Errors-To: pim-admin@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Id: Protocol Independent Multicast <pim.ietf.org>
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-Transfer-Encoding: quoted-printable


First of all, you're using group addr 224.0.0.1 for testing.
It is a very special group, which, along with all of 224.0.0.0/24=20
will not be forwarded by any multicast router.=20
It's reserved for link-local multicast,=20
for protocol hellos and such, that are to be sent with TTL=3D1.=20

However, I can't tell what else is wrong, if you're using other
valid multicast data groups too. At least, the first thought is
to point out the invalid group usage above.

- Paras.

>=20
> Hi,
>=20
> Can someone can help-me to make a very simple multicast configuration.
>=20
> Here is my test configuration  (With just one Router):
>=20
> Server ----------------Multicast Router ----------------------Client
> [192.168.1.1        192.168.1.250]   [192.168.0.250         192.168.0.1=
]
>=20
> Netmask is 255.255.255.0
> /proc/sys/net/ipv4/ip_forward is set to1
> Router is Linux Fedora Core 1 With Pimd-2.1.0-alpha29-18
> IP_Multicast PIM-SM etc is activate by default in kernel.
>=20
> My router is ok for unicast. I can communicate from server to client.
>=20
> But When i want to make Multicast from Server to Client, traffic is not
> forward by the router.When i do a "ping -t 5 224.0.0.1" on Linux Client=
,
> packets are not forwards to Linux Server and vice-versa.
>=20
> What tools can i use to see if configuration is OK ?
> What's about pimd.conf configuration file ?
>=20
> When i do a "ip mroute show" there is nothing to see is it normal ?
>=20
> Do you have any idea.
> Thanks for your help.
>=20
> Best regards
>=20
> Christophe B=E9asse
> France
>=20
>=20
>=20
>=20
> _______________________________________________
> pim mailing list
> pim@ietf.org
> https://www1.ietf.org/mailman/listinfo/pim
>=20


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


From exim@www1.ietf.org  Mon May 10 22:16:15 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA23809
	for <pim-archive@odin.ietf.org>; Mon, 10 May 2004 22:16:15 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNMkd-0000H5-M0
	for pim-archive@odin.ietf.org; Mon, 10 May 2004 22:12:12 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4B2CB5v001051
	for pim-archive@odin.ietf.org; Mon, 10 May 2004 22:12:11 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNMh0-0007bx-SR
	for pim-web-archive@optimus.ietf.org; Mon, 10 May 2004 22:08:26 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA23402
	for <pim-web-archive@ietf.org>; Mon, 10 May 2004 22:08:22 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BNMgx-0001mB-Rd
	for pim-web-archive@ietf.org; Mon, 10 May 2004 22:08:23 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNMg3-0001RV-00
	for pim-web-archive@ietf.org; Mon, 10 May 2004 22:07:28 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNMf6-00017N-00
	for pim-web-archive@ietf.org; Mon, 10 May 2004 22:06:28 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNMV2-00053x-4N; Mon, 10 May 2004 21:56:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNMTQ-0004bD-Be
	for pim@optimus.ietf.org; Mon, 10 May 2004 21:54:24 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA22049
	for <pim@ietf.org>; Mon, 10 May 2004 21:54:20 -0400 (EDT)
From: paras@juniper.net
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BNMTN-0004C0-EH
	for pim@ietf.org; Mon, 10 May 2004 21:54:21 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNMSP-0003qz-00
	for pim@ietf.org; Mon, 10 May 2004 21:53:22 -0400
Received: from natint2.juniper.net ([207.17.136.150] helo=garnet.juniper.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNMRW-0003DK-00
	for pim@ietf.org; Mon, 10 May 2004 21:52:26 -0400
Received: from garnet.juniper.net (localhost [127.0.0.1])
	by garnet.juniper.net (8.12.8p1/8.12.3) with ESMTP id i4B1pudp078781;
	Mon, 10 May 2004 18:51:56 -0700 (PDT)
	(envelope-from paras@garnet.juniper.net)
Received: (from paras@localhost)
	by garnet.juniper.net (8.12.8p1/8.12.3/Submit) id i4B1pukP078779;
	Mon, 10 May 2004 18:51:56 -0700 (PDT)
Message-Id: <200405110151.i4B1pukP078779@garnet.juniper.net>
Subject: Re: [pim] Very simple pimd multicast configuration
To: beasse.pordic@wanadoo.fr (=?iso-8859-1?Q?Famille_B=E9asse?=)
Date: Mon, 10 May 2004 18:51:56 -0700 (PDT)
Cc: pim@ietf.org
In-Reply-To: <004b01c435d7$d1494fe0$a900a8c0@scanpc> from "=?iso-8859-1?Q?Famille_B=E9asse?=" at May 09, 2004 05:10:49 PM
MIME-Version: 1.0
Content-Type: text/plain; charset=DISPLAY
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by garnet.juniper.net id i4B1pudp078781
Content-Transfer-Encoding: quoted-printable
Sender: pim-admin@ietf.org
Errors-To: pim-admin@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Id: Protocol Independent Multicast <pim.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=NO_REAL_NAME autolearn=no 
	version=2.60
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable


First of all, you're using group addr 224.0.0.1 for testing.
It is a very special group, which, along with all of 224.0.0.0/24=20
will not be forwarded by any multicast router.=20
It's reserved for link-local multicast,=20
for protocol hellos and such, that are to be sent with TTL=3D1.=20

However, I can't tell what else is wrong, if you're using other
valid multicast data groups too. At least, the first thought is
to point out the invalid group usage above.

- Paras.

>=20
> Hi,
>=20
> Can someone can help-me to make a very simple multicast configuration.
>=20
> Here is my test configuration  (With just one Router):
>=20
> Server ----------------Multicast Router ----------------------Client
> [192.168.1.1        192.168.1.250]   [192.168.0.250         192.168.0.1=
]
>=20
> Netmask is 255.255.255.0
> /proc/sys/net/ipv4/ip_forward is set to1
> Router is Linux Fedora Core 1 With Pimd-2.1.0-alpha29-18
> IP_Multicast PIM-SM etc is activate by default in kernel.
>=20
> My router is ok for unicast. I can communicate from server to client.
>=20
> But When i want to make Multicast from Server to Client, traffic is not
> forward by the router.When i do a "ping -t 5 224.0.0.1" on Linux Client=
,
> packets are not forwards to Linux Server and vice-versa.
>=20
> What tools can i use to see if configuration is OK ?
> What's about pimd.conf configuration file ?
>=20
> When i do a "ip mroute show" there is nothing to see is it normal ?
>=20
> Do you have any idea.
> Thanks for your help.
>=20
> Best regards
>=20
> Christophe B=E9asse
> France
>=20
>=20
>=20
>=20
> _______________________________________________
> pim mailing list
> pim@ietf.org
> https://www1.ietf.org/mailman/listinfo/pim
>=20


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



From pim-admin@ietf.org  Tue May 11 00:23:59 2004
Received: from optimus.ietf.org (www.iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA00152
	for <pim-archive@lists.ietf.org>; Tue, 11 May 2004 00:23:59 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNOch-0006h8-MS; Tue, 11 May 2004 00:12:07 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNOZA-00055R-3u
	for pim@optimus.ietf.org; Tue, 11 May 2004 00:08:28 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA29713
	for <pim@ietf.org>; Tue, 11 May 2004 00:08:23 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BNOZ7-0004xd-1i
	for pim@ietf.org; Tue, 11 May 2004 00:08:25 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNOYH-0004dC-00
	for pim@ietf.org; Tue, 11 May 2004 00:07:34 -0400
Received: from mta2.huawei.com ([61.144.161.24] helo=huawei.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNOXe-0004Db-00
	for pim@ietf.org; Tue, 11 May 2004 00:07:05 -0400
Received: from huawei.com (localhost [127.0.0.1])
 by mta2.huawei.com (iPlanet Messaging Server 5.2 HotFix 0.7 (built Jun 26
 2002)) with ESMTP id <0HXJ00H727GOU0@mta2.huawei.com> for pim@ietf.org; Tue,
 11 May 2004 12:07:36 +0800 (CST)
Received: from mailin.huawei.com ([10.18.1.252])
 by mta2.huawei.com (iPlanet Messaging Server 5.2 HotFix 0.7 (built Jun 26
 2002)) with ESMTP id <0HXJ00JM87GN3Y@mta2.huawei.com> for pim@ietf.org; Tue,
 11 May 2004 12:07:35 +0800 (CST)
Received: from DELL15 ([10.18.4.137])
 by mailin.huawei.com (Netscape Messaging Server 4.15)
 with ESMTP id HXJ7MG01.007; Tue, 11 May 2004 12:11:04 +0800
Date: Tue, 11 May 2004 09:44:07 +0530
From: Prashant Jhingran <prashantj@huawei.com>
Subject: RE: [pim] Very simple pimd multicast configuration
In-reply-to: <200405110151.i4B1pukP078779@garnet.juniper.net>
To: paras@juniper.net, beasse.pordic@wanadoo.fr
Cc: pim@ietf.org
Reply-to: prashantj@huawei.com
Message-id: <004101c4370e$680367e0$0701010b@DELL15>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
Content-type: text/plain; charset=gb2312
Content-transfer-encoding: QUOTED-PRINTABLE
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: QUOTED-PRINTABLE
Sender: pim-admin@ietf.org
Errors-To: pim-admin@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Id: Protocol Independent Multicast <pim.ietf.org>
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-Transfer-Encoding: QUOTED-PRINTABLE

hi,
    Also not very sure how Ping can work with a multicast address , b=
ecause
multicast fwd entries will be created only on request in case of PIM-=
SM.
You may however try a utility called "mping" instead of normal "ping"=
.

regards,
Prashant

-----Original Message-----
=46rom: pim-admin@ietf.org [mailto:pim-admin@ietf.org]On Behalf Of
paras@juniper.net
Sent: Tuesday, May 11, 2004 7:22 AM
To: Famille B=E9asse .huawei.com
Cc: pim@ietf.org
Subject: Re: [pim] Very simple pimd multicast configuration



First of all, you're using group addr 224.0.0.1 for testing.
It is a very special group, which, along with all of 224.0.0.0/24
will not be forwarded by any multicast router.
It's reserved for link-local multicast,
for protocol hellos and such, that are to be sent with TTL=3D1.

However, I can't tell what else is wrong, if you're using other
valid multicast data groups too. At least, the first thought is
to point out the invalid group usage above.

- Paras.

>
> Hi,
>
> Can someone can help-me to make a very simple multicast configurati=
on.
>
> Here is my test configuration  (With just one Router):
>
> Server ----------------Multicast Router ----------------------Clien=
t
> [192.168.1.1        192.168.1.250]   [192.168.0.250         192.168=
.0.1]
>
> Netmask is 255.255.255.0
> /proc/sys/net/ipv4/ip_forward is set to1
> Router is Linux Fedora Core 1 With Pimd-2.1.0-alpha29-18
> IP_Multicast PIM-SM etc is activate by default in kernel.
>
> My router is ok for unicast. I can communicate from server to clien=
t.
>
> But When i want to make Multicast from Server to Client, traffic is=
 not
> forward by the router.When i do a "ping -t 5 224.0.0.1" on Linux Cl=
ient,
> packets are not forwards to Linux Server and vice-versa.
>
> What tools can i use to see if configuration is OK ?
> What's about pimd.conf configuration file ?
>
> When i do a "ip mroute show" there is nothing to see is it normal ?
>
> Do you have any idea.
> Thanks for your help.
>
> Best regards
>
> Christophe B=E9asse
> France
>
>
>
>
> _______________________________________________
> 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 exim@www1.ietf.org  Tue May 11 00:30:52 2004
Received: from optimus.ietf.org (www.iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA00676
	for <pim-archive@odin.ietf.org>; Tue, 11 May 2004 00:30:52 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNOrY-0001cq-7m
	for pim-archive@odin.ietf.org; Tue, 11 May 2004 00:27:30 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4B4RSj0006243
	for pim-archive@odin.ietf.org; Tue, 11 May 2004 00:27:28 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNOpa-0001Dw-3s
	for pim-web-archive@optimus.ietf.org; Tue, 11 May 2004 00:25:26 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA00308
	for <pim-web-archive@ietf.org>; Tue, 11 May 2004 00:25:22 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BNOpX-00037u-Q7
	for pim-web-archive@ietf.org; Tue, 11 May 2004 00:25:23 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNOof-0002lb-00
	for pim-web-archive@ietf.org; Tue, 11 May 2004 00:24:30 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNOnj-0002PT-00
	for pim-web-archive@ietf.org; Tue, 11 May 2004 00:23:31 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNOch-0006h8-MS; Tue, 11 May 2004 00:12:07 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNOZA-00055R-3u
	for pim@optimus.ietf.org; Tue, 11 May 2004 00:08:28 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA29713
	for <pim@ietf.org>; Tue, 11 May 2004 00:08:23 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BNOZ7-0004xd-1i
	for pim@ietf.org; Tue, 11 May 2004 00:08:25 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNOYH-0004dC-00
	for pim@ietf.org; Tue, 11 May 2004 00:07:34 -0400
Received: from mta2.huawei.com ([61.144.161.24] helo=huawei.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNOXe-0004Db-00
	for pim@ietf.org; Tue, 11 May 2004 00:07:05 -0400
Received: from huawei.com (localhost [127.0.0.1])
 by mta2.huawei.com (iPlanet Messaging Server 5.2 HotFix 0.7 (built Jun 26
 2002)) with ESMTP id <0HXJ00H727GOU0@mta2.huawei.com> for pim@ietf.org; Tue,
 11 May 2004 12:07:36 +0800 (CST)
Received: from mailin.huawei.com ([10.18.1.252])
 by mta2.huawei.com (iPlanet Messaging Server 5.2 HotFix 0.7 (built Jun 26
 2002)) with ESMTP id <0HXJ00JM87GN3Y@mta2.huawei.com> for pim@ietf.org; Tue,
 11 May 2004 12:07:35 +0800 (CST)
Received: from DELL15 ([10.18.4.137])
 by mailin.huawei.com (Netscape Messaging Server 4.15)
 with ESMTP id HXJ7MG01.007; Tue, 11 May 2004 12:11:04 +0800
Date: Tue, 11 May 2004 09:44:07 +0530
From: Prashant Jhingran <prashantj@huawei.com>
Subject: RE: [pim] Very simple pimd multicast configuration
In-reply-to: <200405110151.i4B1pukP078779@garnet.juniper.net>
To: paras@juniper.net, beasse.pordic@wanadoo.fr
Cc: pim@ietf.org
Reply-to: prashantj@huawei.com
Message-id: <004101c4370e$680367e0$0701010b@DELL15>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
Content-type: text/plain; charset=gb2312
Content-transfer-encoding: QUOTED-PRINTABLE
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
Content-Transfer-Encoding: QUOTED-PRINTABLE
Sender: pim-admin@ietf.org
Errors-To: pim-admin@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Id: Protocol Independent Multicast <pim.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: QUOTED-PRINTABLE
Content-Transfer-Encoding: QUOTED-PRINTABLE

hi,
    Also not very sure how Ping can work with a multicast address , b=
ecause
multicast fwd entries will be created only on request in case of PIM-=
SM.
You may however try a utility called "mping" instead of normal "ping"=
.

regards,
Prashant

-----Original Message-----
=46rom: pim-admin@ietf.org [mailto:pim-admin@ietf.org]On Behalf Of
paras@juniper.net
Sent: Tuesday, May 11, 2004 7:22 AM
To: Famille B=E9asse .huawei.com
Cc: pim@ietf.org
Subject: Re: [pim] Very simple pimd multicast configuration



First of all, you're using group addr 224.0.0.1 for testing.
It is a very special group, which, along with all of 224.0.0.0/24
will not be forwarded by any multicast router.
It's reserved for link-local multicast,
for protocol hellos and such, that are to be sent with TTL=3D1.

However, I can't tell what else is wrong, if you're using other
valid multicast data groups too. At least, the first thought is
to point out the invalid group usage above.

- Paras.

>
> Hi,
>
> Can someone can help-me to make a very simple multicast configurati=
on.
>
> Here is my test configuration  (With just one Router):
>
> Server ----------------Multicast Router ----------------------Clien=
t
> [192.168.1.1        192.168.1.250]   [192.168.0.250         192.168=
.0.1]
>
> Netmask is 255.255.255.0
> /proc/sys/net/ipv4/ip_forward is set to1
> Router is Linux Fedora Core 1 With Pimd-2.1.0-alpha29-18
> IP_Multicast PIM-SM etc is activate by default in kernel.
>
> My router is ok for unicast. I can communicate from server to clien=
t.
>
> But When i want to make Multicast from Server to Client, traffic is=
 not
> forward by the router.When i do a "ping -t 5 224.0.0.1" on Linux Cl=
ient,
> packets are not forwards to Linux Server and vice-versa.
>
> What tools can i use to see if configuration is OK ?
> What's about pimd.conf configuration file ?
>
> When i do a "ip mroute show" there is nothing to see is it normal ?
>
> Do you have any idea.
> Thanks for your help.
>
> Best regards
>
> Christophe B=E9asse
> France
>
>
>
>
> _______________________________________________
> 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-admin@ietf.org  Tue May 11 04:10:23 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA10410
	for <pim-archive@lists.ietf.org>; Tue, 11 May 2004 04:10:23 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNS0u-0001C8-3L; Tue, 11 May 2004 03:49:20 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNRwL-0008Fb-BY
	for pim@optimus.ietf.org; Tue, 11 May 2004 03:44:37 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA09086
	for <pim@ietf.org>; Tue, 11 May 2004 03:44:35 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BNRwI-0005Ob-TN
	for pim@ietf.org; Tue, 11 May 2004 03:44:35 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNRvK-000528-00
	for pim@ietf.org; Tue, 11 May 2004 03:43:35 -0400
Received: from zeus.corecess.com ([218.147.97.51])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNRuS-0004g6-00
	for pim@ietf.org; Tue, 11 May 2004 03:42:40 -0400
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C4372A.5E8DFD67"
Subject: RE: [pim] Very simple pimd multicast configuration
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
Date: Tue, 11 May 2004 16:34:18 +0900
Message-ID: <37BAA3695E46C24A91128FB94F0CC3E06AC14E@zeus>
Thread-Topic: [pim] Very simple pimd multicast configuration
Thread-Index: AcQ3Dx4NnM4zvyvqQ8egDuiIcLYYDQAGi/Md
From: "Ganapathasaa" <ganapath@Corecess.com>
To: <prashantj@huawei.com>, <paras@juniper.net>, <beasse.pordic@wanadoo.fr>
Cc: <pim@ietf.org>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: pim-admin@ietf.org
Errors-To: pim-admin@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Id: Protocol Independent Multicast <pim.ietf.org>
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>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C4372A.5E8DFD67
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: base64

SGksDQogDQpFdmVuIHRob3VnaCBpdCBpcyBub3QgcG9zc2libGUgdG8gZW5zdXJlICJlbmQgdG8g
ZW5kIG11bHRpY2FzdCcgY29ubmVjdGl2aXR5IHVzaW5nIHBpbmcgY29tbWFuZCwgaG93ZXZlciB5
b3UgY2FuIGNoZWNrIHRoZSBtdWx0aWNhc3QgY29ubmVjdGl2aXR5IHNlcGVyYXRlbHkoaS5lLiwg
ZnJvbSBzZXJ2ZXIgdG8gTXVsdGljYXN0IHJvdXRlciBhbmQgdGhlbiBmcm9tIHJvdXRlciBjbGll
bnQpIGluIHlvdXIgc2V0dXAsIHVzaW5nIHRoZSBwaW5nIGNvbW1hbmQgaXRzZWxmLg0KIA0KVHJ5
IHBpbmdpbmcgMjI0LjAuMC4yKGFsbCByb3V0ZXJzKSwgMjI0LjAuMC4xMyhhbGwgcGltIHJvdXRl
cnMpIGZyb20gc2VydmVyL2NsaWVudCB0byByb3V0ZXIsIHRoZSByb3V0ZXIgc2hvdWxkIHJlbHB5
IGFzIHlvdSBhcmUgcnVubmluZyBQSU0uIEFuZCBhbHNvIHRyeSAicGluZyAyMjQuMC4wLjEoYWxs
IHN5c3RlbXMpIiBmcm9tIHJvdXRlciB0byBzZXJ2ZXIgYW5kIGNsaWVudC4gQnV0IHJlbWVtYmVy
IHRvIGNoZWNrIHRoZSBkZWZhdWx0IHVuaWNhc3Qgcm91dGUgb24gdGhlIHN5c3RlbSBmcm9tIHdo
ZXJlIHlvdSBhcmUgZ2VuZXJhdGluZyB0aGUgcGluZywgcGluZyAyMjQueC54LnggcGFja2V0cyB3
aWxsIGJlIHNlbnQgb25seSBvbiBkZWZhdWx0IGxpbmsgYXMgdGhlcmUgd2lsbCBiZSBubyBtYXRj
aGluZyBlbnRyeSBmb3IgMjI0LngueC54IGluIHVuaWNhc3Qgcm91dGluZyB0YWJsZS4NCiANCmNo
ZWVycywNCkdhbmFwYXRoDQoNCgktLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLSANCglGcm9tOiBQ
cmFzaGFudCBKaGluZ3JhbihwcmFzaGFudGpAaHVhd2VpLmNvbSkgW21haWx0bzpwcmFzaGFudGpA
aHVhd2VpLmNvbV0gDQoJU2VudDogVHVlIDUvMTEvMjAwNCAxOjE0IFBNIA0KCVRvOiBwYXJhc0Bq
dW5pcGVyLm5ldDsgYmVhc3NlLnBvcmRpY0B3YW5hZG9vLmZyIA0KCUNjOiBwaW1AaWV0Zi5vcmcg
DQoJU3ViamVjdDogUkU6IFtwaW1dIFZlcnkgc2ltcGxlIHBpbWQgbXVsdGljYXN0IGNvbmZpZ3Vy
YXRpb24NCgkNCgkNCg0KCWhpLCANCgkgICAgQWxzbyBub3QgdmVyeSBzdXJlIGhvdyBQaW5nIGNh
biB3b3JrIHdpdGggYSBtdWx0aWNhc3QgYWRkcmVzcyAsIGJlY2F1c2UgDQoJbXVsdGljYXN0IGZ3
ZCBlbnRyaWVzIHdpbGwgYmUgY3JlYXRlZCBvbmx5IG9uIHJlcXVlc3QgaW4gY2FzZSBvZiBQSU0t
U00uIA0KCVlvdSBtYXkgaG93ZXZlciB0cnkgYSB1dGlsaXR5IGNhbGxlZCAibXBpbmciIGluc3Rl
YWQgb2Ygbm9ybWFsICJwaW5nIi4gDQoNCglyZWdhcmRzLCANCglQcmFzaGFudCANCg0KCS0tLS0t
T3JpZ2luYWwgTWVzc2FnZS0tLS0tIA0KCUZyb206IHBpbS1hZG1pbkBpZXRmLm9yZyBbbWFpbHRv
OnBpbS1hZG1pbkBpZXRmLm9yZ11PbiBCZWhhbGYgT2YgDQoJcGFyYXNAanVuaXBlci5uZXQgDQoJ
U2VudDogVHVlc2RheSwgTWF5IDExLCAyMDA0IDc6MjIgQU0gDQoJVG86IEZhbWlsbGUgQumWjXNz
ZSAuaHVhd2VpLmNvbSANCglDYzogcGltQGlldGYub3JnIA0KCVN1YmplY3Q6IFJlOiBbcGltXSBW
ZXJ5IHNpbXBsZSBwaW1kIG11bHRpY2FzdCBjb25maWd1cmF0aW9uIA0KDQoNCg0KCUZpcnN0IG9m
IGFsbCwgeW91J3JlIHVzaW5nIGdyb3VwIGFkZHIgMjI0LjAuMC4xIGZvciB0ZXN0aW5nLiANCglJ
dCBpcyBhIHZlcnkgc3BlY2lhbCBncm91cCwgd2hpY2gsIGFsb25nIHdpdGggYWxsIG9mIDIyNC4w
LjAuMC8yNCANCgl3aWxsIG5vdCBiZSBmb3J3YXJkZWQgYnkgYW55IG11bHRpY2FzdCByb3V0ZXIu
IA0KCUl0J3MgcmVzZXJ2ZWQgZm9yIGxpbmstbG9jYWwgbXVsdGljYXN0LCANCglmb3IgcHJvdG9j
b2wgaGVsbG9zIGFuZCBzdWNoLCB0aGF0IGFyZSB0byBiZSBzZW50IHdpdGggVFRMPTEuIA0KDQoJ
SG93ZXZlciwgSSBjYW4ndCB0ZWxsIHdoYXQgZWxzZSBpcyB3cm9uZywgaWYgeW91J3JlIHVzaW5n
IG90aGVyIA0KCXZhbGlkIG11bHRpY2FzdCBkYXRhIGdyb3VwcyB0b28uIEF0IGxlYXN0LCB0aGUg
Zmlyc3QgdGhvdWdodCBpcyANCgl0byBwb2ludCBvdXQgdGhlIGludmFsaWQgZ3JvdXAgdXNhZ2Ug
YWJvdmUuIA0KDQoJLSBQYXJhcy4gDQoNCgk+IA0KCT4gSGksIA0KCT4gDQoJPiBDYW4gc29tZW9u
ZSBjYW4gaGVscC1tZSB0byBtYWtlIGEgdmVyeSBzaW1wbGUgbXVsdGljYXN0IGNvbmZpZ3VyYXRp
b24uIA0KCT4gDQoJPiBIZXJlIGlzIG15IHRlc3QgY29uZmlndXJhdGlvbiAgKFdpdGgganVzdCBv
bmUgUm91dGVyKTogDQoJPiANCgk+IFNlcnZlciAtLS0tLS0tLS0tLS0tLS0tTXVsdGljYXN0IFJv
dXRlciAtLS0tLS0tLS0tLS0tLS0tLS0tLS0tQ2xpZW50IA0KCT4gWzE5Mi4xNjguMS4xICAgICAg
ICAxOTIuMTY4LjEuMjUwXSAgIFsxOTIuMTY4LjAuMjUwICAgICAgICAgMTkyLjE2OC4wLjFdIA0K
CT4gDQoJPiBOZXRtYXNrIGlzIDI1NS4yNTUuMjU1LjAgDQoJPiAvcHJvYy9zeXMvbmV0L2lwdjQv
aXBfZm9yd2FyZCBpcyBzZXQgdG8xIA0KCT4gUm91dGVyIGlzIExpbnV4IEZlZG9yYSBDb3JlIDEg
V2l0aCBQaW1kLTIuMS4wLWFscGhhMjktMTggDQoJPiBJUF9NdWx0aWNhc3QgUElNLVNNIGV0YyBp
cyBhY3RpdmF0ZSBieSBkZWZhdWx0IGluIGtlcm5lbC4gDQoJPiANCgk+IE15IHJvdXRlciBpcyBv
ayBmb3IgdW5pY2FzdC4gSSBjYW4gY29tbXVuaWNhdGUgZnJvbSBzZXJ2ZXIgdG8gY2xpZW50LiAN
Cgk+IA0KCT4gQnV0IFdoZW4gaSB3YW50IHRvIG1ha2UgTXVsdGljYXN0IGZyb20gU2VydmVyIHRv
IENsaWVudCwgdHJhZmZpYyBpcyBub3QgDQoJPiBmb3J3YXJkIGJ5IHRoZSByb3V0ZXIuV2hlbiBp
IGRvIGEgInBpbmcgLXQgNSAyMjQuMC4wLjEiIG9uIExpbnV4IENsaWVudCwgDQoJPiBwYWNrZXRz
IGFyZSBub3QgZm9yd2FyZHMgdG8gTGludXggU2VydmVyIGFuZCB2aWNlLXZlcnNhLiANCgk+IA0K
CT4gV2hhdCB0b29scyBjYW4gaSB1c2UgdG8gc2VlIGlmIGNvbmZpZ3VyYXRpb24gaXMgT0sgPyAN
Cgk+IFdoYXQncyBhYm91dCBwaW1kLmNvbmYgY29uZmlndXJhdGlvbiBmaWxlID8gDQoJPiANCgk+
IFdoZW4gaSBkbyBhICJpcCBtcm91dGUgc2hvdyIgdGhlcmUgaXMgbm90aGluZyB0byBzZWUgaXMg
aXQgbm9ybWFsID8gDQoJPiANCgk+IERvIHlvdSBoYXZlIGFueSBpZGVhLiANCgk+IFRoYW5rcyBm
b3IgeW91ciBoZWxwLiANCgk+IA0KCT4gQmVzdCByZWdhcmRzIA0KCT4gDQoJPiBDaHJpc3RvcGhl
IELplo1zc2UgDQoJPiBGcmFuY2UgDQoJPiANCgk+IA0KCT4gDQoJPiANCgk+IF9fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fIA0KCT4gcGltIG1haWxpbmcgbGlz
dCANCgk+IHBpbUBpZXRmLm9yZyANCgk+IGh0dHBzOi8vd3d3MS5pZXRmLm9yZy9tYWlsbWFuL2xp
c3RpbmZvL3BpbSANCgk+IA0KDQoNCglfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fXyANCglwaW0gbWFpbGluZyBsaXN0IA0KCXBpbUBpZXRmLm9yZyANCglodHRw
czovL3d3dzEuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9waW0gDQoNCg0KDQoJX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18gDQoJcGltIG1haWxpbmcgbGlz
dCANCglwaW1AaWV0Zi5vcmcgDQoJaHR0cHM6Ly93d3cxLmlldGYub3JnL21haWxtYW4vbGlzdGlu
Zm8vcGltIA0KDQo=

------_=_NextPart_001_01C4372A.5E8DFD67
Content-Type: text/html;
	charset="utf-8"
Content-Transfer-Encoding: base64

PE1FVEEgSFRUUC1FUVVJVj0iQ29udGVudC1UeXBlIiBDT05URU5UPSJ0ZXh0L2h0bWw7IGNoYXJz
ZXQ9dXRmLTgiPgo8IURPQ1RZUEUgSFRNTCBQVUJMSUMgIi0vL1czQy8vRFREIEhUTUwgMy4yLy9F
TiI+CjxIVE1MPgo8SEVBRD4KCjxNRVRBIE5BTUU9IkdlbmVyYXRvciIgQ09OVEVOVD0iTVMgRXhj
aGFuZ2UgU2VydmVyIHZlcnNpb24gNi4wLjU3NjIuMyI+CjxUSVRMRT5SRTogW3BpbV0gVmVyeSBz
aW1wbGUgcGltZCBtdWx0aWNhc3QgY29uZmlndXJhdGlvbjwvVElUTEU+CjwvSEVBRD4KPEJPRFkg
ZGlyPWx0cj4KPERJVj5IaSw8L0RJVj4KPERJVj4mbmJzcDs8L0RJVj4KPERJVj5FdmVuIHRob3Vn
aCBpdCBpcyBub3QgcG9zc2libGUgdG8gZW5zdXJlICJlbmQgdG8gZW5kIG11bHRpY2FzdCcgCmNv
bm5lY3Rpdml0eSB1c2luZyBwaW5nIGNvbW1hbmQsIGhvd2V2ZXIgeW91IGNhbiBjaGVjayB0aGUg
bXVsdGljYXN0IApjb25uZWN0aXZpdHkgc2VwZXJhdGVseShpLmUuLCBmcm9tIHNlcnZlciB0byBN
dWx0aWNhc3Qgcm91dGVyIGFuZCB0aGVuIGZyb20gCnJvdXRlciBjbGllbnQpIGluIHlvdXIgc2V0
dXAsIHVzaW5nIHRoZSBwaW5nIGNvbW1hbmQgaXRzZWxmLjwvRElWPgo8RElWPiZuYnNwOzwvRElW
Pgo8RElWPlRyeSBwaW5naW5nIDIyNC4wLjAuMihhbGwgcm91dGVycyksIDIyNC4wLjAuMTMoYWxs
IHBpbSByb3V0ZXJzKSBmcm9tIApzZXJ2ZXIvY2xpZW50IHRvIHJvdXRlciwgdGhlIHJvdXRlciBz
aG91bGQgcmVscHkgYXMgeW91IGFyZSBydW5uaW5nIFBJTS4gQW5kIAphbHNvIHRyeSAicGluZyAy
MjQuMC4wLjEoYWxsIHN5c3RlbXMpIiBmcm9tIHJvdXRlciB0byBzZXJ2ZXIgYW5kIGNsaWVudC4g
QnV0IApyZW1lbWJlciB0byBjaGVjayB0aGUgZGVmYXVsdCB1bmljYXN0IHJvdXRlIG9uIHRoZSBz
eXN0ZW0gZnJvbSB3aGVyZSB5b3UgYXJlIApnZW5lcmF0aW5nIHRoZSBwaW5nLCBwaW5nIDIyNC54
LngueCBwYWNrZXRzIHdpbGwgYmUgc2VudCBvbmx5IG9uIGRlZmF1bHQgbGluayBhcyAKdGhlcmUg
d2lsbCBiZSBubyBtYXRjaGluZyBlbnRyeSBmb3IgMjI0LngueC54IGluIHVuaWNhc3Qgcm91dGlu
ZyB0YWJsZS48L0RJVj4KPERJVj4mbmJzcDs8L0RJVj4KPERJVj5jaGVlcnMsPEJSPkdhbmFwYXRo
PC9ESVY+CjxCTE9DS1FVT1RFIGRpcj1sdHIgc3R5bGU9Ik1BUkdJTi1SSUdIVDogMHB4Ij4KICA8
RElWPjxGT05UIHNpemU9Mj4tLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLSA8QlI+PEI+RnJvbTo8
L0I+IFByYXNoYW50IAogIEpoaW5ncmFuKHByYXNoYW50akBodWF3ZWkuY29tKSBbbWFpbHRvOnBy
YXNoYW50akBodWF3ZWkuY29tXSA8QlI+PEI+U2VudDo8L0I+IAogIFR1ZSA1LzExLzIwMDQgMTox
NCBQTSA8QlI+PEI+VG86PC9CPiBwYXJhc0BqdW5pcGVyLm5ldDsgCiAgYmVhc3NlLnBvcmRpY0B3
YW5hZG9vLmZyIDxCUj48Qj5DYzo8L0I+IHBpbUBpZXRmLm9yZyA8QlI+PEI+U3ViamVjdDo8L0I+
IFJFOiAKICBbcGltXSBWZXJ5IHNpbXBsZSBwaW1kIG11bHRpY2FzdCBjb25maWd1cmF0aW9uPEJS
PjxCUj48L0ZPTlQ+PC9ESVY+CiAgPFA+PEZPTlQgc2l6ZT0yPmhpLDwvRk9OVD4gPEJSPjxGT05U
IHNpemU9Mj4mbmJzcDsmbmJzcDsmbmJzcDsgQWxzbyBub3QgdmVyeSAKICBzdXJlIGhvdyBQaW5n
IGNhbiB3b3JrIHdpdGggYSBtdWx0aWNhc3QgYWRkcmVzcyAsIGJlY2F1c2U8L0ZPTlQ+IDxCUj48
Rk9OVCAKICBzaXplPTI+bXVsdGljYXN0IGZ3ZCBlbnRyaWVzIHdpbGwgYmUgY3JlYXRlZCBvbmx5
IG9uIHJlcXVlc3QgaW4gY2FzZSBvZiAKICBQSU0tU00uPC9GT05UPiA8QlI+PEZPTlQgc2l6ZT0y
PllvdSBtYXkgaG93ZXZlciB0cnkgYSB1dGlsaXR5IGNhbGxlZCAibXBpbmciIAogIGluc3RlYWQg
b2Ygbm9ybWFsICJwaW5nIi48L0ZPTlQ+IDwvUD4KICA8UD48Rk9OVCBzaXplPTI+cmVnYXJkcyw8
L0ZPTlQ+IDxCUj48Rk9OVCBzaXplPTI+UHJhc2hhbnQ8L0ZPTlQ+IDwvUD4KICA8UD48Rk9OVCBz
aXplPTI+LS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS08L0ZPTlQ+IDxCUj48Rk9OVCBzaXplPTI+
RnJvbTogCiAgcGltLWFkbWluQGlldGYub3JnIFs8QSAKICBocmVmPSJtYWlsdG86cGltLWFkbWlu
QGlldGYub3JnIj5tYWlsdG86cGltLWFkbWluQGlldGYub3JnPC9BPl1PbiBCZWhhbGYgCiAgT2Y8
L0ZPTlQ+IDxCUj48Rk9OVCBzaXplPTI+cGFyYXNAanVuaXBlci5uZXQ8L0ZPTlQ+IDxCUj48Rk9O
VCBzaXplPTI+U2VudDogCiAgVHVlc2RheSwgTWF5IDExLCAyMDA0IDc6MjIgQU08L0ZPTlQ+IDxC
Uj48Rk9OVCBzaXplPTI+VG86IEZhbWlsbGUgQumWjXNzZSAKICAuaHVhd2VpLmNvbTwvRk9OVD4g
PEJSPjxGT05UIHNpemU9Mj5DYzogcGltQGlldGYub3JnPC9GT05UPiA8QlI+PEZPTlQgCiAgc2l6
ZT0yPlN1YmplY3Q6IFJlOiBbcGltXSBWZXJ5IHNpbXBsZSBwaW1kIG11bHRpY2FzdCBjb25maWd1
cmF0aW9uPC9GT05UPiAKICA8L1A+PEJSPjxCUj4KICA8UD48Rk9OVCBzaXplPTI+Rmlyc3Qgb2Yg
YWxsLCB5b3UncmUgdXNpbmcgZ3JvdXAgYWRkciAyMjQuMC4wLjEgZm9yIAogIHRlc3RpbmcuPC9G
T05UPiA8QlI+PEZPTlQgc2l6ZT0yPkl0IGlzIGEgdmVyeSBzcGVjaWFsIGdyb3VwLCB3aGljaCwg
YWxvbmcgd2l0aCAKICBhbGwgb2YgMjI0LjAuMC4wLzI0PC9GT05UPiA8QlI+PEZPTlQgc2l6ZT0y
PndpbGwgbm90IGJlIGZvcndhcmRlZCBieSBhbnkgCiAgbXVsdGljYXN0IHJvdXRlci48L0ZPTlQ+
IDxCUj48Rk9OVCBzaXplPTI+SXQncyByZXNlcnZlZCBmb3IgbGluay1sb2NhbCAKICBtdWx0aWNh
c3QsPC9GT05UPiA8QlI+PEZPTlQgc2l6ZT0yPmZvciBwcm90b2NvbCBoZWxsb3MgYW5kIHN1Y2gs
IHRoYXQgYXJlIHRvIAogIGJlIHNlbnQgd2l0aCBUVEw9MS48L0ZPTlQ+IDwvUD4KICA8UD48Rk9O
VCBzaXplPTI+SG93ZXZlciwgSSBjYW4ndCB0ZWxsIHdoYXQgZWxzZSBpcyB3cm9uZywgaWYgeW91
J3JlIHVzaW5nIAogIG90aGVyPC9GT05UPiA8QlI+PEZPTlQgc2l6ZT0yPnZhbGlkIG11bHRpY2Fz
dCBkYXRhIGdyb3VwcyB0b28uIEF0IGxlYXN0LCB0aGUgCiAgZmlyc3QgdGhvdWdodCBpczwvRk9O
VD4gPEJSPjxGT05UIHNpemU9Mj50byBwb2ludCBvdXQgdGhlIGludmFsaWQgZ3JvdXAgdXNhZ2Ug
CiAgYWJvdmUuPC9GT05UPiA8L1A+CiAgPFA+PEZPTlQgc2l6ZT0yPi0gUGFyYXMuPC9GT05UPiA8
L1A+CiAgPFA+PEZPTlQgc2l6ZT0yPiZndDs8L0ZPTlQ+IDxCUj48Rk9OVCBzaXplPTI+Jmd0OyBI
aSw8L0ZPTlQ+IDxCUj48Rk9OVCAKICBzaXplPTI+Jmd0OzwvRk9OVD4gPEJSPjxGT05UIHNpemU9
Mj4mZ3Q7IENhbiBzb21lb25lIGNhbiBoZWxwLW1lIHRvIG1ha2UgYSAKICB2ZXJ5IHNpbXBsZSBt
dWx0aWNhc3QgY29uZmlndXJhdGlvbi48L0ZPTlQ+IDxCUj48Rk9OVCBzaXplPTI+Jmd0OzwvRk9O
VD4gCiAgPEJSPjxGT05UIHNpemU9Mj4mZ3Q7IEhlcmUgaXMgbXkgdGVzdCBjb25maWd1cmF0aW9u
Jm5ic3A7IChXaXRoIGp1c3Qgb25lIAogIFJvdXRlcik6PC9GT05UPiA8QlI+PEZPTlQgc2l6ZT0y
PiZndDs8L0ZPTlQ+IDxCUj48Rk9OVCBzaXplPTI+Jmd0OyBTZXJ2ZXIgCiAgLS0tLS0tLS0tLS0t
LS0tLU11bHRpY2FzdCBSb3V0ZXIgLS0tLS0tLS0tLS0tLS0tLS0tLS0tLUNsaWVudDwvRk9OVD4g
PEJSPjxGT05UIAogIHNpemU9Mj4mZ3Q7IFsxOTIuMTY4LjEuMSZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyAKICAxOTIuMTY4LjEuMjUwXSZuYnNwOyZuYnNwOyAKICBb
MTkyLjE2OC4wLjI1MCZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyAKICAxOTIuMTY4LjAuMV08L0ZPTlQ+IDxCUj48Rk9OVCBzaXplPTI+Jmd0OzwvRk9OVD4g
PEJSPjxGT05UIHNpemU9Mj4mZ3Q7IE5ldG1hc2sgCiAgaXMgMjU1LjI1NS4yNTUuMDwvRk9OVD4g
PEJSPjxGT05UIHNpemU9Mj4mZ3Q7IC9wcm9jL3N5cy9uZXQvaXB2NC9pcF9mb3J3YXJkIGlzIAog
IHNldCB0bzE8L0ZPTlQ+IDxCUj48Rk9OVCBzaXplPTI+Jmd0OyBSb3V0ZXIgaXMgTGludXggRmVk
b3JhIENvcmUgMSBXaXRoIAogIFBpbWQtMi4xLjAtYWxwaGEyOS0xODwvRk9OVD4gPEJSPjxGT05U
IHNpemU9Mj4mZ3Q7IElQX011bHRpY2FzdCBQSU0tU00gZXRjIGlzIAogIGFjdGl2YXRlIGJ5IGRl
ZmF1bHQgaW4ga2VybmVsLjwvRk9OVD4gPEJSPjxGT05UIHNpemU9Mj4mZ3Q7PC9GT05UPiA8QlI+
PEZPTlQgCiAgc2l6ZT0yPiZndDsgTXkgcm91dGVyIGlzIG9rIGZvciB1bmljYXN0LiBJIGNhbiBj
b21tdW5pY2F0ZSBmcm9tIHNlcnZlciB0byAKICBjbGllbnQuPC9GT05UPiA8QlI+PEZPTlQgc2l6
ZT0yPiZndDs8L0ZPTlQ+IDxCUj48Rk9OVCBzaXplPTI+Jmd0OyBCdXQgV2hlbiBpIAogIHdhbnQg
dG8gbWFrZSBNdWx0aWNhc3QgZnJvbSBTZXJ2ZXIgdG8gQ2xpZW50LCB0cmFmZmljIGlzIG5vdDwv
Rk9OVD4gPEJSPjxGT05UIAogIHNpemU9Mj4mZ3Q7IGZvcndhcmQgYnkgdGhlIHJvdXRlci5XaGVu
IGkgZG8gYSAicGluZyAtdCA1IDIyNC4wLjAuMSIgb24gTGludXggCiAgQ2xpZW50LDwvRk9OVD4g
PEJSPjxGT05UIHNpemU9Mj4mZ3Q7IHBhY2tldHMgYXJlIG5vdCBmb3J3YXJkcyB0byBMaW51eCBT
ZXJ2ZXIgCiAgYW5kIHZpY2UtdmVyc2EuPC9GT05UPiA8QlI+PEZPTlQgc2l6ZT0yPiZndDs8L0ZP
TlQ+IDxCUj48Rk9OVCBzaXplPTI+Jmd0OyBXaGF0IAogIHRvb2xzIGNhbiBpIHVzZSB0byBzZWUg
aWYgY29uZmlndXJhdGlvbiBpcyBPSyA/PC9GT05UPiA8QlI+PEZPTlQgc2l6ZT0yPiZndDsgCiAg
V2hhdCdzIGFib3V0IHBpbWQuY29uZiBjb25maWd1cmF0aW9uIGZpbGUgPzwvRk9OVD4gPEJSPjxG
T05UIAogIHNpemU9Mj4mZ3Q7PC9GT05UPiA8QlI+PEZPTlQgc2l6ZT0yPiZndDsgV2hlbiBpIGRv
IGEgImlwIG1yb3V0ZSBzaG93IiB0aGVyZSBpcyAKICBub3RoaW5nIHRvIHNlZSBpcyBpdCBub3Jt
YWwgPzwvRk9OVD4gPEJSPjxGT05UIHNpemU9Mj4mZ3Q7PC9GT05UPiA8QlI+PEZPTlQgCiAgc2l6
ZT0yPiZndDsgRG8geW91IGhhdmUgYW55IGlkZWEuPC9GT05UPiA8QlI+PEZPTlQgc2l6ZT0yPiZn
dDsgVGhhbmtzIGZvciB5b3VyIAogIGhlbHAuPC9GT05UPiA8QlI+PEZPTlQgc2l6ZT0yPiZndDs8
L0ZPTlQ+IDxCUj48Rk9OVCBzaXplPTI+Jmd0OyBCZXN0IAogIHJlZ2FyZHM8L0ZPTlQ+IDxCUj48
Rk9OVCBzaXplPTI+Jmd0OzwvRk9OVD4gPEJSPjxGT05UIHNpemU9Mj4mZ3Q7IENocmlzdG9waGUg
CiAgQumWjXNzZTwvRk9OVD4gPEJSPjxGT05UIHNpemU9Mj4mZ3Q7IEZyYW5jZTwvRk9OVD4gPEJS
PjxGT05UIHNpemU9Mj4mZ3Q7PC9GT05UPiAKICA8QlI+PEZPTlQgc2l6ZT0yPiZndDs8L0ZPTlQ+
IDxCUj48Rk9OVCBzaXplPTI+Jmd0OzwvRk9OVD4gPEJSPjxGT05UIAogIHNpemU9Mj4mZ3Q7PC9G
T05UPiA8QlI+PEZPTlQgc2l6ZT0yPiZndDsgCiAgX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX188L0ZPTlQ+IDxCUj48Rk9OVCBzaXplPTI+Jmd0OyAKICBwaW0g
bWFpbGluZyBsaXN0PC9GT05UPiA8QlI+PEZPTlQgc2l6ZT0yPiZndDsgcGltQGlldGYub3JnPC9G
T05UPiA8QlI+PEZPTlQgCiAgc2l6ZT0yPiZndDsgPEEgCiAgaHJlZj0iaHR0cHM6Ly93d3cxLmll
dGYub3JnL21haWxtYW4vbGlzdGluZm8vcGltIj5odHRwczovL3d3dzEuaWV0Zi5vcmcvbWFpbG1h
bi9saXN0aW5mby9waW08L0E+PC9GT05UPiAKICA8QlI+PEZPTlQgc2l6ZT0yPiZndDs8L0ZPTlQ+
IDwvUD48QlI+CiAgPFA+PEZPTlQgc2l6ZT0yPl9fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fPC9GT05UPiAKICA8QlI+PEZPTlQgc2l6ZT0yPnBpbSBtYWlsaW5n
IGxpc3Q8L0ZPTlQ+IDxCUj48Rk9OVCBzaXplPTI+cGltQGlldGYub3JnPC9GT05UPiAKICA8QlI+
PEZPTlQgc2l6ZT0yPjxBIAogIGhyZWY9Imh0dHBzOi8vd3d3MS5pZXRmLm9yZy9tYWlsbWFuL2xp
c3RpbmZvL3BpbSI+aHR0cHM6Ly93d3cxLmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vcGltPC9B
PjwvRk9OVD4gCiAgPC9QPjxCUj48QlI+CiAgPFA+PEZPTlQgc2l6ZT0yPl9fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fPC9GT05UPiAKICA8QlI+PEZPTlQgc2l6
ZT0yPnBpbSBtYWlsaW5nIGxpc3Q8L0ZPTlQ+IDxCUj48Rk9OVCBzaXplPTI+cGltQGlldGYub3Jn
PC9GT05UPiAKICA8QlI+PEZPTlQgc2l6ZT0yPjxBIAogIGhyZWY9Imh0dHBzOi8vd3d3MS5pZXRm
Lm9yZy9tYWlsbWFuL2xpc3RpbmZvL3BpbSI+aHR0cHM6Ly93d3cxLmlldGYub3JnL21haWxtYW4v
bGlzdGluZm8vcGltPC9BPjwvRk9OVD4gCiAgPC9QPjwvQkxPQ0tRVU9URT4KCjwvQk9EWT4KPC9I
VE1MPg==

------_=_NextPart_001_01C4372A.5E8DFD67--

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


From exim@www1.ietf.org  Tue May 11 04:38:17 2004
Received: from optimus.ietf.org (www.iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA11952
	for <pim-archive@odin.ietf.org>; Tue, 11 May 2004 04:38:17 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNSYg-0002DF-Ko
	for pim-archive@odin.ietf.org; Tue, 11 May 2004 04:24:16 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4B8OEb0008505
	for pim-archive@odin.ietf.org; Tue, 11 May 2004 04:24:14 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNSMg-0007Fu-9J
	for pim-web-archive@optimus.ietf.org; Tue, 11 May 2004 04:11:50 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA10490
	for <pim-web-archive@ietf.org>; Tue, 11 May 2004 04:11:47 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BNSMd-00009V-Fc
	for pim-web-archive@ietf.org; Tue, 11 May 2004 04:11:47 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNSLX-0007Xc-00
	for pim-web-archive@ietf.org; Tue, 11 May 2004 04:10:39 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNSKn-0007B0-00
	for pim-web-archive@ietf.org; Tue, 11 May 2004 04:09:53 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNS0u-0001C8-3L; Tue, 11 May 2004 03:49:20 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNRwL-0008Fb-BY
	for pim@optimus.ietf.org; Tue, 11 May 2004 03:44:37 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA09086
	for <pim@ietf.org>; Tue, 11 May 2004 03:44:35 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BNRwI-0005Ob-TN
	for pim@ietf.org; Tue, 11 May 2004 03:44:35 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNRvK-000528-00
	for pim@ietf.org; Tue, 11 May 2004 03:43:35 -0400
Received: from zeus.corecess.com ([218.147.97.51])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNRuS-0004g6-00
	for pim@ietf.org; Tue, 11 May 2004 03:42:40 -0400
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C4372A.5E8DFD67"
Subject: RE: [pim] Very simple pimd multicast configuration
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
Date: Tue, 11 May 2004 16:34:18 +0900
Message-ID: <37BAA3695E46C24A91128FB94F0CC3E06AC14E@zeus>
Thread-Topic: [pim] Very simple pimd multicast configuration
Thread-Index: AcQ3Dx4NnM4zvyvqQ8egDuiIcLYYDQAGi/Md
From: "Ganapathasaa" <ganapath@Corecess.com>
To: <prashantj@huawei.com>, <paras@juniper.net>, <beasse.pordic@wanadoo.fr>
Cc: <pim@ietf.org>
Sender: pim-admin@ietf.org
Errors-To: pim-admin@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Id: Protocol Independent Multicast <pim.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60

This is a multi-part message in MIME format.

------_=_NextPart_001_01C4372A.5E8DFD67
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: base64

SGksDQogDQpFdmVuIHRob3VnaCBpdCBpcyBub3QgcG9zc2libGUgdG8gZW5zdXJlICJlbmQgdG8g
ZW5kIG11bHRpY2FzdCcgY29ubmVjdGl2aXR5IHVzaW5nIHBpbmcgY29tbWFuZCwgaG93ZXZlciB5
b3UgY2FuIGNoZWNrIHRoZSBtdWx0aWNhc3QgY29ubmVjdGl2aXR5IHNlcGVyYXRlbHkoaS5lLiwg
ZnJvbSBzZXJ2ZXIgdG8gTXVsdGljYXN0IHJvdXRlciBhbmQgdGhlbiBmcm9tIHJvdXRlciBjbGll
bnQpIGluIHlvdXIgc2V0dXAsIHVzaW5nIHRoZSBwaW5nIGNvbW1hbmQgaXRzZWxmLg0KIA0KVHJ5
IHBpbmdpbmcgMjI0LjAuMC4yKGFsbCByb3V0ZXJzKSwgMjI0LjAuMC4xMyhhbGwgcGltIHJvdXRl
cnMpIGZyb20gc2VydmVyL2NsaWVudCB0byByb3V0ZXIsIHRoZSByb3V0ZXIgc2hvdWxkIHJlbHB5
IGFzIHlvdSBhcmUgcnVubmluZyBQSU0uIEFuZCBhbHNvIHRyeSAicGluZyAyMjQuMC4wLjEoYWxs
IHN5c3RlbXMpIiBmcm9tIHJvdXRlciB0byBzZXJ2ZXIgYW5kIGNsaWVudC4gQnV0IHJlbWVtYmVy
IHRvIGNoZWNrIHRoZSBkZWZhdWx0IHVuaWNhc3Qgcm91dGUgb24gdGhlIHN5c3RlbSBmcm9tIHdo
ZXJlIHlvdSBhcmUgZ2VuZXJhdGluZyB0aGUgcGluZywgcGluZyAyMjQueC54LnggcGFja2V0cyB3
aWxsIGJlIHNlbnQgb25seSBvbiBkZWZhdWx0IGxpbmsgYXMgdGhlcmUgd2lsbCBiZSBubyBtYXRj
aGluZyBlbnRyeSBmb3IgMjI0LngueC54IGluIHVuaWNhc3Qgcm91dGluZyB0YWJsZS4NCiANCmNo
ZWVycywNCkdhbmFwYXRoDQoNCgktLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLSANCglGcm9tOiBQ
cmFzaGFudCBKaGluZ3JhbihwcmFzaGFudGpAaHVhd2VpLmNvbSkgW21haWx0bzpwcmFzaGFudGpA
aHVhd2VpLmNvbV0gDQoJU2VudDogVHVlIDUvMTEvMjAwNCAxOjE0IFBNIA0KCVRvOiBwYXJhc0Bq
dW5pcGVyLm5ldDsgYmVhc3NlLnBvcmRpY0B3YW5hZG9vLmZyIA0KCUNjOiBwaW1AaWV0Zi5vcmcg
DQoJU3ViamVjdDogUkU6IFtwaW1dIFZlcnkgc2ltcGxlIHBpbWQgbXVsdGljYXN0IGNvbmZpZ3Vy
YXRpb24NCgkNCgkNCg0KCWhpLCANCgkgICAgQWxzbyBub3QgdmVyeSBzdXJlIGhvdyBQaW5nIGNh
biB3b3JrIHdpdGggYSBtdWx0aWNhc3QgYWRkcmVzcyAsIGJlY2F1c2UgDQoJbXVsdGljYXN0IGZ3
ZCBlbnRyaWVzIHdpbGwgYmUgY3JlYXRlZCBvbmx5IG9uIHJlcXVlc3QgaW4gY2FzZSBvZiBQSU0t
U00uIA0KCVlvdSBtYXkgaG93ZXZlciB0cnkgYSB1dGlsaXR5IGNhbGxlZCAibXBpbmciIGluc3Rl
YWQgb2Ygbm9ybWFsICJwaW5nIi4gDQoNCglyZWdhcmRzLCANCglQcmFzaGFudCANCg0KCS0tLS0t
T3JpZ2luYWwgTWVzc2FnZS0tLS0tIA0KCUZyb206IHBpbS1hZG1pbkBpZXRmLm9yZyBbbWFpbHRv
OnBpbS1hZG1pbkBpZXRmLm9yZ11PbiBCZWhhbGYgT2YgDQoJcGFyYXNAanVuaXBlci5uZXQgDQoJ
U2VudDogVHVlc2RheSwgTWF5IDExLCAyMDA0IDc6MjIgQU0gDQoJVG86IEZhbWlsbGUgQumWjXNz
ZSAuaHVhd2VpLmNvbSANCglDYzogcGltQGlldGYub3JnIA0KCVN1YmplY3Q6IFJlOiBbcGltXSBW
ZXJ5IHNpbXBsZSBwaW1kIG11bHRpY2FzdCBjb25maWd1cmF0aW9uIA0KDQoNCg0KCUZpcnN0IG9m
IGFsbCwgeW91J3JlIHVzaW5nIGdyb3VwIGFkZHIgMjI0LjAuMC4xIGZvciB0ZXN0aW5nLiANCglJ
dCBpcyBhIHZlcnkgc3BlY2lhbCBncm91cCwgd2hpY2gsIGFsb25nIHdpdGggYWxsIG9mIDIyNC4w
LjAuMC8yNCANCgl3aWxsIG5vdCBiZSBmb3J3YXJkZWQgYnkgYW55IG11bHRpY2FzdCByb3V0ZXIu
IA0KCUl0J3MgcmVzZXJ2ZWQgZm9yIGxpbmstbG9jYWwgbXVsdGljYXN0LCANCglmb3IgcHJvdG9j
b2wgaGVsbG9zIGFuZCBzdWNoLCB0aGF0IGFyZSB0byBiZSBzZW50IHdpdGggVFRMPTEuIA0KDQoJ
SG93ZXZlciwgSSBjYW4ndCB0ZWxsIHdoYXQgZWxzZSBpcyB3cm9uZywgaWYgeW91J3JlIHVzaW5n
IG90aGVyIA0KCXZhbGlkIG11bHRpY2FzdCBkYXRhIGdyb3VwcyB0b28uIEF0IGxlYXN0LCB0aGUg
Zmlyc3QgdGhvdWdodCBpcyANCgl0byBwb2ludCBvdXQgdGhlIGludmFsaWQgZ3JvdXAgdXNhZ2Ug
YWJvdmUuIA0KDQoJLSBQYXJhcy4gDQoNCgk+IA0KCT4gSGksIA0KCT4gDQoJPiBDYW4gc29tZW9u
ZSBjYW4gaGVscC1tZSB0byBtYWtlIGEgdmVyeSBzaW1wbGUgbXVsdGljYXN0IGNvbmZpZ3VyYXRp
b24uIA0KCT4gDQoJPiBIZXJlIGlzIG15IHRlc3QgY29uZmlndXJhdGlvbiAgKFdpdGgganVzdCBv
bmUgUm91dGVyKTogDQoJPiANCgk+IFNlcnZlciAtLS0tLS0tLS0tLS0tLS0tTXVsdGljYXN0IFJv
dXRlciAtLS0tLS0tLS0tLS0tLS0tLS0tLS0tQ2xpZW50IA0KCT4gWzE5Mi4xNjguMS4xICAgICAg
ICAxOTIuMTY4LjEuMjUwXSAgIFsxOTIuMTY4LjAuMjUwICAgICAgICAgMTkyLjE2OC4wLjFdIA0K
CT4gDQoJPiBOZXRtYXNrIGlzIDI1NS4yNTUuMjU1LjAgDQoJPiAvcHJvYy9zeXMvbmV0L2lwdjQv
aXBfZm9yd2FyZCBpcyBzZXQgdG8xIA0KCT4gUm91dGVyIGlzIExpbnV4IEZlZG9yYSBDb3JlIDEg
V2l0aCBQaW1kLTIuMS4wLWFscGhhMjktMTggDQoJPiBJUF9NdWx0aWNhc3QgUElNLVNNIGV0YyBp
cyBhY3RpdmF0ZSBieSBkZWZhdWx0IGluIGtlcm5lbC4gDQoJPiANCgk+IE15IHJvdXRlciBpcyBv
ayBmb3IgdW5pY2FzdC4gSSBjYW4gY29tbXVuaWNhdGUgZnJvbSBzZXJ2ZXIgdG8gY2xpZW50LiAN
Cgk+IA0KCT4gQnV0IFdoZW4gaSB3YW50IHRvIG1ha2UgTXVsdGljYXN0IGZyb20gU2VydmVyIHRv
IENsaWVudCwgdHJhZmZpYyBpcyBub3QgDQoJPiBmb3J3YXJkIGJ5IHRoZSByb3V0ZXIuV2hlbiBp
IGRvIGEgInBpbmcgLXQgNSAyMjQuMC4wLjEiIG9uIExpbnV4IENsaWVudCwgDQoJPiBwYWNrZXRz
IGFyZSBub3QgZm9yd2FyZHMgdG8gTGludXggU2VydmVyIGFuZCB2aWNlLXZlcnNhLiANCgk+IA0K
CT4gV2hhdCB0b29scyBjYW4gaSB1c2UgdG8gc2VlIGlmIGNvbmZpZ3VyYXRpb24gaXMgT0sgPyAN
Cgk+IFdoYXQncyBhYm91dCBwaW1kLmNvbmYgY29uZmlndXJhdGlvbiBmaWxlID8gDQoJPiANCgk+
IFdoZW4gaSBkbyBhICJpcCBtcm91dGUgc2hvdyIgdGhlcmUgaXMgbm90aGluZyB0byBzZWUgaXMg
aXQgbm9ybWFsID8gDQoJPiANCgk+IERvIHlvdSBoYXZlIGFueSBpZGVhLiANCgk+IFRoYW5rcyBm
b3IgeW91ciBoZWxwLiANCgk+IA0KCT4gQmVzdCByZWdhcmRzIA0KCT4gDQoJPiBDaHJpc3RvcGhl
IELplo1zc2UgDQoJPiBGcmFuY2UgDQoJPiANCgk+IA0KCT4gDQoJPiANCgk+IF9fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fIA0KCT4gcGltIG1haWxpbmcgbGlz
dCANCgk+IHBpbUBpZXRmLm9yZyANCgk+IGh0dHBzOi8vd3d3MS5pZXRmLm9yZy9tYWlsbWFuL2xp
c3RpbmZvL3BpbSANCgk+IA0KDQoNCglfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fXyANCglwaW0gbWFpbGluZyBsaXN0IA0KCXBpbUBpZXRmLm9yZyANCglodHRw
czovL3d3dzEuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9waW0gDQoNCg0KDQoJX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18gDQoJcGltIG1haWxpbmcgbGlz
dCANCglwaW1AaWV0Zi5vcmcgDQoJaHR0cHM6Ly93d3cxLmlldGYub3JnL21haWxtYW4vbGlzdGlu
Zm8vcGltIA0KDQo=

------_=_NextPart_001_01C4372A.5E8DFD67
Content-Type: text/html;
	charset="utf-8"
Content-Transfer-Encoding: base64

PE1FVEEgSFRUUC1FUVVJVj0iQ29udGVudC1UeXBlIiBDT05URU5UPSJ0ZXh0L2h0bWw7IGNoYXJz
ZXQ9dXRmLTgiPgo8IURPQ1RZUEUgSFRNTCBQVUJMSUMgIi0vL1czQy8vRFREIEhUTUwgMy4yLy9F
TiI+CjxIVE1MPgo8SEVBRD4KCjxNRVRBIE5BTUU9IkdlbmVyYXRvciIgQ09OVEVOVD0iTVMgRXhj
aGFuZ2UgU2VydmVyIHZlcnNpb24gNi4wLjU3NjIuMyI+CjxUSVRMRT5SRTogW3BpbV0gVmVyeSBz
aW1wbGUgcGltZCBtdWx0aWNhc3QgY29uZmlndXJhdGlvbjwvVElUTEU+CjwvSEVBRD4KPEJPRFkg
ZGlyPWx0cj4KPERJVj5IaSw8L0RJVj4KPERJVj4mbmJzcDs8L0RJVj4KPERJVj5FdmVuIHRob3Vn
aCBpdCBpcyBub3QgcG9zc2libGUgdG8gZW5zdXJlICJlbmQgdG8gZW5kIG11bHRpY2FzdCcgCmNv
bm5lY3Rpdml0eSB1c2luZyBwaW5nIGNvbW1hbmQsIGhvd2V2ZXIgeW91IGNhbiBjaGVjayB0aGUg
bXVsdGljYXN0IApjb25uZWN0aXZpdHkgc2VwZXJhdGVseShpLmUuLCBmcm9tIHNlcnZlciB0byBN
dWx0aWNhc3Qgcm91dGVyIGFuZCB0aGVuIGZyb20gCnJvdXRlciBjbGllbnQpIGluIHlvdXIgc2V0
dXAsIHVzaW5nIHRoZSBwaW5nIGNvbW1hbmQgaXRzZWxmLjwvRElWPgo8RElWPiZuYnNwOzwvRElW
Pgo8RElWPlRyeSBwaW5naW5nIDIyNC4wLjAuMihhbGwgcm91dGVycyksIDIyNC4wLjAuMTMoYWxs
IHBpbSByb3V0ZXJzKSBmcm9tIApzZXJ2ZXIvY2xpZW50IHRvIHJvdXRlciwgdGhlIHJvdXRlciBz
aG91bGQgcmVscHkgYXMgeW91IGFyZSBydW5uaW5nIFBJTS4gQW5kIAphbHNvIHRyeSAicGluZyAy
MjQuMC4wLjEoYWxsIHN5c3RlbXMpIiBmcm9tIHJvdXRlciB0byBzZXJ2ZXIgYW5kIGNsaWVudC4g
QnV0IApyZW1lbWJlciB0byBjaGVjayB0aGUgZGVmYXVsdCB1bmljYXN0IHJvdXRlIG9uIHRoZSBz
eXN0ZW0gZnJvbSB3aGVyZSB5b3UgYXJlIApnZW5lcmF0aW5nIHRoZSBwaW5nLCBwaW5nIDIyNC54
LngueCBwYWNrZXRzIHdpbGwgYmUgc2VudCBvbmx5IG9uIGRlZmF1bHQgbGluayBhcyAKdGhlcmUg
d2lsbCBiZSBubyBtYXRjaGluZyBlbnRyeSBmb3IgMjI0LngueC54IGluIHVuaWNhc3Qgcm91dGlu
ZyB0YWJsZS48L0RJVj4KPERJVj4mbmJzcDs8L0RJVj4KPERJVj5jaGVlcnMsPEJSPkdhbmFwYXRo
PC9ESVY+CjxCTE9DS1FVT1RFIGRpcj1sdHIgc3R5bGU9Ik1BUkdJTi1SSUdIVDogMHB4Ij4KICA8
RElWPjxGT05UIHNpemU9Mj4tLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLSA8QlI+PEI+RnJvbTo8
L0I+IFByYXNoYW50IAogIEpoaW5ncmFuKHByYXNoYW50akBodWF3ZWkuY29tKSBbbWFpbHRvOnBy
YXNoYW50akBodWF3ZWkuY29tXSA8QlI+PEI+U2VudDo8L0I+IAogIFR1ZSA1LzExLzIwMDQgMTox
NCBQTSA8QlI+PEI+VG86PC9CPiBwYXJhc0BqdW5pcGVyLm5ldDsgCiAgYmVhc3NlLnBvcmRpY0B3
YW5hZG9vLmZyIDxCUj48Qj5DYzo8L0I+IHBpbUBpZXRmLm9yZyA8QlI+PEI+U3ViamVjdDo8L0I+
IFJFOiAKICBbcGltXSBWZXJ5IHNpbXBsZSBwaW1kIG11bHRpY2FzdCBjb25maWd1cmF0aW9uPEJS
PjxCUj48L0ZPTlQ+PC9ESVY+CiAgPFA+PEZPTlQgc2l6ZT0yPmhpLDwvRk9OVD4gPEJSPjxGT05U
IHNpemU9Mj4mbmJzcDsmbmJzcDsmbmJzcDsgQWxzbyBub3QgdmVyeSAKICBzdXJlIGhvdyBQaW5n
IGNhbiB3b3JrIHdpdGggYSBtdWx0aWNhc3QgYWRkcmVzcyAsIGJlY2F1c2U8L0ZPTlQ+IDxCUj48
Rk9OVCAKICBzaXplPTI+bXVsdGljYXN0IGZ3ZCBlbnRyaWVzIHdpbGwgYmUgY3JlYXRlZCBvbmx5
IG9uIHJlcXVlc3QgaW4gY2FzZSBvZiAKICBQSU0tU00uPC9GT05UPiA8QlI+PEZPTlQgc2l6ZT0y
PllvdSBtYXkgaG93ZXZlciB0cnkgYSB1dGlsaXR5IGNhbGxlZCAibXBpbmciIAogIGluc3RlYWQg
b2Ygbm9ybWFsICJwaW5nIi48L0ZPTlQ+IDwvUD4KICA8UD48Rk9OVCBzaXplPTI+cmVnYXJkcyw8
L0ZPTlQ+IDxCUj48Rk9OVCBzaXplPTI+UHJhc2hhbnQ8L0ZPTlQ+IDwvUD4KICA8UD48Rk9OVCBz
aXplPTI+LS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS08L0ZPTlQ+IDxCUj48Rk9OVCBzaXplPTI+
RnJvbTogCiAgcGltLWFkbWluQGlldGYub3JnIFs8QSAKICBocmVmPSJtYWlsdG86cGltLWFkbWlu
QGlldGYub3JnIj5tYWlsdG86cGltLWFkbWluQGlldGYub3JnPC9BPl1PbiBCZWhhbGYgCiAgT2Y8
L0ZPTlQ+IDxCUj48Rk9OVCBzaXplPTI+cGFyYXNAanVuaXBlci5uZXQ8L0ZPTlQ+IDxCUj48Rk9O
VCBzaXplPTI+U2VudDogCiAgVHVlc2RheSwgTWF5IDExLCAyMDA0IDc6MjIgQU08L0ZPTlQ+IDxC
Uj48Rk9OVCBzaXplPTI+VG86IEZhbWlsbGUgQumWjXNzZSAKICAuaHVhd2VpLmNvbTwvRk9OVD4g
PEJSPjxGT05UIHNpemU9Mj5DYzogcGltQGlldGYub3JnPC9GT05UPiA8QlI+PEZPTlQgCiAgc2l6
ZT0yPlN1YmplY3Q6IFJlOiBbcGltXSBWZXJ5IHNpbXBsZSBwaW1kIG11bHRpY2FzdCBjb25maWd1
cmF0aW9uPC9GT05UPiAKICA8L1A+PEJSPjxCUj4KICA8UD48Rk9OVCBzaXplPTI+Rmlyc3Qgb2Yg
YWxsLCB5b3UncmUgdXNpbmcgZ3JvdXAgYWRkciAyMjQuMC4wLjEgZm9yIAogIHRlc3RpbmcuPC9G
T05UPiA8QlI+PEZPTlQgc2l6ZT0yPkl0IGlzIGEgdmVyeSBzcGVjaWFsIGdyb3VwLCB3aGljaCwg
YWxvbmcgd2l0aCAKICBhbGwgb2YgMjI0LjAuMC4wLzI0PC9GT05UPiA8QlI+PEZPTlQgc2l6ZT0y
PndpbGwgbm90IGJlIGZvcndhcmRlZCBieSBhbnkgCiAgbXVsdGljYXN0IHJvdXRlci48L0ZPTlQ+
IDxCUj48Rk9OVCBzaXplPTI+SXQncyByZXNlcnZlZCBmb3IgbGluay1sb2NhbCAKICBtdWx0aWNh
c3QsPC9GT05UPiA8QlI+PEZPTlQgc2l6ZT0yPmZvciBwcm90b2NvbCBoZWxsb3MgYW5kIHN1Y2gs
IHRoYXQgYXJlIHRvIAogIGJlIHNlbnQgd2l0aCBUVEw9MS48L0ZPTlQ+IDwvUD4KICA8UD48Rk9O
VCBzaXplPTI+SG93ZXZlciwgSSBjYW4ndCB0ZWxsIHdoYXQgZWxzZSBpcyB3cm9uZywgaWYgeW91
J3JlIHVzaW5nIAogIG90aGVyPC9GT05UPiA8QlI+PEZPTlQgc2l6ZT0yPnZhbGlkIG11bHRpY2Fz
dCBkYXRhIGdyb3VwcyB0b28uIEF0IGxlYXN0LCB0aGUgCiAgZmlyc3QgdGhvdWdodCBpczwvRk9O
VD4gPEJSPjxGT05UIHNpemU9Mj50byBwb2ludCBvdXQgdGhlIGludmFsaWQgZ3JvdXAgdXNhZ2Ug
CiAgYWJvdmUuPC9GT05UPiA8L1A+CiAgPFA+PEZPTlQgc2l6ZT0yPi0gUGFyYXMuPC9GT05UPiA8
L1A+CiAgPFA+PEZPTlQgc2l6ZT0yPiZndDs8L0ZPTlQ+IDxCUj48Rk9OVCBzaXplPTI+Jmd0OyBI
aSw8L0ZPTlQ+IDxCUj48Rk9OVCAKICBzaXplPTI+Jmd0OzwvRk9OVD4gPEJSPjxGT05UIHNpemU9
Mj4mZ3Q7IENhbiBzb21lb25lIGNhbiBoZWxwLW1lIHRvIG1ha2UgYSAKICB2ZXJ5IHNpbXBsZSBt
dWx0aWNhc3QgY29uZmlndXJhdGlvbi48L0ZPTlQ+IDxCUj48Rk9OVCBzaXplPTI+Jmd0OzwvRk9O
VD4gCiAgPEJSPjxGT05UIHNpemU9Mj4mZ3Q7IEhlcmUgaXMgbXkgdGVzdCBjb25maWd1cmF0aW9u
Jm5ic3A7IChXaXRoIGp1c3Qgb25lIAogIFJvdXRlcik6PC9GT05UPiA8QlI+PEZPTlQgc2l6ZT0y
PiZndDs8L0ZPTlQ+IDxCUj48Rk9OVCBzaXplPTI+Jmd0OyBTZXJ2ZXIgCiAgLS0tLS0tLS0tLS0t
LS0tLU11bHRpY2FzdCBSb3V0ZXIgLS0tLS0tLS0tLS0tLS0tLS0tLS0tLUNsaWVudDwvRk9OVD4g
PEJSPjxGT05UIAogIHNpemU9Mj4mZ3Q7IFsxOTIuMTY4LjEuMSZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyAKICAxOTIuMTY4LjEuMjUwXSZuYnNwOyZuYnNwOyAKICBb
MTkyLjE2OC4wLjI1MCZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyAKICAxOTIuMTY4LjAuMV08L0ZPTlQ+IDxCUj48Rk9OVCBzaXplPTI+Jmd0OzwvRk9OVD4g
PEJSPjxGT05UIHNpemU9Mj4mZ3Q7IE5ldG1hc2sgCiAgaXMgMjU1LjI1NS4yNTUuMDwvRk9OVD4g
PEJSPjxGT05UIHNpemU9Mj4mZ3Q7IC9wcm9jL3N5cy9uZXQvaXB2NC9pcF9mb3J3YXJkIGlzIAog
IHNldCB0bzE8L0ZPTlQ+IDxCUj48Rk9OVCBzaXplPTI+Jmd0OyBSb3V0ZXIgaXMgTGludXggRmVk
b3JhIENvcmUgMSBXaXRoIAogIFBpbWQtMi4xLjAtYWxwaGEyOS0xODwvRk9OVD4gPEJSPjxGT05U
IHNpemU9Mj4mZ3Q7IElQX011bHRpY2FzdCBQSU0tU00gZXRjIGlzIAogIGFjdGl2YXRlIGJ5IGRl
ZmF1bHQgaW4ga2VybmVsLjwvRk9OVD4gPEJSPjxGT05UIHNpemU9Mj4mZ3Q7PC9GT05UPiA8QlI+
PEZPTlQgCiAgc2l6ZT0yPiZndDsgTXkgcm91dGVyIGlzIG9rIGZvciB1bmljYXN0LiBJIGNhbiBj
b21tdW5pY2F0ZSBmcm9tIHNlcnZlciB0byAKICBjbGllbnQuPC9GT05UPiA8QlI+PEZPTlQgc2l6
ZT0yPiZndDs8L0ZPTlQ+IDxCUj48Rk9OVCBzaXplPTI+Jmd0OyBCdXQgV2hlbiBpIAogIHdhbnQg
dG8gbWFrZSBNdWx0aWNhc3QgZnJvbSBTZXJ2ZXIgdG8gQ2xpZW50LCB0cmFmZmljIGlzIG5vdDwv
Rk9OVD4gPEJSPjxGT05UIAogIHNpemU9Mj4mZ3Q7IGZvcndhcmQgYnkgdGhlIHJvdXRlci5XaGVu
IGkgZG8gYSAicGluZyAtdCA1IDIyNC4wLjAuMSIgb24gTGludXggCiAgQ2xpZW50LDwvRk9OVD4g
PEJSPjxGT05UIHNpemU9Mj4mZ3Q7IHBhY2tldHMgYXJlIG5vdCBmb3J3YXJkcyB0byBMaW51eCBT
ZXJ2ZXIgCiAgYW5kIHZpY2UtdmVyc2EuPC9GT05UPiA8QlI+PEZPTlQgc2l6ZT0yPiZndDs8L0ZP
TlQ+IDxCUj48Rk9OVCBzaXplPTI+Jmd0OyBXaGF0IAogIHRvb2xzIGNhbiBpIHVzZSB0byBzZWUg
aWYgY29uZmlndXJhdGlvbiBpcyBPSyA/PC9GT05UPiA8QlI+PEZPTlQgc2l6ZT0yPiZndDsgCiAg
V2hhdCdzIGFib3V0IHBpbWQuY29uZiBjb25maWd1cmF0aW9uIGZpbGUgPzwvRk9OVD4gPEJSPjxG
T05UIAogIHNpemU9Mj4mZ3Q7PC9GT05UPiA8QlI+PEZPTlQgc2l6ZT0yPiZndDsgV2hlbiBpIGRv
IGEgImlwIG1yb3V0ZSBzaG93IiB0aGVyZSBpcyAKICBub3RoaW5nIHRvIHNlZSBpcyBpdCBub3Jt
YWwgPzwvRk9OVD4gPEJSPjxGT05UIHNpemU9Mj4mZ3Q7PC9GT05UPiA8QlI+PEZPTlQgCiAgc2l6
ZT0yPiZndDsgRG8geW91IGhhdmUgYW55IGlkZWEuPC9GT05UPiA8QlI+PEZPTlQgc2l6ZT0yPiZn
dDsgVGhhbmtzIGZvciB5b3VyIAogIGhlbHAuPC9GT05UPiA8QlI+PEZPTlQgc2l6ZT0yPiZndDs8
L0ZPTlQ+IDxCUj48Rk9OVCBzaXplPTI+Jmd0OyBCZXN0IAogIHJlZ2FyZHM8L0ZPTlQ+IDxCUj48
Rk9OVCBzaXplPTI+Jmd0OzwvRk9OVD4gPEJSPjxGT05UIHNpemU9Mj4mZ3Q7IENocmlzdG9waGUg
CiAgQumWjXNzZTwvRk9OVD4gPEJSPjxGT05UIHNpemU9Mj4mZ3Q7IEZyYW5jZTwvRk9OVD4gPEJS
PjxGT05UIHNpemU9Mj4mZ3Q7PC9GT05UPiAKICA8QlI+PEZPTlQgc2l6ZT0yPiZndDs8L0ZPTlQ+
IDxCUj48Rk9OVCBzaXplPTI+Jmd0OzwvRk9OVD4gPEJSPjxGT05UIAogIHNpemU9Mj4mZ3Q7PC9G
T05UPiA8QlI+PEZPTlQgc2l6ZT0yPiZndDsgCiAgX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX188L0ZPTlQ+IDxCUj48Rk9OVCBzaXplPTI+Jmd0OyAKICBwaW0g
bWFpbGluZyBsaXN0PC9GT05UPiA8QlI+PEZPTlQgc2l6ZT0yPiZndDsgcGltQGlldGYub3JnPC9G
T05UPiA8QlI+PEZPTlQgCiAgc2l6ZT0yPiZndDsgPEEgCiAgaHJlZj0iaHR0cHM6Ly93d3cxLmll
dGYub3JnL21haWxtYW4vbGlzdGluZm8vcGltIj5odHRwczovL3d3dzEuaWV0Zi5vcmcvbWFpbG1h
bi9saXN0aW5mby9waW08L0E+PC9GT05UPiAKICA8QlI+PEZPTlQgc2l6ZT0yPiZndDs8L0ZPTlQ+
IDwvUD48QlI+CiAgPFA+PEZPTlQgc2l6ZT0yPl9fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fPC9GT05UPiAKICA8QlI+PEZPTlQgc2l6ZT0yPnBpbSBtYWlsaW5n
IGxpc3Q8L0ZPTlQ+IDxCUj48Rk9OVCBzaXplPTI+cGltQGlldGYub3JnPC9GT05UPiAKICA8QlI+
PEZPTlQgc2l6ZT0yPjxBIAogIGhyZWY9Imh0dHBzOi8vd3d3MS5pZXRmLm9yZy9tYWlsbWFuL2xp
c3RpbmZvL3BpbSI+aHR0cHM6Ly93d3cxLmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vcGltPC9B
PjwvRk9OVD4gCiAgPC9QPjxCUj48QlI+CiAgPFA+PEZPTlQgc2l6ZT0yPl9fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fPC9GT05UPiAKICA8QlI+PEZPTlQgc2l6
ZT0yPnBpbSBtYWlsaW5nIGxpc3Q8L0ZPTlQ+IDxCUj48Rk9OVCBzaXplPTI+cGltQGlldGYub3Jn
PC9GT05UPiAKICA8QlI+PEZPTlQgc2l6ZT0yPjxBIAogIGhyZWY9Imh0dHBzOi8vd3d3MS5pZXRm
Lm9yZy9tYWlsbWFuL2xpc3RpbmZvL3BpbSI+aHR0cHM6Ly93d3cxLmlldGYub3JnL21haWxtYW4v
bGlzdGluZm8vcGltPC9BPjwvRk9OVD4gCiAgPC9QPjwvQkxPQ0tRVU9URT4KCjwvQk9EWT4KPC9I
VE1MPg==

------_=_NextPart_001_01C4372A.5E8DFD67--

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



From pim-admin@ietf.org  Tue May 11 06:11:16 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA16466
	for <pim-archive@lists.ietf.org>; Tue, 11 May 2004 06:11:16 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNU1Y-0005lk-49; Tue, 11 May 2004 05:58:08 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNTxD-0004Nj-0O
	for pim@optimus.ietf.org; Tue, 11 May 2004 05:53:39 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA15529
	for <pim@ietf.org>; Tue, 11 May 2004 05:53:35 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BNTx9-0006dQ-EK
	for pim@ietf.org; Tue, 11 May 2004 05:53:35 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNTwF-0006HT-00
	for pim@ietf.org; Tue, 11 May 2004 05:52:39 -0400
Received: from netcore.fi ([193.94.160.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNTvN-0005aI-00
	for pim@ietf.org; Tue, 11 May 2004 05:51:45 -0400
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id i4B9p7V18588;
	Tue, 11 May 2004 12:51:07 +0300
Date: Tue, 11 May 2004 12:51:07 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: Mike McBride <mmcbride@cisco.com>
cc: pim@ietf.org
Subject: Re: [pim] WG Last Call - draft-ietf-pim-bidir-06
In-Reply-To: <Pine.GSO.4.58.0404281220260.8177@irp-view6.cisco.com>
Message-ID: <Pine.LNX.4.44.0405111246510.17589-100000@netcore.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: pim-admin@ietf.org
Errors-To: pim-admin@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Id: Protocol Independent Multicast <pim.ietf.org>
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>

Hi,

On Wed, 28 Apr 2004, Mike McBride wrote:
> Today begins a Working Group Last Call for the Bi-Directional PIM
> Specification. The Last Call runs 2 weeks from Wednesday, April 28th, 2004
> to Wednesday, May 12th, 2004.

There was a lengthy discussion at MBONED how Bidir could or could not 
be modified to support Embedded-RP (and the feasibility of different 
approaches).

I'd like to get an explicit feel what people in this WG think we
should do with regard to the bidir-PIM spec:
 
 1) try to figure out (at least some of) the details of 
    embedded-RP now,

 2) try to work on this later, if necessary (with the caveat that then 
    modifications might be difficult or impossible as they'd have to 
    be backward-compatible), or

 3) do something else, what?

-- 
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 exim@www1.ietf.org  Tue May 11 06:25:03 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA17084
	for <pim-archive@odin.ietf.org>; Tue, 11 May 2004 06:25:03 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNUM2-0003Lz-Bp
	for pim-archive@odin.ietf.org; Tue, 11 May 2004 06:19:18 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4BAJIAD012891
	for pim-archive@odin.ietf.org; Tue, 11 May 2004 06:19:18 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNUFm-0001Hl-Cc
	for pim-web-archive@optimus.ietf.org; Tue, 11 May 2004 06:12:50 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA16561
	for <pim-web-archive@ietf.org>; Tue, 11 May 2004 06:12:46 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BNUFi-0006Ah-MG
	for pim-web-archive@ietf.org; Tue, 11 May 2004 06:12:46 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNUEn-0005mK-00
	for pim-web-archive@ietf.org; Tue, 11 May 2004 06:11:50 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNUDn-0005PK-00
	for pim-web-archive@ietf.org; Tue, 11 May 2004 06:10:47 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNU1Y-0005lk-49; Tue, 11 May 2004 05:58:08 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNTxD-0004Nj-0O
	for pim@optimus.ietf.org; Tue, 11 May 2004 05:53:39 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA15529
	for <pim@ietf.org>; Tue, 11 May 2004 05:53:35 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BNTx9-0006dQ-EK
	for pim@ietf.org; Tue, 11 May 2004 05:53:35 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNTwF-0006HT-00
	for pim@ietf.org; Tue, 11 May 2004 05:52:39 -0400
Received: from netcore.fi ([193.94.160.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNTvN-0005aI-00
	for pim@ietf.org; Tue, 11 May 2004 05:51:45 -0400
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id i4B9p7V18588;
	Tue, 11 May 2004 12:51:07 +0300
Date: Tue, 11 May 2004 12:51:07 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: Mike McBride <mmcbride@cisco.com>
cc: pim@ietf.org
Subject: Re: [pim] WG Last Call - draft-ietf-pim-bidir-06
In-Reply-To: <Pine.GSO.4.58.0404281220260.8177@irp-view6.cisco.com>
Message-ID: <Pine.LNX.4.44.0405111246510.17589-100000@netcore.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: pim-admin@ietf.org
Errors-To: pim-admin@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Id: Protocol Independent Multicast <pim.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60

Hi,

On Wed, 28 Apr 2004, Mike McBride wrote:
> Today begins a Working Group Last Call for the Bi-Directional PIM
> Specification. The Last Call runs 2 weeks from Wednesday, April 28th, 2004
> to Wednesday, May 12th, 2004.

There was a lengthy discussion at MBONED how Bidir could or could not 
be modified to support Embedded-RP (and the feasibility of different 
approaches).

I'd like to get an explicit feel what people in this WG think we
should do with regard to the bidir-PIM spec:
 
 1) try to figure out (at least some of) the details of 
    embedded-RP now,

 2) try to work on this later, if necessary (with the caveat that then 
    modifications might be difficult or impossible as they'd have to 
    be backward-compatible), or

 3) do something else, what?

-- 
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-admin@ietf.org  Tue May 11 13:47:03 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11630
	for <pim-archive@lists.ietf.org>; Tue, 11 May 2004 13:47:03 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNb5t-00043T-EI; Tue, 11 May 2004 13:31:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNavF-00019Y-0A
	for pim@optimus.ietf.org; Tue, 11 May 2004 13:20:05 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09811
	for <pim@ietf.org>; Tue, 11 May 2004 13:20:02 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BNavD-0007ky-1x
	for pim@ietf.org; Tue, 11 May 2004 13:20:03 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNauK-0007Lz-00
	for pim@ietf.org; Tue, 11 May 2004 13:19:08 -0400
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNatr-0006vf-00
	for pim@ietf.org; Tue, 11 May 2004 13:18:40 -0400
Received: from sj-core-5.cisco.com (171.71.177.238)
  by sj-iport-5.cisco.com with ESMTP; 11 May 2004 10:18:01 -0700
Received: from mira-sjc5-b.cisco.com (IDENT:mirapoint@mira-sjc5-b.cisco.com [171.71.163.14])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id i4BHI6W9008106;
	Tue, 11 May 2004 10:18:07 -0700 (PDT)
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 ATB59882;
	Tue, 11 May 2004 10:17:19 -0700 (PDT)
Date: Tue, 11 May 2004 10:18:06 -0700 (PDT)
From: Mike McBride <mmcbride@cisco.com>
To: Pekka Savola <pekkas@netcore.fi>
cc: pim@ietf.org
Subject: Re: [pim] WG Last Call - draft-ietf-pim-bidir-06
In-Reply-To: <Pine.LNX.4.44.0405111246510.17589-100000@netcore.fi>
Message-ID: <Pine.GSO.4.58.0405111007550.18183@irp-view6.cisco.com>
References: <Pine.LNX.4.44.0405111246510.17589-100000@netcore.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: pim-admin@ietf.org
Errors-To: pim-admin@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Id: Protocol Independent Multicast <pim.ietf.org>
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>

Pekka,

On Tue, 11 May 2004, Pekka Savola wrote:

> Hi,
>
> On Wed, 28 Apr 2004, Mike McBride wrote:
> > Today begins a Working Group Last Call for the Bi-Directional PIM
> > Specification. The Last Call runs 2 weeks from Wednesday, April 28th, 2004
> > to Wednesday, May 12th, 2004.
>
> There was a lengthy discussion at MBONED how Bidir could or could not
> be modified to support Embedded-RP (and the feasibility of different
> approaches).
>
> I'd like to get an explicit feel what people in this WG think we
> should do with regard to the bidir-PIM spec:
>
>  1) try to figure out (at least some of) the details of
>     embedded-RP now,
>
>  2) try to work on this later, if necessary (with the caveat that then
>     modifications might be difficult or impossible as they'd have to
>     be backward-compatible), or
>
>  3) do something else, what?

2/3) How about a new bidir w/embedded RP or bidirv2 type draft is
written. And we allow this -06 to proceed.

thanks,
mike

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


From exim@www1.ietf.org  Tue May 11 14:02:31 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA12764
	for <pim-archive@odin.ietf.org>; Tue, 11 May 2004 14:02:31 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNbTS-0001Xa-Kd
	for pim-archive@odin.ietf.org; Tue, 11 May 2004 13:55:26 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4BHtQ9S005922
	for pim-archive@odin.ietf.org; Tue, 11 May 2004 13:55:26 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNbMV-0008R1-Q3
	for pim-web-archive@optimus.ietf.org; Tue, 11 May 2004 13:48:15 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11761
	for <pim-web-archive@ietf.org>; Tue, 11 May 2004 13:48:13 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BNbMT-0004WK-KY
	for pim-web-archive@ietf.org; Tue, 11 May 2004 13:48:13 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNbLe-000457-00
	for pim-web-archive@ietf.org; Tue, 11 May 2004 13:47:23 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNbKr-0003e0-00
	for pim-web-archive@ietf.org; Tue, 11 May 2004 13:46:33 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNb5t-00043T-EI; Tue, 11 May 2004 13:31:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNavF-00019Y-0A
	for pim@optimus.ietf.org; Tue, 11 May 2004 13:20:05 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09811
	for <pim@ietf.org>; Tue, 11 May 2004 13:20:02 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BNavD-0007ky-1x
	for pim@ietf.org; Tue, 11 May 2004 13:20:03 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNauK-0007Lz-00
	for pim@ietf.org; Tue, 11 May 2004 13:19:08 -0400
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNatr-0006vf-00
	for pim@ietf.org; Tue, 11 May 2004 13:18:40 -0400
Received: from sj-core-5.cisco.com (171.71.177.238)
  by sj-iport-5.cisco.com with ESMTP; 11 May 2004 10:18:01 -0700
Received: from mira-sjc5-b.cisco.com (IDENT:mirapoint@mira-sjc5-b.cisco.com [171.71.163.14])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id i4BHI6W9008106;
	Tue, 11 May 2004 10:18:07 -0700 (PDT)
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 ATB59882;
	Tue, 11 May 2004 10:17:19 -0700 (PDT)
Date: Tue, 11 May 2004 10:18:06 -0700 (PDT)
From: Mike McBride <mmcbride@cisco.com>
To: Pekka Savola <pekkas@netcore.fi>
cc: pim@ietf.org
Subject: Re: [pim] WG Last Call - draft-ietf-pim-bidir-06
In-Reply-To: <Pine.LNX.4.44.0405111246510.17589-100000@netcore.fi>
Message-ID: <Pine.GSO.4.58.0405111007550.18183@irp-view6.cisco.com>
References: <Pine.LNX.4.44.0405111246510.17589-100000@netcore.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: pim-admin@ietf.org
Errors-To: pim-admin@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Id: Protocol Independent Multicast <pim.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60

Pekka,

On Tue, 11 May 2004, Pekka Savola wrote:

> Hi,
>
> On Wed, 28 Apr 2004, Mike McBride wrote:
> > Today begins a Working Group Last Call for the Bi-Directional PIM
> > Specification. The Last Call runs 2 weeks from Wednesday, April 28th, 2004
> > to Wednesday, May 12th, 2004.
>
> There was a lengthy discussion at MBONED how Bidir could or could not
> be modified to support Embedded-RP (and the feasibility of different
> approaches).
>
> I'd like to get an explicit feel what people in this WG think we
> should do with regard to the bidir-PIM spec:
>
>  1) try to figure out (at least some of) the details of
>     embedded-RP now,
>
>  2) try to work on this later, if necessary (with the caveat that then
>     modifications might be difficult or impossible as they'd have to
>     be backward-compatible), or
>
>  3) do something else, what?

2/3) How about a new bidir w/embedded RP or bidirv2 type draft is
written. And we allow this -06 to proceed.

thanks,
mike

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



From pim-admin@ietf.org  Tue May 11 19:36:07 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA06441
	for <pim-archive@lists.ietf.org>; Tue, 11 May 2004 19:36:07 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNgfJ-0006YD-4L; Tue, 11 May 2004 19:28:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNgaq-0005uE-Cs
	for pim@optimus.ietf.org; Tue, 11 May 2004 19:23:24 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA05935
	for <pim@ietf.org>; Tue, 11 May 2004 19:23:22 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BNgao-0004f7-Ro
	for pim@ietf.org; Tue, 11 May 2004 19:23:22 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNgZv-0004Ff-00
	for pim@ietf.org; Tue, 11 May 2004 19:22:27 -0400
Received: from smtp1.procket.com ([65.174.124.36])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNgZI-0003nj-00
	for pim@ietf.org; Tue, 11 May 2004 19:21:48 -0400
Received: from miata.procket.com (mil0-fw00-d-1.procket.com [65.174.124.60])
	by smtp1.procket.com (8.12.8p1/8.12.1) with ESMTP id i4C1WRpL054511;
	Tue, 11 May 2004 18:32:27 -0700 (PDT)
Received: from dino-pc.procket.com (dino-pc.procket.com [10.4.17.33])
	by miata.procket.com (8.12.1/8.12.1) with ESMTP id i4BNL3d1022153;
	Tue, 11 May 2004 16:21:03 -0700 (PDT)
Received: (from dino@localhost)
	by dino-pc.procket.com (8.12.1/8.12.1) id i4BNL3LZ005650;
	Tue, 11 May 2004 16:21:03 -0700
Date: Tue, 11 May 2004 16:21:03 -0700
Message-Id: <200405112321.i4BNL3LZ005650@dino-pc.procket.com>
From: Dino Farinacci <dino@procket.com>
To: pekkas@netcore.fi
CC: mmcbride@cisco.com, pim@ietf.org
In-reply-to: <Pine.LNX.4.44.0405111246510.17589-100000@netcore.fi> (message
	from Pekka Savola on Tue, 11 May 2004 12:51:07 +0300 (EEST))
Subject: Re: [pim] WG Last Call - draft-ietf-pim-bidir-06
References: <Pine.LNX.4.44.0405111246510.17589-100000@netcore.fi>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: pim-admin@ietf.org
Errors-To: pim-admin@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Id: Protocol Independent Multicast <pim.ietf.org>
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>

>>  2) try to work on this later, if necessary (with the caveat that then 
>>     modifications might be difficult or impossible as they'd have to 
>>     be backward-compatible), or

    I vote for this.

Dino

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


From pim-admin@ietf.org  Tue May 11 19:40:12 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA06755
	for <pim-archive@lists.ietf.org>; Tue, 11 May 2004 19:40:12 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNgm5-0008C9-Ml; Tue, 11 May 2004 19:35:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNgdc-0006Dx-QH
	for pim@optimus.ietf.org; Tue, 11 May 2004 19:26:16 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA05960
	for <pim@ietf.org>; Tue, 11 May 2004 19:26:15 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BNgdb-0005to-7f
	for pim@ietf.org; Tue, 11 May 2004 19:26:15 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNgca-0005Tp-00
	for pim@ietf.org; Tue, 11 May 2004 19:25:12 -0400
Received: from sj-iport-1-in.cisco.com ([171.71.176.70] helo=sj-iport-1.cisco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNgbS-0004fq-00
	for pim@ietf.org; Tue, 11 May 2004 19:24:02 -0400
Received: from cypher.cisco.com (cypher.cisco.com [171.69.11.143])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id i4BNNVC1029597;
	Tue, 11 May 2004 16:23:31 -0700 (PDT)
Received: from localhost (kouvelas@localhost)
	by cypher.cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) with ESMTP id QAA13982;
	Tue, 11 May 2004 16:23:30 -0700 (PDT)
Message-Id: <200405112323.QAA13982@cypher.cisco.com>
To: Pekka Savola <pekkas@netcore.fi>
cc: Mike McBride <mmcbride@cisco.com>, pim@ietf.org, lorenzo@cypher.cisco.com
Subject: Re: [pim] WG Last Call - draft-ietf-pim-bidir-06 
In-reply-to: Your message of "Tue, 11 May 2004 12:51:07 +0300."
             <Pine.LNX.4.44.0405111246510.17589-100000@netcore.fi> 
Date: Tue, 11 May 2004 16:23:30 -0700
From: Isidor Kouvelas <kouvelas@cisco.com>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: pim-admin@ietf.org
Errors-To: pim-admin@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Id: Protocol Independent Multicast <pim.ietf.org>
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>


I agree with Mike that we should not try to modify the current
specification to include embedded-RP functionality and we should
address this in a separate (possibly non backward compatible) revision
if necessary. The current specification has been fairly stable for a
while and reflects at least 2 shipping implementations.

Isidor

Pekka Savola writes:
>Hi,
>
>On Wed, 28 Apr 2004, Mike McBride wrote:
>> Today begins a Working Group Last Call for the Bi-Directional PIM
>> Specification. The Last Call runs 2 weeks from Wednesday, April 28th, 2004
>> to Wednesday, May 12th, 2004.
>
>There was a lengthy discussion at MBONED how Bidir could or could not 
>be modified to support Embedded-RP (and the feasibility of different 
>approaches).
>
>I'd like to get an explicit feel what people in this WG think we
>should do with regard to the bidir-PIM spec:
> 
> 1) try to figure out (at least some of) the details of 
>    embedded-RP now,
>
> 2) try to work on this later, if necessary (with the caveat that then 
>    modifications might be difficult or impossible as they'd have to 
>    be backward-compatible), or
>
> 3) do something else, what?
>
>-- 
>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
>

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


From exim@www1.ietf.org  Tue May 11 19:57:54 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA07599
	for <pim-archive@odin.ietf.org>; Tue, 11 May 2004 19:57:54 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNh0b-0002sA-2d
	for pim-archive@odin.ietf.org; Tue, 11 May 2004 19:50:01 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4BNo1bi011031
	for pim-archive@odin.ietf.org; Tue, 11 May 2004 19:50:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNgoa-0000dG-2X
	for pim-web-archive@optimus.ietf.org; Tue, 11 May 2004 19:37:36 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA06618
	for <pim-web-archive@ietf.org>; Tue, 11 May 2004 19:37:34 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BNgoY-0003Bq-BU
	for pim-web-archive@ietf.org; Tue, 11 May 2004 19:37:34 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNgng-0002iC-00
	for pim-web-archive@ietf.org; Tue, 11 May 2004 19:36:41 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNgmf-0002C8-00
	for pim-web-archive@ietf.org; Tue, 11 May 2004 19:35:37 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNgfJ-0006YD-4L; Tue, 11 May 2004 19:28:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNgaq-0005uE-Cs
	for pim@optimus.ietf.org; Tue, 11 May 2004 19:23:24 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA05935
	for <pim@ietf.org>; Tue, 11 May 2004 19:23:22 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BNgao-0004f7-Ro
	for pim@ietf.org; Tue, 11 May 2004 19:23:22 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNgZv-0004Ff-00
	for pim@ietf.org; Tue, 11 May 2004 19:22:27 -0400
Received: from smtp1.procket.com ([65.174.124.36])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNgZI-0003nj-00
	for pim@ietf.org; Tue, 11 May 2004 19:21:48 -0400
Received: from miata.procket.com (mil0-fw00-d-1.procket.com [65.174.124.60])
	by smtp1.procket.com (8.12.8p1/8.12.1) with ESMTP id i4C1WRpL054511;
	Tue, 11 May 2004 18:32:27 -0700 (PDT)
Received: from dino-pc.procket.com (dino-pc.procket.com [10.4.17.33])
	by miata.procket.com (8.12.1/8.12.1) with ESMTP id i4BNL3d1022153;
	Tue, 11 May 2004 16:21:03 -0700 (PDT)
Received: (from dino@localhost)
	by dino-pc.procket.com (8.12.1/8.12.1) id i4BNL3LZ005650;
	Tue, 11 May 2004 16:21:03 -0700
Date: Tue, 11 May 2004 16:21:03 -0700
Message-Id: <200405112321.i4BNL3LZ005650@dino-pc.procket.com>
From: Dino Farinacci <dino@procket.com>
To: pekkas@netcore.fi
CC: mmcbride@cisco.com, pim@ietf.org
In-reply-to: <Pine.LNX.4.44.0405111246510.17589-100000@netcore.fi> (message
	from Pekka Savola on Tue, 11 May 2004 12:51:07 +0300 (EEST))
Subject: Re: [pim] WG Last Call - draft-ietf-pim-bidir-06
References: <Pine.LNX.4.44.0405111246510.17589-100000@netcore.fi>
Sender: pim-admin@ietf.org
Errors-To: pim-admin@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Id: Protocol Independent Multicast <pim.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60

>>  2) try to work on this later, if necessary (with the caveat that then 
>>     modifications might be difficult or impossible as they'd have to 
>>     be backward-compatible), or

    I vote for this.

Dino

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



From exim@www1.ietf.org  Tue May 11 19:58:44 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA07685
	for <pim-archive@odin.ietf.org>; Tue, 11 May 2004 19:58:44 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNh0e-0002v4-K6
	for pim-archive@odin.ietf.org; Tue, 11 May 2004 19:50:05 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4BNo4iO011208
	for pim-archive@odin.ietf.org; Tue, 11 May 2004 19:50:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNgsB-0001Bo-OE
	for pim-web-archive@optimus.ietf.org; Tue, 11 May 2004 19:41:19 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA06817
	for <pim-web-archive@ietf.org>; Tue, 11 May 2004 19:41:18 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BNgsA-0004ur-2B
	for pim-web-archive@ietf.org; Tue, 11 May 2004 19:41:18 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNgrF-0004Uy-00
	for pim-web-archive@ietf.org; Tue, 11 May 2004 19:40:21 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNgqc-00045D-00
	for pim-web-archive@ietf.org; Tue, 11 May 2004 19:39:42 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNgm5-0008C9-Ml; Tue, 11 May 2004 19:35:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNgdc-0006Dx-QH
	for pim@optimus.ietf.org; Tue, 11 May 2004 19:26:16 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA05960
	for <pim@ietf.org>; Tue, 11 May 2004 19:26:15 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BNgdb-0005to-7f
	for pim@ietf.org; Tue, 11 May 2004 19:26:15 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNgca-0005Tp-00
	for pim@ietf.org; Tue, 11 May 2004 19:25:12 -0400
Received: from sj-iport-1-in.cisco.com ([171.71.176.70] helo=sj-iport-1.cisco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNgbS-0004fq-00
	for pim@ietf.org; Tue, 11 May 2004 19:24:02 -0400
Received: from cypher.cisco.com (cypher.cisco.com [171.69.11.143])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id i4BNNVC1029597;
	Tue, 11 May 2004 16:23:31 -0700 (PDT)
Received: from localhost (kouvelas@localhost)
	by cypher.cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) with ESMTP id QAA13982;
	Tue, 11 May 2004 16:23:30 -0700 (PDT)
Message-Id: <200405112323.QAA13982@cypher.cisco.com>
To: Pekka Savola <pekkas@netcore.fi>
cc: Mike McBride <mmcbride@cisco.com>, pim@ietf.org, lorenzo@cypher.cisco.com
Subject: Re: [pim] WG Last Call - draft-ietf-pim-bidir-06 
In-reply-to: Your message of "Tue, 11 May 2004 12:51:07 +0300."
             <Pine.LNX.4.44.0405111246510.17589-100000@netcore.fi> 
Date: Tue, 11 May 2004 16:23:30 -0700
From: Isidor Kouvelas <kouvelas@cisco.com>
Sender: pim-admin@ietf.org
Errors-To: pim-admin@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Id: Protocol Independent Multicast <pim.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60


I agree with Mike that we should not try to modify the current
specification to include embedded-RP functionality and we should
address this in a separate (possibly non backward compatible) revision
if necessary. The current specification has been fairly stable for a
while and reflects at least 2 shipping implementations.

Isidor

Pekka Savola writes:
>Hi,
>
>On Wed, 28 Apr 2004, Mike McBride wrote:
>> Today begins a Working Group Last Call for the Bi-Directional PIM
>> Specification. The Last Call runs 2 weeks from Wednesday, April 28th, 2004
>> to Wednesday, May 12th, 2004.
>
>There was a lengthy discussion at MBONED how Bidir could or could not 
>be modified to support Embedded-RP (and the feasibility of different 
>approaches).
>
>I'd like to get an explicit feel what people in this WG think we
>should do with regard to the bidir-PIM spec:
> 
> 1) try to figure out (at least some of) the details of 
>    embedded-RP now,
>
> 2) try to work on this later, if necessary (with the caveat that then 
>    modifications might be difficult or impossible as they'd have to 
>    be backward-compatible), or
>
> 3) do something else, what?
>
>-- 
>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
>

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



From pim-admin@ietf.org  Thu May 13 10:39:18 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA16420
	for <pim-archive@lists.ietf.org>; Thu, 13 May 2004 10:39:18 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BOHIc-0004oM-V7; Thu, 13 May 2004 10:35:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BOHE4-0003Vm-KS
	for pim@optimus.ietf.org; Thu, 13 May 2004 10:30:20 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA15833
	for <pim@ietf.org>; Thu, 13 May 2004 10:30:16 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BOHE1-0004Es-P8
	for pim@ietf.org; Thu, 13 May 2004 10:30:17 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BOHD6-0003h6-00
	for pim@ietf.org; Thu, 13 May 2004 10:29:21 -0400
Received: from bay9-dav12.bay9.hotmail.com ([64.4.46.116] helo=hotmail.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BOHCJ-00035F-00
	for pim@ietf.org; Thu, 13 May 2004 10:28:31 -0400
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	 Thu, 13 May 2004 07:27:57 -0700
Received: from 202.84.17.41 by bay9-dav12.bay9.hotmail.com with DAV;
	Thu, 13 May 2004 14:27:56 +0000
X-Originating-IP: [202.84.17.41]
X-Originating-Email: [wlq_w@hotmail.com]
X-Sender: wlq_w@hotmail.com
Date: Thu, 13 May 2004 22:29:11 +0800
From: "wlq" <wlq_w@hotmail.com>
To: "=?gb2312?B?RmFtaWxsZV9C6WFzc2U=?=" <beasse.pordic@wanadoo.fr>,
        "pim" <pim@ietf.org>
Subject: Re: [pim] Very simple pimd multicast configuration
X-mailer: Foxmail 5.0 [cn]
Mime-Version: 1.0
Content-Type: text/plain;
	charset="gb2312"
Content-Transfer-Encoding: base64
Message-ID: <BAY9-DAV12AOqN14jy70001d46e@hotmail.com>
X-OriginalArrivalTime: 13 May 2004 14:27:57.0199 (UTC) FILETIME=[7C50B1F0:01C438F6]
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=1.1 required=5.0 tests=MIME_BASE64_TEXT autolearn=no 
	version=2.60
Content-Transfer-Encoding: base64
Sender: pim-admin@ietf.org
Errors-To: pim-admin@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Id: Protocol Independent Multicast <pim.ietf.org>
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-Transfer-Encoding: base64

RmFtaWxsZV9C6WFzc2UsxPq6w6OhDQoNCglFeGNlcHQgeW91IHRyeSB0byB1c2UgbXBpbmcgaW5z
dGVhZCBvZiBwaW5nLHlvdSBzaG91bGQgZmlyc3RseSBsZXQgdGhlIHNlcnZlci9jbGllbnQgY2Fu
IHNlbmQgaWdtcCByZXNwb25zZSBtZXNzYWdlIHRvIHRoZSByb3V0ZXIsc28gdGhlIHJvdXRlciBr
bm93cyBpdCBoYXMgYSBtZW1iZXIgam9pbiB0aGUgbXVsdGljYXN0IGdyb3VwLg0KICAgIElmIHRo
ZSBzb3VyY2UgaGFzIHNlbnQgbXVsdGljYXN0IHBhY2tldHMseW91IHVzZSAiaXAgbXJvdXRlIHNo
b3ciIGFuZCBzaG91bGQgc2VlIHRoZSBtcm91dGUgdGFibGUgY3JlYXRlZC4NCiAgICBBbmQgSSB0
aGluayBpZiB5b3UgdXNlIGEgbm9ybWFsIG11bHRpY2FzdCBhZGRyZXNzIHN1Y2ggYXMgMjI1LjEu
MS4xMDAgaXQgd2lsbCBiZSBiZXR0ZXIuDQoNCj09PT09PT0gMjAwNC0wNS0wOSAyMzoxMDo0OSDE
+tTawLTQxdbQ0LS1wKO6PT09PT09PQ0KDQo+SGksDQo+DQo+Q2FuIHNvbWVvbmUgY2FuIGhlbHAt
bWUgdG8gbWFrZSBhIHZlcnkgc2ltcGxlIG11bHRpY2FzdCBjb25maWd1cmF0aW9uLg0KPg0KPkhl
cmUgaXMgbXkgdGVzdCBjb25maWd1cmF0aW9uICAoV2l0aCBqdXN0IG9uZSBSb3V0ZXIpOg0KPg0K
PlNlcnZlciAtLS0tLS0tLS0tLS0tLS0tTXVsdGljYXN0IFJvdXRlciAtLS0tLS0tLS0tLS0tLS0t
LS0tLS0tQ2xpZW50DQo+WzE5Mi4xNjguMS4xICAgICAgICAxOTIuMTY4LjEuMjUwXSAgIFsxOTIu
MTY4LjAuMjUwICAgICAgICAgMTkyLjE2OC4wLjFdDQo+DQo+TmV0bWFzayBpcyAyNTUuMjU1LjI1
NS4wDQo+L3Byb2Mvc3lzL25ldC9pcHY0L2lwX2ZvcndhcmQgaXMgc2V0IHRvMQ0KPlJvdXRlciBp
cyBMaW51eCBGZWRvcmEgQ29yZSAxIFdpdGggUGltZC0yLjEuMC1hbHBoYTI5LTE4DQo+SVBfTXVs
dGljYXN0IFBJTS1TTSBldGMgaXMgYWN0aXZhdGUgYnkgZGVmYXVsdCBpbiBrZXJuZWwuDQo+DQo+
TXkgcm91dGVyIGlzIG9rIGZvciB1bmljYXN0LiBJIGNhbiBjb21tdW5pY2F0ZSBmcm9tIHNlcnZl
ciB0byBjbGllbnQuDQo+DQo+QnV0IFdoZW4gaSB3YW50IHRvIG1ha2UgTXVsdGljYXN0IGZyb20g
U2VydmVyIHRvIENsaWVudCwgdHJhZmZpYyBpcyBub3QNCj5mb3J3YXJkIGJ5IHRoZSByb3V0ZXIu
V2hlbiBpIGRvIGEgInBpbmcgLXQgNSAyMjQuMC4wLjEiIG9uIExpbnV4IENsaWVudCwNCj5wYWNr
ZXRzIGFyZSBub3QgZm9yd2FyZHMgdG8gTGludXggU2VydmVyIGFuZCB2aWNlLXZlcnNhLg0KPg0K
PldoYXQgdG9vbHMgY2FuIGkgdXNlIHRvIHNlZSBpZiBjb25maWd1cmF0aW9uIGlzIE9LID8NCj5X
aGF0J3MgYWJvdXQgcGltZC5jb25mIGNvbmZpZ3VyYXRpb24gZmlsZSA/DQo+DQo+V2hlbiBpIGRv
IGEgImlwIG1yb3V0ZSBzaG93IiB0aGVyZSBpcyBub3RoaW5nIHRvIHNlZSBpcyBpdCBub3JtYWwg
Pw0KPg0KPkRvIHlvdSBoYXZlIGFueSBpZGVhLg0KPlRoYW5rcyBmb3IgeW91ciBoZWxwLg0KPg0K
PkJlc3QgcmVnYXJkcw0KPg0KPkNocmlzdG9waGUgQulhc3NlDQo+RnJhbmNlDQo+DQo+DQo+DQo+
DQo+X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCj5waW0g
bWFpbGluZyBsaXN0DQo+cGltQGlldGYub3JnDQo+aHR0cHM6Ly93d3cxLmlldGYub3JnL21haWxt
YW4vbGlzdGluZm8vcGltDQoNCj0gPSA9ID0gPSA9ID0gPSA9ID0gPSA9ID0gPSA9ID0gPSA9ID0g
PQ0KCQkJDQoNCqGhoaGhoaGhoaGhoaGhoaHWwg0KwPGjoQ0KIA0KCQkJCSANCqGhoaGhoaGhoaGh
oaGhoaF3bHENCqGhoaGhoaGhoaGhoaGhoaF3bHFfd0Bob3RtYWlsLmNvbQ0KoaGhoaGhoaGhoaGh
oaGhoaGhoaEyMDA0LTA1LTEzDQoNCg==

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


From exim@www1.ietf.org  Thu May 13 10:48:31 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA16978
	for <pim-archive@odin.ietf.org>; Thu, 13 May 2004 10:48:31 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BOHUG-0008FE-19
	for pim-archive@odin.ietf.org; Thu, 13 May 2004 10:47:04 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4DEl4pq031693
	for pim-archive@odin.ietf.org; Thu, 13 May 2004 10:47:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BOHOT-0006bb-Cg
	for pim-web-archive@optimus.ietf.org; Thu, 13 May 2004 10:41:05 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA16531
	for <pim-web-archive@ietf.org>; Thu, 13 May 2004 10:41:01 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BOHOR-0002Vr-5w
	for pim-web-archive@ietf.org; Thu, 13 May 2004 10:41:03 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BOHNO-0001wd-00
	for pim-web-archive@ietf.org; Thu, 13 May 2004 10:39:59 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BOHMI-00017F-00
	for pim-web-archive@ietf.org; Thu, 13 May 2004 10:38:50 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BOHIc-0004oM-V7; Thu, 13 May 2004 10:35:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BOHE4-0003Vm-KS
	for pim@optimus.ietf.org; Thu, 13 May 2004 10:30:20 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA15833
	for <pim@ietf.org>; Thu, 13 May 2004 10:30:16 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BOHE1-0004Es-P8
	for pim@ietf.org; Thu, 13 May 2004 10:30:17 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BOHD6-0003h6-00
	for pim@ietf.org; Thu, 13 May 2004 10:29:21 -0400
Received: from bay9-dav12.bay9.hotmail.com ([64.4.46.116] helo=hotmail.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BOHCJ-00035F-00
	for pim@ietf.org; Thu, 13 May 2004 10:28:31 -0400
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	 Thu, 13 May 2004 07:27:57 -0700
Received: from 202.84.17.41 by bay9-dav12.bay9.hotmail.com with DAV;
	Thu, 13 May 2004 14:27:56 +0000
X-Originating-IP: [202.84.17.41]
X-Originating-Email: [wlq_w@hotmail.com]
X-Sender: wlq_w@hotmail.com
Date: Thu, 13 May 2004 22:29:11 +0800
From: "wlq" <wlq_w@hotmail.com>
To: "=?gb2312?B?RmFtaWxsZV9C6WFzc2U=?=" <beasse.pordic@wanadoo.fr>,
        "pim" <pim@ietf.org>
Subject: Re: [pim] Very simple pimd multicast configuration
X-mailer: Foxmail 5.0 [cn]
Mime-Version: 1.0
Content-Type: text/plain;
	charset="gb2312"
Content-Transfer-Encoding: base64
Message-ID: <BAY9-DAV12AOqN14jy70001d46e@hotmail.com>
X-OriginalArrivalTime: 13 May 2004 14:27:57.0199 (UTC) FILETIME=[7C50B1F0:01C438F6]
Content-Transfer-Encoding: base64
Sender: pim-admin@ietf.org
Errors-To: pim-admin@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Id: Protocol Independent Multicast <pim.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=1.1 required=5.0 tests=MIME_BASE64_TEXT autolearn=no 
	version=2.60
Content-Transfer-Encoding: base64
Content-Transfer-Encoding: base64

RmFtaWxsZV9C6WFzc2UsxPq6w6OhDQoNCglFeGNlcHQgeW91IHRyeSB0byB1c2UgbXBpbmcgaW5z
dGVhZCBvZiBwaW5nLHlvdSBzaG91bGQgZmlyc3RseSBsZXQgdGhlIHNlcnZlci9jbGllbnQgY2Fu
IHNlbmQgaWdtcCByZXNwb25zZSBtZXNzYWdlIHRvIHRoZSByb3V0ZXIsc28gdGhlIHJvdXRlciBr
bm93cyBpdCBoYXMgYSBtZW1iZXIgam9pbiB0aGUgbXVsdGljYXN0IGdyb3VwLg0KICAgIElmIHRo
ZSBzb3VyY2UgaGFzIHNlbnQgbXVsdGljYXN0IHBhY2tldHMseW91IHVzZSAiaXAgbXJvdXRlIHNo
b3ciIGFuZCBzaG91bGQgc2VlIHRoZSBtcm91dGUgdGFibGUgY3JlYXRlZC4NCiAgICBBbmQgSSB0
aGluayBpZiB5b3UgdXNlIGEgbm9ybWFsIG11bHRpY2FzdCBhZGRyZXNzIHN1Y2ggYXMgMjI1LjEu
MS4xMDAgaXQgd2lsbCBiZSBiZXR0ZXIuDQoNCj09PT09PT0gMjAwNC0wNS0wOSAyMzoxMDo0OSDE
+tTawLTQxdbQ0LS1wKO6PT09PT09PQ0KDQo+SGksDQo+DQo+Q2FuIHNvbWVvbmUgY2FuIGhlbHAt
bWUgdG8gbWFrZSBhIHZlcnkgc2ltcGxlIG11bHRpY2FzdCBjb25maWd1cmF0aW9uLg0KPg0KPkhl
cmUgaXMgbXkgdGVzdCBjb25maWd1cmF0aW9uICAoV2l0aCBqdXN0IG9uZSBSb3V0ZXIpOg0KPg0K
PlNlcnZlciAtLS0tLS0tLS0tLS0tLS0tTXVsdGljYXN0IFJvdXRlciAtLS0tLS0tLS0tLS0tLS0t
LS0tLS0tQ2xpZW50DQo+WzE5Mi4xNjguMS4xICAgICAgICAxOTIuMTY4LjEuMjUwXSAgIFsxOTIu
MTY4LjAuMjUwICAgICAgICAgMTkyLjE2OC4wLjFdDQo+DQo+TmV0bWFzayBpcyAyNTUuMjU1LjI1
NS4wDQo+L3Byb2Mvc3lzL25ldC9pcHY0L2lwX2ZvcndhcmQgaXMgc2V0IHRvMQ0KPlJvdXRlciBp
cyBMaW51eCBGZWRvcmEgQ29yZSAxIFdpdGggUGltZC0yLjEuMC1hbHBoYTI5LTE4DQo+SVBfTXVs
dGljYXN0IFBJTS1TTSBldGMgaXMgYWN0aXZhdGUgYnkgZGVmYXVsdCBpbiBrZXJuZWwuDQo+DQo+
TXkgcm91dGVyIGlzIG9rIGZvciB1bmljYXN0LiBJIGNhbiBjb21tdW5pY2F0ZSBmcm9tIHNlcnZl
ciB0byBjbGllbnQuDQo+DQo+QnV0IFdoZW4gaSB3YW50IHRvIG1ha2UgTXVsdGljYXN0IGZyb20g
U2VydmVyIHRvIENsaWVudCwgdHJhZmZpYyBpcyBub3QNCj5mb3J3YXJkIGJ5IHRoZSByb3V0ZXIu
V2hlbiBpIGRvIGEgInBpbmcgLXQgNSAyMjQuMC4wLjEiIG9uIExpbnV4IENsaWVudCwNCj5wYWNr
ZXRzIGFyZSBub3QgZm9yd2FyZHMgdG8gTGludXggU2VydmVyIGFuZCB2aWNlLXZlcnNhLg0KPg0K
PldoYXQgdG9vbHMgY2FuIGkgdXNlIHRvIHNlZSBpZiBjb25maWd1cmF0aW9uIGlzIE9LID8NCj5X
aGF0J3MgYWJvdXQgcGltZC5jb25mIGNvbmZpZ3VyYXRpb24gZmlsZSA/DQo+DQo+V2hlbiBpIGRv
IGEgImlwIG1yb3V0ZSBzaG93IiB0aGVyZSBpcyBub3RoaW5nIHRvIHNlZSBpcyBpdCBub3JtYWwg
Pw0KPg0KPkRvIHlvdSBoYXZlIGFueSBpZGVhLg0KPlRoYW5rcyBmb3IgeW91ciBoZWxwLg0KPg0K
PkJlc3QgcmVnYXJkcw0KPg0KPkNocmlzdG9waGUgQulhc3NlDQo+RnJhbmNlDQo+DQo+DQo+DQo+
DQo+X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCj5waW0g
bWFpbGluZyBsaXN0DQo+cGltQGlldGYub3JnDQo+aHR0cHM6Ly93d3cxLmlldGYub3JnL21haWxt
YW4vbGlzdGluZm8vcGltDQoNCj0gPSA9ID0gPSA9ID0gPSA9ID0gPSA9ID0gPSA9ID0gPSA9ID0g
PQ0KCQkJDQoNCqGhoaGhoaGhoaGhoaGhoaHWwg0KwPGjoQ0KIA0KCQkJCSANCqGhoaGhoaGhoaGh
oaGhoaF3bHENCqGhoaGhoaGhoaGhoaGhoaF3bHFfd0Bob3RtYWlsLmNvbQ0KoaGhoaGhoaGhoaGh
oaGhoaGhoaEyMDA0LTA1LTEzDQoNCg==

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



From pim-admin@ietf.org  Mon May 17 04:21:30 2004
Received: from optimus.ietf.org (www.iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA06740
	for <pim-archive@lists.ietf.org>; Mon, 17 May 2004 04:21:30 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPdH6-0004Vy-M8; Mon, 17 May 2004 04:15:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPdC5-0003h4-69
	for pim@optimus.ietf.org; Mon, 17 May 2004 04:09:53 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA06212
	for <pim@ietf.org>; Mon, 17 May 2004 04:09:51 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BPdC2-0000dL-Er
	for pim@ietf.org; Mon, 17 May 2004 04:09:50 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPdBB-0000Ja-00
	for pim@ietf.org; Mon, 17 May 2004 04:08:58 -0400
Received: from web90109.mail.scd.yahoo.com ([66.218.94.80])
	by ietf-mx with smtp (Exim 4.12)
	id 1BPdAE-0007VD-00
	for pim@ietf.org; Mon, 17 May 2004 04:07:58 -0400
Message-ID: <20040517080729.3361.qmail@web90109.mail.scd.yahoo.com>
Received: from [219.93.88.198] by web90109.mail.scd.yahoo.com via HTTP; Mon, 17 May 2004 16:07:29 CST
Date: Mon, 17 May 2004 16:07:29 +0800 (CST)
From: =?iso-8859-1?q?Vincent=20Lim?= <vinres1976@yahoo.com.sg>
To: pim@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0-1882182287-1084781249=:99651"
Content-Transfer-Encoding: 8bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=2.6 required=5.0 tests=AWL,FROM_ENDS_IN_NUMS,
	HTML_40_50,HTML_IMAGE_ONLY_04,HTML_MESSAGE autolearn=no version=2.60
Subject: [pim] Research In PIM SM
Sender: pim-admin@ietf.org
Errors-To: pim-admin@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Id: Protocol Independent Multicast <pim.ietf.org>
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>

--0-1882182287-1084781249=:99651
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

I'm interested in doing research in PIM especially SM. Can somebody advice me any area in PIM need more research? 
 
Thanks.
 
Best Regards,
Vincent

 Yahoo! Messenger
- Log on with your mobile phone!
--0-1882182287-1084781249=:99651
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

<DIV>I'm interested in doing research in PIM especially SM. Can somebody advice me any area in PIM need more research? </DIV>
<DIV>&nbsp;</DIV>
<DIV>Thanks.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Best Regards,</DIV>
<DIV>Vincent</DIV><p><img src=http://sg.yimg.com/i/sg/icons/16/messenger.gif width="16" height="16"><b> <a href="http://sg.rd.yahoo.com/mail/tagline/?http://sg.messenger.yahoo.com/" target=_blank>Yahoo! Messenger</a></b><br><small>- <a href="http://sg.mobile.yahoo.com/sms/msgr20.html">Log on</a> with your mobile phone!</small>
--0-1882182287-1084781249=:99651--

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


From pim-admin@ietf.org  Mon May 17 10:35:30 2004
Received: from optimus.ietf.org (www.iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA25793
	for <pim-archive@lists.ietf.org>; Mon, 17 May 2004 10:35:30 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPj7x-0004xN-NW; Mon, 17 May 2004 10:30:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPizI-0003Q5-Ux
	for pim@optimus.ietf.org; Mon, 17 May 2004 10:21:05 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA25076
	for <pim@ietf.org>; Mon, 17 May 2004 10:21:01 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BPizG-0001ZP-Mg
	for pim@ietf.org; Mon, 17 May 2004 10:21:02 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPiyM-0001Fb-00
	for pim@ietf.org; Mon, 17 May 2004 10:20:06 -0400
Received: from sj-iport-1-in.cisco.com ([171.71.176.70] helo=sj-iport-1.cisco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BPixm-0000v2-00
	for pim@ietf.org; Mon, 17 May 2004 10:19:30 -0400
Received: from cypher.cisco.com (cypher.cisco.com [171.69.11.143])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id i4HEIqW9006493;
	Mon, 17 May 2004 07:18:52 -0700 (PDT)
Received: (from eckert@localhost)
	by cypher.cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) id HAA04037;
	Mon, 17 May 2004 07:18:52 -0700 (PDT)
Date: Mon, 17 May 2004 07:18:52 -0700
From: Toerless Eckert <eckert@cisco.com>
To: Vincent Lim <vinres1976@yahoo.com.sg>
Cc: pim@ietf.org
Subject: Re: [pim] Research In PIM SM
Message-ID: <20040517141851.GI305@cisco.com>
References: <20040517080729.3361.qmail@web90109.mail.scd.yahoo.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20040517080729.3361.qmail@web90109.mail.scd.yahoo.com>
User-Agent: Mutt/1.4i
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: pim-admin@ietf.org
Errors-To: pim-admin@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Id: Protocol Independent Multicast <pim.ietf.org>
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>

On Mon, May 17, 2004 at 04:07:29PM +0800, Vincent Lim wrote:
> I'm interested in doing research in PIM especially SM. Can somebody advice me any area in PIM need more research? 

You could try to express it in something like CCS and prove that it works
for classes of topologies and types of failure conditions within limits
of convergence and exclusion of deadlocks, starvation and other unwanted
conditions.

For starters, compare the type of theoretical work that went into
let's stay unicast LSPs with what went into PIM and then you can likely
find a comparable type of analysis that has not been done for PIM but would
be good to have.

Cheers
	Toerless

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


From exim@www1.ietf.org  Mon May 17 10:49:19 2004
Received: from optimus.ietf.org (www.iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA26421
	for <pim-archive@odin.ietf.org>; Mon, 17 May 2004 10:49:19 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPjQ5-0007Lt-Fx
	for pim-archive@odin.ietf.org; Mon, 17 May 2004 10:48:45 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4HEmj6D028261
	for pim-archive@odin.ietf.org; Mon, 17 May 2004 10:48:45 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPjEn-0005zP-9G
	for pim-web-archive@optimus.ietf.org; Mon, 17 May 2004 10:37:05 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA25886
	for <pim-web-archive@ietf.org>; Mon, 17 May 2004 10:37:02 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BPjEk-0006r6-Vv
	for pim-web-archive@ietf.org; Mon, 17 May 2004 10:37:03 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPjDk-0006Vn-00
	for pim-web-archive@ietf.org; Mon, 17 May 2004 10:36:00 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BPjCl-0006B8-00
	for pim-web-archive@ietf.org; Mon, 17 May 2004 10:34:59 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPj7x-0004xN-NW; Mon, 17 May 2004 10:30:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPizI-0003Q5-Ux
	for pim@optimus.ietf.org; Mon, 17 May 2004 10:21:05 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA25076
	for <pim@ietf.org>; Mon, 17 May 2004 10:21:01 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BPizG-0001ZP-Mg
	for pim@ietf.org; Mon, 17 May 2004 10:21:02 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPiyM-0001Fb-00
	for pim@ietf.org; Mon, 17 May 2004 10:20:06 -0400
Received: from sj-iport-1-in.cisco.com ([171.71.176.70] helo=sj-iport-1.cisco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BPixm-0000v2-00
	for pim@ietf.org; Mon, 17 May 2004 10:19:30 -0400
Received: from cypher.cisco.com (cypher.cisco.com [171.69.11.143])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id i4HEIqW9006493;
	Mon, 17 May 2004 07:18:52 -0700 (PDT)
Received: (from eckert@localhost)
	by cypher.cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) id HAA04037;
	Mon, 17 May 2004 07:18:52 -0700 (PDT)
Date: Mon, 17 May 2004 07:18:52 -0700
From: Toerless Eckert <eckert@cisco.com>
To: Vincent Lim <vinres1976@yahoo.com.sg>
Cc: pim@ietf.org
Subject: Re: [pim] Research In PIM SM
Message-ID: <20040517141851.GI305@cisco.com>
References: <20040517080729.3361.qmail@web90109.mail.scd.yahoo.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20040517080729.3361.qmail@web90109.mail.scd.yahoo.com>
User-Agent: Mutt/1.4i
Sender: pim-admin@ietf.org
Errors-To: pim-admin@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Id: Protocol Independent Multicast <pim.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60

On Mon, May 17, 2004 at 04:07:29PM +0800, Vincent Lim wrote:
> I'm interested in doing research in PIM especially SM. Can somebody advice me any area in PIM need more research? 

You could try to express it in something like CCS and prove that it works
for classes of topologies and types of failure conditions within limits
of convergence and exclusion of deadlocks, starvation and other unwanted
conditions.

For starters, compare the type of theoretical work that went into
let's stay unicast LSPs with what went into PIM and then you can likely
find a comparable type of analysis that has not been done for PIM but would
be good to have.

Cheers
	Toerless

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



From pim-admin@ietf.org  Mon May 17 19:28:58 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA12860
	for <pim-archive@lists.ietf.org>; Mon, 17 May 2004 19:28:58 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPrQs-00059V-J1; Mon, 17 May 2004 19:22:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPrBj-0008DB-EN
	for pim@optimus.ietf.org; Mon, 17 May 2004 19:06:27 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA11939
	for <pim@ietf.org>; Mon, 17 May 2004 19:06:22 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BPrBg-0004Pc-2y
	for pim@ietf.org; Mon, 17 May 2004 19:06:24 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPrAf-00043u-00
	for pim@ietf.org; Mon, 17 May 2004 19:05:22 -0400
Received: from gwnj8.utstar.com ([65.200.123.8] helo=lxmail.xebeo.com)
	by ietf-mx with smtp (Exim 4.12)
	id 1BPr9i-0003Q2-00
	for pim@ietf.org; Mon, 17 May 2004 19:04:22 -0400
Received: (qmail 30198 invoked by uid 404); 17 May 2004 23:03:52 -0000
Received: from manish.gupta@utstar.com by lxmail by uid 401 with qmail-scanner-1.20rc1 
 (clamscan: 0.60. spamassassin: 2.55.  Clear:RC:1:. 
 Processed in 0.023981 secs); 17 May 2004 23:03:52 -0000
Received: from bianco.nj.us.utstar.com (HELO utstar.com) (172.16.36.187)
  by lxmail.xebeo.com with SMTP; 17 May 2004 23:03:51 -0000
Message-ID: <40A944D4.50407@utstar.com>
Date: Mon, 17 May 2004 19:03:48 -0400
From: Manish Gupta <manish.gupta@utstar.com>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.2.1) Gecko/20030324
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: pim@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Subject: [pim] Question about the PIM-SM protocol
Sender: pim-admin@ietf.org
Errors-To: pim-admin@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Id: Protocol Independent Multicast <pim.ietf.org>
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-Transfer-Encoding: 7bit


Hi

 I am not sure if this is the right mailing list for
 posting such queries. I am new to the protocol
 and want to understand what is PIM-SM
 expected to do in the following situation. I
 hope somebody can clarify.

  [PRx]  => PIM Router-x
  (ix)   => Interface-x
  [RCVR] => Receiver registered for Group G
  [SNDR] => Sender (S) for Group G

    ---(i3)---[PR1]---(i5)-----(i7)---[PR3]---(iR)---[RCVR]
   |                                    |
  (i1)                                 (iX)
   |                                    |
  [RP]                                  |
   |                                    |
  (i2)                                 (iY)
   |                                    |
    ---(i4)---[PR2]---(i6)-----(i8)---[PR3]---(iS)---[SNDR]


  In the above network, skipping the
  Register/Register-Stop Messaging etc. Once the
  PIM-SM has stablized, including PR3 already
  switched to SPT, my understanding is that
  network will look something like:


  [RP]:
      (S, G, SPT=TRUE): iif=i2, oif={i1}

  [PR1]:
      (*,G): iif=i3, oif={i5}
      (S,G,RPT=TRUE): iif=i3, oif={}

  [PR2]
      (S,G,SPT=TRUE): iif=i6, oif={i4}

  [PR3]
      (S,G,SPT=TRUE): iif=iX, oif={iR}

  [PR4]
      (S,G,SPT=TRUE): iif=iS, oif={i8, iY}

  Is this correct?

  Now, what will happen if the link between
  [PR3] -- [PR4] breaks?

  Will [PR3] send Join (S,G,rpt) or Join (S,G)
  towards RP? Can somebody please clarify?

thanks
manish


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


From exim@www1.ietf.org  Mon May 17 19:41:57 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA13711
	for <pim-archive@odin.ietf.org>; Mon, 17 May 2004 19:41:57 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPrh8-00030g-Jh
	for pim-archive@odin.ietf.org; Mon, 17 May 2004 19:38:54 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4HNcsf0011562
	for pim-archive@odin.ietf.org; Mon, 17 May 2004 19:38:54 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPrYv-00083E-4A
	for pim-web-archive@optimus.ietf.org; Mon, 17 May 2004 19:30:25 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA12957
	for <pim-web-archive@ietf.org>; Mon, 17 May 2004 19:30:24 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BPrYt-0004rW-He
	for pim-web-archive@ietf.org; Mon, 17 May 2004 19:30:23 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPrXu-0004Tf-00
	for pim-web-archive@ietf.org; Mon, 17 May 2004 19:29:23 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BPrX1-00046k-00
	for pim-web-archive@ietf.org; Mon, 17 May 2004 19:28:27 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPrQs-00059V-J1; Mon, 17 May 2004 19:22:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPrBj-0008DB-EN
	for pim@optimus.ietf.org; Mon, 17 May 2004 19:06:27 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA11939
	for <pim@ietf.org>; Mon, 17 May 2004 19:06:22 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BPrBg-0004Pc-2y
	for pim@ietf.org; Mon, 17 May 2004 19:06:24 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPrAf-00043u-00
	for pim@ietf.org; Mon, 17 May 2004 19:05:22 -0400
Received: from gwnj8.utstar.com ([65.200.123.8] helo=lxmail.xebeo.com)
	by ietf-mx with smtp (Exim 4.12)
	id 1BPr9i-0003Q2-00
	for pim@ietf.org; Mon, 17 May 2004 19:04:22 -0400
Received: (qmail 30198 invoked by uid 404); 17 May 2004 23:03:52 -0000
Received: from manish.gupta@utstar.com by lxmail by uid 401 with qmail-scanner-1.20rc1 
 (clamscan: 0.60. spamassassin: 2.55.  Clear:RC:1:. 
 Processed in 0.023981 secs); 17 May 2004 23:03:52 -0000
Received: from bianco.nj.us.utstar.com (HELO utstar.com) (172.16.36.187)
  by lxmail.xebeo.com with SMTP; 17 May 2004 23:03:51 -0000
Message-ID: <40A944D4.50407@utstar.com>
Date: Mon, 17 May 2004 19:03:48 -0400
From: Manish Gupta <manish.gupta@utstar.com>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.2.1) Gecko/20030324
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: pim@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [pim] Question about the PIM-SM protocol
Sender: pim-admin@ietf.org
Errors-To: pim-admin@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Id: Protocol Independent Multicast <pim.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


Hi

 I am not sure if this is the right mailing list for
 posting such queries. I am new to the protocol
 and want to understand what is PIM-SM
 expected to do in the following situation. I
 hope somebody can clarify.

  [PRx]  => PIM Router-x
  (ix)   => Interface-x
  [RCVR] => Receiver registered for Group G
  [SNDR] => Sender (S) for Group G

    ---(i3)---[PR1]---(i5)-----(i7)---[PR3]---(iR)---[RCVR]
   |                                    |
  (i1)                                 (iX)
   |                                    |
  [RP]                                  |
   |                                    |
  (i2)                                 (iY)
   |                                    |
    ---(i4)---[PR2]---(i6)-----(i8)---[PR3]---(iS)---[SNDR]


  In the above network, skipping the
  Register/Register-Stop Messaging etc. Once the
  PIM-SM has stablized, including PR3 already
  switched to SPT, my understanding is that
  network will look something like:


  [RP]:
      (S, G, SPT=TRUE): iif=i2, oif={i1}

  [PR1]:
      (*,G): iif=i3, oif={i5}
      (S,G,RPT=TRUE): iif=i3, oif={}

  [PR2]
      (S,G,SPT=TRUE): iif=i6, oif={i4}

  [PR3]
      (S,G,SPT=TRUE): iif=iX, oif={iR}

  [PR4]
      (S,G,SPT=TRUE): iif=iS, oif={i8, iY}

  Is this correct?

  Now, what will happen if the link between
  [PR3] -- [PR4] breaks?

  Will [PR3] send Join (S,G,rpt) or Join (S,G)
  towards RP? Can somebody please clarify?

thanks
manish


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



From pim-admin@ietf.org  Mon May 17 19:49:53 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA13985
	for <pim-archive@lists.ietf.org>; Mon, 17 May 2004 19:49:53 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPrjB-00040R-MW; Mon, 17 May 2004 19:41:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BOFB6-00046D-Gm
	for pim@optimus.ietf.org; Thu, 13 May 2004 08:19:08 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA07626
	for <pim@ietf.org>; Thu, 13 May 2004 08:19:06 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BOFB5-0003Xf-DY
	for pim@ietf.org; Thu, 13 May 2004 08:19:07 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BOFA6-00030x-00
	for pim@ietf.org; Thu, 13 May 2004 08:18:07 -0400
Received: from smtp.dataconnection.com ([192.91.191.4] helo=smtp.datcon.co.uk)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BOF9P-0002II-00
	for pim@ietf.org; Thu, 13 May 2004 08:17:23 -0400
Received: by goodman.datcon.co.uk with Internet Mail Service (5.5.2653.19)
	id <JWAYXARZ>; Thu, 13 May 2004 13:16:40 +0100
Message-ID: <37701240971DD31193970000F6CCB9F705A5B527@duke.datcon.co.uk>
From: Jonathan Hardwick <jon.hardwick@dataconnection.com>
To: "'m.handley@cs.ucl.ac.uk'" <m.handley@cs.ucl.ac.uk>,
        "'kouvelas@cisco.com'" <kouvelas@cisco.com>,
        "'speakman@cisco.com'"
	 <speakman@cisco.com>,
        "'lorenzo@cisco.com'" <lorenzo@cisco.com>
Cc: "'pim@ietf.org'" <pim@ietf.org>
Date: Thu, 13 May 2004 13:16:41 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Subject: [pim] WG last call for draft-ietf-pim-bidir-06 - comments
Sender: pim-admin@ietf.org
Errors-To: pim-admin@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Id: Protocol Independent Multicast <pim.ietf.org>
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>

Hi,

Here are my comments on draft-ietf-pim-bidir-06.  Apologies for slightly
missing the deadline for this.  I have divided my comments into
"technical" and "editorial" for the convenience of the reader.

Please let me know if anything I say needs clarification.

Thanks,
Jon


Technical comments
==================

Section 2.1, definition of RPA.
-------------------------------

1st sentence.  This gives the impression that the RPA is always
configured, but it may instead be dynamically learned e.g. using BSR.
I suggest rewording to say "An RPA is an address that is to be used...".

Section 3.1.4
-------------

Replace:

"The set "joins(G)" is the set of all interfaces on which the router has
 received (*,G) Joins".

With:

"The set "joins(G)" is the set of all interfaces on which the router has
been elected the DF for RPA(G) and has received (*,G) Joins".

Section 3.3.2
-------------

Last sentence: "doing so requires data driven events".  It's not clear
(to me at least) why storing per-group state requires data-driven events
in the control plane, but storing per-RPA state does not.  Please could
you add some more explanatory text here?

Section 3.4.1
-------------

(1) First sentence: s/must/MUST/

(2) "If the RP address in the message does not match RPA(G) the Join or
     Prune MUST be silently dropped."

    This is inconsistent with the PIM-SM draft, where if a Join (*,G) is
    received and an RP is not known for G, then the PIM-SM router MAY
    learn the G->RP mapping from the Join.  Why not allow this for
    BIDIR-PIM too?  Alternatively, please explain the reason for the
    inconsistency.

(3) Second paragraph under the table: "However on point-to-point links
    we also recommend...".  Recast this sentence as a SHOULD or
    RECOMMENDED.

    In general, I suggest doing an audit of the document to check for
    missing RFC 2119-style text.

(4) I think this FSM assumes that it is not possible to have a Join(*,G)
    or Prune(*,G) event if you are not the DF for RPA(G).

    I conclude this from the facts that (i) the FSM tranitions to NI state
    when the router stops being DF for RPA(G) on I, and (ii) there is
    nothing that keeps the FSM in NI state if a Join(*,G) is subsequently
    received.  Is my interpretation correct?

    If so, I suggest (i) modifying the text to state that the inputs are
    filtered if the router is not DF for RPA(G) on I, and (ii) rewording
    the description of the Join state to remove the implication that the
    router can be in Join state without being the DF.

    If not, please add some text to explain why the FSM transitions to
    NI state when the router stops being DF, but does not necessarily
    stay there.

Section 3.4.2
-------------

In state machine table for Joined state, the event labelled "Change of
RPF_DF(RPA(G))" ought to be "Change of RPF_interface(RPA(G))" - I think.

If I'm wrong, then please add some explanatory text to differentiate the
events labelled "RPF_DF(RPA(G)) changes" and "Change of RPF_DF(RPA(G))".

Section 3.5.2.3
---------------

Final paragraph (sending a single Winner message if the current Winner's
metric improves) is not mentioned in section 3.5.3.  This behaviour
should be incorporated into the DF election state machine as a new event
in Win state, labelled "Metric changes and is now better".



Editorial comments
==================

Section 2.1, definition of RPA.
-------------------------------

Typo in 4th sentence: s/that/which/

Section 3 - document structure
------------------------------

Why not list the sections in numerical order?  If they are numbered in
the wrong order, please renumber them.  (The existing numbering looks fine
to me.)

Section 3.3
-----------

In the pseudocode just before the start of section 3.3.1, "I_am_DF(RPA,
I)" should be "I_am_DF(RPA, iif)".

Section 3.3.1
-------------

s/RPA address/RPA/

Section 3.3.2
-------------

In last sentence, s/tha/the/

Section 3.4.1
-------------

The formatting of the table in the text-only version of the spec needs
to be tidied.

Section 3.5.2.4
---------------

I think you should delete this note, now that we're at last call.
There's no need to document ways in which the spec could work, but
doesn't.

Section 3.5.2.5
---------------

s/if its metric worse/if its metric is worse/

Section 3.5.3.1
---------------

In description of Lose state, s/RP/RPA/

In description of Best-Offer, sentence doesn't scan.  I suggest
rewording as follows:

"Used by the DF to record the identity and advertised metrics of the
router that has made the last offer, for use when sending the Path
message."

Section 3.5.3.2
---------------

Missing comma after "PIM control messages".

Section 3.6
-----------

Missing comma in section header (Timers, Counters and Constants).

In DFT table, value names should be OPlow and OPhigh (with lowercase 'l'
and 'h') for consistency with the rest of the text.


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


From pim-admin@ietf.org  Mon May 17 19:51:05 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA14111
	for <pim-archive@lists.ietf.org>; Mon, 17 May 2004 19:51:05 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPrjC-00041f-Hn; Mon, 17 May 2004 19:41:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPjg6-0000oz-VD
	for pim@optimus.ietf.org; Mon, 17 May 2004 11:05:19 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA27278
	for <pim@ietf.org>; Mon, 17 May 2004 11:05:15 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BPjg4-0000kD-BN
	for pim@ietf.org; Mon, 17 May 2004 11:05:16 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPjf0-0000OX-00
	for pim@ietf.org; Mon, 17 May 2004 11:04:11 -0400
Received: from usc.edu ([128.125.253.136] ident=root)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BPje9-00004C-00
	for pim@ietf.org; Mon, 17 May 2004 11:03:18 -0400
Received: from mcphail.usc.edu (mcphail.usc.edu [128.125.253.51])
	by usc.edu (8.9.3.1/8.9.3/usc) with SMTP
	id IAA04642; Mon, 17 May 2004 08:03:10 -0700 (PDT)
Received: from ceng.usc.edu(128.125.72.78) by mcphail.usc.edu via csmap 
	 id 56baca52_a813_11d8_9e8c_0002b3c946b2_4182;
	Mon, 17 May 2004 08:03:22 -0700 (PDT)
Received: from localhost (helmy@localhost)
	by ceng.usc.edu (8.10.1/8.10.1/usc) with ESMTP
	id i4HF39229703; Mon, 17 May 2004 08:03:09 -0700 (PDT)
Date: Mon, 17 May 2004 08:03:09 -0700 (PDT)
From: helmy <helmy@ceng.usc.edu>
To: Toerless Eckert <eckert@cisco.com>
cc: Vincent Lim <vinres1976@yahoo.com.sg>, <pim@ietf.org>
Subject: Re: [pim] Research In PIM SM
In-Reply-To: <20040517141851.GI305@cisco.com>
Message-ID: <Pine.GSO.4.33.0405170800590.29547-100000@ceng.usc.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: pim-admin@ietf.org
Errors-To: pim-admin@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Id: Protocol Independent Multicast <pim.ietf.org>
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>

> On Mon, May 17, 2004 at 04:07:29PM +0800, Vincent Lim wrote:
> > I'm interested in doing research in PIM especially SM. Can somebody advice me any area in PIM need more research?
>
> You could try to express it in something like CCS and prove that it works
> for classes of topologies and types of failure conditions within limits
> of convergence and exclusion of deadlocks, starvation and other unwanted
> conditions.
>
> For starters, compare the type of theoretical work that went into
> let's stay unicast LSPs with what went into PIM and then you can likely
> find a comparable type of analysis that has not been done for PIM but would
> be good to have.

For a similar study you can check the 'STRESS' project
[netweb.usc.edu/stress]. There are also up-to-date publications and links
on my website ceng.usc.edu/~helmy

Regards,
-Ahmed

----------
Ahmed Helmy
Assistant Professor of Computer Networks
Electrical Engineering Department
University of Southern California
http://ceng.usc.edu/~helmy

>
> Cheers
> 	Toerless
>
> _______________________________________________
> 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 exim@www1.ietf.org  Mon May 17 20:18:20 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA15910
	for <pim-archive@odin.ietf.org>; Mon, 17 May 2004 20:18:20 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPs4g-0001kr-LF
	for pim-archive@odin.ietf.org; Mon, 17 May 2004 20:03:15 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4I03EQ5006746
	for pim-archive@odin.ietf.org; Mon, 17 May 2004 20:03:14 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPrv0-0007jn-48
	for pim-web-archive@optimus.ietf.org; Mon, 17 May 2004 19:53:14 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA14376
	for <pim-web-archive@ietf.org>; Mon, 17 May 2004 19:53:12 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BPruy-0004vo-A9
	for pim-web-archive@ietf.org; Mon, 17 May 2004 19:53:12 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPrtJ-0004My-00
	for pim-web-archive@ietf.org; Mon, 17 May 2004 19:51:30 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BPrrG-0003jr-00
	for pim-web-archive@ietf.org; Mon, 17 May 2004 19:49:22 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPrjB-00040R-MW; Mon, 17 May 2004 19:41:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BOFB6-00046D-Gm
	for pim@optimus.ietf.org; Thu, 13 May 2004 08:19:08 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA07626
	for <pim@ietf.org>; Thu, 13 May 2004 08:19:06 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BOFB5-0003Xf-DY
	for pim@ietf.org; Thu, 13 May 2004 08:19:07 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BOFA6-00030x-00
	for pim@ietf.org; Thu, 13 May 2004 08:18:07 -0400
Received: from smtp.dataconnection.com ([192.91.191.4] helo=smtp.datcon.co.uk)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BOF9P-0002II-00
	for pim@ietf.org; Thu, 13 May 2004 08:17:23 -0400
Received: by goodman.datcon.co.uk with Internet Mail Service (5.5.2653.19)
	id <JWAYXARZ>; Thu, 13 May 2004 13:16:40 +0100
Message-ID: <37701240971DD31193970000F6CCB9F705A5B527@duke.datcon.co.uk>
From: Jonathan Hardwick <jon.hardwick@dataconnection.com>
To: "'m.handley@cs.ucl.ac.uk'" <m.handley@cs.ucl.ac.uk>,
        "'kouvelas@cisco.com'" <kouvelas@cisco.com>,
        "'speakman@cisco.com'"
	 <speakman@cisco.com>,
        "'lorenzo@cisco.com'" <lorenzo@cisco.com>
Cc: "'pim@ietf.org'" <pim@ietf.org>
Date: Thu, 13 May 2004 13:16:41 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [pim] WG last call for draft-ietf-pim-bidir-06 - comments
Sender: pim-admin@ietf.org
Errors-To: pim-admin@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Id: Protocol Independent Multicast <pim.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60

Hi,

Here are my comments on draft-ietf-pim-bidir-06.  Apologies for slightly
missing the deadline for this.  I have divided my comments into
"technical" and "editorial" for the convenience of the reader.

Please let me know if anything I say needs clarification.

Thanks,
Jon


Technical comments
==================

Section 2.1, definition of RPA.
-------------------------------

1st sentence.  This gives the impression that the RPA is always
configured, but it may instead be dynamically learned e.g. using BSR.
I suggest rewording to say "An RPA is an address that is to be used...".

Section 3.1.4
-------------

Replace:

"The set "joins(G)" is the set of all interfaces on which the router has
 received (*,G) Joins".

With:

"The set "joins(G)" is the set of all interfaces on which the router has
been elected the DF for RPA(G) and has received (*,G) Joins".

Section 3.3.2
-------------

Last sentence: "doing so requires data driven events".  It's not clear
(to me at least) why storing per-group state requires data-driven events
in the control plane, but storing per-RPA state does not.  Please could
you add some more explanatory text here?

Section 3.4.1
-------------

(1) First sentence: s/must/MUST/

(2) "If the RP address in the message does not match RPA(G) the Join or
     Prune MUST be silently dropped."

    This is inconsistent with the PIM-SM draft, where if a Join (*,G) is
    received and an RP is not known for G, then the PIM-SM router MAY
    learn the G->RP mapping from the Join.  Why not allow this for
    BIDIR-PIM too?  Alternatively, please explain the reason for the
    inconsistency.

(3) Second paragraph under the table: "However on point-to-point links
    we also recommend...".  Recast this sentence as a SHOULD or
    RECOMMENDED.

    In general, I suggest doing an audit of the document to check for
    missing RFC 2119-style text.

(4) I think this FSM assumes that it is not possible to have a Join(*,G)
    or Prune(*,G) event if you are not the DF for RPA(G).

    I conclude this from the facts that (i) the FSM tranitions to NI state
    when the router stops being DF for RPA(G) on I, and (ii) there is
    nothing that keeps the FSM in NI state if a Join(*,G) is subsequently
    received.  Is my interpretation correct?

    If so, I suggest (i) modifying the text to state that the inputs are
    filtered if the router is not DF for RPA(G) on I, and (ii) rewording
    the description of the Join state to remove the implication that the
    router can be in Join state without being the DF.

    If not, please add some text to explain why the FSM transitions to
    NI state when the router stops being DF, but does not necessarily
    stay there.

Section 3.4.2
-------------

In state machine table for Joined state, the event labelled "Change of
RPF_DF(RPA(G))" ought to be "Change of RPF_interface(RPA(G))" - I think.

If I'm wrong, then please add some explanatory text to differentiate the
events labelled "RPF_DF(RPA(G)) changes" and "Change of RPF_DF(RPA(G))".

Section 3.5.2.3
---------------

Final paragraph (sending a single Winner message if the current Winner's
metric improves) is not mentioned in section 3.5.3.  This behaviour
should be incorporated into the DF election state machine as a new event
in Win state, labelled "Metric changes and is now better".



Editorial comments
==================

Section 2.1, definition of RPA.
-------------------------------

Typo in 4th sentence: s/that/which/

Section 3 - document structure
------------------------------

Why not list the sections in numerical order?  If they are numbered in
the wrong order, please renumber them.  (The existing numbering looks fine
to me.)

Section 3.3
-----------

In the pseudocode just before the start of section 3.3.1, "I_am_DF(RPA,
I)" should be "I_am_DF(RPA, iif)".

Section 3.3.1
-------------

s/RPA address/RPA/

Section 3.3.2
-------------

In last sentence, s/tha/the/

Section 3.4.1
-------------

The formatting of the table in the text-only version of the spec needs
to be tidied.

Section 3.5.2.4
---------------

I think you should delete this note, now that we're at last call.
There's no need to document ways in which the spec could work, but
doesn't.

Section 3.5.2.5
---------------

s/if its metric worse/if its metric is worse/

Section 3.5.3.1
---------------

In description of Lose state, s/RP/RPA/

In description of Best-Offer, sentence doesn't scan.  I suggest
rewording as follows:

"Used by the DF to record the identity and advertised metrics of the
router that has made the last offer, for use when sending the Path
message."

Section 3.5.3.2
---------------

Missing comma after "PIM control messages".

Section 3.6
-----------

Missing comma in section header (Timers, Counters and Constants).

In DFT table, value names should be OPlow and OPhigh (with lowercase 'l'
and 'h') for consistency with the rest of the text.


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



From exim@www1.ietf.org  Mon May 17 20:18:32 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA15932
	for <pim-archive@odin.ietf.org>; Mon, 17 May 2004 20:18:32 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPs4i-0001m1-8o
	for pim-archive@odin.ietf.org; Mon, 17 May 2004 20:03:16 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4I03GUx006813
	for pim-archive@odin.ietf.org; Mon, 17 May 2004 20:03:16 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPrwS-0008EE-8C
	for pim-web-archive@optimus.ietf.org; Mon, 17 May 2004 19:54:44 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA14587
	for <pim-web-archive@ietf.org>; Mon, 17 May 2004 19:54:43 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BPrwQ-0005Ob-DY
	for pim-web-archive@ietf.org; Mon, 17 May 2004 19:54:42 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPruL-0004gC-00
	for pim-web-archive@ietf.org; Mon, 17 May 2004 19:52:34 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BPrsQ-00040X-00
	for pim-web-archive@ietf.org; Mon, 17 May 2004 19:50:34 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPrjC-00041f-Hn; Mon, 17 May 2004 19:41:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPjg6-0000oz-VD
	for pim@optimus.ietf.org; Mon, 17 May 2004 11:05:19 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA27278
	for <pim@ietf.org>; Mon, 17 May 2004 11:05:15 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BPjg4-0000kD-BN
	for pim@ietf.org; Mon, 17 May 2004 11:05:16 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPjf0-0000OX-00
	for pim@ietf.org; Mon, 17 May 2004 11:04:11 -0400
Received: from usc.edu ([128.125.253.136] ident=root)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BPje9-00004C-00
	for pim@ietf.org; Mon, 17 May 2004 11:03:18 -0400
Received: from mcphail.usc.edu (mcphail.usc.edu [128.125.253.51])
	by usc.edu (8.9.3.1/8.9.3/usc) with SMTP
	id IAA04642; Mon, 17 May 2004 08:03:10 -0700 (PDT)
Received: from ceng.usc.edu(128.125.72.78) by mcphail.usc.edu via csmap 
	 id 56baca52_a813_11d8_9e8c_0002b3c946b2_4182;
	Mon, 17 May 2004 08:03:22 -0700 (PDT)
Received: from localhost (helmy@localhost)
	by ceng.usc.edu (8.10.1/8.10.1/usc) with ESMTP
	id i4HF39229703; Mon, 17 May 2004 08:03:09 -0700 (PDT)
Date: Mon, 17 May 2004 08:03:09 -0700 (PDT)
From: helmy <helmy@ceng.usc.edu>
To: Toerless Eckert <eckert@cisco.com>
cc: Vincent Lim <vinres1976@yahoo.com.sg>, <pim@ietf.org>
Subject: Re: [pim] Research In PIM SM
In-Reply-To: <20040517141851.GI305@cisco.com>
Message-ID: <Pine.GSO.4.33.0405170800590.29547-100000@ceng.usc.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: pim-admin@ietf.org
Errors-To: pim-admin@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Id: Protocol Independent Multicast <pim.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60

> On Mon, May 17, 2004 at 04:07:29PM +0800, Vincent Lim wrote:
> > I'm interested in doing research in PIM especially SM. Can somebody advice me any area in PIM need more research?
>
> You could try to express it in something like CCS and prove that it works
> for classes of topologies and types of failure conditions within limits
> of convergence and exclusion of deadlocks, starvation and other unwanted
> conditions.
>
> For starters, compare the type of theoretical work that went into
> let's stay unicast LSPs with what went into PIM and then you can likely
> find a comparable type of analysis that has not been done for PIM but would
> be good to have.

For a similar study you can check the 'STRESS' project
[netweb.usc.edu/stress]. There are also up-to-date publications and links
on my website ceng.usc.edu/~helmy

Regards,
-Ahmed

----------
Ahmed Helmy
Assistant Professor of Computer Networks
Electrical Engineering Department
University of Southern California
http://ceng.usc.edu/~helmy

>
> Cheers
> 	Toerless
>
> _______________________________________________
> 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-admin@ietf.org  Mon May 17 20:20:06 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA16010
	for <pim-archive@lists.ietf.org>; Mon, 17 May 2004 20:20:06 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPs5S-0001sZ-6T; Mon, 17 May 2004 20:04:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPrv8-0007mv-H1
	for pim@optimus.ietf.org; Mon, 17 May 2004 19:53:22 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA14398
	for <pim@ietf.org>; Mon, 17 May 2004 19:53:21 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BPrv6-0004zk-LA
	for pim@ietf.org; Mon, 17 May 2004 19:53:20 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPrtO-0004Nn-00
	for pim@ietf.org; Mon, 17 May 2004 19:51:35 -0400
Received: from smtp2.procket.com ([65.174.124.37])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BPrrV-0003dP-00
	for pim@ietf.org; Mon, 17 May 2004 19:49:37 -0400
Received: from miata.procket.com (mil0-fw00-d-1.procket.com [65.174.124.60])
	by smtp2.procket.com (8.12.8p1/8.12.1) with ESMTP id i4I1uxAw010346;
	Mon, 17 May 2004 18:56:59 -0700 (PDT)
Received: from exchangefe2.na.procket.com (email.na.procket.com [10.1.7.252])
	by miata.procket.com (8.12.1/8.12.1) with ESMTP id i4HNmvd1010341;
	Mon, 17 May 2004 16:48:57 -0700 (PDT)
Received: from [10.1.5.14] ([10.1.5.14]) by exchangefe2.na.procket.com with Microsoft SMTPSVC(5.0.2195.6713);
	 Mon, 17 May 2004 16:48:57 -0700
In-Reply-To: <40A944D4.50407@utstar.com>
References: <40A944D4.50407@utstar.com>
Mime-Version: 1.0 (Apple Message framework v613)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <C2482698-A85C-11D8-B2A3-00039307689E@procket.com>
Content-Transfer-Encoding: 7bit
Cc: John Zwiebel <jzwiebel@procket.com>, pim@ietf.org
From: John Zwiebel <jzwiebel@procket.com>
Subject: Re: [pim] Question about the PIM-SM protocol
Date: Mon, 17 May 2004 16:48:55 -0700
To: Manish Gupta <manish.gupta@utstar.com>
X-Mailer: Apple Mail (2.613)
X-OriginalArrivalTime: 17 May 2004 23:48:57.0098 (UTC) FILETIME=[84D4AEA0:01C43C69]
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: pim-admin@ietf.org
Errors-To: pim-admin@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Id: Protocol Independent Multicast <pim.ietf.org>
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-Transfer-Encoding: 7bit


On May 17, 2004, at 4:03 PM, Manish Gupta wrote:

>
> Hi
>
> I am not sure if this is the right mailing list for
> posting such queries. I am new to the protocol
> and want to understand what is PIM-SM
> expected to do in the following situation. I
> hope somebody can clarify.
>
>  [PRx]  => PIM Router-x
>  (ix)   => Interface-x
>  [RCVR] => Receiver registered for Group G
>  [SNDR] => Sender (S) for Group G
>
>    ---(i3)---[PR1]---(i5)-----(i7)---[PR3]---(iR)---[RCVR]
>   |                                    |
>  (i1)                                 (iX)
>   |                                    |
>  [RP]                                  |
>   |                                    |
>  (i2)                                 (iY)
>   |                                    |
>    ---(i4)---[PR2]---(i6)-----(i8)---[PR3]---(iS)---[SNDR]
>
>
>  In the above network, skipping the
>  Register/Register-Stop Messaging etc. Once the
>  PIM-SM has stablized, including PR3 already
>  switched to SPT, my understanding is that
>  network will look something like:
>
>
>  [RP]:
>      (S, G, SPT=TRUE): iif=i2, oif={i1}
>
>  [PR1]:
>      (*,G): iif=i3, oif={i5}
>      (S,G,RPT=TRUE): iif=i3, oif={}
>
>  [PR2]
>      (S,G,SPT=TRUE): iif=i6, oif={i4}
>
>  [PR3]
>      (S,G,SPT=TRUE): iif=iX, oif={iR}
>
>  [PR4]
>      (S,G,SPT=TRUE): iif=iS, oif={i8, iY}
>
>  Is this correct?

Not quite.
There is no reason for traffic to flow to the RP.
Exactly what happens may depend on how the vendor implemented
things, but consider that the RP has the OIF in the (S,G) is
inherited from the (*,G) so when the (S,G,R) prune was sent
up the shared-tree, that interface should be removed and then
the SPT through pr4 and pr2 will be deleted.

If the vendor does not know "inherited" OIFs, then
the fact that there will no longer be any (S,G) joins
sent to the RP should cause that OIF to timeout in ~3 minutes,
and again the SPT through pr4 and pr2 will be deleted.

(S,G) state will be kept alive on the RP by PIM registers.
State on PR2 will timeout and be deleted since the RP
will no longer send (s,g) joins toward the source.

>
>  Now, what will happen if the link between
>  [PR3] -- [PR4] breaks?
>
>  Will [PR3] send Join (S,G,rpt) or Join (S,G)
>  towards RP? Can somebody please clarify?

The shortest path will be through PR1 since its
the only path.  PR3 will send a (S,G) join.

>
> thanks
> manish
>
>
> _______________________________________________
> 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-admin@ietf.org  Mon May 17 20:25:29 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA16219
	for <pim-archive@lists.ietf.org>; Mon, 17 May 2004 20:25:29 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPsKv-0006h0-H4; Mon, 17 May 2004 20:20:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPs5w-0001xo-Ge
	for pim@optimus.ietf.org; Mon, 17 May 2004 20:04:32 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA15463
	for <pim@ietf.org>; Mon, 17 May 2004 20:04:31 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BPs5u-0001Ug-Ii
	for pim@ietf.org; Mon, 17 May 2004 20:04:30 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPs51-00019b-00
	for pim@ietf.org; Mon, 17 May 2004 20:03:35 -0400
Received: from sj-iport-1-in.cisco.com ([171.71.176.70] helo=sj-iport-1.cisco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BPs4Q-0000lj-00
	for pim@ietf.org; Mon, 17 May 2004 20:02:58 -0400
Received: from cypher.cisco.com (cypher.cisco.com [171.69.11.143])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id i4I02QSu016695;
	Mon, 17 May 2004 17:02:27 -0700 (PDT)
Received: from localhost (kouvelas@localhost)
	by cypher.cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) with ESMTP id RAA20390;
	Mon, 17 May 2004 17:02:26 -0700 (PDT)
Message-Id: <200405180002.RAA20390@cypher.cisco.com>
To: Jonathan Hardwick <jon.hardwick@dataconnection.com>
cc: "'m.handley@cs.ucl.ac.uk'" <m.handley@cs.ucl.ac.uk>,
        "'kouvelas@cisco.com'" <kouvelas@cisco.com>,
        "'speakman@cisco.com'" <speakman@cisco.com>,
        "'lorenzo@cisco.com'" <lorenzo@cisco.com>,
        "'pim@ietf.org'" <pim@ietf.org>
In-reply-to: Your message of "Thu, 13 May 2004 13:16:41 BST."
             <37701240971DD31193970000F6CCB9F705A5B527@duke.datcon.co.uk> 
Date: Mon, 17 May 2004 17:02:26 -0700
From: Isidor Kouvelas <kouvelas@cisco.com>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Subject: [pim] Re: WG last call for draft-ietf-pim-bidir-06 - comments
Sender: pim-admin@ietf.org
Errors-To: pim-admin@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Id: Protocol Independent Multicast <pim.ietf.org>
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>


Thanks for the very careful reading and the comments. Some responses
inline.

Jonathan Hardwick writes:
>Section 3.1.4
>-------------
>
>Replace:
>
>"The set "joins(G)" is the set of all interfaces on which the router has
> received (*,G) Joins".
>
>With:
>
>"The set "joins(G)" is the set of all interfaces on which the router has
>been elected the DF for RPA(G) and has received (*,G) Joins".

A non-DF will accept join messages and start the relevant timers. It
will just not act on the join state by forwarding.

>Section 3.3.2
>-------------
>
>Last sentence: "doing so requires data driven events".  It's not clear
>(to me at least) why storing per-group state requires data-driven events
>in the control plane, but storing per-RPA state does not.  Please could
>you add some more explanatory text here?

Group specific state should never exist for inactive groups. On source
only branches there are no control messages to identify the active
groups. Such activity must be detected by the multicast data packets
for those groups.

>Section 3.4.1
>-------------
>
>(4) I think this FSM assumes that it is not possible to have a Join(*,G)
>    or Prune(*,G) event if you are not the DF for RPA(G).
>
>    I conclude this from the facts that (i) the FSM tranitions to NI state
>    when the router stops being DF for RPA(G) on I, and (ii) there is
>    nothing that keeps the FSM in NI state if a Join(*,G) is subsequently
>    received.  Is my interpretation correct?

Yes.

>    If so, I suggest (i) modifying the text to state that the inputs are
>    filtered if the router is not DF for RPA(G) on I, and (ii) rewording
>    the description of the Join state to remove the implication that the
>    router can be in Join state without being the DF.

The router CAN be in join state without being the DF. It just does not
forward. To forward on an interface you must be in join state AND be
the DF.

>    If not, please add some text to explain why the FSM transitions to
>    NI state when the router stops being DF, but does not necessarily
>    stay there.

We allow transitioning to Join state when we are not the DF so that if
the join and the news about the new DF (pass) arrive out-of-order,
then we can start forwarding as soon as we receive the pass. If we
were to discard the Join then we would have to wait for a whole join
period before we can start forwarding.
Now when we stop being the DF there is no reason to keep the J/P state
around. We could just let it time out. Clearing it is just an
optimisation.

>Section 3.4.2
>-------------
>
>In state machine table for Joined state, the event labelled "Change of
>RPF_DF(RPA(G))" ought to be "Change of RPF_interface(RPA(G))" - I think.
>
>If I'm wrong, then please add some explanatory text to differentiate the
>events labelled "RPF_DF(RPA(G)) changes" and "Change of RPF_DF(RPA(G))".

The event "RPF_DF(RPA(G)) changes" should read "RPF_DF(RPA(G)) GenID
changes". The diagram in the postscript version reflects this. I will
fix the text version.

>Section 3.5.2.3
>---------------
>
>Final paragraph (sending a single Winner message if the current Winner's
>metric improves) is not mentioned in section 3.5.3.  This behaviour
>should be incorporated into the DF election state machine as a new event
>in Win state, labelled "Metric changes and is now better".

As the intro to 3.5.2 explains, if there is any difference between
3.5.2 and 3.5.3 then 3.5.3 is correct :-)
This sentence describes an optimisation that is unecessary.
I think the fix is to remove the sentence from 3.5.2.3.

Isidor

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


From exim@www1.ietf.org  Mon May 17 20:27:21 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA16345
	for <pim-archive@odin.ietf.org>; Mon, 17 May 2004 20:27:21 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPsR4-0000j9-Ov
	for pim-archive@odin.ietf.org; Mon, 17 May 2004 20:26:22 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4I0QMqM002796
	for pim-archive@odin.ietf.org; Mon, 17 May 2004 20:26:22 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPsMO-0007KP-Pu
	for pim-web-archive@optimus.ietf.org; Mon, 17 May 2004 20:21:32 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA16074
	for <pim-web-archive@ietf.org>; Mon, 17 May 2004 20:21:31 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BPsMM-0007OV-R8
	for pim-web-archive@ietf.org; Mon, 17 May 2004 20:21:30 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPsLO-00070D-00
	for pim-web-archive@ietf.org; Mon, 17 May 2004 20:20:31 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BPsKV-0006dx-00
	for pim-web-archive@ietf.org; Mon, 17 May 2004 20:19:35 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPs5S-0001sZ-6T; Mon, 17 May 2004 20:04:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPrv8-0007mv-H1
	for pim@optimus.ietf.org; Mon, 17 May 2004 19:53:22 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA14398
	for <pim@ietf.org>; Mon, 17 May 2004 19:53:21 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BPrv6-0004zk-LA
	for pim@ietf.org; Mon, 17 May 2004 19:53:20 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPrtO-0004Nn-00
	for pim@ietf.org; Mon, 17 May 2004 19:51:35 -0400
Received: from smtp2.procket.com ([65.174.124.37])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BPrrV-0003dP-00
	for pim@ietf.org; Mon, 17 May 2004 19:49:37 -0400
Received: from miata.procket.com (mil0-fw00-d-1.procket.com [65.174.124.60])
	by smtp2.procket.com (8.12.8p1/8.12.1) with ESMTP id i4I1uxAw010346;
	Mon, 17 May 2004 18:56:59 -0700 (PDT)
Received: from exchangefe2.na.procket.com (email.na.procket.com [10.1.7.252])
	by miata.procket.com (8.12.1/8.12.1) with ESMTP id i4HNmvd1010341;
	Mon, 17 May 2004 16:48:57 -0700 (PDT)
Received: from [10.1.5.14] ([10.1.5.14]) by exchangefe2.na.procket.com with Microsoft SMTPSVC(5.0.2195.6713);
	 Mon, 17 May 2004 16:48:57 -0700
In-Reply-To: <40A944D4.50407@utstar.com>
References: <40A944D4.50407@utstar.com>
Mime-Version: 1.0 (Apple Message framework v613)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <C2482698-A85C-11D8-B2A3-00039307689E@procket.com>
Content-Transfer-Encoding: 7bit
Cc: John Zwiebel <jzwiebel@procket.com>, pim@ietf.org
From: John Zwiebel <jzwiebel@procket.com>
Subject: Re: [pim] Question about the PIM-SM protocol
Date: Mon, 17 May 2004 16:48:55 -0700
To: Manish Gupta <manish.gupta@utstar.com>
X-Mailer: Apple Mail (2.613)
X-OriginalArrivalTime: 17 May 2004 23:48:57.0098 (UTC) FILETIME=[84D4AEA0:01C43C69]
Content-Transfer-Encoding: 7bit
Sender: pim-admin@ietf.org
Errors-To: pim-admin@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Id: Protocol Independent Multicast <pim.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On May 17, 2004, at 4:03 PM, Manish Gupta wrote:

>
> Hi
>
> I am not sure if this is the right mailing list for
> posting such queries. I am new to the protocol
> and want to understand what is PIM-SM
> expected to do in the following situation. I
> hope somebody can clarify.
>
>  [PRx]  => PIM Router-x
>  (ix)   => Interface-x
>  [RCVR] => Receiver registered for Group G
>  [SNDR] => Sender (S) for Group G
>
>    ---(i3)---[PR1]---(i5)-----(i7)---[PR3]---(iR)---[RCVR]
>   |                                    |
>  (i1)                                 (iX)
>   |                                    |
>  [RP]                                  |
>   |                                    |
>  (i2)                                 (iY)
>   |                                    |
>    ---(i4)---[PR2]---(i6)-----(i8)---[PR3]---(iS)---[SNDR]
>
>
>  In the above network, skipping the
>  Register/Register-Stop Messaging etc. Once the
>  PIM-SM has stablized, including PR3 already
>  switched to SPT, my understanding is that
>  network will look something like:
>
>
>  [RP]:
>      (S, G, SPT=TRUE): iif=i2, oif={i1}
>
>  [PR1]:
>      (*,G): iif=i3, oif={i5}
>      (S,G,RPT=TRUE): iif=i3, oif={}
>
>  [PR2]
>      (S,G,SPT=TRUE): iif=i6, oif={i4}
>
>  [PR3]
>      (S,G,SPT=TRUE): iif=iX, oif={iR}
>
>  [PR4]
>      (S,G,SPT=TRUE): iif=iS, oif={i8, iY}
>
>  Is this correct?

Not quite.
There is no reason for traffic to flow to the RP.
Exactly what happens may depend on how the vendor implemented
things, but consider that the RP has the OIF in the (S,G) is
inherited from the (*,G) so when the (S,G,R) prune was sent
up the shared-tree, that interface should be removed and then
the SPT through pr4 and pr2 will be deleted.

If the vendor does not know "inherited" OIFs, then
the fact that there will no longer be any (S,G) joins
sent to the RP should cause that OIF to timeout in ~3 minutes,
and again the SPT through pr4 and pr2 will be deleted.

(S,G) state will be kept alive on the RP by PIM registers.
State on PR2 will timeout and be deleted since the RP
will no longer send (s,g) joins toward the source.

>
>  Now, what will happen if the link between
>  [PR3] -- [PR4] breaks?
>
>  Will [PR3] send Join (S,G,rpt) or Join (S,G)
>  towards RP? Can somebody please clarify?

The shortest path will be through PR1 since its
the only path.  PR3 will send a (S,G) join.

>
> thanks
> manish
>
>
> _______________________________________________
> 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 exim@www1.ietf.org  Mon May 17 20:45:38 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA17383
	for <pim-archive@odin.ietf.org>; Mon, 17 May 2004 20:45:38 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPsXQ-00024c-CN
	for pim-archive@odin.ietf.org; Mon, 17 May 2004 20:32:56 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4I0Wum8007955
	for pim-archive@odin.ietf.org; Mon, 17 May 2004 20:32:56 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPsRU-0000qm-Gd
	for pim-web-archive@optimus.ietf.org; Mon, 17 May 2004 20:26:48 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA16328
	for <pim-web-archive@ietf.org>; Mon, 17 May 2004 20:26:46 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BPsRS-0001Vt-CY
	for pim-web-archive@ietf.org; Mon, 17 May 2004 20:26:46 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPsQX-00017k-00
	for pim-web-archive@ietf.org; Mon, 17 May 2004 20:25:50 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BPsPi-0000kY-00
	for pim-web-archive@ietf.org; Mon, 17 May 2004 20:24:58 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPsKv-0006h0-H4; Mon, 17 May 2004 20:20:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPs5w-0001xo-Ge
	for pim@optimus.ietf.org; Mon, 17 May 2004 20:04:32 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA15463
	for <pim@ietf.org>; Mon, 17 May 2004 20:04:31 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BPs5u-0001Ug-Ii
	for pim@ietf.org; Mon, 17 May 2004 20:04:30 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPs51-00019b-00
	for pim@ietf.org; Mon, 17 May 2004 20:03:35 -0400
Received: from sj-iport-1-in.cisco.com ([171.71.176.70] helo=sj-iport-1.cisco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BPs4Q-0000lj-00
	for pim@ietf.org; Mon, 17 May 2004 20:02:58 -0400
Received: from cypher.cisco.com (cypher.cisco.com [171.69.11.143])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id i4I02QSu016695;
	Mon, 17 May 2004 17:02:27 -0700 (PDT)
Received: from localhost (kouvelas@localhost)
	by cypher.cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) with ESMTP id RAA20390;
	Mon, 17 May 2004 17:02:26 -0700 (PDT)
Message-Id: <200405180002.RAA20390@cypher.cisco.com>
To: Jonathan Hardwick <jon.hardwick@dataconnection.com>
cc: "'m.handley@cs.ucl.ac.uk'" <m.handley@cs.ucl.ac.uk>,
        "'kouvelas@cisco.com'" <kouvelas@cisco.com>,
        "'speakman@cisco.com'" <speakman@cisco.com>,
        "'lorenzo@cisco.com'" <lorenzo@cisco.com>,
        "'pim@ietf.org'" <pim@ietf.org>
In-reply-to: Your message of "Thu, 13 May 2004 13:16:41 BST."
             <37701240971DD31193970000F6CCB9F705A5B527@duke.datcon.co.uk> 
Date: Mon, 17 May 2004 17:02:26 -0700
From: Isidor Kouvelas <kouvelas@cisco.com>
Subject: [pim] Re: WG last call for draft-ietf-pim-bidir-06 - comments
Sender: pim-admin@ietf.org
Errors-To: pim-admin@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Id: Protocol Independent Multicast <pim.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60


Thanks for the very careful reading and the comments. Some responses
inline.

Jonathan Hardwick writes:
>Section 3.1.4
>-------------
>
>Replace:
>
>"The set "joins(G)" is the set of all interfaces on which the router has
> received (*,G) Joins".
>
>With:
>
>"The set "joins(G)" is the set of all interfaces on which the router has
>been elected the DF for RPA(G) and has received (*,G) Joins".

A non-DF will accept join messages and start the relevant timers. It
will just not act on the join state by forwarding.

>Section 3.3.2
>-------------
>
>Last sentence: "doing so requires data driven events".  It's not clear
>(to me at least) why storing per-group state requires data-driven events
>in the control plane, but storing per-RPA state does not.  Please could
>you add some more explanatory text here?

Group specific state should never exist for inactive groups. On source
only branches there are no control messages to identify the active
groups. Such activity must be detected by the multicast data packets
for those groups.

>Section 3.4.1
>-------------
>
>(4) I think this FSM assumes that it is not possible to have a Join(*,G)
>    or Prune(*,G) event if you are not the DF for RPA(G).
>
>    I conclude this from the facts that (i) the FSM tranitions to NI state
>    when the router stops being DF for RPA(G) on I, and (ii) there is
>    nothing that keeps the FSM in NI state if a Join(*,G) is subsequently
>    received.  Is my interpretation correct?

Yes.

>    If so, I suggest (i) modifying the text to state that the inputs are
>    filtered if the router is not DF for RPA(G) on I, and (ii) rewording
>    the description of the Join state to remove the implication that the
>    router can be in Join state without being the DF.

The router CAN be in join state without being the DF. It just does not
forward. To forward on an interface you must be in join state AND be
the DF.

>    If not, please add some text to explain why the FSM transitions to
>    NI state when the router stops being DF, but does not necessarily
>    stay there.

We allow transitioning to Join state when we are not the DF so that if
the join and the news about the new DF (pass) arrive out-of-order,
then we can start forwarding as soon as we receive the pass. If we
were to discard the Join then we would have to wait for a whole join
period before we can start forwarding.
Now when we stop being the DF there is no reason to keep the J/P state
around. We could just let it time out. Clearing it is just an
optimisation.

>Section 3.4.2
>-------------
>
>In state machine table for Joined state, the event labelled "Change of
>RPF_DF(RPA(G))" ought to be "Change of RPF_interface(RPA(G))" - I think.
>
>If I'm wrong, then please add some explanatory text to differentiate the
>events labelled "RPF_DF(RPA(G)) changes" and "Change of RPF_DF(RPA(G))".

The event "RPF_DF(RPA(G)) changes" should read "RPF_DF(RPA(G)) GenID
changes". The diagram in the postscript version reflects this. I will
fix the text version.

>Section 3.5.2.3
>---------------
>
>Final paragraph (sending a single Winner message if the current Winner's
>metric improves) is not mentioned in section 3.5.3.  This behaviour
>should be incorporated into the DF election state machine as a new event
>in Win state, labelled "Metric changes and is now better".

As the intro to 3.5.2 explains, if there is any difference between
3.5.2 and 3.5.3 then 3.5.3 is correct :-)
This sentence describes an optimisation that is unecessary.
I think the fix is to remove the sentence from 3.5.2.3.

Isidor

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



From pim-admin@ietf.org  Tue May 18 07:02:04 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA03353
	for <pim-archive@lists.ietf.org>; Tue, 18 May 2004 07:02:04 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQ29s-0002ms-KX; Tue, 18 May 2004 06:49:16 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQ26o-0001mJ-7Z
	for pim@optimus.ietf.org; Tue, 18 May 2004 06:46:06 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA02418
	for <pim@ietf.org>; Tue, 18 May 2004 06:46:02 -0400 (EDT)
From: shiroko.nr@ncos.nec.co.jp
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BQ26k-0007Qv-4C
	for pim@ietf.org; Tue, 18 May 2004 06:46:02 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQ25p-00071i-00
	for pim@ietf.org; Tue, 18 May 2004 06:45:06 -0400
Received: from tyo202.gate.nec.co.jp ([202.32.8.202])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQ24s-0006FE-00
	for pim@ietf.org; Tue, 18 May 2004 06:44:06 -0400
Received: from mailgate4.nec.co.jp (mailgate54.nec.co.jp [10.7.69.197])
	by TYO202.gate.nec.co.jp (8.11.7/3.7W01080315) with ESMTP id i4IAhWY18194
	for <pim@ietf.org>; Tue, 18 May 2004 19:43:35 +0900 (JST)
Received: (from root@localhost) by mailgate4.nec.co.jp (8.11.7/3.7W-MAILGATE-NEC)
	id i4IAhWA29146 for pim@ietf.org; Tue, 18 May 2004 19:43:32 +0900 (JST)
Received: from ncos.nec.co.jp (mailgate2.ncos.nec.co.jp [10.40.15.12]) by mailsv5.nec.co.jp (8.11.7/3.7W-MAILSV4-NEC) with SMTP
	id i4IAhVa14466 for <pim@ietf.org>; Tue, 18 May 2004 19:43:31 +0900 (JST)
Received: (qmail 22940 invoked by uid 0); 18 May 2004 19:43:31 +0900
Received: from unknown (HELO bn4p0152) (10.43.80.152)
  by 172.16.255.129 with SMTP; 18 May 2004 19:43:31 +0900
To: pim@ietf.org
Message-Id: <20040518194333shiroko.nr@smtp.ncos.nec.co.jp>
Mime-Version: 1.0
X-Mailer: WeMail32[2.09A] ID:NCOSWM
Date: Tue, 18 May 2004 19:43:33 +0900
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=NO_REAL_NAME autolearn=no 
	version=2.60
Content-Transfer-Encoding: 7bit
Subject: [pim] IPv6 Register Fragmentation
Sender: pim-admin@ietf.org
Errors-To: pim-admin@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Id: Protocol Independent Multicast <pim.ietf.org>
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-Transfer-Encoding: 7bit


Hello,

I have a few comments regarding the Register message fragmentation in IPv6,
described as below in draft-ietf-pim-sm-v2-new-09.

    In IPv6, the DR MUST perform Path-MTU discovery, and an ICMP
    Fragmentation Required message MUST be sent by the encapsulating DR if
    it receives a packet that will not fit in the effective MTU of the
    tunnel.  If the MTU between the DR and the RP results in the effective
    tunnel MTU being smaller than 1280 (the IPv6 minimum MTU), the DR MUST
    send Fragmentation Required messages with an MTU value of 1280 and MUST
    fragment its PIM register messages as required, using an IPv6
    fragmentation header between the outer IPv6 header and the PIM Register
    header.

Here are my comments.

1) "ICMP Packet Too Big message" is appropriate rather than
   "ICMP Fragmentation Required message" in IPv6.

2) I believe that DR should not send ICMP Packet Too Big message
   when the original multicast packet is equal or smaller than
   the IPv6 minimum MTU. 
   The sender of multicast packets cannot send smaller packets,
   even if it has received such ICMP message. 

   I think IPv6 Register fragmentation should be treated the same as
   "IPv6 Tunnel Packet Fragmentation" described in RFC2473 Section 7.1.

   That is, ICMP "Packet Too Big" message should be sent by the
   encapsulating DR if the original IPv6 packet size is larger than
   the IPv6 minimum MTU. If the original IPv6 packet is equal or smaller
   than  the IPv6 minimum link MTU, DR must fragment its PIM register
   messages as required, using an IPv6 fragmentation header between
   the outer IPv6 header and the PIM Register header.

   IMHO, the encapsulating DR MAY fragment its register message whenever
   the original IPv6 packet size is larger than the effective tunnel MTU,
   and MAY not send ICMP "Packet Too Big" message.
   Because RP can process such fragmented register messages, and I think
   many implementations currently would works so. 

Any comments would be appreciated.

Best Regards,
Shiroko.

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


From exim@www1.ietf.org  Tue May 18 07:24:36 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA05238
	for <pim-archive@odin.ietf.org>; Tue, 18 May 2004 07:24:36 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQ2W8-0007xV-Ed
	for pim-archive@odin.ietf.org; Tue, 18 May 2004 07:12:16 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4IBCGNA030593
	for pim-archive@odin.ietf.org; Tue, 18 May 2004 07:12:16 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQ2NI-0005WW-Hb
	for pim-web-archive@optimus.ietf.org; Tue, 18 May 2004 07:03:08 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA03421
	for <pim-web-archive@ietf.org>; Tue, 18 May 2004 07:03:04 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BQ2NE-0006bo-Ed
	for pim-web-archive@ietf.org; Tue, 18 May 2004 07:03:04 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQ2MP-0006Cz-00
	for pim-web-archive@ietf.org; Tue, 18 May 2004 07:02:14 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQ2Lm-0005nN-00
	for pim-web-archive@ietf.org; Tue, 18 May 2004 07:01:34 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQ29s-0002ms-KX; Tue, 18 May 2004 06:49:16 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQ26o-0001mJ-7Z
	for pim@optimus.ietf.org; Tue, 18 May 2004 06:46:06 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA02418
	for <pim@ietf.org>; Tue, 18 May 2004 06:46:02 -0400 (EDT)
From: shiroko.nr@ncos.nec.co.jp
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BQ26k-0007Qv-4C
	for pim@ietf.org; Tue, 18 May 2004 06:46:02 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQ25p-00071i-00
	for pim@ietf.org; Tue, 18 May 2004 06:45:06 -0400
Received: from tyo202.gate.nec.co.jp ([202.32.8.202])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQ24s-0006FE-00
	for pim@ietf.org; Tue, 18 May 2004 06:44:06 -0400
Received: from mailgate4.nec.co.jp (mailgate54.nec.co.jp [10.7.69.197])
	by TYO202.gate.nec.co.jp (8.11.7/3.7W01080315) with ESMTP id i4IAhWY18194
	for <pim@ietf.org>; Tue, 18 May 2004 19:43:35 +0900 (JST)
Received: (from root@localhost) by mailgate4.nec.co.jp (8.11.7/3.7W-MAILGATE-NEC)
	id i4IAhWA29146 for pim@ietf.org; Tue, 18 May 2004 19:43:32 +0900 (JST)
Received: from ncos.nec.co.jp (mailgate2.ncos.nec.co.jp [10.40.15.12]) by mailsv5.nec.co.jp (8.11.7/3.7W-MAILSV4-NEC) with SMTP
	id i4IAhVa14466 for <pim@ietf.org>; Tue, 18 May 2004 19:43:31 +0900 (JST)
Received: (qmail 22940 invoked by uid 0); 18 May 2004 19:43:31 +0900
Received: from unknown (HELO bn4p0152) (10.43.80.152)
  by 172.16.255.129 with SMTP; 18 May 2004 19:43:31 +0900
To: pim@ietf.org
Message-Id: <20040518194333shiroko.nr@smtp.ncos.nec.co.jp>
Mime-Version: 1.0
X-Mailer: WeMail32[2.09A] ID:NCOSWM
Date: Tue, 18 May 2004 19:43:33 +0900
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [pim] IPv6 Register Fragmentation
Sender: pim-admin@ietf.org
Errors-To: pim-admin@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Id: Protocol Independent Multicast <pim.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=NO_REAL_NAME autolearn=no 
	version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


Hello,

I have a few comments regarding the Register message fragmentation in IPv6,
described as below in draft-ietf-pim-sm-v2-new-09.

    In IPv6, the DR MUST perform Path-MTU discovery, and an ICMP
    Fragmentation Required message MUST be sent by the encapsulating DR if
    it receives a packet that will not fit in the effective MTU of the
    tunnel.  If the MTU between the DR and the RP results in the effective
    tunnel MTU being smaller than 1280 (the IPv6 minimum MTU), the DR MUST
    send Fragmentation Required messages with an MTU value of 1280 and MUST
    fragment its PIM register messages as required, using an IPv6
    fragmentation header between the outer IPv6 header and the PIM Register
    header.

Here are my comments.

1) "ICMP Packet Too Big message" is appropriate rather than
   "ICMP Fragmentation Required message" in IPv6.

2) I believe that DR should not send ICMP Packet Too Big message
   when the original multicast packet is equal or smaller than
   the IPv6 minimum MTU. 
   The sender of multicast packets cannot send smaller packets,
   even if it has received such ICMP message. 

   I think IPv6 Register fragmentation should be treated the same as
   "IPv6 Tunnel Packet Fragmentation" described in RFC2473 Section 7.1.

   That is, ICMP "Packet Too Big" message should be sent by the
   encapsulating DR if the original IPv6 packet size is larger than
   the IPv6 minimum MTU. If the original IPv6 packet is equal or smaller
   than  the IPv6 minimum link MTU, DR must fragment its PIM register
   messages as required, using an IPv6 fragmentation header between
   the outer IPv6 header and the PIM Register header.

   IMHO, the encapsulating DR MAY fragment its register message whenever
   the original IPv6 packet size is larger than the effective tunnel MTU,
   and MAY not send ICMP "Packet Too Big" message.
   Because RP can process such fragmented register messages, and I think
   many implementations currently would works so. 

Any comments would be appreciated.

Best Regards,
Shiroko.

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



From pim-admin@ietf.org  Tue May 18 20:16:19 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA00085
	for <pim-archive@lists.ietf.org>; Tue, 18 May 2004 20:16:19 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQEcr-0005Qw-14; Tue, 18 May 2004 20:08:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQEVK-0003aE-NW
	for pim@optimus.ietf.org; Tue, 18 May 2004 20:00:14 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA29221
	for <pim@ietf.org>; Tue, 18 May 2004 20:00:13 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BQEVI-0001SY-PV
	for pim@ietf.org; Tue, 18 May 2004 20:00:12 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQEUL-0001QD-00
	for pim@ietf.org; Tue, 18 May 2004 19:59:14 -0400
Received: from smtp1.procket.com ([65.174.124.36])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQEU8-0001Ns-00
	for pim@ietf.org; Tue, 18 May 2004 19:59:00 -0400
Received: from miata.procket.com (mil0-fw00-d-1.procket.com [65.174.124.60])
	by smtp1.procket.com (8.12.8p1/8.12.1) with ESMTP id i4J29xpL040119
	for <pim@ietf.org>; Tue, 18 May 2004 19:09:59 -0700 (PDT)
Received: from dino-pc.procket.com (dino-pc.procket.com [10.4.17.33])
	by miata.procket.com (8.12.1/8.12.1) with ESMTP id i4INwPd1019972;
	Tue, 18 May 2004 16:58:25 -0700 (PDT)
Received: (from dino@localhost)
	by dino-pc.procket.com (8.12.1/8.12.1) id i4INwPhN022305;
	Tue, 18 May 2004 16:58:25 -0700
Date: Tue, 18 May 2004 16:58:25 -0700
Message-Id: <200405182358.i4INwPhN022305@dino-pc.procket.com>
From: Dino Farinacci <dino@procket.com>
To: pim@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Subject: [pim] I-D ACTION:draft-farinacci-pim-pop-count-00.txt
Sender: pim-admin@ietf.org
Errors-To: pim-admin@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Id: Protocol Independent Multicast <pim.ietf.org>
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>

    Folks, please comment.

Dino

-------------------------------------------------------------------------------
A New Internet-Draft is available from the on-line Internet-Drafts directories.


	Title		: Population Count Extensions to PIM
	Author(s)	: D. Farinacci, G. Shepherd
	Filename	: draft-farinacci-pim-pop-count-00.txt
	Pages		: 8
	Date		: 2004-5-18
	
Performing an approximation in some form of multicast distribution
   tree accounting proves to be useful for billing and debugging. The
   Population Count extensions to PIM, documented in this draft,
   provide an efficient method to achieve this.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-farinacci-pim-pop-count-00.txt

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


Internet-Drafts are also available by anonymous FTP. Login with th
-------------------------------------------------------------------------------



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


From exim@www1.ietf.org  Tue May 18 20:28:38 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA00686
	for <pim-archive@odin.ietf.org>; Tue, 18 May 2004 20:28:38 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQEuy-0008Jk-Sf
	for pim-archive@odin.ietf.org; Tue, 18 May 2004 20:26:45 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4J0QiF0031972
	for pim-archive@odin.ietf.org; Tue, 18 May 2004 20:26:44 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQElq-0006OP-G4
	for pim-web-archive@optimus.ietf.org; Tue, 18 May 2004 20:17:18 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA00155
	for <pim-web-archive@ietf.org>; Tue, 18 May 2004 20:17:16 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BQElo-0002gG-G7
	for pim-web-archive@ietf.org; Tue, 18 May 2004 20:17:16 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQEkt-0002d3-00
	for pim-web-archive@ietf.org; Tue, 18 May 2004 20:16:19 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQEkO-0002a6-00
	for pim-web-archive@ietf.org; Tue, 18 May 2004 20:15:48 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQEcr-0005Qw-14; Tue, 18 May 2004 20:08:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQEVK-0003aE-NW
	for pim@optimus.ietf.org; Tue, 18 May 2004 20:00:14 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA29221
	for <pim@ietf.org>; Tue, 18 May 2004 20:00:13 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BQEVI-0001SY-PV
	for pim@ietf.org; Tue, 18 May 2004 20:00:12 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQEUL-0001QD-00
	for pim@ietf.org; Tue, 18 May 2004 19:59:14 -0400
Received: from smtp1.procket.com ([65.174.124.36])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQEU8-0001Ns-00
	for pim@ietf.org; Tue, 18 May 2004 19:59:00 -0400
Received: from miata.procket.com (mil0-fw00-d-1.procket.com [65.174.124.60])
	by smtp1.procket.com (8.12.8p1/8.12.1) with ESMTP id i4J29xpL040119
	for <pim@ietf.org>; Tue, 18 May 2004 19:09:59 -0700 (PDT)
Received: from dino-pc.procket.com (dino-pc.procket.com [10.4.17.33])
	by miata.procket.com (8.12.1/8.12.1) with ESMTP id i4INwPd1019972;
	Tue, 18 May 2004 16:58:25 -0700 (PDT)
Received: (from dino@localhost)
	by dino-pc.procket.com (8.12.1/8.12.1) id i4INwPhN022305;
	Tue, 18 May 2004 16:58:25 -0700
Date: Tue, 18 May 2004 16:58:25 -0700
Message-Id: <200405182358.i4INwPhN022305@dino-pc.procket.com>
From: Dino Farinacci <dino@procket.com>
To: pim@ietf.org
Subject: [pim] I-D ACTION:draft-farinacci-pim-pop-count-00.txt
Sender: pim-admin@ietf.org
Errors-To: pim-admin@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Id: Protocol Independent Multicast <pim.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60

    Folks, please comment.

Dino

-------------------------------------------------------------------------------
A New Internet-Draft is available from the on-line Internet-Drafts directories.


	Title		: Population Count Extensions to PIM
	Author(s)	: D. Farinacci, G. Shepherd
	Filename	: draft-farinacci-pim-pop-count-00.txt
	Pages		: 8
	Date		: 2004-5-18
	
Performing an approximation in some form of multicast distribution
   tree accounting proves to be useful for billing and debugging. The
   Population Count extensions to PIM, documented in this draft,
   provide an efficient method to achieve this.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-farinacci-pim-pop-count-00.txt

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


Internet-Drafts are also available by anonymous FTP. Login with th
-------------------------------------------------------------------------------



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



From pim-admin@ietf.org  Wed May 19 15:55:34 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09106
	for <pim-archive@lists.ietf.org>; Wed, 19 May 2004 15:55:34 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQWmT-0008FH-DV; Wed, 19 May 2004 15:31:09 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQW92-0003En-Br
	for pim@optimus.ietf.org; Wed, 19 May 2004 14:50:24 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA00307
	for <pim@ietf.org>; Wed, 19 May 2004 14:50:21 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BQW8z-0000bV-GG
	for pim@ietf.org; Wed, 19 May 2004 14:50:21 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQW89-0000SR-00
	for pim@ietf.org; Wed, 19 May 2004 14:49:30 -0400
Received: from tyholt.uninett.no ([158.38.60.10])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQW71-00009C-00
	for pim@ietf.org; Wed, 19 May 2004 14:48:19 -0400
Received: from sverresborg.uninett.no (sverresborg.uninett.no [IPv6:2001:700:e000:0:204:75ff:fee4:423b])
	by tyholt.uninett.no (8.12.10/8.12.10) with ESMTP id i4JIlkDW031490;
	Wed, 19 May 2004 20:47:46 +0200
Received: (from venaas@localhost)
	by sverresborg.uninett.no (8.12.8/8.12.8/Submit) id i4JIljSf012410;
	Wed, 19 May 2004 20:47:45 +0200
X-Authentication-Warning: sverresborg.uninett.no: venaas set sender to Stig.Venaas@uninett.no using -f
Date: Wed, 19 May 2004 20:47:45 +0200
From: Stig Venaas <Stig.Venaas@uninett.no>
To: shiroko.nr@ncos.nec.co.jp
Cc: pim@ietf.org
Subject: Re: [pim] IPv6 Register Fragmentation
Message-ID: <20040519184745.GA12370@sverresborg.uninett.no>
References: <20040518194333shiroko.nr@smtp.ncos.nec.co.jp>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20040518194333shiroko.nr@smtp.ncos.nec.co.jp>
User-Agent: Mutt/1.4.1i
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: pim-admin@ietf.org
Errors-To: pim-admin@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Id: Protocol Independent Multicast <pim.ietf.org>
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>

On Tue, May 18, 2004 at 07:43:33PM +0900, shiroko.nr@ncos.nec.co.jp wrote:
> 
> Hello,
> 
> I have a few comments regarding the Register message fragmentation in IPv6,
> described as below in draft-ietf-pim-sm-v2-new-09.

I also have a comment on this that I've meant to give for some time.

>     In IPv6, the DR MUST perform Path-MTU discovery, and an ICMP
>     Fragmentation Required message MUST be sent by the encapsulating DR if
>     it receives a packet that will not fit in the effective MTU of the
>     tunnel.  If the MTU between the DR and the RP results in the effective
[...]

I don't think is a good idea. Usually I think it's better to have
the DR simply fragment the register packets instead of sending
"Packet Too Big" back.

Let me try to describe why I don't like it. Let's say for simplicity
that we have a PIM domain where all links have MTU 1500, and a source
sends 1500 byte datagrams. The MTU of the register tunnel is <1500 so
the DR will send ICMP PTB to the source. The source learns the smaller
PMTU and starts sending fragmented datagrams.

I believe that it's common for the RP to switch to native forwarding
immediately. Once the switch is done there's no need for fragmentation.
But the source will keep fragmenting until it tries to send larger
packets again, that typically happens after 10 minutes. At least some
implementations use 10 minutes, and it's also suggested in RFC 1191.

So, the first few packets, perhaps for a couple of seconds, are
sent as register packets; while the source will unnecessarily keep
doing it for say 10 minutes.

In this case I believe it's better for the DR to fragment the packets
itself. I would rather say that the DR MAY send ICMP PTB. Whether the
DR does it or not can be implementation specific. Some DRs could
immediately send ICMP PTB back, others could do it if they keep
registering for a long time or if load is too high or whatever. But
I don't think it should be a MUST.

I'm aware that one is supposed to always do PMTU discovery in IPv6
and do fragmentation at the source, but do we really need to follow
this for register tunnels?

Stig

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


From pim-admin@ietf.org  Wed May 19 17:32:34 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA19255
	for <pim-archive@lists.ietf.org>; Wed, 19 May 2004 17:32:33 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQYR1-0002sV-S3; Wed, 19 May 2004 17:17:07 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQXVv-0006TK-E3
	for pim@optimus.ietf.org; Wed, 19 May 2004 16:18:07 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11304
	for <pim@ietf.org>; Wed, 19 May 2004 16:18:04 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BQXVt-0006Qw-JE
	for pim@ietf.org; Wed, 19 May 2004 16:18:05 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQXUX-00065u-00
	for pim@ietf.org; Wed, 19 May 2004 16:16:42 -0400
Received: from netcore.fi ([193.94.160.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQXTE-0005hY-00
	for pim@ietf.org; Wed, 19 May 2004 16:15:20 -0400
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id i4JKEZC23507;
	Wed, 19 May 2004 23:14:35 +0300
Date: Wed, 19 May 2004 23:14:35 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: Stig Venaas <Stig.Venaas@uninett.no>
cc: shiroko.nr@ncos.nec.co.jp, <pim@ietf.org>
Subject: Re: [pim] IPv6 Register Fragmentation
In-Reply-To: <20040519184745.GA12370@sverresborg.uninett.no>
Message-ID: <Pine.LNX.4.44.0405192313260.23234-100000@netcore.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: pim-admin@ietf.org
Errors-To: pim-admin@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Id: Protocol Independent Multicast <pim.ietf.org>
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>

On Wed, 19 May 2004, Stig Venaas wrote:
> I'm aware that one is supposed to always do PMTU discovery in IPv6
> and do fragmentation at the source, but do we really need to follow
> this for register tunnels?

Bear in mind that this requires also defragmentation at decapsulation.

There's at least one hardware implementation that AFAIR doesn't do 
defrag.

-- 
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-admin@ietf.org  Wed May 19 17:35:26 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA19531
	for <pim-archive@lists.ietf.org>; Wed, 19 May 2004 17:35:26 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQYbr-0007pg-6t; Wed, 19 May 2004 17:28:19 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQXlp-00036W-Dy
	for pim@optimus.ietf.org; Wed, 19 May 2004 16:34:33 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA12767
	for <pim@ietf.org>; Wed, 19 May 2004 16:34:30 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BQXln-0000wJ-Ej
	for pim@ietf.org; Wed, 19 May 2004 16:34:31 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQXkM-0000cT-00
	for pim@ietf.org; Wed, 19 May 2004 16:33:03 -0400
Received: from tyholt.uninett.no ([158.38.60.10])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQXiF-0000Es-00
	for pim@ietf.org; Wed, 19 May 2004 16:30:51 -0400
Received: from sverresborg.uninett.no (sverresborg.uninett.no [IPv6:2001:700:e000:0:204:75ff:fee4:423b])
	by tyholt.uninett.no (8.12.10/8.12.10) with ESMTP id i4JKUIDW025942;
	Wed, 19 May 2004 22:30:18 +0200
Received: (from venaas@localhost)
	by sverresborg.uninett.no (8.12.8/8.12.8/Submit) id i4JKUH5t012555;
	Wed, 19 May 2004 22:30:17 +0200
X-Authentication-Warning: sverresborg.uninett.no: venaas set sender to Stig.Venaas@uninett.no using -f
Date: Wed, 19 May 2004 22:30:17 +0200
From: Stig Venaas <Stig.Venaas@uninett.no>
To: Pekka Savola <pekkas@netcore.fi>
Cc: shiroko.nr@ncos.nec.co.jp, pim@ietf.org
Subject: Re: [pim] IPv6 Register Fragmentation
Message-ID: <20040519203017.GA12539@sverresborg.uninett.no>
References: <20040519184745.GA12370@sverresborg.uninett.no> <Pine.LNX.4.44.0405192313260.23234-100000@netcore.fi>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.LNX.4.44.0405192313260.23234-100000@netcore.fi>
User-Agent: Mutt/1.4.1i
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: pim-admin@ietf.org
Errors-To: pim-admin@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Id: Protocol Independent Multicast <pim.ietf.org>
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>

On Wed, May 19, 2004 at 11:14:35PM +0300, Pekka Savola wrote:
> On Wed, 19 May 2004, Stig Venaas wrote:
> > I'm aware that one is supposed to always do PMTU discovery in IPv6
> > and do fragmentation at the source, but do we really need to follow
> > this for register tunnels?
> 
> Bear in mind that this requires also defragmentation at decapsulation.
> 
> There's at least one hardware implementation that AFAIR doesn't do 
> defrag.

ok, but the draft also says:

   In IPv6, the DR MUST perform Path-MTU discovery, and an ICMP
   Fragmentation Required message MUST be sent by the encapsulating
   DR if it receives a packet that will not fit in the effective MTU
   of the tunnel.  If the MTU between the DR and the RP results in the
   effective tunnel MTU being smaller than 1280 (the IPv6 minimum MTU),
   the DR MUST send Fragmentation Required messages with an MTU value
   of 1280 and MUST fragment its PIM register messages as required,
   using an IPv6 fragmentation header between the outer IPv6 header
   and the PIM Register header.

So there are valid cases where the register message will be fragmented
anyway (even with the current MUST).

One more thing. By only reading the text above, it might seem that
one should send ICMP PTB (FragReq) every time a packet too large
for the <1280 register tunnel MTU is received. I don't think it
should be, at least not if the packet was 1280. In that case the
source won't fragment the packet anyway and possibly keep sending
1280 byte packets. Also IPv6 hosts not doing PMTU discovery would
send packets up to 1280 anyway. So I believe one should only send
ICMP PTP if the packet was >1280.

Stig

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


From exim@www1.ietf.org  Wed May 19 17:59:12 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA22548
	for <pim-archive@odin.ietf.org>; Wed, 19 May 2004 17:59:12 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQZ2K-0001zh-O2
	for pim-archive@odin.ietf.org; Wed, 19 May 2004 17:55:42 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4JLtec8007661
	for pim-archive@odin.ietf.org; Wed, 19 May 2004 17:55:40 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQYnI-00057D-0y
	for pim-web-archive@optimus.ietf.org; Wed, 19 May 2004 17:40:08 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA20477
	for <pim-web-archive@ietf.org>; Wed, 19 May 2004 17:40:04 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BQYnF-0004rF-E9
	for pim-web-archive@ietf.org; Wed, 19 May 2004 17:40:05 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQYkU-0004EB-00
	for pim-web-archive@ietf.org; Wed, 19 May 2004 17:37:15 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQYfV-0003Ue-00
	for pim-web-archive@ietf.org; Wed, 19 May 2004 17:32:05 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQYR1-0002sV-S3; Wed, 19 May 2004 17:17:07 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQXVv-0006TK-E3
	for pim@optimus.ietf.org; Wed, 19 May 2004 16:18:07 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11304
	for <pim@ietf.org>; Wed, 19 May 2004 16:18:04 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BQXVt-0006Qw-JE
	for pim@ietf.org; Wed, 19 May 2004 16:18:05 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQXUX-00065u-00
	for pim@ietf.org; Wed, 19 May 2004 16:16:42 -0400
Received: from netcore.fi ([193.94.160.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQXTE-0005hY-00
	for pim@ietf.org; Wed, 19 May 2004 16:15:20 -0400
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id i4JKEZC23507;
	Wed, 19 May 2004 23:14:35 +0300
Date: Wed, 19 May 2004 23:14:35 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: Stig Venaas <Stig.Venaas@uninett.no>
cc: shiroko.nr@ncos.nec.co.jp, <pim@ietf.org>
Subject: Re: [pim] IPv6 Register Fragmentation
In-Reply-To: <20040519184745.GA12370@sverresborg.uninett.no>
Message-ID: <Pine.LNX.4.44.0405192313260.23234-100000@netcore.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: pim-admin@ietf.org
Errors-To: pim-admin@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Id: Protocol Independent Multicast <pim.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60

On Wed, 19 May 2004, Stig Venaas wrote:
> I'm aware that one is supposed to always do PMTU discovery in IPv6
> and do fragmentation at the source, but do we really need to follow
> this for register tunnels?

Bear in mind that this requires also defragmentation at decapsulation.

There's at least one hardware implementation that AFAIR doesn't do 
defrag.

-- 
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 exim@www1.ietf.org  Wed May 19 18:00:09 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA22719
	for <pim-archive@odin.ietf.org>; Wed, 19 May 2004 18:00:09 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQZ2P-00024A-0d
	for pim-archive@odin.ietf.org; Wed, 19 May 2004 17:55:45 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4JLtiAd007936
	for pim-archive@odin.ietf.org; Wed, 19 May 2004 17:55:44 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQYo8-0005TH-AM
	for pim-web-archive@optimus.ietf.org; Wed, 19 May 2004 17:41:00 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA20651
	for <pim-web-archive@ietf.org>; Wed, 19 May 2004 17:40:56 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BQYo5-00050W-Qa
	for pim-web-archive@ietf.org; Wed, 19 May 2004 17:40:57 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQYm5-0004YT-00
	for pim-web-archive@ietf.org; Wed, 19 May 2004 17:38:54 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQYiH-0003oW-00
	for pim-web-archive@ietf.org; Wed, 19 May 2004 17:34:57 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQYbr-0007pg-6t; Wed, 19 May 2004 17:28:19 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQXlp-00036W-Dy
	for pim@optimus.ietf.org; Wed, 19 May 2004 16:34:33 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA12767
	for <pim@ietf.org>; Wed, 19 May 2004 16:34:30 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BQXln-0000wJ-Ej
	for pim@ietf.org; Wed, 19 May 2004 16:34:31 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQXkM-0000cT-00
	for pim@ietf.org; Wed, 19 May 2004 16:33:03 -0400
Received: from tyholt.uninett.no ([158.38.60.10])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQXiF-0000Es-00
	for pim@ietf.org; Wed, 19 May 2004 16:30:51 -0400
Received: from sverresborg.uninett.no (sverresborg.uninett.no [IPv6:2001:700:e000:0:204:75ff:fee4:423b])
	by tyholt.uninett.no (8.12.10/8.12.10) with ESMTP id i4JKUIDW025942;
	Wed, 19 May 2004 22:30:18 +0200
Received: (from venaas@localhost)
	by sverresborg.uninett.no (8.12.8/8.12.8/Submit) id i4JKUH5t012555;
	Wed, 19 May 2004 22:30:17 +0200
X-Authentication-Warning: sverresborg.uninett.no: venaas set sender to Stig.Venaas@uninett.no using -f
Date: Wed, 19 May 2004 22:30:17 +0200
From: Stig Venaas <Stig.Venaas@uninett.no>
To: Pekka Savola <pekkas@netcore.fi>
Cc: shiroko.nr@ncos.nec.co.jp, pim@ietf.org
Subject: Re: [pim] IPv6 Register Fragmentation
Message-ID: <20040519203017.GA12539@sverresborg.uninett.no>
References: <20040519184745.GA12370@sverresborg.uninett.no> <Pine.LNX.4.44.0405192313260.23234-100000@netcore.fi>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.LNX.4.44.0405192313260.23234-100000@netcore.fi>
User-Agent: Mutt/1.4.1i
Sender: pim-admin@ietf.org
Errors-To: pim-admin@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Id: Protocol Independent Multicast <pim.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60

On Wed, May 19, 2004 at 11:14:35PM +0300, Pekka Savola wrote:
> On Wed, 19 May 2004, Stig Venaas wrote:
> > I'm aware that one is supposed to always do PMTU discovery in IPv6
> > and do fragmentation at the source, but do we really need to follow
> > this for register tunnels?
> 
> Bear in mind that this requires also defragmentation at decapsulation.
> 
> There's at least one hardware implementation that AFAIR doesn't do 
> defrag.

ok, but the draft also says:

   In IPv6, the DR MUST perform Path-MTU discovery, and an ICMP
   Fragmentation Required message MUST be sent by the encapsulating
   DR if it receives a packet that will not fit in the effective MTU
   of the tunnel.  If the MTU between the DR and the RP results in the
   effective tunnel MTU being smaller than 1280 (the IPv6 minimum MTU),
   the DR MUST send Fragmentation Required messages with an MTU value
   of 1280 and MUST fragment its PIM register messages as required,
   using an IPv6 fragmentation header between the outer IPv6 header
   and the PIM Register header.

So there are valid cases where the register message will be fragmented
anyway (even with the current MUST).

One more thing. By only reading the text above, it might seem that
one should send ICMP PTB (FragReq) every time a packet too large
for the <1280 register tunnel MTU is received. I don't think it
should be, at least not if the packet was 1280. In that case the
source won't fragment the packet anyway and possibly keep sending
1280 byte packets. Also IPv6 hosts not doing PMTU discovery would
send packets up to 1280 anyway. So I believe one should only send
ICMP PTP if the packet was >1280.

Stig

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



From pim-admin@ietf.org  Thu May 20 03:49:37 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA03557
	for <pim-archive@lists.ietf.org>; Thu, 20 May 2004 03:49:37 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQiEi-0002j2-1J; Thu, 20 May 2004 03:45:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQiDh-0002Yz-A2
	for pim@optimus.ietf.org; Thu, 20 May 2004 03:44:01 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA03428
	for <pim@ietf.org>; Thu, 20 May 2004 03:43:59 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BQiDe-0005R3-RB
	for pim@ietf.org; Thu, 20 May 2004 03:43:58 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQiCV-0005Fd-00
	for pim@ietf.org; Thu, 20 May 2004 03:42:48 -0400
Received: from netcore.fi ([193.94.160.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQiBy-00052a-00
	for pim@ietf.org; Thu, 20 May 2004 03:42:14 -0400
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id i4K7fac01232;
	Thu, 20 May 2004 10:41:36 +0300
Date: Thu, 20 May 2004 10:41:35 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: Mike McBride <mmcbride@cisco.com>
cc: pim@ietf.org
Subject: Re: [pim] WG Last Call - draft-ietf-pim-bidir-06
In-Reply-To: <Pine.GSO.4.58.0404281220260.8177@irp-view6.cisco.com>
Message-ID: <Pine.LNX.4.44.0405201000220.649-100000@netcore.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: pim-admin@ietf.org
Errors-To: pim-admin@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Id: Protocol Independent Multicast <pim.ietf.org>
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>

On Wed, 28 Apr 2004, Mike McBride wrote:
> Today begins a Working Group Last Call for the Bi-Directional PIM
> Specification. The Last Call runs 2 weeks from Wednesday, April 28th, 2004
> to Wednesday, May 12th, 2004.
> 
> Please review this document and send comments either to the list or
> directly to the authors.

Sorry for missing the LC DL a bit. A couple of observations.

Major comment fundamental comment:
----------------------------------

I fail to see the high-level justification for this approach, perhaps
a more extensive "Protocol Overview" would be called for if I've
misunderstood something.

Basically, I don't see what it is that requires 45 pages of
specification and new mechanisms which weren't available in PIM-SM!  
The fundamental function of bidir-PIM appears to be:
 
   Forwarding packets from the adjacent links without 
   register-encapsulation towards the RP, for groups supported by 
   bidir-PIM.

But the spec also includes e.g. DF election procedures (11 pages).

AFAICS, what you could do is just specify that:
  a) DF is automatically elected the same way as DR, but just among 
     those DRs which are bidir-capable.  Code reuse and 
     simplification.  Why should different DF's be used for different
     groups?  This way it works for embedded-RP as well.
  b) if the group has been configured as bidir, instead of  
     encapsulating, just send it over towards the RP.
  c) if the group has been configured as bidir, the routers along the 
     path are expected to be bidir-capable.  The only change they need 
     is to (if I'm not mistaken) is to add the RP address for all 
     groups G to their olist, i.e., pass the data packets towards the 
     RP if they come from the right direction. 
  d) if you'd send a packet to a router using bidir mechanisms but it 
     doesn't advertise to be bidir-capable with hellos, log an error.

   15 pages of very simple spec, and this would also work for embedded 
   RP.

Could someone please enlighten me what is the justification behind the 
current design?  I see that killing data encap/decap is important, but 
I fail to see the need for this way too complex approach.

I guess the reason here is "no data driven events", but I can't see
how this applies, as DF election is also a data-driven event
(something must trigger the election to happen for a specific group --
for example if there is no group-specific state and the first thing to
a new group is a sender-only branch).

More minor comments:
--------------------

Bidir PIM introduces the Bidir_Capable PIM-Hello option that MUST be
included in all Hello messages from a Bidir-PIM capable router.  The
Bidir_Capable option advertises the router's ability to participate in
the Bidir-PIM protocol. The format of the Bidir_Capable option is
described in section 3.7.

==> HELLO?!?!!?!?  Do you mean that every router in a domain that is
bidir-capable starts logging errors about every neighbor they have
which is not bidir-capable?!??  Say goodbye to incremental deployment 
and adding bidir capability on by default!

The warning is should probably something that should be activated if a 
group has been configured as bidir, but your neighbor isn't, or if you 
try to use bidir forwarding algorithm towards the neighbor, and it 
isn't bidir-capable.

...

If instead the administrator chooses to configure the RPA to be the
address of an interface of a specific router then nothing changes.

==> s/an interface/a physical interface/ ?  
==> fwiw, this section is IMHO quite confusing and pretty much 

BIDIR-PIM messages are multicast with TTL 1 to the `ALL-PIM-ROUTERS'
group `224.0.0.13'.

==> IPv6 support, anyone?

RP-Address
     The bidir RPA for which the election is taking place (note that the
     length of this field is more than 32 bits).

==> the point of the bit-wise diagrams is that they are accurate.  If 
it isn't 32 bits, change it accordingly!  The figures aren't just 
listing which fields come after another, but describing where one 
ends and the another begins.

....

4.  RP Discovery

Routers discover that a range of multicast group addresses operates in
bi-directional mode and the address of the Rendezvous-Point address
(RPA) serving the group range either through static configuration or
using an automatic RP discovery mechanism like the PIM Bootsrtap
mechanism (BSR).  [9] or Auto-RP.

==> what is the BIDIR interdomain strategy?  There's no need for such, 
I think, because it'll "just work the same way as PIM-SM" if you use 
MSDP, but it would not hurt to spell it out.

==> s/BSR). /BSR)/, s/Bootsrtap/Bootstrap/

==> It would be worth stating (because it's not obvious) that the BSR 
discovery works by the RP setting the bidir-capable bit in the 
Encoded-Group Address (this isn't yet reflected in the bsr spec).

5.3.  Authentication Using IPsec

The IPsec [5] transport mode using the Authentication Header (AH) is 
the RECOMMENDED method to prevent the above attacks against BIDIR-PIM.

It is RECOMMENDED that IPsec authentication be applied to all 
BIDIR-PIM protocol messages.

==> this is totally bogus recommendation, and luckily enough the 
PIM-SM spec uses only MAY.  This would require manual key config on 
the routers per interfaces, and is completely unrealistic.


editorials:
-----------

     This document discusses Bi-directional PIM, a variant of PIM
     Sparse-Mode [4] that builds bi-directional shared trees

==> no refs in the abstract.

"OPTIONAL" are to be interpreted as described in RFC 2119 and indicate

==> maybe should add an explicit ref to 2119.

In this respect BIDIR-PIM differs from PIM-SM that
      requires an actual router to be configured as the Rendezvous Point
      (RP).

==> that requires --> that _it_ requires?  however this is not clear 
whether "it" would refer to bidir of pim-sm.

-- 
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 exim@www1.ietf.org  Thu May 20 03:53:24 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA03688
	for <pim-archive@odin.ietf.org>; Thu, 20 May 2004 03:53:24 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQiL3-0003nl-VK
	for pim-archive@odin.ietf.org; Thu, 20 May 2004 03:51:37 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4K7pbB0014609
	for pim-archive@odin.ietf.org; Thu, 20 May 2004 03:51:37 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQiK1-0003Zb-TQ
	for pim-web-archive@optimus.ietf.org; Thu, 20 May 2004 03:50:33 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA03601
	for <pim-web-archive@ietf.org>; Thu, 20 May 2004 03:50:31 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BQiJz-0006ZY-EK
	for pim-web-archive@ietf.org; Thu, 20 May 2004 03:50:31 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQiJ1-0006PY-00
	for pim-web-archive@ietf.org; Thu, 20 May 2004 03:49:32 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQiId-0006FT-00
	for pim-web-archive@ietf.org; Thu, 20 May 2004 03:49:07 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQiEi-0002j2-1J; Thu, 20 May 2004 03:45:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQiDh-0002Yz-A2
	for pim@optimus.ietf.org; Thu, 20 May 2004 03:44:01 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA03428
	for <pim@ietf.org>; Thu, 20 May 2004 03:43:59 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BQiDe-0005R3-RB
	for pim@ietf.org; Thu, 20 May 2004 03:43:58 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQiCV-0005Fd-00
	for pim@ietf.org; Thu, 20 May 2004 03:42:48 -0400
Received: from netcore.fi ([193.94.160.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQiBy-00052a-00
	for pim@ietf.org; Thu, 20 May 2004 03:42:14 -0400
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id i4K7fac01232;
	Thu, 20 May 2004 10:41:36 +0300
Date: Thu, 20 May 2004 10:41:35 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: Mike McBride <mmcbride@cisco.com>
cc: pim@ietf.org
Subject: Re: [pim] WG Last Call - draft-ietf-pim-bidir-06
In-Reply-To: <Pine.GSO.4.58.0404281220260.8177@irp-view6.cisco.com>
Message-ID: <Pine.LNX.4.44.0405201000220.649-100000@netcore.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: pim-admin@ietf.org
Errors-To: pim-admin@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Id: Protocol Independent Multicast <pim.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60

On Wed, 28 Apr 2004, Mike McBride wrote:
> Today begins a Working Group Last Call for the Bi-Directional PIM
> Specification. The Last Call runs 2 weeks from Wednesday, April 28th, 2004
> to Wednesday, May 12th, 2004.
> 
> Please review this document and send comments either to the list or
> directly to the authors.

Sorry for missing the LC DL a bit. A couple of observations.

Major comment fundamental comment:
----------------------------------

I fail to see the high-level justification for this approach, perhaps
a more extensive "Protocol Overview" would be called for if I've
misunderstood something.

Basically, I don't see what it is that requires 45 pages of
specification and new mechanisms which weren't available in PIM-SM!  
The fundamental function of bidir-PIM appears to be:
 
   Forwarding packets from the adjacent links without 
   register-encapsulation towards the RP, for groups supported by 
   bidir-PIM.

But the spec also includes e.g. DF election procedures (11 pages).

AFAICS, what you could do is just specify that:
  a) DF is automatically elected the same way as DR, but just among 
     those DRs which are bidir-capable.  Code reuse and 
     simplification.  Why should different DF's be used for different
     groups?  This way it works for embedded-RP as well.
  b) if the group has been configured as bidir, instead of  
     encapsulating, just send it over towards the RP.
  c) if the group has been configured as bidir, the routers along the 
     path are expected to be bidir-capable.  The only change they need 
     is to (if I'm not mistaken) is to add the RP address for all 
     groups G to their olist, i.e., pass the data packets towards the 
     RP if they come from the right direction. 
  d) if you'd send a packet to a router using bidir mechanisms but it 
     doesn't advertise to be bidir-capable with hellos, log an error.

   15 pages of very simple spec, and this would also work for embedded 
   RP.

Could someone please enlighten me what is the justification behind the 
current design?  I see that killing data encap/decap is important, but 
I fail to see the need for this way too complex approach.

I guess the reason here is "no data driven events", but I can't see
how this applies, as DF election is also a data-driven event
(something must trigger the election to happen for a specific group --
for example if there is no group-specific state and the first thing to
a new group is a sender-only branch).

More minor comments:
--------------------

Bidir PIM introduces the Bidir_Capable PIM-Hello option that MUST be
included in all Hello messages from a Bidir-PIM capable router.  The
Bidir_Capable option advertises the router's ability to participate in
the Bidir-PIM protocol. The format of the Bidir_Capable option is
described in section 3.7.

==> HELLO?!?!!?!?  Do you mean that every router in a domain that is
bidir-capable starts logging errors about every neighbor they have
which is not bidir-capable?!??  Say goodbye to incremental deployment 
and adding bidir capability on by default!

The warning is should probably something that should be activated if a 
group has been configured as bidir, but your neighbor isn't, or if you 
try to use bidir forwarding algorithm towards the neighbor, and it 
isn't bidir-capable.

...

If instead the administrator chooses to configure the RPA to be the
address of an interface of a specific router then nothing changes.

==> s/an interface/a physical interface/ ?  
==> fwiw, this section is IMHO quite confusing and pretty much 

BIDIR-PIM messages are multicast with TTL 1 to the `ALL-PIM-ROUTERS'
group `224.0.0.13'.

==> IPv6 support, anyone?

RP-Address
     The bidir RPA for which the election is taking place (note that the
     length of this field is more than 32 bits).

==> the point of the bit-wise diagrams is that they are accurate.  If 
it isn't 32 bits, change it accordingly!  The figures aren't just 
listing which fields come after another, but describing where one 
ends and the another begins.

....

4.  RP Discovery

Routers discover that a range of multicast group addresses operates in
bi-directional mode and the address of the Rendezvous-Point address
(RPA) serving the group range either through static configuration or
using an automatic RP discovery mechanism like the PIM Bootsrtap
mechanism (BSR).  [9] or Auto-RP.

==> what is the BIDIR interdomain strategy?  There's no need for such, 
I think, because it'll "just work the same way as PIM-SM" if you use 
MSDP, but it would not hurt to spell it out.

==> s/BSR). /BSR)/, s/Bootsrtap/Bootstrap/

==> It would be worth stating (because it's not obvious) that the BSR 
discovery works by the RP setting the bidir-capable bit in the 
Encoded-Group Address (this isn't yet reflected in the bsr spec).

5.3.  Authentication Using IPsec

The IPsec [5] transport mode using the Authentication Header (AH) is 
the RECOMMENDED method to prevent the above attacks against BIDIR-PIM.

It is RECOMMENDED that IPsec authentication be applied to all 
BIDIR-PIM protocol messages.

==> this is totally bogus recommendation, and luckily enough the 
PIM-SM spec uses only MAY.  This would require manual key config on 
the routers per interfaces, and is completely unrealistic.


editorials:
-----------

     This document discusses Bi-directional PIM, a variant of PIM
     Sparse-Mode [4] that builds bi-directional shared trees

==> no refs in the abstract.

"OPTIONAL" are to be interpreted as described in RFC 2119 and indicate

==> maybe should add an explicit ref to 2119.

In this respect BIDIR-PIM differs from PIM-SM that
      requires an actual router to be configured as the Rendezvous Point
      (RP).

==> that requires --> that _it_ requires?  however this is not clear 
whether "it" would refer to bidir of pim-sm.

-- 
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-admin@ietf.org  Thu May 20 12:03:45 2004
Received: from optimus.ietf.org (www.iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA27668
	for <pim-archive@lists.ietf.org>; Thu, 20 May 2004 12:03:45 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQpl8-0001FF-D8; Thu, 20 May 2004 11:47:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQpAN-0005NA-Gm
	for pim@optimus.ietf.org; Thu, 20 May 2004 11:09:04 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA22236
	for <pim@ietf.org>; Thu, 20 May 2004 11:08:59 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BQpAK-0007aF-S5
	for pim@ietf.org; Thu, 20 May 2004 11:09:00 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQp95-0007Ky-00
	for pim@ietf.org; Thu, 20 May 2004 11:07:45 -0400
Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQp85-0006v5-00
	for pim@ietf.org; Thu, 20 May 2004 11:06:41 -0400
Received: from sj-core-2.cisco.com (171.71.177.254)
  by sj-iport-3.cisco.com with ESMTP; 20 May 2004 07:13:49 +0000
Received: from cypher.cisco.com (cypher.cisco.com [171.69.11.143])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id i4KF678R006849;
	Thu, 20 May 2004 08:06:08 -0700 (PDT)
Received: (from eckert@localhost)
	by cypher.cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) id IAA17173;
	Thu, 20 May 2004 08:06:07 -0700 (PDT)
Date: Thu, 20 May 2004 08:06:06 -0700
From: Toerless Eckert <eckert@cisco.com>
To: Pekka Savola <pekkas@netcore.fi>
Cc: Mike McBride <mmcbride@cisco.com>, pim@ietf.org
Subject: Re: [pim] WG Last Call - draft-ietf-pim-bidir-06
Message-ID: <20040520150606.GK305@cisco.com>
References: <Pine.GSO.4.58.0404281220260.8177@irp-view6.cisco.com> <Pine.LNX.4.44.0405201000220.649-100000@netcore.fi>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.LNX.4.44.0405201000220.649-100000@netcore.fi>
User-Agent: Mutt/1.4i
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: pim-admin@ietf.org
Errors-To: pim-admin@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Id: Protocol Independent Multicast <pim.ietf.org>
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>

On Thu, May 20, 2004 at 10:41:35AM +0300, Pekka Savola wrote:
> Sorry for missing the LC DL a bit. A couple of observations.

There must be a hibernation virus going around... ;-))

> Major comment fundamental comment:
> ----------------------------------
> 
> I fail to see the high-level justification for this approach, perhaps
> a more extensive "Protocol Overview" would be called for if I've
> misunderstood something.
> 
> Basically, I don't see what it is that requires 45 pages of
> specification and new mechanisms which weren't available in PIM-SM!  

Protocol architecture and motivation drafts are also what i am always
asking for, but there doesn't seem to be too much of an interest in the
IETF to write them. Likely they can also be controversial and they
are probably also not easy to write.

I don't think it is fair to bring up this point against the Bidir-PIM
draft, because i think none of the multicast protocols so far has had
any such companion documents or larger parts of the protocol spec
reserved for such motivational talk. If you want to contribute to the
process, i would propose you pick up the PIM architecture draft,
that ran from 1994 to i think 1998 and was then silently killed because
everybody who worked on it got bored (i guess). I only have a version
from 1999 lying around, but i think i once tracked it up to 1998 on some
ftp servers on the internet.
 (ftp://ftpeng.cisco.com/ipmulticast/drafts/pimv1-arch.txt)

(And being so critical against the multicast protocols not providing
 good motivational architecture drafts, i have to also mention that other 
 groups in the IETF are not much better, they just sometimes make money by
 writing books about the background of their protocols *hint* *hint* ;-))

> The fundamental function of bidir-PIM appears to be:
>  
>    Forwarding packets from the adjacent links without 
>    register-encapsulation towards the RP, for groups supported by 
>    bidir-PIM.

Not really, it's more like the "establish and fast-converge of
loop-free rp-rooted bidirectional spanning trees within a network" function.

> But the spec also includes e.g. DF election procedures (11 pages).

WHich is kinda the core of Bidir-PIM, ensuring the fast and loop-free
creation of the crucial upstream forwarding part of the tree.

> AFAICS, what you could do is just specify that:
>   a) DF is automatically elected the same way as DR, but just among 
>      those DRs which are bidir-capable.  Code reuse and 
>      simplification.  Why should different DF's be used for different
>      groups?  This way it works for embedded-RP as well.

A bidirectional spanning tree for a group has to be rooted in the RP.
See also SPT protocols at L2 ;-). That's why DF election has to be per DF.

>   b) if the group has been configured as bidir, instead of  
>      encapsulating, just send it over towards the RP.

"over towards RP" - please explain.

>   c) if the group has been configured as bidir, the routers along the 
>      path are expected to be bidir-capable.  The only change they need 
>      is to (if I'm not mistaken) is to add the RP address for all 
>      groups G to their olist, i.e., pass the data packets towards the 
>      RP if they come from the right direction. 

Yeah, well if it was just that simple.  The problem is really in
differentiation upstream vs. downstream traffic to avoid loops if you try
to avoid DF election.

We've been circling around lots of options to simplify the design and
get away from DF election - so as to be able to easier support
embedded-RP with Bidir-PIM, but the problem is that to avoid possible
loops you then have to well know whether you're sending upstream or
downstream. There are a couple of options on how to do this, one
was Dino's original UMP option in the IP header (set only for upstream,
then cleared), which is not too cool as long as there are still vendors
with ASIC driven HW forwarding (sigh), and the other option is to
differentiate based on L2 information, eg: upstream forwarding uses
for example unicast encap and downstream forwarding multicast, but this
falls flat when you have an L2 that doesn't have unicast/multicast
differentiation - like POS (you don't know whether the packet is up or
downstream). Not to speak of ASIC HW forwarding that wouldn't know
L2 encap anymore when it's doing L3 lookup.

>   d) if you'd send a packet to a router using bidir mechanisms but it 
>      doesn't advertise to be bidir-capable with hellos, log an error.

Data-triggered-event ? That's about the time when the Bidir-Philosophy
Enforcement team (in the person of Isidor) would come to claim your head.

Yes, if we introduce some form of data triggered events we can also have
some other workaround for the problem.

>    15 pages of very simple spec, and this would also work for embedded 
>    RP.
> 
> Could someone please enlighten me what is the justification behind the 
> current design?  I see that killing data encap/decap is important, but 
> I fail to see the need for this way too complex approach.
> 
> I guess the reason here is "no data driven events", but I can't see
> how this applies, as DF election is also a data-driven event
> (something must trigger the election to happen for a specific group --
> for example if there is no group-specific state and the first thing to
> a new group is a sender-only branch).

Yes, well, that's why they call DF-election packets like all other
PIM link-layer packets "control-plane-packets" - so it's not a data-triggered
event.

Bidir-PIM works fine as it is defined for domains where you can have
consistent RP mapping and it does fill in its current form an important
role in providing scalability for multi-source enterprise ASM applications.
Expanding bidirectional (*,G) only trees beyond this is definitely an
entertaining engineering topic, but it would not invalidate the current
Bidir-PIM design because even if we may be able to get rid of DF election,
we will be creating some other form of complexity/downside. So right
now Bidir-PIM is understood to be only applicable to a single coordinated
administrative domain or group of domains.

In addition to protocol complexity, it is completely questionable how much
more than engineering curiosity will be satisfied with for example a better
Internet-wide ASM model through whatever Bidir-PIMv2 we might want to design:

As i think i said more than once: Who the heck would want to use ASM service
across an Internet where 5 million users can blast traffic into your group ?
Yes, in something like 6NET or even I2 or other IPv4 multicast deployments
you might be able to safely use ASM, but also only because not every single
PC of every single consumer is connected to it.

As long as (partially interdomain) networks stay this way, ASM has value,
but for such networks you could also still pretty well administer
coordination for existing Bidir-PIM domains if there was a strong enough
need for it.


So, in summary:
  - Bidir-PIMv1 fills a need in enterprises, it works, it should go forward.
  - Bidir-PIM for larger scopes is an interesting engineering exercise,
    but it has not yet proven to be in strong demand, and it is unclear
    what largest scope it would make sense for anyhow before the
    security issues of the ASM service model would become overwhelming.
    Likely the range of scopes for such a larger scope Bidir will be limited.

I'll let the details questions below be answered from someone
from the spec writers team.

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


From exim@www1.ietf.org  Thu May 20 12:41:17 2004
Received: from optimus.ietf.org (www.iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA00410
	for <pim-archive@odin.ietf.org>; Thu, 20 May 2004 12:41:17 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQqTA-0000Ow-4x
	for pim-archive@odin.ietf.org; Thu, 20 May 2004 12:32:32 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4KGWWrn001538
	for pim-archive@odin.ietf.org; Thu, 20 May 2004 12:32:32 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQq2N-0007Hn-P7
	for pim-web-archive@optimus.ietf.org; Thu, 20 May 2004 12:04:51 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA27779
	for <pim-web-archive@ietf.org>; Thu, 20 May 2004 12:04:48 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BQq2M-0001DA-JK
	for pim-web-archive@ietf.org; Thu, 20 May 2004 12:04:50 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQq1Z-00018z-00
	for pim-web-archive@ietf.org; Thu, 20 May 2004 12:04:02 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQq0r-00012r-00
	for pim-web-archive@ietf.org; Thu, 20 May 2004 12:03:17 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQpl8-0001FF-D8; Thu, 20 May 2004 11:47:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQpAN-0005NA-Gm
	for pim@optimus.ietf.org; Thu, 20 May 2004 11:09:04 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA22236
	for <pim@ietf.org>; Thu, 20 May 2004 11:08:59 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BQpAK-0007aF-S5
	for pim@ietf.org; Thu, 20 May 2004 11:09:00 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQp95-0007Ky-00
	for pim@ietf.org; Thu, 20 May 2004 11:07:45 -0400
Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQp85-0006v5-00
	for pim@ietf.org; Thu, 20 May 2004 11:06:41 -0400
Received: from sj-core-2.cisco.com (171.71.177.254)
  by sj-iport-3.cisco.com with ESMTP; 20 May 2004 07:13:49 +0000
Received: from cypher.cisco.com (cypher.cisco.com [171.69.11.143])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id i4KF678R006849;
	Thu, 20 May 2004 08:06:08 -0700 (PDT)
Received: (from eckert@localhost)
	by cypher.cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) id IAA17173;
	Thu, 20 May 2004 08:06:07 -0700 (PDT)
Date: Thu, 20 May 2004 08:06:06 -0700
From: Toerless Eckert <eckert@cisco.com>
To: Pekka Savola <pekkas@netcore.fi>
Cc: Mike McBride <mmcbride@cisco.com>, pim@ietf.org
Subject: Re: [pim] WG Last Call - draft-ietf-pim-bidir-06
Message-ID: <20040520150606.GK305@cisco.com>
References: <Pine.GSO.4.58.0404281220260.8177@irp-view6.cisco.com> <Pine.LNX.4.44.0405201000220.649-100000@netcore.fi>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.LNX.4.44.0405201000220.649-100000@netcore.fi>
User-Agent: Mutt/1.4i
Sender: pim-admin@ietf.org
Errors-To: pim-admin@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Id: Protocol Independent Multicast <pim.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60

On Thu, May 20, 2004 at 10:41:35AM +0300, Pekka Savola wrote:
> Sorry for missing the LC DL a bit. A couple of observations.

There must be a hibernation virus going around... ;-))

> Major comment fundamental comment:
> ----------------------------------
> 
> I fail to see the high-level justification for this approach, perhaps
> a more extensive "Protocol Overview" would be called for if I've
> misunderstood something.
> 
> Basically, I don't see what it is that requires 45 pages of
> specification and new mechanisms which weren't available in PIM-SM!  

Protocol architecture and motivation drafts are also what i am always
asking for, but there doesn't seem to be too much of an interest in the
IETF to write them. Likely they can also be controversial and they
are probably also not easy to write.

I don't think it is fair to bring up this point against the Bidir-PIM
draft, because i think none of the multicast protocols so far has had
any such companion documents or larger parts of the protocol spec
reserved for such motivational talk. If you want to contribute to the
process, i would propose you pick up the PIM architecture draft,
that ran from 1994 to i think 1998 and was then silently killed because
everybody who worked on it got bored (i guess). I only have a version
from 1999 lying around, but i think i once tracked it up to 1998 on some
ftp servers on the internet.
 (ftp://ftpeng.cisco.com/ipmulticast/drafts/pimv1-arch.txt)

(And being so critical against the multicast protocols not providing
 good motivational architecture drafts, i have to also mention that other 
 groups in the IETF are not much better, they just sometimes make money by
 writing books about the background of their protocols *hint* *hint* ;-))

> The fundamental function of bidir-PIM appears to be:
>  
>    Forwarding packets from the adjacent links without 
>    register-encapsulation towards the RP, for groups supported by 
>    bidir-PIM.

Not really, it's more like the "establish and fast-converge of
loop-free rp-rooted bidirectional spanning trees within a network" function.

> But the spec also includes e.g. DF election procedures (11 pages).

WHich is kinda the core of Bidir-PIM, ensuring the fast and loop-free
creation of the crucial upstream forwarding part of the tree.

> AFAICS, what you could do is just specify that:
>   a) DF is automatically elected the same way as DR, but just among 
>      those DRs which are bidir-capable.  Code reuse and 
>      simplification.  Why should different DF's be used for different
>      groups?  This way it works for embedded-RP as well.

A bidirectional spanning tree for a group has to be rooted in the RP.
See also SPT protocols at L2 ;-). That's why DF election has to be per DF.

>   b) if the group has been configured as bidir, instead of  
>      encapsulating, just send it over towards the RP.

"over towards RP" - please explain.

>   c) if the group has been configured as bidir, the routers along the 
>      path are expected to be bidir-capable.  The only change they need 
>      is to (if I'm not mistaken) is to add the RP address for all 
>      groups G to their olist, i.e., pass the data packets towards the 
>      RP if they come from the right direction. 

Yeah, well if it was just that simple.  The problem is really in
differentiation upstream vs. downstream traffic to avoid loops if you try
to avoid DF election.

We've been circling around lots of options to simplify the design and
get away from DF election - so as to be able to easier support
embedded-RP with Bidir-PIM, but the problem is that to avoid possible
loops you then have to well know whether you're sending upstream or
downstream. There are a couple of options on how to do this, one
was Dino's original UMP option in the IP header (set only for upstream,
then cleared), which is not too cool as long as there are still vendors
with ASIC driven HW forwarding (sigh), and the other option is to
differentiate based on L2 information, eg: upstream forwarding uses
for example unicast encap and downstream forwarding multicast, but this
falls flat when you have an L2 that doesn't have unicast/multicast
differentiation - like POS (you don't know whether the packet is up or
downstream). Not to speak of ASIC HW forwarding that wouldn't know
L2 encap anymore when it's doing L3 lookup.

>   d) if you'd send a packet to a router using bidir mechanisms but it 
>      doesn't advertise to be bidir-capable with hellos, log an error.

Data-triggered-event ? That's about the time when the Bidir-Philosophy
Enforcement team (in the person of Isidor) would come to claim your head.

Yes, if we introduce some form of data triggered events we can also have
some other workaround for the problem.

>    15 pages of very simple spec, and this would also work for embedded 
>    RP.
> 
> Could someone please enlighten me what is the justification behind the 
> current design?  I see that killing data encap/decap is important, but 
> I fail to see the need for this way too complex approach.
> 
> I guess the reason here is "no data driven events", but I can't see
> how this applies, as DF election is also a data-driven event
> (something must trigger the election to happen for a specific group --
> for example if there is no group-specific state and the first thing to
> a new group is a sender-only branch).

Yes, well, that's why they call DF-election packets like all other
PIM link-layer packets "control-plane-packets" - so it's not a data-triggered
event.

Bidir-PIM works fine as it is defined for domains where you can have
consistent RP mapping and it does fill in its current form an important
role in providing scalability for multi-source enterprise ASM applications.
Expanding bidirectional (*,G) only trees beyond this is definitely an
entertaining engineering topic, but it would not invalidate the current
Bidir-PIM design because even if we may be able to get rid of DF election,
we will be creating some other form of complexity/downside. So right
now Bidir-PIM is understood to be only applicable to a single coordinated
administrative domain or group of domains.

In addition to protocol complexity, it is completely questionable how much
more than engineering curiosity will be satisfied with for example a better
Internet-wide ASM model through whatever Bidir-PIMv2 we might want to design:

As i think i said more than once: Who the heck would want to use ASM service
across an Internet where 5 million users can blast traffic into your group ?
Yes, in something like 6NET or even I2 or other IPv4 multicast deployments
you might be able to safely use ASM, but also only because not every single
PC of every single consumer is connected to it.

As long as (partially interdomain) networks stay this way, ASM has value,
but for such networks you could also still pretty well administer
coordination for existing Bidir-PIM domains if there was a strong enough
need for it.


So, in summary:
  - Bidir-PIMv1 fills a need in enterprises, it works, it should go forward.
  - Bidir-PIM for larger scopes is an interesting engineering exercise,
    but it has not yet proven to be in strong demand, and it is unclear
    what largest scope it would make sense for anyhow before the
    security issues of the ASM service model would become overwhelming.
    Likely the range of scopes for such a larger scope Bidir will be limited.

I'll let the details questions below be answered from someone
from the spec writers team.

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



From pim-admin@ietf.org  Fri May 21 20:14:52 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA14681
	for <pim-archive@lists.ietf.org>; Fri, 21 May 2004 20:14:52 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRJwj-0002fm-Qm; Fri, 21 May 2004 20:01:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRJs3-0001JH-RB
	for pim@optimus.ietf.org; Fri, 21 May 2004 19:56:11 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA13939
	for <pim@ietf.org>; Fri, 21 May 2004 19:56:09 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BRJs1-0004vr-Pu
	for pim@ietf.org; Fri, 21 May 2004 19:56:09 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRJrL-0004ow-00
	for pim@ietf.org; Fri, 21 May 2004 19:55:28 -0400
Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRJqJ-0004cA-00
	for pim@ietf.org; Fri, 21 May 2004 19:54:23 -0400
Received: from sj-core-2.cisco.com (171.71.177.254)
  by sj-iport-3.cisco.com with ESMTP; 21 May 2004 16:01:48 +0000
Received: from cypher.cisco.com (cypher.cisco.com [171.69.11.143])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id i4LNrp8R010475;
	Fri, 21 May 2004 16:53:51 -0700 (PDT)
Received: from localhost (kouvelas@localhost)
	by cypher.cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) with ESMTP id QAA21477;
	Fri, 21 May 2004 16:53:50 -0700 (PDT)
Message-Id: <200405212353.QAA21477@cypher.cisco.com>
To: Pekka Savola <pekkas@netcore.fi>
cc: Mike McBride <mmcbride@cisco.com>, pim@ietf.org, lorenzo@cypher.cisco.com
Subject: Re: [pim] WG Last Call - draft-ietf-pim-bidir-06 
In-reply-to: Your message of "Thu, 20 May 2004 10:41:35 +0300."
             <Pine.LNX.4.44.0405201000220.649-100000@netcore.fi> 
Date: Fri, 21 May 2004 16:53:50 -0700
From: Isidor Kouvelas <kouvelas@cisco.com>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: pim-admin@ietf.org
Errors-To: pim-admin@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Id: Protocol Independent Multicast <pim.ietf.org>
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>


Pekka Savola writes:

I have skipped the "Major comment" to which I think Toerless gave a
good response.

>More minor comments:
>--------------------
>
>Bidir PIM introduces the Bidir_Capable PIM-Hello option that MUST be
>included in all Hello messages from a Bidir-PIM capable router.  The
>Bidir_Capable option advertises the router's ability to participate in
>the Bidir-PIM protocol. The format of the Bidir_Capable option is
>described in section 3.7.
>
>==> HELLO?!?!!?!?  Do you mean that every router in a domain that is
>bidir-capable starts logging errors about every neighbor they have
>which is not bidir-capable?!??  Say goodbye to incremental deployment 
>and adding bidir capability on by default!

HIIIII!!!!! HOW ARE YOU?!?!?!?!?!
First of all there is no incremental deployment for BIDIR-PIM.  Mixing
BIDIR capable and legacy routers in a domain is a mis-config which the
option helps detect. Obviously if on a BIDIR capable router you have
BIDIR PIM disabled then you will not see such a message because you
have a non capable neighbour.
Now it is true that the option itself dates back to Dino's draft that
did specify incremental deployment. The main reason we cannot remove it
now is to keep existing code happy.

>The warning is should probably something that should be activated if a 
>group has been configured as bidir, but your neighbor isn't, or if you 
>try to use bidir forwarding algorithm towards the neighbor, and it 
>isn't bidir-capable.

There is currently no way of knowing what the group to RP / protocol
mapping is on a neighbouring PIM router. The assumption is that if the
neighbour is BIDIR capable then it has made the same interpretation of
the config / BSR advertisement.

>BIDIR-PIM messages are multicast with TTL 1 to the `ALL-PIM-ROUTERS'
>group `224.0.0.13'.
>
>==> IPv6 support, anyone?

Someone. Some of the v6 mods went into the current PIM-SM spec after I
pulled a lot of the text for Bidir. I guess we have missed some stuff
that changed since. We will go through PIM-SM to see what applies.

>...
>==> what is the BIDIR interdomain strategy?  There's no need for such, 
>I think, because it'll "just work the same way as PIM-SM" if you use 
>MSDP, but it would not hurt to spell it out.

It does not "just work". We scoped the mods at one point in time to
see what would be required. There are significant changes to make
source-only branches traverse a BIDIR domain.

>==> It would be worth stating (because it's not obvious) that the BSR 
>discovery works by the RP setting the bidir-capable bit in the 
>Encoded-Group Address (this isn't yet reflected in the bsr spec).

It was in the BIDIR spec but I pulled it out and handed the text over
to the BSR authors for inclusion in the next version of that spec.

>5.3.  Authentication Using IPsec
>
>The IPsec [5] transport mode using the Authentication Header (AH) is 
>the RECOMMENDED method to prevent the above attacks against BIDIR-PIM.
>
>It is RECOMMENDED that IPsec authentication be applied to all 
>BIDIR-PIM protocol messages.
>
>==> this is totally bogus recommendation, and luckily enough the 
>PIM-SM spec uses only MAY.  This would require manual key config on 
>the routers per interfaces, and is completely unrealistic.

I am sorry that this is so "totally bogus". I think this text was
again lifted from PIM-SM. We will update to match the current version.

Isidor


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


From exim@www1.ietf.org  Fri May 21 20:22:29 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA15307
	for <pim-archive@odin.ietf.org>; Fri, 21 May 2004 20:22:29 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRKFv-0007Q5-7J
	for pim-archive@odin.ietf.org; Fri, 21 May 2004 20:20:51 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4M0KpVs028517
	for pim-archive@odin.ietf.org; Fri, 21 May 2004 20:20:51 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRKBM-0006K0-LR
	for pim-web-archive@optimus.ietf.org; Fri, 21 May 2004 20:16:08 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA14813
	for <pim-web-archive@ietf.org>; Fri, 21 May 2004 20:16:06 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BRKBK-0006uc-Fq
	for pim-web-archive@ietf.org; Fri, 21 May 2004 20:16:06 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRKAR-0006mi-00
	for pim-web-archive@ietf.org; Fri, 21 May 2004 20:15:12 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRK9f-0006f8-00
	for pim-web-archive@ietf.org; Fri, 21 May 2004 20:14:23 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRJwj-0002fm-Qm; Fri, 21 May 2004 20:01:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRJs3-0001JH-RB
	for pim@optimus.ietf.org; Fri, 21 May 2004 19:56:11 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA13939
	for <pim@ietf.org>; Fri, 21 May 2004 19:56:09 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BRJs1-0004vr-Pu
	for pim@ietf.org; Fri, 21 May 2004 19:56:09 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRJrL-0004ow-00
	for pim@ietf.org; Fri, 21 May 2004 19:55:28 -0400
Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRJqJ-0004cA-00
	for pim@ietf.org; Fri, 21 May 2004 19:54:23 -0400
Received: from sj-core-2.cisco.com (171.71.177.254)
  by sj-iport-3.cisco.com with ESMTP; 21 May 2004 16:01:48 +0000
Received: from cypher.cisco.com (cypher.cisco.com [171.69.11.143])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id i4LNrp8R010475;
	Fri, 21 May 2004 16:53:51 -0700 (PDT)
Received: from localhost (kouvelas@localhost)
	by cypher.cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) with ESMTP id QAA21477;
	Fri, 21 May 2004 16:53:50 -0700 (PDT)
Message-Id: <200405212353.QAA21477@cypher.cisco.com>
To: Pekka Savola <pekkas@netcore.fi>
cc: Mike McBride <mmcbride@cisco.com>, pim@ietf.org, lorenzo@cypher.cisco.com
Subject: Re: [pim] WG Last Call - draft-ietf-pim-bidir-06 
In-reply-to: Your message of "Thu, 20 May 2004 10:41:35 +0300."
             <Pine.LNX.4.44.0405201000220.649-100000@netcore.fi> 
Date: Fri, 21 May 2004 16:53:50 -0700
From: Isidor Kouvelas <kouvelas@cisco.com>
Sender: pim-admin@ietf.org
Errors-To: pim-admin@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Id: Protocol Independent Multicast <pim.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60


Pekka Savola writes:

I have skipped the "Major comment" to which I think Toerless gave a
good response.

>More minor comments:
>--------------------
>
>Bidir PIM introduces the Bidir_Capable PIM-Hello option that MUST be
>included in all Hello messages from a Bidir-PIM capable router.  The
>Bidir_Capable option advertises the router's ability to participate in
>the Bidir-PIM protocol. The format of the Bidir_Capable option is
>described in section 3.7.
>
>==> HELLO?!?!!?!?  Do you mean that every router in a domain that is
>bidir-capable starts logging errors about every neighbor they have
>which is not bidir-capable?!??  Say goodbye to incremental deployment 
>and adding bidir capability on by default!

HIIIII!!!!! HOW ARE YOU?!?!?!?!?!
First of all there is no incremental deployment for BIDIR-PIM.  Mixing
BIDIR capable and legacy routers in a domain is a mis-config which the
option helps detect. Obviously if on a BIDIR capable router you have
BIDIR PIM disabled then you will not see such a message because you
have a non capable neighbour.
Now it is true that the option itself dates back to Dino's draft that
did specify incremental deployment. The main reason we cannot remove it
now is to keep existing code happy.

>The warning is should probably something that should be activated if a 
>group has been configured as bidir, but your neighbor isn't, or if you 
>try to use bidir forwarding algorithm towards the neighbor, and it 
>isn't bidir-capable.

There is currently no way of knowing what the group to RP / protocol
mapping is on a neighbouring PIM router. The assumption is that if the
neighbour is BIDIR capable then it has made the same interpretation of
the config / BSR advertisement.

>BIDIR-PIM messages are multicast with TTL 1 to the `ALL-PIM-ROUTERS'
>group `224.0.0.13'.
>
>==> IPv6 support, anyone?

Someone. Some of the v6 mods went into the current PIM-SM spec after I
pulled a lot of the text for Bidir. I guess we have missed some stuff
that changed since. We will go through PIM-SM to see what applies.

>...
>==> what is the BIDIR interdomain strategy?  There's no need for such, 
>I think, because it'll "just work the same way as PIM-SM" if you use 
>MSDP, but it would not hurt to spell it out.

It does not "just work". We scoped the mods at one point in time to
see what would be required. There are significant changes to make
source-only branches traverse a BIDIR domain.

>==> It would be worth stating (because it's not obvious) that the BSR 
>discovery works by the RP setting the bidir-capable bit in the 
>Encoded-Group Address (this isn't yet reflected in the bsr spec).

It was in the BIDIR spec but I pulled it out and handed the text over
to the BSR authors for inclusion in the next version of that spec.

>5.3.  Authentication Using IPsec
>
>The IPsec [5] transport mode using the Authentication Header (AH) is 
>the RECOMMENDED method to prevent the above attacks against BIDIR-PIM.
>
>It is RECOMMENDED that IPsec authentication be applied to all 
>BIDIR-PIM protocol messages.
>
>==> this is totally bogus recommendation, and luckily enough the 
>PIM-SM spec uses only MAY.  This would require manual key config on 
>the routers per interfaces, and is completely unrealistic.

I am sorry that this is so "totally bogus". I think this text was
again lifted from PIM-SM. We will update to match the current version.

Isidor


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



From pim-admin@ietf.org  Sat May 22 00:14:31 2004
Received: from optimus.ietf.org (www.iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA25171
	for <pim-archive@lists.ietf.org>; Sat, 22 May 2004 00:14:31 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRNfK-00074n-HX; Fri, 21 May 2004 23:59:18 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRNaB-0005eO-Fw
	for pim@optimus.ietf.org; Fri, 21 May 2004 23:53:59 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA24328
	for <pim@ietf.org>; Fri, 21 May 2004 23:53:55 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BRNa8-0006nl-Kf
	for pim@ietf.org; Fri, 21 May 2004 23:53:56 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRNZA-0006gn-00
	for pim@ietf.org; Fri, 21 May 2004 23:53:00 -0400
Received: from netcore.fi ([193.94.160.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRNYE-0006V6-00
	for pim@ietf.org; Fri, 21 May 2004 23:51:58 -0400
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id i4M3pH510867;
	Sat, 22 May 2004 06:51:17 +0300
Date: Sat, 22 May 2004 06:51:17 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: Isidor Kouvelas <kouvelas@cisco.com>
cc: Mike McBride <mmcbride@cisco.com>, <pim@ietf.org>,
        <lorenzo@cypher.cisco.com>
Subject: Re: [pim] WG Last Call - draft-ietf-pim-bidir-06 
In-Reply-To: <200405212353.QAA21477@cypher.cisco.com>
Message-ID: <Pine.LNX.4.44.0405220644420.10805-100000@netcore.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: pim-admin@ietf.org
Errors-To: pim-admin@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Id: Protocol Independent Multicast <pim.ietf.org>
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>

Sorry if I sounded a bit aggressive in my comments .. :)

On Fri, 21 May 2004, Isidor Kouvelas wrote:
> >More minor comments:
> >--------------------
> >
> >Bidir PIM introduces the Bidir_Capable PIM-Hello option that MUST be
> >included in all Hello messages from a Bidir-PIM capable router.  The
> >Bidir_Capable option advertises the router's ability to participate in
> >the Bidir-PIM protocol. The format of the Bidir_Capable option is
> >described in section 3.7.
> >
> >==> HELLO?!?!!?!?  Do you mean that every router in a domain that is
> >bidir-capable starts logging errors about every neighbor they have
> >which is not bidir-capable?!??  Say goodbye to incremental deployment 
> >and adding bidir capability on by default!
> 
> HIIIII!!!!! HOW ARE YOU?!?!?!?!?!
> First of all there is no incremental deployment for BIDIR-PIM.  Mixing
> BIDIR capable and legacy routers in a domain is a mis-config which the
> option helps detect. Obviously if on a BIDIR capable router you have
> BIDIR PIM disabled then you will not see such a message because you
> have a non capable neighbour.
> Now it is true that the option itself dates back to Dino's draft that
> did specify incremental deployment. The main reason we cannot remove it
> now is to keep existing code happy.

Sorry, what I meant is incremental _router software_ deployment.

In a network of 100 multicast routers, this implies either that:
 a) bidir-pim must always be disabled by default, or
 b) all the routers must be upgraded simultaneously.

If I'm not misunderstanding something, bidir-pim could be enabled by 
default (but not active until a group advertisement with bidir flag is 
sent) by a slightly different strategy .. see below.

> >The warning is should probably something that should be activated if a 
> >group has been configured as bidir, but your neighbor isn't, or if you 
> >try to use bidir forwarding algorithm towards the neighbor, and it 
> >isn't bidir-capable.
> 
> There is currently no way of knowing what the group to RP / protocol
> mapping is on a neighbouring PIM router. The assumption is that if the
> neighbour is BIDIR capable then it has made the same interpretation of
> the config / BSR advertisement.

I fail to see why this is relevant. The routers could stay "dormant", 
advertising bidir-pim capabilities but not using bidir-pim for 
anything until such time that config/BSR advertisement decrees that 
bidir-pim is to be used for a group, right?  Or is there something I'm 
missing?

When you get that BSR advertisement, only *then* you should start 
complaining if your neighbors aren't bidir-PIM -capable.
 
> >...
> >==> what is the BIDIR interdomain strategy?  There's no need for such, 
> >I think, because it'll "just work the same way as PIM-SM" if you use 
> >MSDP, but it would not hurt to spell it out.
> 
> It does not "just work". We scoped the mods at one point in time to
> see what would be required. There are significant changes to make
> source-only branches traverse a BIDIR domain.

So it should be spelled out I think..
 
-- 
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 exim@www1.ietf.org  Sat May 22 00:24:30 2004
Received: from optimus.ietf.org (www.iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA25689
	for <pim-archive@odin.ietf.org>; Sat, 22 May 2004 00:24:30 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRO0x-0003ES-I5
	for pim-archive@odin.ietf.org; Sat, 22 May 2004 00:21:40 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4M4Ld2O012421
	for pim-archive@odin.ietf.org; Sat, 22 May 2004 00:21:39 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRNvh-00020s-P1
	for pim-web-archive@optimus.ietf.org; Sat, 22 May 2004 00:16:13 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA25216
	for <pim-web-archive@ietf.org>; Sat, 22 May 2004 00:16:09 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BRNve-0001fw-Tf
	for pim-web-archive@ietf.org; Sat, 22 May 2004 00:16:10 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRNuf-0001YW-00
	for pim-web-archive@ietf.org; Sat, 22 May 2004 00:15:11 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRNtb-0001R8-00
	for pim-web-archive@ietf.org; Sat, 22 May 2004 00:14:03 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRNfK-00074n-HX; Fri, 21 May 2004 23:59:18 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRNaB-0005eO-Fw
	for pim@optimus.ietf.org; Fri, 21 May 2004 23:53:59 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA24328
	for <pim@ietf.org>; Fri, 21 May 2004 23:53:55 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BRNa8-0006nl-Kf
	for pim@ietf.org; Fri, 21 May 2004 23:53:56 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRNZA-0006gn-00
	for pim@ietf.org; Fri, 21 May 2004 23:53:00 -0400
Received: from netcore.fi ([193.94.160.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRNYE-0006V6-00
	for pim@ietf.org; Fri, 21 May 2004 23:51:58 -0400
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id i4M3pH510867;
	Sat, 22 May 2004 06:51:17 +0300
Date: Sat, 22 May 2004 06:51:17 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: Isidor Kouvelas <kouvelas@cisco.com>
cc: Mike McBride <mmcbride@cisco.com>, <pim@ietf.org>,
        <lorenzo@cypher.cisco.com>
Subject: Re: [pim] WG Last Call - draft-ietf-pim-bidir-06 
In-Reply-To: <200405212353.QAA21477@cypher.cisco.com>
Message-ID: <Pine.LNX.4.44.0405220644420.10805-100000@netcore.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: pim-admin@ietf.org
Errors-To: pim-admin@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Id: Protocol Independent Multicast <pim.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60

Sorry if I sounded a bit aggressive in my comments .. :)

On Fri, 21 May 2004, Isidor Kouvelas wrote:
> >More minor comments:
> >--------------------
> >
> >Bidir PIM introduces the Bidir_Capable PIM-Hello option that MUST be
> >included in all Hello messages from a Bidir-PIM capable router.  The
> >Bidir_Capable option advertises the router's ability to participate in
> >the Bidir-PIM protocol. The format of the Bidir_Capable option is
> >described in section 3.7.
> >
> >==> HELLO?!?!!?!?  Do you mean that every router in a domain that is
> >bidir-capable starts logging errors about every neighbor they have
> >which is not bidir-capable?!??  Say goodbye to incremental deployment 
> >and adding bidir capability on by default!
> 
> HIIIII!!!!! HOW ARE YOU?!?!?!?!?!
> First of all there is no incremental deployment for BIDIR-PIM.  Mixing
> BIDIR capable and legacy routers in a domain is a mis-config which the
> option helps detect. Obviously if on a BIDIR capable router you have
> BIDIR PIM disabled then you will not see such a message because you
> have a non capable neighbour.
> Now it is true that the option itself dates back to Dino's draft that
> did specify incremental deployment. The main reason we cannot remove it
> now is to keep existing code happy.

Sorry, what I meant is incremental _router software_ deployment.

In a network of 100 multicast routers, this implies either that:
 a) bidir-pim must always be disabled by default, or
 b) all the routers must be upgraded simultaneously.

If I'm not misunderstanding something, bidir-pim could be enabled by 
default (but not active until a group advertisement with bidir flag is 
sent) by a slightly different strategy .. see below.

> >The warning is should probably something that should be activated if a 
> >group has been configured as bidir, but your neighbor isn't, or if you 
> >try to use bidir forwarding algorithm towards the neighbor, and it 
> >isn't bidir-capable.
> 
> There is currently no way of knowing what the group to RP / protocol
> mapping is on a neighbouring PIM router. The assumption is that if the
> neighbour is BIDIR capable then it has made the same interpretation of
> the config / BSR advertisement.

I fail to see why this is relevant. The routers could stay "dormant", 
advertising bidir-pim capabilities but not using bidir-pim for 
anything until such time that config/BSR advertisement decrees that 
bidir-pim is to be used for a group, right?  Or is there something I'm 
missing?

When you get that BSR advertisement, only *then* you should start 
complaining if your neighbors aren't bidir-PIM -capable.
 
> >...
> >==> what is the BIDIR interdomain strategy?  There's no need for such, 
> >I think, because it'll "just work the same way as PIM-SM" if you use 
> >MSDP, but it would not hurt to spell it out.
> 
> It does not "just work". We scoped the mods at one point in time to
> see what would be required. There are significant changes to make
> source-only branches traverse a BIDIR domain.

So it should be spelled out I think..
 
-- 
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-admin@ietf.org  Sat May 22 01:17:48 2004
Received: from optimus.ietf.org (www.iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA28361
	for <pim-archive@lists.ietf.org>; Sat, 22 May 2004 01:17:48 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BROjq-0003hD-80; Sat, 22 May 2004 01:08:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BROZN-0001k7-NN
	for pim@optimus.ietf.org; Sat, 22 May 2004 00:57:13 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA27747
	for <pim@ietf.org>; Sat, 22 May 2004 00:57:09 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BROZK-0007Gw-Uc
	for pim@ietf.org; Sat, 22 May 2004 00:57:11 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BROYH-000798-00
	for pim@ietf.org; Sat, 22 May 2004 00:56:06 -0400
Received: from netcore.fi ([193.94.160.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BROXb-0006xe-00
	for pim@ietf.org; Sat, 22 May 2004 00:55:23 -0400
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id i4M4sia11678;
	Sat, 22 May 2004 07:54:44 +0300
Date: Sat, 22 May 2004 07:54:44 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: Toerless Eckert <eckert@cisco.com>
cc: Mike McBride <mmcbride@cisco.com>, <pim@ietf.org>
Subject: Re: [pim] WG Last Call - draft-ietf-pim-bidir-06
In-Reply-To: <20040520150606.GK305@cisco.com>
Message-ID: <Pine.LNX.4.44.0405220652520.10805-100000@netcore.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: pim-admin@ietf.org
Errors-To: pim-admin@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Id: Protocol Independent Multicast <pim.ietf.org>
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>

On Thu, 20 May 2004, Toerless Eckert wrote:
> On Thu, May 20, 2004 at 10:41:35AM +0300, Pekka Savola wrote:
> > Major comment fundamental comment:
> > ----------------------------------
> > 
> > I fail to see the high-level justification for this approach, perhaps
> > a more extensive "Protocol Overview" would be called for if I've
> > misunderstood something.
> > 
> > Basically, I don't see what it is that requires 45 pages of
> > specification and new mechanisms which weren't available in PIM-SM!  
> 
> Protocol architecture and motivation drafts are also what i am always
> asking for, but there doesn't seem to be too much of an interest in the
> IETF to write them. Likely they can also be controversial and they
> are probably also not easy to write.

In most cases, some of this is included in the specifications 
themselves.  There's a short section even in PIM-SM spec, though not 
really a lengthy one.

> I don't think it is fair to bring up this point against the Bidir-PIM
> draft, because i think none of the multicast protocols so far has had
> any such companion documents or larger parts of the protocol spec
> reserved for such motivational talk. If you want to contribute to the
> process, i would propose you pick up the PIM architecture draft,
> that ran from 1994 to i think 1998 and was then silently killed because
> everybody who worked on it got bored (i guess). I only have a version
> from 1999 lying around, but i think i once tracked it up to 1998 on some
> ftp servers on the internet.
>  (ftp://ftpeng.cisco.com/ipmulticast/drafts/pimv1-arch.txt)

No such draft there.

What I'm looking for is the answer to questions like:
 - "what are the functions of the protocol?  what problems is it 
intended to solve and how it does that?"
 - "why this is the correct approach to solving these problems?"
 
> > The fundamental function of bidir-PIM appears to be:
> >  
> >    Forwarding packets from the adjacent links without 
> >    register-encapsulation towards the RP, for groups supported by 
> >    bidir-PIM.
> 
> Not really, it's more like the "establish and fast-converge of
> loop-free rp-rooted bidirectional spanning trees within a network" function.
> 
> > But the spec also includes e.g. DF election procedures (11 pages).
> 
> WHich is kinda the core of Bidir-PIM, ensuring the fast and loop-free
> creation of the crucial upstream forwarding part of the tree.

This is my main gripe, I think.

If you want to make PIM-SM DR election faster, why not improve DR 
election, instead of inventing a new protocol which does N+1 other 
things as well.

Couldn't all of these be achieved by modular PIM-SM enhancements
(killing the registers, faster convergence, adding IGP metrics, ...) ?
 
> > AFAICS, what you could do is just specify that:
> >   a) DF is automatically elected the same way as DR, but just among 
> >      those DRs which are bidir-capable.  Code reuse and 
> >      simplification.  Why should different DF's be used for different
> >      groups?  This way it works for embedded-RP as well.
> 
> A bidirectional spanning tree for a group has to be rooted in the RP.
> See also SPT protocols at L2 ;-). That's why DF election has to be per DF.

Perhaps you meant 'per group' not 'per DF'.

So, you have an implicit assumption that you have important scenarios 
where there are multiple multicast routers attached to receiver/sender 
LANs, and those different multicast routers serve different groups?

Is this really a relevant scenario? 
 
Even if so, note that actually you don't need DF election per group,
but per group-to-RP mapping, right?  With such a change, it would work
for embedded-RP as well I think.

> >   b) if the group has been configured as bidir, instead of  
> >      encapsulating, just send it over towards the RP.
> 
> "over towards RP" - please explain.

The bidir PIM data forwarding algorithm appears to be basically 'punt
the data out on the interface which is the best neighbor towards the
RP'.  There is no magic in this.  Could be done with PIM-SM if the
routers would just learn that it's safe to do so (i.e., that the
routers on the path all supported this data forwarding).

> >   c) if the group has been configured as bidir, the routers along the 
> >      path are expected to be bidir-capable.  The only change they need 
> >      is to (if I'm not mistaken) is to add the RP address for all 
> >      groups G to their olist, i.e., pass the data packets towards the 
> >      RP if they come from the right direction. 
> 
> Yeah, well if it was just that simple.  The problem is really in
> differentiation upstream vs. downstream traffic to avoid loops if you try
> to avoid DF election.
> 
> We've been circling around lots of options to simplify the design and
> get away from DF election - so as to be able to easier support
> embedded-RP with Bidir-PIM, but the problem is that to avoid possible
> loops you then have to well know whether you're sending upstream or
> downstream. There are a couple of options on how to do this, one
> was Dino's original UMP option in the IP header (set only for upstream,
> then cleared), which is not too cool as long as there are still vendors
> with ASIC driven HW forwarding (sigh), and the other option is to
> differentiate based on L2 information, eg: upstream forwarding uses
> for example unicast encap and downstream forwarding multicast, but this
> falls flat when you have an L2 that doesn't have unicast/multicast
> differentiation - like POS (you don't know whether the packet is up or
> downstream). Not to speak of ASIC HW forwarding that wouldn't know
> L2 encap anymore when it's doing L3 lookup.

This problem should have ended up in the spec :).

However, I don't quite understand why doing DF election avoids this
particular problem?

One clarification: when the packets go to the RP, and the RP sends
them back, are the packets stamped with RP's IP address, or the
original senders'?  I guess it's the original. (Otherwise, you could
use the RP addresses to distinguish up/downstreams.)

Isn't it sufficient to just check that if the packet came from iif
that points toward the RP, it's a downstream packet, and if it came
from somewhere else (provided that the direction is RPF-wise correct),
it's an upstream packet?

> >   d) if you'd send a packet to a router using bidir mechanisms but it 
> >      doesn't advertise to be bidir-capable with hellos, log an error.
> 
> Data-triggered-event ? That's about the time when the Bidir-Philosophy
> Enforcement team (in the person of Isidor) would come to claim your head.
> 
> Yes, if we introduce some form of data triggered events we can also have
> some other workaround for the problem.

OK, you can make this control-plane triggered event as well, by
checking that when a group w/ bidir appears in BSR or config, require
that all neighbors support bidir.
 
> >    15 pages of very simple spec, and this would also work for embedded 
> >    RP.
> > 
> > Could someone please enlighten me what is the justification behind the 
> > current design?  I see that killing data encap/decap is important, but 
> > I fail to see the need for this way too complex approach.
> > 
> > I guess the reason here is "no data driven events", but I can't see
> > how this applies, as DF election is also a data-driven event
> > (something must trigger the election to happen for a specific group --
> > for example if there is no group-specific state and the first thing to
> > a new group is a sender-only branch).
> 
> Yes, well, that's why they call DF-election packets like all other
> PIM link-layer packets "control-plane-packets" - so it's not a data-triggered
> event.

But that's not the point.  You'll have to have a data-driven even in
any case, I think.  How can you elect a DF for a group which you don't
know a host will be creating before the group has been created by
sending to it?  E.g., if you specify that 239.2.0.0/16 is bidir, and a
source-only host starts sending to 239.2.2.2, you don't know that
before the data has been sent, and you have to snoop the data to know
it -- making it a data-driven event!?
 
-- 
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 exim@www1.ietf.org  Sat May 22 01:25:14 2004
Received: from optimus.ietf.org (www.iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA28920
	for <pim-archive@odin.ietf.org>; Sat, 22 May 2004 01:25:13 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BROz5-0006ad-4G
	for pim-archive@odin.ietf.org; Sat, 22 May 2004 01:23:47 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4M5Nln2025326
	for pim-archive@odin.ietf.org; Sat, 22 May 2004 01:23:47 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BROub-0005qZ-67
	for pim-web-archive@optimus.ietf.org; Sat, 22 May 2004 01:19:09 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA28423
	for <pim-web-archive@ietf.org>; Sat, 22 May 2004 01:19:07 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BROuY-0001tO-7x
	for pim-web-archive@ietf.org; Sat, 22 May 2004 01:19:06 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BROtg-0001kS-00
	for pim-web-archive@ietf.org; Sat, 22 May 2004 01:18:13 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BROso-0001cx-00
	for pim-web-archive@ietf.org; Sat, 22 May 2004 01:17:18 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BROjq-0003hD-80; Sat, 22 May 2004 01:08:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BROZN-0001k7-NN
	for pim@optimus.ietf.org; Sat, 22 May 2004 00:57:13 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA27747
	for <pim@ietf.org>; Sat, 22 May 2004 00:57:09 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BROZK-0007Gw-Uc
	for pim@ietf.org; Sat, 22 May 2004 00:57:11 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BROYH-000798-00
	for pim@ietf.org; Sat, 22 May 2004 00:56:06 -0400
Received: from netcore.fi ([193.94.160.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BROXb-0006xe-00
	for pim@ietf.org; Sat, 22 May 2004 00:55:23 -0400
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id i4M4sia11678;
	Sat, 22 May 2004 07:54:44 +0300
Date: Sat, 22 May 2004 07:54:44 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: Toerless Eckert <eckert@cisco.com>
cc: Mike McBride <mmcbride@cisco.com>, <pim@ietf.org>
Subject: Re: [pim] WG Last Call - draft-ietf-pim-bidir-06
In-Reply-To: <20040520150606.GK305@cisco.com>
Message-ID: <Pine.LNX.4.44.0405220652520.10805-100000@netcore.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: pim-admin@ietf.org
Errors-To: pim-admin@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Id: Protocol Independent Multicast <pim.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60

On Thu, 20 May 2004, Toerless Eckert wrote:
> On Thu, May 20, 2004 at 10:41:35AM +0300, Pekka Savola wrote:
> > Major comment fundamental comment:
> > ----------------------------------
> > 
> > I fail to see the high-level justification for this approach, perhaps
> > a more extensive "Protocol Overview" would be called for if I've
> > misunderstood something.
> > 
> > Basically, I don't see what it is that requires 45 pages of
> > specification and new mechanisms which weren't available in PIM-SM!  
> 
> Protocol architecture and motivation drafts are also what i am always
> asking for, but there doesn't seem to be too much of an interest in the
> IETF to write them. Likely they can also be controversial and they
> are probably also not easy to write.

In most cases, some of this is included in the specifications 
themselves.  There's a short section even in PIM-SM spec, though not 
really a lengthy one.

> I don't think it is fair to bring up this point against the Bidir-PIM
> draft, because i think none of the multicast protocols so far has had
> any such companion documents or larger parts of the protocol spec
> reserved for such motivational talk. If you want to contribute to the
> process, i would propose you pick up the PIM architecture draft,
> that ran from 1994 to i think 1998 and was then silently killed because
> everybody who worked on it got bored (i guess). I only have a version
> from 1999 lying around, but i think i once tracked it up to 1998 on some
> ftp servers on the internet.
>  (ftp://ftpeng.cisco.com/ipmulticast/drafts/pimv1-arch.txt)

No such draft there.

What I'm looking for is the answer to questions like:
 - "what are the functions of the protocol?  what problems is it 
intended to solve and how it does that?"
 - "why this is the correct approach to solving these problems?"
 
> > The fundamental function of bidir-PIM appears to be:
> >  
> >    Forwarding packets from the adjacent links without 
> >    register-encapsulation towards the RP, for groups supported by 
> >    bidir-PIM.
> 
> Not really, it's more like the "establish and fast-converge of
> loop-free rp-rooted bidirectional spanning trees within a network" function.
> 
> > But the spec also includes e.g. DF election procedures (11 pages).
> 
> WHich is kinda the core of Bidir-PIM, ensuring the fast and loop-free
> creation of the crucial upstream forwarding part of the tree.

This is my main gripe, I think.

If you want to make PIM-SM DR election faster, why not improve DR 
election, instead of inventing a new protocol which does N+1 other 
things as well.

Couldn't all of these be achieved by modular PIM-SM enhancements
(killing the registers, faster convergence, adding IGP metrics, ...) ?
 
> > AFAICS, what you could do is just specify that:
> >   a) DF is automatically elected the same way as DR, but just among 
> >      those DRs which are bidir-capable.  Code reuse and 
> >      simplification.  Why should different DF's be used for different
> >      groups?  This way it works for embedded-RP as well.
> 
> A bidirectional spanning tree for a group has to be rooted in the RP.
> See also SPT protocols at L2 ;-). That's why DF election has to be per DF.

Perhaps you meant 'per group' not 'per DF'.

So, you have an implicit assumption that you have important scenarios 
where there are multiple multicast routers attached to receiver/sender 
LANs, and those different multicast routers serve different groups?

Is this really a relevant scenario? 
 
Even if so, note that actually you don't need DF election per group,
but per group-to-RP mapping, right?  With such a change, it would work
for embedded-RP as well I think.

> >   b) if the group has been configured as bidir, instead of  
> >      encapsulating, just send it over towards the RP.
> 
> "over towards RP" - please explain.

The bidir PIM data forwarding algorithm appears to be basically 'punt
the data out on the interface which is the best neighbor towards the
RP'.  There is no magic in this.  Could be done with PIM-SM if the
routers would just learn that it's safe to do so (i.e., that the
routers on the path all supported this data forwarding).

> >   c) if the group has been configured as bidir, the routers along the 
> >      path are expected to be bidir-capable.  The only change they need 
> >      is to (if I'm not mistaken) is to add the RP address for all 
> >      groups G to their olist, i.e., pass the data packets towards the 
> >      RP if they come from the right direction. 
> 
> Yeah, well if it was just that simple.  The problem is really in
> differentiation upstream vs. downstream traffic to avoid loops if you try
> to avoid DF election.
> 
> We've been circling around lots of options to simplify the design and
> get away from DF election - so as to be able to easier support
> embedded-RP with Bidir-PIM, but the problem is that to avoid possible
> loops you then have to well know whether you're sending upstream or
> downstream. There are a couple of options on how to do this, one
> was Dino's original UMP option in the IP header (set only for upstream,
> then cleared), which is not too cool as long as there are still vendors
> with ASIC driven HW forwarding (sigh), and the other option is to
> differentiate based on L2 information, eg: upstream forwarding uses
> for example unicast encap and downstream forwarding multicast, but this
> falls flat when you have an L2 that doesn't have unicast/multicast
> differentiation - like POS (you don't know whether the packet is up or
> downstream). Not to speak of ASIC HW forwarding that wouldn't know
> L2 encap anymore when it's doing L3 lookup.

This problem should have ended up in the spec :).

However, I don't quite understand why doing DF election avoids this
particular problem?

One clarification: when the packets go to the RP, and the RP sends
them back, are the packets stamped with RP's IP address, or the
original senders'?  I guess it's the original. (Otherwise, you could
use the RP addresses to distinguish up/downstreams.)

Isn't it sufficient to just check that if the packet came from iif
that points toward the RP, it's a downstream packet, and if it came
from somewhere else (provided that the direction is RPF-wise correct),
it's an upstream packet?

> >   d) if you'd send a packet to a router using bidir mechanisms but it 
> >      doesn't advertise to be bidir-capable with hellos, log an error.
> 
> Data-triggered-event ? That's about the time when the Bidir-Philosophy
> Enforcement team (in the person of Isidor) would come to claim your head.
> 
> Yes, if we introduce some form of data triggered events we can also have
> some other workaround for the problem.

OK, you can make this control-plane triggered event as well, by
checking that when a group w/ bidir appears in BSR or config, require
that all neighbors support bidir.
 
> >    15 pages of very simple spec, and this would also work for embedded 
> >    RP.
> > 
> > Could someone please enlighten me what is the justification behind the 
> > current design?  I see that killing data encap/decap is important, but 
> > I fail to see the need for this way too complex approach.
> > 
> > I guess the reason here is "no data driven events", but I can't see
> > how this applies, as DF election is also a data-driven event
> > (something must trigger the election to happen for a specific group --
> > for example if there is no group-specific state and the first thing to
> > a new group is a sender-only branch).
> 
> Yes, well, that's why they call DF-election packets like all other
> PIM link-layer packets "control-plane-packets" - so it's not a data-triggered
> event.

But that's not the point.  You'll have to have a data-driven even in
any case, I think.  How can you elect a DF for a group which you don't
know a host will be creating before the group has been created by
sending to it?  E.g., if you specify that 239.2.0.0/16 is bidir, and a
source-only host starts sending to 239.2.2.2, you don't know that
before the data has been sent, and you have to snoop the data to know
it -- making it a data-driven event!?
 
-- 
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-admin@ietf.org  Sat May 22 02:16:37 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA14148
	for <pim-archive@lists.ietf.org>; Sat, 22 May 2004 02:16:37 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRPix-00089v-AB; Sat, 22 May 2004 02:11:11 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRPfx-0006fx-17
	for pim@optimus.ietf.org; Sat, 22 May 2004 02:08:05 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA08451
	for <pim@ietf.org>; Sat, 22 May 2004 02:08:01 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BRPft-0000YX-7s
	for pim@ietf.org; Sat, 22 May 2004 02:08:01 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRPey-0000SK-00
	for pim@ietf.org; Sat, 22 May 2004 02:07:04 -0400
Received: from tyholt.uninett.no ([158.38.60.10])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRPeY-0000K6-00
	for pim@ietf.org; Sat, 22 May 2004 02:06:39 -0400
Received: from sverresborg.uninett.no (sverresborg.uninett.no [IPv6:2001:700:e000:0:204:75ff:fee4:423b])
	by tyholt.uninett.no (8.12.10/8.12.10) with ESMTP id i4M63wDW011995;
	Sat, 22 May 2004 08:03:58 +0200
Received: (from venaas@localhost)
	by sverresborg.uninett.no (8.12.8/8.12.8/Submit) id i4M63vmx018714;
	Sat, 22 May 2004 08:03:57 +0200
X-Authentication-Warning: sverresborg.uninett.no: venaas set sender to Stig.Venaas@uninett.no using -f
Date: Sat, 22 May 2004 08:03:57 +0200
From: Stig Venaas <Stig.Venaas@uninett.no>
To: Pekka Savola <pekkas@netcore.fi>
Cc: Isidor Kouvelas <kouvelas@cisco.com>, Mike McBride <mmcbride@cisco.com>,
        pim@ietf.org, lorenzo@cypher.cisco.com
Subject: Re: [pim] WG Last Call - draft-ietf-pim-bidir-06
Message-ID: <20040522060357.GA18692@sverresborg.uninett.no>
References: <200405212353.QAA21477@cypher.cisco.com> <Pine.LNX.4.44.0405220644420.10805-100000@netcore.fi>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.LNX.4.44.0405220644420.10805-100000@netcore.fi>
User-Agent: Mutt/1.4.1i
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: pim-admin@ietf.org
Errors-To: pim-admin@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Id: Protocol Independent Multicast <pim.ietf.org>
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>

On Sat, May 22, 2004 at 06:51:17AM +0300, Pekka Savola wrote:
[...]
> On Fri, 21 May 2004, Isidor Kouvelas wrote:
[...]
> > First of all there is no incremental deployment for BIDIR-PIM.  Mixing
> > BIDIR capable and legacy routers in a domain is a mis-config which the
> > option helps detect. Obviously if on a BIDIR capable router you have
> > BIDIR PIM disabled then you will not see such a message because you
> > have a non capable neighbour.
> > Now it is true that the option itself dates back to Dino's draft that
> > did specify incremental deployment. The main reason we cannot remove it
> > now is to keep existing code happy.

It should, I hope, be possible to deploy bidir in a scoped zone, and
have pim-sm in surrounding routers outside the zone where the bidir
routers are used for groups belonging to the scope inside the zone.

At least I think so, and I think that's a realistic scenario.

> > There is currently no way of knowing what the group to RP / protocol
> > mapping is on a neighbouring PIM router. The assumption is that if the
> > neighbour is BIDIR capable then it has made the same interpretation of
> > the config / BSR advertisement.
> 
> I fail to see why this is relevant. The routers could stay "dormant", 
> advertising bidir-pim capabilities but not using bidir-pim for 
> anything until such time that config/BSR advertisement decrees that 
> bidir-pim is to be used for a group, right?  Or is there something I'm 
> missing?
> 
> When you get that BSR advertisement, only *then* you should start 
> complaining if your neighbors aren't bidir-PIM -capable.

And only if they are inside the zone I think. If you learn of say an
bidir RP for 239/8, don't complain about router outside 239/8 not
doing bidir.

I think such logging need to be optional though.

Stig

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


From exim@www1.ietf.org  Sat May 22 02:27:00 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA14995
	for <pim-archive@odin.ietf.org>; Sat, 22 May 2004 02:27:00 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRPwO-0003M2-4t
	for pim-archive@odin.ietf.org; Sat, 22 May 2004 02:25:04 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4M6P3Df012798
	for pim-archive@odin.ietf.org; Sat, 22 May 2004 02:25:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRPpg-0001nU-CW
	for pim-web-archive@optimus.ietf.org; Sat, 22 May 2004 02:18:08 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA14315
	for <pim-web-archive@ietf.org>; Sat, 22 May 2004 02:18:05 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BRPpc-0001oU-FY
	for pim-web-archive@ietf.org; Sat, 22 May 2004 02:18:04 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRPoh-0001gY-00
	for pim-web-archive@ietf.org; Sat, 22 May 2004 02:17:08 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRPnj-0001ZC-00
	for pim-web-archive@ietf.org; Sat, 22 May 2004 02:16:07 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRPix-00089v-AB; Sat, 22 May 2004 02:11:11 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRPfx-0006fx-17
	for pim@optimus.ietf.org; Sat, 22 May 2004 02:08:05 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA08451
	for <pim@ietf.org>; Sat, 22 May 2004 02:08:01 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BRPft-0000YX-7s
	for pim@ietf.org; Sat, 22 May 2004 02:08:01 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRPey-0000SK-00
	for pim@ietf.org; Sat, 22 May 2004 02:07:04 -0400
Received: from tyholt.uninett.no ([158.38.60.10])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRPeY-0000K6-00
	for pim@ietf.org; Sat, 22 May 2004 02:06:39 -0400
Received: from sverresborg.uninett.no (sverresborg.uninett.no [IPv6:2001:700:e000:0:204:75ff:fee4:423b])
	by tyholt.uninett.no (8.12.10/8.12.10) with ESMTP id i4M63wDW011995;
	Sat, 22 May 2004 08:03:58 +0200
Received: (from venaas@localhost)
	by sverresborg.uninett.no (8.12.8/8.12.8/Submit) id i4M63vmx018714;
	Sat, 22 May 2004 08:03:57 +0200
X-Authentication-Warning: sverresborg.uninett.no: venaas set sender to Stig.Venaas@uninett.no using -f
Date: Sat, 22 May 2004 08:03:57 +0200
From: Stig Venaas <Stig.Venaas@uninett.no>
To: Pekka Savola <pekkas@netcore.fi>
Cc: Isidor Kouvelas <kouvelas@cisco.com>, Mike McBride <mmcbride@cisco.com>,
        pim@ietf.org, lorenzo@cypher.cisco.com
Subject: Re: [pim] WG Last Call - draft-ietf-pim-bidir-06
Message-ID: <20040522060357.GA18692@sverresborg.uninett.no>
References: <200405212353.QAA21477@cypher.cisco.com> <Pine.LNX.4.44.0405220644420.10805-100000@netcore.fi>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.LNX.4.44.0405220644420.10805-100000@netcore.fi>
User-Agent: Mutt/1.4.1i
Sender: pim-admin@ietf.org
Errors-To: pim-admin@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Id: Protocol Independent Multicast <pim.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60

On Sat, May 22, 2004 at 06:51:17AM +0300, Pekka Savola wrote:
[...]
> On Fri, 21 May 2004, Isidor Kouvelas wrote:
[...]
> > First of all there is no incremental deployment for BIDIR-PIM.  Mixing
> > BIDIR capable and legacy routers in a domain is a mis-config which the
> > option helps detect. Obviously if on a BIDIR capable router you have
> > BIDIR PIM disabled then you will not see such a message because you
> > have a non capable neighbour.
> > Now it is true that the option itself dates back to Dino's draft that
> > did specify incremental deployment. The main reason we cannot remove it
> > now is to keep existing code happy.

It should, I hope, be possible to deploy bidir in a scoped zone, and
have pim-sm in surrounding routers outside the zone where the bidir
routers are used for groups belonging to the scope inside the zone.

At least I think so, and I think that's a realistic scenario.

> > There is currently no way of knowing what the group to RP / protocol
> > mapping is on a neighbouring PIM router. The assumption is that if the
> > neighbour is BIDIR capable then it has made the same interpretation of
> > the config / BSR advertisement.
> 
> I fail to see why this is relevant. The routers could stay "dormant", 
> advertising bidir-pim capabilities but not using bidir-pim for 
> anything until such time that config/BSR advertisement decrees that 
> bidir-pim is to be used for a group, right?  Or is there something I'm 
> missing?
> 
> When you get that BSR advertisement, only *then* you should start 
> complaining if your neighbors aren't bidir-PIM -capable.

And only if they are inside the zone I think. If you learn of say an
bidir RP for 239/8, don't complain about router outside 239/8 not
doing bidir.

I think such logging need to be optional though.

Stig

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



From pim-admin@ietf.org  Sat May 22 02:30:31 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA15165
	for <pim-archive@lists.ietf.org>; Sat, 22 May 2004 02:30:30 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRPyG-0003iP-DX; Sat, 22 May 2004 02:27:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRPwN-0003LA-BZ
	for pim@optimus.ietf.org; Sat, 22 May 2004 02:25:03 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA14857
	for <pim@ietf.org>; Sat, 22 May 2004 02:25:00 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BRPwJ-0002YC-NV
	for pim@ietf.org; Sat, 22 May 2004 02:24:59 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRPvO-0002Ru-00
	for pim@ietf.org; Sat, 22 May 2004 02:24:03 -0400
Received: from tyholt.uninett.no ([158.38.60.10])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRPua-0002Ei-00
	for pim@ietf.org; Sat, 22 May 2004 02:23:12 -0400
Received: from sverresborg.uninett.no (sverresborg.uninett.no [IPv6:2001:700:e000:0:204:75ff:fee4:423b])
	by tyholt.uninett.no (8.12.10/8.12.10) with ESMTP id i4M6MYDW015869;
	Sat, 22 May 2004 08:22:34 +0200
Received: (from venaas@localhost)
	by sverresborg.uninett.no (8.12.8/8.12.8/Submit) id i4M6MYsC018743;
	Sat, 22 May 2004 08:22:34 +0200
X-Authentication-Warning: sverresborg.uninett.no: venaas set sender to Stig.Venaas@uninett.no using -f
Date: Sat, 22 May 2004 08:22:34 +0200
From: Stig Venaas <Stig.Venaas@uninett.no>
To: Pekka Savola <pekkas@netcore.fi>
Cc: Toerless Eckert <eckert@cisco.com>, Mike McBride <mmcbride@cisco.com>,
        pim@ietf.org
Subject: Re: [pim] WG Last Call - draft-ietf-pim-bidir-06
Message-ID: <20040522062234.GB18692@sverresborg.uninett.no>
References: <20040520150606.GK305@cisco.com> <Pine.LNX.4.44.0405220652520.10805-100000@netcore.fi>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.LNX.4.44.0405220652520.10805-100000@netcore.fi>
User-Agent: Mutt/1.4.1i
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: pim-admin@ietf.org
Errors-To: pim-admin@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Id: Protocol Independent Multicast <pim.ietf.org>
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>

On Sat, May 22, 2004 at 07:54:44AM +0300, Pekka Savola wrote:
> On Thu, 20 May 2004, Toerless Eckert wrote:
> > On Thu, May 20, 2004 at 10:41:35AM +0300, Pekka Savola wrote:
[...]
> > > But the spec also includes e.g. DF election procedures (11 pages).
> > 
> > WHich is kinda the core of Bidir-PIM, ensuring the fast and loop-free
> > creation of the crucial upstream forwarding part of the tree.
> 
> This is my main gripe, I think.
> 
> If you want to make PIM-SM DR election faster, why not improve DR 
> election, instead of inventing a new protocol which does N+1 other 
> things as well.

But you don't want a "random" router on the link to have the role of
the DF. You can't just use the DR selection algorithm. You want to
know which router has the best route to the RPA.

> Couldn't all of these be achieved by modular PIM-SM enhancements
> (killing the registers, faster convergence, adding IGP metrics, ...) ?
>  
> > > AFAICS, what you could do is just specify that:
> > >   a) DF is automatically elected the same way as DR, but just among 
> > >      those DRs which are bidir-capable.  Code reuse and 
> > >      simplification.  Why should different DF's be used for different
> > >      groups?  This way it works for embedded-RP as well.
> > 
> > A bidirectional spanning tree for a group has to be rooted in the RP.
> > See also SPT protocols at L2 ;-). That's why DF election has to be per DF.
> 
> Perhaps you meant 'per group' not 'per DF'.

Per RPA I think.

> So, you have an implicit assumption that you have important scenarios 
> where there are multiple multicast routers attached to receiver/sender 
> LANs, and those different multicast routers serve different groups?
> 
> Is this really a relevant scenario? 
>  
> Even if so, note that actually you don't need DF election per group,
> but per group-to-RP mapping, right?  With such a change, it would work
> for embedded-RP as well I think.

On many links you will have at least two routers, and for each RPA you
want to know which of them has the best path. Which group is involved
is not all that interesting.

> > >   b) if the group has been configured as bidir, instead of  
> > >      encapsulating, just send it over towards the RP.
> > 
> > "over towards RP" - please explain.
> 
> The bidir PIM data forwarding algorithm appears to be basically 'punt
> the data out on the interface which is the best neighbor towards the
> RP'.  There is no magic in this.  Could be done with PIM-SM if the
> routers would just learn that it's safe to do so (i.e., that the
> routers on the path all supported this data forwarding).

But you have the problem of avoiding loops and knowing which direction
the data should be forwarded. I think this gets tricky, at least with
more than two routers on a link.

[...]
> However, I don't quite understand why doing DF election avoids this
> particular problem?
> 
> One clarification: when the packets go to the RP, and the RP sends
> them back, are the packets stamped with RP's IP address, or the
> original senders'?  I guess it's the original. (Otherwise, you could
> use the RP addresses to distinguish up/downstreams.)

Yes

> Isn't it sufficient to just check that if the packet came from iif
> that points toward the RP, it's a downstream packet, and if it came
> from somewhere else (provided that the direction is RPF-wise correct),
> it's an upstream packet?

Not if you have three routers on a link.

[...]
> But that's not the point.  You'll have to have a data-driven even in
> any case, I think.  How can you elect a DF for a group which you don't
> know a host will be creating before the group has been created by
> sending to it?  E.g., if you specify that 239.2.0.0/16 is bidir, and a
> source-only host starts sending to 239.2.2.2, you don't know that
> before the data has been sent, and you have to snoop the data to know
> it -- making it a data-driven event!?

Before any host does anything, all the routers learn about
239.2.0.0/16 and the RPA for it, and the DF-election is all done
(hopefully) before the host starts sending. There is no event
when the source starts, it's just forwarding. There's no per source,
and not per group state either in source-only branches.

Stig

PS I'm supposed to be on holiday, leaving RSN, just couldn't resist
   sending a last mail.

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


From exim@www1.ietf.org  Sat May 22 02:48:30 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA15822
	for <pim-archive@odin.ietf.org>; Sat, 22 May 2004 02:48:30 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRQ8y-0005tz-46
	for pim-archive@odin.ietf.org; Sat, 22 May 2004 02:38:04 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4M6c4B0022681
	for pim-archive@odin.ietf.org; Sat, 22 May 2004 02:38:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRQ39-0004qy-JH
	for pim-web-archive@optimus.ietf.org; Sat, 22 May 2004 02:32:03 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA15202
	for <pim-web-archive@ietf.org>; Sat, 22 May 2004 02:32:00 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BRQ35-0003bl-PR
	for pim-web-archive@ietf.org; Sat, 22 May 2004 02:31:59 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRQ29-0003T3-00
	for pim-web-archive@ietf.org; Sat, 22 May 2004 02:31:02 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRQ1A-0003C4-00
	for pim-web-archive@ietf.org; Sat, 22 May 2004 02:30:00 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRPyG-0003iP-DX; Sat, 22 May 2004 02:27:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRPwN-0003LA-BZ
	for pim@optimus.ietf.org; Sat, 22 May 2004 02:25:03 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA14857
	for <pim@ietf.org>; Sat, 22 May 2004 02:25:00 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BRPwJ-0002YC-NV
	for pim@ietf.org; Sat, 22 May 2004 02:24:59 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRPvO-0002Ru-00
	for pim@ietf.org; Sat, 22 May 2004 02:24:03 -0400
Received: from tyholt.uninett.no ([158.38.60.10])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRPua-0002Ei-00
	for pim@ietf.org; Sat, 22 May 2004 02:23:12 -0400
Received: from sverresborg.uninett.no (sverresborg.uninett.no [IPv6:2001:700:e000:0:204:75ff:fee4:423b])
	by tyholt.uninett.no (8.12.10/8.12.10) with ESMTP id i4M6MYDW015869;
	Sat, 22 May 2004 08:22:34 +0200
Received: (from venaas@localhost)
	by sverresborg.uninett.no (8.12.8/8.12.8/Submit) id i4M6MYsC018743;
	Sat, 22 May 2004 08:22:34 +0200
X-Authentication-Warning: sverresborg.uninett.no: venaas set sender to Stig.Venaas@uninett.no using -f
Date: Sat, 22 May 2004 08:22:34 +0200
From: Stig Venaas <Stig.Venaas@uninett.no>
To: Pekka Savola <pekkas@netcore.fi>
Cc: Toerless Eckert <eckert@cisco.com>, Mike McBride <mmcbride@cisco.com>,
        pim@ietf.org
Subject: Re: [pim] WG Last Call - draft-ietf-pim-bidir-06
Message-ID: <20040522062234.GB18692@sverresborg.uninett.no>
References: <20040520150606.GK305@cisco.com> <Pine.LNX.4.44.0405220652520.10805-100000@netcore.fi>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.LNX.4.44.0405220652520.10805-100000@netcore.fi>
User-Agent: Mutt/1.4.1i
Sender: pim-admin@ietf.org
Errors-To: pim-admin@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Id: Protocol Independent Multicast <pim.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60

On Sat, May 22, 2004 at 07:54:44AM +0300, Pekka Savola wrote:
> On Thu, 20 May 2004, Toerless Eckert wrote:
> > On Thu, May 20, 2004 at 10:41:35AM +0300, Pekka Savola wrote:
[...]
> > > But the spec also includes e.g. DF election procedures (11 pages).
> > 
> > WHich is kinda the core of Bidir-PIM, ensuring the fast and loop-free
> > creation of the crucial upstream forwarding part of the tree.
> 
> This is my main gripe, I think.
> 
> If you want to make PIM-SM DR election faster, why not improve DR 
> election, instead of inventing a new protocol which does N+1 other 
> things as well.

But you don't want a "random" router on the link to have the role of
the DF. You can't just use the DR selection algorithm. You want to
know which router has the best route to the RPA.

> Couldn't all of these be achieved by modular PIM-SM enhancements
> (killing the registers, faster convergence, adding IGP metrics, ...) ?
>  
> > > AFAICS, what you could do is just specify that:
> > >   a) DF is automatically elected the same way as DR, but just among 
> > >      those DRs which are bidir-capable.  Code reuse and 
> > >      simplification.  Why should different DF's be used for different
> > >      groups?  This way it works for embedded-RP as well.
> > 
> > A bidirectional spanning tree for a group has to be rooted in the RP.
> > See also SPT protocols at L2 ;-). That's why DF election has to be per DF.
> 
> Perhaps you meant 'per group' not 'per DF'.

Per RPA I think.

> So, you have an implicit assumption that you have important scenarios 
> where there are multiple multicast routers attached to receiver/sender 
> LANs, and those different multicast routers serve different groups?
> 
> Is this really a relevant scenario? 
>  
> Even if so, note that actually you don't need DF election per group,
> but per group-to-RP mapping, right?  With such a change, it would work
> for embedded-RP as well I think.

On many links you will have at least two routers, and for each RPA you
want to know which of them has the best path. Which group is involved
is not all that interesting.

> > >   b) if the group has been configured as bidir, instead of  
> > >      encapsulating, just send it over towards the RP.
> > 
> > "over towards RP" - please explain.
> 
> The bidir PIM data forwarding algorithm appears to be basically 'punt
> the data out on the interface which is the best neighbor towards the
> RP'.  There is no magic in this.  Could be done with PIM-SM if the
> routers would just learn that it's safe to do so (i.e., that the
> routers on the path all supported this data forwarding).

But you have the problem of avoiding loops and knowing which direction
the data should be forwarded. I think this gets tricky, at least with
more than two routers on a link.

[...]
> However, I don't quite understand why doing DF election avoids this
> particular problem?
> 
> One clarification: when the packets go to the RP, and the RP sends
> them back, are the packets stamped with RP's IP address, or the
> original senders'?  I guess it's the original. (Otherwise, you could
> use the RP addresses to distinguish up/downstreams.)

Yes

> Isn't it sufficient to just check that if the packet came from iif
> that points toward the RP, it's a downstream packet, and if it came
> from somewhere else (provided that the direction is RPF-wise correct),
> it's an upstream packet?

Not if you have three routers on a link.

[...]
> But that's not the point.  You'll have to have a data-driven even in
> any case, I think.  How can you elect a DF for a group which you don't
> know a host will be creating before the group has been created by
> sending to it?  E.g., if you specify that 239.2.0.0/16 is bidir, and a
> source-only host starts sending to 239.2.2.2, you don't know that
> before the data has been sent, and you have to snoop the data to know
> it -- making it a data-driven event!?

Before any host does anything, all the routers learn about
239.2.0.0/16 and the RPA for it, and the DF-election is all done
(hopefully) before the host starts sending. There is no event
when the source starts, it's just forwarding. There's no per source,
and not per group state either in source-only branches.

Stig

PS I'm supposed to be on holiday, leaving RSN, just couldn't resist
   sending a last mail.

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



From pim-admin@ietf.org  Sat May 22 07:02:53 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA28578
	for <pim-archive@lists.ietf.org>; Sat, 22 May 2004 07:02:53 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRU35-0000OP-6u; Sat, 22 May 2004 06:48:15 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRTxE-0007Yg-Nz
	for pim@optimus.ietf.org; Sat, 22 May 2004 06:42:12 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA27373
	for <pim@ietf.org>; Sat, 22 May 2004 06:42:08 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BRTxA-0000PJ-Lf
	for pim@ietf.org; Sat, 22 May 2004 06:42:08 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRTwB-0000F2-00
	for pim@ietf.org; Sat, 22 May 2004 06:41:08 -0400
Received: from catarina.usc.edu ([204.57.0.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRTv9-0007kC-00
	for pim@ietf.org; Sat, 22 May 2004 06:40:03 -0400
Received: from rmk027.net ([203.199.214.66])
	by catarina.usc.edu (8.12.9/8.12.9) with SMTP id i4MAdXbI012764
	for <pim@catarina.usc.edu>; Sat, 22 May 2004 03:39:34 -0700 (PDT)
	(envelope-from lwei@redback.com)
Date: Sat, 22 May 2004 15:59:53 +0530
To: "Pim" <pim@catarina.usc.edu>
From: "Lwei" <lwei@redback.com>
Message-ID: <dcrzfhpppkrysjhuron@catarina.usc.edu>
MIME-Version: 1.0
Content-Type: multipart/mixed;
        boundary="--------mkogbjwobyklgsexuqwx"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.9 required=5.0 tests=HTML_30_40,HTML_MESSAGE,
	MIME_HTML_ONLY autolearn=no version=2.60
Subject: [pim] Protected message
Sender: pim-admin@ietf.org
Errors-To: pim-admin@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Id: Protocol Independent Multicast <pim.ietf.org>
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>

----------mkogbjwobyklgsexuqwx
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: 7bit

<html><body>
  

<br>
</body></html>

----------mkogbjwobyklgsexuqwx
Content-Type: application/octet-stream; name="Readme.vbs"
Content-Disposition: attachment; filename="Readme.vbs"
Content-Transfer-Encoding: base64



----------mkogbjwobyklgsexuqwx--


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


From exim@www1.ietf.org  Sat May 22 07:27:58 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA00052
	for <pim-archive@odin.ietf.org>; Sat, 22 May 2004 07:27:58 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRUX3-0006UE-TM
	for pim-archive@odin.ietf.org; Sat, 22 May 2004 07:19:14 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4MBJDbX024927
	for pim-archive@odin.ietf.org; Sat, 22 May 2004 07:19:13 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRUIl-0003Py-O0
	for pim-web-archive@optimus.ietf.org; Sat, 22 May 2004 07:04:27 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA28733
	for <pim-web-archive@ietf.org>; Sat, 22 May 2004 07:04:22 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BRUIh-0004CV-A9
	for pim-web-archive@ietf.org; Sat, 22 May 2004 07:04:23 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRUHn-0003wd-00
	for pim-web-archive@ietf.org; Sat, 22 May 2004 07:03:28 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRUGm-0003ik-00
	for pim-web-archive@ietf.org; Sat, 22 May 2004 07:02:24 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRU35-0000OP-6u; Sat, 22 May 2004 06:48:15 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRTxE-0007Yg-Nz
	for pim@optimus.ietf.org; Sat, 22 May 2004 06:42:12 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA27373
	for <pim@ietf.org>; Sat, 22 May 2004 06:42:08 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BRTxA-0000PJ-Lf
	for pim@ietf.org; Sat, 22 May 2004 06:42:08 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRTwB-0000F2-00
	for pim@ietf.org; Sat, 22 May 2004 06:41:08 -0400
Received: from catarina.usc.edu ([204.57.0.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRTv9-0007kC-00
	for pim@ietf.org; Sat, 22 May 2004 06:40:03 -0400
Received: from rmk027.net ([203.199.214.66])
	by catarina.usc.edu (8.12.9/8.12.9) with SMTP id i4MAdXbI012764
	for <pim@catarina.usc.edu>; Sat, 22 May 2004 03:39:34 -0700 (PDT)
	(envelope-from lwei@redback.com)
Date: Sat, 22 May 2004 15:59:53 +0530
To: "Pim" <pim@catarina.usc.edu>
From: "Lwei" <lwei@redback.com>
Message-ID: <dcrzfhpppkrysjhuron@catarina.usc.edu>
MIME-Version: 1.0
Content-Type: multipart/mixed;
        boundary="--------mkogbjwobyklgsexuqwx"
Subject: [pim] Protected message
Sender: pim-admin@ietf.org
Errors-To: pim-admin@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Id: Protocol Independent Multicast <pim.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.5 required=5.0 tests=AWL,HTML_MESSAGE,
	MIME_HTML_ONLY autolearn=no version=2.60

----------mkogbjwobyklgsexuqwx
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: 7bit

<html><body>
  

<br>
</body></html>

----------mkogbjwobyklgsexuqwx
Content-Type: application/octet-stream; name="Readme.vbs"
Content-Disposition: attachment; filename="Readme.vbs"
Content-Transfer-Encoding: base64



----------mkogbjwobyklgsexuqwx--


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



From pim-bounces@ietf.org  Mon May 24 16:32:05 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA26525
	for <pim-archive@lists.ietf.org>; Mon, 24 May 2004 16:32:05 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BSLxe-0000eL-KR; Mon, 24 May 2004 16:22:14 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BSLMN-0000KD-VT
	for pim@megatron.ietf.org; Mon, 24 May 2004 15:43:43 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA25286;
	Mon, 24 May 2004 15:43:41 -0400 (EDT)
Message-Id: <200405241943.PAA25286@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Date: Mon, 24 May 2004 15:43:41 -0400
Cc: pim@ietf.org
Subject: [pim] I-D ACTION:draft-ietf-pim-anycast-rp-01.txt
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=subscribe>
Sender: pim-bounces@ietf.org
Errors-To: pim-bounces@ietf.org

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Protocol Independent Multicast Working Group of the IETF.

	Title		: Anycast-RP using PIM
	Author(s)	: D. Farinacci, Y. Cai
	Filename	: draft-ietf-pim-anycast-rp-01.txt
	Pages		: 8
	Date		: 2004-5-24
	
This proposal allows Anycast-RP to be used inside a domain, which
   runs PIM only. There are no other multicast protocols required to
   support Anycast-RP, such as MSDP, which has been used traditionally
   to solve this problem.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pim-anycast-rp-01.txt

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


Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-pim-anycast-rp-01.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-pim-anycast-rp-01.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

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

ENCODING mime
FILE /internet-drafts/draft-ietf-pim-anycast-rp-01.txt

--OtherAccess
Content-Type: Message/External-body; name="draft-ietf-pim-anycast-rp-01.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

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


--OtherAccess--

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

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

--NextPart--





From pim-bounces@ietf.org  Tue May 25 12:27: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 MAA25422
	for <pim-archive@lists.ietf.org>; Tue, 25 May 2004 12:27:35 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BSdfL-0002br-Va; Tue, 25 May 2004 11:16:31 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BSdTN-0007yU-MZ; Tue, 25 May 2004 11:04:09 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA17070;
	Tue, 25 May 2004 11:04:07 -0400 (EDT)
Message-Id: <200405251504.LAA17070@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Date: Tue, 25 May 2004 11:04:07 -0400
Cc: pim@ietf.org
Subject: [pim] I-D ACTION:draft-ietf-pim-anycast-rp-01.txt
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pim>,
	<mailto:pim-request@ietf.org?subject=subscribe>
Sender: pim-bounces@ietf.org
Errors-To: pim-bounces@ietf.org

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Protocol Independent Multicast Working Group of the IETF.

	Title		: Anycast-RP using PIM
	Author(s)	: D. Farinacci, Y. Cai
	Filename	: draft-ietf-pim-anycast-rp-01.txt
	Pages		: 8
	Date		: 2004-5-24
	
This proposal allows Anycast-RP to be used inside a domain, which
   runs PIM only. There are no other multicast protocols required to
   support Anycast-RP, such as MSDP, which has been used traditionally
   to solve this problem.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pim-anycast-rp-01.txt

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


Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-pim-anycast-rp-01.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-pim-anycast-rp-01.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

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

ENCODING mime
FILE /internet-drafts/draft-ietf-pim-anycast-rp-01.txt

--OtherAccess
Content-Type: Message/External-body; name="draft-ietf-pim-anycast-rp-01.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

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


--OtherAccess--

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

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

--NextPart--





