Re: [Igmp-mld-bis] Meet in Montreal?

Olufemi Komolafe <femi@arista.com> Tue, 23 July 2019 19:30 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 011341208F4 for <igmp-mld-bis@ietfa.amsl.com>; Tue, 23 Jul 2019 12:30:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 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_HELO_NONE=0.001, SPF_PASS=-0.001, 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 0o_vUcjv8KOE for <igmp-mld-bis@ietfa.amsl.com>; Tue, 23 Jul 2019 12:30:44 -0700 (PDT)
Received: from mail-pf1-x42c.google.com (mail-pf1-x42c.google.com [IPv6:2607:f8b0:4864:20::42c]) (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 853A21208DC for <igmp-mld-bis@ietf.org>; Tue, 23 Jul 2019 12:30:44 -0700 (PDT)
Received: by mail-pf1-x42c.google.com with SMTP id q10so19626226pff.9 for <igmp-mld-bis@ietf.org>; Tue, 23 Jul 2019 12:30:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=arista.com; s=googlenew; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=Ew33g0z8ILLTJGJ65wHaPVZK/2m1nvic/fd6XcB2EdY=; b=SVTZI0rMkcVyPs0zPImQefq9WClLyo21EHnCjAh6ioFMKjlGkVJ6ga7GPZVarXck4K vkekCZWIuT9EdtBWDzjAxvIEneBg0FjsE0fUyzBU6Kj6msG0NaA2HU4yvxwNCYtsBSnz 5Dl8KwqSY7MwogvlNKU9BTqVk7ZlcYMWkjv8JrXIZLYKrBwNjo1XzLNIqsUniSgWL9zY X0PcpAG2Go9V7zcBvyVhQQVN5BX/s7PvlPhN+dmKMxWG8zrTkYhrWslLXRnKUXpCVZHl XsKLbx7WGE3jz80/exEL12Bt6J+Kj3xLgue89k0ygSJ5xLcBPAQMGqR3QsjIXOFoLNB7 ViLg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=Ew33g0z8ILLTJGJ65wHaPVZK/2m1nvic/fd6XcB2EdY=; b=rnOI6P4ScFbo0NkQ/LXiIzUtEUaWYItZ+D0X87Lrr8GWWkhOVCzv0gKwezJ3I6HyZK Gc3sfknyOGJ0+cWmWfjOYe00+nVOxcQc2Lj1JDUU1e8EMtbd3t2QYR4jfxz1k02HVtKc t9mZQ2Fl8pQ7W1E8T4Sec9iGrsD485RHGMoS+WeFfpJKoSQXFJgG+vxhOmlU07IOmHG6 CZAb73NaqK9UxLBi3hk0Bt7ntFbhzEiHScRTPkmfBL0DFOtuc99r8q1zgdbigKpiOKpo aQc15IU7W7e2oQBGcw7UOICcdOT0sgkoLYV/oGZ5FzFBTvoaczmiQUI53OU5UUYU40Ss tVhQ==
X-Gm-Message-State: APjAAAW8ohAjEje3FQlk0H/wuxBpjefbfUM7a03HZuY6VeJgzPaqfrdV dpNsa6H+XDGdIm8MIZFr/NaQZy3qjJiurH266ldzxl/dqsza36FM1SzH1XNIURnY9+hmSSGUoHF cFWrpCN9Jsdb9pCPHAnLsDEfuV45gN4inFzCqYXA/ElFVqStuNob465+ZzcDl+qJ69SJPJDgGOM 3mf4D98+ziL57YDk8=
X-Google-Smtp-Source: APXvYqyP+ApAAnO+ol+anoqyJFeZiwGsuXdllxdTHy//hW7iZjIY6QQQoq6KokpXIiu4BNNq/ia0rQ==
X-Received: by 2002:a62:3347:: with SMTP id z68mr7565378pfz.174.1563910243995; Tue, 23 Jul 2019 12:30:43 -0700 (PDT)
Received: from ?IPv6:2620:a0:4001:100::1ac? ([2620:a0:4001:100::1ac]) by smtp.gmail.com with ESMTPSA id t8sm47634202pfq.31.2019.07.23.12.30.41 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 23 Jul 2019 12:30:43 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: Olufemi Komolafe <femi@arista.com>
In-Reply-To: <CAHANBtKb-M9DLwmrNt15-nvpjkwr=oOYt5csJ97t+6Ovs8MDXA@mail.gmail.com>
Date: Tue, 23 Jul 2019 15:30:38 -0400
Cc: Toerless Eckert <tte@cs.fau.de>, Timothy Winters <twinters@iol.unh.edu>, Tim Chown <Tim.Chown@jisc.ac.uk>, "igmp-mld-bis@ietf.org" <igmp-mld-bis@ietf.org>, Hitoshi Asaeda <asaeda@ieee.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <2F35843F-EFAF-4622-A0F1-3144B4C41ED2@arista.com>
References: <20190723173747.45vmewvyedcuadmj@faui48f.informatik.uni-erlangen.de> <CAHANBtKb-M9DLwmrNt15-nvpjkwr=oOYt5csJ97t+6Ovs8MDXA@mail.gmail.com>
To: Stig Venaas <stig@venaas.com>
X-Mailer: Apple Mail (2.3273)
X-CLOUD-SEC-AV-Info: arista,google_mail,monitor
X-CLOUD-SEC-AV-Sent: true
X-Gm-Spam: 0
X-Gm-Phishy: 0
Archived-At: <https://mailarchive.ietf.org/arch/msg/igmp-mld-bis/aKj5RRzMz-QEsZ0EChRsVeLq3u8>
Subject: Re: [Igmp-mld-bis] Meet in Montreal?
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: Tue, 23 Jul 2019 19:30:48 -0000

Stig,

> On 23 Jul 2019, at 14:47, Stig Venaas <stig@venaas.com> wrote:
> 
> Hi
> 
> Too bad I didn't see this until now. The main question I have for you
> guys is whether you tried to create a list of features, to help people
> answer consistently which features they have deployed. It may be hard
> for some to understand that question, and think of what is a feature.

We debated whether or not to include a list of features.  And also whether we should restrict ourselves to features explicitly defined in the RFC or mention features that are not defined in the RFCs but are commonly thought of as IGMPv3 features (e.g. snooping proxy).

For IGMPv3, the identified features so far are:
+ SSM membership report
+ Include mode with source list
+ Exclude mode with source list

Any thoughts?

Should we list only features defined in the specific RFCs or take a more liberal approach?

Regards,
Femi


> 
> Can one of you give a brief update in the pim WG? It helps that people
> know what is going on, and people in the WG may also be able to assist
> in spreading the survey.
> 
> Stig
> 
> On Tue, Jul 23, 2019 at 10:38 AM Toerless Eckert <tte@cs.fau.de> wrote:
>> 
>> Thanks folks for catching up.
>> 
>> Points collected:
>> 
>> a) Tim Chown: When you get irregular responses like "i do not understand
>>   the questions", please inform us (anonymized).
>> 
>> b) Let discuss during WG meeting ideas whom to send to:
>>    groups, e.g.:
>>      internet2 multicast group
>>    multiplicators, e.g.:
>>      Dino Farinacci (still working with a customer, knowin operators).
>> 
>> Cheers
>>    Toerless
>> 
>> In-Reply-To: <20190723154907.3b74oiijconcdgjv@faui48f.informatik.uni-erlangen.de>
>> 
>> On Tue, Jul 23, 2019 at 05:49:07PM +0200, Toerless Eckert wrote:
>>> I need to chair my WG at 1:30, so meet would be nice, but i don't think
>>> that time then is sufficient to go to some lunch place, so if anybody
>>> is interest to go to llunch at noon, let me know, i will be back at 1PM
>>> before Laurier to meet.
>>> 
>>> On Tue, Jul 23, 2019 at 11:36:17AM -0400, Timothy Winters wrote:
>>>> I can be free at 1.
>>>> 
>>>> ~Tim
>>>> 
>>>> On Tue, Jul 23, 2019 at 11:34 AM Olufemi Komolafe <femi=
>>>> 40arista.com@dmarc.ietf.org> wrote:
>>>> 
>>>>> Perhaps we can meet at 1pm then if that works better?  Perhaps Tim will be
>>>>> free by then too?
>>>>> 
>>>>> We can meet on the first floor, perhaps at the entrance to Laurier?
>>>>> 
>>>>> Regards,
>>>>> Femi
>>>>> 
>>>>>> On 23 Jul 2019, at 11:30, Toerless Eckert <tte@cs.fau.de> wrote:
>>>>>> 
>>>>>> How long do you think ? 12:30 ?
>>>>>> 
>>>>>> On Tue, Jul 23, 2019 at 11:28:50AM -0400, Hitoshi Asaeda wrote:
>>>>>>> Ah, sorry, I'm also booked another meeting this noon.
>>>>>>> But whenever my meeting is over, I try to join.
>>>>>>> Sorry about that.
>>>>>>> 
>>>>>>> Hitoshi
>>>>>>> 
>>>>>>>> On Jul 23, 2019, at 11:24, Toerless Eckert <tte@cs.fau.de> wrote:
>>>>>>>> 
>>>>>>>> Sounds good. Foyer = ground floor of hotel ?!
>>>>>>>> 
>>>>>>>> On Tue, Jul 23, 2019 at 09:46:27AM -0400, Olufemi Komolafe wrote:
>>>>>>>>> Does meeting at noon today still work for the folks in Montreal?  If
>>>>> so, shall we just meet in the foyer and we can grab a spot to chat?
>>>>>>>>> 
>>>>>>>>> I think our goal should be to try to ensure there???s nothing
>>>>> outstanding and finalise what we should tell the WG chairs to try to
>>>>> progress this work, hopefully this week.
>>>>>>>>> 
>>>>>>>>> Regards,
>>>>>>>>> Femi
>>>>>>>>> 
>>>>>>>>>> On 19 Jul 2019, at 07:45, Olufemi Komolafe <femi@arista.com> wrote:
>>>>>>>>>> 
>>>>>>>>>> Hi,
>>>>>>>>>> 
>>>>>>>>>> I???ll be there too.
>>>>>>>>>> 
>>>>>>>>>> So I believe we have Tim, Toerless, Hitoshi and myself.  Anyone else?
>>>>>>>>>> 
>>>>>>>>>> Shall we try to meet on Tuesday, then?  Say at noon?  Anyone that
>>>>> does not suit?
>>>>>>>>>> 
>>>>>>>>>> Nice work getting a response to the survey, Hitoshi.
>>>>>>>>>> 
>>>>>>>>>> Regards,
>>>>>>>>>> Femi
>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>>>> On 19 Jul 2019, at 11:28, Hitoshi Asaeda <asaeda@ieee.org> wrote:
>>>>>>>>>>> 
>>>>>>>>>>> Hi folks,
>>>>>>>>>>> 
>>>>>>>>>>> I'll be there.
>>>>>>>>>>> 
>>>>>>>>>>> I'm sorry I've not contributed to this draft update.
>>>>>>>>>>> I'm not an operator and have no information privately, but I asked
>>>>> one Japanese operator to give some input based on the questionnaire and got
>>>>> it. I hope it can be a good input.
>>>>>>>>>>> 
>>>>>>>>>>> Regards,
>>>>>>>>>>> 
>>>>>>>>>>> Hitoshi
>>>>>>>>>>> 
>>>>>>>>>>> 
>>>>>>>>>>> ===from here===
>>>>>>>>>>> 
>>>>>>>>>>> 3.2.  Questionnaire for Network Operators
>>>>>>>>>>> 
>>>>>>>>>>> Name: Takatoshi Ikeda
>>>>>>>>>>> 
>>>>>>>>>>> Affiliation/Organization: APAN-JP
>>>>>>>>>>> 
>>>>>>>>>>> Contact Email: ops@jp.apan.net
>>>>>>>>>>> 
>>>>>>>>>>> Do you wish to keep your name and affiliation confidential?:
>>>>>>>>>>> 
>>>>>>>>>>> 3.2.1.  Deployment Status
>>>>>>>>>>> 
>>>>>>>>>>> Which of the following are currently deployed in your network?  And
>>>>>>>>>>> for how long has it been deployed?
>>>>>>>>>>> 
>>>>>>>>>>> 1.  IGMPv1 [RFC1112] deployed?: N, since:
>>>>>>>>>>> 
>>>>>>>>>>> 2.  IGMPv2 [RFC2236] deployed?: Y, since:
>>>>>>>>>>> 
>>>>>>>>>>> 3.  IGMPv3 [RFC3376] deployed?: Y, since:
>>>>>>>>>>> 
>>>>>>>>>>> 4.  Lightweight IGMPv3 [RFC5790] Implemented: N, since:
>>>>>>>>>>> 
>>>>>>>>>>> 5.  MLDv1 [RFC2710] deployed?: Y, since:
>>>>>>>>>>> 
>>>>>>>>>>> 6.  MLDv2 [RFC3810] deployed?: Y, since:
>>>>>>>>>>> 
>>>>>>>>>>> 7.  Lightweight MLDv2 [RFC5790] deployed?: N, since:
>>>>>>>>>>> 
>>>>>>>>>>> 3.2.2.  Deployment Specifics
>>>>>>>>>>> 
>>>>>>>>>>> 1.  Which IGMPv3 features are in use?  (Is Exclude mode with source
>>>>>>>>>>>   list in use?)
>>>>>>>>>>>    Membership-report for SSM
>>>>>>>>>>>    No filter function is used.
>>>>>>>>>>> 
>>>>>>>>>>> 
>>>>>>>>>>> 2.  Which MLDv2 features are in use?  (Is Exclude mode with source
>>>>>>>>>>>   list in use?)
>>>>>>>>>>>    Membership-report for SSM
>>>>>>>>>>>    No filter function is used.
>>>>>>>>>>> 
>>>>>>>>>>> 
>>>>>>>>>>> 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?)
>>>>>>>>>>> 
>>>>>>>>>>>    No
>>>>>>>>>>> 
>>>>>>>>>>> 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?)
>>>>>>>>>>> 
>>>>>>>>>>>   No
>>>>>>>>>>> 
>>>>>>>>>>> 3.2.3.  Deployment Perspectives
>>>>>>>>>>> 
>>>>>>>>>>> 1.  What have you found to be the strengths of IGMPv3/MLDv2?
>>>>>>>>>>>   Specifying Source for Multicast
>>>>>>>>>>> 
>>>>>>>>>>> 2.  What have you found to be the weaknesses of IGMPv3/MLDv2?
>>>>>>>>>>>   None
>>>>>>>>>>> 
>>>>>>>>>>> 3.  What suggestions would you make to the PIM WG as it seeks to
>>>>>>>>>>>   update these documents?
>>>>>>>>>>> 
>>>>>>>>>>> ===to here===
>>>>>>>>>>> 
>>>>>>>>>>> 
>>>>>>>>>>>> On Jul 17, 2019, at 4:59, Toerless Eckert <tte@cs.fau.de> wrote:
>>>>>>>>>>>> 
>>>>>>>>>>>> I hope i can go to IETF105 and would be happy to meet. Have not
>>>>> tried to
>>>>>>>>>>>> work out my schedule, but if i am there, it will be whole week.
>>>>>>>>>>>> 
>>>>>>>>>>>> Who else is coming ?
>>>>>>>>>>>> 
>>>>>>>>>>>> Cheers
>>>>>>>>>>>> Toerless
>>>>>>>>>>>> 
>>>>>>>>>>>> On Mon, Jul 15, 2019 at 07:07:55PM +0000, Mankamana Mishra
>>>>> (mankamis) wrote:
>>>>>>>>>>>>> Hi,
>>>>>>>>>>>>> This IETF I would not be able to make it.
>>>>>>>>>>>>> 
>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>> Mankamana
>>>>>>>>>>>>> 
>>>>>>>>>>>>> 
>>>>>>>>>>>>> From: Igmp-mld-bis <igmp-mld-bis-bounces@ietf.org> on behalf of
>>>>> Timothy Winters <twinters@iol.unh.edu>
>>>>>>>>>>>>> Date: Monday, July 15, 2019 at 12:06 PM
>>>>>>>>>>>>> To: Olufemi Komolafe <femi=40arista.com@dmarc.ietf.org>
>>>>>>>>>>>>> Cc: "igmp-mld-bis@ietf.org" <igmp-mld-bis@ietf.org>
>>>>>>>>>>>>> Subject: Re: [Igmp-mld-bis] Meet in Montreal?
>>>>>>>>>>>>> 
>>>>>>>>>>>>> I'm available Tuesday morning.
>>>>>>>>>>>>> 
>>>>>>>>>>>>> ~Tim
>>>>>>>>>>>>> 
>>>>>>>>>>>>> On Sun, Jul 14, 2019 at 3:01 PM Olufemi Komolafe <femi=
>>>>> 40arista.com@dmarc.ietf.org<mailto:40arista.com@dmarc.ietf.org>> wrote:
>>>>>>>>>>>>> Not sure who is attending IETF 105 in Montreal next week but I
>>>>> was thinking that perhaps those of us attending can fix a time/place to
>>>>> meet up?
>>>>>>>>>>>>> 
>>>>>>>>>>>>> It might be an idea to meet on Monday or Tuesday, i.e. before the
>>>>> PIM WG meeting on Thursday, to try to progress and finalise the survey?
>>>>>>>>>>>>> 
>>>>>>>>>>>>> Also, there have been some discussions on the thread recently so
>>>>> it???d be good for folks to please take a look and provide any
>>>>> thoughts/feedback?
>>>>>>>>>>>>> 
>>>>>>>>>>>>> In my opinion, we should aim to handing over the survey to the WG
>>>>> chairs before the meeting so the focus can shift on to starting the actual
>>>>> mechanics of distributing the survey etc.
>>>>>>>>>>>>> 
>>>>>>>>>>>>> Regards,
>>>>>>>>>>>>> Femi
>>>>>>>>>>>>> 
>>>>>>>>>>>>> --
>>>>>>>>>>>>> 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
>>>>>>>>>>>> 
>>>>>>>>>>>>> --
>>>>>>>>>>>>> Igmp-mld-bis mailing list
>>>>>>>>>>>>> Igmp-mld-bis@ietf.org
>>>>>>>>>>>>> https://www.ietf.org/mailman/listinfo/igmp-mld-bis
>>>>>>>>>>>> 
>>>>>>>>>>>> 
>>>>>>>>>>>> --
>>>>>>>>>>>> ---
>>>>>>>>>>>> tte@cs.fau.de
>>>>>>>>>>>> 
>>>>>>>>>>>> --
>>>>>>>>>>>> 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
>>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> --
>>>>>>>>> Igmp-mld-bis mailing list
>>>>>>>>> Igmp-mld-bis@ietf.org
>>>>>>>>> https://www.ietf.org/mailman/listinfo/igmp-mld-bis
>>>>>>>> 
>>>>>>>> --
>>>>>>>> ---
>>>>>>>> tte@cs.fau.de
>>>>>>> 
>>>>>>> --
>>>>>>> Igmp-mld-bis mailing list
>>>>>>> Igmp-mld-bis@ietf.org
>>>>>>> https://www.ietf.org/mailman/listinfo/igmp-mld-bis
>>>>>> 
>>>>>> --
>>>>>> ---
>>>>>> tte@cs.fau.de
>>>>>> 
>>>>>> --
>>>>>> 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
>>>>> 
>>> 
>>>> --
>>>> Igmp-mld-bis mailing list
>>>> Igmp-mld-bis@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/igmp-mld-bis
>>> 
>>> 
>>> --
>>> ---
>>> tte@cs.fau.de
>>> 
>>> --
>>> Igmp-mld-bis mailing list
>>> Igmp-mld-bis@ietf.org
>>> https://www.ietf.org/mailman/listinfo/igmp-mld-bis
>> 
>> --
>> ---
>> tte@cs.fau.de
>> 
>> --
>> Igmp-mld-bis mailing list
>> Igmp-mld-bis@ietf.org
>> https://www.ietf.org/mailman/listinfo/igmp-mld-bis