Re: igmpv3/mldv2 equivalent messages

> the TO_EX({}) and IS_EX({}) messages, i imagine that the more common 
> solicited IS_EX({}) messages (query responses should
> typically outnumber
> interface state changes) were chosen as the translation for IGMPv2 /
> IGMPv1 / MLDv1 reports.

Ok, so I'd like to expand the quesion, "there is no problem even if a
host uses TO_EX() instead of IS_EX() in any case". What do you think?

> messages.  to reduce unnecessary complexity and to standardize on a
> single message mapping, and in light of the protocol equivalence of

Good catch (for desigining the lite version:).

Thanks.
--
Hitoshi Asaeda