<?xml version="1.0" encoding="US-ASCII"?> version='1.0' encoding='UTF-8'?>

<!DOCTYPE rfc SYSTEM "rfc2629.dtd">
<?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>
<?rfc toc="yes"?>
<?rfc sortrefs="yes"?>
<?rfc symrefs="yes"?>
<?rfc compact="yes"?>
<?rfc comments="yes"?>
<?rfc inline="yes"?> [
  <!ENTITY nbsp    "&#160;">
  <!ENTITY zwsp   "&#8203;">
  <!ENTITY nbhy   "&#8209;">
  <!ENTITY wj     "&#8288;">
]>

<rfc xmlns:xi="http://www.w3.org/2001/XInclude" category="std" docName="draft-ietf-pim-3376bis-12" number="9776" ipr="pre5378trust200902" updates="2236" obsoletes="3376"> obsoletes="3376" submissionType="IETF" consensus="true" xml:lang="en" tocInclude="true" sortRefs="true" symRefs="true" version="3">

  <front>
    <title abbrev="IGMPv3 Revision">Internet abbrev="IGMPv3">Internet Group Management Protocol, Version 3</title>
    <seriesInfo name="RFC" value="9776"/>
    <seriesInfo name="STD" value="100"/>
    <author fullname="Brian Haberman" initials="B." surname="Haberman" role="editor">
      <organization abbrev="JHU APL">Johns Hopkins University Applied Physics Lab</organization>
      <address>
        <email>brian@innovationslab.net</email>
      </address>
    </author>

    <date year="2025" month="March"/>

    <area>RTG</area>
    <workgroup>pim</workgroup>

<!-- [rfced] Please insert any keywords (beyond those that appear in
the title) for use on https://www.rfc-editor.org/search.
-->

<abstract>
   <t>IGMP

      <t>The Internet Group Management
   Protocol (IGMP) is the protocol used by IPv4 systems to
   report their IP multicast group memberships to neighboring multicast
   routers.  Version 3 of IGMP (IGMPv3) adds support for source filtering, that
   is, the ability for a system to report interest in receiving packets
   only from specific source addresses, or from all but specific
   source addresses, sent to a particular multicast address.  That
   information may be used by multicast routing protocols to avoid
   delivering multicast packets from specific sources to networks where
   there are no interested receivers.</t>
   <t>This document specifies Version 3 of the Internet Group Management
   Protocol, IGMPv3.  It is a revised
   version of the specification to include RFC 3376 that includes
   clarifications and fixes for errata in RFC 3376 errata, and it is backwards backward compatible
   with RFC 3376.</t>
      <t>This document updates RFC 2236 and obsoletes RFC 3376.</t>
    </abstract>
  </front>
  <middle>
    <section anchor="intro" title="Introduction"> numbered="true" toc="default">
      <name>Introduction</name>
      <t>The Internet Group Management Protocol (IGMP) is used by IPv4 systems
   (hosts and routers) to report their IP multicast group memberships to
   any neighboring multicast routers.  Note that an IP multicast router
   may itself be a member of one or more multicast groups, in which case
   it performs both the multicast router part of the protocol (to
   collect the membership information needed by its multicast routing
   protocol) and the group member part of the protocol (to inform
   itself and other, neighboring multicast routers of its memberships).</t>
      <t>IGMP is also used for other IP multicast management functions, using
   message types other than those used for group membership reporting.
   This document specifies only the group membership reporting functions
   and messages.</t>
      <t>This document specifies Version 3 of IGMP.  Version 1, specified in
   <xref target="RFC1112" />, format="default"/>, was the first widely-deployed widely deployed version and the first
   version to become an Internet Standard.  Version 2, specified in
   <xref target="RFC2236" />, format="default"/>, added support for low leave latency, that is, a
   reduction in the time it takes for a multicast router to learn that
   there are no longer any members of a particular group present on an
   attached network.  Version 3 adds support for source filtering,
   that is, the ability for a system to report interest in receiving
   packets only from specific source addresses, as required to support
   Source-Specific Multicast (SSM) <xref target="RFC3569" />, format="default"/>, or from all but specific source
   addresses, sent to a particular multicast address.  Version 3 is
      designed to be interoperable with Versions 1 and 2.</t>

      <t>This document uses SSM-aware "SSM-aware" to refer to systems
      that support Source-Specific Multicast (SSM) SSM as defined in <xref target="RFC4607" />.</t> format="default"/>.</t>

      <t>This document updates <xref target="RFC2236"/> target="RFC2236" format="default"/> as a proper implementation of Version 3 of IGMP IGMPv3 needs to implement Version 2 IGMPv2 Report and Leave message handling.</t>
      <t>This document obsoletes <xref target="RFC3376"/> target="RFC3376" format="default"/> as it provides clarifications and fixes
   for errata in RFC 3376. <xref target="RFC3376"/>. Detailed updates for those changes are described in <xref target="errata-details"/>.</t> target="errata-details" format="default"/>.</t>
      <section title="Conventions numbered="true" toc="default">
        <name>Conventions Used in This Document"> Document</name>
        <t>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", "<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>", "<bcp14>REQUIRED</bcp14>", "<bcp14>SHALL</bcp14>", "<bcp14>SHALL NOT</bcp14>",
   "<bcp14>SHOULD</bcp14>", "<bcp14>SHOULD NOT</bcp14>", "<bcp14>RECOMMENDED</bcp14>", "<bcp14>NOT RECOMMENDED</bcp14>", "<bcp14>MAY</bcp14>", and
   "OPTIONAL"
   "<bcp14>OPTIONAL</bcp14>" in this document are to be interpreted as described in
   BCP 14 <xref target="RFC2119"/> target="RFC2119" format="default"/> <xref target="RFC8174"/> target="RFC8174" format="default"/> when, and only when, they appear in all
   capitals, as shown here.</t>
      </section>
    </section>
    <section title="The numbered="true" toc="default">
      <name>The Service Interface for Requesting IP Multicast Reception"> Reception</name>
      <t>Within an IP system, there is (at least conceptually) a service
   interface used by upper-layer protocols or application programs to
   ask the IP layer to enable and disable reception of packets sent to
   specific IP multicast addresses.  In order to take full advantage of
   the capabilities of IGMPv3, a system's IP service interface must
   support the following operation:</t>

   <figure>
      <artwork><![CDATA[

      <artwork name="" type="pseudocode" align="left" alt=""><![CDATA[
      IPMulticastListen ( socket, interface, multicast-address,
                          filter-mode, source-list )
      ]]></artwork>
   </figure>

   <t>where:
   <list style="symbols"> )]]></artwork>

      <t>where:</t>
      <ul spacing="normal">
        <li>
          <t>"socket" is an implementation-specific parameter used to
     distinguish among different requesting entities (e.g., programs or
     processes) within the system; the socket parameter of BSD Unix
     system calls is a specific example.</t>
        </li>
        <li>
          <t>"interface" is a local identifier of the network interface on which
     reception of the specified multicast address is to be enabled or
     disabled.  Interfaces may be physical (e.g., an Ethernet interface)
     or virtual (e.g., the endpoint of a Frame Relay virtual circuit or
     the endpoint of an IP-in-IP "tunnel").  An implementation may allow
     a special "unspecified" value to be passed as the interface
     parameter, in which case the request would apply to the "primary"
     or "default" interface of the system (perhaps established by system
     configuration).  If reception of the same multicast address is
     desired on more than one interface, IPMulticastListen is invoked
     separately for each desired interface.</t>
        </li>
        <li>
          <t>"multicast-address" is the IP multicast address, or group, to which
     the request pertains.  If reception of more than one multicast
     address on a given interface is desired, IPMulticastListen is
     invoked separately for each desired multicast address.</t>
        </li>
        <li>
          <t>"filter-mode" may be either INCLUDE or EXCLUDE.  In INCLUDE mode,
     reception of packets sent to the specified multicast address is
     requested only from those IP source addresses listed in the
     source-list parameter.  In EXCLUDE mode, reception of packets sent
     to the given multicast address is requested from all IP source
     addresses except those listed in the source-list parameter.</t>
        </li>
        <li>
          <t>"source-list" is an unordered list of zero or more IP unicast
     addresses from which multicast reception is desired or not desired,
     depending on the filter mode. filter-mode.  An implementation MAY <bcp14>MAY</bcp14> impose a limit
     on the size of source lists, source-lists, but that limit MUST NOT <bcp14>MUST NOT</bcp14> be less than
     64 addresses per list.  When an operation causes the source list source-list
     size limit to be exceeded, the service interface MUST <bcp14>MUST</bcp14> return an
     error.</t>
   </list></t>
        </li>
      </ul>
      <t>For a given combination of socket, interface, and multicast address,
   only a single filter mode filter-mode and source list source-list can be in effect at any one
   time.  However, either the filter mode filter-mode or the source list, source-list, or both,
   may be changed by subsequent IPMulticastListen requests that specify
   the same socket, interface, and multicast address.  Each subsequent
   request completely replaces any earlier request for the given socket,
   interface
   interface, and multicast address.</t>

      <t>Previous versions of IGMP did not support source filters and had a
   simpler service interface consisting of Join and Leave operations to
   enable and disable reception of a given multicast address (from all
   sources) on a given interface.  The equivalent operations in the new
	   service interface follow:</t>
      <t>The Join operation is equivalent to:</t>
   <figure>
      <artwork><![CDATA[

      <artwork name="" type="pseudocode" align="left" alt=""><![CDATA[
      IPMulticastListen ( socket, interface, multicast-address,
                          EXCLUDE, {} )
      ]]></artwork>
   </figure> )]]></artwork>

      <t>and the Leave operation is equivalent to:</t>
   <figure>
      <artwork><![CDATA[

      <artwork name="" type="pseudocode" align="left" alt=""><![CDATA[
      IPMulticastListen ( socket, interface, multicast-address,
                          INCLUDE, {} )
      ]]></artwork>
   </figure> )]]></artwork>

      <t>where {} is an empty source list.</t> source-list.</t>
      <t>An example of an API providing the capabilities outlined in this
   service interface is in <xref target="RFC3678" />.</t> format="default"/>.</t>
    </section>
    <section title="Multicast numbered="true" toc="default">
      <name>Multicast Reception State Maintained by Systems"> Systems</name>
      <section title="Socket State"> numbered="true" toc="default">
        <name>Socket State</name>
        <t>For each socket on which IPMulticastListen has been invoked, the
   system records the desired multicast reception state for that socket.
	   That state conceptually consists of a set of records of the form:</t>

   <figure>
      <artwork><![CDATA[

        <artwork name="" type="pseudocode" align="left" alt=""><![CDATA[
      (interface, multicast-address, filter-mode, source-list)
      ]]></artwork>
   </figure> source-list)]]></artwork>

        <t>The socket state evolves in response to each invocation of
   IPMulticastListen on the socket, as follows:
   <list style="symbols">
        </t>
        <ul spacing="normal">
          <li>
            <t>If the requested filter mode filter-mode is INCLUDE and the requested source
     list source-list
     is empty, then the entry corresponding to the requested
     interface and multicast address is deleted if present.  If no such
	   entry is present, the request is ignored.</t>
          </li>
          <li>
            <t>If the requested filter mode filter-mode is EXCLUDE or the requested source
     list source-list
     is non-empty, then the entry corresponding to the requested
     interface and multicast address, if present, is changed to contain
     the requested filter mode filter-mode and source list. source-list.  If no such entry is
     present, a new entry is created, using the parameters specified in
	   the request.</t>
   </list></t>
          </li>
        </ul>
      </section>
      <section title="Interface State" anchor="if_state"> anchor="if_state" numbered="true" toc="default">
        <name>Interface State</name>
        <t>In addition to the per-socket multicast reception state, a system
     must also maintain or compute multicast reception state for each of
     its interfaces.  That state conceptually consists of a set of
	   records of the form:</t>

   <figure>
      <artwork><![CDATA[
        <artwork name="" type="pseudocode" align="left" alt=""><![CDATA[
        (multicast-address, filter-mode, source-list)
      ]]></artwork>
   </figure> source-list)]]></artwork>

        <t>At most most, one record per multicast-address exists for a given
     interface.  This per-interface state is derived from the per-socket
     state, but it may differ from the per-socket state when different
     sockets have differing filter modes filter-modes and/or source lists source-lists for the
     same multicast address and interface. For example, suppose one
     application or process invokes the following operation on socket
	   s1:</t>

   <figure>
      <artwork><![CDATA[
        <artwork name="" type="pseudocode" align="left" alt=""><![CDATA[
        IPMulticastListen ( s1, i, m, INCLUDE, {a, b, c} )
      ]]></artwork>
   </figure> )]]></artwork>

        <t>requesting reception on interface i of packets sent to multicast
     address m, only if they come from source a, b, or c.  Suppose
     another application or process invokes the following operation on
	   socket s2:</t>

   <figure>
      <artwork><![CDATA[
        <artwork name="" type="pseudocode" align="left" alt=""><![CDATA[
        IPMulticastListen ( s2, i, m, INCLUDE, {b, c, d} )
      ]]></artwork>
   </figure> )]]></artwork>

        <t>requesting reception on the same interface i of packets sent to the
     same multicast address m, only if they come from sources b, c, or
     d.  In order to satisfy the reception requirements of both sockets,
     it is necessary for interface i to receive packets sent to m from
     any one of the sources a, b, c, or d.  Thus, in this example, the
     reception state of interface i for multicast address m has filter
     mode filter-mode
     INCLUDE and source list source-list {a, b, c, d}.</t>
        <t>After a multicast packet has been accepted from an interface by the
     IP layer, its subsequent delivery to the application or process
     listening on a particular socket depends on the multicast reception
     state of that socket [and (and possibly also on other conditions, such
     as what transport-layer port the socket is bound to]. to).  So, in the
     above example, if a packet arrives on interface i, destined to
     multicast address m, with source address a, it will be delivered on
     socket s1 but not on socket s2.  Note that IGMP Queries and Reports
     are not subject to source filtering and must always be processed by
	hosts and routers.</t>

        <t>Filtering of packets based upon a socket's multicast reception
     state is a new feature of this service interface.  The previous
     service interface <xref target="RFC1112" /> format="default"/> described no filtering based upon
     multicast join state; rather, a join on a socket simply caused the
     host to join a group on the given interface, and packets destined
     for that group could be delivered to all sockets whether they had
	   joined or not.</t>
        <t>The general rules for deriving the per-interface state from the
     per-socket state are as follows:  For each distinct (interface,
     multicast-address) pair that appears in any socket state, a per-
     interface per-interface record is created for that multicast address on that
     interface.  Considering all socket records containing the same
     (interface, multicast-address) pair,
   <list style="symbols">
        </t>
        <ul spacing="normal">
          <li>
            <t>if any such record has a filter mode filter-mode of EXCLUDE, then the filter
     mode
            filter-mode of the interface record is EXCLUDE, and the source list source-list
            of the interface record is the intersection of the source lists source-lists
            of all socket records in EXCLUDE mode, minus those source
            addresses that appear in any socket record in INCLUDE mode.  For
            example, if the socket records for multicast address m on
            interface i are:

   <list style="hanging">
	   <t>from are:</t>
            <ul spacing="normal">
              <li>from socket s1:  ( i, m, EXCLUDE, {a, b, c, d} )</t>
	   <t>from )</li>
              <li>from socket s2:  ( i, m, EXCLUDE, {b, c, d, e} )</t>
	   <t>from )</li>
              <li>from socket s3:  ( i, m, INCLUDE, {d, e, f} )</t>
   </list>

   then )</li>
            </ul>
            <t>then the corresponding interface record on interface i is:

   <list style="hanging">
	   <t>( is:</t>
            <ul spacing="normal">
              <li>( m, EXCLUDE, {b, c} )</t>
   </list>

     If )</li>
            </ul>
            <t>If a fourth socket is added, such as:

   <list style="hanging">
	   <t>from as:</t>
            <ul spacing="normal">
              <li>from socket s4:  ( i, m, EXCLUDE, {} )</t>
   </list>

     then )</li>
            </ul>
            <t>then the interface record becomes:

   <list style="hanging">
	   <t>( becomes:</t>
            <ul spacing="normal">
              <li>( m, EXCLUDE, {} )</t>
	   </list></t> )</li>
            </ul>
          </li>
          <li>
            <t>if all such records have a filter mode filter-mode of INCLUDE, then the
     filter mode
            filter-mode of the interface record is INCLUDE, and the source list source-list
            of the interface record is the union of the source lists source-lists of
            all the socket records.  For example, if the socket records for
            multicast address m on interface i are:

   <list style="hanging">
	   <t>from are:</t>
            <ul spacing="normal">
              <li>from socket s1:  ( i, m, INCLUDE, {a, b, c} )</t>
	   <t>from )</li>
              <li>from socket s2:  ( i, m, INCLUDE, {b, c, d} )</t>
	   <t>from )</li>
              <li>from socket s3:  ( i, m, INCLUDE, {e, f} )</t>
   </list> )</li>
            </ul>
            <t> then the corresponding interface record on interface i is:

   <list style="hanging">
	   <t>(
            </t>
            <ul spacing="normal">
              <li>( m, INCLUDE, {a, b, c, d, e, f} )</t>
   </list>

     An )</li>
            </ul>
            <t>An implementation MUST NOT <bcp14>MUST NOT</bcp14> use an EXCLUDE
            interface record to represent a group when all sockets for this
            group are in INCLUDE state.  If system resource limits are reached
            when an interface state source list source-list is calculated, an error MUST
            <bcp14>MUST</bcp14> be returned to the application which that requested
            the operation.</t>
   </list></t>
          </li>
        </ul>
        <t>The above rules for deriving the interface state are (re-)evaluated
   whenever an IPMulticastListen invocation modifies the socket state by
   adding, deleting, or modifying a per-socket state record.  Note that
   a change  of socket state does not necessarily result in a change of
	   interface state.</t>
      </section>
    </section>
    <section title="Message Formats"> numbered="true" toc="default">
      <name>Message Formats</name>
      <t>IGMP messages are encapsulated in IPv4 datagrams, with an IP protocol
      number of 2.
      Every IGMP message described in this document is sent
   with an IP Time-to-Live of 1, IP Precedence of Internetwork Control
   (e.g., Type of Service 0xc0), and carries an IP Router Alert option
   <xref target="RFC2113" /> format="default"/> in its IP header.  IGMP message types are
   registered per <xref target="I-D.ietf-pim-3228bis"/>.</t> target="BCP57" format="default"/>.</t>
      <t>There are two IGMP message types of concern to the IGMPv3 protocol
      described in this document:</t>

   <texttable

      <table anchor="v3-msgs" title="New messages introduced align="center">
        <name>New Messages Introduced by IGMP3">
	   <ttcol align="center">Type IGMPv3</name>
        <thead>
          <tr>
            <th align="left">Type Number (hex)</ttcol>
	   <ttcol align="center">Message Name</ttcol>
	   <c>0x11</c><c>Membership Query</c>
	   <c>0x22</c><c>Version (hex)</th>
            <th align="left">Message Name</th>
          </tr>
        </thead>
        <tbody>
          <tr>
            <td align="left">0x11</td>
            <td align="left">Membership Query</td>
          </tr>
<!-- [rfced] We see the following discrepancies with the IGMP Type Numbers registry <https://www.iana.org/assignments/igmp-type-numbers>.  Please review and let us know if we may update the names to match what appears in the IANA registry.  In addition, please consider whether uses of "version X" should be updated for consistency as well.

From the IANA registry:
  0x22   IGMPv3 Membership Report
  Type 0x22 - IGMPv3 Membership Report

Table 1:
  0x22 	Version 3 Membership Report</c>
   </texttable> Report

From the IANA registry:
0x12 	IGMPv1 Membership Report
0x16 	IGMPv2 Membership Report
0x17 	IGMPv2 Leave Group

Table 2:
0x12 	Version 1 Membership Report
0x16 	Version 2 Membership Report
0x17 	Version 2 Leave Group

[bkh] Yes, the names can be updated to match
-->

          <tr>
            <td align="left">0x22</td>
            <td align="left">IGMPv3 Membership Report</td>
          </tr>
        </tbody>
      </table>
      <t>An implementation of IGMPv3 MUST <bcp14>MUST</bcp14> also support the following three
   message types, for interoperation with previous versions of IGMP (see
	   <xref target="interop" />):</t>

   <texttable format="default"/>):</t>
      <table anchor="legacy-msgs" title="Legacy align="center">
        <name>Legacy IGMP messages">
	   <ttcol align="center">Type Messages</name>
        <thead>
          <tr>
            <th align="left">Type Number (hex)</ttcol>
	   <ttcol align="center">Message Name</ttcol>
	   <ttcol align="center">Reference</ttcol>
	   <c>0x12</c><c>Version 1 (hex)</th>
            <th align="left">Message Name</th>
            <th align="left">Reference</th>
          </tr>
        </thead>
        <tbody>
          <tr>
            <td align="left">0x12</td>
            <td align="left">IGMPv1 Membership Report</c><c><xref Report</td>
            <td align="left">
              <xref target="RFC1112" /></c>
	   <c>0x16</c><c>Version 2 format="default"/></td>
          </tr>
          <tr>
            <td align="left">0x16</td>
            <td align="left">IGMPv2 Membership Report</c><c><xref Report</td>
            <td align="left">
              <xref target="RFC2236" /></c>
	   <c>0x17</c><c>Version 2 format="default"/></td>
          </tr>
          <tr>
            <td align="left">0x17</td>
            <td align="left">IGMPv2 Leave Group</c><c><xref Group</td>
            <td align="left">
              <xref target="RFC2236" /></c>
   </texttable> format="default"/></td>
          </tr>
        </tbody>
      </table>
      <t>Unrecognized message types MUST <bcp14>MUST</bcp14> be silently ignored.  Other message
   types may be used by newer versions or extensions of IGMP, by
	   multicast routing protocols, or for other uses.</t>
      <t>In this document, unless otherwise qualified, the capitalized words
   "Query" and "Report" refer to IGMP Membership Queries and IGMP
	   Version 3 IGMPv3
	   Membership Reports, respectively.</t>
      <section title="Membership numbered="true" toc="default">
        <name>Membership Query Message"> Message</name>
        <t>Membership Queries are sent by IP multicast routers to query the
   multicast reception state of neighboring interfaces.  Queries have
	   the following format:</t>
        <figure anchor="v3-qry" title="IGMPv3 anchor="v3-qry">
          <name>IGMPv3 Query Message">
      <artwork><![CDATA[ Message</name>
          <artwork name="" type="" align="left" alt=""><![CDATA[
     0                   1                   2                   3
     0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |  Type = 0x11  | Max Resp Code |           Checksum            |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |                         Group Address                         |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    | Flags |S| QRV |     QQIC      |     Number of Sources (N)     |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |                       Source Address [1]                      |
    +-                                                             -+
    |                       Source Address [2]                      |
    +-                              .                              -+
    .                               .                               .
    .                               .                               .
    +-                                                             -+
    |                       Source Address [N]                      |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      ]]></artwork>
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+]]></artwork>
        </figure>
        <section title="Max Resp Code" anchor="max_resp_code"> anchor="max_resp_code" numbered="true" toc="default">
          <name>Max Response Code</name>
          <t>The Max Resp Code field specifies the maximum time allowed before
          sending a responding report.  The actual time allowed, called the Max
   Resp Time,
          "Max Response Time", is represented in units of 1/10 second and is derived
          from the Max Resp Code as follows:</t>

   <t>If
	  <ul spacing="normal">
            <li>If Max Resp Code &lt; 128, Max Resp Response Time = Max Resp Code</t>

   <t>If Code</li>
            <li><t>If Max Resp Code >= &gt;= 128, Max Resp Code represents a
            floating-point value as follows:</t>

          <figure anchor="max-resp" title="Max anchor="max-resp">
            <name>Max Resp Code Representation">
      <artwork><![CDATA[ Representation</name>
            <artwork name="" type="" align="left" alt=""><![CDATA[
       0 1 2 3 4 5 6 7
      +-+-+-+-+-+-+-+-+
      |1| exp | mant  |
      +-+-+-+-+-+-+-+-+

   Max Resp Response Time = (mant | 0x10) << (exp + 3)
      ]]></artwork> 3)]]></artwork>
          </figure>
	    </li>
	  </ul>
          <t>Small values of Max Resp Response Time allow IGMPv3 routers to tune the "leave
   latency" (the time between the moment the last host leaves a group
   and the moment the routing protocol is notified that there are no
   more members).  Larger values, especially in the exponential range,
   allow tuning of the burstiness of IGMP traffic on a network.</t>
        </section>
        <section title="Checksum"> numbered="true" toc="default">
          <name>Checksum</name>
          <t>The Checksum field is the 16-bit one's complement of the one's complement
   sum of the whole IGMP message (the entire IP payload).  For computing
   the checksum, the Checksum field is set to zero.  When receiving
   packets, the checksum MUST <bcp14>MUST</bcp14> be verified before processing a packet
   <xref target="RFC1071" />.</t> format="default"/>.</t>
        </section>
        <section title="Group Address"> numbered="true" toc="default">
          <name>Group Address</name>

          <t>The Group Address field is set to zero when sending a General Query, Query
   and set to the IP multicast address being queried when sending a
   Group-Specific Query or Group-and-Source-Specific Group-and-Source Specific Query (see
   <xref target="src_addr_field" />, target="qry_vars" format="default"/>, below).</t>
        </section>
        <section title="Flags"> numbered="true" toc="default">
          <name>Flags</name>
          <t>The Flags field is a bitstring managed by an IANA the "IGMP Type Numbers" registry defined in
   <xref target="I-D.ietf-pim-3228bis"/>.</t> target="BCP57" format="default"/>.</t>
        </section>
        <section title="S numbered="true" toc="default">

          <name>S Flag (Suppress Router-Side Processing)"> Processing)</name>
          <t>When set to one, the S Flag flag indicates to any receiving multicast
   routers that they are to suppress the normal timer updates they
   perform upon hearing receiving a Query.  It does not, however, suppress the
   querier
   Querier election or the normal "host-side" processing of a Query that
   a router may be required to perform as a consequence of itself being
	   a group member.</t>
        </section>
        <section title="QRV numbered="true" toc="default">
          <name>QRV (Querier's Robustness Variable)"> Variable)</name>
          <t>If non-zero, the QRV field contains the [Robustness Variable] value
   used by the querier, i.e., the sender of the Query.  If the querier's
   [Robustness Variable] exceeds 7, the maximum value of the QRV field,
   the QRV is set to zero.  Routers adopt the QRV value from the most
   recently received Query as their own [Robustness Variable] value,
   unless that most recently received QRV was zero, in which case the
   receivers use the default [Robustness Variable] value specified in
   <xref target="robust" /> format="default"/> or a statically configured value.</t>
        </section>
        <section title="QQIC numbered="true" toc="default">
          <name>QQIC (Querier's Query Interval Code)"> Code)</name>
          <t>The Querier's Query Interval Code QQIC field specifies the [Query
   Interval] used by the querier.  The actual interval, called the
   Querier's
   "Querier's Query Interval (QQI), (QQI)", is represented in units of seconds
	   and is derived from the Querier's Query Interval Code QQIC as follows:</t>

   <t>If
	   <ul spacing="normal">
             <li>If QQIC &lt; 128, QQI = QQIC</t>

   <t>If QQIC</li>
             <li><t>If QQIC >= &gt;= 128, QQIC represents a floating-point value as follows:</t>
          <figure anchor="QQIC" title="QQIC Representation">
      <artwork><![CDATA[ anchor="QQIC">
            <name>QQIC Representation</name>
            <artwork name="" type="" align="left" alt=""><![CDATA[
       0 1 2 3 4 5 6 7
      +-+-+-+-+-+-+-+-+
      |1| exp | mant  |
      +-+-+-+-+-+-+-+-+

   QQI = (mant | 0x10) << (exp + 3)
      ]]></artwork> 3)]]></artwork>
          </figure>
	     </li>
	   </ul>
          <t>Multicast routers that are not the current querier adopt the QQI
   value from the most recently received Query as their own [Query
   Interval] value, unless that most recently received QQI was zero, in
   which case the receiving routers use the default [Query Interval]
	   value specified in <xref target="qry_int" />.</t> format="default"/>.</t>
        </section>
        <section title="Number numbered="true" toc="default">
          <name>Number of Sources (N)"> (N)</name>
          <t>The Number of Sources (N) field specifies how many source addresses
   are present in the Query.  This number is zero in a General Query or
   a Group-Specific Query, Group Specific Query and non-zero in a Group-and-Source-Specific Group-and-Source Specific
   Query.  This number is limited by the MTU of the network over which
   the Query is transmitted.  For example, on an Ethernet with an MTU of
   1500 octets, the IP header including the Router Alert option consumes
   24 octets, and the IGMP fields up to and including the Number of Sources
   (N) field consume 12 octets, leaving 1464 octets for source
   addresses, which limits the number of source addresses to 366 (1464/4).</t>
        </section>
        <section title="Source anchor="src_addr_field" numbered="true" toc="default">
          <name>Source Address [i]" anchor="src_addr_field"> [i]</name>
          <t>The Source Address [i] fields are a vector of n IP unicast addresses,
	   where n is the value in the Number of Sources (N) field.</t>
        </section>
        <section title="Additional Data"> numbered="true" toc="default">
          <name>Additional Data</name>
          <t>If the Packet Length field in the IP header of a received Query
   indicates that there are additional octets of data present, beyond
   the fields described here, IGMPv3 implementations MUST <bcp14>MUST</bcp14> include those
   octets in the computation to verify the received IGMP Checksum, Checksum but
   MUST
   <bcp14>MUST</bcp14> otherwise ignore those additional octets.  When sending a Query,
   an IGMPv3 implementation MUST NOT <bcp14>MUST NOT</bcp14> include additional octets beyond
	   the fields described here.</t>
        </section>
        <section title="Query Variants" anchor="qry_vars"> anchor="qry_vars" numbered="true" toc="default">
          <name>Query Variants</name>
          <t>There are three variants of the Query message:

   <list style="numbers"> Message:

          </t>
          <ol spacing="normal" type="1"><li>
              <t>A General Query is sent by a multicast router to learn the
      complete multicast reception state of the neighboring interfaces
      (that is, the interfaces attached to the network on which the
      Query is transmitted).  In a General Query, both the Group Address
	   field and the Number of Sources (N) field are zero.</t>
            </li>
            <li>
              <t>A Group-Specific Group Specific Query is sent by a multicast router to learn
      the reception state, with respect to a single multicast address,
      of the neighboring interfaces.  In a Group-Specific Group Specific Query, the
      Group Address field contains the multicast address of interest,
	   and the Number of Sources (N) field contains zero.</t>
            </li>
            <li>
              <t>A Group-and-Source-Specific Group-and-Source Specific Query is sent by a multicast router
      to learn if any neighboring interface desires reception of packets
      sent to a specified multicast address, from any of a specified
      list of sources.  In a Group-and-Source-Specific Group-and-Source Specific Query, the Group
      Address field contains the multicast address of interest, and the
      Source Address [i] fields contain the source address(es) of
	   interest.</t>
   </list></t>
            </li>
          </ol>
        </section>
        <section title="IP numbered="true" toc="default">
          <name>IP Destination Addresses for Queries"> Queries</name>
          <t>In IGMPv3, General Queries are sent with an IP destination address of
   224.0.0.1, the all-systems multicast address.  Group-Specific  Group Specific and
   Group-and-Source-Specific
   Group-and-Source Specific Queries are sent with an IP destination
   address equal to the  multicast address of interest.  However, a
   system MUST <bcp14>MUST</bcp14> accept and  process any Query whose IP Destination
   Address field contains any of the addresses (unicast or multicast)
	   assigned to the interface on which the Query arrives.</t>
        </section>
      </section>
      <section title="Version 3 numbered="true" toc="default">
        <name>IGMPv3 Membership Report Message">

   <t>Version 3 Message</name>
        <t>IGMPv3 Membership Reports are sent by IP systems to report (to
   neighboring routers) the current multicast reception state, or
   changes in the multicast reception state, of their interfaces.
	   Reports have the following format:</t>
        <figure anchor="v3-rpt" title="IGMPv3 anchor="v3-rpt">
          <name>IGMPv3 Report Message">
      <artwork><![CDATA[ Message</name>
          <artwork name="" type="" align="left" alt=""><![CDATA[
     0                   1                   2                   3
     0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |  Type = 0x22  |    Reserved   |           Checksum            |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |             Flags             |  Number of Group Records (M)  |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |                                                               |
    .                                                               .
    .                        Group Record [1]                       .
    .                                                               .
    |                                                               |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |                                                               |
    .                                                               .
    .                        Group Record [2]                       .
    .                                                               .
    |                                                               |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |                               .                               |
    .                               .                               .
    |                               .                               |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |                                                               |
    .                                                               .
    .                        Group Record [M]                       .
    .                                                               .
    |                                                               |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      ]]></artwork>
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+]]></artwork>
        </figure>
        <t>where each Group Record has the following internal format:</t>
        <figure anchor="v3-grp" title="IGMPv3 anchor="v3-grp">
          <name>IGMPv3 Report Group Record">
      <artwork><![CDATA[ Record</name>
          <artwork name="" type="" align="left" alt=""><![CDATA[
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |  Record Type  |  Aux Data Len |     Number of Sources (N)     |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |                       Multicast Address                       |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |                       Source Address [1]                      |
    +-                                                             -+
    |                       Source Address [2]                      |
    +-                                                             -+
    .                               .                               .
    .                               .                               .
    .                               .                               .
    +-                                                             -+
    |                       Source Address [N]                      |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |                                                               |
    .                                                               .
    .                         Auxiliary Data                        .
    .                                                               .
    |                                                               |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      ]]></artwork>
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+]]></artwork>
        </figure>
        <section title="Reserved"> numbered="true" toc="default">
          <name>Reserved</name>
          <t>The Reserved field is set to zero on transmission, transmission and ignored on
   reception.</t>
        </section>
        <section title="Checksum"> numbered="true" toc="default">
          <name>Checksum</name>
          <t>The Checksum field is the 16-bit one's complement of the one's complement
   sum of the whole IGMP message (the entire IP payload).  For computing
   the checksum, the Checksum field is set to zero.  When receiving
	   packets, the checksum MUST <bcp14>MUST</bcp14> be verified before processing a message.</t>
        </section>
        <section title="Flags"> numbered="true" toc="default">
          <name>Flags</name>
          <t>The Flags field is a bitstring managed by an IANA the "IGMP Type Numbers" registry defined in
   <xref target="I-D.ietf-pim-3228bis"/>.</t> target="BCP57" format="default"/>.</t>
        </section>
        <section title="Number numbered="true" toc="default">
          <name>Number of Group Records (M)"> (M)</name>
          <t>The Number of Group Records (M) field specifies how many Group
	   Records are present in this Report.</t>
        </section>
        <section title="Group Record"> numbered="true" toc="default">
          <name>Group Record</name>
          <t>Each Group Record is a block of fields containing information
   pertaining to the sender's membership in a single multicast group on
	   the interface from which the Report is sent.</t>
        </section>
        <section title="Record Type"> numbered="true" toc="default">
          <name>Record Type</name>
          <t>See <xref target="grp_rec_types" />, format="default"/>, below.</t>
        </section>
        <section title="Aux numbered="true" toc="default">
          <name>Aux Data Len"> Len</name>
          <t>The Aux Data Len field contains the length of the Auxiliary Data
   field in this Group Record, in units of 32-bit words.  It may contain
	   zero, to indicate the absence of any auxiliary data.</t>
        </section>
        <section title="Number numbered="true" toc="default">
          <name>Number of Sources (N)"> (N)</name>
          <t>The Number of Sources (N) field specifies how many source addresses
	   are present in this Group Record.</t>
        </section>
        <section title="Multicast Address"> numbered="true" toc="default">
          <name>Multicast Address</name>
          <t>The Multicast Address field contains the IP multicast address to
	   which this Group Record pertains.</t>
        </section>
        <section title="Source numbered="true" toc="default">
          <name>Source Address [i]"> [i]</name>
          <t>The Source Address [i] fields are a vector of n IP unicast addresses,
	   where n is the value in this record's Number of Sources (N) field.</t>
        </section>
        <section title="Auxiliary Data"> numbered="true" toc="default">
          <name>Auxiliary Data</name>
          <t>The Auxiliary Data field, if present, contains additional information
   pertaining to this Group Record.  The protocol specified in this
   document, IGMPv3, does not define any auxiliary data.  Therefore,
   implementations of IGMPv3 MUST NOT <bcp14>MUST NOT</bcp14> include any auxiliary data (i.e.,
   MUST
   <bcp14>MUST</bcp14> set the Aux Data Len field to zero) in any transmitted Group
   Record,
   Record and MUST <bcp14>MUST</bcp14> ignore any auxiliary data present in any received
   Group Record.  The semantics and internal encoding of the Auxiliary
   Data field are to be defined by any future version or extension of
	   IGMP that uses this field.</t>
        </section>
        <section title="Additional Data"> numbered="true" toc="default">
          <name>Additional Data</name>
          <t>If the Packet Length field in the IP header of a received Report
   indicates that there are additional octets of data present, beyond
   the last Group Record, IGMPv3 implementations MUST <bcp14>MUST</bcp14> include those
   octets in the computation to verify the received IGMP Checksum, Checksum but
   MUST
   <bcp14>MUST</bcp14> otherwise ignore those additional octets.  When sending a
   Report, an IGMPv3 implementation MUST NOT <bcp14>MUST NOT</bcp14> include additional octets
	   beyond the last Group Record.</t>
        </section>
        <section title="Group anchor="grp_rec_types" numbered="true" toc="default">
          <name>Group Record Types" anchor="grp_rec_types"> Types</name>
          <t>There are a number of different types of Group Records that may be
   included in a Report message:
   <list style="symbols">
          </t>
          <ul spacing="normal">
            <li>
              <t>A Current-State Record is sent by a system in response to a
              Query received on an interface.  It reports the current
              reception state of that interface, with respect to a single
              multicast address.  The Record Type of a Current-State Record
              may be one of the following two values:
     <list style="format %d - " counter="my_cnt"> values:</t>
              <ol group="my_cnt" spacing="normal" type="1">
		<li>
                  <t>MODE_IS_INCLUDE - indicates that the interface has a
           filter mode
                  filter-mode of INCLUDE for the specified multicast address.
                  The Source Address [i] fields in this Group Record contain
                  the interface's source list source-list for the specified multicast
                  address, if it is non-empty.</t>
                </li>
                <li>
                  <t>MODE_IS_EXCLUDE - indicates that the interface has a
           filter mode
                  filter-mode of EXCLUDE for the specified multicast
                  address. The Source Address [i] fields in this Group Record
                  contain the interface's source list source-list for the specified
                  multicast address, if it is non-empty. An SSM-aware host SHOULD NOT
                  <bcp14>SHOULD NOT</bcp14> send a MODE_IS_EXCLUDE record type
                  for multicast addresses that fall within the SSM address
                  range as they will be ignored by SSM-aware routers <xref target="RFC4604"/>.</t>
   </list></t>
                  target="RFC4604" format="default"/>.</t>
                </li>
              </ol>
            </li>
            <li>
              <t>A Filter-Mode-Change Record is sent by a system whenever a
              local invocation of IPMulticastListen causes a change of the filter mode
              filter-mode (i.e., a change from INCLUDE to EXCLUDE, or from
              EXCLUDE to
     INCLUDE), INCLUDE) of the interface-level state entry for a
              particular multicast address.  The Record is included in a
              Report sent from the interface on which the change occurred.
              The Record Type of a Filter-Mode-Change Record may be one of the
              following two values:
     <list style="format %d - " counter="my_cnt">
              </t>
              <ol group="my_cnt" spacing="normal" type="1"><li>
                  <t>CHANGE_TO_INCLUDE_MODE - indicates that the interface has
                  changed to INCLUDE filter mode filter-mode for the specified multicast
                  address.  The Source Address [i] fields in this Group Record
                  contain the interface's new
           source list source-list for the specified
                  multicast address, if it is non-empty.</t>
                </li>
                <li>
                  <t>CHANGE_TO_EXCLUDE_MODE - indicates that the interface has
                  changed to EXCLUDE filter mode filter-mode for the specified multicast
                  address. The Source Address [i] fields in this Group Record
                  contain the interface's new
           source list source-list for the specified
                  multicast address, if it is non-empty. An SSM-aware host SHOULD NOT
                  <bcp14>SHOULD NOT</bcp14> send a CHANGE_TO_EXCLUDE_MODE
                  record type for multicast addresses that fall within the SSM
                  address range.</t>
   </list></t>
                </li>
              </ol>
            </li>
            <li>
              <t>A Source-List-Change Record is sent by a system whenever a
              local invocation of IPMulticastListen causes a change of source list the source-list
              that is not coincident with a change of filter mode, the filter-mode, of the
              interface-level state entry for a particular multicast address.
              The Record is included in a Report sent from the interface on
              which the change occurred.  The Record Type of a
              Source-List-Change Record may be one of the following two
              values:
     <list style="format %d - " counter="my_cnt">
              </t>
              <ol group="my_cnt" spacing="normal" type="1">
		<li>
                  <t>ALLOW_NEW_SOURCES - indicates that the Source Address [i]
                  fields in this Group Record contain a list of the additional
                  sources that the system wishes to
               hear from, receive, for packets
                  sent to the specified multicast address.  If the change was
                  to an INCLUDE
               source list, source-list, these are the addresses that were
                  added to the list; if the change was to an EXCLUDE source
               list, source-list,
                  these are the addresses that were deleted from the
                  list.</t>
                </li>
                <li>
                  <t>BLOCK_OLD_SOURCES - indicates that the Source Address [i]
                  fields in this Group Record contain a list of the sources
                  that the system no longer wishes to
               hear from, receive, for packets
                  sent to the specified multicast address.  If the change was
                  to an INCLUDE
               source list, source-list, these are the addresses that were
                  deleted from the list; if the change was to an EXCLUDE source list,
                  source-list, these are the addresses that were added to the
                  list.</t>
   </list></t>
   </list></t>
                </li>
              </ol>
            </li>
          </ul>
          <t>If a change of source list source-list results in both allowing new sources
          and blocking old sources, then two Group Records are sent for the
          same multicast address, one of type ALLOW_NEW_SOURCES and one of
          type BLOCK_OLD_SOURCES.</t>
          <t>We use the term State-Change Record "State-Change Record" to refer to either a Filter-
	   Mode-Change Record or a Source-List-Change Record.</t>
          <t>Unrecognized Record Type values MUST <bcp14>MUST</bcp14> be silently ignored.</t>
        </section>
        <section title="IP numbered="true" toc="default">
          <name>IP Source Addresses for Reports"> Reports</name>
          <t>An IGMP report is sent with a valid unicast IPv4 source address for the
   destination subnet.  The 0.0.0.0 source address may be used by a
   system that has not yet acquired an IP address.  Note that the
   0.0.0.0 source address may simultaneously be used by multiple systems
   on a LAN.  Routers MUST <bcp14>MUST</bcp14> accept a report with a source address of
   0.0.0.0.</t>
        </section>
        <section title="IP numbered="true" toc="default">
          <name>IP Destination Addresses for Reports"> Reports</name>
          <t>Version 3 Reports are sent with an IP destination address of
   224.0.0.22, to which all IGMPv3-capable multicast routers listen.  A
   system that is operating in version 1 v1 or version 2 v2 compatibility
   modes sends version 1 v1 or version 2 v2 Reports to the multicast group
   specified in the Group Address field of the Report.  In addition, a
   system MUST <bcp14>MUST</bcp14> accept and process any version 1 v1 or version 2 v2 Report
   whose IP Destination Address field contains any of the addresses
   (unicast or multicast) assigned to the interface on which the Report
   arrives.</t>
        </section>
        <section title="Notation numbered="true" toc="default">
          <name>Notation for Group Records"> Records</name>
          <t>In the rest of this document, we use the following notation to
   describe the contents of a Group Record pertaining to a particular
	  multicast address:</t>

   <figure>
      <artwork><![CDATA[
      IS_IN
<ul spacing="compact">
      <li>IS_IN ( x )  -  Type MODE_IS_INCLUDE, source addresses x
      IS_EX x</li>
      <li>IS_EX ( x )  -  Type MODE_IS_EXCLUDE, source addresses x
      TO_IN x</li>
      <li>TO_IN ( x )  -  Type CHANGE_TO_INCLUDE_MODE, source addresses x
      TO_EX x</li>
      <li>TO_EX ( x )  -  Type CHANGE_TO_EXCLUDE_MODE, source addresses x
      ALLOW x</li>
      <li>ALLOW ( x )  -  Type ALLOW_NEW_SOURCES, source addresses x
      BLOCK x</li>
      <li>BLOCK ( x )  -  Type BLOCK_OLD_SOURCES, source addresses x
      ]]></artwork>
   </figure> x</li>
</ul>

          <t>where x is either:

   <list style="symbols"> either:</t>
          <ul spacing="normal">
            <li>
              <t>a capital letter (e.g., "A") to represent the set of source
		   addresses,
		   addresses or</t>
            </li>
            <li>
              <t>a set expression (e.g., "A+B"), where "A+B" means the union of sets
     A and B, "A*B" means the intersection of sets A and B, and "A-B"
		   means the removal of all elements of set B from set A.</t>
	   </list></t>
            </li>
          </ul>
        </section>
        <section title="Membership numbered="true" toc="default">
          <name>Membership Report Size"> Size</name>
          <t>If the set of Group Records required in a Report report does not fit within
   the size limit of a single Report message (as determined by the MTU
   of the network on which it will be sent), the Group Records are sent
	   in as many Report messages as needed to report the entire set.</t>
          <t>If a single Group Record contains so many source addresses that it
   does not fit within the size limit of a single Report message, and if its
   Type is not MODE_IS_EXCLUDE or CHANGE_TO_EXCLUDE_MODE, it is split
   into multiple Group Records, each containing a different subset of
   the source addresses and each sent in a separate Report message.  If
   its Type is MODE_IS_EXCLUDE or CHANGE_TO_EXCLUDE_MODE, a single Group
   Record is sent, containing as many source addresses as can fit, and</t>

   <t>the and
   the remaining source addresses are not reported; though the choice of
   which sources to report is arbitrary, it is preferable to report the
   same set of sources in each subsequent report, rather than reporting
	   different sources each time.</t>
        </section>
      </section>
    </section>
    <section title="Description anchor="grp_mbrs" numbered="true" toc="default">
      <name>Description of the Protocol for Group Members" anchor="grp_mbrs"> Members</name>
      <t>IGMP is an asymmetric protocol, specifying separate behaviors for
   group members -- that is, hosts or routers that wish to receive
   multicast packets -- and multicast routers.  This section describes
   the part of IGMPv3 that applies to all group members.  (Note that a
   multicast router that is also a group member performs both parts of
   IGMPv3, receiving and responding to its own IGMP message
   transmissions as well as those of its neighbors.  The multicast
	   router part of IGMPv3 is described in <xref target="mcast_rtrs" />.)</t> format="default"/>.)</t>
      <t>A system performs the protocol described in this section over all
   interfaces on which multicast reception is supported, even if more
	   than one of those interfaces is connected to the same network.</t>
      <t>For interoperability with multicast routers running older versions of
   IGMP, systems maintain a MulticastRouterVersion variable for each
   interface on which multicast reception is supported.  This section
   describes the behavior of group member systems on interfaces for
   which MulticastRouterVersion = 3.  The algorithm for determining
   MulticastRouterVersion, and the behavior for versions other than 3,
	   are described in <xref target="interop" />.</t> format="default"/>.</t>
      <t>The all-systems multicast address, 224.0.0.1, is handled as a special
   case.  On all systems -- that is is, all hosts and routers, routers including
   multicast routers -- reception of packets destined to the all-systems
   multicast address, from all sources, is permanently enabled on all
   interfaces on which multicast reception is supported.  No IGMP
	   messages are ever sent regarding the all-systems multicast address.</t>
      <t>There are two types of events that trigger IGMPv3 protocol actions on
	   an interface:

   <list style="symbols">
	   <t>a

      </t>
      <ul spacing="normal">
        <li>
          <t>A change of the interface reception state, caused by a local
		   invocation of IPMulticastListen.</t>

	   <t>reception
        </li>
        <li>
          <t>The reception of a Query.</t>
   </list></t>
        </li>
      </ul>
      <t>(Received IGMP messages of types other than Query are silently
   ignored, except as required for interoperation with earlier versions
	   of IGMP.)</t>
      <t>The following subsections describe the actions to be taken for each
   of these two cases.  In those descriptions, timer and counter names
   appear in square brackets.  The default values for those timers and
	   counters are specified in <xref target="timers" />.</t> format="default"/>.</t>
      <section title="Action numbered="true" toc="default">
        <name>Action on Change of Interface State"> State</name>
        <t>An invocation of IPMulticastListen may cause the multicast reception
   state of an interface to change, according to the rules in
   <xref target="if_state" />. format="default"/>.  Each such change affects the per-interface entry for a single
	   multicast address.</t>
        <t>A change of interface state causes the system to immediately transmit
   a State-Change Report from that interface.  The type and contents of
   the Group Record(s) in that Report are determined by comparing the
   filter mode
   filter-mode and source list source-list for the affected multicast address before
   and after the change, according to the table below. <xref target="state-change-record"/>.  If no interface
   state existed for that multicast address before the change (i.e., the
   change consisted of creating a new per-interface record), or if no
   state exists after the change (i.e., the change consisted of deleting
   a per-interface record), then the "non-existent" state is considered
	to have a filter mode filter-mode of INCLUDE and an empty source list.</t>

   <texttable>
	   <ttcol align="center">Old State</ttcol>
	   <ttcol align="center">New State</ttcol>
	   <ttcol align="center">State-Change Record Sent</ttcol>
	   <c>INCLUDE (A)</c><c>INCLUDE (B)</c><c>ALLOW source-list.</t>

<table anchor="state-change-record" align="center">
  <name>Transmitted Group Records for State Changes</name>
          <thead>
            <tr>
              <th align="left">Old State</th>
              <th align="left">New State</th>
              <th align="left">State-Change Record Sent</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left">INCLUDE (A)</td>
              <td align="left">INCLUDE (B)</td>
              <td align="left">ALLOW (B-A), BLOCK (A-B)</c>
	   <c>EXCLUDE (A)</c><c>EXCLUDE (B)</c><c>ALLOW (A-B)</td>
            </tr>
            <tr>
              <td align="left">EXCLUDE (A)</td>
              <td align="left">EXCLUDE (B)</td>
              <td align="left">ALLOW (A-B), BLOCK (B-A)</c>
	   <c>INCLUDE (A)</c><c>EXCLUDE (B)</c><c>TO_EX (B)</c>
	   <c>EXCLUDE (A)</c><c>INCLUDE (B)</c><c>TO_IN (B)</c>
   </texttable> (B-A)</td>
            </tr>
            <tr>
              <td align="left">INCLUDE (A)</td>
              <td align="left">EXCLUDE (B)</td>
              <td align="left">TO_EX (B)</td>
            </tr>
            <tr>
              <td align="left">EXCLUDE (A)</td>
              <td align="left">INCLUDE (B)</td>
              <td align="left">TO_IN (B)</td>
            </tr>
          </tbody>
        </table>
        <t>If the computed source list source-list for either an ALLOW or a BLOCK State-
   Change Record is empty, that record is omitted from the Report
	   message.</t>
        <t>To cover the possibility of the State-Change Report being missed by
   one or more multicast routers, it is retransmitted [Robustness
   Variable] - 1 more times, at intervals chosen at random from the
	   range (0, [Unsolicited Report Interval]).</t>
        <t>If more changes to the same interface state entry occur before all
   the retransmissions of the State-Change Report for the first change
   have been completed, each such additional change triggers the
	   immediate transmission of a new State-Change Report.</t>
        <t>The contents of the new transmitted report are calculated as follows.
   As was done with the first report, the interface state for the
   affected group before and after the latest change is compared.  The
   report records expressing the difference are built according to the
   table above.  However <xref target="state-change-record"/>.  However, these records are not transmitted in a message
   but instead are merged with the contents of the pending report, report to create
   the new State-Change report.  The rules for merging the difference
   report resulting from the state change and the pending report are
	   described below.</t>
        <t>The transmission of the merged State-Change Report terminates
   retransmissions of the earlier State-Change Reports for the same
   multicast address, and becomes the first of [Robustness Variable]
	   transmissions of State-Change Reports.</t>
        <t>Each time a source is included in the difference report calculated
   above, retransmission state for that source needs to be maintained
   until [Robustness Variable] State-Change reports Reports have been sent by
   the host.  This is done in order to ensure that a series of
	   successive state changes do not break the protocol robustness.</t>
        <t>If the interface reception-state change that triggers the new report
   is a filter-mode change, then the next [Robustness Variable] State-
   Change State-Change
   Reports will include a Filter-Mode-Change record. Record.  This
   applies even if any number of source-list changes occur in that
   period.  The host has to maintain retransmission state for the group
   until the [Robustness Variable] State-Change reports Reports have been sent.
   When [Robustness Variable] State-Change reports Reports with Filter-Mode-
   Change records Filter-Mode-Change
   Records have been transmitted after the last filter-mode
   change, and if source-list changes to the interface reception have
   scheduled additional reports, then the next State-Change report Report will
	   include Source-List-Change records.</t> Records.</t>
        <t>Each time a State-Change Report is transmitted, the contents are
	determined as follows.

	If the report should contain a Filter-Mode-
   Change record, then Filter-Mode-Change
   Record, and if the current filter-mode of the interface is
   INCLUDE, a TO_IN record is included in the report, otherwise report; otherwise, a TO_EX
   record is included.  If instead the report should contain Source-
   List-Change records, a Source-List-Change
   Record, an ALLOW and a BLOCK record are included.  The
	   contents of these records are built according to the table below.</t>

   <texttable>
	   <ttcol align="center">Record</ttcol>
	   <ttcol align="center">Sources Included</ttcol>
	   <c>TO_IN</c><c>All <xref target="sources_included"/>.</t>
        <table anchor="sources_included" align="center">
	 <name>Change Record Construction</name>
          <thead>
            <tr>
              <th align="left">Record</th>
              <th align="left">Sources Included</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left">TO_IN</td>
              <td align="left">All in the current interface state that must be forwarded</c>
	   <c>TO_EX</c><c>All forwarded</td>
            </tr>
            <tr>
              <td align="left">TO_EX</td>
              <td align="left">All in the current interface state that must be blocked</c>
	   <c>ALLOW</c><c>All blocked</td>
            </tr>
            <tr>
              <td align="left">ALLOW</td>
              <td align="left">All with retransmission state that must be forwarded</c>
	   <c>BLOCK</c><c>All forwarded</td>
            </tr>
            <tr>
              <td align="left">BLOCK</td>
              <td align="left">All with retransmission state that must be blocked</c>
   </texttable> blocked</td>
            </tr>
          </tbody>
        </table>
        <t>If the computed source list source-list for either an ALLOW or a BLOCK record is
	empty, that record is omitted from the State-Change report.</t>

   <t>Note: Report.</t>

      <aside><t>Note: When the first State-Change report Report is sent, the non-existent
   pending report to merge with, with can be treated as a source-change
   report Source-Change
   Report with empty ALLOW and BLOCK records (no sources have
	   retransmission state).</t> state).</t></aside>
      </section>
      <section title="Action numbered="true" toc="default">
        <name>Action on Reception of a Query"> Query</name>
        <t>When a system receives a Query, it does not respond immediately.
   Instead, it delays its response by a random amount of time, bounded
   by the Max Resp Response Time value derived from the Max Resp Code in the
   received Query message. Message.  A system may receive a variety of Queries on
   different interfaces and of different kinds (e.g., General Queries,
   Group-Specific
   Group Specific Queries, and Group-and-Source-Specific Group-and-Source Specific Queries), each
   of which may require its own delayed response.</t>
        <t>Before scheduling a response to a Query, the system must first
   consider previously scheduled pending responses and as, in many cases cases,
   it can schedule a combined response.  Therefore, the system must be able to
   maintain the following state:<list style="symbols"> state:</t>
        <ul spacing="normal">
          <li>
            <t>A timer per interface for scheduling responses to General Queries.</t>
          </li>
          <li>
            <t>A per-group and interface timer Interface Timer for scheduling responses to Group- Group
	   Specific and Group-and-Source-Specific Group-and-Source Specific Queries.</t>
          </li>
          <li>
            <t>A per-group and interface list of sources to be reported in the
	   response to a Group-and-Source-Specific Group-and-Source Specific Query.</t>
   </list></t>
          </li>
        </ul>
        <t>When a new Query with the Router-Alert Router Alert option arrives on an
   interface, provided the system has state to report, a delay for a
   response is randomly selected in the range (0, [Max Resp Response Time]) where
   Max Resp Response Time is derived from Max Resp Code in the received Query
   message.
   Message.  The following rules are then used to determine if a Report
   needs to be scheduled and the type of Report to schedule.  The rules
   are considered in order and only the first matching rule is applied.

   <list style="numbers">

        </t>
        <ol spacing="normal" type="1"><li>
            <t>If there is a pending response to a previous General Query
      scheduled sooner than the selected delay, no additional response
      needs to be scheduled.</t>
          </li>
          <li>
            <t>If the received Query is a General Query, the interface timer Interface Timer is
      used to schedule a response to the General Query after the
      selected delay.  Any previously pending response to a General
      Query is canceled.</t>
          </li>
          <li>
            <t>If the received Query is a Group-Specific Group Specific Query or a Group-and-
      Source-Specific
      Source Specific Query and there is no pending response to a
      previous Query for this group, then the group timer Group Timer is used to
      schedule a report.  If the received Query is a Group-and-Source- Group-and-Source
      Specific Query, the list of queried sources is recorded to be used
      when generating a response.</t>
          </li>
          <li>
            <t>If there already is a pending response to a previous Query
      scheduled for this group, and either the new Query is a Group- Group
      Specific Query or the recorded source-list associated with the
      group is empty, then the group source-list is cleared and a single
      response is scheduled using the group timer. Group Timer.  The new response is
      scheduled to be sent at the earliest of the remaining time for the
      pending report and the selected delay.</t>
          </li>
          <li>
            <t>If the received Query is a Group-and-Source-Specific Group-and-Source Specific Query and
      there is a pending response for this group with a non-empty
      source-list, then the group source list source-list is augmented to contain
      the list of sources in the new Query and a single response is
      scheduled using the group timer. Group Timer.  The new response is scheduled to
      be sent at the earliest of the remaining time for the pending
     report and the selected delay.</t>
   </list></t>
          </li>
        </ol>
        <t>When the timer in a pending response record expires, the system
   transmits, on the associated interface, one or more Report messages
	   carrying one or more Current-State Records (see <xref target="grp_rec_types" />), format="default"/>), as
   follows:<list style="numbers">
   follows:</t>
        <ol spacing="normal" type="1"><li>
            <t>If the expired timer is the interface timer Interface Timer (i.e., it is a pending
      response to a General Query), then one Current-State Record is
      sent for each multicast address for which the specified interface
	   has reception state, as described in <xref target="if_state" />. format="default"/>.  The Current-
      State Current-State Record carries the multicast address and its associated
      filter mode
      filter-mode (MODE_IS_INCLUDE or MODE_IS_EXCLUDE) and source list. source-list.
      Multiple Current-State Records are packed into individual Report
      messages, to the extent possible.
      <vspace blankLines="1" />
            </t>
            <t>
      This naive algorithm may result in bursts of packets when a system
      is a member of a large number of groups.  Instead of using a
      single interface timer, Interface Timer, implementations are recommended to spread
      transmission of such Report messages over the interval (0, [Max
      Resp
      Response Time]).  Note that any such implementation MUST <bcp14>MUST</bcp14> avoid the
      "ack-implosion" problem, i.e., MUST NOT <bcp14>MUST NOT</bcp14> send a Report immediately
      on reception of a General Query.</t>
          </li>
          <li>
            <t>If the expired timer is a group timer Group Timer and the list of recorded
      sources for the that group is empty (i.e., it is a pending
      response to a Group-Specific Group Specific Query), then if and only if the
      interface has reception state for that group address, a single
      Current-State Record is sent for that address.  The Current-State
      Record carries the multicast address and its associated filter
	   mode filter-mode
	   (MODE_IS_INCLUDE or MODE_IS_EXCLUDE) and source list.</t>

   <t>If source-list.</t>
          </li>
          <li>
            If the expired timer is a group timer Group Timer and the list of recorded
      sources for that group is non-empty (i.e., it is a pending
      response to a Group-and-Source-Specific Group-and-Source Specific Query), then if and only
      if the interface has reception state for that group address, the
      contents of the responding Current-State Record is determined from
      the interface state and the pending response record, as specified
	   in the following table:</t></list></t>

   <texttable>
	   <ttcol align="center">Per-Interface State</ttcol>
	   <ttcol align="center">Set <xref target="per-interface-state"/>.
          </li>
        </ol>
        <table anchor="per-interface-state" align="center">
	  <name>Current-State Record Construction</name>
          <thead>
            <tr>
              <th align="left">Per-Interface State</th>
              <th align="left">Set of Sources in the Pending Response Record</ttcol>
	   <ttcol align="center">Current-State Record</ttcol>
	   <c>INCLUDE (A)</c><c>B</c><c>IS_IN (A*B)</c>
	   <c>EXCLUDE (A)</c><c>B</c><c>IS_IN (B-A)</c>
   </texttable> Record</th>
              <th align="left">Current-State Record</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left">INCLUDE (A)</td>
              <td align="left">B</td>
              <td align="left">IS_IN (A*B)</td>
            </tr>
            <tr>
              <td align="left">EXCLUDE (A)</td>
              <td align="left">B</td>
              <td align="left">IS_IN (B-A)</td>
            </tr>
          </tbody>
        </table>
        <t>If the resulting Current-State Record has an empty set of source
	   addresses, then no response is sent.</t>
        <t>Finally, after any required Report messages have been generated, the
	   source lists
	   source-lists associated with any reported groups are cleared.</t>
      </section>
    </section>
    <section title="Description anchor="mcast_rtrs" numbered="true" toc="default">
      <name>Description of the Protocol for Multicast Routers" anchor="mcast_rtrs"> Routers</name>
      <t>The purpose of IGMP is to enable each multicast router to learn, for
   each of its directly attached networks, which multicast addresses are
   of interest to the systems attached to those networks.  IGMP version
   3  IGMPv3 adds the capability for a multicast router to also learn  which
   sources are of interest to neighboring systems, for packets sent to
   any particular multicast address.  The information gathered by IGMP
   is provided to whichever multicast routing protocol is being used by
   the router, in order to ensure that multicast packets are delivered
	   to all networks where there are interested receivers.</t>
      <t>This section describes the part of IGMPv3 that is performed by
   multicast routers.  Multicast routers may also themselves become
   members of multicast groups, and therefore also perform the group
	   member part of IGMPv3, as described in <xref target="grp_mbrs" />.</t> format="default"/>.</t>
      <t>A multicast router performs the protocol described in this section
   over each of its directly-attached directly attached networks.  If a multicast router
   has more than one interface to the same network, it only needs to
   operate this protocol over one of those interfaces.  On each
   interface over which this protocol is being run, the router MUST <bcp14>MUST</bcp14>
   enable reception of multicast address 224.0.0.22, 224.0.0.22 from all sources
   (and MUST <bcp14>MUST</bcp14> perform the group member part of IGMPv3 for that address on
	   that interface).</t>
      <t>Multicast routers need to know only that at least one system on an
   attached network is interested in packets to a particular multicast
   address from a particular source; a multicast router is not required
   to keep track of the interests of each individual neighboring system.
	   (However, see <xref target="suppression" /> point format="default"/>, item 1 for discussion.)</t>
      <t>IGMPv3 is backward compatible with previous versions of the IGMP
   protocol.  In order to remain backward compatible with older IGMP
   systems, IGMPv3 multicast routers MUST <bcp14>MUST</bcp14> also implement versions 1 and
	   2 of the protocol (see <xref target="interop" />).</t> format="default"/>).</t>
      <section title="Conditions numbered="true" toc="default">
        <name>Conditions for IGMP Queries"> Queries</name>
        <t>Multicast routers send General Queries periodically to request group
   membership information from an attached network.  These queries Queries are
   used to build and refresh the group membership state of systems on
   attached networks.  Systems respond to these queries Queries by reporting
   their group membership state (and their desired set of sources) with
	   Current-State Group Records in IGMPv3 Membership Reports.</t>
        <t>As a member of a multicast group, a system may express interest in
   receiving or not receiving traffic from particular sources.  As the
   desired reception state of a system changes, it reports these changes
   using Filter-Mode-Change Records or Source-List-Change Records.
   These records indicate an explicit state change in a group at a
   system in either the group record's source list Group Record's source-list or its filter-mode.
   When a group membership is terminated at a system or traffic from a
   particular source is no longer desired, a multicast router must query
   for other members of the group or listeners of the source before
	   deleting the group (or source) and pruning its traffic.</t>
        <t>To enable all systems on a network to respond to changes in group
	membership, multicast routers send specific queries. A Group- Group Specific
   Query is sent to verify there are no systems that desire
   reception of the specified group or to "rebuild" the desired
   reception state for a particular group.  Group-Specific  Group Specific Queries are
   sent when a router receives a State-Change record Record indicating a system
	   is leaving a group.</t>
        <t>A Group-and-Source Specific Query is used to verify there are no
   systems on a network which that desire to receive receiving traffic from a set of
   sources.  Group-and-Source Specific Queries list sources for a
   particular group which that have been requested to no longer be forwarded.
   This query is sent by a multicast router to learn if any systems
   desire reception of packets to the specified group address from the
   specified source addresses.  Group-and-Source Specific Queries are
   only sent in response to State-Change Records and never in response
	   to Current-State Records.  <xref target="qry_vars" /> format="default"/> describes each query in
	   more detail.</t>
      </section>
      <section title="IGMP numbered="true" toc="default">
        <name>IGMP State Maintained by Multicast Routers"> Routers</name>
        <t>Multicast routers implementing IGMPv3 keep state per group per
   attached network.  This group state consists of a filter-mode, a list
   of sources, and various timers.  For each attached network running
   IGMP, a multicast router records the desired reception state for that
   network.  That state conceptually consists of a set of records of the
   form:

   <figure>
      <artwork><![CDATA[

        </t>
        <artwork name="" type="pseudocode" align="left" alt=""><![CDATA[
  (multicast address, group timer, filter-mode, Group Timer, Router Filter Mode, (source records))
      ]]></artwork>
   </figure></t> records))]]></artwork>

 <t>Each source record is of the form:

   <figure>
      <artwork><![CDATA[ form:</t>

        <artwork name="" type="pseudocode" align="left" alt=""><![CDATA[
  (source address, source timer)
      ]]></artwork>
   </figure></t> Source Timer)]]></artwork>

        <t>If all sources within a given group are desired, an empty source
   record list is kept with filter-mode set to EXCLUDE.  This means
   hosts on this network want all sources for this group to be
   forwarded.  This is the IGMPv3 equivalent to a an IGMPv1 or IGMPv2 group
   join.</t>
        <section anchor="sec-rfm" title="Definition numbered="true" toc="default">
          <name>Definition of Router Filter-Mode"> Filter Mode</name>
          <t>To reduce internal state, IGMPv3 routers keep a filter-mode per group
   per attached network.  This filter-mode is used to condense the total
   desired reception state of a group to a minimum set such that all
   systems' memberships are satisfied.  This filter-mode may change in
   response to the reception of particular types of group records Group Records or
   when certain timer conditions occur.  In the following sections, we
   use the term "router filter-mode" Router Filter Mode to refer to the filter-mode of a
	   particular group within a router.  <xref target="rcv_rpts" /> format="default"/> describes the changes of a router filter-mode Router Filter Mode per group record Group Record received.</t>
          <t>Conceptually, when a group record Group Record is received, the router filter-mode Router Filter Mode
   for that group is updated to cover all the requested sources using
   the least amount of state.  As a rule, once a group record Group Record with a
   filter-mode of EXCLUDE is received, the router filter-mode Router Filter Mode for that
	   group will be EXCLUDE.</t>
          <t>When a router filter-mode Router Filter Mode for a group is EXCLUDE, the source record
   list contains two types of sources.  The first type is the set which that
   represents conflicts in the desired reception state; this set must be
   forwarded by some router on the network.  The second type is the set
   of sources which that hosts have requested to not be forwarded.  <xref target="rationale" /> format="default"/>
   describes the reasons for keeping two different sets when in EXCLUDE
	   mode.</t>
          <t>When a router filter-mode Router Filter Mode for a group is INCLUDE, the source record
   list is the list of sources desired for the group.  This is the total
   desired set of sources for that group.  Each source in the source
	   record list must be forwarded by some router on the network.</t>
          <t>Because a reported group record Group Record with a filter-mode of EXCLUDE will
   cause a router to transition its filter-mode for that group to
   EXCLUDE, a mechanism for transitioning a router's filter-mode back to
   INCLUDE must exist.  If all systems with a group record Group Record in EXCLUDE
   filter-mode cease reporting, it is desirable for the router filter-
   mode Router Filter
   Mode for that group to transition back to INCLUDE mode.  This
   transition occurs when the group timer Group Timer expires and is explained in
	   detail in <xref target="fltr_modes" />.</t> format="default"/>.</t>
        </section>
        <section title="Definition numbered="true" toc="default">
          <name>Definition of Group Timers"> Timers</name>
          <t>The group timer Group Timer is only used when a group is in EXCLUDE mode and it
   represents the time for the filter-mode of the group to expire and
   switch to INCLUDE mode.  We define a group timer Group Timer as a decrementing
   timer with a lower bound of zero kept per group per attached network.
   Group timers are updated according to the types of group records Group Records
	   received.</t>
          <t>A group timer Group Timer expiring when a router filter-mode Router Filter Mode for the group is
   EXCLUDE means there are no listeners on the attached network in
   EXCLUDE mode.  At this point, a router will transition to INCLUDE
	   filter-mode.  <xref target="fltr_modes" /> format="default"/> describes the actions taken when a group
	   timer Group
	   Timer expires while in EXCLUDE mode.</t>

   <t>The following table
          <t><xref target="group-timer"/> summarizes the role of the group timer. Group Timer.
   <xref target="rcv_rpts" /> format="default"/> describes the details of setting the group timer Group Timer per type of
	   group record
	   Group Record received.</t>
   <texttable>
      <ttcol align="center">Group Filter-Mode</ttcol>
      <ttcol align="center">Group Timer Value</ttcol>
      <ttcol align="center">Actions/Comments</ttcol>
      <c>INCLUDE</c><c>Timer >= 0</c><c>All
           <table anchor="group-timer" align="center">
	     <name>Group Timer Actions</name>
            <thead>
              <tr>
                <th align="left">Group Filter-Mode</th>
                <th align="left">Group Timer Value</th>
                <th align="left">Actions/Comments</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td align="left">INCLUDE</td>
                <td align="left">Timer &gt;= 0</td>
                <td align="left">All members in INCLUDE mode.</c>
      <c>EXCLUDE</c><c>Timer > 0</c><c>At mode.</td>
              </tr>
              <tr>
                <td align="left">EXCLUDE</td>
                <td align="left">Timer &gt; 0</td>
                <td align="left">At least one member in EXCLUDE mode.</c>
      <c>EXCLUDE</c><c>Timer mode.</td>
              </tr>
              <tr>
                <td align="left">EXCLUDE</td>
                <td align="left">Timer == 0</c>
      <c>No 0</td>
                <td align="left">No more listeners to group.  If all source timers have expired expired, then
	      delete Group Record.  If there are still source record timers running,
	      switch to INCLUDE filter-mode using those source records with running
	      timers as the INCLUDE source record state.</c>
   </texttable> state.</td>
              </tr>
            </tbody>
          </table>
        </section>
        <section title="Definition numbered="true" toc="default">
          <name>Definition of Source Timers"> Timers</name>
          <t>A source timer Source Timer is kept per source record and is a decrementing timer
   with a lower bound of zero.  Source timers are updated according to
   the type and filter-mode of the group record Group Record received.  Source timers
   are always updated (for a particular group) whenever the source is
   present in a received record for that group.  <xref target="rcv_rpts" /> format="default"/> describes
   the setting of source timers per type of group records Group Records received.</t>
          <t>A source record with a running timer with a router filter-mode Router Filter Mode for
   the group of INCLUDE means that there is currently one or more
   systems (in INCLUDE filter-mode) which that desire to receive that source.
   If a source timer Source Timer expires with a router filter-mode Router Filter Mode for the group of
   INCLUDE, the router concludes that traffic from this particular
   source is no longer desired on the attached network, network and deletes the
   associated source record.</t>
          <t>Source timers are treated differently when a router filter-mode Router Filter Mode for a
   group is EXCLUDE.  If a source record has a running timer with a
   router filter-mode
   Router Filter Mode for the group of EXCLUDE, it means that at least
   one system desires the source.  It should therefore be forwarded by a
   router on the network.  <xref target="rationale" /> format="default"/> describes the reasons for keeping
   state for sources that have been requested to be forwarded while in
   EXCLUDE state.</t>
          <t>If a source timer Source Timer expires with a router filter-mode Router Filter Mode for the group of
   EXCLUDE, the router informs the routing protocol that there is no
   longer a receiver on the network interested in traffic from this
   source.</t>
          <t>When a router filter-mode Router Filter Mode for a group is EXCLUDE, source records are
   only deleted when the group timer Group Timer expires.  <xref target="ss_fwd" /> format="default"/> describes the
   actions that should be taken dependent upon the value of a source
   timer.</t> Source
   Timer.</t>
        </section>
      </section>
      <section title="IGMPv3 anchor="ss_fwd" numbered="true" toc="default">
        <name>IGMPv3 Source-Specific Forwarding Rules" anchor="ss_fwd"> Rules</name>
        <t>When a multicast router receives a datagram from a source destined to
   a particular group, a decision has to be made whether to forward the
   datagram onto an attached network or not.  The multicast routing
   protocol in use is in charge of this decision, decision and should use the
   IGMPv3 information to ensure that all sources/groups desired on a
   subnetwork are forwarded to that subnetwork.  IGMPv3 information does
   not override multicast routing information; for example, if the
   IGMPv3 filter-mode group for G is EXCLUDE, a router may still forward
	   packets for excluded sources to a transit subnet.</t>
        <t>To summarize, the following table <xref target="forwarding_suggestions" /> describes the forwarding
   suggestions made by IGMP to the routing protocol for traffic
   originating from a source destined to a group.  It also summarizes
   the actions taken upon the expiration of a source timer Source Timer based on the
	   router filter-mode
	   Router Filter Mode of the group.</t>
   <texttable>
      <ttcol align="center">Group Filter-Mode</ttcol>
      <ttcol align="center">Group Timer Value</ttcol>
      <ttcol align="center">Action</ttcol>
      <c>INCLUDE</c><c>TIMER > 0</c><c>Suggest
           <table anchor="forwarding_suggestions" align="center">
	     <name>IGMP Forwarding Recommendations</name>
          <thead>
            <tr>
              <th align="left">Group Filter-Mode</th>
              <th align="left">Group Timer Value</th>
              <th align="left">Action</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left">INCLUDE</td>
              <td align="left">TIMER &gt; 0</td>
              <td align="left">Suggest to forward traffic from source</c>

      <c>INCLUDE</c><c>TIMER source.</td>
            </tr>
            <tr>
              <td align="left">INCLUDE</td>
              <td align="left">TIMER == 0</c><c>Suggest 0</td>
              <td align="left">Suggest to stop forwarding traffic from
	      source and remove source record.  If there are no more source
	      records for the group, delete group record.</c>

      <c>INCLUDE</c><c>No Group Record.</td>
            </tr>
            <tr>
              <td align="left">INCLUDE</td>
              <td align="left">No Source Elements</c><c>Suggest Elements</td>
              <td align="left">Suggest to not forward source</c>

      <c>EXCLUDE</c><c>TIMER > 0</c><c>Suggest source.</td>
            </tr>
            <tr>
              <td align="left">EXCLUDE</td>
              <td align="left">TIMER &gt; 0</td>
              <td align="left">Suggest to forward traffic from source</c>

      <c>EXCLUDE</c><c>TIMER source.</td>
            </tr>
            <tr>
              <td align="left">EXCLUDE</td>
              <td align="left">TIMER == 0</c><c>Suggest 0</td>
              <td align="left">Suggest to not forward traffic from source (DO NOT remove record)</c>

      <c>EXCLUDE</c><c>No record).</td>
            </tr>
            <tr>
              <td align="left">EXCLUDE</td>
              <td align="left">No Source Elements</c><c>Suggest Elements</td>
              <td align="left">Suggest to forward traffic from source</c>
   </texttable> source.</td>
            </tr>
          </tbody>
        </table>
      </section>
      <section title="Action anchor="rcv_rpts" numbered="true" toc="default">
        <name>Action on Reception of Reports" anchor="rcv_rpts"> Reports</name>
        <t>SSM-aware routers SHOULD <bcp14>SHOULD</bcp14> ignore records that contain multicast addresses
   in the SSM address range if the record type is MODE_IS_EXCLUDE or
   CHANGE_TO_EXCLUDE_MODE. SSM-aware routers SHOULD <bcp14>SHOULD</bcp14> ignore IGMPv1/IGMPv2
   Report and IGMPv2 DONE messages that contain multicast addresses in the SSM address range, SHOULD NOT <bcp14>SHOULD NOT</bcp14>
   use such Reports to establish IP forwarding state, and MAY <bcp14>MAY</bcp14> log an error if it receives
   such a message.</t>
        <section title="Reception numbered="true" toc="default">
          <name>Reception of Current-State Records"> Records</name>
          <t>When receiving Current-State Records, a router updates both its group
   and source timers.  In some circumstances, the reception of a type of
   group record
   Group Record will cause the router filter-mode Router Filter Mode for that group to
   change.  The table below  <xref target="router_state_8"/> describes the actions, with respect to state
   and timers that occur to a router's state upon reception of Current-
   State Records.</t>
          <t>The following notation is used to describe the updating of source
   timers.  The notation ( A, B ) will be used to represent the total
	  number of sources for a particular group, where</t>

   <figure>
      <artwork><![CDATA[

<ul>
<li> A = set of source records whose source timers > 0 (Sources that at
     least one host has requested to be forwarded) forwarded)</li>
<li> B = set of source records whose source timers = 0 (Sources that IGMP
will suggest to the routing protocol not to forward)
      ]]></artwork>
   </figure> forward)</li>
</ul>

          <t>Note that there will only be two sets when a router's filter-mode for
   a group is EXCLUDE.  When a router's filter-mode for a group is
   INCLUDE, a single set is used to describe the set of sources
   requested to be forwarded (e.g., simply (A)).</t>
          <t>In the following tables, Tables <xref target="router_state_8" format="counter"/> and <xref target="router_state_9" format="counter"/>, abbreviations are used for several variables
	   (all of which are described in detail in <xref target="timers" />). format="default"/>).  The variable
   GMI is an abbreviation for the Group Membership Interval, which is
   the time in which group memberships will time out.  The variable LMQT
   is an abbreviation for the Last Member Query Time, which is the total
   time spent after Last [Last Member Query Count Count] retransmissions.  LMQT
   represents the  "leave latency", leave latency or the difference between the
   transmission of a membership change and the change in the information
   given to the routing protocol.</t>
          <t>Within the "Actions" section of the router state tables, we use the
   notation 'A=J', which means that the set A of source records should
   have their source timers set to value J.  'Delete A' means that the
   set A of source records should be deleted.  'Group Timer=J' means
   that the Group Timer for the group should be set to value J.</t>

   <figure>
      <artwork><![CDATA[
Router State

   <table anchor="router_state_8" align="center">
     <name>Actions on Current-State Report Rec'd  New Reception</name>
     <thead>
       <tr>
	 <th>Router State</th>
	 <th>Report Rec'd</th>
	 <th>New Router State         Actions
------------   ------------  ----------------         -------

INCLUDE (A)    IS_IN (B)     INCLUDE (A+B)            (B)=GMI

INCLUDE (A)    IS_EX (B)     EXCLUDE (A*B,B-A)        (B-A)=0
                                                      Delete (A-B)
                                                      Group Timer=GMI

EXCLUDE (X,Y)  IS_IN (A)     EXCLUDE (X+A,Y-A)        (A)=GMI

EXCLUDE (X,Y)  IS_EX (A)     EXCLUDE (A-Y,Y*A)        (A-X-Y)=GMI
                                                      Delete (X-A)
                                                      Delete (Y-A)
                                                      Group Timer=GMI
      ]]></artwork>
   </figure>
   </section>

   <section title="Reception State</th>
         <th>Actions</th>
       </tr>
     </thead>
     <tbody>
       <tr>
	 <td>INCLUDE (A)</td>
	 <td>IS_IN (B)</td>
	 <td>INCLUDE (A+B)</td>
         <td>(B)=GMI</td>
       </tr>
       <tr>
	 <td>INCLUDE (A)</td>
	 <td>IS_EX (B)</td>
	 <td>EXCLUDE (A*B,B-A)</td>
         <td>(B-A)=0<br/>Delete (A-B)<br/>Group Timer=GMI</td>
       </tr>
       <tr>
	 <td>EXCLUDE (X,Y)</td>
	 <td>IS_IN (A)</td>
	 <td>EXCLUDE (X+A,Y-A)</td>
         <td>(A)=GMI</td>
       </tr>
       <tr>
	 <td>EXCLUDE (X,Y)</td>
	 <td>IS_EX (A)</td>
	 <td>EXCLUDE (A-Y,Y*A)</td>
         <td>(A-X-Y)=GMI<br/>Delete (X-A)<br/>Delete (Y-A)<br/>Group Timer=GMI</td>
       </tr>
     </tbody>
   </table>

        </section>
        <section anchor="slc_recs" numbered="true" toc="default">
          <name>Reception of Filter-Mode-Change and Source-List-Change Records" anchor="slc_recs"> Records</name>
          <t>When a change in the global state of a group occurs in a system, the
   system sends either a Source-List-Change Record or a Filter-Mode-
   Change Record for that group.  As with Current-State Records, routers
   must act upon these records and possibly change their own state to
   reflect the new desired membership state of the network.</t>
          <t>Routers must query sources that are requested to be no longer
   forwarded to a group.  When a router queries or receives a query for
   a specific set of sources, it lowers its source timers for those
   sources to a small interval of Last [Last Member Query Time Time] seconds.  If
   group records
   Group Records are received in response to the queries which express
   interest in receiving traffic from the queried sources, the
   corresponding timers are updated.</t>
          <t>Similarly, when a router queries a specific group, it lowers its
   group timer
   Group Timer for that group to a small interval of Last [Last Member Query
   Time
   Time] seconds.  If any group records Group Records expressing EXCLUDE mode interest
   in the group are received within the interval, the group timer Group Timer for
   the group is updated and the suggestion to the routing protocol to
   forward the group stands without any interruption.</t>
          <t>During a query period (i.e., Last [Last Member Query Time Time] seconds), the
   IGMP component in the router continues to suggest to the routing
   protocol that it forwards traffic from the groups or sources that it
   is querying.  It is not until after Last [Last Member Query Time Time] seconds
   without receiving a record expressing interest in the queried group
   or sources that the router may prune the group or sources from the
   network.</t>

   <t>The following table
          <t> <xref target="router_state_9"/> describes the changes in group state and the
   action(s) taken when receiving either Filter-Mode-Change or Source-
   List-Change Source-List-Change
   Records.  This table also describes the queries which that are
   sent by the querier when a particular report is received.</t>
          <t>We use the following notation for describing the queries which that are
   sent.  We use the notation 'Q(G)' to describe a Group-Specific Group Specific Query
   to G.  We use the notation 'Q(G,A)' to describe a Group-and-Source
   Specific Query to G with source-list A.  If source-list A is null as
   a result of the action (e.g., A*B) A*B), then no query is sent as a result
   of the operation.</t>
          <t>In order to maintain protocol robustness, queries sent by actions in
   the table below
   <xref target="router_state_9"/> need to be transmitted [Last Member Query Count]
   times, once every [Last Member Query Interval].</t>
          <t>If while scheduling new queries, queries there are already pending queries to
   be retransmitted for the same group, the new and pending queries have
   to be merged.  In addition, received host reports for a group with
   pending queries may affect the contents of those queries.
   <xref target="ssqs" /> format="default"/> describes the process of building and maintaining the state of
   pending queries.</t>

   <figure>
      <artwork><![CDATA[

   <table anchor="router_state_9" align="center">
     <name>Actions on Change Record Reception</name>
     <thead>
       <tr>
	 <th>Router State</th>
	 <th>Report Rec'd</th>
	 <th>New Router State   Report Rec'd New State</th>
	 <th>Actions</th>
       </tr>
     </thead>
     <tbody>
       <tr>
	 <td>INCLUDE (A)</td>
	 <td>ALLOW (B)</td>
	 <td>INCLUDE (A+B)</td>
         <td>(B)=GMI</td>
       </tr>
       <tr>
	 <td>INCLUDE (A)</td>
	 <td>BLOCK (B)</td>
	 <td>INCLUDE (A)</td>
         <td>Send Q(G,A*B)</td>
       </tr>
       <tr>
	 <td>INCLUDE (A)</td>
	 <td>TO_EX (B)</td>
	 <td>EXCLUDE (A*B,B-A)</td>
	 <td>(B-A)=0<br/>Delete (A-B)<br/>Send Q(G,A*B)<br/>Group Timer=GMI</td>
       </tr>
       <tr>
	 <td>INCLUDE (A)</td>
	 <td>TO_IN (B)</td>
	 <td>INCLUDE (A+B)</td>
         <td>(B)=GMI<br/>Send Q(G,A-B)</td>
       </tr>
       <tr>
	 <td>EXCLUDE (X,Y)</td>
	 <td>ALLOW (A)</td>
	 <td>EXCLUDE (X+A,Y-A)</td>
	 <td>(A)=GMI</td>
       </tr>
       <tr>
	 <td>EXCLUDE (X,Y)</td>
	 <td>BLOCK (A)</td>
	 <td>EXCLUDE (X+(A-Y),Y)</td>
	 <td>(A-X-Y)=Group Timer<br/>Send Q(G,A-Y)</td>
       </tr>
       <tr>
	 <td>EXCLUDE (X,Y)</td>
	 <td>TO_EX (A)</td>
	 <td>EXCLUDE (A-Y,Y*A)</td>
	 <td>(A-X-Y)=Group Timer<br/>Delete (X-A)<br/>Delete (Y-A)<br/>Send Q(G,A-Y)<br/>Group Timer=GMI</td>
       </tr>
       <tr>
	 <td>EXCLUDE (X,Y)</td>
	 <td>TO_IN (A)</td>
	 <td>EXCLUDE (X+A,Y-A)</td>
	 <td>(A)=GMI<br/>Send Q(G,X-A)<br/>Send Q(G)</td>
       </tr>
     </tbody>
   </table>

        </section>
      </section>
      <section anchor="fltr_modes" numbered="true" toc="default">
        <name>Switching Router State      Actions
------------   ------------ ----------------      -------

INCLUDE (A)    ALLOW (B)    INCLUDE (A+B)         (B)=GMI

INCLUDE (A)    BLOCK (B)    INCLUDE (A)           Send Q(G,A*B)

INCLUDE (A)    TO_EX (B)    EXCLUDE (A*B,B-A)     (B-A)=0
                                                  Delete (A-B)
                                                  Send Q(G,A*B) Filter Modes</name>
        <t>The Group Timer=GMI

INCLUDE (A)    TO_IN (B)    INCLUDE (A+B)         (B)=GMI
                                                  Send Q(G,A-B)

EXCLUDE (X,Y)  ALLOW (A)    EXCLUDE (X+A,Y-A)     (A)=GMI

EXCLUDE (X,Y)  BLOCK (A)    EXCLUDE (X+(A-Y),Y)   (A-X-Y)=Group Timer
                                                  Send Q(G,A-Y)

EXCLUDE (X,Y)  TO_EX (A)    EXCLUDE (A-Y,Y*A)     (A-X-Y)=Group Timer
                                                  Delete (X-A)
                                                  Delete (Y-A)
                                                  Send Q(G,A-Y)
                                                  Group Timer=GMI

EXCLUDE (X,Y)  TO_IN (A)    EXCLUDE (X+A,Y-A)     (A)=GMI
                                                  Send Q(G,X-A)
                                                  Send Q(G)
      ]]></artwork>
   </figure>
   </section>
   </section>

   <section title="Switching Router Filter-Modes" anchor="fltr_modes">

   <t>The group timer is used as a mechanism for transitioning the router
   filter-mode Router
   Filter Mode from EXCLUDE to INCLUDE.</t>
        <t>When a group timer Group Timer expires with a router filter-mode Router Filter Mode of EXCLUDE, a
   router assumes that there are no systems with a filter-mode of
   EXCLUDE present on the attached network.  When a router's filter-mode
   for a group is EXCLUDE and the group timer Group Timer expires, the router
   filter-mode Router
   Filter Mode for the group transitions to INCLUDE.</t>
        <t>A router uses source records with running source timers as its state
   for the switch to a filter-mode of INCLUDE.  If there are any source
   records with source timers greater than zero (i.e., requested to be
   forwarded), a router switches to filter-mode of INCLUDE using those
   source records.  Source records whose timers are zero (from the
   previous EXCLUDE mode) are deleted.</t>
        <t>For example, if a router's state for a group is EXCLUDE(X,Y) and the
   group timer
   Group Timer expires for that group, the router switches to filter-
   mode of INCLUDE with state INCLUDE(X).</t>
      </section>
      <section title="Action numbered="true" toc="default">
        <name>Action on Reception of Queries"> Queries</name>
        <section title="Timer Updates"> numbered="true" toc="default">
          <name>Timer Updates</name>
          <t>When a router sends or receives a query with a clear Suppress
   Router-Side Processing flag, it must update its timers to reflect the
   correct timeout values for the group or sources being queried.  The
   following table <xref target="timer_actions"/> describes the timer actions when sending or receiving
   a Group-Specific Group Specific or Group-and-Source Specific Query with the Suppress
	   Router-Side Processing S flag not set.</t>
   <texttable>
      <ttcol align="center">Query</ttcol>
      <ttcol align="center">Action</ttcol>
      <c>Q(G,A)</c><c>Source
   <table anchor="timer_actions" align="center">
     <name>Timer Updates on Query</name>
            <thead>
              <tr>
                <th align="left">Query</th>
                <th align="left">Action</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td align="left">Q(G,A)</td>
                <td align="left">Source Timer for sources in A are lowered to LMQT</c>
      <c>Q(G)</c><c>Group LMQT</td>
              </tr>
              <tr>
                <td align="left">Q(G)</td>
                <td align="left">Group Timer is lowered to LMQT</c>
   </texttable> LMQT</td>
              </tr>
            </tbody>
          </table>
          <t>When a router sends or receives a query with the Suppress Router-Side
   Processing S flag set, it will not update its timers.</t>
        </section>
        <section title="Querier Election"> numbered="true" toc="default">
          <name>Querier Election</name>
          <t>IGMPv3 elects a single querier per subnet using the same querier Querier
   election mechanism as IGMPv2, namely by IP address.  When a router
   receives a general query General Query with a lower IP address, it sets the Other-Querier-
   Present timer Other-Querier-Present
   Timer to Other [Other Querier Present Interval Interval] and ceases to send
   general queries on the network if it was the previously elected querier.
   After its Other-Querier Present timer Other-Querier-Present Timer expires, it should begin
   sending General Queries.</t>
          <t>If a router receives an older version general query, General Query, it MUST <bcp14>MUST</bcp14> use the oldest
   version of IGMP on the network.  For a detailed description of
	   compatibility issues between IGMP versions versions, see <xref target="interop" />.</t> format="default"/>.</t>
        </section>
        <section title="Building anchor="ssqs" numbered="true" toc="default">
          <name>Building and Sending Specific Queries" anchor="ssqs"> Queries</name>
          <section title="Building numbered="true" toc="default">
            <name>Building and Sending Group Specific Queries"> Queries</name>
            <t>When a table action "Send Q(G)" is encountered, then the group timer Group Timer
   must be lowered to LMQT.  The router must then immediately send a
   group specific query
   Group Specific Query as well as schedule [Last Member Query Count Count] -
   1] 1
   query retransmissions retransmission(s) to be sent every [Last Member Query
	   Interval] over [Last Member Query Time].</t>
            <t>When transmitting a group specific query, Group Specific Query, if the group timer Group Timer is
   larger than LMQT, the "Suppress Router-Side Processing" bit is set in
	   the query message.</t> Query Message.</t>
          </section>
          <section title="Building numbered="true" toc="default">

            <name>Building and Sending Group and Source Group-and-Source Specific Queries"> Queries</name>
            <t>When a table action "Send Q(G,X)" is encountered by a querier in the
	   table in <xref target="router_state_9"/> (<xref target="slc_recs" />, format="default"/>), the following actions must be performed for each of the sources in X of group G, with source timer the Source Timer larger than
   LMQT:
   <list style="symbols">
            </t>
            <ul spacing="normal">
              <li>
                <t>Set the number of retransmissions for each source to [Last Member Query Count].</t>
              </li>
              <li>
                <t>Lower source timer the Source Timer to LMQT.</t>
   </list></t>
              </li>
            </ul>
            <t>The router must then immediately send a group and source specific
   query Group-and-Source Specific
   Query as well as schedule [Last Member Query Count Count] - 1] 1 query
   retransmissions
   retransmission(s) to be sent every [Last Member Query Interval] over
   [Last Member Query Time].  The contents of these queries are
   calculated as follows.</t>
            <t>When building a group and source specific query Group-and-source Specific Query for a group G, two
   separate query messages Query Messages are sent for the group.  The first one has
   the "Suppress Router-Side Processing" bit set and contains all the
   sources with retransmission state and timers greater than LMQT.  The
   second has the "Suppress Router-Side Processing" bit clear and
   contains all the sources with retransmission state and timers lower
   or equal to LMQT.  If either of the two calculated messages does not
   contain any sources, then its transmission is suppressed.</t>

   <t>Note:
        <aside><t>Note: If a group specific query Group Specific Query is scheduled to be transmitted at the
   same time as a group and source specific query Group-and-Source Specific Query for the same group,
   then transmission of the group and source specific message Group-and-Source Specific Query Message with the
   "Suppress Router-Side Processing" bit set may be suppressed.</t> suppressed.</t></aside>
          </section>
        </section>
      </section>
    </section>
    <section title="Interoperation anchor="interop" numbered="true" toc="default">
      <name>Interoperation With Older Versions of IGMP" anchor="interop">

   <t>IGMP version 3 IGMP</name>
      <t>IGMPv3 hosts and routers interoperate with hosts and routers
   that have not yet been upgraded to IGMPv3.  This compatibility is
   maintained by hosts and routers taking appropriate actions depending
   on the versions of IGMP operating on hosts and routers within a
   network.</t>
      <section title="Query numbered="true" toc="default">
        <name>Query Version Distinctions"> Distinctions</name>
        <t>The IGMP version of a Membership Query message Message is determined as
   follows:
   <list style="empty">
        </t>
        <ul spacing="normal">
          <li>
            <t>IGMPv1 Query: length = 8 octets AND Max Resp Code field is zero</t>
          </li>
          <li>
            <t>IGMPv2 Query: length = 8 octets AND Max Resp Code field is non-zero</t>
          </li>
          <li>
            <t>IGMPv3 Query: length >= &gt;= 12 octets</t>
   </list></t>
          </li>
        </ul>
        <t>Query messages Messages that do not match any of the above conditions (e.g., a
   Query of length 10 octets) MUST <bcp14>MUST</bcp14> be silently ignored.</t>
      </section>
      <section title="Group numbered="true" toc="default">
        <name>Group Member Behavior"> Behavior</name>
        <section title="In numbered="true" toc="default">
          <name>In the Presence of Older Version Queriers"> Queriers</name>
          <t>In order to be compatible with older version routers, IGMPv3 hosts
   MUST
   <bcp14>MUST</bcp14> operate in version 1 v1 and version 2 v2 compatibility modes. IGMPv3
   hosts MUST <bcp14>MUST</bcp14> keep state per local interface regarding the compatibility mode of each attached network.  A host's compatibility mode is
   determined from the Host Compatibility Mode variable variable, which can be in
   one of three states:  IGMPv1, IGMPv2 IGMPv2, or IGMPv3.  This variable is
   kept per interface and is dependent on the version of General Queries
   heard
   received on that interface as well as the Older Version Querier Present
	   timers Older-Version-Querier-Present
	   Timer for the interface.</t>
          <t>In order to switch gracefully between versions of IGMP, hosts keep
   both an IGMPv1 Querier Present timer IGMPv1-Querier-Present Timer and an IGMPv2 Querier Present
   timer IGMPv2-Querier-Present
   Timer per interface.  IGMPv1 Querier Present  IGMPv1-Querier-Present Timer is set to Older [Older Version
   Querier Present Timeout Interval] seconds whenever an IGMPv1 Membership Query
   is received.  IGMPv2 Querier Present  IGMPv2-Querier-Present Timer is set to Older [Older Version Querier
	   Present Timeout Interval] seconds whenever an IGMPv2 General Query is received.</t>
          <t>The Host Compatibility Mode of an interface changes whenever an older
   version query (than the current compatibility mode) is heard received or when
   certain timer conditions occur.  When the IGMPv1 Querier Present
   timer IGMPv1-Querier-Present
   Timer expires, a host switches to Host Compatibility mode Mode of IGMPv2
   if it has a running IGMPv2 Querier Present timer.  If it does not
   have a running IGMPv2 Querier Present timer timer, then it switches to Host
   Compatibility of IGMPv3.  When the IGMPv2 Querier Present timer
	   expires, a host switches to Host Compatibility mode Mode of IGMPv3.</t>
          <t>The Host Compatibility Mode variable is based on whether an older
   version General query Query was heard received in the last Older [Older Version Querier
   Present Timeout Interval] seconds. The Host Compatibility mode Mode variable value MUST NOT <bcp14>MUST NOT</bcp14>
   be changed by an older version group-specific query. Group Specific Query.
   The Host Compatibility Mode is set depending on the following:</t>
   <texttable>
      <ttcol align="center">Host
   <table align="center">
     <name>Host Compatibility Mode</ttcol>
      <ttcol align="center">Timer State</ttcol>
      <c>IGMPv3 (default)</c><c>IGMPv2 Mode Settings</name>
            <thead>
              <tr>
                <th align="left">Host Compatibility Mode</th>
                <th align="left">Timer State</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td align="left">IGMPv3 (default)</td>
                <td align="left">IGMPv2 Querier Present not running and IGMPv1 Querier Present not running</c>
      <c>IGMPv2</c><c>IGMPv2 running</td>
              </tr>
              <tr>
                <td align="left">IGMPv2</td>
                <td align="left">IGMPv2 Querier Present running and IGMPv1 Querier Present not running</c>
      <c>IGMPv1</c><c>IGMPv1 running</td>
              </tr>
              <tr>
                <td align="left">IGMPv1</td>
                <td align="left">IGMPv1 Querier Present running</c>
   </texttable> running</td>
              </tr>
            </tbody>
          </table>
          <t>If a host receives a query which that causes its Querier Present timers to
   be updated and correspondingly its compatibility mode, it should
   switch compatibility modes immediately.</t>
          <t>When Host Compatibility Mode is IGMPv3, a host acts using the IGMPv3
   protocol on that interface.  When Host Compatibility Mode is IGMPv2,
   a host acts in IGMPv2 compatibility mode, using only the IGMPv2
   protocol, on that interface.  When Host Compatibility Mode is IGMPv1,
   a host acts in IGMPv1 compatibility mode, using only the IGMPv1
   protocol on that interface.</t>
          <t>An IGMPv1 router will send General Queries with the Max Resp Code set
   to 0.  This MUST <bcp14>MUST</bcp14> be interpreted as a value of 100 (10 seconds).</t>
          <t>An IGMPv2 router will send General Queries with the Max Resp Code set
   to the desired Max Resp Response Time, i.e., the full range of this field is
	   linear and the exponential algorithm described in <xref target="max_resp_code" /> format="default"/> is
   not used.</t>
          <t>Whenever a host changes its compatibility mode, it cancels all its
   pending response and retransmission timers.</t>
          <t>An SSM-aware host that receives an IGMPv1 Query, an IGMPv2 General Query,
   or an IGMPv2 Group Specific Query for a multicast address in the SSM address range
   SHOULD
   <bcp14>SHOULD</bcp14> log an error. It is RECOMMENDED <bcp14>RECOMMENDED</bcp14> that implementions implementations provide a configuration option
   to disable use of the Host Compatibility Mode to allow networks to operate only in SSM mode.
   This configuration option SHOULD <bcp14>SHOULD</bcp14> be disabled by default.</t>
        </section>
        <section title="In numbered="true" toc="default">
          <name>In the Presence of Older Version Group Members"> Members</name>
          <t>An IGMPv3 host may be placed on a network where there are hosts that
   have not yet been upgraded to IGMPv3.  A host MAY <bcp14>MAY</bcp14> allow its IGMPv3
   Membership Record to be suppressed by either a Version 1 an IGMPv1 Membership
   Report,
   Report or a Version 2 an IGMPv2 Membership Report. SSM-aware hosts MUST NOT <bcp14>MUST NOT</bcp14> allow
   its IGMPv3 Membership Record to be suppressed.</t>
        </section>
      </section>
      <section title="Multicast numbered="true" toc="default">
        <name>Multicast Router Behavior"> Behavior</name>
        <section title="In numbered="true" toc="default">
          <name>In the Presence of Older Version Queriers"> Queriers</name>
          <t>IGMPv3 routers may be placed on a network where at least one router
   on the network has not yet been upgraded to IGMPv3.  The following
   requirements apply:
   <list style="symbols">
          </t>
          <ul spacing="normal">
            <li>
              <t>If any older versions of IGMP are present on routers, the querier
     MUST
     <bcp14>MUST</bcp14> use the lowest version of IGMP present on the network.  This
     must be administratively assured; routers that desire to be
     compatible with IGMPv1 and IGMPv2 MUST <bcp14>MUST</bcp14> have a configuration option
     to act in IGMPv1 or IGMPv2 compatibility modes.  When in IGMPv1
     mode, routers MUST <bcp14>MUST</bcp14> send Periodic Queries with a Max Resp Code of 0
     and truncated at the Group Address field (i.e., 8 bytes long), long) and
     MUST
     <bcp14>MUST</bcp14> ignore Leave Group messages.  They SHOULD <bcp14>SHOULD</bcp14> also warn about
     receiving an IGMPv2 or IGMPv3 query, although such warnings MUST <bcp14>MUST</bcp14> be
     rate-limited.  When in IGMPv2 mode, routers MUST <bcp14>MUST</bcp14> send Periodic
     Queries truncated at the Group Address field (i.e., 8 bytes long), long)
     and SHOULD <bcp14>SHOULD</bcp14> also warn about receiving an IGMPv3 query (such warnings
     MUST
     <bcp14>MUST</bcp14> be rate-limited).  They also MUST <bcp14>MUST</bcp14> fill in the Max Resp Response Time in
     the Max Resp Code field, i.e., the exponential algorithm described
	   in <xref target="max_resp_code" /> format="default"/> is not used.</t>
            </li>
            <li>
              <t>If a router is not explicitly configured to use IGMPv1 or IGMPv2
     and hears receives an IGMPv1 Query or IGMPv2 General Query, it SHOULD <bcp14>SHOULD</bcp14> log a
   warning.  These warnings MUST <bcp14>MUST</bcp14> be rate-limited.</t>
            </li>
            <li>
              <t>It is RECOMMENDED <bcp14>RECOMMENDED</bcp14> that implementions implementations provide a configuration option
   to disable use of compatibility mode to allow networks to operate only
   in SSM mode. This configuration option SHOULD <bcp14>SHOULD</bcp14> be disabled by default.</t>
   </list></t>
            </li>
          </ul>
        </section>
        <section title="In numbered="true" toc="default">
          <name>In the Presence of Older Version Group Members"> Members</name>
          <t>IGMPv3 routers may be placed on a network where there are hosts that
   have not yet been upgraded to IGMPv3.  In order to be compatible with
   older version hosts, IGMPv3 routers MUST <bcp14>MUST</bcp14> operate in version 1 v1 and
   version 2
   v2 compatibility modes.  IGMPv3 routers keep a compatibility
   mode per group record. Group Record.  A group's compatibility mode is determined
   from the Group Compatibility Mode variable variable, which can be in one of
   three states:  IGMPv1, IGMPv2 IGMPv2, or IGMPv3.  This variable is kept per
   group record
   Group Record and is dependent on the version of Membership Reports
   heard
   received for that group as well as the Older Version Host Present timer Older-Version-Host-Present Timer
   for the group.</t>
          <t>In order to switch gracefully between versions of IGMP, routers keep
   an IGMPv1 Host Present timer IGMPv1-Host-Present Timer and an IGMPv2 Host Present timer IGMPv2-Host-Present Timer per
   group record.
   Group Record.  The IGMPv1 Host Present timer IGMPv1-Host-Present Timer is set to Older [Older Version
   Host Present Timeout Interval] seconds whenever an IGMPv1 Membership Report is
   received.  The IGMPv2 Host Present timer IGMPv2-Host-Present Timer is set to Older [Older Version Host
   Present Timeout Interval] seconds whenever an IGMPv2 Membership Report is
   received.</t>
          <t>The Group Compatibility Mode of a group record Group Record changes whenever an
   older version report (than the current compatibility mode) is heard received
   or when certain timer conditions occur.  When the IGMPv1 Host Present
   timer IGMPv1-Host-Present
   Timer expires, a router switches to Group Compatibility mode Mode of
   IGMPv2 if it has a running IGMPv2 Host Present timer.  If it does not
   have a running IGMPv2 Host Present timer timer, then it switches to Group
   Compatibility Mode of IGMPv3.  When the IGMPv2 Host Present timer IGMPv2-Host-Present Timer expires
   and the IGMPv1 Host Present timer IGMPv1-Host-Present Timer is not running, a router switches
   to Group Compatibility mode Mode of IGMPv3.  Note that when a group
   switches back to IGMPv3 mode, it takes some time to regain source-
   specific state information.  Source-specific information will be
   learned during the next General Query, but sources that should be
   blocked will not be blocked until [Group Membership Interval] after
   that.</t>
          <t>The Group Compatibility Mode variable is based on whether an older
   version report was heard received in the last Older [Older Version Host Present
   Timeout
   Interval] seconds.  The Group Compatibility Mode is set depending on
	   the following:</t>
   <texttable>
      <ttcol align="center">Group
           <table align="center">
	     <name>Group Compatibility Mode Settings</name>
            <thead>
              <tr>
                <th align="left">Group Compatibility Mode</ttcol>
      <ttcol align="center">Timer State</ttcol>
      <c>IGMPv3 (default)</c><c>IGMPv2 Mode</th>
                <th align="left">Timer State</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td align="left">IGMPv3 (default)</td>
                <td align="left">IGMPv2 Host Present not running and IGMPv1 Host Present not running</c>
      <c>IGMPv2</c><c>IGMPv2 running</td>
              </tr>
              <tr>
                <td align="left">IGMPv2</td>
                <td align="left">IGMPv2 Host Present running and IGMPv1 Host Present not running</c>
      <c>IGMPv1</c><c>IGMPv1 running</td>
              </tr>
              <tr>
                <td align="left">IGMPv1</td>
                <td align="left">IGMPv1 Host Present running</c>
   </texttable> running</td>
              </tr>
            </tbody>
          </table>
          <t>If a router receives a report which that causes its older Host Present
   timers to be updated and correspondingly its compatibility mode, it
   SHOULD
   <bcp14>SHOULD</bcp14> switch compatibility modes immediately.</t>
          <t>When Group Compatibility Mode is IGMPv3, a router acts using the
   IGMPv3 protocol for that group.</t>
          <t>When Group Compatibility Mode is IGMPv2, a router internally
   translates the following IGMPv2 messages for that group to their
	   IGMPv3 equivalents:</t>
   <texttable>
      <ttcol align="center">IGMPv2 Message</ttcol>
      <ttcol align="center">IGMPv3 Equivalent</ttcol>
      <c>Report</c><c>IS_EX(
           <table align="center">
	     <name>IGMPv2 Compatibility Mode Message Translation</name>
            <thead>
              <tr>
                <th align="left">IGMPv2 Message</th>
                <th align="left">IGMPv3 Equivalent</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td align="left">Report</td>
                <td align="left">IS_EX( {} )</c>
      <c>Leave</c><c>TO_IN( )</td>
              </tr>
              <tr>
                <td align="left">Leave</td>
                <td align="left">TO_IN( {} )</c>
   </texttable> )</td>
              </tr>
            </tbody>
          </table>
          <t>IGMPv3 BLOCK messages are ignored, as are source-lists in TO_EX()
   messages (i.e., any TO_EX() message is treated as TO_EX( {} )).</t>
          <t>When Group Compatibility Mode is IGMPv1, a router internally
   translates the following IGMPv1 and IGMPv2 messages for that group to
	   their IGMPv3 equivalents:</t>
   <texttable>
      <ttcol align="center">IGMPv2 Message</ttcol>
      <ttcol align="center">IGMPv3 Equivalent</ttcol>
      <c>v1 Report</c><c>IS_EX(
           <table align="center">
	     <name> IGMPv1 Compatibility Mode Message Translation</name>
            <thead>
              <tr>
                <th align="left">IGMPv2 Message</th>
                <th align="left">IGMPv3 Equivalent</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td align="left">v1 Report</td>
                <td align="left">IS_EX( {} )</c>
      <c>v2 Report</c><c>IS_EX( )</td>
              </tr>
              <tr>
                <td align="left">v2 Report</td>
                <td align="left">IS_EX( {} )</c>
   </texttable> )</td>
              </tr>
            </tbody>
          </table>
          <t>In addition to ignoring IGMPv3 BLOCK messages and source-lists in
   TO_EX() messages as in IGMPv2 Group Compatibility Mode, IGMPv2 Leave
   messages and IGMPv3 TO_IN() messages are also ignored.</t>
        </section>
      </section>
    </section>
    <section title="List anchor="timers" numbered="true" toc="default">
      <name>List of Timers, Counters Counters, and Their Default Values" anchor="timers"> Values</name>

      <t>Most of these timers and counters are configurable.  If non-default settings are
   used, they MUST <bcp14>MUST</bcp14> be consistent among all systems on a single link.
   Note that parentheses are used to group expressions to make the
   algebra clear.</t>
      <section title="Robustness Variable" anchor="robust"> anchor="robust" numbered="true" toc="default">
        <name>Robustness Variable</name>
        <t>The Robustness Variable allows tuning for the expected packet loss on
   a network.  If a network is expected to be lossy, the Robustness
   Variable may be increased.  IGMP is robust to (Robustness Variable -
   1) packet losses.  The Robustness Variable MUST NOT <bcp14>MUST NOT</bcp14> be zero, zero and
   SHOULD NOT
   <bcp14>SHOULD NOT</bcp14> be one.  Default: 2</t> 2.</t>
      </section>
      <section title="Query Interval" anchor="qry_int"> anchor="qry_int" numbered="true" toc="default">
        <name>Query Interval</name>
        <t>The Query Interval is the interval between General Queries sent by
   the Querier.  Default: 125 seconds.</t>
        <t>By varying the [Query Interval], Query Interval, an administrator may tune the number
   of IGMP messages on the network; larger values cause IGMP Queries to
   be sent less often.</t>
      </section>
      <section title="Query numbered="true" toc="default">
        <name>Query Response Interval"> Interval</name>

        <t>The Query Response Interval uses the Max Response Time used to calculate the Max Resp Code that is inserted into the periodic General Queries.  Default: 100 (10 seconds)</t> seconds).</t>
        <t>By varying the [Query Response Interval], an administrator may tune
   the burstiness of IGMP messages on the network; larger values make
   the traffic less bursty, as host responses are spread out over a
   larger interval.  The number of seconds represented by the [Query
   Response Interval] must be less than the [Query Interval].</t>
      </section>
      <section title="Group numbered="true" toc="default">
        <name>Group Membership Interval"> Interval</name>
        <t>The Group Membership Interval is the amount of time that must pass
   before a multicast router decides there are no more members of a
   group or a particular source on a network.</t>
        <t>This value MUST <bcp14>MUST</bcp14> be ((the Robustness Variable) ([Robustness Variable] times (the Query
   Interval)) [Query
   Interval]) plus (2 * Query [Query Response Interval).</t> Interval]).</t>
      </section>
      <section title="Other numbered="true" toc="default">
        <name>Other Querier Present Interval"> Interval</name>
        <t>The Other Querier Present Interval is the length of time that must
   pass before a multicast router decides that there is no longer
   another multicast router which that should be the querier.  This value
   MUST
   <bcp14>MUST</bcp14> be ((the Robustness Variable) ([Robustness Variable] times (the Query Interval)) [Query Interval]) plus
   (one half of one Query
   (0.5 times [Query Response Interval).</t> Interval]).</t>
      </section>
      <section title="Startup numbered="true" toc="default">
        <name>Startup Query Interval"> Interval</name>
        <t>The Startup Query Interval is the interval between General Queries
   sent by a Querier on startup.  Default: 1/4 the Query Interval.</t> times [Query Interval].</t>
      </section>
      <section title="Startup numbered="true" toc="default">
        <name>Startup Query Count"> Count</name>
        <t>The Startup Query Count is the number of Queries sent out on startup,
   separated by the Startup Query Interval.  Default: the Robustness
   Variable.</t> [Robustness
   Variable].</t>
      </section>
      <section title="Last numbered="true" toc="default">
        <name>Last Member Query Interval"> Interval</name>
        <t>The Last Member Query Interval (LMQI) is the Max Response Time used to
   calculate the Max Resp Code that is inserted into Group-Specific Group Specific Queries sent
   in response to Leave Group messages.  It is also the Max Response
   Time used in calculating the Max Resp Code for Group-and-Source- Group-and-Source Specific
	Query messages. Messages.  Default: 10 (1 second)</t> second).</t>

        <t>Note that for values of LMQI greater than 12.8 seconds, a limited set
   of values can be represented, corresponding to sequential values of
   Max Resp Code.  When converting a configured time to a Max Resp Code
   value, it is recommended to use the exact value value, if possible, or the
   next lower value if the requested value is not exactly representable.</t>
        <t>This value may be tuned to modify the "leave latency" leave latency of the network.
   A reduced value results in reduced time to detect the loss of the
   last member of a group or source.</t>
      </section>
      <section title="Last numbered="true" toc="default">
        <name>Last Member Query Count"> Count</name>
        <t>The Last Member Query Count is the number of Group-Specific Group Specific Queries
   sent before the router assumes there are no local members.  The Last
   Member Query Count is also the number of Group-and-Source-Specific Group-and-Source Specific
   Queries sent before the router assumes there are no listeners for a
   particular source.  Default: the Robustness Variable.</t> [Robustness Variable].</t>
      </section>
      <section title="Last numbered="true" toc="default">
        <name>Last Member Query Time"> Time</name>
        <t>The Last Member Query Time is the time value represented by the Last [Last
   Member Query Interval, multiplied by the Last Interval] times [Last Member Query Count. Count].  It
   is not a tunable value, but it may be tuned by changing its components.</t>
      </section>
      <section title="Unsolicited numbered="true" toc="default">
        <name>Unsolicited Report Interval"> Interval</name>
        <t>The Unsolicited Report Interval is the time between repetitions of a
   host's initial report of membership in a group.  Default: 1 second.</t>
      </section>
      <section title="Older numbered="true" toc="default">
        <name>Older Version Querier Present Interval"> Interval</name>
        <t>The Older Version Querier Present Interval is the timeout for transitioning
   a host back to IGMPv3 mode once an older version query is heard. received.
   When an older version query is received, hosts set their Older
   Version Querier Present Older-Version-Querier-Present
   Timer to Older [Older Version Querier Present Interval.</t> Interval].</t>
        <t>It is RECOMMENDED <bcp14>RECOMMENDED</bcp14> to use the default values for calculating the interval value
   as hosts do not know the values configured on the querying routers.
   This value SHOULD <bcp14>SHOULD</bcp14> be [Robustness Variable] times [Query
   Interval] plus (10 times the Max Resp Response Time in the last received query message).</t> Query Message).</t>
      </section>
      <section title="Older numbered="true" toc="default">
        <name>Older Host Present Interval"> Interval</name>
        <t>The Older Host Present Interval is the time-out timeout for transitioning a
   group back to IGMPv3 mode once an older version report is sent for
   that group.  When an older version report is received, routers set
   their Older Host Present Older-Host-Present Timer to Older [Older Host Present Interval.</t> Interval].</t>
        <t>This value MUST <bcp14>MUST</bcp14> be ((the Robustness Variable) ([Robustness Variable] times (the Query
   Interval)) [Query
   Interval]) plus (one Query [Query Response Interval).</t> Interval].</t>
      </section>
      <section title="Configuring Timers"> numbered="true" toc="default">
        <name>Configuring Timers</name>
        <t>This section is meant to provide advice to network administrators on
   how to tune these settings to their network.  Ambitious router
   implementations might tune these settings dynamically based upon
   changing characteristics of the network.</t>
        <section title="Robustness Variable"> numbered="true" toc="default">
          <name>Robustness Variable</name>
          <t>The Robustness Variable tunes IGMP to expected losses on a link.
   IGMPv3 is robust to (Robustness Variable ([Robustness Variable] - 1) packet losses, e.g., if
   the Robustness Variable is set to the default value of 2, IGMPv3 is
   robust to a single packet loss but may operate imperfectly if more
   losses occur.  On lossy subnetworks, the Robustness Variable should
   be increased to allow for the expected level of packet loss. However,
   increasing the Robustness Variable increases the leave latency of the
   subnetwork.  (The leave latency is the time between when the last
   member stops listening to a source or group and when the traffic
   stops flowing.)</t>
        </section>
        <section title="Query Interval"> numbered="true" toc="default">
          <name>Query Interval</name>
          <t>The overall level of periodic IGMP traffic is inversely proportional
   to the Query Interval.  A longer Query Interval results in a lower
   overall level of IGMP traffic.  The Query Interval MUST <bcp14>MUST</bcp14> be equal to
   or longer than the Max Response Time inserted in General Query
   messages.</t>
   Messages.</t>
        </section>
        <section title="Max numbered="true" toc="default">
          <name>Max Response Time"> Time</name>
          <t>The burstiness of IGMP traffic is inversely proportional to the Max
   Response Time.  A longer Max Response Time will spread Report
   messages over a longer interval.  However, a longer Max Response Time
   in Group-Specific Group Specific and Source-and-Group-Specific Source-and-Group Specific Queries extends the
   leave latency.  (The leave latency is the time between when the last
   member stops listening to a source or group and when the traffic
   stops flowing.)  The expected rate of Report messages can be
   calculated by dividing the expected number of Reporters by the Max
   Response Time.  The Max Response Time may be dynamically calculated
   per Query by using the expected number of Reporters for that Query as
	   follows:</t>
   <texttable>
      <ttcol align="center">Query Type</ttcol>
      <ttcol align="center">Expected number
           <table align="center">
	     <name>Expected Number of Reporters</ttcol>
      <c>General Query</c><c>All IGMP Reporters</name>
            <thead>
              <tr>
                <th align="left">Query Type</th>
                <th align="left">Expected Number of Reporters</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td align="left">General Query</td>
                <td align="left">All systems on subnetwork</c>
      <c>Group-Specific Query</c><c>All the subnetwork</td>
              </tr>
              <tr>
                <td align="left">Group Specific Query</td>
                <td align="left">All systems that had expressed interest in the group on the subnetwork</c>
      <c>Source-and-Group-Specific Query</c><c>All subnetwork</td>
              </tr>
              <tr>
                <td align="left">Source-and-Group Specific Query</td>
                <td align="left">All systems on the subnetwork that had expressed interest in
	      the source and group</c>
   </texttable> group</td>
              </tr>
            </tbody>
          </table>
          <t>A router is not required to calculate these populations or tune the
   Max Response Time dynamically; these are simply guidelines.</t>
        </section>
      </section>
    </section>
    <section title="Security Considerations"> numbered="true" toc="default">
      <name>Security Considerations</name>
      <t>IGMP does provide provides any form of confidentiality. This means any device
   on a link can passively receive any IGMP message on the link. Such access
   can lead to privacy concerns around potentially sensitive multicast groups
   or the ability to identify/map the devices on a link.</t>
      <t>We consider the ramifications of a forged message of each type, type and
   describe the usage of an IPsec AH Authentication Header (AH) to authenticate messages if desired.</t>
      <section title="Query Message"> numbered="true" toc="default">
        <name>Query Message</name>
        <t>A forged Query message Message from a machine with a lower IP address than
   the current Querier will cause Querier duties to be assigned to the
   forger.  If the forger then sends no more Query messages, Messages, other
   routers' Other Querier Present timer Other-Querier-Present Timer will time out and one will
   resume the role of Querier.  During this time, if the forger ignores
   Leave Messages, messages, traffic might flow to groups with no members for up
   to [Group Membership Interval].</t>
        <t>A DoS Denial-of-Service (DoS) attack on a host could be staged through forged Group-and-
   Source-Specific
   Source Specific Queries.  The attacker can find out about membership
   of a specific host with a general query. General Query.  After that that, it could send a
   large number of Group-and-Source-Specific queries, Group-and-Source Specific Queries, each with a large
   source list
   source-list and the Maximum Response Time set to a large value.  The
   host will have to store and maintain the sources specified in all of
   those queries Queries for as long as it takes to send the delayed response.
   This would consume both memory and CPU cycles in order to augment the
   recorded sources with the source lists source-lists included in the successive
   queries.</t>
   Queries.</t>
        <t>To protect against such a DoS attack, a host stack implementation
   could restrict the number of Group-and-Source-Specific Group-and-Source Specific Queries per
   group membership within this interval, interval and/or record only a limited
   number of sources.</t>
        <t>Forged Query messages Messages from the local network can be easily traced.
   There are three measures necessary to defend against externally
   forged Queries:
   <list style="bullets">
        </t>
        <ul spacing="normal">
          <li>
            <t>Routers SHOULD NOT <bcp14>SHOULD NOT</bcp14> forward Queries.  This is easier for a router to
     accomplish if the Query carries the Router-Alert Router Alert option.</t>
          </li>
          <li>
            <t>Hosts SHOULD <bcp14>SHOULD</bcp14> ignore v2 or v3 Queries without the Router-Alert Router Alert
     option.</t>
          </li>
          <li>
            <t>Hosts SHOULD <bcp14>SHOULD</bcp14> ignore v1, v2 v2, or v3 General Queries sent to a
     multicast address other than 224.0.0.1, the all-systems address.</t>
   </list></t>
          </li>
        </ul>
      </section>
      <section title="Current-State numbered="true" toc="default">
        <name>Current-State Report messages"> Messages</name>
        <t>A forged Report message may cause multicast routers to think there
   are members of a group on a network when there are not.  Forged
   Report messages from the local network are meaningless, since as joining
   a group on a host is generally an unprivileged operation, so a local
   user may trivially gain the same result without forging any messages.
   Forged Report messages from external sources are more troublesome;
   there are two defenses against externally forged Reports:
   <list style="bullets">
        </t>
        <ol spacing="normal">
          <li>
            <t>Ignore the Report if you cannot identify the source address of the
     packet as belonging to a network assigned to the interface on which
     the packet was received.  This solution means that Reports sent by
     mobile hosts without addresses on the local network will be
     ignored.  Report messages with a source address of 0.0.0.0 SHOULD <bcp14>SHOULD</bcp14>
     be accepted on any interface.</t>
          </li>
          <li>
            <t>Ignore Report messages without Router Alert options <xref target="RFC2113" />, format="default"/> and
     require that routers to not forward Report messages.  (The requirement
     is not a requirement of generalized filtering in the forwarding
     path, since as the packets already have Router Alert options in them.)
     This solution breaks backwards compatibility with implementations
     of IGMPv1 or earlier versions of IGMPv2 which that did not require a
   Router Alert.</t>
   </list></t>
          </li>
        </ol>
        <t>A forged Version 1 v1 Report Message message may put a router into "version 1 "v1
   members present" state for a particular group, meaning that the
   router will ignore Leave messages.  This can cause traffic to flow to
   groups with no members for up to [Group Membership Interval].  This
   can be solved by providing routers with a configuration switch to
   ignore Version 1 v1 messages completely.  This breaks automatic
   compatibility with Version 1 v1 hosts, so it should only be used in
   situations where "fast leave" is critical.</t>
        <t>A forged Version 2 v2 Report Message message may put a router into "version 2 "v2
   members present" state for a particular group, meaning that the
   router will ignore IGMPv3 source-specific state messages.  This can
   cause traffic to flow from unwanted sources for up to [Group
   Membership Interval].  This can be solved by providing routers with a
   configuration switch to ignore Version 2 v2 messages completely.  This
   breaks automatic compatibility with Version 2 v2 hosts, so it should only
   be used in situations where source include and exclude is critical.</t>
      </section>
      <section title="State-Change numbered="true" toc="default">
        <name>State-Change Report Messages"> Messages</name>
        <t>A forged State-Change Report message will cause the Querier to send
   out Group-Specific Group Specific or Source-and-Group-Specific Source-and-Group Specific Queries for the group
   in question.  This causes extra processing on each router and on each
   member of the group, but can not it cannot cause loss of desired traffic.
   There are two defenses against externally forged State-Change Report
   messages:
   <list style="bullets">
        </t>
        <ol spacing="normal">
          <li>
            <t>Ignore the State-Change Report message if you cannot identify the
     source address of the packet as belonging to a subnet assigned to
     the interface on which the packet was received.  This solution
     means that State-Change Report messages sent by mobile hosts
     without addresses on the local subnet will be ignored.  State-
     Change Report messages with a source address of 0.0.0.0 SHOULD <bcp14>SHOULD</bcp14> be
	   accepted on any interface.</t>
          </li>
          <li>
            <t>Ignore State-Change Report messages without Router Alert options
   <xref target="RFC2113" />, format="default"/> and require that routers to not forward State-Change
     Report messages.  (The requirement is not a requirement of
     generalized filtering in the forwarding path, since as the packets
     already have Router Alert options in them.)</t>
   </list></t>
          </li>
        </ol>
      </section>
      <section title="IPsec Usage"> numbered="true" toc="default">
        <name>IPsec Usage</name>
        <t>In addition to these measures, IPsec in Authentication Header AH mode
   <xref target="RFC4302" /> format="default"/> may be used to protect against remote attacks by ensuring that IGMPv3 messages came from a system on the LAN (or, more specifically,
   from a system with the proper key).  When using IPsec, the messages sent
   to 224.0.0.1 and 224.0.0.22 should be authenticated using AH.  When
   keying, there are two possibilities:
   <list style="numbers">
        </t>
        <ol spacing="normal" type="1"><li>
            <t>Use a symmetric signature algorithm with a single key for the LAN
      (or a key for each group).  This allows validation that a packet
      was sent by a system with the key.  This has the limitation that
      any system with the key can forge a message; it is not possible to
      authenticate the individual sender precisely.  It also requires
      disabling IPSec's IPsec's Replay Protection.</t>
          </li>
          <li>
            <t>When appropriate key management standards have been developed, use
      an asymmetric signature algorithm.  All systems need to know the
      public key of all routers, and all routers need to know the public
      key of all systems.  This requires a large amount of key
      management but has the advantage that senders can be authenticated
      individually so so, e.g., a host cannot forge a message that only
      routers should be allowed to send.</t>
   </list></t>
          </li>
        </ol>
        <t>This solution only directly applies to Query and Leave messages in
   IGMPv1 and IGMPv2, since IGMPv2 as Reports are sent to the group being reported reported,
   and it is not feasible to agree on a key for host-to-router
   communication for arbitrary multicast groups.</t>
      </section>
    </section>
    <section title="IANA Considerations"> numbered="true" toc="default">
      <name>IANA Considerations</name>
      <t>All IGMP types described in this document are managed via <xref target="I-D.ietf-pim-3228bis"/>.</t>
   <t>References to RFC 3376 that currently exist in IANA registries are to be updated to target="BCP57" format="default"/>.</t>
      <t>IANA has replaced each reference
   this document. This includes to <xref target="RFC3376"/> with a reference to this document in both the IGMP "IGMP Type Numbers registry Numbers" and the informational
	   reference in the IPFIX "IPFIX Information Elements registry.</t> Elements" registries.
      </t>
    </section>

   <section title="Contributors">
   <t>Brad Cain, Steve Deering, Isidor Kouvelas, Bill Fenner, and Ajit Thyagarajan
   are the authors of RFC 3376, which forms the bulk of the content contained herein.</t>

   <t>Anuj Budhiraja, Toerless Eckert, Olufemi Komolafe and Tim Winters have contributed
   valuable content to this version of the specification.</t>
   </section>

   <section title="Acknowledgments">
   <t>We would like to thank Ran Atkinson, Luis Costa, Toerless Eckert,
   Dino Farinacci, Serge Fdida, Wilbert de Graaf, Sumit Gupta, Mark
   Handley, Bob Quinn, Michael Speer, Dave Thaler and Rolland Vida

  </middle>
  <back>
    <references>
      <name>References</name>
      <references>
        <name>Normative References</name>
        <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.1112.xml"/>
        <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.2113.xml"/>
        <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.2119.xml"/>
        <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.2236.xml"/>
        <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.4302.xml"/>
        <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.4607.xml"/>
        <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.4604.xml"/>
        <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8174.xml"/>

<referencegroup anchor="BCP57" target="https://www.rfc-editor.org/info/bcp57">
  	<reference anchor="RFC9778" target="https://www.rfc-editor.org/info/rfc9778">
	  <front>
	    <title>IANA Considerations for
   comments and suggestions on Internet Group Management Protocols</title>
	    <author initials="B." surname="Haberman" fullname="Brian Haberman" role="editor">
	      <organization>Johns Hopkins University Applied Physics Lab</organization>
	    </author>
	    <date month="March" year="2025"/>
	  </front>
	  <seriesInfo name="BCP" value="57"/>
	  <seriesInfo name="RFC" value="9778"/>
	  <seriesInfo name="DOI" value="10.17487/RFC9778"/>
	</reference>
</referencegroup>

<!-- [I-D.ietf-pim-3228bis] companion document RFC 3376.</t>

   <t>Stig Venaas, Hitoshi Asaeda, and Mike McBride have provided valuable feedback on this
   version of the specification and we thank them 9778

	<reference anchor="RFC9778" target="https://www.rfc-editor.org/info/rfc9778">
	  <front>
	    <title>IANA Considerations for their input.</t>
   </section>
 </middle>

 <back>
   <references title="Normative References">
      <?rfc include="reference.RFC.1112" ?>
      <?rfc include="reference.RFC.2113" ?>
      <?rfc include="reference.RFC.2119" ?>
      <?rfc include="reference.RFC.2236" ?>
      <?rfc include="reference.RFC.4302" ?>
      <?rfc include="reference.RFC.4607" ?>
      <?rfc include="reference.RFC.4604" ?>
      <?rfc include="reference.RFC.8174" ?>
      <?rfc include="reference.I-D.ietf-pim-3228bis" ?> Internet Group Management Protocols</title>
	    <author initials="B." surname="Haberman" fullname="Brian Haberman" role="editor">
	      <organization>Johns Hopkins University Applied Physics Lab</organization>
	    </author>
	    <date month="March" year="2025"/>
	  </front>
	  <seriesInfo name="BCP" value="57"/>
	  <seriesInfo name="RFC" value="9778"/>
	  <seriesInfo name="DOI" value="10.17487/RFC9778"/>
	</reference>
-->
      </references>
      <references>
        <name>Informative References</name>
        <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.1071.xml"/>
        <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.3376.xml"/>
        <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.3569.xml"/>
        <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.3678.xml"/>
      </references>

   <references title="Informative References">
      <?rfc include="reference.RFC.1071" ?>
      <?rfc include="reference.RFC.3376" ?>
      <?rfc include="reference.RFC.3569" ?>
      <?rfc include="reference.RFC.3678" ?>
    </references>
    <section anchor="rationale" title="Design Rationale"> numbered="true" toc="default">
      <name>Design Rationale</name>
      <section anchor="state-change" title="The numbered="true" toc="default">
        <name>The Need for State-Change Messages"> Messages</name>
        <t>IGMPv3 specifies two types of Membership Reports: Current-State and
   State Change.
   State-Change.  This section describes the rationale for the need for needing both these types of Reports.</t>
        <t>Routers need to distinguish Membership Reports that were sent in
   response to Queries from those that were sent as a result of a change
   in interface state.  Membership reports that are sent in response to
   Membership Queries are used mainly to refresh the existing state at
   the router; they typically do not cause transitions in state at the
   router.  Membership Reports that are sent in response to changes in
   interface state require the router to take some action in response to
	   the received report (see <xref target="rcv_rpts" />).</t> format="default"/>).</t>
        <t>The inability to distinguish between the two types of reports would
   force a router to treat all Membership Reports as potential changes
   in state state, and it could result in increased processing at the router as
   well as an increase in IGMP traffic on the network.</t>
      </section>
      <section anchor="suppression" title="Host Suppression"> numbered="true" toc="default">
        <name>Host Suppression</name>
        <t>In IGMPv1 and IGMPv2, a host would cancel sending a pending
   membership reports
   Membership Reports if a similar report was observed from another
   member on the network.  In IGMPv3, this suppression of host
   membership reports
   Membership Reports has been removed.  The following points explain
   the reasons behind this decision.

   <list style="numbers">

        </t>
        <ol spacing="normal" type="1"><li>
            <t>Routers may want to track per-host membership status on an
      interface.  This allows routers to implement fast leaves (e.g.,
      for layered multicast congestion control schemes) as well as track
	   membership status for possible accounting purposes.</t>
          </li>
          <li>
            <t>Membership Report suppression does not work well on bridged LANs.
      Many bridges and Layer2/Layer3 Layer 2 / Layer 3 switches that implement IGMP
      snooping do not forward IGMP messages across LAN segments in order
      to prevent membership report Membership Report suppression.  Removing membership
      report Membership
      Report suppression eases the job of these IGMP snooping devices.</t>
          </li>
          <li>
            <t>By eliminating membership report Membership Report suppression, hosts have fewer
      messages to process; this leads to a simpler state machine
	   implementation.</t>
          </li>
          <li>
            <t>In IGMPv3, a single membership report Membership Report now bundles multiple
      multicast group records Group Records to decrease the number of packets sent.
      In comparison, the previous versions of IGMP required that each
	   multicast group be reported in a separate message.</t>
   </list></t>
          </li>
        </ol>
      </section>
      <section anchor="switch-modes" title="Switching numbered="true" toc="default">
        <name>Switching Router Filter Modes from EXCLUDE to INCLUDE"> INCLUDE</name>
        <t>If there exist hosts exist in both EXCLUDE and INCLUDE modes for a single
   multicast group in a network, the router must be in EXCLUDE mode as
   well (see <xref target="sec-rfm" />). format="default"/>).  In EXCLUDE mode, a router forwards traffic
   from all sources unless that source exists in the exclusion source
   list. source-list.
   If all hosts in EXCLUDE mode cease to exist, it would be
   desirable for the router to switch back to INCLUDE mode seamlessly
	   without interrupting the flow of traffic to existing receivers.</t>
        <t>One of the ways to accomplish this is for routers to keep track of
   all sources desired by hosts that are in INCLUDE mode even though the
   router itself is in EXCLUDE mode.  If the group timer Group Timer now expires in
   EXCLUDE mode, it implies that there are no hosts in EXCLUDE mode on
   the network (otherwise (otherwise, a membership report Membership Report from that host would have
   refreshed the group timer). Group Timer).  The router can then switch to INCLUDE
   mode seamlessly with the list of sources currently being forwarded in
	   its source list.</t> source-list.</t>
      </section>
    </section>
    <section anchor="summary" title="Summary numbered="true" toc="default">
      <name>Summary of Changes from IGMPv2"> IGMPv2</name>
      <t>While the main additional feature of IGMPv3 is the addition of source
   filtering, the following is a summary of other changes from RFC 2236.

   <list style="symbols"> <xref target="RFC2236"/>.

      </t>
      <ul spacing="normal">
        <li>
          <t>State is maintained as Group + List-of-Sources, not simply Group as
   in IGMPv2.</t>
        </li>
        <li>
          <t>Interoperability with IGMPv1 and IGMPv2 systems is defined as
	   operations on the IGMPv3 state.</t>
        </li>
        <li>
          <t>The IP Service Interface service interface has changed changed, to allow specification of
	   source-lists.</t>
        </li>
        <li>
          <t>The Querier includes its Robustness Variable and Query Interval in
     Query packets to allow synchronization of these variables on non-
	   Queriers.</t>
        </li>
        <li>
          <t>The Max Response Time in Query messages Messages has an exponential range,
     changing the maximum from 25.5 seconds to about 53 minutes, for use
	   on links with a huge numbers number of systems.</t>
        </li>
        <li>
          <t>Hosts retransmit state-change messages for increased robustness.</t>
        </li>
        <li>
          <t>Additional data sections are defined defined, to allow later extensions.</t>
        </li>
        <li>
          <t>Report packets are sent to 224.0.0.22, to assist layer-2 Layer 2 switches
	   in snooping.</t>
        </li>
        <li>
          <t>Report packets can contain multiple group records, Group Records, to allow
	   reporting of full current state using fewer packets.</t>
        </li>
        <li>
          <t>Hosts no longer perform suppression, to simplify implementations
	   and permit explicit membership tracking.</t>

   <t>New Suppress Router-Side Processing (S)
        </li>
        <li>
          <t>A new S flag in Query messages Messages
	   fixes robustness issues issues, which were also present in IGMPv2.</t>
   </list></t>
        </li>
      </ul>
    </section>
    <section anchor="errata-details" title="Summary numbered="true" toc="default">
      <name>Summary of Changes from RFC 3376"> 3376</name>
      <t>The following is a list of changes made since RFC 3376.
   <list style="symbols"> <xref target="RFC3376"/> was published.
      </t>
      <ul spacing="normal">
        <li>
          <t>Modified the definition of Older Version Querier Present
		   Interval to address Erratum 4375.</t>
        </li>
        <li>
          <t>Modified the metadata to fix the Obsoletes vs vs. Updates relationship with RFC 2236 <xref target="RFC2236"/> per Erratum 1501.</t>
        </li>
        <li>
          <t>Updated the introductory text to describe the Updates relationship with RFC 2236 <xref target="RFC2236"/> per Erratum 7339.</t>
        </li>
        <li>
          <t>Updated the definition of Group Membership Interval definition to address Erratum 6725.</t>
        </li>
        <li>
          <t>Updated the text for relating to the Router Filter-Mode Filter Mode to address Erratum 5562.</t>
        </li>
        <li>
          <t>Clarified the use of General Queries in the Querier election process.</t>
   </list></t>
        </li>
      </ul>
    </section>

    <section numbered="false" toc="default">
      <name>Acknowledgments</name>
      <t>We would like to thank <contact fullname="Ran Atkinson"/>, <contact
      fullname="Luis Costa"/>, <contact fullname="Toerless Eckert"/>, <contact
      fullname="Dino Farinacci"/>, <contact fullname="Serge Fdida"/>, <contact
      fullname="Wilbert de Graaf"/>, <contact fullname="Sumit Gupta"/>,
      <contact fullname="Mark Handley"/>, <contact fullname="Bob Quinn"/>,
      <contact fullname="Michael Speer"/>, <contact fullname="Dave Thaler"/>,
      and <contact fullname="Rolland Vida"/> for comments and suggestions on
      <xref target="RFC3376"/>.</t>

      <t><contact fullname="Stig Venaas"/>, <contact fullname="Hitoshi
      Asaeda"/>, and <contact fullname="Mike McBride"/> have provided valuable
      feedback on this specification, and we thank them for their input.</t>
    </section>
     <section numbered="false" toc="default">
      <name>Contributors</name>
      <t><contact fullname="Brad Cain"/>, <contact fullname="Steve Deering"/>,
      <contact fullname="Isidor Kouvelas"/>, <contact fullname="Bill
      Fenner"/>, and <contact fullname="Ajit Thyagarajan"/> are the authors of
      <xref target="RFC3376"/>, which forms the bulk of the content contained herein.</t>

      <t><contact fullname="Anuj Budhiraja"/>, <contact fullname="Toerless
      Eckert"/>, <contact fullname="Olufemi Komolafe"/>, and <contact
      fullname="Tim Winters"/> have contributed valuable content to this
      specification.</t>
    </section>
  </back>
</rfc>