Re: mboned: RE: suggestion for simplifying IGMPV3/MLDV2 to discard EXCLUDEmode

Thanks for the report, John.

> When and application joins a new (S,G) one expects to see two  
> (robustness variable)
> (if the querier is configured for default) IGMP packets with
> at least one record.

Right.

> If one carefully reads the spec para 4.2.12
> it would appear that this record should be a CHANGE-TO-INCLUDE-MODE.

An initial interface state of each host is (m, INCLUDE, NULL).
When the host changes the state (m, INCLUDE, s1) (due to (m,s1) join),
it sends ALLOW(m,s1), not TO_IN(m,s1), because the host's initial
filter mode has been INCLUDE.

> After that, the host should respond to IGMP general queries with MODE- 
> IS-INCLUDE
> records.

Correct.

>  I would argue that one only uses ALLOW-NEW-SOURCES when  
> you've already
> sent a report to join a specific group.  (NOT that I really care that  
> much, but
> its the only way I can justify to myself the CHANGE-TO- modes).

ALLOW is used to notify or add interesting sources.

> When FreeBSD 5.4 sends the initial IGMP report for a new (S,G) it sends
> only one (1) packet with a single record which is ALLOW-NEW-SOURCES.

The message is correct, but it should send the message rob_ver times.

> FreeBSD 5.4 responds to IGMPv3 general query with one (1) packets with
> one record MODE-IS-INCLUDE

Same of above.
--
Hitoshi Asaeda