Re: [Igmp-mld-bis] Meetings for IETF IGMP/MLD update volunteer team
Olufemi Komolafe <femi@arista.com> Wed, 09 January 2019 14:46 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 013BE124BE5 for <igmp-mld-bis@ietfa.amsl.com>; Wed, 9 Jan 2019 06:46:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.653
X-Spam-Level:
X-Spam-Status: No, score=-4.653 tagged_above=-999 required=5 tests=[DKIMWL_WL_HIGH=-4.553, 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] 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 lJkDHXEDSe4h for <igmp-mld-bis@ietfa.amsl.com>; Wed, 9 Jan 2019 06:46:54 -0800 (PST)
Received: from mail-pf1-x431.google.com (mail-pf1-x431.google.com [IPv6:2607:f8b0:4864:20::431]) (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 102E21228B7 for <igmp-mld-bis@ietf.org>; Wed, 9 Jan 2019 06:46:54 -0800 (PST)
Received: by mail-pf1-x431.google.com with SMTP id c123so3779910pfb.0 for <igmp-mld-bis@ietf.org>; Wed, 09 Jan 2019 06:46:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=arista.com; s=googlenew; h=from:mime-version:subject:date:references:to:in-reply-to:message-id; bh=Jwwww6PTMphULIZQZgwyy3AWG0dr57XDHqBgwGazG/Q=; b=b2wEfW95SIoL1oKbzFmlDyxkrlosPsRwlrXIEGt6KFHDvDLF2xOdB9ai3AwArHsNY3 miaojut51ln/uCpY/BP5mrZKLY4/zyqJBFyudsL7CTosIXlfZtHBg3dqB5L4nwjypG8S 5BUfzmN59JYRpEmoYy/mO/BTgwOZ6Abr/95liKXyy6opbOFTZmHmBZ8iMr2prjJwBSCX rgybF4DKG1zj+unw6MdvQaSs/oH9zTBOl2paIT9IrsYKlbJ/ie7utxpQ24SMta0vJE7r CXyURJrqzpewq16rOhLB4ljH7gj4tm2UAE7JdFl5oFL8amo4JyFaoXPhqeYM7TlxluAm GRyg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:mime-version:subject:date:references:to :in-reply-to:message-id; bh=Jwwww6PTMphULIZQZgwyy3AWG0dr57XDHqBgwGazG/Q=; b=dUPXOH5Ar7OhnT31CADBjcXdN/jEM2t/J+Urwbh8hcwn3pM1oJva1pAd++3y6Gap/v 0tcjtJyX68SQOzcxfovfw8MvoVuBNKzQaOOZvokgg64ASyQzq8ZP6n45foTr6wLilOkX fL4DoOHArffv17RdnBmJGqemthdAOQgyxH2zm9XcPYpIKCPjKglJ6fCdaorgbKbAkgUf UH2wGvPiPdQs8YDeCLh/wFt+Ko2W8LN06+/5xDRoWkLhaMtz3OGfy8vSE/wfZFQaJoI8 4bAYVpqqJNrPblJN3z9bTeBu8gOnCF8/+Isyv2L/XQ86g2ZDTk9KZrH11AxojsIU/bzR t/XA==
X-Gm-Message-State: AJcUukeFq2Yuutf3esKv5A0k+x97kKG0wLv4Avrs04jTBTD6uk7vBAOc vCUZDaEBff+yBOAQvBecyQJFMEfYiHc=
X-Google-Smtp-Source: ALg8bN6l8lJFYW/bdJWg4Zk11YS2G22aZAsN2U8qhud+TXprkwCaR/QC2pLf7J2ftKbFn/ZxcvBzPQ==
X-Received: by 2002:aa7:8542:: with SMTP id y2mr6317112pfn.83.1547045213067; Wed, 09 Jan 2019 06:46:53 -0800 (PST)
Received: from [192.168.1.81] (host86-146-19-56.range86-146.btcentralplus.com. [86.146.19.56]) by smtp.gmail.com with ESMTPSA id u186sm108599176pfu.51.2019.01.09.06.46.51 for <igmp-mld-bis@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 09 Jan 2019 06:46:52 -0800 (PST)
From: Olufemi Komolafe <femi@arista.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_B152BF48-6522-4DCF-B4A0-39F514F484EA"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Date: Wed, 09 Jan 2019 14:46:49 +0000
References: <ff38cb1916424f5d8342ba18dcce5f48@XCH-RTP-011.cisco.com> <FBAF3327-89B3-4C5F-8F9C-8916B8C363DF@cisco.com> <138B256E-F145-48ED-B50E-B054DD90C207@juniper.net>
To: igmp-mld-bis@ietf.org
In-Reply-To: <138B256E-F145-48ED-B50E-B054DD90C207@juniper.net>
Message-Id: <05A19511-58FB-47E1-B014-D31E61967AF9@arista.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/igmp-mld-bis/p0rJqzhxoo7joAWKisQlDeCoyjo>
Subject: Re: [Igmp-mld-bis] Meetings for IETF IGMP/MLD update volunteer team
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: Wed, 09 Jan 2019 14:46:57 -0000
Here are some very initial thoughts on how we can possibly try to structure the suggested questions. To be updated but just thought I’d share right now…. Regards, Femi —————————————————————————————————————————————————————————————— 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 If IGMPv3 (RFC 3376) is deployed + Is IGMP Membership Exclude mode with source list in use? If MLDv2 (RFC 3810) is deployed + Is Exclude mode with source list for MLDv2? Does your network rely on the fallback mechanism between different IGMP versions? + what versions? 3. Deployment Perspectives What have you found to be the strengths of the protocol(s) you have deployed? What have you found to be the weaknesses of the protocol(s) you have deployed? What suggestions would you make to the IETF PIM WG as it seeks to update these documents? —————————————————————————————————————————————————————————————— 1. Implementation Status Which of the following features have you implemented? [list of key features from different RFCs] 2. Implementation Specifics 3. Implementation Perspectives + What feature(s) has been deliberately omitted from your implementation? + because you think it is a bad or sub-optimal? + because you of insufficient demand/use cases? Which ambiguities or inconsistencies in the RFC made the implementation challenging? What suggestions would you make to the IETF PIM WG as it seeks to update these documents? —————————————————————————————————————————————————————————————— > On 7 Jan 2019, at 02:30, Suneesh Babu <suneesh@juniper.net> wrote: > > Thanks Mankamana. > > Regards, > Suneesh > > From: "Mankamana Mishra (mankamis)" <mankamis@cisco.com> > Date: Thursday, 3 January 2019 at 5:31 AM > To: "Stig Venaas (svenaas)" <svenaas@cisco.com>, Toerless Eckert <tte+ietf@cs.fau.de>, Hitoshi Asaeda <asaeda@ieee.org>, Anish Peter <anish.ietf@gmail.com>, "femi@arista.com" <femi@arista.com>, Suneesh Babu <suneesh@juniper.net>, "N.Leymann@telekom.de" <N.Leymann@telekom.de>, "ramakanthjosyula@gmail.com" <ramakanthjosyula@gmail.com>, "twinters@iol.unh.edu" <twinters@iol.unh.edu>, "Michael.McBride@huawei.com" <Michael.McBride@huawei.com> > Subject: Re: Meetings for IETF IGMP/MLD update volunteer team > > Hi Team, > Attaching the initial questionnaire which I had prepared. And attaching comment from Toerless too. I would merge it and come up with text which covers his comment. Attaching the initial version of document, so that it would give some idea what kind of questions we are going to add. > > > Thanks > Mankamana > > > From: "Stig Venaas (svenaas)" <svenaas@cisco.com> > Date: Wednesday, January 2, 2019 at 3:56 PM > To: "Mankamana Mishra (mankamis)" <mankamis@cisco.com>, Toerless Eckert <tte+ietf@cs.fau.de>, Hitoshi Asaeda <asaeda@ieee.org>, Anish Peter <anish.ietf@gmail.com>, "femi@arista.com" <femi@arista.com>, Suneesh Babu <suneesh@juniper.net>, "N.Leymann@telekom.de" <N.Leymann@telekom.de>, "ramakanthjosyula@gmail.com" <ramakanthjosyula@gmail.com>, "twinters@iol.unh.edu" <twinters@iol.unh.edu>, "Michael.McBride@huawei.com" <Michael.McBride@huawei.com> > Subject: Meetings for IETF IGMP/MLD update volunteer team > > Hi > > I’m setting up this meeting series. I’ve made it bi-weekly for now. We can discuss what is best at our meeting January 9th. > Before the next meeting, please have a look at this wiki and subscribe to the mailing list mentioned there. We want to start using the mailing list ASAP. > https://trac.ietf.org/trac/pim/wiki/igmp-mld-bis <https://urldefense.proofpoint.com/v2/url?u=https-3A__trac.ietf.org_trac_pim_wiki_igmp-2Dmld-2Dbis&d=DwMGaQ&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=SsQgKVptGdoEQ0IwmOYClpveG-Z2a6-RVt3NWZsVhtY&m=xfyDIIHTwAev66q2fAFloUXuL1MCQUGgqnkXE9f9_jU&s=2Y17p1qHkvmgLzHEDZVDGEwmYzlu0B_mTBwJeyYmzc0&e=> > You should all be able to edit this page. Request an account if you don’t have one. I hope the info I provided on participants is correct. Please correct it if needed. > > Enjoy the holidays, > Stig > > -- Do not delete or change any of the following text. -- <> > > > Join WebEx meeting <https://urldefense.proofpoint.com/v2/url?u=https-3A__cisco.webex.com_cisco_j.php-3FMTID-3Dm908071a63cbc651330983bb9cd66673a&d=DwMGaQ&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=SsQgKVptGdoEQ0IwmOYClpveG-Z2a6-RVt3NWZsVhtY&m=xfyDIIHTwAev66q2fAFloUXuL1MCQUGgqnkXE9f9_jU&s=QYKu49wTxQJ5zEccONrrKMCFxmBQ4SjLJcr_D6hc2jg&e=> > Meeting number (access code): 206 081 407 > Meeting password: qSjJS28j (77557285 from phones) > > > Join from a video system or application > Dial 206081407@cisco.webex.com <sip:206081407@cisco.webex.com> > You can also dial 173.243.2.68 and enter your meeting number. > From the Cisco internal network, dial *267* and the 9-digit meeting number. If you are the host, enter your PIN when prompted. > > Join by phone > +1-866-432-9903 <tel:%2B1-866-432-9903,,*01*206081407%2377557285%23*01*> Call-in toll-free number (US/Canada) > +1-408-525-6800 <tel:%2B1-408-525-6800,,*01*206081407%2377557285%23*01*> Call-in toll number (US/Canada) > Global call-in numbers <https://urldefense.proofpoint.com/v2/url?u=https-3A__cisco.webex.com_cisco_globalcallin.php-3FserviceType-3DMC-26ED-3D468649747-26tollFree-3D1&d=DwMGaQ&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=SsQgKVptGdoEQ0IwmOYClpveG-Z2a6-RVt3NWZsVhtY&m=xfyDIIHTwAev66q2fAFloUXuL1MCQUGgqnkXE9f9_jU&s=BhaAfZ16q-xGlg5Xh9elY859xteZUCxp2Pt1g7FBCgo&e=> | Toll-free calling restrictions <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.webex.com_pdf_tollfree-5Frestrictions.pdf&d=DwMGaQ&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=SsQgKVptGdoEQ0IwmOYClpveG-Z2a6-RVt3NWZsVhtY&m=xfyDIIHTwAev66q2fAFloUXuL1MCQUGgqnkXE9f9_jU&s=pN5NwVuM-DLTUn4jH1qezTTgfE9MB9KnnfCyK8vwOPg&e=> > > Join using Microsoft Lync or Microsoft Skype for Business > Dial 206081407.cisco@lync.webex.com <sip:206081407.cisco@lync.webex.com> > > Can't join the meeting? <https://urldefense.proofpoint.com/v2/url?u=https-3A__help.webex.com_docs_DOC-2D5412&d=DwMGaQ&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=SsQgKVptGdoEQ0IwmOYClpveG-Z2a6-RVt3NWZsVhtY&m=xfyDIIHTwAev66q2fAFloUXuL1MCQUGgqnkXE9f9_jU&s=uLjK37sqq1R7_xlbocvBMfWrJycXTXc5fDRp5QZVyY4&e=> > > If you are a host, go here <https://urldefense.proofpoint.com/v2/url?u=https-3A__cisco.webex.com_cisco_j.php-3FMTID-3Dmd27c1c7bcdec4b610b0c0d25998ded46&d=DwMGaQ&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=SsQgKVptGdoEQ0IwmOYClpveG-Z2a6-RVt3NWZsVhtY&m=xfyDIIHTwAev66q2fAFloUXuL1MCQUGgqnkXE9f9_jU&s=oYDdjvkNcQVayRh0zXN_k5-zL4DOHbeHRoPd242PePc&e=> to view host information. > > IMPORTANT NOTICE: Please note that this Webex service allows audio and other information sent during the session to be recorded, which may be discoverable in a legal matter. By joining this session, you automatically consent to such recordings. If you do not consent to being recorded, discuss your concerns with the host or do not join the session.