wg-multicast - Re: Default IGMP querier
Subject: All things related to multicast
List archive
- From: Hitoshi Asaeda <>
- To:
- Cc: ,
- Subject: Re: Default IGMP querier
- Date: Wed, 06 Nov 2002 18:41:04 +0100 (MET)
> I can't really think of any problems a "rogue querier" can cause.
> All IGMP routers listen to membership reports and time groups out
> independently.
I agree with John.
One of the examples;
http://www1.ietf.org/mail-archive/working-groups/magma/current/msg00027.html
But, unfortunately, as a protocol level, it's a little difficult to
avoid bogus or rogue queriers, since IMO some security addendum to
IGMP/MLD for this purpose would be burden.
Anyway, if looking for the solution, I believe there is some proposal
related to it in MSEC WG or something.
In addition, this is also just my opinion and isn't related to the
concerning point, though, using "lowest IP address" for selecting
querier is in any case poor. At least, querier selection should've
been done by another mechanism like PIM's DR selection mechanism. But
the problem is how to make a compatibility with old routers, which
only use a lowest IP address for selecting a querier...
--
Hitoshi Asaeda
p.s. My IGMPv3/MLDv2 host-side kernel implementations have a static
configuration option to set querier's IGMP/MLD version, in order to
fix the problem stated in a magma ML.
- Default IGMP querier, John Kristoff, 11/05/2002
- Re: Default IGMP querier, Tom Pusateri, 11/05/2002
- Re: Default IGMP querier, Hitoshi Asaeda, 11/06/2002
- Re: Default IGMP querier, John Zwiebel, 11/06/2002
- Re: Default IGMP querier, Hitoshi Asaeda, 11/07/2002
- Re: Default IGMP querier, John Kristoff, 11/07/2002
- Re: Default IGMP querier, Tom Pusateri, 11/05/2002
Archive powered by MHonArc 2.6.16.