Re: IGMPv2 query processing by a v1 stack
Indranil Bhattacharya <[email protected]> Sun, 19 Jul 2009 02:44:17 +0530
| Newsgroups | gmane.ietf.magma |
|---|---|
| Message-ID | <[email protected]> |
Hi Subrata,
I think it is option 3. This is because once the V3 router
in the LAN receives the General Query from V1 router then it will switch
back to v1 mode and will start sending v1 query then onwards.
Thanks,
Indranil
On Sat, Jul 18, 2009 at 5:53 PM, Subrata Sa <[email protected]> wrote:
> Hello,
>
> An IGMPv1 stack has joined groups G1, G2 and G3 and it has received an
> IGMPv2 group (G1) specific query where none of the groups is "all
> hosts group". I can think of following possibilities as how the stack
> can handle the Query:
>
> 1. Process it as an IGMPv1 general query
>
> As per RFC 1112 (pages 11, 12)
> "
> Group Address
> In a Host Membership Query message, the group address field is zeroed
> when sent, ignored when received. (B)
> "
>
> So the IGMPv2 Query packet is treated as a general query and reports
> for ALL groups are sent.
>
> Cons: Groups (G2, G3) that are not queried are being reported.
>
> 2. Send report for only group G1
>
> Cons: any?
>
> 3. Drop it
>
> Cons: Router/ snooping switch cannot refresh its forwarding state for
> group G1 though sending a periodic v2 general query would do so.
>
> I'm tempted to go for the 3rd option. What to you think?
>
> -Subrata
> _______________________________________________
> magma mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/magma
>
_______________________________________________
magma mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/magma