Thread (41 messages) 41 messages, 8 authors, 2013-08-09

RE: IGMP Unsolicited Report Interval too long for IGMPv3?

From: Lukas Tribus <hidden>
Date: 2013-07-22 22:12:44

Date: Mon, 22 Jul 2013 17:18:55 -0400
quoted
I would guess that this 10s has come from IGMPv2 RFC2236, which was
reduced to 1s in IGMPv3 RFC3376.
Reducing the timeout does not solve the problem you are encountering, as
any packet loss will still result in a 1 second delay.
Packet loss will always result in a delay and I think William is well aware
of that.

off-topic: 1 second is not a problem in IPTV, 10 seconds are ([1]).


The correct approach is to queue the IGMP multicast join with a higher
priority than other traffic in the system so that the requests are not
lost due to congestion of a single queue.
While this certainly makes sense, congestion is not the only reason for
packet loss. There is no way to fix packet loss in lower network layers,
like ADSL, satellite links or IPoAC.

Improving retransmission by making it more predictable, bringing it closer
to RFC proposals and real life problems makes a lot of sense, imho. This
includes setting TC_PRIO_CONTROL, but I'm not sure it will fix Williams use
case.


lukas

[1] http://en.wikipedia.org/wiki/Zap_time 		 	   		  
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help