Re: [pim] IGMP query solicitation message

Harvey <flycoolman@gmail.com> Thu, 09 July 2020 15:57 UTC

Return-Path: <flycoolman@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 9A6723A0CA1 for <pim@ietfa.amsl.com>; Thu, 9 Jul 2020 08:57:51 -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 N4ffwJi3Nz4w for <pim@ietfa.amsl.com>; Thu, 9 Jul 2020 08:57:49 -0700 (PDT)
Received: from mail-lj1-x22b.google.com (mail-lj1-x22b.google.com [IPv6:2a00:1450:4864:20::22b]) (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 528183A0CA0 for <pim@ietf.org>; Thu, 9 Jul 2020 08:57:49 -0700 (PDT)
Received: by mail-lj1-x22b.google.com with SMTP id e8so3006423ljb.0 for <pim@ietf.org>; Thu, 09 Jul 2020 08:57:49 -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=nGzkUhqNbpfSeGuEduwEQ/RPM/+umuRtvhE/sm4YPt0=; b=A/MDdJLqKiFRZyDgAYkP+bzjcOXAgF4RripKlTZ/P1+pI22lE5jcqAY+aM6PubcBAJ GyDbF7095u7n6SITtrTDwC0uJY+a2G3FJOlNoVxArxfb2ItnPvl2cWnQfW0UT5Fd+Rmk RTNYLP1IVwlf/vGQTACS6kThoqAO8xS4kKtS7oQn4oH8MgADA9t/5bQYwYLruQfLTOvn WGwTTc0q605he6IWWlk6SVv38a6XgROHpDQN5LMHHuadVcstASgwN7Lk3iha2ZRWWavD m33G+Q/rbweMszoCo8cKQbkbP0/Pf5U/Jr0qV5VntIWTV0elFy0virapm7GCKg2NXBua L9Tw==
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=nGzkUhqNbpfSeGuEduwEQ/RPM/+umuRtvhE/sm4YPt0=; b=chrUHFeVTiXJu586ex6ruQzsHK8sTWSoI/GfnEpu/bLCWBqgVuaDpw+ugk6T8FqUzS 48Nisl+/YfKsrAygGpks4S3jfB6fKfwQ1r79oQcfx0BKvaUZiDwQtxJO8aFcoianQq3u LkGwKSmYDQiu9FzMghRc1Q1Qse6qnOZ5v4heEDGIV8iSBSzKHZc5WNIVPA2Hbx98p0WT 2z0mPbjR/WmsCf9wxMOZ2nBoxGsOvG8ZfMshmZB4+rFs7Tqit1c8zPRj5MJPMr34uJU7 4VChD9MuxO2SMiK0Lnnd2IGn3NardqJbcldOqMm2/cBriyREUCt//HcYojKc6HhSlxOT siPQ==
X-Gm-Message-State: AOAM532FwbOPBafw5BXOb5pkzcHAk7eOwUaFEdirCdUJX7U4VsTQQd6u IWAQins5cmcpYJI/vlJwonPQzNI4IwbIQdzXw6I=
X-Google-Smtp-Source: ABdhPJxoqWpLsMJyAoHUZQjyqmTJcZ/yzB1R/oSUGFOuYAm3xG7XVf7lBgIJXbrv33A15+f04PcCtzClo8lWZWRoUYg=
X-Received: by 2002:a2e:80cc:: with SMTP id r12mr32154406ljg.344.1594310267456; Thu, 09 Jul 2020 08:57:47 -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> <CAAG_SC-0uDyUijMyO0C-KiQW6yhsp6oh+vxaHTjfmzJeYuLqiw@mail.gmail.com>
In-Reply-To: <CAAG_SC-0uDyUijMyO0C-KiQW6yhsp6oh+vxaHTjfmzJeYuLqiw@mail.gmail.com>
From: Harvey <flycoolman@gmail.com>
Date: Thu, 9 Jul 2020 11:57:36 -0400
Message-ID: <CAL73O_zXQtKO2geKDJe3RqLrBpgXPMbEq9aJfdKkfauctCoUxQ@mail.gmail.com>
To: gangadhara reddy chavva <meetgangadhara@gmail.com>
Cc: pim@ietf.org
Content-Type: multipart/alternative; boundary="00000000000027522a05aa04497e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/pim/ZKISmn7HQZe7MzHdzmWPfYuoptM>
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 15:57:52 -0000

Hi Gangadhara,
Please refer to the RFC3376 with the supported messages, you would be able
to understand the related implementation on the IGMPv3.

https://tools.ietf.org/html/rfc3376



   There are two IGMP message types of concern to the IGMPv3 protocol
   described in this document:

      Type Number (hex)   Message Name
      -----------------   ------------

            0x11          Membership Query

            0x22          Version 3 Membership Report

   An implementation of IGMPv3 MUST also support the following three
   message types, for interoperation with previous versions of IGMP (see
   section 7 <https://tools.ietf.org/html/rfc3376#section-7>):

           0x12          Version 1 Membership Report    [RFC-1112
<https://tools.ietf.org/html/rfc1112>]

           0x16          Version 2 Membership Report    [RFC-2236
<https://tools.ietf.org/html/rfc2236>]

           0x17          Version 2 Leave Group          [RFC-2236
<https://tools.ietf.org/html/rfc2236>]


On Thu, Jul 9, 2020 at 5:20 AM gangadhara reddy chavva <
meetgangadhara@gmail.com> wrote:

> 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
>>>>
>>>