<?xml version="1.0" encoding="US-ASCII"?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
<!ENTITY RFC2119 SYSTEM
  "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml">
<!ENTITY RFC2629 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2629.xml">
<!ENTITY RFC5378 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.5378.xml">
]>
<?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>
<?rfc strict="yes" ?>
<?rfc toc="yes"?>
<?rfc symrefs="yes"?>
<?rfc sortrefs="no" ?>
<?rfc compact="yes" ?>
<?rfc subcompact="no" ?>
<rfc category="info" docName="draft-volunteers-pim-igmp-mld-bis-00" ipr="trust200902">

  <!-- ***** FRONT MATTER ***** -->

  <front>
    <!-- The abbreviated title is used in the page header - it is only
         necessary if the full title is longer than 39 characters -->

    <title>
      IGMPv3 and MLDv2 Survey
    </title>

    <!-- add 'role="editor"' below for the editors if appropriate -->

    <!-- Another author who claims to be an editor -->

    <author initials="M" surname="Mishra" fullname="Mankamana Mishra">
      <organization abbrev="Cisco">Cisco Systems</organization>
      <address>
	<postal>
	  <street>821 Alder Drive</street>
	  <city>Milpitas</city> <region>CA</region>
	  <code>95035</code>
	  <country>USA</country>
	</postal>
	<email>mankamis@cisco.com</email>
      </address>
    </author>
    
    <author initials="T" surname="Eckert" fullname="Toerless Eckert">
      <organization abbrev="Huawei">Huawei Technologies</organization>
      <address>
	<postal>
	  <street></street>
	  <city></city> <region></region>
	  <code></code>
	  <country></country>
	</postal>
	<email>tte@cs.fau.de</email>
      </address>
    </author>
    
    <author initials="H" surname="Asaeda" fullname="Hitoshi Asaeda">
      <organization abbrev="NICT">National Institute of Information and Communications Technology</organization>
      <address>
	<postal>
	  <street></street>
	  <city></city> <region></region>
	  <code></code>
	  <country></country>
	</postal>
	<email>asaeda@nict.go.jp</email>
      </address>
    </author>
    
    <author initials="A" surname="Peter" fullname="Anish Peter">
      <organization></organization>
      <address>
	<postal>
	  <street></street>
	  <city></city> <region></region>
	  <code></code>
	  <country></country>
	</postal>
	<email>anish.ietf@gmail.com</email>
      </address>
    </author>
    <author initials="O" surname="Komolafe" fullname="Olufemi Komolafe">
      <organization>Arista Networks</organization>
      <address>
	<postal>
	  <street></street>
	  <city></city> <region></region>
	  <code></code>
	  <country></country>
	</postal>
	<email>femi@arista.com</email>
      </address>
    </author>

    <author initials="S" surname="Babu" fullname="Suneesh Babu">
      <organization>Juniper</organization>
      <address>
	<postal>
	  <street></street>
	  <city></city> <region></region>
	  <code></code>
	  <country></country>
	</postal>
	<email>suneesh@juniper.net</email>
      </address>
    </author>

    <author initials="N" surname="Leymann" fullname="Nicolai Leymann">
      <organization>DT</organization>
      <address>
	<postal>
	  <street></street>
	  <city></city> <region></region>
	  <code></code>
	  <country></country>
	</postal>
	<email>N.Leymann@telekom.de</email>
      </address>
    </author>
    
    <author initials="R" surname="Josyula" fullname="Ramakanth Josyula">
      <organization>Arris</organization>
      <address>
	<postal>
	  <street></street>
	  <city></city> <region></region>
	  <code></code>
	  <country></country>
	</postal>
	<email>ramakanthjosyula@gmail.com</email>
      </address>
    </author>

    <author initials="T" surname="Winters" fullname="Timothy Winters">
      <organization>UNH</organization>
      <address>
	<postal>
	  <street></street>
	  <city></city> <region></region>
	  <code></code>
	  <country></country>
	</postal>
	<email>twinters@iol.unh.edu</email>
      </address>
    </author>

    <date year="2019"/>

    <!-- If the month and year are both specified and are the current
         ones, xml2rfc will fill in the current day for you. If only
         the current year is specified, xml2rfc will fill in the
         current day and month for you. If the year is not the current
         one, it is necessary to specify at least a month (xml2rfc
         assumes day="1" if not specified for the purpose of
         calculating the expiry date).  With drafts it is normally
         sufficient to specify just the year. -->

    <!-- Meta-data Declarations -->

    <area>Routing</area>
    <workgroup>PIM Working Group</workgroup>

    <keyword>multicast</keyword>
    <keyword>IGMP</keyword>
    <keyword>MLD</keyword>

    <abstract>
      <t> The PIM WG intends to progress IGMPv3 and MLDv2 from Proposed Standards to Internet Standards.  This document describes the motivation, procedures and questions proposed for a survey of operators, vendors and implementors of IGMPv3 and MLDv2.  The objective of the survey is to collate information to help the PIM WG progress these protocols to Internet Standards.
      </t>
    </abstract>
  </front>

  <middle>

  <!-- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% -->

  <section anchor="sec.intro" title="Introduction">

    <t>Internet Group Management Protocol Version 3 (IGMPv3) <xref target="RFC3376" /> and Multicast Listener Discovery Version 2 (MLDv2) for IPv6 <xref target="RFC3810" /> are currently Proposed Standards. Given the fact that multiple independent implementations of these protocols exist and they have been successfully and widely used operationally, the PIM WG is keen to progress these protocols to Internet Standards. In order to facilitate this effort, it is critical to establish if there are features specified in <xref target="RFC3376" /> and <xref target="RFC3810" /> that have not been widely used and also to determine any interoperability issues that have arisen from using the protocols.</t>

    <t>Following approach taken for PIM-SM, documented in <xref target="RFC7063" />, the PIM WG has decided that conducting a comprehensive survey on implementations and deployment of IGMPv3 and MLDv2 will provide valuable information to facilitate their progression to Internet Standard.</t>

    <t>This document describes the procedures proposed for conducting the survey and introduces the proposed questions.</t>

  </section>

  <!-- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% -->

  <section anchor="sec.proc" title="Procedures Followed">

    <section title="Methodology">
      <t>The PIM WG Chairs will officially kick off the survey and distribute the questionnaire and pertinent information through appropriate forums, aiming to ensure the survey reaches as wide an audience as possible.</t>
    </section>

    <section title="Intended Recipients of Questionnaire">

      <t><list style='numbers'>
	<t>Network operators</t>
	<t>Router vendors</t>
	<t>Switch vendors</t>
	<t>Host implementors</t>
      </list></t>

    </section>

    <section title="Processing of Responses">
      <t>Responses received will remain confidential. Only the aggregated results will be published and so it will be impossible to identify the contributions by individual operators, vendors or implementors. Furthermore, an option to submit the completed questionnaire anonymously will be available.</t>
    </section>

  </section>

  <!-- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% -->

  <section anchor="sec.question" title="Questionnaire">

    <!-- ========================================================== -->
    
    <section title="Questionnaire for Vendors or Host Implementors">

      <t>Name:</t>
      <t>Affiliation/Organization:</t>
      <t>Contact Email:</t>
      <t>Do you wish to keep your name and affiliation confidential?: Y/N</t>

      <section title="Implementation Status">

	<t>Which of the following have you implemented? And for how long has it been implemented?</t>
	<t><list style='numbers'>
<!--	  <t>Have you deployed IGMPv3 in your network?</t>
	  <t>How long have you had IGMPv3 deployed in your network ?</t>
	  <t>Is your implementation based on <xref target="RFC3376" />?</t>
	  <t>Is lightweight IGMPv3 <xref target="RFC5790" /> is deployed in your network?</t>
	  <t>Have you deployed MLDv2 in your network?</t>
	  <t>Have you deployed IGMP membership Exclude mode with source list defined in <xref target="RFC3376" />?</t>
	  <t>Does any application use Exclude mode with source list for MLDv2?</t>
	  <t>Do you have any other comments / concerns on IGMPv3 / MLDv2? </t>
	  <t>Does your network still have IGMPv1 <xref target="RFC1112" /> deployed?</t>-->
	  <t>IGMPv1 <xref target="RFC1112" /> implemented?: Y/N, since:</t>
	  <t>IGMPv2 <xref target="RFC2236" /> implemented?: Y/N, since:</t>
	  <t>IGMPv3 <xref target="RFC3376" /> implemented?: Y/N, since:</t>
	  <t>Lightweight IGMPv3 <xref target="RFC5790" /> Implemented: Y/N, since:</t>
	  <t>MLDv1 <xref target="RFC2710" /> implemented?: Y/N, since:</t>
	  <t>MLDv2 <xref target="RFC3810" /> implemented?: Y/N, since:</t>
	  <t>Lightweight MLDv2 <xref target="RFC5790" /> implemented?: Y/N, since:</t>
	</list></t>
      </section>

      <section title="Implementation Specifics">
	<t><list style='numbers'>
	  <t>Which IGMPv3 features have you implemented?</t>
	  <t>Which MLDv2 features have you implemented?</t>
	  <t>Have you carried out IGMPv3 or MLDv2 interoperability tests with other implementations? (What issues arose during these tests?) (How could the standards have help minimize these issues?)</t>
	</list></t>
      </section>

      <section title="Implementation Perspectives">
	<t><list style='numbers'>
	  <t>What feature(s) has been deliberately omitted from IGMPv3 or MLDv2 implementations? (Because you think it is sub-optimal or potentially has significant disadvantages/issues?) (Because of insufficient demand/use cases?)</t>
	  <t>Which ambiguities or inconsistencies in RFC 3376 or RFC 3810 made the implementation challenging?</t>
	  <t>What suggestions would you make to the PIM WG as it seeks to progress IGMPv3 and MLDv2 to Internet Standard?</t>
	</list></t>
      </section>

    </section>

    <!-- ========================================================== -->

    <section title="Questionnaire for Network Operators">

      <t>Name:</t>
      <t>Affiliation/Organization:</t>
      <t>Contact Email:</t>
      <t>Do you wish to keep your name and affiliation confidential?:</t>

      <section title="Deployment Status">

	<t>Which of the following are currently deployed in your network? And for how long has it been deployed?</t>
	<t><list style='numbers'>
	  <t>IGMPv1 <xref target="RFC1112" /> deployed?: Y/N, since:</t>
	  <t>IGMPv2 <xref target="RFC2236" /> deployed?: Y/N, since:</t>
	  <t>IGMPv3 <xref target="RFC3376" /> deployed?: Y/N, since:</t>
	  <t>Lightweight IGMPv3 <xref target="RFC5790" /> Implemented: Y/N, since:</t>
	  <t>MLDv1 <xref target="RFC2710" /> deployed?: Y/N, since:</t>
	  <t>MLDv2 <xref target="RFC3810" /> deployed?: Y/N, since:</t>
	  <t>Lightweight MLDv2 <xref target="RFC5790" /> deployed?: Y/N, since:</t>
	</list></t>
      </section>

      <section title="Deployment Specifics">
	<t><list style='numbers'>
	  <t>Which IGMPv3 features are in use? (Is Exclude mode with source list in use?)</t>
	  <t>Which MLDv2 features are in use? (Is Exclude mode with source list in use?)</t>
	  <t>Does your network rely on the fallback mechanism between different IGMP versions? (Between which IGMP versions?) (What is your experience with this fallback mechanism?)</t>
	  <t>Are you using equipment with different (multi-vendor) implementations for your deployment? (Have you encountered any inter-operability or backward-compatibility issues amongst differing implementations?) (What are your concerns about these issues?)</t>
	</list></t>
      </section>

      <section title="Deployment Perspectives">
	<t><list style='numbers'>
	  <t>What have you found to be the strengths of IGMPv3 or MLDv2?</t>
	  <t>What have you found to be the weaknesses of IGMPv3 or MLDv2?</t>
	  <t>What suggestions would you make to the PIM WG as it seeks to progress IGMPv3 and MLDv2 to Internet Standard?</t>
	</list></t>
      </section>
      
    </section>

  </section>

  <section title="Acknowledgments">
      <t> The authors would like to thank Stig and Mike for valuable review and feedback.
  </t>
      </section>


  <!-- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% -->

</middle>

<back>
  <references title="Normative References">

    <reference anchor="RFC1112">
      <front>
	<title>Host Extensions for IP Multicasting</title>
	<author initials="S" surname="Deering" />
	<date month="August" year="1989" />
      </front>
      <seriesInfo name="RFC" value="1112" />
    </reference>

    <reference anchor="RFC2236">
      <front>
	<title>Internet Group Management Protocol, Version 2</title>
	<author initials="W" surname="Fenner" />
	<date month="November" year="1997" />
      </front>
      <seriesInfo name="RFC" value="2236" />
    </reference>

    <reference anchor="RFC3376">
      <front>
	<title>Internet Group Management Protocol, Version 3</title>
	<author initials="B" surname="Cain" />
	<author initials="S" surname="Deering" />
	<author initials="I" surname="Kouvelas" />
	<author initials="B" surname="Fenner" />
	<author initials="A" surname="Thyagarajan" />
	<date month="October" year="2002" />
      </front>
      <seriesInfo name="RFC" value="3376" />
    </reference>

    <reference anchor="RFC2710">
      <front>
	<title>Multicast Listener Discovery (MLD) for IPv6</title>
	<author initials="S" surname="Deering" />
	<author initials="W" surname="Fenner" />
	<author initials="B" surname="Haberman" />
	<date month="October" year="1999" />
      </front>
      <seriesInfo name="RFC" value="2710" />
    </reference>

    <reference anchor="RFC3810">
      <front>
	<title>Multicast Listener Discovery Version 2 (MLDv2) for IPv6</title>
	<author initials="R" surname="Vida" />
	<author initials="L" surname="Costa" />
	<date month="June" year="2004" />
      </front>
      <seriesInfo name="RFC" value="3810" />
    </reference>

    <reference anchor="RFC5790">
      <front>
	<title>Lightweight Internet Group Management Protocol Version 3 (IGMPv3) and Multicast Listener Discovery Version 2 (MLDv2) Protocols</title>
	<author initials="H" surname="Liu" />
	<author initials="W" surname="Cao" />
	<author initials="H" surname="Asaeda" />
	<date month="February" year="2010" />
      </front>
      <seriesInfo name="RFC" value="5790" />
    </reference>

  </references>

  <references title="Informative References">

    <reference anchor="RFC7063">
      <front>
	<title>Survey Report on Protocol Independent Multicast - Sparse Mode (PIM-SM) Implementations and Deployments</title>
	<author initials="L" surname="Zheng" />
	<author initials="Z" surname="Zhang" />
	<author initials="R" surname="Parekh" />
	<date month="December" year="2013" />
      </front>
      <seriesInfo name="RFC" value="7063" />
    </reference>

<!--    <reference anchor="refs.SSM">
      <front>
	<title>Source-Specific Multicast for IP</title>
	<author initials="H" surname="Holbrook" />
	<author initials="B" surname="Cain" />
	<date month="August" year="2006" />
      </front>
      <seriesInfo name="RFC" value="4607" />
    </reference>

    <reference anchor="refs.Proxy">
      <front>
	<title>Internet Group Management Protocol (IGMP) / Multicast Listener Discovery (MLD)-Based Multicast Forwarding ("IGMP/MLD Proxying")</title>
	<author initials="B" surname="Fenner" />
	<author initials="H" surname="He" />
	<author initials="B" surname="Haberman" />
	<author initials="H" surname="Sandick" />
	<date month="August" year="2006" />
      </front>
      <seriesInfo name="RFC" value="4605" />
    </reference>-->

  </references>
</back>

</rfc>
