Re: [pim] IGMP query solicitation message

gangadhara reddy chavva <meetgangadhara@gmail.com> Thu, 09 July 2020 09:20 UTC

Return-Path: <meetgangadhara@gmail.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 138693A0998 for <pim@ietfa.amsl.com>; Thu, 9 Jul 2020 02:20:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ju3CG7merZuH for <pim@ietfa.amsl.com>; Thu, 9 Jul 2020 02:20:46 -0700 (PDT)
Received: from mail-io1-xd35.google.com (mail-io1-xd35.google.com [IPv6:2607:f8b0:4864:20::d35]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 90B373A0995 for <pim@ietf.org>; Thu, 9 Jul 2020 02:20:46 -0700 (PDT)
Received: by mail-io1-xd35.google.com with SMTP id v6so1593100iob.4 for <pim@ietf.org>; Thu, 09 Jul 2020 02:20:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=PHrBGQLo179FbKvxGrA45Rfj9KjqYyMSR/EV5tiIURE=; b=Ycmcmjf51samnSzDDxPD1YeFGUeV+o9loHHT27b5b6dp34vJ+3IyByYMSV/ibMkNCt S3DxyGvu6JLhRvwQ+Ywc1/F+jbHSbapUHjB4wQIY8qfR2nr8XyjqrFWYam12wQ/RjGWw GUS82b6AvwOMZeZ0kxi9DdHHHSrnGkRYSOPK9X+HWMPjgY3OEepen8P+Qbi5OlWd3ioS cuNEpZ29hqDJHytlU8i87IFrD/h+EpDt7iQOA1NFB/VoVySNxHEpDAHP2NuGjzKFo9W9 +0hC6rryGY5LMw0xwagDiZo07qlkJWyQPAlHICKr39G4mlrJJSN9L5hCi2t2hd39jkBo 1dww==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=PHrBGQLo179FbKvxGrA45Rfj9KjqYyMSR/EV5tiIURE=; b=pZdDtJlJzv6BQJjBYFknSH9aPUewc4/Nq5+0KvKiBFbKh+az9haYih9P3Kym2fVTHP 5wCjUimhNOyD5Hqf8TgyUHIdY6Qi6BtVwq2E/GFUWFDrS2bjPlxkLVQkTfH3cJbN4/49 8DO8C5ohPC2uDGNjts3CeFx45snDI1gQuLkbGVdVXBi/quastbtMqWeanQ3Ttwem63kU 7wAKMC9wRrR9eudD696Kkb/XQeeNaXOwCOmJWvC9RaoyR1lUfFBdSqKS2p/0ScYHY1bC 6lOFZcFFBg0XOYX9SNaegcRBlAdLc5NDrNqCPhxAnNjZzmS3bN85ydNgbFsrO3k3lQ1I aDSg==
X-Gm-Message-State: AOAM530VodaRiipCMAdvsj4F+IfZWz7jIR2pRqB5N2SWjxRAFAxD3JYl cg13aa73vN3SGtzKSxLZ52CrGdRxyoIGbNN9TZM=
X-Google-Smtp-Source: ABdhPJx60bUmaobh39AWcgh92Vfr9fDvVWy1/x8aeKvR6drXANwDSZt6b8HTEb3FzO4mwaHoO/E9il/4jH/+uqKl+fw=
X-Received: by 2002:a05:6638:d05:: with SMTP id q5mr69217444jaj.2.1594286445525; Thu, 09 Jul 2020 02:20:45 -0700 (PDT)
MIME-Version: 1.0
References: <mailman.109.1593716432.1395.pim@ietf.org> <CAL73O_wifxdnOa1yjh_atiSne6WrL6-V47a371UHBq0DmTsfSQ@mail.gmail.com> <CAAG_SC8M=NDVSKA6+i__cJNepLUkpjFXCrD=db9La0Nzgtt2vA@mail.gmail.com>
In-Reply-To: <CAAG_SC8M=NDVSKA6+i__cJNepLUkpjFXCrD=db9La0Nzgtt2vA@mail.gmail.com>
From: gangadhara reddy chavva <meetgangadhara@gmail.com>
Date: Thu, 9 Jul 2020 14:50:34 +0530
Message-ID: <CAAG_SC-0uDyUijMyO0C-KiQW6yhsp6oh+vxaHTjfmzJeYuLqiw@mail.gmail.com>
To: Harvey <flycoolman@gmail.com>
Cc: pim@ietf.org
Content-Type: multipart/alternative; boundary="000000000000417f5405a9febd08"
Archived-At: <https://mailarchive.ietf.org/arch/msg/pim/uW2vpFN6E-pyMieMUFVUZZSB1bQ>
Subject: Re: [pim] IGMP query solicitation message
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pim/>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Jul 2020 09:20:48 -0000

Hi Harvey,

I could see some vendors are using "Query solicitation" messages (sending
IGMP leave with group address 0.0.0.0 ) for faster convergence.
this might be working for IGMPv2. what is the method for IGMPv3 configured
snooping switches, they can still generate V2 leave and expected to receive
general query from router? or is there any IGMPv3 query solicitation
message.
please let me know how to proceed with this for IGMPv3 configured snooping
switches.

Thanks,
Gangadhar

On Sat, Jul 4, 2020 at 5:44 PM gangadhara reddy chavva <
meetgangadhara@gmail.com> wrote:

> Thanks Harvey for the information and the rfc links.
>
> Best Regards,
> Gangadhar
>
> On Fri, Jul 3, 2020 at 1:54 AM Harvey <flycoolman@gmail.com> wrote:
>
>> Hi Gangadhar,
>> The links below might be worth taking a look at.
>> https://tools.ietf.org/html/draft-ietf-idmr-igmp-mrdisc-10
>>
>>
>> http://stevehaskew.blogspot.com/2014/06/igmp-query-solicitation.html#:~:text=As%20well%20as%20flooding%20the,send%20out%20a%20General%20Query.
>>
>> Thanks,
>> Hongwei
>>
>>
>>> Date: Thu, 2 Jul 2020 13:07:07 +0530
>>> From: gangadhara reddy chavva <meetgangadhara@gmail.com>
>>> To: pim@ietf.org
>>> Subject: [pim] IGMP query solicitation message
>>> Message-ID:
>>>         <
>>> CAAG_SC-beE+fywnhovZiaAsS_9-bBLEPAz-MHEYihxnz9nRSdw@mail.gmail.com>
>>> Content-Type: text/plain; charset="utf-8"
>>>
>>> Hi,
>>>
>>> I could see a problem in igmp snooping functionality during port shut and
>>> unshut, RP switchover. During these triggers if the igmp snooping switch
>>> is
>>> not querier, it can't send query messages immediately to get the report
>>> message from the hosts. so snooping switch has to wait for the next
>>> querier
>>> query interval to learn the entries. Because of this there could be
>>> traffic
>>> drop/flood in the bridge domain.
>>>
>>> I could see some vendors are using query solicitation messages to trigger
>>> query messages immediately so the snooping switch can converge the
>>> traffic
>>> quickly.
>>>
>>> when i search for query solicitation message i couldn't find it in any
>>> ietf/rfc documents which suggest the same. Did I miss something?  Please
>>> let me know if there is any IETF/RFC document which suggests the same.
>>>
>>> Thanks,
>>> Gangadhar
>>> -------------- next part --------------
>>> An HTML attachment was scrubbed...
>>> URL: <
>>> https://mailarchive.ietf.org/arch/browse/pim/attachments/20200702/9221b844/attachment.htm
>>> >
>>>
>>> ------------------------------
>>>
>>> Subject: Digest Footer
>>>
>>> _______________________________________________
>>> pim mailing list
>>> pim@ietf.org
>>> https://www.ietf.org/mailman/listinfo/pim
>>>
>>