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

Hitoshi Asaeda <asaeda@ieee.org> Fri, 08 March 2019 10:02 UTC

Return-Path: <asaeda@ieee.org>
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 D1F10130EE4 for <igmp-mld-bis@ietfa.amsl.com>; Fri, 8 Mar 2019 02:02:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ieee.org
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 z8SFcbajiOgc for <igmp-mld-bis@ietfa.amsl.com>; Fri, 8 Mar 2019 02:02:05 -0800 (PST)
Received: from mail-pg1-x544.google.com (mail-pg1-x544.google.com [IPv6:2607:f8b0:4864:20::544]) (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 D420E130E2B for <igmp-mld-bis@ietf.org>; Fri, 8 Mar 2019 02:02:03 -0800 (PST)
Received: by mail-pg1-x544.google.com with SMTP id 125so13527845pgc.12 for <igmp-mld-bis@ietf.org>; Fri, 08 Mar 2019 02:02:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ieee.org; s=google; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=8C5aItapHKrg9YfPnWSQJMHblHfuzpAYDZTUtG9Jzoo=; b=Xjws9Q6A+8Bb/3GBt97OihVe4nXuaBpbWOMpUKlEtnl/NNdOWkzoGMgLodKRFtzZLr sfmrLsqXhhgQFTxSCE8sFij0BTZvlAsouhSBrAfH93ADnc2lOsVfUvnTl95paP7LIpkO 47eFH9jOGhTQREn4ao3hRKiORB0SFQjSZIxwk=
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=8C5aItapHKrg9YfPnWSQJMHblHfuzpAYDZTUtG9Jzoo=; b=ZFobLd4DOyHBlZK+mdss53d4lWBZVJQCEfAgdQ2LJPul9wLJhMKcB5yxFiIhq0TPZw x6AhXIkV/3Ov9ZL8MmRAZpavCwKMj2+jPhzPH1Vd9itNZCZl0y6Z2wRQlupYSXXdQQaL fSYSQmoYqi0vQtntPzhYK8apKim9K3igtbhwjhTJAhHJMoV0bi4ujfdGE30e/DWLLyh4 dQK8ExL6je1F7HdG4WRvFSp0gt/9InofEZRw4LXLFQ9YLQrDVqCOgcAY1eqhPoilzrVj BJF8FoPfQY8ddNdzPJ55s4K4nYkWn65f76Yf25L5cCfpC6mxlDL0NmzqBXnuc+Se9/al ltcw==
X-Gm-Message-State: APjAAAUP32j85fTdD7/AZb/2/uFUK5AKiG/W248W1LNONFNk4vcX5M1M JuCVdQ9Mf5MRydQAXSRg9J9CoQ==
X-Google-Smtp-Source: APXvYqw3aui7AMZ5MDBTHuSO0k+2ijJ2MDXzGdYgzQOk9xzqNIInqDAHF+Z9yfBsWadtI704BCPW4g==
X-Received: by 2002:a62:e719:: with SMTP id s25mr17499365pfh.12.1552039322462; Fri, 08 Mar 2019 02:02:02 -0800 (PST)
Received: from [133.69.36.103] ([133.69.36.103]) by smtp.gmail.com with ESMTPSA id d26sm10277455pfn.86.2019.03.08.02.02.00 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 08 Mar 2019 02:02:01 -0800 (PST)
From: Hitoshi Asaeda <asaeda@ieee.org>
Message-Id: <36520185-EE26-479F-A7F0-2920D45BE694@ieee.org>
Content-Type: multipart/mixed; boundary="Apple-Mail=_E2D26ED7-DCDD-4646-AA84-247EDB9954AB"
Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\))
Date: Fri, 8 Mar 2019 19:01:55 +0900
In-Reply-To: <828507AD-7BE7-4E5A-B0F4-CA121717DC15@arista.com>
Cc: "igmp-mld-bis@ietf.org" <igmp-mld-bis@ietf.org>, Michael McBride <Michael.McBride@huawei.com>
To: Olufemi Komolafe <femi=40arista.com@dmarc.ietf.org>
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> <828507AD-7BE7-4E5A-B0F4-CA121717DC15@arista.com>
X-Mailer: Apple Mail (2.3445.102.3)
Archived-At: <https://mailarchive.ietf.org/arch/msg/igmp-mld-bis/l8pCt4EVamKsT5lm39RefX2cdTg>
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 10:02:10 -0000

Hi folks,

Since nroff is difficult to maintain, I created an xml file for this draft (based on Femi's proposal).
Please use the attached xml file (and revise the text).

Regards,

Hitoshi


> On Mar 8, 2019, at 10:49, Olufemi Komolafe <femi=40arista.com@dmarc.ietf.org> wrote:
> 
> 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> 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] On Behalf Of Mankamana Mishra (mankamis)
>> Sent: Thursday, March 07, 2019 10:20 AM
>> To: 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
>> https://www.ietf.org/mailman/listinfo/igmp-mld-bis
> 
> -- 
> Igmp-mld-bis mailing list
> Igmp-mld-bis@ietf.org
> https://www.ietf.org/mailman/listinfo/igmp-mld-bis