RE: IGMP router behavior during LMQT period

Hi,
 
If host tracking is not implemented on router it makes sense to reset
the timers on reception of leave from H2. Since H2 showed its interest
by sending a report to the Query, Router has to refresh the group timer
and subsequent leave should be used to reset the timer to LMQT in
Router. 
 
"But how can the router distinguish between leaves from 2 different
hosts unless it is explicitly tracking hosts?"
Why should Router distinguish between leaves from 2 different hosts
(considering they are connected to same interface)? Router has to make a
decision whether to forward the streams for the multicast group or not
on that interface. Even if a host is leaving the group but some other
host is interested then it needs to forward the streams.  
 
I too faced a similar if not exact problem. The issue was that the group
timer was reset every time (until RV) the leave was received for a
multicast group. This resulted in higher leave latency. Higher the RV
value higher the leave latency. Resetting the timers only for first
leave solves the problem, but should it be done that way, can anyone
tell me? 
 
Does RFC 3376 section quoted below is referring to the same problem as I
have faced or is it referring to something else? 
 
8.14.1. Robustness Variable
 
   The Robustness Variable tunes IGMP to expected losses on a link.
   IGMPv3 is robust to (Robustness Variable - 1) packet losses, e.g., if
   the Robustness Variable is set to the default value of 2, IGMPv3 is
   robust to a single packet loss but may operate imperfectly if more
   losses occur.  On lossy subnetworks, the Robustness Variable should
   be increased to allow for the expected level of packet loss. However,
   increasing the Robustness Variable increases the leave latency of the
   subnetwork.  (The leave latency is the time between when the last
   member stops listening to a source or group and when the traffic
   stops flowing.)
 
 
Regards,
Sandeep.
 
________________________________

From: Princy Elizabeth [mailto:[email protected]] 
Sent: Tuesday, September 18, 2007 10:38 AM
To: [email protected]
Subject: [magma] IGMP router behavior during LMQT period
 
Hi,
 
I had a question regarding the expected router behavior during the last
member query timeout(LMQT) period. Consider 2 IGMPv3 hosts, H1 and H2
sitting on a LAN. Both have subscribed to a group G1. Host H1 now sends
a leave for the group G1. On receiving this the querier would reduce its
GMI to LMQT and schedule RV number of group specific queries to be sent,
one every last member query interval (LMQI) seconds. Since IGMPv3 state
change records are retransmitted by the host to guard against packet
loss, H1 would retransmit its Leave (TO_INCLUDE{}) after the unsolicited
report interval. What should the router do on receiving this leave? 
 
a) Should it reset the group timer LMQT again and again send out RV
number of group specific queries 
OR
b) Should it simply ignore this leave?
 
If it is (b), what should it do if it gets a leave from the other host
H2 also during this LMQT period(i.e. H2 leaves the group immediately
after sending an overriding join in response to the first group specific
query)? Shouldn't that be treated as described in (a)? But how can the
router distinguish between leaves from 2 different hosts unless it is
explicitly tracking hosts?
 
Thanks,
Princy
  
________________________________

Tonight's top picks. What will you watch tonight? Preview the hottest
shows
<http://us.rd.yahoo.com/tv/mail/tagline/tonightspicks/evt=48220/*http:/t
v.yahoo.com/%20%0d%0a>  on Yahoo! TV.

_______________________________________________
magma mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/magma