From bgmp-admin@catarina.usc.edu  Mon Apr  1 08:01:25 2002
Received: from catarina.usc.edu (catarina.usc.edu [204.57.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA23732
	for <pim-archive@lists.ietf.org>; Mon, 1 Apr 2002 08:01:20 -0500 (EST)
Received: from catarina.usc.edu (localhost.localdomain [127.0.0.1])
	by catarina.usc.edu (8.11.6/8.11.6) with ESMTP id g31D0Q464986
	for <pim-archive@lists.ietf.org>; Mon, 1 Apr 2002 05:00:26 -0800 (PST)
	(envelope-from bgmp-admin@catarina.usc.edu)
Date: Mon, 1 Apr 2002 05:00:26 -0800 (PST)
Message-Id: <200204011300.g31D0Q464986@catarina.usc.edu>
Subject: catarina.usc.edu mailing list memberships reminder
From: mailman-owner@catarina.usc.edu
To: pim-archive@ietf.org
X-No-Archive: yes
X-Ack: no
Sender: bgmp-admin@catarina.usc.edu
Errors-To: bgmp-admin@catarina.usc.edu
X-BeenThere: bgmp@catarina.usc.edu
X-Mailman-Version: 2.0.8
Precedence: bulk

This is a reminder, sent out once a month, about your catarina.usc.edu
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@catarina.usc.edu) containing just
the word 'help' in the message body, and an email message will be sent
to you with instructions.

If you have questions, problems, comments, etc, send them to
mailman-owner@catarina.usc.edu.  Thanks!

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

List                                     Password // URL
----                                     --------  
pim@catarina.usc.edu                     kimoit    
http://catarina.usc.edu/mailman/options/pim/pim-archive%40lists.ietf.org


From pim-admin@catarina.usc.edu  Tue Apr  2 18:19:14 2002
Received: from catarina.usc.edu (catarina.usc.edu [204.57.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA07681
	for <pim-archive@lists.ietf.org>; Tue, 2 Apr 2002 18:19:12 -0500 (EST)
Received: from catarina.usc.edu (localhost.localdomain [127.0.0.1])
	by catarina.usc.edu (8.11.6/8.11.6) with ESMTP id g32NF8497440;
	Tue, 2 Apr 2002 15:15:09 -0800 (PST)
	(envelope-from pim-admin@catarina.usc.edu)
Received: from stash.attlabs.att.com (mpfg.attlabs.net [12.106.35.2])
	by catarina.usc.edu (8.11.6/8.11.6) with ESMTP id g32MoS497062;
	Tue, 2 Apr 2002 14:50:28 -0800 (PST)
	(envelope-from fenner@research.att.com)
Received: from stash.attlabs.att.com (localhost [127.0.0.1])
	by stash.attlabs.att.com (8.12.2/8.12.2) with ESMTP id g32Mo9I2044819;
	Tue, 2 Apr 2002 14:50:09 -0800 (PST)
	(envelope-from fenner@stash.attlabs.att.com)
Received: (from fenner@localhost)
	by stash.attlabs.att.com (8.12.2/8.12.2/Submit) id g32Mo757044817;
	Tue, 2 Apr 2002 14:50:07 -0800 (PST)
Message-Id: <200204022250.g32Mo757044817@stash.attlabs.att.com>
To: routing-discussion@ietf.org
From: Bill Fenner <fenner@research.att.com>
Subject: [pim] routing-discussion mailing list resurrected
Sender: pim-admin@catarina.usc.edu
Errors-To: pim-admin@catarina.usc.edu
X-BeenThere: pim@catarina.usc.edu
X-Mailman-Version: 2.0.8
Precedence: bulk
List-Help: <mailto:pim-request@catarina.usc.edu?subject=help>
List-Post: <mailto:pim@catarina.usc.edu>
List-Subscribe: <http://catarina.usc.edu/mailman/listinfo/pim>,
	<mailto:pim-request@catarina.usc.edu?subject=subscribe>
List-Id: <pim.catarina.usc.edu>
List-Unsubscribe: <http://catarina.usc.edu/mailman/listinfo/pim>,
	<mailto:pim-request@catarina.usc.edu?subject=unsubscribe>
List-Archive: <http://catarina.usc.edu/pipermail/pim/>
Date: Tue, 2 Apr 2002 14:50:07 -0800 (PST)

Dear Routing Area participants,

  Alex and I have resurrected the routing-discussion mailing list,
routing-discussion@ietf.org (routing-discussion-request@ietf.org to
subscribe, or https://www1.ietf.org/mailman/listinfo/routing-discussion).
This list is intended for use for general routing area issues, especially
routing-related items that cross multiple working groups or do not fall
specifically within a given group's charter.  It will also be used for
cross-area coordination of routing issues.

  Please sign up for the list if you are interested.

Thanks,
  Bill and Alex.
_______________________________________________
pim mailing list
pim@catarina.usc.edu
http://catarina.usc.edu/mailman/listinfo/pim


From pim-admin@catarina.usc.edu  Tue Apr  9 18:31:50 2002
Received: from catarina.usc.edu (catarina.usc.edu [204.57.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA24812
	for <pim-archive@odin.ietf.org>; Tue, 9 Apr 2002 18:31:48 -0400 (EDT)
Received: from catarina.usc.edu (localhost.localdomain [127.0.0.1])
	by catarina.usc.edu (8.11.6/8.11.6) with ESMTP id g39MU7436689;
	Tue, 9 Apr 2002 15:30:07 -0700 (PDT)
	(envelope-from pim-admin@catarina.usc.edu)
Received: from external.zumanetworks.com ([64.161.185.13])
	by catarina.usc.edu (8.11.6/8.11.6) with SMTP id g39MT6436667
	for <pim@catarina.usc.edu>; Tue, 9 Apr 2002 15:29:06 -0700 (PDT)
	(envelope-from jhuang@zumanetworks.com)
Received: from no.name.available by external.zumanetworks.com
          via smtpd (for catarina.usc.edu [204.57.0.1]) with SMTP; 9 Apr 2002 22:29:06 UT
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
Message-ID: <E277CFA74A8D544A83F5314976B0451B7F2BB5@msmail.win.zumanetworks.com>
Thread-Topic: pim-sm questions
Thread-Index: AcHgFfBdr8tQs/m5QNGvum3vqgnI/w==
From: "James Huang" <jhuang@zumanetworks.com>
To: <pim@catarina.usc.edu>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by catarina.usc.edu id g39MT6436667
Subject: [pim] pim-sm questions
Sender: pim-admin@catarina.usc.edu
Errors-To: pim-admin@catarina.usc.edu
X-BeenThere: pim@catarina.usc.edu
X-Mailman-Version: 2.0.8
Precedence: bulk
List-Help: <mailto:pim-request@catarina.usc.edu?subject=help>
List-Post: <mailto:pim@catarina.usc.edu>
List-Subscribe: <http://catarina.usc.edu/mailman/listinfo/pim>,
	<mailto:pim-request@catarina.usc.edu?subject=subscribe>
List-Id: <pim.catarina.usc.edu>
List-Unsubscribe: <http://catarina.usc.edu/mailman/listinfo/pim>,
	<mailto:pim-request@catarina.usc.edu?subject=unsubscribe>
List-Archive: <http://catarina.usc.edu/pipermail/pim/>
Date: Tue, 9 Apr 2002 15:28:57 -0700
Content-Transfer-Encoding: 8bit

Hi all,

I have two questions related to pim-sm:

(1) When CouldAssert(S,G,I) becomes FALSE and the per-interface (S,G) assert state-machine moves from IAmWinner to NoInfo, a AssertCancel(S,G) message will be sent. According to the spec, it will send a (S,G) assert with RPT bit set to 1 and metric set to infinite.  What is the reason for setting RPT to 1 when a (S,G) assert is sent?

(2) According to sec 4.5.9 of the latest spec, triggered Prune(S,G,rpt) will be send to RPF'(S,G,rpt).  What if RPF'(S,G,rpt) is the same as RPF'(S,G) as in the following case?  Should triggered Prune(S,G,rpt) be sent to RPF'(*,G) instead?

			S --------------> RP
			|			|
			|			|
			R1			R2
			|			|
			|			|
		-----------------------------------
			|			|
			|			|
			R3			R4
			^			^
			|			|
			|			|
		igmp(S,G) join	   igmp(*,G) join

In this case, R1 will send a (S,G) assert when R2 forward the (S,G) traffic to the lan.
WHen R4 sees the assert, it will set SPTbit to 1 and PruneDesired(S,G) become TRUE.
R4 will send a Prune(S,G,rpt) upstream.  Should R4 send it to R2 or R1??

Regards,
James C. Huang

                    

_______________________________________________
pim mailing list
pim@catarina.usc.edu
http://catarina.usc.edu/mailman/listinfo/pim


From pim-admin@catarina.usc.edu  Tue Apr  9 19:08:00 2002
Received: from catarina.usc.edu (catarina.usc.edu [204.57.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA25294
	for <pim-archive@odin.ietf.org>; Tue, 9 Apr 2002 19:07:55 -0400 (EDT)
Received: from catarina.usc.edu (localhost.localdomain [127.0.0.1])
	by catarina.usc.edu (8.11.6/8.11.6) with ESMTP id g39N71437242;
	Tue, 9 Apr 2002 16:07:01 -0700 (PDT)
	(envelope-from pim-admin@catarina.usc.edu)
Received: from external.zumanetworks.com (external.zumanetworks.com [64.161.185.13])
	by catarina.usc.edu (8.11.6/8.11.6) with SMTP id g39N6i437229
	for <pim@catarina.usc.edu>; Tue, 9 Apr 2002 16:06:44 -0700 (PDT)
	(envelope-from jhuang@zumanetworks.com)
Received: from no.name.available by external.zumanetworks.com
          via smtpd (for catarina.usc.edu [204.57.0.1]) with SMTP; 9 Apr 2002 23:06:44 UT
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: [pim] pim-sm questions
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
Message-ID: <E277CFA74A8D544A83F5314976B0451B7FB090@msmail.win.zumanetworks.com>
Thread-Topic: pim-sm questions
Thread-Index: AcHgFfBdr8tQs/m5QNGvum3vqgnI/wAA+Ovg
From: "James Huang" <jhuang@zumanetworks.com>
To: <pim@catarina.usc.edu>
Cc: "Reuben Sivan" <rsivan@zumanetworks.com>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by catarina.usc.edu id g39N6i437229
Sender: pim-admin@catarina.usc.edu
Errors-To: pim-admin@catarina.usc.edu
X-BeenThere: pim@catarina.usc.edu
X-Mailman-Version: 2.0.8
Precedence: bulk
List-Help: <mailto:pim-request@catarina.usc.edu?subject=help>
List-Post: <mailto:pim@catarina.usc.edu>
List-Subscribe: <http://catarina.usc.edu/mailman/listinfo/pim>,
	<mailto:pim-request@catarina.usc.edu?subject=subscribe>
List-Id: <pim.catarina.usc.edu>
List-Unsubscribe: <http://catarina.usc.edu/mailman/listinfo/pim>,
	<mailto:pim-request@catarina.usc.edu?subject=unsubscribe>
List-Archive: <http://catarina.usc.edu/pipermail/pim/>
Date: Tue, 9 Apr 2002 16:06:33 -0700
Content-Transfer-Encoding: 8bit

Hi all,

I have figured out the answer for my question (2).  When R4 receives the Assert(S,G) from R1, it will move the per-intf (S,G) assert state-machine from the NoINfo state to the AssertLoser state and set SPT bit to 1.  Setting SPTbit to 1 will in turn cause AssertTrackingDesired(S,G,I) to become FALSE, and the state-machine will again move from the AssertLoser state to the NoInfo state.  So When R4 sends a prune(S,G,rpt) to RPF'(S,G,rpt), it will be send RPF'(*,G).

I am still confused by question (1). Can someone find the answer for me?

Regards,
James Huang 

-----Original Message-----
From: James Huang 
Sent: Tuesday, April 09, 2002 3:29 PM
To: pim@catarina.usc.edu
Subject: [pim] pim-sm questions


Hi all,

I have two questions related to pim-sm:

(1) When CouldAssert(S,G,I) becomes FALSE and the per-interface (S,G) assert state-machine moves from IAmWinner to NoInfo, a AssertCancel(S,G) message will be sent. According to the spec, it will send a (S,G) assert with RPT bit set to 1 and metric set to infinite.  What is the reason for setting RPT to 1 when a (S,G) assert is sent?

(2) According to sec 4.5.9 of the latest spec, triggered Prune(S,G,rpt) will be send to RPF'(S,G,rpt).  What if RPF'(S,G,rpt) is the same as RPF'(S,G) as in the following case?  Should triggered Prune(S,G,rpt) be sent to RPF'(*,G) instead?

			S --------------> RP
			|			|
			|			|
			R1			R2
			|			|
			|			|
		-----------------------------------
			|			|
			|			|
			R3			R4
			^			^
			|			|
			|			|
		igmp(S,G) join	   igmp(*,G) join

In this case, R1 will send a (S,G) assert when R2 forward the (S,G) traffic to the lan.
WHen R4 sees the assert, it will set SPTbit to 1 and PruneDesired(S,G) become TRUE.
R4 will send a Prune(S,G,rpt) upstream.  Should R4 send it to R2 or R1??

Regards,
James C. Huang

                    

_______________________________________________
pim mailing list
pim@catarina.usc.edu
http://catarina.usc.edu/mailman/listinfo/pim
_______________________________________________
pim mailing list
pim@catarina.usc.edu
http://catarina.usc.edu/mailman/listinfo/pim


From pim-admin@catarina.usc.edu  Wed Apr 10 16:05:58 2002
Received: from catarina.usc.edu (catarina.usc.edu [204.57.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA01473
	for <pim-archive@lists.ietf.org>; Wed, 10 Apr 2002 16:05:58 -0400 (EDT)
Received: from catarina.usc.edu (localhost.localdomain [127.0.0.1])
	by catarina.usc.edu (8.11.6/8.11.6) with ESMTP id g3AK52456099;
	Wed, 10 Apr 2002 13:05:02 -0700 (PDT)
	(envelope-from pim-admin@catarina.usc.edu)
Received: from external.zumanetworks.com (external.zumanetworks.com [64.161.185.13])
	by catarina.usc.edu (8.11.6/8.11.6) with SMTP id g3AK4b456082
	for <pim@catarina.usc.edu>; Wed, 10 Apr 2002 13:04:37 -0700 (PDT)
	(envelope-from jhuang@zumanetworks.com)
Received: from no.name.available by external.zumanetworks.com
          via smtpd (for catarina.usc.edu [204.57.0.1]) with SMTP; 10 Apr 2002 20:04:37 UT
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
Message-ID: <E277CFA74A8D544A83F5314976B0451B7FB091@msmail.win.zumanetworks.com>
Thread-Topic: Per-intf (S,G) assert state-machine
Thread-Index: AcHgyvDcrtFiuKsERpG6SW7COCqpag==
From: "James Huang" <jhuang@zumanetworks.com>
To: <pim@catarina.usc.edu>
Cc: "Reuben Sivan" <rsivan@zumanetworks.com>,
        "Junyu Mai" <jmai@zumanetworks.com>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by catarina.usc.edu id g3AK4b456082
Subject: [pim] Per-intf (S,G) assert state-machine
Sender: pim-admin@catarina.usc.edu
Errors-To: pim-admin@catarina.usc.edu
X-BeenThere: pim@catarina.usc.edu
X-Mailman-Version: 2.0.8
Precedence: bulk
List-Help: <mailto:pim-request@catarina.usc.edu?subject=help>
List-Post: <mailto:pim@catarina.usc.edu>
List-Subscribe: <http://catarina.usc.edu/mailman/listinfo/pim>,
	<mailto:pim-request@catarina.usc.edu?subject=subscribe>
List-Id: <pim.catarina.usc.edu>
List-Unsubscribe: <http://catarina.usc.edu/mailman/listinfo/pim>,
	<mailto:pim-request@catarina.usc.edu?subject=unsubscribe>
List-Archive: <http://catarina.usc.edu/pipermail/pim/>
Date: Wed, 10 Apr 2002 13:04:37 -0700
Content-Transfer-Encoding: 8bit

Hi all,

The per-intf (S,G) assert state-machine will transition from the NoInfo state to the AssertLoser state when it receives a prefered assert with RPTbit clear and AssertTrackingDesired(S,G,I) == TRUE.  Also it will set SPTbit(S,G) to 1 if the Assert message is received from RPF_intf(S).  

My question is "Should the state-machine also start the KeepAliveTimer(S,G) if the Assert message is received from RPF_intf(S)?".  Sptbit set to 1 while KeepAliveTimer not running doesn't seem to be a good state to me.  I have run into a scenario where this problem can cause a black-hole in (S,G) forwarding.

The scenario is as follows:



                               RP:225 *****
                                      * 1 *
                                      *****
                                        |
                                        |  lan1
                                        |
                                      *****         =====  receiver
                                      * 2 *---------= 3 = (192.168.4.6, 
                                      *****   lan2  =====  225.1.1.1)
                                        |                              
                                        |
                               lan3     |  
                      -------------------------------------
                            |                        |
                            |                        |
                     lan6   |                        |
              =====       *****                    *****
              = 8 =-------* 4 *                    * 5 *
              =====       *****                    *****
             receiver       |                        |
           (192.168.4.6,    | lan4              lan5 |
            225.1.1.1)      |                        |
                          =====                    =====
                          = 6 =                    = 7 =
                          =====                    =====
                         source                   receiver (*,225.1.1.1)



(1) host 7 sends a igmp (*,G) join
(2) host 8 sends a igmp (S,G) join
(3) host 3 sends a igmp (S,G) join
(4) host 6 pings 225.1.1.1 a few times
(5) wait until the KeepAliveTimer times out in router 2 and router 4
(6) host 6 pings 225.1.1.1 continuously
(7) host 8 sends a igmp (S,G) leave

After step(7), this has become the classical turn-around router scenario.  However, R4 has also become the (S,G) Assert Winner for lan3.
When R4's Assert timer expires, it will send a periodic Assert(S,G) message.  When R5 receives the Assert message, its per-intf (S,G) Assert state-machine will transition from the NoINfo state to the AssertLoser state.  Also R5 will set SPTbit(S,G) to 1.  This will change AssertTrackingDesired(S,G,I) at R5 to False and so R5's Assert state-machine will be moved back to the NoInfo state.  Setting Sptbit(S,G) to 1 will make PruneDesired(S,G,rpt) at R5 to become true.  So R5 will send a Prune(S,G,rpt) to R2.  When R2 receives the Prune(S,G,rpt) from R5, its inherited_olist(S,G) becomes NULL.  So JoinDesired(S,G) becomes False at R2 and it will send a prune(S,G) to R4.  From now on, R4 will no longer forward (S,G) traffic to lan3 and a black-hole is created.

This problem can be fixed by setting KeepAliveTimer(S,G) at R5 when it receives the Assert(S,G) message from R4.  With this fix, R5 has both SPTbit(S,G) set to 1 and the KeepAliveTimer(S,G) running.  So it will send a Prune(S,G,rpt) to R2 and a Join(S,G) to R4.  This will prevent the black-hole from being created in this scenario.

 
Regards,
James Huang

_______________________________________________
pim mailing list
pim@catarina.usc.edu
http://catarina.usc.edu/mailman/listinfo/pim


From pim-admin@catarina.usc.edu  Wed Apr 10 16:11:43 2002
Received: from catarina.usc.edu (catarina.usc.edu [204.57.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA01610
	for <pim-archive@lists.ietf.org>; Wed, 10 Apr 2002 16:11:43 -0400 (EDT)
Received: from catarina.usc.edu (localhost.localdomain [127.0.0.1])
	by catarina.usc.edu (8.11.6/8.11.6) with ESMTP id g3AKB1456254;
	Wed, 10 Apr 2002 13:11:01 -0700 (PDT)
	(envelope-from pim-admin@catarina.usc.edu)
Received: from external.zumanetworks.com (external.zumanetworks.com [64.161.185.13])
	by catarina.usc.edu (8.11.6/8.11.6) with SMTP id g3AKAV456240
	for <pim@catarina.usc.edu>; Wed, 10 Apr 2002 13:10:31 -0700 (PDT)
	(envelope-from jhuang@zumanetworks.com)
Received: from no.name.available by external.zumanetworks.com
          via smtpd (for catarina.usc.edu [204.57.0.1]) with SMTP; 10 Apr 2002 20:10:31 UT
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
Message-ID: <E277CFA74A8D544A83F5314976B0451B7FB092@msmail.win.zumanetworks.com>
Thread-Topic: Per-intf (S,G) assert state-machine
Thread-Index: AcHgy8N4NC2Nd4AqTE22D0REHgSr3A==
From: "James Huang" <jhuang@zumanetworks.com>
To: <pim@catarina.usc.edu>
Cc: "Reuben Sivan" <rsivan@zumanetworks.com>,
        "Junyu Mai" <jmai@zumanetworks.com>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by catarina.usc.edu id g3AKAV456240
Subject: [pim] Per-intf (S,G) assert state-machine
Sender: pim-admin@catarina.usc.edu
Errors-To: pim-admin@catarina.usc.edu
X-BeenThere: pim@catarina.usc.edu
X-Mailman-Version: 2.0.8
Precedence: bulk
List-Help: <mailto:pim-request@catarina.usc.edu?subject=help>
List-Post: <mailto:pim@catarina.usc.edu>
List-Subscribe: <http://catarina.usc.edu/mailman/listinfo/pim>,
	<mailto:pim-request@catarina.usc.edu?subject=subscribe>
List-Id: <pim.catarina.usc.edu>
List-Unsubscribe: <http://catarina.usc.edu/mailman/listinfo/pim>,
	<mailto:pim-request@catarina.usc.edu?subject=unsubscribe>
List-Archive: <http://catarina.usc.edu/pipermail/pim/>
Date: Wed, 10 Apr 2002 13:10:30 -0700
Content-Transfer-Encoding: 8bit

Hi all,

The per-intf (S,G) assert state-machine will transition from the NoInfo state to the AssertLoser state when it receives a prefered assert with RPTbit clear and AssertTrackingDesired(S,G,I) == TRUE.  Also it will set SPTbit(S,G) to 1 if the Assert message is received from RPF_intf(S).  

My question is "Should the state-machine also start the KeepAliveTimer(S,G) if the Assert message is received from RPF_intf(S)?".  Sptbit set to 1 while KeepAliveTimer not running doesn't seem to be a good state to me.  I have run into a scenario where this problem can cause a black-hole in (S,G) forwarding.

The scenario is as follows:



                               RP:225 *****
                                      * 1 *
                                      *****
                                        |
                                        |  lan1
                                        |
                                      *****         =====  receiver
                                      * 2 *---------= 3 = (192.168.4.6, 
                                      *****   lan2  =====  225.1.1.1)
                                        |                              
                                        |
                               lan3     |  
                      -------------------------------------
                            |                        |
                            |                        |
                     lan6   |                        |
              =====       *****                    *****
              = 8 =-------* 4 *                    * 5 *
              =====       *****                    *****
             receiver       |                        |
           (192.168.4.6,    | lan4              lan5 |
            225.1.1.1)      |                        |
                          =====                    =====
                          = 6 =                    = 7 =
                          =====                    =====
                         source                   receiver (*,225.1.1.1)



(1) host 7 sends a igmp (*,G) join
(2) host 8 sends a igmp (S,G) join
(3) host 3 sends a igmp (S,G) join
(4) host 6 pings 225.1.1.1 a few times
(5) wait until the KeepAliveTimer times out in router 2 and router 4
(6) host 6 pings 225.1.1.1 continuously
(7) host 8 sends a igmp (S,G) leave

Assuming that router 5 will not switch from the PRT tree to the SPT tree when it call CheckSwitchtoSpt(S,G).

After step(7), this has become the classical turn-around router scenario.  However, R4 has also become the (S,G) Assert Winner for lan3.
When R4's Assert timer expires, it will send a periodic Assert(S,G) message.  When R5 receives the Assert message, its per-intf (S,G) Assert state-machine will transition from the NoINfo state to the AssertLoser state.  Also R5 will set SPTbit(S,G) to 1.  This will change AssertTrackingDesired(S,G,I) at R5 to False and so R5's Assert state-machine will be moved back to the NoInfo state.  Setting Sptbit(S,G) to 1 will make PruneDesired(S,G,rpt) at R5 to become true.  So R5 will send a Prune(S,G,rpt) to R2.  When R2 receives the Prune(S,G,rpt) from R5, its inherited_olist(S,G) becomes NULL.  So JoinDesired(S,G) becomes False at R2 and it will send a prune(S,G) to R4.  From now on, R4 will no longer forward (S,G) traffic to lan3 and a black-hole is created.

This problem can be fixed by setting KeepAliveTimer(S,G) at R5 when it receives the Assert(S,G) message from R4.  With this fix, R5 has both SPTbit(S,G) set to 1 and the KeepAliveTimer(S,G) running.  So it will send a Prune(S,G,rpt) to R2 and a Join(S,G) to R4.  This will prevent the black-hole from being created in this scenario.

 
Regards,
James Huang


_______________________________________________
pim mailing list
pim@catarina.usc.edu
http://catarina.usc.edu/mailman/listinfo/pim


From pim-admin@catarina.usc.edu  Wed Apr 10 17:33:56 2002
Received: from catarina.usc.edu (catarina.usc.edu [204.57.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA03262
	for <pim-archive@lists.ietf.org>; Wed, 10 Apr 2002 17:33:54 -0400 (EDT)
Received: from catarina.usc.edu (localhost.localdomain [127.0.0.1])
	by catarina.usc.edu (8.11.6/8.11.6) with ESMTP id g3ALX2457583;
	Wed, 10 Apr 2002 14:33:02 -0700 (PDT)
	(envelope-from pim-admin@catarina.usc.edu)
Received: from dmz1.procket.com (dmz1.procket.com [65.174.124.36])
	by catarina.usc.edu (8.11.6/8.11.6) with ESMTP id g3ALPd457447
	for <pim@catarina.usc.edu>; Wed, 10 Apr 2002 14:25:47 -0700 (PDT)
	(envelope-from John.Zwiebel@procket.com)
Received: from miata.procket.com (miata.procket.com [65.174.124.5])
	by dmz1.procket.com (Postfix) with ESMTP
	id 047A723C2F; Wed, 10 Apr 2002 14:14:35 -0700 (PDT)
Received: from EXCHANGE0-0.na.procket.com (exchange0b.na.procket.com [10.1.7.8])
	by miata.procket.com (8.12.1/8.12.1) with ESMTP id g3ALPPvM012952;
	Wed, 10 Apr 2002 14:25:25 -0700 (PDT)
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Subject: RE: [pim] Per-intf (S,G) assert state-machine
Message-ID: <D2EC481073504E498A8DB9C0687E8CAF01842612@EXCHANGE0-0.na.procket.com>
Thread-Topic: [pim] Per-intf (S,G) assert state-machine
Thread-Index: AcHgyvDcrtFiuKsERpG6SW7COCqpagACDFhg
From: "John Zwiebel" <John.Zwiebel@procket.com>
To: "James Huang" <jhuang@zumanetworks.com>, <pim@catarina.usc.edu>
Cc: "Reuben Sivan" <rsivan@zumanetworks.com>,
        "Junyu Mai" <jmai@zumanetworks.com>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by catarina.usc.edu id g3ALPd457447
Sender: pim-admin@catarina.usc.edu
Errors-To: pim-admin@catarina.usc.edu
X-BeenThere: pim@catarina.usc.edu
X-Mailman-Version: 2.0.8
Precedence: bulk
List-Help: <mailto:pim-request@catarina.usc.edu?subject=help>
List-Post: <mailto:pim@catarina.usc.edu>
List-Subscribe: <http://catarina.usc.edu/mailman/listinfo/pim>,
	<mailto:pim-request@catarina.usc.edu?subject=subscribe>
List-Id: <pim.catarina.usc.edu>
List-Unsubscribe: <http://catarina.usc.edu/mailman/listinfo/pim>,
	<mailto:pim-request@catarina.usc.edu?subject=unsubscribe>
List-Archive: <http://catarina.usc.edu/pipermail/pim/>
Date: Wed, 10 Apr 2002 14:25:25 -0700
Content-Transfer-Encoding: 8bit


FWIW:
If a router is recevinging an IGMPv3 report for a specific
(S,G), I do not believe one should worry about data when
setting the KAT on the last-hop router.  One could argue
that unless S was in the SSM range that only data should
determine the KAT, but then you will have a case where 
state will be deleted and then recreated over and over every
3 minutes for (IMHO) no good reason.  I recognize that for
non-SSM groups routers that are further upstream on the SPT will
delete and reinstall the (S,G) resulting in up to a 60 second
black-hole.  I submit that "if its important" this not happen,
that it is an error for the host to send an IGMPv3 (S,G) report.
However, for most video/audio uses: a) the user seldom joins 
before the source is sending; b) migrating to IGMPv3 and 
(S,G) reports is 'more important' than solving this 'interim
problem'.

If router 5 has (S,G) state, this is -not- a turn-around problem.
Since you have R5 setting the SPT bit R2 does not need to
worry about identifying 'non-atomic' joins (PIM (*,G) joins
without an (S,G,R) prune) with is a requirement to identify
a router as a "turn-around" router.

R5 should not transition to assert loser.  Its IIF is on LAN3
so it should never forward for the source so it should never
participate in an assert (ie only a router that has an interface
in the olist that sees an assert should care here).

R5 does care about the assert because it needs to know when it
can switch from the RPT to the SPT.  Since the IIF to both the
RPT and SPT are the same, the only way it can be -sure- it received
packets on the SPT is if it sees the assert.

Whether or not the SPT-bit is set the (S,G) KAT should be updated
anytime R5 forwards a packet.  Since the only time one should see an
assert on LAN3 is when there is a data packet, the KAT should be
running.

Finally, even though the SPT-bit is not set on R5, there is no
reason it should not be sending an (S,G) join toward the source
and overriding any actions of R2 that might cause a black-hole.

The only thing the SPT-bit should do is enable sending an (S,G,R)
prune from R5.

HOWEVER, if you want to implement updating the KAT when you see 
the assert, you start the KAT, I doubt it will cause any
interoperability
problems.  

Just be sure that you don't assert when you see an assert.  Only 
send an assert when you actually see data on an interface in the
Olist. 

> -----Original Message-----
> From: James Huang [mailto:jhuang@zumanetworks.com] 
> Sent: Wednesday, April 10, 2002 1:05 PM
> To: pim@catarina.usc.edu
> Cc: Reuben Sivan; Junyu Mai
> Subject: [pim] Per-intf (S,G) assert state-machine
> 
> 
> Hi all,
> 
> The per-intf (S,G) assert state-machine will transition from 
> the NoInfo state to the AssertLoser state when it receives a 
> prefered assert with RPTbit clear and 
> AssertTrackingDesired(S,G,I) == TRUE.  Also it will set 
> SPTbit(S,G) to 1 if the Assert message is received from RPF_intf(S).  
> 
> My question is "Should the state-machine also start the 
> KeepAliveTimer(S,G) if the Assert message is received from 
> RPF_intf(S)?".  Sptbit set to 1 while KeepAliveTimer not 
> running doesn't seem to be a good state to me.  I have run 
> into a scenario where this problem can cause a black-hole in 
> (S,G) forwarding.
> 
> The scenario is as follows:
> 
> 
> 
>                                RP:225 *****
>                                       * 1 *
>                                       *****
>                                         |
>                                         |  lan1
>                                         |
>                                       *****         =====  receiver
>                                       * 2 *---------= 3 = 
> (192.168.4.6, 
>                                       *****   lan2  =====  225.1.1.1)
>                                         |                     
>          
>                                         |
>                                lan3     |  
>                       -------------------------------------
>                             |                        |
>                             |                        |
>                      lan6   |                        |
>               =====       *****                    *****
>               = 8 =-------* 4 *                    * 5 *
>               =====       *****                    *****
>              receiver       |                        |
>            (192.168.4.6,    | lan4              lan5 |
>             225.1.1.1)      |                        |
>                           =====                    =====
>                           = 6 =                    = 7 =
>                           =====                    =====
>                          source                   receiver 
> (*,225.1.1.1)
> 
> 
> 
> (1) host 7 sends a igmp (*,G) join
> (2) host 8 sends a igmp (S,G) join
> (3) host 3 sends a igmp (S,G) join
> (4) host 6 pings 225.1.1.1 a few times
> (5) wait until the KeepAliveTimer times out in router 2 and router 4
> (6) host 6 pings 225.1.1.1 continuously
> (7) host 8 sends a igmp (S,G) leave
> 
> After step(7), this has become the classical turn-around 
> router scenario.  However, R4 has also become the (S,G) 
> Assert Winner for lan3.
> When R4's Assert timer expires, it will send a periodic 
> Assert(S,G) message.  When R5 receives the Assert message, 
> its per-intf (S,G) Assert state-machine will transition from 
> the NoINfo state to the AssertLoser state.  Also R5 will set 
> SPTbit(S,G) to 1.  This will change 
> AssertTrackingDesired(S,G,I) at R5 to False and so R5's 
> Assert state-machine will be moved back to the NoInfo state.  
> Setting Sptbit(S,G) to 1 will make PruneDesired(S,G,rpt) at 
> R5 to become true.  So R5 will send a Prune(S,G,rpt) to R2.  
> When R2 receives the Prune(S,G,rpt) from R5, its 
> inherited_olist(S,G) becomes NULL.  So JoinDesired(S,G) 
> becomes False at R2 and it will send a prune(S,G) to R4.  
> From now on, R4 will no longer forward (S,G) traffic to lan3 
> and a black-hole is created.
> 
> This problem can be fixed by setting KeepAliveTimer(S,G) at 
> R5 when it receives the Assert(S,G) message from R4.  With 
> this fix, R5 has both SPTbit(S,G) set to 1 and the 
> KeepAliveTimer(S,G) running.  So it will send a 
> Prune(S,G,rpt) to R2 and a Join(S,G) to R4.  This will 
> prevent the black-hole from being created in this scenario.
> 
>  
> Regards,
> James Huang
> 
> _______________________________________________
> pim mailing list
> pim@catarina.usc.edu
> http://catarina.usc.edu/mailman/listinfo/pim
> 
_______________________________________________
pim mailing list
pim@catarina.usc.edu
http://catarina.usc.edu/mailman/listinfo/pim


From pim-admin@catarina.usc.edu  Wed Apr 10 18:15:45 2002
Received: from catarina.usc.edu (catarina.usc.edu [204.57.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA03991
	for <pim-archive@lists.ietf.org>; Wed, 10 Apr 2002 18:15:44 -0400 (EDT)
Received: from catarina.usc.edu (localhost.localdomain [127.0.0.1])
	by catarina.usc.edu (8.11.6/8.11.6) with ESMTP id g3AMF2458427;
	Wed, 10 Apr 2002 15:15:02 -0700 (PDT)
	(envelope-from pim-admin@catarina.usc.edu)
Received: from external.zumanetworks.com (external.zumanetworks.com [64.161.185.13])
	by catarina.usc.edu (8.11.6/8.11.6) with SMTP id g3AMEg458409
	for <pim@catarina.usc.edu>; Wed, 10 Apr 2002 15:14:42 -0700 (PDT)
	(envelope-from jhuang@zumanetworks.com)
Received: from no.name.available by external.zumanetworks.com
          via smtpd (for catarina.usc.edu [204.57.0.1]) with SMTP; 10 Apr 2002 22:14:42 UT
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: [pim] Per-intf (S,G) assert state-machine
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
Message-ID: <E277CFA74A8D544A83F5314976B0451B7FB093@msmail.win.zumanetworks.com>
Thread-Topic: [pim] Per-intf (S,G) assert state-machine
Thread-Index: AcHgyvDcrtFiuKsERpG6SW7COCqpagACDFhgAAGUyHA=
From: "James Huang" <jhuang@zumanetworks.com>
To: "John Zwiebel" <John.Zwiebel@procket.com>, <pim@catarina.usc.edu>
Cc: "Reuben Sivan" <rsivan@zumanetworks.com>,
        "Junyu Mai" <jmai@zumanetworks.com>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by catarina.usc.edu id g3AMEg458409
Sender: pim-admin@catarina.usc.edu
Errors-To: pim-admin@catarina.usc.edu
X-BeenThere: pim@catarina.usc.edu
X-Mailman-Version: 2.0.8
Precedence: bulk
List-Help: <mailto:pim-request@catarina.usc.edu?subject=help>
List-Post: <mailto:pim@catarina.usc.edu>
List-Subscribe: <http://catarina.usc.edu/mailman/listinfo/pim>,
	<mailto:pim-request@catarina.usc.edu?subject=subscribe>
List-Id: <pim.catarina.usc.edu>
List-Unsubscribe: <http://catarina.usc.edu/mailman/listinfo/pim>,
	<mailto:pim-request@catarina.usc.edu?subject=unsubscribe>
List-Archive: <http://catarina.usc.edu/pipermail/pim/>
Date: Wed, 10 Apr 2002 15:14:40 -0700
Content-Transfer-Encoding: 8bit

See my comment below.

Regards,
James Huang

> -----Original Message-----
> From: John Zwiebel [mailto:John.Zwiebel@procket.com]
> Sent: Wednesday, April 10, 2002 2:25 PM
> To: James Huang; pim@catarina.usc.edu
> Cc: Reuben Sivan; Junyu Mai
> Subject: RE: [pim] Per-intf (S,G) assert state-machine
> 
> 
> 
> FWIW:
> If a router is recevinging an IGMPv3 report for a specific
> (S,G), I do not believe one should worry about data when
> setting the KAT on the last-hop router.  One could argue
> that unless S was in the SSM range that only data should
> determine the KAT, but then you will have a case where 
> state will be deleted and then recreated over and over every
> 3 minutes for (IMHO) no good reason.  I recognize that for
> non-SSM groups routers that are further upstream on the SPT will
> delete and reinstall the (S,G) resulting in up to a 60 second
> black-hole.  I submit that "if its important" this not happen,
> that it is an error for the host to send an IGMPv3 (S,G) report.
> However, for most video/audio uses: a) the user seldom joins 
> before the source is sending; b) migrating to IGMPv3 and 
> (S,G) reports is 'more important' than solving this 'interim
> problem'.
> 
> If router 5 has (S,G) state, this is -not- a turn-around problem.
> Since you have R5 setting the SPT bit R2 does not need to
> worry about identifying 'non-atomic' joins (PIM (*,G) joins
> without an (S,G,R) prune) with is a requirement to identify
> a router as a "turn-around" router.

After step(5), (S,G) KAT at R5 will time out.  So JoinDesired(S,G) will 
become FALSE.  So R5 will not update (S,G) KAT when it receives (S,G) traffic 
and JoinDesired(S,G) will remain FALSE.  After step(7) where host3 sends a igmp leave, 
it will become the classical turn-around router scenario except that R4 will also become
the AssertWinner in lan3 and will periodically send Assert(S,G) messages. The blackhole 
will be created the next time R4 sends the Assert(S,G) message.

> 
> R5 should not transition to assert loser.  Its IIF is on LAN3
> so it should never forward for the source so it should never
> participate in an assert (ie only a router that has an interface
> in the olist that sees an assert should care here).

After step (5) in my email, KeepAliveTimer(S,G) in R2, R4, and R5
will time out.  So JoinDesired(S,G) becomes FALSE at R5 and it will set its SPTbit
to 0. Now AssertTrackingDesired(S,G,I) become TRUE at R5, so R5 will track (S,G) asserts.

> 
> R5 does care about the assert because it needs to know when it
> can switch from the RPT to the SPT.  Since the IIF to both the
> RPT and SPT are the same, the only way it can be -sure- it received
> packets on the SPT is if it sees the assert.

When R5 receives the periodic Assert(S,G) message sent by R4, it will set 
its SPTbit(S,G) back to 1. 

> 
> Whether or not the SPT-bit is set the (S,G) KAT should be updated
> anytime R5 forwards a packet.  Since the only time one should see an
> assert on LAN3 is when there is a data packet, the KAT should be
> running.

(S,G) KAT at R5 is not updated by (S,G) traffic because after step(5) (S,G) KAT 
will time out, JoinDesired(S,G) will become FALSE.  So R5 will not update (S,G) KAT
when it receives (S,G) traffic.
 
> 
> Finally, even though the SPT-bit is not set on R5, there is no
> reason it should not be sending an (S,G) join toward the source
> and overriding any actions of R2 that might cause a black-hole.
> 
> The only thing the SPT-bit should do is enable sending an (S,G,R)
> prune from R5.
> 
> HOWEVER, if you want to implement updating the KAT when you see 
> the assert, you start the KAT, I doubt it will cause any
> interoperability
> problems.  

I beleive what I saw is a problem in the current spec. I want to make sure 
the spec gets updated if my observation is correct.

> 
> Just be sure that you don't assert when you see an assert.  Only 
> send an assert when you actually see data on an interface in the
> Olist. 
> 
> > -----Original Message-----
> > From: James Huang [mailto:jhuang@zumanetworks.com] 
> > Sent: Wednesday, April 10, 2002 1:05 PM
> > To: pim@catarina.usc.edu
> > Cc: Reuben Sivan; Junyu Mai
> > Subject: [pim] Per-intf (S,G) assert state-machine
> > 
> > 
> > Hi all,
> > 
> > The per-intf (S,G) assert state-machine will transition from 
> > the NoInfo state to the AssertLoser state when it receives a 
> > prefered assert with RPTbit clear and 
> > AssertTrackingDesired(S,G,I) == TRUE.  Also it will set 
> > SPTbit(S,G) to 1 if the Assert message is received from 
> RPF_intf(S).  
> > 
> > My question is "Should the state-machine also start the 
> > KeepAliveTimer(S,G) if the Assert message is received from 
> > RPF_intf(S)?".  Sptbit set to 1 while KeepAliveTimer not 
> > running doesn't seem to be a good state to me.  I have run 
> > into a scenario where this problem can cause a black-hole in 
> > (S,G) forwarding.
> > 
> > The scenario is as follows:
> > 
> > 
> > 
> >                         RP:225 *****
> >                                * 1 *
> >                                *****
> >                                  |
> >                                  |  lan1
> >                                  |
> >                                *****         =====  receiver
> >                                * 2 *---------= 3 =  (92.168.4.6, 
> >                                *****   lan2  =====   225.1.1.1)
> >                                  |                     
> >                                  |
> >                         lan3     |  
> >                -------------------------------------
> >                      |                        |
> >                      |                        |
> >               lan6   |                        |
> >        =====       *****                    *****
> >        = 8 =-------* 4 *                    * 5 *
> >        =====       *****                    *****
> >       receiver       |                        |
> >     (192.168.4.6,    | lan4              lan5 |
> >      225.1.1.1)      |                        |
> >                    =====                    =====
> >                    = 6 =                    = 7 =
> >                    =====                    =====
> >                    source                   receiver 
> >                                           (*,225.1.1.1)
> > 
> > 
> > 
> > (1) host 7 sends a igmp (*,G) join
> > (2) host 8 sends a igmp (S,G) join
> > (3) host 3 sends a igmp (S,G) join
> > (4) host 6 pings 225.1.1.1 a few times
> > (5) wait until the KeepAliveTimer times out in router 2 and router 4
> > (6) host 6 pings 225.1.1.1 continuously
> > (7) host 8 sends a igmp (S,G) leave
> > 
> > Assuming that router 5 will not switch from the PRT tree to the SPT tree when 
> > it call CheckSwitchtoSpt(S,G).
> >
> > After step(7), this has become the classical turn-around 
> > router scenario.  However, R4 has also become the (S,G) 
> > Assert Winner for lan3.
> > When R4's Assert timer expires, it will send a periodic 
> > Assert(S,G) message.  When R5 receives the Assert message, 
> > its per-intf (S,G) Assert state-machine will transition from 
> > the NoINfo state to the AssertLoser state.  Also R5 will set 
> > SPTbit(S,G) to 1.  This will change 
> > AssertTrackingDesired(S,G,I) at R5 to False and so R5's 
> > Assert state-machine will be moved back to the NoInfo state.  
> > Setting Sptbit(S,G) to 1 will make PruneDesired(S,G,rpt) at 
> > R5 to become true.  So R5 will send a Prune(S,G,rpt) to R2.  
> > When R2 receives the Prune(S,G,rpt) from R5, its 
> > inherited_olist(S,G) becomes NULL.  So JoinDesired(S,G) 
> > becomes False at R2 and it will send a prune(S,G) to R4.  
> > From now on, R4 will no longer forward (S,G) traffic to lan3 
> > and a black-hole is created.
> > 
> > This problem can be fixed by setting KeepAliveTimer(S,G) at 
> > R5 when it receives the Assert(S,G) message from R4.  With 
> > this fix, R5 has both SPTbit(S,G) set to 1 and the 
> > KeepAliveTimer(S,G) running.  So it will send a 
> > Prune(S,G,rpt) to R2 and a Join(S,G) to R4.  This will 
> > prevent the black-hole from being created in this scenario.
> > 
> >  
> > Regards,
> > James Huang
> > 
> > _______________________________________________
> > pim mailing list
> > pim@catarina.usc.edu
> > http://catarina.usc.edu/mailman/listinfo/pim
> > 
> 
_______________________________________________
pim mailing list
pim@catarina.usc.edu
http://catarina.usc.edu/mailman/listinfo/pim


From pim-admin@catarina.usc.edu  Wed Apr 10 19:02:54 2002
Received: from catarina.usc.edu (catarina.usc.edu [204.57.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA04849
	for <pim-archive@lists.ietf.org>; Wed, 10 Apr 2002 19:02:53 -0400 (EDT)
Received: from catarina.usc.edu (localhost.localdomain [127.0.0.1])
	by catarina.usc.edu (8.11.6/8.11.6) with ESMTP id g3AN23459302;
	Wed, 10 Apr 2002 16:02:03 -0700 (PDT)
	(envelope-from pim-admin@catarina.usc.edu)
Received: from dmz2.procket.com (dmz2.procket.com [65.174.124.37])
	by catarina.usc.edu (8.11.6/8.11.6) with ESMTP id g3AN15459280
	for <pim@catarina.usc.edu>; Wed, 10 Apr 2002 16:01:06 -0700 (PDT)
	(envelope-from John.Zwiebel@procket.com)
Received: from miata.procket.com (miata.procket.com [65.174.124.5])
	by dmz2.procket.com (Postfix) with ESMTP
	id 8138434434; Wed, 10 Apr 2002 16:05:16 -0700 (PDT)
Received: from EXCHANGE0-0.na.procket.com (exchange0b.na.procket.com [10.1.7.8])
	by miata.procket.com (8.12.1/8.12.1) with ESMTP id g3AN10vM020971;
	Wed, 10 Apr 2002 16:01:00 -0700 (PDT)
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Subject: RE: [pim] Per-intf (S,G) assert state-machine
Message-ID: <D2EC481073504E498A8DB9C0687E8CAF01842613@EXCHANGE0-0.na.procket.com>
Thread-Topic: [pim] Per-intf (S,G) assert state-machine
Thread-Index: AcHgyvDcrtFiuKsERpG6SW7COCqpagACDFhgAAGUyHAAAZQmYA==
From: "John Zwiebel" <John.Zwiebel@procket.com>
To: "James Huang" <jhuang@zumanetworks.com>, <pim@catarina.usc.edu>
Cc: "Reuben Sivan" <rsivan@zumanetworks.com>,
        "Junyu Mai" <jmai@zumanetworks.com>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by catarina.usc.edu id g3AN15459280
Sender: pim-admin@catarina.usc.edu
Errors-To: pim-admin@catarina.usc.edu
X-BeenThere: pim@catarina.usc.edu
X-Mailman-Version: 2.0.8
Precedence: bulk
List-Help: <mailto:pim-request@catarina.usc.edu?subject=help>
List-Post: <mailto:pim@catarina.usc.edu>
List-Subscribe: <http://catarina.usc.edu/mailman/listinfo/pim>,
	<mailto:pim-request@catarina.usc.edu?subject=subscribe>
List-Id: <pim.catarina.usc.edu>
List-Unsubscribe: <http://catarina.usc.edu/mailman/listinfo/pim>,
	<mailto:pim-request@catarina.usc.edu?subject=unsubscribe>
List-Archive: <http://catarina.usc.edu/pipermail/pim/>
Date: Wed, 10 Apr 2002 16:01:00 -0700
Content-Transfer-Encoding: 8bit


First: I should complement you on clearly stating
the problem.

Basically, if the KAT is expired on R5, (S,G) state
should have been deleted.  All of the other problems
go away.

Also, IGMPv3 and SSM behavior will cause you problems
if you don't take into account the differences, which
should be easy to overcome.

> -----Original Message-----
> From: James Huang [mailto:jhuang@zumanetworks.com] 
> 
> See my comment below.
> 
> 
> After step(5), (S,G) KAT at R5 will time out.  

If the KAT has expired, why does (S,G) state exist on
R5?  It should have been deleted.  If "JoinDesired"
is false, why are you maintaining (S,G) state in that
router?  

Then when the next mpacket is received on the (*,G)
R5 should create (S,G) state and trigger a join toward
the source.

FWIW: an implementation -may- choose to keep (S,G)
state on a router that just sees packets going by and
if I had my way, it would.  In such a case JoinDesired"
would be FALSE as you suggest, but then (*,G) would 
also be FALSE.

> So R5 will not update (S,G) KAT when it 
> receives (S,G) traffic 
> and JoinDesired(S,G) will remain FALSE.  After step(7) where 
> host3 sends a igmp leave, 
> it will become the classical turn-around router scenario 
> except that R4 will also become
> the AssertWinner in lan3 and will periodically send 
> Assert(S,G) messages. The blackhole 
> will be created the next time R4 sends the Assert(S,G) message.

The -only- way R3 can become a turnaround router is if R5
is configured to never join to the shortest-path.  Anything
else is -not- a turnaround router.  Since I invented the
term, I should know.  ;-)

Also FWIW: the asserts that will happen in this topology
will be between the RPT and the SPT.  I do not believe
the spec recommends sending a periodic assert in such a
case, and even if it does -- I wouldn't.  Doing so doesn't
buy you anything.

> 
> > 
> > R5 should not transition to assert loser.  Its IIF is on LAN3
> > so it should never forward for the source so it should never
> > participate in an assert (ie only a router that has an interface
> > in the olist that sees an assert should care here).
> 
> After step (5) in my email, KeepAliveTimer(S,G) in R2, R4, and R5
> will time out.  So JoinDesired(S,G) becomes FALSE at R5 and 
> it will set its SPTbit
> to 0. Now AssertTrackingDesired(S,G,I) become TRUE at R5, so 
> R5 will track (S,G) asserts.

Again, if the KAT has expired, (S,G) state should not exist on
R5 so nothing else matters.

>
> > R5 does care about the assert because it needs to know when it
> > can switch from the RPT to the SPT.  Since the IIF to both the
> > RPT and SPT are the same, the only way it can be -sure- it received
> > packets on the SPT is if it sees the assert.
> 
> When R5 receives the periodic Assert(S,G) message sent by R4, 
> it will set 
> its SPTbit(S,G) back to 1. 

If the KAT expired on R5 why didn't it expire on R4?  And
why is R4 sending an assert for a source that has expired.

Perhaps its the IGMPv3 report that is causing the problem?
Since you are apparently updating state on R4 because of that
report.  Mixing SSM and standard PIM is going to get you 
into trouble in this case.

Sending the periodic assert shouldn't update the (S,G) on
R5 so again, why is R5 maintaing that state.  
> 
> > 
> > Whether or not the SPT-bit is set the (S,G) KAT should be updated
> > anytime R5 forwards a packet.  Since the only time one should see an
> > assert on LAN3 is when there is a data packet, the KAT should be
> > running.
> 
> (S,G) KAT at R5 is not updated by (S,G) traffic because after 
> step(5) (S,G) KAT 
> will time out, JoinDesired(S,G) will become FALSE.  So R5 
> will not update (S,G) KAT
> when it receives (S,G) traffic.
>  
> > 
> > Finally, even though the SPT-bit is not set on R5, there is no
> > reason it should not be sending an (S,G) join toward the source
> > and overriding any actions of R2 that might cause a black-hole.
> > 
> > The only thing the SPT-bit should do is enable sending an (S,G,R)
> > prune from R5.
> > 
> > HOWEVER, if you want to implement updating the KAT when you see 
> > the assert, you start the KAT, I doubt it will cause any
> > interoperability
> > problems.  
> 
> I beleive what I saw is a problem in the current spec. I want 
> to make sure 
> the spec gets updated if my observation is correct.
> 
> >
_______________________________________________
pim mailing list
pim@catarina.usc.edu
http://catarina.usc.edu/mailman/listinfo/pim


From pim-admin@catarina.usc.edu  Wed Apr 10 19:27:49 2002
Received: from catarina.usc.edu (catarina.usc.edu [204.57.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA05096
	for <pim-archive@lists.ietf.org>; Wed, 10 Apr 2002 19:27:48 -0400 (EDT)
Received: from catarina.usc.edu (localhost.localdomain [127.0.0.1])
	by catarina.usc.edu (8.11.6/8.11.6) with ESMTP id g3ANR8459717;
	Wed, 10 Apr 2002 16:27:08 -0700 (PDT)
	(envelope-from pim-admin@catarina.usc.edu)
Received: from external.zumanetworks.com (external.zumanetworks.com [64.161.185.13])
	by catarina.usc.edu (8.11.6/8.11.6) with SMTP id g3ANQw459705
	for <pim@catarina.usc.edu>; Wed, 10 Apr 2002 16:26:59 -0700 (PDT)
	(envelope-from jhuang@zumanetworks.com)
Received: from no.name.available by external.zumanetworks.com
          via smtpd (for catarina.usc.edu [204.57.0.1]) with SMTP; 10 Apr 2002 23:26:58 UT
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: [pim] Per-intf (S,G) assert state-machine
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
Message-ID: <E277CFA74A8D544A83F5314976B0451B7FB094@msmail.win.zumanetworks.com>
Thread-Topic: [pim] Per-intf (S,G) assert state-machine
Thread-Index: AcHgyvDcrtFiuKsERpG6SW7COCqpagACDFhgAAGUyHAAAZQmYAABJpKw
From: "James Huang" <jhuang@zumanetworks.com>
To: "John Zwiebel" <John.Zwiebel@procket.com>, <pim@catarina.usc.edu>
Cc: "Reuben Sivan" <rsivan@zumanetworks.com>,
        "Junyu Mai" <jmai@zumanetworks.com>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by catarina.usc.edu id g3ANQw459705
Sender: pim-admin@catarina.usc.edu
Errors-To: pim-admin@catarina.usc.edu
X-BeenThere: pim@catarina.usc.edu
X-Mailman-Version: 2.0.8
Precedence: bulk
List-Help: <mailto:pim-request@catarina.usc.edu?subject=help>
List-Post: <mailto:pim@catarina.usc.edu>
List-Subscribe: <http://catarina.usc.edu/mailman/listinfo/pim>,
	<mailto:pim-request@catarina.usc.edu?subject=subscribe>
List-Id: <pim.catarina.usc.edu>
List-Unsubscribe: <http://catarina.usc.edu/mailman/listinfo/pim>,
	<mailto:pim-request@catarina.usc.edu?subject=unsubscribe>
List-Archive: <http://catarina.usc.edu/pipermail/pim/>
Date: Wed, 10 Apr 2002 16:26:55 -0700
Content-Transfer-Encoding: 8bit

Hi John,

In my company's pim-sm implementaion, (S,G) in R5 is not deleted after 
its KAT expires because the Upstream (S,G,rpt) state-machine is in the 
NotPruned state (instead of the RPTNotJoined(G) state).  Is it O.K. to 
delete the (S,G) entry in this case (KAT expired, all downstream intf 
are in the NoInfo state, the Upstream (S,G) state-machine is in the NotJoined 
state, the Register state-machine is in the NoInfo state, and the 
Upstream (S,G,rpt) state-machine is in the NotPruned state)?

Another issue is even if R5 deleted its (S,G) entry, its AssertTrackingDesired(S,G,I)
is still TRUE (RPF_intf(RP) == I AND JoinDesired(*,G) == TRUE AND SPTbit(S,G) == FALSE).
So when it receives a Assert(S,G) message from R4, it will recreate the (S,G) entry and
the problem will still occur.
 
Thanks,
James Huang


> -----Original Message-----
> From: John Zwiebel [mailto:John.Zwiebel@procket.com]
> Sent: Wednesday, April 10, 2002 4:01 PM
> To: James Huang; pim@catarina.usc.edu
> Cc: Reuben Sivan; Junyu Mai
> Subject: RE: [pim] Per-intf (S,G) assert state-machine
> 
> 
> 
> First: I should complement you on clearly stating
> the problem.
> 
> Basically, if the KAT is expired on R5, (S,G) state
> should have been deleted.  All of the other problems
> go away.
> 
> Also, IGMPv3 and SSM behavior will cause you problems
> if you don't take into account the differences, which
> should be easy to overcome.
> 
> > -----Original Message-----
> > From: James Huang [mailto:jhuang@zumanetworks.com] 
> > 
> > See my comment below.
> > 
> > 
> > After step(5), (S,G) KAT at R5 will time out.  
> 
> If the KAT has expired, why does (S,G) state exist on
> R5?  It should have been deleted.  If "JoinDesired"
> is false, why are you maintaining (S,G) state in that
> router?  
> 
> Then when the next mpacket is received on the (*,G)
> R5 should create (S,G) state and trigger a join toward
> the source.
> 
> FWIW: an implementation -may- choose to keep (S,G)
> state on a router that just sees packets going by and
> if I had my way, it would.  In such a case JoinDesired"
> would be FALSE as you suggest, but then (*,G) would 
> also be FALSE.
> 
> > So R5 will not update (S,G) KAT when it 
> > receives (S,G) traffic 
> > and JoinDesired(S,G) will remain FALSE.  After step(7) where 
> > host3 sends a igmp leave, 
> > it will become the classical turn-around router scenario 
> > except that R4 will also become
> > the AssertWinner in lan3 and will periodically send 
> > Assert(S,G) messages. The blackhole 
> > will be created the next time R4 sends the Assert(S,G) message.
> 
> The -only- way R3 can become a turnaround router is if R5
> is configured to never join to the shortest-path.  Anything
> else is -not- a turnaround router.  Since I invented the
> term, I should know.  ;-)
> 
> Also FWIW: the asserts that will happen in this topology
> will be between the RPT and the SPT.  I do not believe
> the spec recommends sending a periodic assert in such a
> case, and even if it does -- I wouldn't.  Doing so doesn't
> buy you anything.
> 
> > 
> > > 
> > > R5 should not transition to assert loser.  Its IIF is on LAN3
> > > so it should never forward for the source so it should never
> > > participate in an assert (ie only a router that has an interface
> > > in the olist that sees an assert should care here).
> > 
> > After step (5) in my email, KeepAliveTimer(S,G) in R2, R4, and R5
> > will time out.  So JoinDesired(S,G) becomes FALSE at R5 and 
> > it will set its SPTbit
> > to 0. Now AssertTrackingDesired(S,G,I) become TRUE at R5, so 
> > R5 will track (S,G) asserts.
> 
> Again, if the KAT has expired, (S,G) state should not exist on
> R5 so nothing else matters.
> 
> >
> > > R5 does care about the assert because it needs to know when it
> > > can switch from the RPT to the SPT.  Since the IIF to both the
> > > RPT and SPT are the same, the only way it can be -sure- 
> it received
> > > packets on the SPT is if it sees the assert.
> > 
> > When R5 receives the periodic Assert(S,G) message sent by R4, 
> > it will set 
> > its SPTbit(S,G) back to 1. 
> 
> If the KAT expired on R5 why didn't it expire on R4?  And
> why is R4 sending an assert for a source that has expired.
> 
> Perhaps its the IGMPv3 report that is causing the problem?
> Since you are apparently updating state on R4 because of that
> report.  Mixing SSM and standard PIM is going to get you 
> into trouble in this case.
> 
> Sending the periodic assert shouldn't update the (S,G) on
> R5 so again, why is R5 maintaing that state.  
> > 
> > > 
> > > Whether or not the SPT-bit is set the (S,G) KAT should be updated
> > > anytime R5 forwards a packet.  Since the only time one 
> should see an
> > > assert on LAN3 is when there is a data packet, the KAT should be
> > > running.
> > 
> > (S,G) KAT at R5 is not updated by (S,G) traffic because after 
> > step(5) (S,G) KAT 
> > will time out, JoinDesired(S,G) will become FALSE.  So R5 
> > will not update (S,G) KAT
> > when it receives (S,G) traffic.
> >  
> > > 
> > > Finally, even though the SPT-bit is not set on R5, there is no
> > > reason it should not be sending an (S,G) join toward the source
> > > and overriding any actions of R2 that might cause a black-hole.
> > > 
> > > The only thing the SPT-bit should do is enable sending an (S,G,R)
> > > prune from R5.
> > > 
> > > HOWEVER, if you want to implement updating the KAT when you see 
> > > the assert, you start the KAT, I doubt it will cause any
> > > interoperability
> > > problems.  
> > 
> > I beleive what I saw is a problem in the current spec. I want 
> > to make sure 
> > the spec gets updated if my observation is correct.
> > 
> > >
> 
_______________________________________________
pim mailing list
pim@catarina.usc.edu
http://catarina.usc.edu/mailman/listinfo/pim


From pim-admin@catarina.usc.edu  Wed Apr 10 20:33:53 2002
Received: from catarina.usc.edu (catarina.usc.edu [204.57.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA06074
	for <pim-archive@lists.ietf.org>; Wed, 10 Apr 2002 20:33:52 -0400 (EDT)
Received: from catarina.usc.edu (localhost.localdomain [127.0.0.1])
	by catarina.usc.edu (8.11.6/8.11.6) with ESMTP id g3B0X1460859;
	Wed, 10 Apr 2002 17:33:01 -0700 (PDT)
	(envelope-from pim-admin@catarina.usc.edu)
Received: from dmz2.procket.com (dmz2.procket.com [65.174.124.37])
	by catarina.usc.edu (8.11.6/8.11.6) with ESMTP id g3B0W6460844
	for <pim@catarina.usc.edu>; Wed, 10 Apr 2002 17:32:06 -0700 (PDT)
	(envelope-from John.Zwiebel@procket.com)
Received: from miata.procket.com (miata.procket.com [65.174.124.5])
	by dmz2.procket.com (Postfix) with ESMTP
	id 0E76F34436; Wed, 10 Apr 2002 17:36:14 -0700 (PDT)
Received: from EXCHANGE0-0.na.procket.com (exchange0b.na.procket.com [10.1.7.8])
	by miata.procket.com (8.12.1/8.12.1) with ESMTP id g3B0VvvM028848;
	Wed, 10 Apr 2002 17:31:57 -0700 (PDT)
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Subject: RE: [pim] Per-intf (S,G) assert state-machine
Message-ID: <D2EC481073504E498A8DB9C0687E8CAF01842614@EXCHANGE0-0.na.procket.com>
Thread-Topic: [pim] Per-intf (S,G) assert state-machine
Thread-Index: AcHgyvDcrtFiuKsERpG6SW7COCqpagACDFhgAAGUyHAAAZQmYAABJpKwAAIL9YA=
From: "John Zwiebel" <John.Zwiebel@procket.com>
To: "James Huang" <jhuang@zumanetworks.com>, <pim@catarina.usc.edu>
Cc: "Reuben Sivan" <rsivan@zumanetworks.com>,
        "Junyu Mai" <jmai@zumanetworks.com>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by catarina.usc.edu id g3B0W6460844
Sender: pim-admin@catarina.usc.edu
Errors-To: pim-admin@catarina.usc.edu
X-BeenThere: pim@catarina.usc.edu
X-Mailman-Version: 2.0.8
Precedence: bulk
List-Help: <mailto:pim-request@catarina.usc.edu?subject=help>
List-Post: <mailto:pim@catarina.usc.edu>
List-Subscribe: <http://catarina.usc.edu/mailman/listinfo/pim>,
	<mailto:pim-request@catarina.usc.edu?subject=subscribe>
List-Id: <pim.catarina.usc.edu>
List-Unsubscribe: <http://catarina.usc.edu/mailman/listinfo/pim>,
	<mailto:pim-request@catarina.usc.edu?subject=unsubscribe>
List-Archive: <http://catarina.usc.edu/pipermail/pim/>
Date: Wed, 10 Apr 2002 17:31:57 -0700
Content-Transfer-Encoding: 8bit



> -----Original Message-----
> Hi John,
> 
> In my company's pim-sm implementaion, (S,G) in R5 is not 
> deleted after 
> its KAT expires because the Upstream (S,G,rpt) state-machine 
> is in the 
> NotPruned state (instead of the RPTNotJoined(G) state).  Is 
> it O.K. to 
> delete the (S,G) entry in this case (KAT expired, all downstream intf 
> are in the NoInfo state, the Upstream (S,G) state-machine is 
> in the NotJoined 
> state, the Register state-machine is in the NoInfo state, and the 
> Upstream (S,G,rpt) state-machine is in the NotPruned state)?

FWIW: if the KAT is expired should alone cause you to delete state.
Nothing else should matter for maintaining (S,G) state.  (S,G,R)
state is, however, updated by receipt of the (S,G,R) prune.  It 
may not be clear in the spec, but it is the Expiry Timer in 4.4.4
page 33.

NOTE: you -may- want to update the KAT when you just see a packet
on an interface rather than forward it. (Hint, hint -- wink, wink)

> 
> Another issue is even if R5 deleted its (S,G) entry, its 
> AssertTrackingDesired(S,G,I)
> is still TRUE (RPF_intf(RP) == I AND JoinDesired(*,G) == TRUE 
> AND SPTbit(S,G) == FALSE).

If you delete the (S,G) why are you maintaining this other state?

> So when it receives a Assert(S,G) message from R4, it will 
> recreate the (S,G) entry and
> the problem will still occur.

In 'standard PIM' (S,G) is created by:
  -- data
  -- and (S,G) join

nothing else.

In 'standard PIM' (S,G) KAT is updated by data -- nothing else.

In SSM-PIM (S,G) KAT is updated by (S,G) joins -- nothing else.

Note that the conflict between standard and SSM PIM does not
prevent reliable delivery of data.  However it -may- result in
a blackhole of up to 60 seconds if the receiver joins more than 
3 minutes before the source starts sending and you are using 
'standard PIM' in your network.

So to repeat my latest "kick", -ALL- multicast sources should
advertise their source address in -ALL- sdp sessions so that
an IGMPv3 capable receiver can join directly to the source.  
There may be some exceptions to this in the enterprise environment
or in some special applications.

Just to be clear, yes I am advocating that -receivers- be provided
the option to use SSM over standard PIM in -all- multicast group
ranges.   HOWEVER, networks should still be configured to support
SSM only in the 232/8 range.

The sooner SSM is deployed the sooner we can scrap MSDP.  It is
imperitive MSDP be 'decommissioned' for use between ISPs before
the use of multicast becomes too great in the internet.


>  
> Thanks,
> James Huang
> > 
_______________________________________________
pim mailing list
pim@catarina.usc.edu
http://catarina.usc.edu/mailman/listinfo/pim


From pim-admin@catarina.usc.edu  Thu Apr 11 15:49:05 2002
Received: from catarina.usc.edu (catarina.usc.edu [204.57.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11770
	for <pim-archive@odin.ietf.org>; Thu, 11 Apr 2002 15:49:01 -0400 (EDT)
Received: from catarina.usc.edu (localhost.localdomain [127.0.0.1])
	by catarina.usc.edu (8.11.6/8.11.6) with ESMTP id g3BJm3478063;
	Thu, 11 Apr 2002 12:48:06 -0700 (PDT)
	(envelope-from pim-admin@catarina.usc.edu)
Received: from external.zumanetworks.com (external.zumanetworks.com [64.161.185.13])
	by catarina.usc.edu (8.11.6/8.11.6) with SMTP id g3BJle478044
	for <pim@catarina.usc.edu>; Thu, 11 Apr 2002 12:47:40 -0700 (PDT)
	(envelope-from jhuang@zumanetworks.com)
Received: from no.name.available by external.zumanetworks.com
          via smtpd (for catarina.usc.edu [204.57.0.1]) with SMTP; 11 Apr 2002 19:47:40 UT
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
Message-ID: <E277CFA74A8D544A83F5314976B0451B7FB095@msmail.win.zumanetworks.com>
Thread-Topic: Per-intf (S,G) assert state-machine
Thread-Index: AcHhkbzA/x6qkbITR+Cp+NLRKTkPWw==
From: "James Huang" <jhuang@zumanetworks.com>
To: <pim@catarina.usc.edu>
Cc: "Reuben Sivan" <rsivan@zumanetworks.com>,
        "Junyu Mai" <jmai@zumanetworks.com>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by catarina.usc.edu id g3BJle478044
Subject: [pim] Per-intf (S,G) assert state-machine
Sender: pim-admin@catarina.usc.edu
Errors-To: pim-admin@catarina.usc.edu
X-BeenThere: pim@catarina.usc.edu
X-Mailman-Version: 2.0.8
Precedence: bulk
List-Help: <mailto:pim-request@catarina.usc.edu?subject=help>
List-Post: <mailto:pim@catarina.usc.edu>
List-Subscribe: <http://catarina.usc.edu/mailman/listinfo/pim>,
	<mailto:pim-request@catarina.usc.edu?subject=subscribe>
List-Id: <pim.catarina.usc.edu>
List-Unsubscribe: <http://catarina.usc.edu/mailman/listinfo/pim>,
	<mailto:pim-request@catarina.usc.edu?subject=unsubscribe>
List-Archive: <http://catarina.usc.edu/pipermail/pim/>
Date: Thu, 11 Apr 2002 12:47:39 -0700
Content-Transfer-Encoding: 8bit

Hi all,

After more thoughts on the issue that I raised in my previous emails, 
I still believe there is a problem with the (S,G) assert state-machine.

The problem is as follows:
Suppose initially the state-machine is in the NoInfo state and 
AssertTrackingDesired(S,G,I)== TRUE. When it receives a prefered (S,G) assert 
message with RPT clear from intf I, it will transition to the AssertLoser state.
Additionally, if (I == RPF_intf(S)), it will set SPTbit(S,G) to 1.
Now if JoinDesired(S,G) is FALSE, we have created a bad (S,G) state where SPTbit(S,G)
is set to 1 while JoinDesired(S,G) is FALSE.  This bad state can prevent this router 
from forwarding future (S,G) traffic (see sec 4.2 Data Forwarding Rules).

I think the fix is to set SPTbit(S,G) to 1 only if (I == RPF_intf(S) && JoinDesired(S,G) == TRUE).

What do you think?

Regards,
James Huang
_______________________________________________
pim mailing list
pim@catarina.usc.edu
http://catarina.usc.edu/mailman/listinfo/pim


From pim-admin@catarina.usc.edu  Thu Apr 11 17:40:00 2002
Received: from catarina.usc.edu (catarina.usc.edu [204.57.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA16047
	for <pim-archive@odin.ietf.org>; Thu, 11 Apr 2002 17:39:57 -0400 (EDT)
Received: from catarina.usc.edu (localhost.localdomain [127.0.0.1])
	by catarina.usc.edu (8.11.6/8.11.6) with ESMTP id g3BLd1479817;
	Thu, 11 Apr 2002 14:39:01 -0700 (PDT)
	(envelope-from pim-admin@catarina.usc.edu)
Received: from gateway.ipinfusion.com (gt.ipinfusion.com [209.11.132.18] (may be forged))
	by catarina.usc.edu (8.11.6/8.11.6) with ESMTP id g3BLcw479806
	for <pim@catarina.usc.edu>; Thu, 11 Apr 2002 14:38:58 -0700 (PDT)
	(envelope-from rishabh@ipinfusion.com)
Received: from ipinfusion.com ([10.10.0.92])
	by gateway.ipinfusion.com (8.11.0/8.11.0) with ESMTP id g3BLbsC21676
	for <pim@catarina.usc.edu>; Thu, 11 Apr 2002 14:37:54 -0700
Message-ID: <3CB60221.8E2919AB@ipinfusion.com>
From: Rishabh Parekh <rishabh@ipinfusion.com>
Organization: IP Infusion Inc
X-Mailer: Mozilla 4.78 [en] (X11; U; Linux 2.4.9-31 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: pim@catarina.usc.edu
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: [pim] Questions on Assert Message handling
Sender: pim-admin@catarina.usc.edu
Errors-To: pim-admin@catarina.usc.edu
X-BeenThere: pim@catarina.usc.edu
X-Mailman-Version: 2.0.8
Precedence: bulk
List-Help: <mailto:pim-request@catarina.usc.edu?subject=help>
List-Post: <mailto:pim@catarina.usc.edu>
List-Subscribe: <http://catarina.usc.edu/mailman/listinfo/pim>,
	<mailto:pim-request@catarina.usc.edu?subject=subscribe>
List-Id: <pim.catarina.usc.edu>
List-Unsubscribe: <http://catarina.usc.edu/mailman/listinfo/pim>,
	<mailto:pim-request@catarina.usc.edu?subject=unsubscribe>
List-Archive: <http://catarina.usc.edu/pipermail/pim/>
Date: Thu, 11 Apr 2002 14:37:37 -0700
Content-Transfer-Encoding: 7bit

Hi,
I have a few questions about handling received Assert messages as
specified in the new draft-05.

The section 4.6.2 on (*,G) Assert Message State Machine has two
paragraphs in bold characters. The paragraphs can be summarized as
below:
A) An Assert Message must be first matched against the (S,G) Assert
State Machine before considering that Assert message for the (*,G)
Assert State Machine.
B) After applying an Assert Message to the (S,G) Assert State Machine,
it should NOT be applied to the (*,G) Assert State Machine if the (S,G)
Assert State Machine for the "relevant" S and G is NOT in the "No Info"
state.
C) After applying an Assert Message to the (S,G) Assert State Machine,
it should NOT be applied to the (*,G) Assert State Machine if that
message has caused ANY state change in the (S,G) Assert State Machine.

Now, from section 4.10 of the draft-05, I deduce that there are 3 types
Assert Messages that can be received.
1) A "pure" (*,G) Assert Message with the R-bit set and the source
address of INADDR_ANY
2) A "data-triggered" (*,G) Assert Message with R-bit set and the source
address set to S.
3) A "pure" (S,G) Assert Message with R-bit clear and the source address
set to S.

My questions are as follows:
a) In case a "pure" (*,G) Assert Message is received, how do I apply the
message to the (S,G) Assert State Machine? Do I have to traverse the TIB
and apply this message to the TIB entries for all sources S of group G?
If I have to do a traversal, then is it true that if the above condition
A) or B) is true for any source S for group G, then I cannot apply this
"pure" (*,G) Assert Message to the (*,G) Assert State Machine? What is
the "relevant" source S in this case?

b) In case of a "data-triggered" (*,G) Assert Message, should I apply
this message only to the (S,G) Assert State Machine for the source S in
the message? Or, do I have to traverse the TIB for all the sources for
group G?

Regards,
Rishabh Parekh.



_______________________________________________
pim mailing list
pim@catarina.usc.edu
http://catarina.usc.edu/mailman/listinfo/pim


From pim-admin@catarina.usc.edu  Tue Apr 16 12:53:54 2002
Received: from catarina.usc.edu (catarina.usc.edu [204.57.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA18773
	for <pim-archive@odin.ietf.org>; Tue, 16 Apr 2002 12:53:53 -0400 (EDT)
Received: from catarina.usc.edu (localhost.localdomain [127.0.0.1])
	by catarina.usc.edu (8.11.6/8.11.6) with ESMTP id g3GGqA475946;
	Tue, 16 Apr 2002 09:52:10 -0700 (PDT)
	(envelope-from pim-admin@catarina.usc.edu)
Received: from prattle.redback.com (prattle.redback.com [155.53.12.9])
	by catarina.usc.edu (8.11.6/8.11.6) with ESMTP id g3GGpR475925
	for <pim@catarina.usc.edu>; Tue, 16 Apr 2002 09:51:27 -0700 (PDT)
	(envelope-from lwei@redback.com)
Received: from yoo-hoo.redback.com (yoo-hoo.redback.com [155.53.12.43])
	by prattle.redback.com (Postfix) with ESMTP
	id D501A1B8EE7; Tue, 16 Apr 2002 09:51:16 -0700 (PDT)
Received: (from lwei@localhost)
	by yoo-hoo.redback.com (8.9.3-LCCHA/8.9.3/null redback solaris client) id JAA23229;
	Tue, 16 Apr 2002 09:51:16 -0700 (PDT)
Message-Id: <200204161651.JAA23229@yoo-hoo.redback.com>
From: Liming Wei <lwei@redback.com>
To: pim@catarina.usc.edu
Cc: pusateri@juniper.net
Reply-To: lwei@redback.com
Subject: [pim] Request for agenda items for Yokohama meeting
Sender: pim-admin@catarina.usc.edu
Errors-To: pim-admin@catarina.usc.edu
X-BeenThere: pim@catarina.usc.edu
X-Mailman-Version: 2.0.8
Precedence: bulk
List-Help: <mailto:pim-request@catarina.usc.edu?subject=help>
List-Post: <mailto:pim@catarina.usc.edu>
List-Subscribe: <http://catarina.usc.edu/mailman/listinfo/pim>,
	<mailto:pim-request@catarina.usc.edu?subject=subscribe>
List-Id: <pim.catarina.usc.edu>
List-Unsubscribe: <http://catarina.usc.edu/mailman/listinfo/pim>,
	<mailto:pim-request@catarina.usc.edu?subject=unsubscribe>
List-Archive: <http://catarina.usc.edu/pipermail/pim/>
Date: Tue, 16 Apr 2002 09:51:16 -0700 (PDT)

Hello everyone,

If you have any agenda items for the Yokohama WG meeting, please
post it here or send it to me.

I'd recommend to do this earlier even if the work is still in progress.
Please indicate how much time you need too.

 Thanks,
-Liming & Tom
_______________________________________________
pim mailing list
pim@catarina.usc.edu
http://catarina.usc.edu/mailman/listinfo/pim


From pim-admin@catarina.usc.edu  Wed Apr 17 19:43:19 2002
Received: from catarina.usc.edu (catarina.usc.edu [204.57.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA11117
	for <pim-archive@lists.ietf.org>; Wed, 17 Apr 2002 19:43:16 -0400 (EDT)
Received: from catarina.usc.edu (localhost.localdomain [127.0.0.1])
	by catarina.usc.edu (8.11.6/8.11.6) with ESMTP id g3HNgD404354;
	Wed, 17 Apr 2002 16:42:13 -0700 (PDT)
	(envelope-from pim-admin@catarina.usc.edu)
Received: from external.zumanetworks.com ([64.161.185.13])
	by catarina.usc.edu (8.11.6/8.11.6) with SMTP id g3HNex404332
	for <pim@catarina.usc.edu>; Wed, 17 Apr 2002 16:41:00 -0700 (PDT)
	(envelope-from jhuang@zumanetworks.com)
Received: from no.name.available by external.zumanetworks.com
          via smtpd (for catarina.usc.edu [204.57.0.1]) with SMTP; 17 Apr 2002 23:40:59 UT
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Message-ID: <E277CFA74A8D544A83F5314976B0451B7FB097@msmail.win.zumanetworks.com>
Thread-Topic: AssertTrackingDesired(S,G,I)
Thread-Index: AcHmaVOt5MUokhKOQ7CP0X0QVaOzTQ==
From: "James Huang" <jhuang@zumanetworks.com>
To: <pim@catarina.usc.edu>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by catarina.usc.edu id g3HNex404332
Subject: [pim] AssertTrackingDesired(S,G,I)
Sender: pim-admin@catarina.usc.edu
Errors-To: pim-admin@catarina.usc.edu
X-BeenThere: pim@catarina.usc.edu
X-Mailman-Version: 2.0.8
Precedence: bulk
List-Help: <mailto:pim-request@catarina.usc.edu?subject=help>
List-Post: <mailto:pim@catarina.usc.edu>
List-Subscribe: <http://catarina.usc.edu/mailman/listinfo/pim>,
	<mailto:pim-request@catarina.usc.edu?subject=subscribe>
List-Id: <pim.catarina.usc.edu>
List-Unsubscribe: <http://catarina.usc.edu/mailman/listinfo/pim>,
	<mailto:pim-request@catarina.usc.edu?subject=unsubscribe>
List-Archive: <http://catarina.usc.edu/pipermail/pim/>
Date: Wed, 17 Apr 2002 16:40:59 -0700
Content-Transfer-Encoding: 8bit

Hi all,

In the current pim-sm draft, AssertTrackingDesired(S,G,I) includes the following clause:
	
  (RPF_interface(RP)==I AND JoinDesired(*,G)==TRUE AND SPTbit(S,G)==FALSE)

Can someone tell me why it is necessary for a router with (*,G) state only to track 
(S,G) asserts in its RPF_intf(RP(G))?

Consider the following scenario:

			S --------------- RP
			|			|
			|			|
			R1			R2
			|			|
			|			|
		-----------------------------------
			|			|
			|			|
			R3			R4
			^			^
			|			|
			|			|
		igmp(S,G) join	   igmp(*,G) join
	

Suppose we have the following condition before the (S,G) traffic starts:
At R3, RPF'(S)=R1, JoinDesired(S,G) == TRUE, KLA(S,G) not running, and SPTbit(S,G) == 0
At R4, RPF'(RP(G))=R2, JoinDesired(*,G) == TRUE,  and no (S,G) state.

When R1 observes (S,G) traffic forwarded by R2 to the LAN, it will sends a 
(S,G) assert with RPT bit clear.  
When R4 receives the (S,G) assert, it will create the (S,G) state and move its (S,G) assert 
state-machine for the interface from the NoInfo state to the AssertLoser state because 
AssertTrackingDesired(S,G) is TRUE due to the clause above. Furthermore, it will set 
SPTbit(S,G) to 1 because the assert message is received from RPF_intf(S).
Now at R4, JoinDesired(S,G) == FALSE (UpstreamJPState(S,G) != Joined) while SPTbit(S,G) == 1.
This will create a black-hole and cause R4 to drop all (S,G) traffic it receives.

Am I missing something??

Regards,
James Huang
_______________________________________________
pim mailing list
pim@catarina.usc.edu
http://catarina.usc.edu/mailman/listinfo/pim


From pim-admin@catarina.usc.edu  Thu Apr 18 21:38:17 2002
Received: from catarina.usc.edu (catarina.usc.edu [204.57.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA28046
	for <pim-archive@lists.ietf.org>; Thu, 18 Apr 2002 21:38:16 -0400 (EDT)
Received: from catarina.usc.edu (localhost.localdomain [127.0.0.1])
	by catarina.usc.edu (8.11.6/8.11.6) with ESMTP id g3J1bB454792;
	Thu, 18 Apr 2002 18:37:12 -0700 (PDT)
	(envelope-from pim-admin@catarina.usc.edu)
Received: from web15004.mail.bjs.yahoo.com (web15004.mail.bjs.yahoo.com [61.135.128.7])
	by catarina.usc.edu (8.11.6/8.11.6) with SMTP id g3J1aZ454779
	for <pim@catarina.usc.edu>; Thu, 18 Apr 2002 18:36:36 -0700 (PDT)
	(envelope-from hurong_hr@yahoo.com.cn)
Message-ID: <20020419013614.88156.qmail@web15004.mail.bjs.yahoo.com>
Received: from [61.149.21.221] by web15004.mail.bjs.yahoo.com via HTTP; Fri, 19 Apr 2002 09:36:14 CST
From: =?gb2312?q?=C8=D8=20=BA=FA?= <hurong_hr@yahoo.com.cn>
To: pim@catarina.usc.edu
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0-446526440-1019180174=:86952"
Content-Transfer-Encoding: 8bit
Subject: [pim] a question about triggering join/prune
Sender: pim-admin@catarina.usc.edu
Errors-To: pim-admin@catarina.usc.edu
X-BeenThere: pim@catarina.usc.edu
X-Mailman-Version: 2.0.8
Precedence: bulk
List-Help: <mailto:pim-request@catarina.usc.edu?subject=help>
List-Post: <mailto:pim@catarina.usc.edu>
List-Subscribe: <http://catarina.usc.edu/mailman/listinfo/pim>,
	<mailto:pim-request@catarina.usc.edu?subject=subscribe>
List-Id: <pim.catarina.usc.edu>
List-Unsubscribe: <http://catarina.usc.edu/mailman/listinfo/pim>,
	<mailto:pim-request@catarina.usc.edu?subject=unsubscribe>
List-Archive: <http://catarina.usc.edu/pipermail/pim/>
Date: Fri, 19 Apr 2002 09:36:14 +0800 (CST)

--0-446526440-1019180174=:86952
Content-Type: text/plain; charset=gb2312
Content-Transfer-Encoding: 8bit


I want to join a multicast group on Windows2000 professional platform.How can I do it?

Another question :

cisco has a command "ip igmp join-group group address". If we enable it and configure the router to be a pimv2 one, can the router itself send join messages according to the group it joined? That is to say, can it act as both a host and a DR?

Thanks for help me ! 





---------------------------------
Do You Yahoo!?
30 张免费世界杯球票 7 天送完！有种你就快来抢！
--0-446526440-1019180174=:86952
Content-Type: text/html; charset=gb2312
Content-Transfer-Encoding: 8bit

<P>I want to join a multicast group on Windows2000 professional platform.How can I do it?</P>
<P>Another question :</P>
<P>cisco has a command "ip igmp join-group group address". If we enable it and configure the router to be a pimv2 one, can the router itself send join messages according to the group it joined? That is to say, can it act as both a host and a DR?</P>
<P>Thanks for help me !&nbsp;</P><BR><BR><p><br><hr size=1><b>Do You Yahoo!?</b><br>
30 张免费世界杯球票 7 天送完！有种你就<a href="http://rd.yahoo.com/mail_cn/tag/?http://cn.promo.yahoo.com/49/"><b>快来抢</b></a>！
--0-446526440-1019180174=:86952--
_______________________________________________
pim mailing list
pim@catarina.usc.edu
http://catarina.usc.edu/mailman/listinfo/pim


From pim-admin@catarina.usc.edu  Thu Apr 18 22:54:05 2002
Received: from catarina.usc.edu (catarina.usc.edu [204.57.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA00360
	for <pim-archive@odin.ietf.org>; Thu, 18 Apr 2002 22:54:05 -0400 (EDT)
Received: from catarina.usc.edu (localhost.localdomain [127.0.0.1])
	by catarina.usc.edu (8.11.6/8.11.6) with ESMTP id g3J2r1455935;
	Thu, 18 Apr 2002 19:53:01 -0700 (PDT)
	(envelope-from pim-admin@catarina.usc.edu)
Received: from dmz1.procket.com (dmz1.procket.com [65.174.124.36])
	by catarina.usc.edu (8.11.6/8.11.6) with ESMTP id g3J2qP455921
	for <pim@catarina.usc.edu>; Thu, 18 Apr 2002 19:52:26 -0700 (PDT)
	(envelope-from John.Zwiebel@procket.com)
Received: from miata.procket.com (miata.procket.com [65.174.124.5])
	by dmz1.procket.com (Postfix) with ESMTP
	id CFBB723C2F; Thu, 18 Apr 2002 19:41:11 -0700 (PDT)
Received: from EXCHANGE0-0.na.procket.com (exchange0a.na.procket.com [10.1.7.7])
	by miata.procket.com (8.12.1/8.12.1) with ESMTP id g3J2qKvM016435;
	Thu, 18 Apr 2002 19:52:20 -0700 (PDT)
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1E74D.3933F220"
Subject: RE: [pim] a question about triggering join/prune
Message-ID: <D2EC481073504E498A8DB9C0687E8CAF01842618@EXCHANGE0-0.na.procket.com>
Thread-Topic: [pim] a question about triggering join/prune
Thread-Index: AcHnSO6GnaI0Gdy9TjGsafEkYrRoXAAA6kmA
From: "John Zwiebel" <John.Zwiebel@procket.com>
To: "? ?" <hurong_hr@yahoo.com.cn>, <pim@catarina.usc.edu>
Sender: pim-admin@catarina.usc.edu
Errors-To: pim-admin@catarina.usc.edu
X-BeenThere: pim@catarina.usc.edu
X-Mailman-Version: 2.0.8
Precedence: bulk
List-Help: <mailto:pim-request@catarina.usc.edu?subject=help>
List-Post: <mailto:pim@catarina.usc.edu>
List-Subscribe: <http://catarina.usc.edu/mailman/listinfo/pim>,
	<mailto:pim-request@catarina.usc.edu?subject=subscribe>
List-Id: <pim.catarina.usc.edu>
List-Unsubscribe: <http://catarina.usc.edu/mailman/listinfo/pim>,
	<mailto:pim-request@catarina.usc.edu?subject=unsubscribe>
List-Archive: <http://catarina.usc.edu/pipermail/pim/>
Date: Thu, 18 Apr 2002 19:52:20 -0700

This is a multi-part message in MIME format.

------_=_NextPart_001_01C1E74D.3933F220
Content-Type: text/plain;
	charset="gb2312"
Content-Transfer-Encoding: quoted-printable

=20

	-----Original Message-----
	From: hurong_hr@yahoo.com.cn [mailto:hurong_hr@yahoo.com.cn]=20
	Sent: Thursday, April 18, 2002 6:36 PM
	To: pim@catarina.usc.edu
	Subject: [pim] a question about triggering join/prune
=09
=09

	I want to join a multicast group on Windows2000 professional =
platform.How can I do it?=20

	=20

	You might try compiling "pmsft"  which was written by wibert degraf for =
FreeBSD, but

	with the idea of running it on a Windows system.  It does not work on =
Windows XP,

	you have to bug the right folks at Microsoft to get it.  (BTW, this is =
just for if

	you want the PC to join a group, not if you want it to actually do =
anything, there

	are lots of applications that let you do that.)

	Another question :

	cisco has a command "ip igmp join-group group address". If we enable it =
and configure the router to be a pimv2 one, can the router itself send =
join messages according to the group it joined? That is to say, can it =
act as both a host and a DR?

	Thanks for help me ! =20

	Yes.  Assuming that when you say "joined" you mean that the router =
sends an IGMP

	host report out the interface this command is configured on, and then =
the DR on that

	subnet (it does -not- have to be the same router) will send a PIM join =
toward the RP.=20
=09
=09

=09
=09
  _____ =20

	Do You Yahoo!?
	30 =D5=C5=C3=E2=B7=D1=CA=C0=BD=E7=B1=AD=C7=F2=C6=B1 7 =
=CC=EC=CB=CD=CD=EA=A3=A1=D3=D0=D6=D6=C4=E3=BE=CD=BF=EC=C0=B4=C7=C0 =
<http://rd.yahoo.com/mail_cn/tag/?http://cn.promo.yahoo.com/49/> =A3=A1


------_=_NextPart_001_01C1E74D.3933F220
Content-Type: text/html;
	charset="gb2312"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>Message</TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dgb2312">
<META content=3D"MSHTML 5.50.4611.1300" name=3DGENERATOR></HEAD>
<BODY>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT>&nbsp;</DIV>
<BLOCKQUOTE=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV></DIV>
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft><FONT=20
  face=3DTahoma size=3D2>-----Original Message-----<BR><B>From:</B>=20
  hurong_hr@yahoo.com.cn [mailto:hurong_hr@yahoo.com.cn] =
<BR><B>Sent:</B>=20
  Thursday, April 18, 2002 6:36 PM<BR><B>To:</B>=20
  pim@catarina.usc.edu<BR><B>Subject:</B> [pim] a question about =
triggering=20
  join/prune<BR><BR></FONT></DIV>
  <P>I want to join a multicast group on Windows2000 professional =
platform.How=20
  can I do it?<SPAN class=3D255494702-19042002><FONT face=3DArial =
color=3D#0000ff=20
  size=3D2>&nbsp;</FONT></SPAN></P>
  <P><SPAN class=3D255494702-19042002></SPAN>&nbsp;</P>
  <P><SPAN class=3D255494702-19042002><FONT face=3DArial color=3D#0000ff =
size=3D2>You=20
  might try compiling "pmsft" </FONT>&nbsp;<FONT face=3DArial =
color=3D#0000ff=20
  size=3D2>which was written by wibert degraf for FreeBSD, =
but</FONT></SPAN></P>
  <P><SPAN class=3D255494702-19042002><FONT face=3DArial color=3D#0000ff =
size=3D2>with=20
  the idea of running it on a Windows system.&nbsp; It does not work on =
Windows=20
  XP,</FONT></SPAN></P>
  <P><SPAN class=3D255494702-19042002><FONT face=3DArial color=3D#0000ff =
size=3D2>you=20
  have to bug the right folks at Microsoft to get it.&nbsp; (BTW, this =
is just=20
  for if</FONT></SPAN></P>
  <P><SPAN class=3D255494702-19042002><FONT face=3DArial color=3D#0000ff =
size=3D2>you=20
  want the PC to join a group, not if you want it to actually do =
anything,=20
  there</FONT></SPAN></P>
  <P><SPAN class=3D255494702-19042002><FONT face=3DArial color=3D#0000ff =
size=3D2>are=20
  lots of applications that let you do that.)</FONT></SPAN></P>
  <P>Another question :</P>
  <P>cisco has a command "ip igmp join-group group address". If we =
enable it and=20
  configure the router to be a pimv2 one, can the router itself send =
join=20
  messages according to the group it joined? That is to say, can it act =
as both=20
  a host and a DR?</P>
  <P>Thanks for help me !&nbsp;<SPAN class=3D255494702-19042002><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2>&nbsp;</FONT></SPAN></P>
  <P><SPAN class=3D255494702-19042002><FONT face=3DArial color=3D#0000ff =

  size=3D2>Yes.&nbsp; Assuming that&nbsp;when you say "joined"&nbsp;you =
mean that=20
  the router sends an IGMP</FONT></SPAN></P>
  <P><SPAN class=3D255494702-19042002><FONT face=3DArial color=3D#0000ff =
size=3D2>host=20
  report out the interface&nbsp;this command is configured on, and then =
the DR=20
  on that</FONT></SPAN></P>
  <P><SPAN class=3D255494702-19042002><FONT face=3DArial color=3D#0000ff =
size=3D2>subnet=20
  (it does -not- have to be the same router) will send a PIM join toward =
the=20
  RP.</FONT>&nbsp;</SPAN><BR><BR></P>
  <P><BR>
  <HR SIZE=3D1>
  <B>Do You Yahoo!?</B><BR>30 =
=D5=C5=C3=E2=B7=D1=CA=C0=BD=E7=B1=AD=C7=F2=C6=B1 7 =
=CC=EC=CB=CD=CD=EA=A3=A1=D3=D0=D6=D6=C4=E3=BE=CD<A=20
  =
href=3D"http://rd.yahoo.com/mail_cn/tag/?http://cn.promo.yahoo.com/49/"><=
B>=BF=EC=C0=B4=C7=C0</B></A>=A3=A1</BLOCKQUOTE></BODY></HTML>
=00
------_=_NextPart_001_01C1E74D.3933F220--
_______________________________________________
pim mailing list
pim@catarina.usc.edu
http://catarina.usc.edu/mailman/listinfo/pim


From pim-admin@catarina.usc.edu  Mon Apr 22 04:01:32 2002
Received: from catarina.usc.edu (catarina.usc.edu [204.57.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA18684
	for <pim-archive@lists.ietf.org>; Mon, 22 Apr 2002 04:01:30 -0400 (EDT)
Received: from catarina.usc.edu (localhost.localdomain [127.0.0.1])
	by catarina.usc.edu (8.11.6/8.11.6) with ESMTP id g3M804426635;
	Mon, 22 Apr 2002 01:00:04 -0700 (PDT)
	(envelope-from pim-admin@catarina.usc.edu)
Received: from web15003.mail.bjs.yahoo.com (web15003.mail.bjs.yahoo.com [61.135.128.6])
	by catarina.usc.edu (8.11.6/8.11.6) with SMTP id g3M7xP426608
	for <pim@catarina.usc.edu>; Mon, 22 Apr 2002 00:59:29 -0700 (PDT)
	(envelope-from hurong_hr@yahoo.com.cn)
Message-ID: <20020422075916.80466.qmail@web15003.mail.bjs.yahoo.com>
Received: from [61.149.20.242] by web15003.mail.bjs.yahoo.com via HTTP; Mon, 22 Apr 2002 15:59:16 CST
From: =?gb2312?q?=C8=D8=20=BA=FA?= <hurong_hr@yahoo.com.cn>
To: pim@catarina.usc.edu
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0-29418416-1019462356=:80442"
Content-Transfer-Encoding: 8bit
Subject: [pim] question about join/prune suppression
Sender: pim-admin@catarina.usc.edu
Errors-To: pim-admin@catarina.usc.edu
X-BeenThere: pim@catarina.usc.edu
X-Mailman-Version: 2.0.8
Precedence: bulk
List-Help: <mailto:pim-request@catarina.usc.edu?subject=help>
List-Post: <mailto:pim@catarina.usc.edu>
List-Subscribe: <http://catarina.usc.edu/mailman/listinfo/pim>,
	<mailto:pim-request@catarina.usc.edu?subject=subscribe>
List-Id: <pim.catarina.usc.edu>
List-Unsubscribe: <http://catarina.usc.edu/mailman/listinfo/pim>,
	<mailto:pim-request@catarina.usc.edu?subject=unsubscribe>
List-Archive: <http://catarina.usc.edu/pipermail/pim/>
Date: Mon, 22 Apr 2002 15:59:16 +0800 (CST)

--0-29418416-1019462356=:80442
Content-Type: text/plain; charset=gb2312
Content-Transfer-Encoding: 8bit


All,

    when a router receive a join/prune not intended to it ,I think that it hear the message from a multi-access network and should suppress its relating route entries'  join/prune. Does it just start join/prune suppression timer of the matching route entries ? Or something else need doing ? According to different entries ,such as (*, G) , (*, *, RP), (S, G), especially (*, *, RP), different actions are needed to be done, but I'm not clear in mind. 



---------------------------------
Do You Yahoo!?
30 张免费世界杯球票 7 天送完！有种你就快来抢！
--0-29418416-1019462356=:80442
Content-Type: text/html; charset=gb2312
Content-Transfer-Encoding: 8bit

<P>All,</P>
<P>&nbsp;&nbsp;&nbsp; when a router receive a join/prune not intended to it ,I think that it hear the message from a multi-access network and should suppress its relating route entries'&nbsp; join/prune. Does it just start join/prune suppression timer of the matching route entries ? Or something else need doing ? According to different entries ,such as (*, G) , (*, *, RP), (S, G), especially (*, *, RP), different actions are needed to be done, but I'm not clear in mind. </P><p><br><hr size=1><b>Do You Yahoo!?</b><br>
30 张免费世界杯球票 7 天送完！有种你就<a href="http://rd.yahoo.com/mail_cn/tag/?http://cn.promo.yahoo.com/49/"><b>快来抢</b></a>！
--0-29418416-1019462356=:80442--
_______________________________________________
pim mailing list
pim@catarina.usc.edu
http://catarina.usc.edu/mailman/listinfo/pim


From pim-admin@catarina.usc.edu  Mon Apr 22 13:16:08 2002
Received: from catarina.usc.edu (catarina.usc.edu [204.57.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA03304
	for <pim-archive@lists.ietf.org>; Mon, 22 Apr 2002 13:16:08 -0400 (EDT)
Received: from catarina.usc.edu (localhost.localdomain [127.0.0.1])
	by catarina.usc.edu (8.11.6/8.11.6) with ESMTP id g3MHF2435802;
	Mon, 22 Apr 2002 10:15:02 -0700 (PDT)
	(envelope-from pim-admin@catarina.usc.edu)
Received: from fsnt.future.futsoft.com ([203.197.140.35])
	by catarina.usc.edu (8.11.6/8.11.6) with ESMTP id g3MHEs435788
	for <pim@catarina.usc.edu>; Mon, 22 Apr 2002 10:14:55 -0700 (PDT)
	(envelope-from prashantj@future.futsoft.com)
Received: from kailash.future.futsoft.com (unverified) by fsnt.future.futsoft.com
 (Content Technologies SMTPRS 2.0.15) with ESMTP id <B0002353806@fsnt.future.futsoft.com>;
 Mon, 22 Apr 2002 23:04:05 +0530
Received: from prashantj (prashantj.future.futsoft.com [10.4.5.20])
	by kailash.future.futsoft.com (8.11.0/8.11.0) with SMTP id g3MHEXh12622;
	Mon, 22 Apr 2002 22:44:33 +0530
Reply-To: <prashantj@future.futsoft.com>
From: "Prashant Jhingran" <prashantj@future.futsoft.com>
To: =?gb2312?B?J6ioPyBvqLIn?= <hurong_hr@yahoo.com.cn>, <pim@catarina.usc.edu>
Subject: RE: [pim] question about join/prune suppression
Message-Id: <000e01c1ea20$7b228f00$1405040a@future.futsoft.com>
MIME-Version: 1.0
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
In-Reply-To: <20020422075916.80466.qmail@web15003.mail.bjs.yahoo.com>
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_000F_01C1EA4E.94DACB00"
Sender: pim-admin@catarina.usc.edu
Errors-To: pim-admin@catarina.usc.edu
X-BeenThere: pim@catarina.usc.edu
X-Mailman-Version: 2.0.8
Precedence: bulk
List-Help: <mailto:pim-request@catarina.usc.edu?subject=help>
List-Post: <mailto:pim@catarina.usc.edu>
List-Subscribe: <http://catarina.usc.edu/mailman/listinfo/pim>,
	<mailto:pim-request@catarina.usc.edu?subject=subscribe>
List-Id: <pim.catarina.usc.edu>
List-Unsubscribe: <http://catarina.usc.edu/mailman/listinfo/pim>,
	<mailto:pim-request@catarina.usc.edu?subject=unsubscribe>
List-Archive: <http://catarina.usc.edu/pipermail/pim/>
Date: Mon, 22 Apr 2002 22:39:35 +0530

This is a multi-part message in MIME format.

------=_NextPart_000_000F_01C1EA4E.94DACB00
Content-Type: text/plain;
	charset="gb2312"
Content-Transfer-Encoding: 8bit

hi all,
        Well according to the latest draft ...(or I should better say
according to the latest version...as they keep coming..:-) )...there is no
"suppression timer"...
           tough one can find one in RFC 2362....

         In the latest draft, for  almost all the entries one is supposed to
either Decrease or Increase the Join Timer (JT) for the affected entry to
t_override or t_joinsuppress  time respectively...(for details pls refer the
draft)......on receiving so called "unintended" join/prune messages, which I
feel can only happen on the multi-access LAN.

Now its all implementation specific...if you are upgrading RFC to
draft.....then you can use the similar concept...otherwise...according to
draft one needs to manipulate the Join Timer....as per the specifications
given in the draft......
Hope this shall clear your doubt.....
regards,
Prashant
  -----Original Message-----
  From: pim-admin@catarina.usc.edu [mailto:pim-admin@catarina.usc.edu]On
Behalf Of 蓉 胡
  Sent: Monday, April 22, 2002 1:29 PM
  To: pim@catarina.usc.edu
  Subject: [pim] question about join/prune suppression


  All,

      when a router receive a join/prune not intended to it ,I think that it
hear the message from a multi-access network and should suppress its
relating route entries'  join/prune. Does it just start join/prune
suppression timer of the matching route entries ? Or something else need
doing ? According to different entries ,such as (*, G) , (*, *, RP), (S, G),
especially (*, *, RP), different actions are needed to be done, but I'm not
clear in mind.





----------------------------------------------------------------------------
--
  Do You Yahoo!?
  30 张免费世界杯球票 7 天送完！有种你就快来抢！

***************************************************************************
This message is proprietary to Future Software Limited (FSL) 
and is intended solely for the use of the individual to whom it
is addressed. It may contain  privileged or confidential information 
and should not be circulated or used for any purpose other than for 
what it is intended. 

If you have received this message in error, please notify the
originator immediately. If you are not the intended recipient,
you are notified that you are strictly prohibited from using,
copying, altering, or disclosing the contents of this message. 
FSL accepts no responsibility for loss or damage arising from 
the use of the information transmitted by this email including
damage from virus.
***************************************************************************
------=_NextPart_000_000F_01C1EA4E.94DACB00
Content-Type: text/html;
	charset="gb2312"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dgb2312">


<META content=3D"MSHTML 6.00.2600.0" name=3DGENERATOR></HEAD>
<BODY>
<DIV>
<DIV><SPAN class=3D630535116-22042002><FONT face=3DArial color=3D#0000ff =
size=3D2>hi=20
all,</FONT></SPAN></DIV>
<DIV><SPAN class=3D630535116-22042002><FONT face=3DArial color=3D#0000ff =

size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Well according to =
the latest=20
draft ...(or I should better say according to the latest version...as =
they keep=20
coming..:-) )...there is no "suppression timer"...</FONT></SPAN></DIV>
<DIV><SPAN class=3D630535116-22042002><FONT face=3DArial color=3D#0000ff =

size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
tough one=20
can find&nbsp;one in RFC 2362....</FONT></SPAN></DIV>
<DIV><SPAN class=3D630535116-22042002><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D630535116-22042002><FONT face=3DArial color=3D#0000ff =

size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;In the =
latest=20
draft,&nbsp;for &nbsp;almost all the&nbsp;entries one is supposed to =
either=20
<STRONG><EM>Decrease or Increase the Join Timer (JT)</EM></STRONG> for =
the=20
affected entry to t_override or t_joinsuppress&nbsp; time =
respectively...(for=20
details pls refer the draft)......on receiving&nbsp;so called =
"unintended"=20
join/prune messages, which I feel can only happen on the multi-access=20
LAN.</FONT></SPAN></DIV>
<DIV><SPAN class=3D630535116-22042002><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D630535116-22042002><FONT face=3DArial color=3D#0000ff =
size=3D2>Now=20
its all implementation specific...if you are upgrading RFC to =
draft.....then you=20
can use the similar concept...otherwise...according to draft one needs =
to=20
manipulate the Join Timer....as per the specifications given in the=20
draft......</FONT></SPAN></DIV>
<DIV><SPAN class=3D630535116-22042002><FONT face=3DArial color=3D#0000ff =
size=3D2>Hope=20
this shall clear your doubt.....</FONT></SPAN></DIV>
<DIV><SPAN class=3D630535116-22042002><FONT face=3DArial color=3D#0000ff =

size=3D2>regards,</FONT></SPAN></DIV>
<DIV><SPAN class=3D630535116-22042002><FONT face=3DArial color=3D#0000ff =

size=3D2>Prashant </FONT></SPAN></DIV></DIV>
<BLOCKQUOTE>
  <DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT =
face=3DTahoma=20
  size=3D2>-----Original Message-----<BR><B>From:</B> =
pim-admin@catarina.usc.edu=20
  [mailto:pim-admin@catarina.usc.edu]<B>On Behalf Of </B>=C8=D8 =
=BA=FA<BR><B>Sent:</B>=20
  Monday, April 22, 2002 1:29 PM<BR><B>To:</B>=20
  pim@catarina.usc.edu<BR><B>Subject:</B> [pim] question about =
join/prune=20
  suppression<BR><BR></FONT></DIV>
  <P>All,</P>
  <P>&nbsp;&nbsp;&nbsp; when a router receive a join/prune not intended =
to it ,I=20
  think that it hear the message from a multi-access network and should =
suppress=20
  its relating route entries'&nbsp; join/prune. Does it just start =
join/prune=20
  suppression timer of the matching route entries ? Or something else =
need doing=20
  ? According to different entries ,such as (*, G) , (*, *, RP), (S, G), =

  especially (*, *, RP), different actions are needed to be done, but =
I'm not=20
  clear in mind. </P>
  <P><BR>
  <HR SIZE=3D1>
  <B>Do You Yahoo!?</B><BR>30 =
=D5=C5=C3=E2=B7=D1=CA=C0=BD=E7=B1=AD=C7=F2=C6=B1 7 =
=CC=EC=CB=CD=CD=EA=A3=A1=D3=D0=D6=D6=C4=E3=BE=CD<A=20
  =
href=3D"http://rd.yahoo.com/mail_cn/tag/?http://cn.promo.yahoo.com/49/"><=
B>=BF=EC=C0=B4=C7=C0</B></A>=A3=A1</BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_000F_01C1EA4E.94DACB00--

_______________________________________________
pim mailing list
pim@catarina.usc.edu
http://catarina.usc.edu/mailman/listinfo/pim


From pim-admin@catarina.usc.edu  Mon Apr 22 16:22:51 2002
Received: from catarina.usc.edu (catarina.usc.edu [204.57.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11658
	for <pim-archive@lists.ietf.org>; Mon, 22 Apr 2002 16:22:49 -0400 (EDT)
Received: from catarina.usc.edu (localhost.localdomain [127.0.0.1])
	by catarina.usc.edu (8.11.6/8.11.6) with ESMTP id g3MKM1438851;
	Mon, 22 Apr 2002 13:22:01 -0700 (PDT)
	(envelope-from pim-admin@catarina.usc.edu)
Received: from external.zumanetworks.com (external.zumanetworks.com [64.161.185.13])
	by catarina.usc.edu (8.11.6/8.11.6) with SMTP id g3MKLE438833
	for <pim@catarina.usc.edu>; Mon, 22 Apr 2002 13:21:14 -0700 (PDT)
	(envelope-from jhuang@zumanetworks.com)
Received: from no.name.available by external.zumanetworks.com
          via smtpd (for catarina.usc.edu [204.57.0.1]) with SMTP; 22 Apr 2002 20:21:14 UT
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Message-ID: <E277CFA74A8D544A83F5314976B0451B7FB098@msmail.win.zumanetworks.com>
Thread-Topic: (S,G) expiration timer for pim-dm
Thread-Index: AcHqO0ACkz8HYhgBQbyFPvawU97JkQ==
From: "James Huang" <jhuang@zumanetworks.com>
To: <pim@catarina.usc.edu>
Cc: <ala@nexthop.com>, <jonathan.nicholas@itt.com>, <wfs@nexthop.com>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by catarina.usc.edu id g3MKLE438833
Subject: [pim] (S,G) expiration timer for pim-dm
Sender: pim-admin@catarina.usc.edu
Errors-To: pim-admin@catarina.usc.edu
X-BeenThere: pim@catarina.usc.edu
X-Mailman-Version: 2.0.8
Precedence: bulk
List-Help: <mailto:pim-request@catarina.usc.edu?subject=help>
List-Post: <mailto:pim@catarina.usc.edu>
List-Subscribe: <http://catarina.usc.edu/mailman/listinfo/pim>,
	<mailto:pim-request@catarina.usc.edu?subject=subscribe>
List-Id: <pim.catarina.usc.edu>
List-Unsubscribe: <http://catarina.usc.edu/mailman/listinfo/pim>,
	<mailto:pim-request@catarina.usc.edu?subject=unsubscribe>
List-Archive: <http://catarina.usc.edu/pipermail/pim/>
Date: Mon, 22 Apr 2002 13:21:14 -0700
Content-Transfer-Encoding: 8bit

Hi all,

The latest pim-dm spec does not have any description for the expiration timer of (S,G) entries.  
Section 5.6 "Timing out multicast forwarding entries" in draft-ietf-idmr-pim-dm-06.txt has some description but the document is more than four years old.
Shouldn't the management of the expiration timer be standardized?  Should the timer be updated only upon receiving (S,G) data packets or should it also be updated when a state-refresh message or prune message is received??  What bothers me is that the following scenario may occur if the expiration timer is not standardized.

Suppose a downstream router R2 ages out a (S,G) entry before its upstream router R1 does. If the source S becomes active again after the (S,G) entry in R2 is aged out but before R1 ages out its (S,G) entry and suppose R1's interface toward R2 is in the pruned state, then R2 will not be able to receive (S,G) traffic from R1 and re-create (S,G) entry until R1 times out the prune timer of its downstream interface.  Now if R2 receives a igmp (*,G) join during this period, it will not be able to send a graft(S,G) message toward the source.  So the receiver will not receive (S,G) traffic either.


Regards,
James Huang

_______________________________________________
pim mailing list
pim@catarina.usc.edu
http://catarina.usc.edu/mailman/listinfo/pim


From pim-admin@catarina.usc.edu  Mon Apr 22 18:17:07 2002
Received: from catarina.usc.edu (catarina.usc.edu [204.57.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA16621
	for <pim-archive@odin.ietf.org>; Mon, 22 Apr 2002 18:17:06 -0400 (EDT)
Received: from catarina.usc.edu (localhost.localdomain [127.0.0.1])
	by catarina.usc.edu (8.11.6/8.11.6) with ESMTP id g3MMG1440673;
	Mon, 22 Apr 2002 15:16:01 -0700 (PDT)
	(envelope-from pim-admin@catarina.usc.edu)
Received: from external.zumanetworks.com (external.zumanetworks.com [64.161.185.13])
	by catarina.usc.edu (8.11.6/8.11.6) with SMTP id g3MMFw440662
	for <pim@catarina.usc.edu>; Mon, 22 Apr 2002 15:15:59 -0700 (PDT)
	(envelope-from jhuang@zumanetworks.com)
Received: from no.name.available by external.zumanetworks.com
          via smtpd (for catarina.usc.edu [204.57.0.1]) with SMTP; 22 Apr 2002 22:15:58 UT
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Message-ID: <E277CFA74A8D544A83F5314976B0451B7FB09A@msmail.win.zumanetworks.com>
Thread-Topic: (S,G) expiration timer for pim-dm
Thread-Index: AcHqS0eE/tQJSTAJQvWt2Kr1tKlO9g==
From: "James Huang" <jhuang@zumanetworks.com>
To: <pim@catarina.usc.edu>
Cc: <ala@nexthop.com>, <jonathan.nicholas@itt.com>, <wfs@nexthop.com>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by catarina.usc.edu id g3MMFw440662
Subject: [pim] (S,G) expiration timer for pim-dm
Sender: pim-admin@catarina.usc.edu
Errors-To: pim-admin@catarina.usc.edu
X-BeenThere: pim@catarina.usc.edu
X-Mailman-Version: 2.0.8
Precedence: bulk
List-Help: <mailto:pim-request@catarina.usc.edu?subject=help>
List-Post: <mailto:pim@catarina.usc.edu>
List-Subscribe: <http://catarina.usc.edu/mailman/listinfo/pim>,
	<mailto:pim-request@catarina.usc.edu?subject=subscribe>
List-Id: <pim.catarina.usc.edu>
List-Unsubscribe: <http://catarina.usc.edu/mailman/listinfo/pim>,
	<mailto:pim-request@catarina.usc.edu?subject=unsubscribe>
List-Archive: <http://catarina.usc.edu/pipermail/pim/>
Date: Mon, 22 Apr 2002 15:15:58 -0700
Content-Transfer-Encoding: 8bit

Hi all,

The latest pim-dm spec does not have any description for the expiration timer of (S,G) entries.  
Section 5.6 "Timing out multicast forwarding entries" in draft-ietf-idmr-pim-dm-06.txt has some description but the document is more than four years old.
Shouldn't the management of the expiration timer be standardized?  Should the timer be updated only upon receiving (S,G) data packets or should it also be updated when a state-refresh message or prune message is received??  What bothers me is that the following scenario may occur if the expiration timer is not standardized.

Suppose the (S,G) expiration timer in a downstream router R2 is smaller than that in its upstream router R1 and suppose R1's interface toward R2 is in the pruned state. If R2 expires its (S,G) entry first and source S becomes active again before R1 expires its (S,G) entry, then R2 will not be able to receive (S,G) traffic from R1 and re-create (S,G) entry until the prune timer of R1's downstream interface expires.  Now if R2 receives a igmp (*,G) join during this period, it will not be able to send a graft(S,G) message toward the source.  So the receiver will not receive (S,G) traffic either.

Am I missing something?

Regards,
James Huang



_______________________________________________
pim mailing list
pim@catarina.usc.edu
http://catarina.usc.edu/mailman/listinfo/pim


From pim-admin@catarina.usc.edu  Mon Apr 22 18:46:46 2002
Received: from catarina.usc.edu (catarina.usc.edu [204.57.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA17105
	for <pim-archive@odin.ietf.org>; Mon, 22 Apr 2002 18:46:45 -0400 (EDT)
Received: from catarina.usc.edu (localhost.localdomain [127.0.0.1])
	by catarina.usc.edu (8.11.6/8.11.6) with ESMTP id g3MMk1441174;
	Mon, 22 Apr 2002 15:46:01 -0700 (PDT)
	(envelope-from pim-admin@catarina.usc.edu)
Received: from dmz1.procket.com (dmz1.procket.com [65.174.124.36])
	by catarina.usc.edu (8.11.6/8.11.6) with ESMTP id g3MMjf441163
	for <pim@catarina.usc.edu>; Mon, 22 Apr 2002 15:45:41 -0700 (PDT)
	(envelope-from John.Zwiebel@procket.com)
Received: from miata.procket.com (miata.procket.com [65.174.124.5])
	by dmz1.procket.com (Postfix) with ESMTP
	id C53EE23C31; Mon, 22 Apr 2002 15:34:18 -0700 (PDT)
Received: from email.procket.com (email.na.procket.com [10.1.7.252])
	by miata.procket.com (8.12.1/8.12.1) with ESMTP id g3MMjZvM005580;
	Mon, 22 Apr 2002 15:45:35 -0700 (PDT)
Received: from wl-d-70.procket.com ([10.1.1.1]) by email.procket.com over TLS secured channel with Microsoft SMTPSVC(5.0.2195.4905);
	 Mon, 22 Apr 2002 15:45:34 -0700
Subject: Re: [pim] (S,G) expiration timer for pim-dm
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v481)
Cc: <pim@catarina.usc.edu>, <ala@nexthop.com>, <jonathan.nicholas@itt.com>,
        <wfs@nexthop.com>
To: "James Huang" <jhuang@zumanetworks.com>
From: John Zwiebel <jzwiebel@procket.com>
In-Reply-To: <E277CFA74A8D544A83F5314976B0451B7FB098@msmail.win.zumanetworks.com>
Message-Id: <BD0021D4-5642-11D6-A49B-00039307689E@procket.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.481)
X-OriginalArrivalTime: 22 Apr 2002 22:45:34.0906 (UTC) FILETIME=[6A4139A0:01C1EA4F]
Sender: pim-admin@catarina.usc.edu
Errors-To: pim-admin@catarina.usc.edu
X-BeenThere: pim@catarina.usc.edu
X-Mailman-Version: 2.0.8
Precedence: bulk
List-Help: <mailto:pim-request@catarina.usc.edu?subject=help>
List-Post: <mailto:pim@catarina.usc.edu>
List-Subscribe: <http://catarina.usc.edu/mailman/listinfo/pim>,
	<mailto:pim-request@catarina.usc.edu?subject=subscribe>
List-Id: <pim.catarina.usc.edu>
List-Unsubscribe: <http://catarina.usc.edu/mailman/listinfo/pim>,
	<mailto:pim-request@catarina.usc.edu?subject=unsubscribe>
List-Archive: <http://catarina.usc.edu/pipermail/pim/>
Date: Mon, 22 Apr 2002 15:46:09 -0700
Content-Transfer-Encoding: 7bit

You are looking at the wrong spec.

Go to "draft-ietf-pim-dm-new-v2-01.txt"

FWIW: you might want to reexamine your need for
implementing dense-mode PIM.


On Monday, April 22, 2002, at 01:21 PM, James Huang wrote:

> Hi all,
>
> The latest pim-dm spec does not have any description for the expiration 
> timer of (S,G) entries.
> Section 5.6 "Timing out multicast forwarding entries" in 
> draft-ietf-idmr-pim-dm-06.txt has some description but the document is 
> more than four years old.
> Shouldn't the management of the expiration timer be standardized?  
> Should the timer be updated only upon receiving (S,G) data packets or 
> should it also be updated when a state-refresh message or prune message 
> is received??  What bothers me is that the following scenario may occur 
> if the expiration timer is not standardized.
>
> Suppose a downstream router R2 ages out a (S,G) entry before its 
> upstream router R1 does. If the source S becomes active again after the 
> (S,G) entry in R2 is aged out but before R1 ages out its (S,G) entry 
> and suppose R1's interface toward R2 is in the pruned state, then R2 
> will not be able to receive (S,G) traffic from R1 and re-create (S,G) 
> entry until R1 times out the prune timer of its downstream interface.  
> Now if R2 receives a igmp (*,G) join during this period, it will not be 
> able to send a graft(S,G) message toward the source.  So the receiver 
> will not receive (S,G) traffic either.
>
>
> Regards,
> James Huang
>
> _______________________________________________
> pim mailing list
> pim@catarina.usc.edu
> http://catarina.usc.edu/mailman/listinfo/pim

_______________________________________________
pim mailing list
pim@catarina.usc.edu
http://catarina.usc.edu/mailman/listinfo/pim


From pim-admin@catarina.usc.edu  Mon Apr 22 18:49:45 2002
Received: from catarina.usc.edu (catarina.usc.edu [204.57.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA17187
	for <pim-archive@odin.ietf.org>; Mon, 22 Apr 2002 18:49:44 -0400 (EDT)
Received: from catarina.usc.edu (localhost.localdomain [127.0.0.1])
	by catarina.usc.edu (8.11.6/8.11.6) with ESMTP id g3MMn1441274;
	Mon, 22 Apr 2002 15:49:01 -0700 (PDT)
	(envelope-from pim-admin@catarina.usc.edu)
Received: from external.zumanetworks.com (external.zumanetworks.com [64.161.185.13])
	by catarina.usc.edu (8.11.6/8.11.6) with SMTP id g3MMmF441242
	for <pim@catarina.usc.edu>; Mon, 22 Apr 2002 15:48:15 -0700 (PDT)
	(envelope-from jhuang@zumanetworks.com)
Received: from no.name.available by external.zumanetworks.com
          via smtpd (for catarina.usc.edu [204.57.0.1]) with SMTP; 22 Apr 2002 22:48:15 UT
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: [pim] (S,G) expiration timer for pim-dm
Message-ID: <E277CFA74A8D544A83F5314976B0451B7F2BC6@msmail.win.zumanetworks.com>
Thread-Topic: [pim] (S,G) expiration timer for pim-dm
Thread-Index: AcHqT2sxbx4jbemzTdGGQ+N2Fi2vkAAACDVg
From: "James Huang" <jhuang@zumanetworks.com>
To: "John Zwiebel" <jzwiebel@procket.com>
Cc: <pim@catarina.usc.edu>, <ala@nexthop.com>, <jonathan.nicholas@itt.com>,
        <wfs@nexthop.com>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by catarina.usc.edu id g3MMmF441242
Sender: pim-admin@catarina.usc.edu
Errors-To: pim-admin@catarina.usc.edu
X-BeenThere: pim@catarina.usc.edu
X-Mailman-Version: 2.0.8
Precedence: bulk
List-Help: <mailto:pim-request@catarina.usc.edu?subject=help>
List-Post: <mailto:pim@catarina.usc.edu>
List-Subscribe: <http://catarina.usc.edu/mailman/listinfo/pim>,
	<mailto:pim-request@catarina.usc.edu?subject=subscribe>
List-Id: <pim.catarina.usc.edu>
List-Unsubscribe: <http://catarina.usc.edu/mailman/listinfo/pim>,
	<mailto:pim-request@catarina.usc.edu?subject=unsubscribe>
List-Archive: <http://catarina.usc.edu/pipermail/pim/>
Date: Mon, 22 Apr 2002 15:48:14 -0700
Content-Transfer-Encoding: 8bit

"draft-ietf-pim-dm-new-v2-01.txt" is the draft that does not have any description for (S,G) expiration timer.
draft-ietf-idmr-pim-dm-06.txt has some description but is out of date.

Regards,
James Huang

> -----Original Message-----
> From: John Zwiebel [mailto:jzwiebel@procket.com]
> Sent: Monday, April 22, 2002 3:46 PM
> To: James Huang
> Cc: pim@catarina.usc.edu; ala@nexthop.com; jonathan.nicholas@itt.com;
> wfs@nexthop.com
> Subject: Re: [pim] (S,G) expiration timer for pim-dm
> 
> 
> You are looking at the wrong spec.
> 
> Go to "draft-ietf-pim-dm-new-v2-01.txt"
> 
> FWIW: you might want to reexamine your need for
> implementing dense-mode PIM.
> 
> 
> On Monday, April 22, 2002, at 01:21 PM, James Huang wrote:
> 
> > Hi all,
> >
> > The latest pim-dm spec does not have any description for 
> the expiration 
> > timer of (S,G) entries.
> > Section 5.6 "Timing out multicast forwarding entries" in 
> > draft-ietf-idmr-pim-dm-06.txt has some description but the 
> document is 
> > more than four years old.
> > Shouldn't the management of the expiration timer be standardized?  
> > Should the timer be updated only upon receiving (S,G) data 
> packets or 
> > should it also be updated when a state-refresh message or 
> prune message 
> > is received??  What bothers me is that the following 
> scenario may occur 
> > if the expiration timer is not standardized.
> >
> > Suppose a downstream router R2 ages out a (S,G) entry before its 
> > upstream router R1 does. If the source S becomes active 
> again after the 
> > (S,G) entry in R2 is aged out but before R1 ages out its 
> (S,G) entry 
> > and suppose R1's interface toward R2 is in the pruned 
> state, then R2 
> > will not be able to receive (S,G) traffic from R1 and 
> re-create (S,G) 
> > entry until R1 times out the prune timer of its downstream 
> interface.  
> > Now if R2 receives a igmp (*,G) join during this period, it 
> will not be 
> > able to send a graft(S,G) message toward the source.  So 
> the receiver 
> > will not receive (S,G) traffic either.
> >
> >
> > Regards,
> > James Huang
> >
> > _______________________________________________
> > pim mailing list
> > pim@catarina.usc.edu
> > http://catarina.usc.edu/mailman/listinfo/pim
> 
> 
_______________________________________________
pim mailing list
pim@catarina.usc.edu
http://catarina.usc.edu/mailman/listinfo/pim


From pim-admin@catarina.usc.edu  Tue Apr 23 08:22:14 2002
Received: from catarina.usc.edu (catarina.usc.edu [204.57.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA14058
	for <pim-archive@lists.ietf.org>; Tue, 23 Apr 2002 08:22:14 -0400 (EDT)
Received: from catarina.usc.edu (localhost.localdomain [127.0.0.1])
	by catarina.usc.edu (8.11.6/8.11.6) with ESMTP id g3NCL4459882;
	Tue, 23 Apr 2002 05:21:04 -0700 (PDT)
	(envelope-from pim-admin@catarina.usc.edu)
Received: from gate1.itt.com (gate1.itt.com [151.190.254.100])
	by catarina.usc.edu (8.11.6/8.11.6) with SMTP id g3NCKN459861
	for <pim@catarina.usc.edu>; Tue, 23 Apr 2002 05:20:23 -0700 (PDT)
	(envelope-from Jonathan.Nicholas@itt.com)
Received: from no.name.available by gate1.itt.com
          via smtpd (for catarina.usc.edu [204.57.0.1]) with SMTP; 23 Apr 2002 12:20:23 UT
Received: by FWDCMAIL2.fwdc.de.ittind.com with Internet Mail Service (5.5.2653.19)
	id <2NJBKKD7>; Tue, 23 Apr 2002 07:20:19 -0500
Message-ID: <C92AD5F39518D5119A0F0002B30A10319390CD@acdnjmail3.acdav.de.ittind.com>
From: "Nicholas, Jonathan" <Jonathan.Nicholas@itt.com>
To: "'James Huang'" <jhuang@zumanetworks.com>, pim@catarina.usc.edu
Cc: ala@nexthop.com, wfs@nexthop.com
Subject: RE: [pim] (S,G) expiration timer for pim-dm
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: pim-admin@catarina.usc.edu
Errors-To: pim-admin@catarina.usc.edu
X-BeenThere: pim@catarina.usc.edu
X-Mailman-Version: 2.0.8
Precedence: bulk
List-Help: <mailto:pim-request@catarina.usc.edu?subject=help>
List-Post: <mailto:pim@catarina.usc.edu>
List-Subscribe: <http://catarina.usc.edu/mailman/listinfo/pim>,
	<mailto:pim-request@catarina.usc.edu?subject=subscribe>
List-Id: <pim.catarina.usc.edu>
List-Unsubscribe: <http://catarina.usc.edu/mailman/listinfo/pim>,
	<mailto:pim-request@catarina.usc.edu?subject=unsubscribe>
List-Archive: <http://catarina.usc.edu/pipermail/pim/>
Date: Tue, 23 Apr 2002 07:20:17 -0500

PIM-DM has no expiration timer.  This was a conscious choice.

Because the default state for PIM-DM is forwarding, the maintenance of
forwarding entries is left as an implementor choice based on available
processing power and memory resources.  Maintenance of entries as long as
any state machine is not in the default state is mandatory, perhaps this
requirement should be stated more clearly.

The Upstream state machine's default is Forwarding.
The Downstream state machine's default is No Info.
The Assert state machine's default is No Info.
The Originator state machine's default is Not Originator.

All state machines have specific timers describing when they return to the
default state.  None of the state machines can remain indefinitely in a non
default state in the absence of traffic.

In the scenario described below, either R1 erroneously became pruned when R2
desired the traffic (i.e. R1 did not receive R2's Prune Override), or R2
left an Upstream Prune state without sending a Graft, which is an illegal
operation.  In either case, the soon to arrive State Refresh message will
trigger a Prune Override from R2, correcting the condition.

Jonathan Nicholas
Network Systems Engineer
ITT Aerospace/Communications Division

> Hi all,
> 
> The latest pim-dm spec does not have any description for the 
> expiration timer of (S,G) entries.  
> Section 5.6 "Timing out multicast forwarding entries" in 
> draft-ietf-idmr-pim-dm-06.txt has some description but the 
> document is more than four years old.
> Shouldn't the management of the expiration timer be 
> standardized?  Should the timer be updated only upon 
> receiving (S,G) data packets or should it also be updated 
> when a state-refresh message or prune message is received??  
> What bothers me is that the following scenario may occur if 
> the expiration timer is not standardized.
> 
> Suppose a downstream router R2 ages out a (S,G) entry before 
> its upstream router R1 does. If the source S becomes active 
> again after the (S,G) entry in R2 is aged out but before R1 
> ages out its (S,G) entry and suppose R1's interface toward R2 
> is in the pruned state, then R2 will not be able to receive 
> (S,G) traffic from R1 and re-create (S,G) entry until R1 
> times out the prune timer of its downstream interface.  Now 
> if R2 receives a igmp (*,G) join during this period, it will 
> not be able to send a graft(S,G) message toward the source.  
> So the receiver will not receive (S,G) traffic either.
> 
> 
> Regards,
> James Huang

************************************ 
If this email is not intended for you, or you are not responsible for the
delivery of this message to the addressee, please note that this message may
contain ITT Privileged/Proprietary Information.  In such a case, you may not
copy or deliver this message to anyone.  You should destroy this message and
kindly notify the sender by reply email.  Information contained in this
message that does not relate to the business of ITT is neither endorsed by
nor attributable to ITT. 
************************************ 

_______________________________________________
pim mailing list
pim@catarina.usc.edu
http://catarina.usc.edu/mailman/listinfo/pim


From pim-admin@catarina.usc.edu  Tue Apr 23 13:22:02 2002
Received: from catarina.usc.edu (catarina.usc.edu [204.57.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA28279
	for <pim-archive@odin.ietf.org>; Tue, 23 Apr 2002 13:22:02 -0400 (EDT)
Received: from catarina.usc.edu (localhost.localdomain [127.0.0.1])
	by catarina.usc.edu (8.11.6/8.11.6) with ESMTP id g3NHL2464742;
	Tue, 23 Apr 2002 10:21:02 -0700 (PDT)
	(envelope-from pim-admin@catarina.usc.edu)
Received: from external.zumanetworks.com (external.zumanetworks.com [64.161.185.13])
	by catarina.usc.edu (8.11.6/8.11.6) with SMTP id g3NHK7464722
	for <pim@catarina.usc.edu>; Tue, 23 Apr 2002 10:20:07 -0700 (PDT)
	(envelope-from jhuang@zumanetworks.com)
Received: from no.name.available by external.zumanetworks.com
          via smtpd (for catarina.usc.edu [204.57.0.1]) with SMTP; 23 Apr 2002 17:20:07 UT
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: [pim] (S,G) expiration timer for pim-dm
Message-ID: <E277CFA74A8D544A83F5314976B0451B7FB09C@msmail.win.zumanetworks.com>
Thread-Topic: [pim] (S,G) expiration timer for pim-dm
Thread-Index: AcHqwT190nqS44LBQxqSCiGkMT9GbgAJH08g
From: "James Huang" <jhuang@zumanetworks.com>
To: "Nicholas, Jonathan" <Jonathan.Nicholas@itt.com>, <pim@catarina.usc.edu>
Cc: <ala@nexthop.com>, <wfs@nexthop.com>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by catarina.usc.edu id g3NHK7464722
Sender: pim-admin@catarina.usc.edu
Errors-To: pim-admin@catarina.usc.edu
X-BeenThere: pim@catarina.usc.edu
X-Mailman-Version: 2.0.8
Precedence: bulk
List-Help: <mailto:pim-request@catarina.usc.edu?subject=help>
List-Post: <mailto:pim@catarina.usc.edu>
List-Subscribe: <http://catarina.usc.edu/mailman/listinfo/pim>,
	<mailto:pim-request@catarina.usc.edu?subject=subscribe>
List-Id: <pim.catarina.usc.edu>
List-Unsubscribe: <http://catarina.usc.edu/mailman/listinfo/pim>,
	<mailto:pim-request@catarina.usc.edu?subject=unsubscribe>
List-Archive: <http://catarina.usc.edu/pipermail/pim/>
Date: Tue, 23 Apr 2002 10:20:07 -0700
Content-Transfer-Encoding: 8bit

Thanks for replying to me email.
I still have some question with this issue.
Please see the comment below.

Regards,
James Huang

> -----Original Message-----
> From: Nicholas, Jonathan [mailto:Jonathan.Nicholas@itt.com]
> Sent: Tuesday, April 23, 2002 5:20 AM
> To: James Huang; pim@catarina.usc.edu
> Cc: ala@nexthop.com; wfs@nexthop.com
> Subject: RE: [pim] (S,G) expiration timer for pim-dm
> 
> 
> PIM-DM has no expiration timer.  This was a conscious choice.
> 
> Because the default state for PIM-DM is forwarding, the maintenance of
> forwarding entries is left as an implementor choice based on available
> processing power and memory resources.  Maintenance of 
> entries as long as
> any state machine is not in the default state is mandatory, 
> perhaps this
> requirement should be stated more clearly.
> 
> The Upstream state machine's default is Forwarding.
> The Downstream state machine's default is No Info.
> The Assert state machine's default is No Info.
> The Originator state machine's default is Not Originator.
> 
> All state machines have specific timers describing when they 
> return to the
> default state.  None of the state machines can remain 
> indefinitely in a non default state in the absence of traffic.

This is true for the downstram state machine, the assert state machine,
and the originator state machine.  But for the upstream state machine, it
will stay in the pruned state as long as olist(S,G) remains NULL.
To conserve memory resouce, it might be desirable to also clean up this (S,G) entry 
after the traffic has stopped for a long time. But as I describe in my previous 
email, removing a (S,G) entry with its upstream state machine in the pruned state 
may result in the failure of packet delivery to the interested receivers.
So I guess the only way out of it is to send a graft message upstream before such a entry 
is removed.


> 
> In the scenario described below, either R1 erroneously became 
> pruned when R2
> desired the traffic (i.e. R1 did not receive R2's Prune 
> Override), or R2
> left an Upstream Prune state without sending a Graft, which 
> is an illegal
> operation.  In either case, the soon to arrive State Refresh 
> message will
> trigger a Prune Override from R2, correcting the condition.
> 
> Jonathan Nicholas
> Network Systems Engineer
> ITT Aerospace/Communications Division
> 
> > Hi all,
> > 
> > The latest pim-dm spec does not have any description for the 
> > expiration timer of (S,G) entries.  
> > Section 5.6 "Timing out multicast forwarding entries" in 
> > draft-ietf-idmr-pim-dm-06.txt has some description but the 
> > document is more than four years old.
> > Shouldn't the management of the expiration timer be 
> > standardized?  Should the timer be updated only upon 
> > receiving (S,G) data packets or should it also be updated 
> > when a state-refresh message or prune message is received??  
> > What bothers me is that the following scenario may occur if 
> > the expiration timer is not standardized.
> > 
> > Suppose a downstream router R2 ages out a (S,G) entry before 
> > its upstream router R1 does. If the source S becomes active 
> > again after the (S,G) entry in R2 is aged out but before R1 
> > ages out its (S,G) entry and suppose R1's interface toward R2 
> > is in the pruned state, then R2 will not be able to receive 
> > (S,G) traffic from R1 and re-create (S,G) entry until R1 
> > times out the prune timer of its downstream interface.  Now 
> > if R2 receives a igmp (*,G) join during this period, it will 
> > not be able to send a graft(S,G) message toward the source.  
> > So the receiver will not receive (S,G) traffic either.
> > 
> > 
> > Regards,
> > James Huang
> 
> ************************************ 
> If this email is not intended for you, or you are not 
> responsible for the
> delivery of this message to the addressee, please note that 
> this message may
> contain ITT Privileged/Proprietary Information.  In such a 
> case, you may not
> copy or deliver this message to anyone.  You should destroy 
> this message and
> kindly notify the sender by reply email.  Information 
> contained in this
> message that does not relate to the business of ITT is 
> neither endorsed by
> nor attributable to ITT. 
> ************************************ 
> 
> 
_______________________________________________
pim mailing list
pim@catarina.usc.edu
http://catarina.usc.edu/mailman/listinfo/pim


From pim-admin@catarina.usc.edu  Tue Apr 23 15:15:10 2002
Received: from catarina.usc.edu (catarina.usc.edu [204.57.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA02907
	for <pim-archive@odin.ietf.org>; Tue, 23 Apr 2002 15:15:09 -0400 (EDT)
Received: from catarina.usc.edu (localhost.localdomain [127.0.0.1])
	by catarina.usc.edu (8.11.6/8.11.6) with ESMTP id g3NJE2466857;
	Tue, 23 Apr 2002 12:14:02 -0700 (PDT)
	(envelope-from pim-admin@catarina.usc.edu)
Received: from gate1.itt.com (gate1.itt.com [151.190.254.100])
	by catarina.usc.edu (8.11.6/8.11.6) with SMTP id g3NJDK466841
	for <pim@catarina.usc.edu>; Tue, 23 Apr 2002 12:13:20 -0700 (PDT)
	(envelope-from Jonathan.Nicholas@itt.com)
Received: from no.name.available by gate1.itt.com
          via smtpd (for catarina.usc.edu [204.57.0.1]) with SMTP; 23 Apr 2002 19:13:20 UT
Received: by FWDCMAIL2.fwdc.de.ittind.com with Internet Mail Service (5.5.2653.19)
	id <2NJBLDLH>; Tue, 23 Apr 2002 14:13:18 -0500
Message-ID: <C92AD5F39518D5119A0F0002B30A10319390CE@acdnjmail3.acdav.de.ittind.com>
From: "Nicholas, Jonathan" <Jonathan.Nicholas@itt.com>
To: "'James Huang'" <jhuang@zumanetworks.com>, pim@catarina.usc.edu
Cc: ala@nexthop.com, wfs@nexthop.com
Subject: RE: [pim] (S,G) expiration timer for pim-dm
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: pim-admin@catarina.usc.edu
Errors-To: pim-admin@catarina.usc.edu
X-BeenThere: pim@catarina.usc.edu
X-Mailman-Version: 2.0.8
Precedence: bulk
List-Help: <mailto:pim-request@catarina.usc.edu?subject=help>
List-Post: <mailto:pim@catarina.usc.edu>
List-Subscribe: <http://catarina.usc.edu/mailman/listinfo/pim>,
	<mailto:pim-request@catarina.usc.edu?subject=subscribe>
List-Id: <pim.catarina.usc.edu>
List-Unsubscribe: <http://catarina.usc.edu/mailman/listinfo/pim>,
	<mailto:pim-request@catarina.usc.edu?subject=unsubscribe>
List-Archive: <http://catarina.usc.edu/pipermail/pim/>
Date: Tue, 23 Apr 2002 14:13:17 -0500

You are correct that the Upstream state machine could remain in the Prune
state indefinitely.  This is only possible for a router with no downstream
PIM routers.  

However, in this case, the Upstream state machine's Prune Limit Timer would
be the indicator used to determine expiration along with the Assert Timer,
if any.  That is, if the Prune Limit Timer is still running, the entry must
be maintained.

Since State Refreshes cause the Prune Limit Timer to restart, when the Prune
Limit Timer expires it is safe for the router to assume its upstream router
is no longer in a Pruned state (in fact, has quite likely expired its own
entry) and the entry may be removed.

Thank you for your comments.  I will add clarifying text to the next draft.

Jonathan Nicholas
Network Systems Engineer
ITT Aerospace/Communications Division

> 
> Thanks for replying to me email.
> I still have some question with this issue.
> Please see the comment below.
> 
> > All state machines have specific timers describing when they 
> > return to the
> > default state.  None of the state machines can remain 
> > indefinitely in a non default state in the absence of traffic.
> 
> This is true for the downstram state machine, the assert 
> state machine,
> and the originator state machine.  But for the upstream state 
> machine, it
> will stay in the pruned state as long as olist(S,G) remains NULL.
> To conserve memory resouce, it might be desirable to also 
> clean up this (S,G) entry 
> after the traffic has stopped for a long time. But as I 
> describe in my previous 
> email, removing a (S,G) entry with its upstream state machine 
> in the pruned state 
> may result in the failure of packet delivery to the 
> interested receivers.
> So I guess the only way out of it is to send a graft message 
> upstream before such a entry 
> is removed.
> 

************************************ 
If this email is not intended for you, or you are not responsible for the
delivery of this message to the addressee, please note that this message may
contain ITT Privileged/Proprietary Information.  In such a case, you may not
copy or deliver this message to anyone.  You should destroy this message and
kindly notify the sender by reply email.  Information contained in this
message that does not relate to the business of ITT is neither endorsed by
nor attributable to ITT. 
************************************ 

_______________________________________________
pim mailing list
pim@catarina.usc.edu
http://catarina.usc.edu/mailman/listinfo/pim


From pim-admin@catarina.usc.edu  Thu Apr 25 13:27:19 2002
Received: from catarina.usc.edu (catarina.usc.edu [204.57.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA28439
	for <pim-archive@lists.ietf.org>; Thu, 25 Apr 2002 13:27:19 -0400 (EDT)
Received: from catarina.usc.edu (localhost.localdomain [127.0.0.1])
	by catarina.usc.edu (8.11.6/8.11.6) with ESMTP id g3PHQ4408046;
	Thu, 25 Apr 2002 10:26:04 -0700 (PDT)
	(envelope-from pim-admin@catarina.usc.edu)
Received: from web15004.mail.bjs.yahoo.com (web15004.mail.bjs.yahoo.com [61.135.128.7])
	by catarina.usc.edu (8.11.6/8.11.6) with SMTP id g3P7ou499753
	for <pim@catarina.usc.edu>; Thu, 25 Apr 2002 00:50:57 -0700 (PDT)
	(envelope-from jiahaow@yahoo.com.cn)
Message-ID: <20020425075049.50773.qmail@web15004.mail.bjs.yahoo.com>
Received: from [202.110.185.60] by web15004.mail.bjs.yahoo.com via HTTP; Thu, 25 Apr 2002 15:50:49 CST
From: =?gb2312?q?Jiahao=20Wang?= <jiahaow@yahoo.com.cn>
To: pim@catarina.usc.edu
MIME-Version: 1.0
Content-Type: text/plain; charset=gb2312
Content-Transfer-Encoding: 8bit
Subject: [pim] Interoperability between PIM-SM and DVMRP
Sender: pim-admin@catarina.usc.edu
Errors-To: pim-admin@catarina.usc.edu
X-BeenThere: pim@catarina.usc.edu
X-Mailman-Version: 2.0.8
Precedence: bulk
List-Help: <mailto:pim-request@catarina.usc.edu?subject=help>
List-Post: <mailto:pim@catarina.usc.edu>
List-Subscribe: <http://catarina.usc.edu/mailman/listinfo/pim>,
	<mailto:pim-request@catarina.usc.edu?subject=subscribe>
List-Id: <pim.catarina.usc.edu>
List-Unsubscribe: <http://catarina.usc.edu/mailman/listinfo/pim>,
	<mailto:pim-request@catarina.usc.edu?subject=unsubscribe>
List-Archive: <http://catarina.usc.edu/pipermail/pim/>
Date: Thu, 25 Apr 2002 15:50:49 +0800 (CST)
Content-Transfer-Encoding: 8bit

In the newest Pimd source code(pimd-current.tar.gz), I
couldn't find implementation of PMBR, could you tell
me the reason? In RFC 2715 and
draft-ietf-pim-sm-v2-new-05.txt, the requirement of
Interoperability between PIM-SM and DVMRP is
necessary, How to implement PMBR in Pimd? 
Thanks!


Best regard
Jiahaow

_________________________________________________________
Do You Yahoo!? 
到世界杯主题公园玩一玩，赢取世界杯门票乐一乐。
http://cn.fifaworldcup.yahoo.com/
_______________________________________________
pim mailing list
pim@catarina.usc.edu
http://catarina.usc.edu/mailman/listinfo/pim


From pim-admin@catarina.usc.edu  Thu Apr 25 13:33:47 2002
Received: from catarina.usc.edu (catarina.usc.edu [204.57.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA28670
	for <pim-archive@odin.ietf.org>; Thu, 25 Apr 2002 13:33:46 -0400 (EDT)
Received: from catarina.usc.edu (localhost.localdomain [127.0.0.1])
	by catarina.usc.edu (8.11.6/8.11.6) with ESMTP id g3PHX1408191;
	Thu, 25 Apr 2002 10:33:01 -0700 (PDT)
	(envelope-from pim-admin@catarina.usc.edu)
Received: from prattle.redback.com (prattle.redback.com [155.53.12.9])
	by catarina.usc.edu (8.11.6/8.11.6) with ESMTP id g3PHWv408180
	for <pim@catarina.usc.edu>; Thu, 25 Apr 2002 10:32:57 -0700 (PDT)
	(envelope-from lwei@redback.com)
Received: from yoo-hoo.redback.com (yoo-hoo.redback.com [155.53.12.43])
	by prattle.redback.com (Postfix) with ESMTP
	id 65ABE1DCC78; Thu, 25 Apr 2002 10:32:52 -0700 (PDT)
Received: (from lwei@localhost)
	by yoo-hoo.redback.com (8.9.3-LCCHA/8.9.3/null redback solaris client) id KAA19266;
	Thu, 25 Apr 2002 10:32:52 -0700 (PDT)
Message-Id: <200204251732.KAA19266@yoo-hoo.redback.com>
From: Liming Wei <lwei@redback.com>
To: jiahaow@yahoo.com.cn
Cc: pim@catarina.usc.edu
In-reply-to: <20020425075049.50773.qmail@web15004.mail.bjs.yahoo.com> (message
	from =?gb2312?q?Jiahao=20Wang?= on Thu, 25 Apr 2002 15:50:49 +0800
	(CST))
Subject: Re: [pim] Interoperability between PIM-SM and DVMRP
Reply-To: lwei@redback.com
Sender: pim-admin@catarina.usc.edu
Errors-To: pim-admin@catarina.usc.edu
X-BeenThere: pim@catarina.usc.edu
X-Mailman-Version: 2.0.8
Precedence: bulk
List-Help: <mailto:pim-request@catarina.usc.edu?subject=help>
List-Post: <mailto:pim@catarina.usc.edu>
List-Subscribe: <http://catarina.usc.edu/mailman/listinfo/pim>,
	<mailto:pim-request@catarina.usc.edu?subject=subscribe>
List-Id: <pim.catarina.usc.edu>
List-Unsubscribe: <http://catarina.usc.edu/mailman/listinfo/pim>,
	<mailto:pim-request@catarina.usc.edu?subject=unsubscribe>
List-Archive: <http://catarina.usc.edu/pipermail/pim/>
Date: Thu, 25 Apr 2002 10:32:52 -0700 (PDT)

Jiahao,

Have you considered to implement the domain wide report in DVMRP ?

With that you don't need to touch PIM-SM or the USC pimd.

-Liming
-------------
> From: =?gb2312?q?Jiahao=20Wang?= <jiahaow@yahoo.com.cn>
> 
> In the newest Pimd source code(pimd-current.tar.gz), I
> couldn't find implementation of PMBR, could you tell
> me the reason? In RFC 2715 and
> draft-ietf-pim-sm-v2-new-05.txt, the requirement of
> Interoperability between PIM-SM and DVMRP is
> necessary, How to implement PMBR in Pimd? 
> Thanks!
> 
> 
> Best regard
> Jiahaow
> 
> _________________________________________________________
> Do You Yahoo!? 
> 到世界杯主题公园玩一玩，赢取世界杯门票乐一乐。
> http://cn.fifaworldcup.yahoo.com/
> _______________________________________________
> pim mailing list
> pim@catarina.usc.edu
> http://catarina.usc.edu/mailman/listinfo/pim
> 
_______________________________________________
pim mailing list
pim@catarina.usc.edu
http://catarina.usc.edu/mailman/listinfo/pim


From pim-admin@catarina.usc.edu  Thu Apr 25 23:38:50 2002
Received: from catarina.usc.edu (catarina.usc.edu [204.57.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA15085
	for <pim-archive@odin.ietf.org>; Thu, 25 Apr 2002 23:38:49 -0400 (EDT)
Received: from catarina.usc.edu (localhost.localdomain [127.0.0.1])
	by catarina.usc.edu (8.11.6/8.11.6) with ESMTP id g3Q3c2416665;
	Thu, 25 Apr 2002 20:38:02 -0700 (PDT)
	(envelope-from pim-admin@catarina.usc.edu)
Received: from web15004.mail.bjs.yahoo.com (web15004.mail.bjs.yahoo.com [61.135.128.7])
	by catarina.usc.edu (8.11.6/8.11.6) with SMTP id g3Q3YP416589
	for <pim@catarina.usc.edu>; Thu, 25 Apr 2002 20:34:26 -0700 (PDT)
	(envelope-from jiahaow@yahoo.com.cn)
Message-ID: <20020426033417.25804.qmail@web15004.mail.bjs.yahoo.com>
Received: from [202.110.185.60] by web15004.mail.bjs.yahoo.com via HTTP; Fri, 26 Apr 2002 11:34:17 CST
From: =?gb2312?q?Jiahao=20Wang?= <jiahaow@yahoo.com.cn>
To: pim@catarina.usc.edu
MIME-Version: 1.0
Content-Type: text/plain; charset=gb2312
Content-Transfer-Encoding: 8bit
Subject: [pim] about PMBR
Sender: pim-admin@catarina.usc.edu
Errors-To: pim-admin@catarina.usc.edu
X-BeenThere: pim@catarina.usc.edu
X-Mailman-Version: 2.0.8
Precedence: bulk
List-Help: <mailto:pim-request@catarina.usc.edu?subject=help>
List-Post: <mailto:pim@catarina.usc.edu>
List-Subscribe: <http://catarina.usc.edu/mailman/listinfo/pim>,
	<mailto:pim-request@catarina.usc.edu?subject=subscribe>
List-Id: <pim.catarina.usc.edu>
List-Unsubscribe: <http://catarina.usc.edu/mailman/listinfo/pim>,
	<mailto:pim-request@catarina.usc.edu?subject=unsubscribe>
List-Archive: <http://catarina.usc.edu/pipermail/pim/>
Date: Fri, 26 Apr 2002 11:34:17 +0800 (CST)
Content-Transfer-Encoding: 8bit

Hi, Liming Wei
   
    Thank your advice very much!
    I think I had better implement the domain wide
report in PIM-SM. There are some reasons. PIM-SM can
support inter-domain multicast better than DVMRP, such
as MSDP/MBGP, and Cisco has implemented it. The source
codes of MrouteD and PimD are written by USC, they are
very similar, therefore, it is easy to touch PIMD
after touching MroutD.
    According to RFC 2715 and
draft-ietf-pim-sm-v2-new-05.txt, PMBR should have
several multicast components, I am concerned that
DVMRP and PIM-SM component on PMBR. There is only one
component running on one interface at PMBR, isn't it?
I am not sure that PMBR should run PIM-SM at PIM cloud
interfaces and run DVMRP at DVMRP cloud interfaces.
Could you help me interpret it?
    Thanks!


Best regards
Jiahaow


_________________________________________________________
Do You Yahoo!? 
到世界杯主题公园玩一玩，赢取世界杯门票乐一乐。
http://cn.fifaworldcup.yahoo.com/
_______________________________________________
pim mailing list
pim@catarina.usc.edu
http://catarina.usc.edu/mailman/listinfo/pim


From pim-admin@catarina.usc.edu  Fri Apr 26 01:07:49 2002
Received: from catarina.usc.edu (catarina.usc.edu [204.57.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA16569
	for <pim-archive@odin.ietf.org>; Fri, 26 Apr 2002 01:07:49 -0400 (EDT)
Received: from catarina.usc.edu (localhost.localdomain [127.0.0.1])
	by catarina.usc.edu (8.11.6/8.11.6) with ESMTP id g3Q572417944;
	Thu, 25 Apr 2002 22:07:02 -0700 (PDT)
	(envelope-from pim-admin@catarina.usc.edu)
Received: from possum.icir.org (possum.icir.org [192.150.187.67])
	by catarina.usc.edu (8.11.6/8.11.6) with ESMTP id g3Q56r417930
	for <pim@catarina.usc.edu>; Thu, 25 Apr 2002 22:06:53 -0700 (PDT)
	(envelope-from pavlin@possum.icir.org)
Received: from possum.icir.org (localhost [127.0.0.1])
	by possum.icir.org (8.11.6/8.11.3) with ESMTP id g3Q56j314418;
	Thu, 25 Apr 2002 22:06:45 -0700 (PDT)
	(envelope-from pavlin@possum.icir.org)
Message-Id: <200204260506.g3Q56j314418@possum.icir.org>
To: =?gb2312?q?Jiahao=20Wang?= <jiahaow@yahoo.com.cn>
cc: pim@catarina.usc.edu
Subject: Re: [pim] about PMBR 
In-Reply-To: Message from =?gb2312?q?Jiahao=20Wang?= <jiahaow@yahoo.com.cn> 
   of "Fri, 26 Apr 2002 11:34:17 +0800." <20020426033417.25804.qmail@web15004.mail.bjs.yahoo.com> 
From: Pavlin Radoslavov <pavlin@icir.org>
Sender: pim-admin@catarina.usc.edu
Errors-To: pim-admin@catarina.usc.edu
X-BeenThere: pim@catarina.usc.edu
X-Mailman-Version: 2.0.8
Precedence: bulk
List-Help: <mailto:pim-request@catarina.usc.edu?subject=help>
List-Post: <mailto:pim@catarina.usc.edu>
List-Subscribe: <http://catarina.usc.edu/mailman/listinfo/pim>,
	<mailto:pim-request@catarina.usc.edu?subject=subscribe>
List-Id: <pim.catarina.usc.edu>
List-Unsubscribe: <http://catarina.usc.edu/mailman/listinfo/pim>,
	<mailto:pim-request@catarina.usc.edu?subject=unsubscribe>
List-Archive: <http://catarina.usc.edu/pipermail/pim/>
Date: Thu, 25 Apr 2002 22:06:45 -0700

> as MSDP/MBGP, and Cisco has implemented it. The source
> codes of MrouteD and PimD are written by USC, they are

An (out-of-topic) clarification. Mrouted was not written in USC;
rather, various pieces of code from mrouted have been reused in
pimd (in particular, most of the things that are DVMRP and PIM-SM
independent such as IGMP and UNIX kernel interaction).

FreeBSD's mrouted manual page says that the authors of mrouted are
Steve Deering, Ajit Thyagarajan, Bill Fenner (I guess in order of
appearance :)

Pavlin

> very similar, therefore, it is easy to touch PIMD
> after touching MroutD.
_______________________________________________
pim mailing list
pim@catarina.usc.edu
http://catarina.usc.edu/mailman/listinfo/pim


