RE: IGMP join/leave time variability

[Nat Ersoz]

This morning, after dealing with other bugs, I was able to verify (using
tcpdump) that

#define  IGMP_Initial_Report_Delay	5

fixed the "long" (1 sec) variable delay associated with the first igmp join
message.  This resolves a specific bug in our application (excessive IGMP
join delay as compared to an NT client).

Can we get something like this moved into future versions of ipv4/igmp.c?

Thanks,

Nat

-----Original Message-----
From: Torrey Hoffman [mailto:[e-mail]]
Sent: Thursday, July 26, 2001 10:47 AM
To: 'Alan Cox'; Nat Ersoz
Cc: [e-mail]
Subject: RE: IGMP join/leave time variability

Alan Cox wrote:
 
> Read the IGMP RFC documents they discuss in detail the cases 
> where time delays and randomness are needed and important. 

I'm one of Nat's co-workers, also looking at this problem.

RFC 2236, the IGMPv2 spec, states:
"
   When a host joins a multicast group, it should immediately transmit
   an unsolicited Version 2 Membership Report for that group, in case it
   is the first member of that group on the network.  To cover the
   possibility of the initial Membership Report being lost or damaged,
   it is recommended that it be repeated once or twice after short
   delays [Unsolicited Report Interval].  
"

the IGMP join.  In fact, a quick peek at the source confirms this: 
(net/ipv4/igmp.c):

#define IGMP_Initial_Report_Delay               (1*HZ)

/* IGMP_Initial_Report_Delay is not from IGMP specs!
 * IGMP specs require to report membership immediately after
 * joining a group, but we delay the first report by a
 * small interval. It seems more natural and still does not
 * contradict to specs provided this delay is small enough.
 */

But this "small interval" is actually very noticeable in our application.

I think we'll take it out of our version, and I believe it should be 
removed from the standard kernel.

Regards,

Torrey Hoffman