Re: [Igmp-mld-bis] Tomorrow's meeting

<N.Leymann@telekom.de> Mon, 03 June 2019 12:47 UTC

Return-Path: <N.Leymann@telekom.de>
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 3660B120090 for <igmp-mld-bis@ietfa.amsl.com>; Mon, 3 Jun 2019 05:47:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.307
X-Spam-Level:
X-Spam-Status: No, score=-4.307 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=telekom.de
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 u-hv_gOcFcrD for <igmp-mld-bis@ietfa.amsl.com>; Mon, 3 Jun 2019 05:47:51 -0700 (PDT)
Received: from mailout11.telekom.de (mailout11.telekom.de [194.25.225.207]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0F5F11200FA for <igmp-mld-bis@ietf.org>; Mon, 3 Jun 2019 05:47:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telekom.de; i=@telekom.de; q=dns/txt; s=dtag1; t=1559566068; x=1591102068; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=xVc8S6hpCJ8xFZ2uhr6kptKLCrkUPvjZZGINaOFhBY0=; b=ag9sbw5ru7LeK9VzOZ4n7BDqM9igQtvTzCp1qtCIpGiQSMcojRuoOeMg rqNxkGyJ8tNBSg7PZOBTKeIUZJsWKvRAnBSekgHdU92zO5dYqGPDQvop6 vDKTKsrel8N88RnmVV078TP5rn80CX7w3cCeWg11vfK2n9ta5FZGdUT7M eYucr5CscIHOVk9Q3Wi5S+Vs8oQPyFC2EnO6gvPHin60gTNJR6SJpg4aK jXf5Z93zUL7xg0x9cTJkqfVjKtPrfnshmwmyezNYZETUrMILa+Hzu6svZ V3Qrip+25q1TDj8T2QIq2yWlKoIPRspQGccOdVAXHmuhR64uQuXHloZS5 Q==;
Received: from qde9xy.de.t-internal.com ([10.171.254.32]) by MAILOUT11.dmznet.de.t-internal.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 03 Jun 2019 14:47:45 +0200
X-IronPort-AV: E=Sophos;i="5.60,546,1549926000"; d="scan'208";a="297521174"
X-MGA-submission: MDFu7nBwQq3gZHS1eLwyM2hsj1bQ4OI5S4GLV8JH3+Fo0rJ/rdEoAbiJ6Ks4KMM5DB+ZntiOymB+FRyrgEUJYGaMcWuXgRXaqmllbUqcaTlwSU3IH8x3YRfYSLCcwUgnqFw1YNE+3d3iduotz0LqsRIMbADvXOQ89aQg1YegP4LyGw==
Received: from he105665.emea1.cds.t-internal.com ([10.169.118.62]) by QDE9Y1.de.t-internal.com with ESMTP/TLS/AES256-SHA; 03 Jun 2019 14:45:18 +0200
Received: from HE105664.EMEA1.cds.t-internal.com (10.169.118.61) by HE105665.emea1.cds.t-internal.com (10.169.118.62) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 3 Jun 2019 14:45:17 +0200
Received: from HE106564.emea1.cds.t-internal.com (10.171.40.16) by HE105664.EMEA1.cds.t-internal.com (10.169.118.61) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Mon, 3 Jun 2019 14:45:17 +0200
Received: from GER01-LEJ-obe.outbound.protection.outlook.de (51.5.80.19) by O365mail01.telekom.de (172.30.0.234) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 3 Jun 2019 14:45:14 +0200
Received: from LEJPR01MB0377.DEUPRD01.PROD.OUTLOOK.DE (10.158.142.20) by LEJPR01MB0379.DEUPRD01.PROD.OUTLOOK.DE (10.158.142.22) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1922.21; Mon, 3 Jun 2019 12:45:17 +0000
Received: from LEJPR01MB0377.DEUPRD01.PROD.OUTLOOK.DE ([fe80::d4b8:dd84:b63b:1fa0]) by LEJPR01MB0377.DEUPRD01.PROD.OUTLOOK.DE ([fe80::d4b8:dd84:b63b:1fa0%4]) with mapi id 15.20.1922.025; Mon, 3 Jun 2019 12:45:17 +0000
From: N.Leymann@telekom.de
To: femi=40arista.com@dmarc.ietf.org, tte@cs.fau.de
CC: anish.ietf@gmail.com, igmp-mld-bis@ietf.org, mankamis@cisco.com
Thread-Topic: [Igmp-mld-bis] Tomorrow's meeting
Thread-Index: AQHU/zulRURX2keSgEyovBtRMNFxSaZUr8MAgAGfiQCAAAPAwYArC2uAgAi1HWA=
Date: Mon, 03 Jun 2019 12:45:16 +0000
Message-ID: <LEJPR01MB037769D389C1533F6D66B98E98140@LEJPR01MB0377.DEUPRD01.PROD.OUTLOOK.DE>
References: <94764FD1-AA9D-475F-A888-ADCF941C0565@arista.com> <9516CE1F-999A-4841-9D77-ABD64C642BE3@cisco.com> <CAA6qS9qGB+zm30nm-Or=8oMSQBpLqV=XeJ68Z3h84T-LWX2fxA@mail.gmail.com> <20190501141529.akjsqlqh64x3qnmf@faui48f.informatik.uni-erlangen.de> <5C363D02-6913-4672-82F6-309E10C3E03C@arista.com> <5B00E7A8-F32E-48AC-8CBA-6E0441CD7001@arista.com>
In-Reply-To: <5B00E7A8-F32E-48AC-8CBA-6E0441CD7001@arista.com>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=N.Leymann@telekom.de;
x-originating-ip: [164.19.3.15]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 762610de-4836-43d9-a38e-08d6e821549d
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(5600148)(711020)(4605104)(1401327)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(2017052603328)(7193020); SRVR:LEJPR01MB0379;
x-ms-traffictypediagnostic: LEJPR01MB0379:
x-ms-exchange-purlcount: 1
x-microsoft-antispam-prvs: <LEJPR01MB0379170DCDB5AF1410430EDB98140@LEJPR01MB0379.DEUPRD01.PROD.OUTLOOK.DE>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 0057EE387C
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(136003)(396003)(376002)(39860400002)(346002)(366004)(54094003)(199004)(189003)(26005)(68736007)(3846002)(6116002)(74482002)(66946007)(7736002)(64756008)(5660300002)(4326008)(305945005)(66476007)(66556008)(76116006)(73956011)(186003)(8676002)(71190400001)(71200400001)(8936002)(53936002)(256004)(81166006)(66446008)(81156014)(86362001)(102836004)(53546011)(6306002)(75402003)(316002)(76176011)(7696005)(52396003)(54906003)(33656002)(55016002)(9686003)(2906002)(110136005)(446003)(11346002)(486006)(72206003)(476003)(14454004)(966005)(66066001)(478600001); DIR:OUT; SFP:1101; SCL:1; SRVR:LEJPR01MB0379; H:LEJPR01MB0377.DEUPRD01.PROD.OUTLOOK.DE; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: telekom.de does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: SQJgLC3dDBZI7GnN6YX8bXky9LcCQsfkS17uO1jSpMZl3ogdnoBuUkhZAGsS4HO9DXtdksDRQM4WLY8wLK1qhgb8MTKENbEYt75NDly/mvnL4BqNCo8TdK8ZYvkSWkvGLPzm4z3H2yoUC9Auzvasv+C6yVvxWMbB/bh7RTtmkse5O1xUyGvcTRRtxK1ZQ5K+rXDrXu88TEzKzbIM6H4+LF/h9FiGUzaTNvHmxb6juh1US63niYPnfByV5xscWadbaxaUEn9hRNkFVUcSEMWg+MU+McVZHuh7RD49rtClygTVEP9i2tNfjEp0GUSOJHmKVcwtY7bNUnxf2KP3YbX/gReqrrazdqTlGCA4rMzOml3o6If5iW6gAXwAY2dRA1f7JrRjSLre0jB1QnSA7MRIC5z5X6dLujN77zzusJ1gR9E=
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 762610de-4836-43d9-a38e-08d6e821549d
X-MS-Exchange-CrossTenant-originalarrivaltime: 03 Jun 2019 12:45:17.0175 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bde4dffc-4b60-4cf6-8b04-a5eeb25f5c4f
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: N.Leymann@telekom.de
X-MS-Exchange-Transport-CrossTenantHeadersStamped: LEJPR01MB0379
X-OriginatorOrg: telekom.de
Archived-At: <https://mailarchive.ietf.org/arch/msg/igmp-mld-bis/kdl2dG_RzorXLDmhULMOqEIAs7Y>
Subject: Re: [Igmp-mld-bis] Tomorrow's meeting
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: Mon, 03 Jun 2019 12:47:54 -0000

Hi,

In Section 3.2.1 (Deployment Status) I guess under "4." It should read "deployed?" instead of "Implemented:".

I think giving some more details on the features makes sense. I personally also see IGMP snooping/proxying as a feature 
(on our home gateways) even if those are not part of the protocol itself.

regards

Nic

-----Ursprüngliche Nachricht-----
Von: Igmp-mld-bis <igmp-mld-bis-bounces@ietf.org> Im Auftrag von Olufemi Komolafe
Gesendet: Mittwoch, 29. Mai 2019 01:39
An: Toerless Eckert <tte@cs.fau.de>
Cc: Anish Peter <anish.ietf@gmail.com>; igmp-mld-bis@ietf.org; Mankamana Mishra (mankamis) <mankamis@cisco.com>
Betreff: Re: [Igmp-mld-bis] Tomorrow's meeting

I think we should try to progress this work over the coming weeks.  Hopefully we can meet tomorrow and discuss next steps.

I re-read the latest version of the questionnaire and was wondering if we should spell out what features in the RFCs we are interested in?  For example, in Section 3.1.2, we ask “Which IGMPv3 features have you implemented?” I can imagine some folks giving answers referring to what they consider IGMPv3 features (e.g. snooping proxy etc) that are not actually in the RFCs we are focusing on.  Furthermore, in the PIM survey (RFC7063) the authors actually itemise the features in RFC4601 in which they are interested.  So, to help us be able to better process the responses, I wonder if we should itemise the features that we are trying to gauge their popularity?

Which made me wonder,  other than Include list and exclude list, are there other features we should call out?

Regards,
Femi

> On 1 May 2019, at 15:18, Olufemi Komolafe <femi@arista.com> wrote:
> 
> Mankamana, Timothy and myself were on the call.  Mankamana is going to email the chairs to try to determine the next steps to distributing the questionnaire.
> 
> Regards,
> Femi
> 
> 
>> On 1 May 2019, at 15:15, Toerless Eckert <tte@cs.fau.de> wrote:
>> 
>> Ok, thats the classical excuse until we get rid of DST i guess ;-) I 
>> was only 15 minutes late, so i have no real excuse.... ;-)
>> 
>> On Wed, May 01, 2019 at 07:35:08PM +0530, Anish Peter wrote:
>>> Very sorry, I happened to join this meeting 1hr late.
>>> 
>>> On Tue, Apr 30, 2019 at 6:48 PM Mankamana Mishra (mankamis) < 
>>> mankamis@cisco.com> wrote:
>>> 
>>>> Sure .
>>>> 
>>>> Sent from my iPhone
>>>> 
>>>>> On Apr 30, 2019, at 03:01, Olufemi Komolafe <femi=
>>>> 40arista.com@dmarc.ietf.org> wrote:
>>>>> 
>>>>> I feel we are losing some momentum with this effort and so I think
>>>> tomorrow when we meet it???d be really good to identify exactly 
>>>> what remains to be done and set some milestones and deadlines.  
>>>> Does that seem reasonable?
>>>>> 
>>>>> Regards,
>>>>> Femi
>>>>> --
>>>>> 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