Re: [Igmp-mld-bis] Initial version of Questionnaire

Olufemi Komolafe <femi@arista.com> Fri, 08 March 2019 01:49 UTC

Return-Path: <femi@arista.com>
X-Original-To: igmp-mld-bis@ietfa.amsl.com
Delivered-To: igmp-mld-bis@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 85FB71311CE for <igmp-mld-bis@ietfa.amsl.com>; Thu, 7 Mar 2019 17:49:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.99
X-Spam-Level:
X-Spam-Status: No, score=-1.99 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_FILL_THIS_FORM_SHORT=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=arista.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id niGU_rwILaQr for <igmp-mld-bis@ietfa.amsl.com>; Thu, 7 Mar 2019 17:48:58 -0800 (PST)
Received: from mail-pg1-x52d.google.com (mail-pg1-x52d.google.com [IPv6:2607:f8b0:4864:20::52d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 579FB1310FF for <igmp-mld-bis@ietf.org>; Thu, 7 Mar 2019 17:48:58 -0800 (PST)
Received: by mail-pg1-x52d.google.com with SMTP id b2so12759894pgl.9 for <igmp-mld-bis@ietf.org>; Thu, 07 Mar 2019 17:48:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=arista.com; s=googlenew; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=1Pb1xSeJDRbmQhlm+WPRiR9fecfMlnnKAgbjaXNJBr0=; b=hOCU0qONj1FYBkM8uxs9FAhcjvvdGbr6qESCIlvmLvd8YBajaevOTeSgjOsRptYZxL u7cMvrecy890eEVvn40ANd1SSp1aPFIsqTZoaO0BG3DKPiHvNLYcjMkcPkDwgIx9wu8O zz35fSY/Yo/yWhqp4oQwVYSkCbz1qd1Ieggb1dP8CE5g2G5g4KsYsGezPAmAWe7UKfwB vJ1/+gNhRvGD0dwC4jHV8SIPIrgijVYpJZ1EcXYvBWO5fBNxODfXYwbGPC49mTwhVMh1 dNEhjtugD81T+58pAdPc5y4lrkjC01xdqXK+dE4iVlK3MjNXzBHLpmbpBNgfAF4OZ+DT uhog==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=1Pb1xSeJDRbmQhlm+WPRiR9fecfMlnnKAgbjaXNJBr0=; b=MpcxtRo7euwyXHnMUeVl5o8l/SqIVzEqCj6D0H0SOe1ChU9AjMi/D5kb1icqnfsayC RjQsNcjy/BGmFVHde0OmJHU8S/vvhp14cm3+QIeX1AGPFzUwBnjakWQsx1/ISMmuCcya /isohmbCWvFg+HfZcVA8fTCv9Y9MPmDN453REJfOn5I1DeJmsk2c8f0bTqjXI+d74rZg 5+nNWJaRWiFbJQkAS1TL/lKmbJgbMPGkKLaeLSINDPtDIMMtzPltAiEMigEA6Ob4pwBT ilznlQWEUEW0DvnjiHv/szkv6jBxDkkO15Jjc3z8k/PhjirObME5zRk2ZGwnZiOQwakm F8nA==
X-Gm-Message-State: APjAAAXKHTALSfZ0+WzKZaxT8xj/ttQ2zNHasX3/4Py/G12GJvYgVb+m tZNQ5F74VjtfE3KT+xfM8SzeQQ==
X-Google-Smtp-Source: APXvYqxBU1gUmFPJERakn0OIGcHFklSwJ+uaNt48nV+6mV2lCr3V7W1Uqk0TP4XT/Z4mjhQwXadEWg==
X-Received: by 2002:a17:902:7b90:: with SMTP id w16mr16443424pll.228.1552009737554; Thu, 07 Mar 2019 17:48:57 -0800 (PST)
Received: from [192.168.1.81] (host217-39-43-202.range217-39.btcentralplus.com. [217.39.43.202]) by smtp.gmail.com with ESMTPSA id i7sm8471135pgp.62.2019.03.07.17.48.55 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 07 Mar 2019 17:48:56 -0800 (PST)
From: Olufemi Komolafe <femi@arista.com>
Message-Id: <828507AD-7BE7-4E5A-B0F4-CA121717DC15@arista.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_9BB97376-8EED-40BA-900B-EBA5C4927C05"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Date: Fri, 8 Mar 2019 01:49:07 +0000
In-Reply-To: <011BE099-D1C7-430A-9502-11787CEBC54D@cisco.com>
Cc: Michael McBride <Michael.McBride@huawei.com>, "igmp-mld-bis@ietf.org" <igmp-mld-bis@ietf.org>
To: "Mankamana Mishra (mankamis)" <mankamis@cisco.com>
References: <16B07F66-593E-42D8-A8FE-FBEDCE94650F@cisco.com> <8CCB28152EA2E14A96BBEDC15823481A1CEBEDA4@sjceml521-mbs.china.huawei.com> <D7A799CE-2FBD-4E4D-9208-F7036E40ED0F@arista.com> <011BE099-D1C7-430A-9502-11787CEBC54D@cisco.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/igmp-mld-bis/O4TxhUx_fkzXS4jLXxdl0T-WbIA>
Subject: Re: [Igmp-mld-bis] Initial version of Questionnaire
X-BeenThere: igmp-mld-bis@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <igmp-mld-bis.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/igmp-mld-bis>, <mailto:igmp-mld-bis-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/igmp-mld-bis/>
List-Post: <mailto:igmp-mld-bis@ietf.org>
List-Help: <mailto:igmp-mld-bis-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/igmp-mld-bis>, <mailto:igmp-mld-bis-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Mar 2019 01:49:30 -0000

Mankamana,

OK, I’ve simply written out some proposed text below for the draft.

Reading through Stig’s original email again, it seems that we should focus mostly on IGMPv3 and MLDv2. 

I think most of the questions we’ve discussed over the weeks are covered in the questions listed under the different headings below.  These are just some suggestions. Feel free to add other questions.  

I was wondering if we could itemize the different features specified in the MLDv2 and IGMPv3 RFCs to help guide people as they complete the questionnaire?  Basically have a list of features that the user can just tick the supported ones?

Any other thoughts/feedback?

Regards,
Femi


1. Introduction

IGMPv3 [RFC 3376] and MLDv2 [RFC 3810] 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 RFC 3376 and RFC 3810 that have not been widely used and also to determine any interoperability issues that have arisen from using the protocols.

Following approach taken for PIM-SM, documented in RFC 7063, 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.

This document describes the procedures proposed for conducting the survey and introduces the proposed questions.     

2. Procedures Followed

2.1 Methodology
The PIM WG Chairs will officially kick off the survey and distribute the questionnaire and pertinent information through appropriate forums, aiming to ensure the questionnaire reaches as wide an audience as possible. 
 
2.2 Intended Recipients of Questionnaire
Given the nature of IGMPv3 and MLDv2, the questionnaire proposed in this document will be targeted at:
1 - Network operators
2 - Router vendors
3 - Switch vendors
4 - Host implementors

2.3 Processing of Responses
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.


3. Questionnaire

3.1 Questionnaire for Vendors or Host implementors

Name:

Affiliation/Organization?:

Contact Email:

Do you wish to keep your name and affiliation confidential:

Brief description of IGMPv3/MLDv2 implementation:

1. Implementation Status
Which of the following have you implemented? And for how long has it been implemented?
IGMPv1 (RFC 1112) Implemented: Y/N Since:
IGMPv2 (RFC 2236) Implemented: Y/N Since:
IGMPv3 (RFC 3376) Implemented: Y/N Since:
Lightweight IGMPv3 (RFC 5790) Implemented: Y/N Since:
MLDv1 (RFC 2710) Implemented: Y/N Since:
MLDv2 (RFC 3810) Implemented: Y/N Since:
Lightweight MLDv2 (RFC 5790) Implemented: Y/N Since:

2. Implementation Specifics
2.1 Which IGMPv3 features have you implemented?

2.2 Which MLDv2 features have you implemented?

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

3. Implementation Perspectives
3.1 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?

3.2 Which ambiguities or inconsistencies in RFC 3376 or RFC 3810 made the implementation challenging?

3.3 What suggestions would you make to the IETF PIM WG as it seeks to update these documents?



3.2 Questionnaire for Network Operators
Name:

Affiliation/Organization?:

Contact Email:

Do you wish to keep your name and affiliation confidential:

Brief description of IGMPv3/MLDv2 deployment:

1. Deployment Status
Which of the following are currently deployed in your network? And for how long has it been deployed?
IGMPv1 (RFC 1112) Deployed: Y/N Since:
IGMPv2 (RFC 2236) Deployed: Y/N Since:
IGMPv3 (RFC 3376) Deployed: Y/N Since:
Lightweight IGMPv3 (RFC 5790) Deployed: Y/N Since:
MLDv1 (RFC 2710) Deployed: Y/N Since:
MLDv2 (RFC 3810) Deployed: Y/N Since:
Lightweight MLDv2 (RFC 5790) Deployed: Y/N Since:

2. Deployment Specifics

2.1 Which IGMPv3 features are in use?
+ Is IGMP Membership Exclude mode with source list in use?

2.2 Which MLDv2 features are in use?
+ Is Exclude mode with source list for used for MLDv2?

2.3 Does your network rely on the fallback mechanism between different IGMP versions?
+ Between which IGMP versions?
+ What is your experience with this fallback mechanism?

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

3. Deployment Perspectives
3.1 What have you found to be the strengths of IGMPv3/MLDv2?
3.2 What have you found to be the weaknesses IGMPv3/MLDv2?
3.3 What suggestions would you make to the IETF PIM WG as it seeks to update these documents?




> On 7 Mar 2019, at 22:12, Mankamana Mishra (mankamis) <mankamis@cisco.com> wrote:
> 
> Feel free to update nroff file directly. If this does not work out / or not comfortable provide comment in text file. I can copy.
>  
> Thanks
> Mankamana
>  
>  
> From: Olufemi Komolafe <femi@arista.com>
> Date: Thursday, March 7, 2019 at 2:11 PM
> To: Michael McBride <Michael.McBride@huawei.com>
> Cc: "Mankamana Mishra (mankamis)" <mankamis@cisco.com>om>, "igmp-mld-bis@ietf.org" <igmp-mld-bis@ietf.org>
> Subject: Re: [Igmp-mld-bis] Initial version of Questionnaire
>  
> Mankamana, 
>  
> Thanks a lot for making a start with the draft.  I was going to edit some of the text.  Shall I just edit it directly or do you want me to list the suggested changes?
>  
> Also, more importantly, I think we really should structure the questions better.   I think structuring them will make it easier for the folks completing the question, help us get more insightful answers and make the analysis easier.  I had suggested some structure in the Wiki (e.g. dividing the questions into headings such as “Deployment Status”, “Deployment Specifics” and “Deployment Perspectives”  and similarly for implementation etc).  Please feel free to modify these headings or even propose new ones but I think that dividing the questions into such headings will improve the whole process.
>  
> Regards,
> Femi
>  
> On 7 Mar 2019, at 19:35, Michael McBride <Michael.McBride@huawei.com <mailto:Michael.McBride@huawei.com>> wrote:
>  
> Hi Mankamana,
>  
> Looking good. Please consider making the following changes:
>  
>        3- Do you know if your implementation is based on [RFC3376]
>  
> MM- Instead: “Is your implementation based on [RFC3376]?”
>  
>        4- Do you know if lightweight IGMPv3 [RFC5790] is deployed in your network ?
>  
> MM- Instead: “Is lightweight IGMPv3 [RFC5790] deployed in your network ?
>        7- Does any application uses Exclude mode with source list for MLDv2 ?
>                                                    ^^^
> MM-use
>  
>        8- Which part of IGMPv3 RFC 3376 is used more often ?
>  
> MM-Fairly wide open question. Perhaps that’s what you want. But the reader may need some guidance by following the existing question with something like “ex: INCLUDE/EXCLUDE source filtering, socket filtering, etc”
>  
>        10-Does your network still has deployment for IGMPv1 [RFC1112]?
>                                                         ^^^
>  
> MM- Instead: “Does your network still have IGMPv1 [RFC1112] deployed?”
>  
> Thanks,
> mike
>  
> From: Igmp-mld-bis [mailto:igmp-mld-bis-bounces@ietf.org <mailto:igmp-mld-bis-bounces@ietf.org>] On Behalf Of Mankamana Mishra (mankamis)
> Sent: Thursday, March 07, 2019 10:20 AM
> To: igmp-mld-bis@ietf.org <mailto:igmp-mld-bis@ietf.org>
> Subject: [Igmp-mld-bis] Initial version of Questionnaire
>  
> Hi Team, 
> Please find the initial version of draft.  Attaching original nroff too, but you can optionally provide comment in text file directly, I can make the edit in nroff file.
>  
> Thanks 
> Mankamana 
>  
> -- 
> Igmp-mld-bis mailing list
> Igmp-mld-bis@ietf.org <mailto:Igmp-mld-bis@ietf.org>
> https://www.ietf.org/mailman/listinfo/igmp-mld-bis <https://www.ietf.org/mailman/listinfo/igmp-mld-bis>