
From nobody Wed Jul 19 09:51:06 2017
Return-Path: <swmike@swm.pp.se>
X-Original-To: mcast-wifi@ietfa.amsl.com
Delivered-To: mcast-wifi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7CD7C13167D for <mcast-wifi@ietfa.amsl.com>; Wed, 19 Jul 2017 09:51:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.301
X-Spam-Level: 
X-Spam-Status: No, score=-4.301 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, RP_MATCHES_RCVD=-0.001, 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=swm.pp.se
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 9zKmafkDLTZQ for <mcast-wifi@ietfa.amsl.com>; Wed, 19 Jul 2017 09:51:01 -0700 (PDT)
Received: from uplift.swm.pp.se (swm.pp.se [212.247.200.143]) (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 4306612EC3F for <mcast-wifi@ietf.org>; Wed, 19 Jul 2017 09:51:01 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id C272EA2; Wed, 19 Jul 2017 18:50:58 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1500483058; bh=pQsc0NVNXEylzwHuWZ5HFnFYKYYh6m+H82+nDyzy914=; h=Date:From:To:Subject:From; b=o4F3d5Oe+5yk47z4kXE9QmxiiieT++v/eDNmjTcgY4FZyfwAxcDEwBPsfrVJQkIvf +lA3Qu2Ddxuac3ReFaXTxxmmRhB+UP27Aa04bLVDU9U3HQzeunEqesC4zMztIJBKms OiQRIONR7nkQfO27sXWf1s8/As1kagOXynYIiSCo=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id AB1A1A1 for <mcast-wifi@ietf.org>; Wed, 19 Jul 2017 18:50:58 +0200 (CEST)
Date: Wed, 19 Jul 2017 18:50:58 +0200 (CEST)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: mcast-wifi@ietf.org
Message-ID: <alpine.DEB.2.02.1707191842270.29742@uplift.swm.pp.se>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII; FORMAT=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/mcast-wifi/muf8GqcTRzQubgHI-uc90aIC2YY>
Subject: Re: [Mcast-wifi] Multicast and Wireless (fwd)
X-BeenThere: mcast-wifi@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Discussions related to issues with multicast in 802.11 Wi-Fi networks & solutions/optimizations targeted at resolving these issues." <mcast-wifi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mcast-wifi>, <mailto:mcast-wifi-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mcast-wifi/>
List-Post: <mailto:mcast-wifi@ietf.org>
List-Help: <mailto:mcast-wifi-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mcast-wifi>, <mailto:mcast-wifi-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Jul 2017 16:51:04 -0000

Hi,

Below is an email I wrote to the approximately 10 people who were 
"gathered" to discuss how to proceed with the wifi-multicast "problem".

In the meeting, there were lots of discussions, some regarding catching up 
with what had been discussed before, but the last 30 minutes (in my 
opinion) were productive. There were solutions proposed, and I'd like to 
get shared here in writing. Please invite more interested people and make 
them aware of this list, and let's do the discussions here. I will do some 
announcements on other lists to bring awareness to this list.

One proposal was that we could make sure 
http://www.ieee802.org/1/pages/802.1ak.html was available in end systems, 
and this could be adapted by 802.11 as one way to help the APs handle 
multicast load by letting them more easily identify how to turn multicast 
packets into unicast packets.

Another proposal was to just do less multicast by redesigning IETF 
protocols and how they behave.

WHen we're saying multicast here, we're talking L1/L2 multicast, ie 
sending multicast/broadcast packets over wifi between devices connected to 
the same L2 domain. This can be IPv6 ND/RA packets, but also service 
discover such as Bonjour packets.

I would like to have the people who proposed the solutions to elaborate on 
what their thinking was.

----

Hi,

there is nothing concrete being proposed as far as I know. Alia indicated to me 
she was still looking for a problem statement.

The problem statement I was involved in writing 2 years ago:

https://www.iab.org/wp-content/IAB-uploads/2013/01/multicast-problem-statement.pptx

https://www.ietf.org/mail-archive/web/int-area/current/msg04903.html

https://www.ietf.org/proceedings/94/slides/slides-94-intarea-1.pdf
At the end there are multiple links to problem statements etc.

>From what I can tell, there is a problem. It's unclear what should be done 
about it, if this is a IEEE problem to make sure wifi works well with 
multicast, or if IETF should adapt its protocols to handle the way IEEE does 
multicast over 802.11 without the special mechanisms for improved multicast 
reliability that isn't widely implemented in currently shipping devices.

So I guess this is what we're supposed to consider.


From nobody Wed Jul 19 10:13:00 2017
Return-Path: <pthubert@cisco.com>
X-Original-To: mcast-wifi@ietfa.amsl.com
Delivered-To: mcast-wifi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 46E3312EC3F for <mcast-wifi@ietfa.amsl.com>; Wed, 19 Jul 2017 10:12:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.522
X-Spam-Level: 
X-Spam-Status: No, score=-14.522 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 FeO6nsg7msGC for <mcast-wifi@ietfa.amsl.com>; Wed, 19 Jul 2017 10:12:57 -0700 (PDT)
Received: from alln-iport-7.cisco.com (alln-iport-7.cisco.com [173.37.142.94]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9C3311270AC for <mcast-wifi@ietf.org>; Wed, 19 Jul 2017 10:12:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=11731; q=dns/txt; s=iport; t=1500484377; x=1501693977; h=from:to:subject:date:message-id:mime-version; bh=bEY7B/NTAQnpIdfCait+FSNdIQpFSYDSFEBwjuKjf/s=; b=kwKE0UcgjZXTIyHyiU5x8o/DtZ9clNVUmAYatITWsod/++5YKtSTq/6J 4vgDE6PFZPm+bfsBZ49Ct8dW7JDn2KB/D4HA6PB9ls0TIMTmLqfzZIefv zLjZ/savTl3gGkTWSZxwODJZGMdjBpGu+NqLx/Palc7pCBMFvjRwOij88 g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DKAQCakm9Z/5xdJa1bHAEBBAEBCgEBg?= =?us-ascii?q?m9rZIEbjgSiOYUsghGJKz8YAQIBAQEBAQEBax0LhUxeAYEAHwcBBBsTiTBkt0m?= =?us-ascii?q?LHAEBAQEGAQEBASSDKINNiUyGFwWHI4IzhwGBYI0CAo5chTKSOZVbAR84gQp1F?= =?us-ascii?q?Ydfh1iBMYENAQEB?=
X-IronPort-AV: E=Sophos;i="5.40,381,1496102400";  d="scan'208,217";a="458099135"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by alln-iport-7.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 19 Jul 2017 17:12:56 +0000
Received: from XCH-RCD-002.cisco.com (xch-rcd-002.cisco.com [173.37.102.12]) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id v6JHCuup030319 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL) for <mcast-wifi@ietf.org>; Wed, 19 Jul 2017 17:12:56 GMT
Received: from xch-rcd-001.cisco.com (173.37.102.11) by XCH-RCD-002.cisco.com (173.37.102.12) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Wed, 19 Jul 2017 12:12:55 -0500
Received: from xch-rcd-001.cisco.com ([173.37.102.11]) by XCH-RCD-001.cisco.com ([173.37.102.11]) with mapi id 15.00.1210.000; Wed, 19 Jul 2017 12:12:55 -0500
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: "mcast-wifi@ietf.org" <mcast-wifi@ietf.org>
Thread-Topic: my take from the meeting
Thread-Index: AdMArJqlUHXnSAniQL+e61nSsC7DQg==
Date: Wed, 19 Jul 2017 17:12:43 +0000
Deferred-Delivery: Wed, 19 Jul 2017 17:11:57 +0000
Message-ID: <2b5f3ef210b84feaae3adcbed8e053fb@XCH-RCD-001.cisco.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.61.230.140]
Content-Type: multipart/alternative; boundary="_000_2b5f3ef210b84feaae3adcbed8e053fbXCHRCD001ciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/mcast-wifi/gSXjXCqT26RW71c8fY4FTyLdXMc>
Subject: [Mcast-wifi] my take from the meeting
X-BeenThere: mcast-wifi@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Discussions related to issues with multicast in 802.11 Wi-Fi networks & solutions/optimizations targeted at resolving these issues." <mcast-wifi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mcast-wifi>, <mailto:mcast-wifi-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mcast-wifi/>
List-Post: <mailto:mcast-wifi@ietf.org>
List-Help: <mailto:mcast-wifi-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mcast-wifi>, <mailto:mcast-wifi-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Jul 2017 17:12:59 -0000

--_000_2b5f3ef210b84feaae3adcbed8e053fbXCHRCD001ciscocom_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Dear all :

For a lot of the meeting time, we discussed a lot on our views of what the =
problem is, and I'm not reporting on that. At least we agreed that the disc=
ussion is NOT IPv4 vs. IPv6, and that we do not expect to see wireless broa=
dcast become cheap and reliable, so we seemed to have consensus that the IE=
TF should contribute to solving the problems that our protocols are experie=
ncing.

I noted that we discussed 2 main directions that we should take in the futu=
re:


-         On the one hand, IETF should protect its future and work on reduc=
ing the amount of multicast that we are using in our protocols, for protoco=
ls that we already have and for the ones we are designing now. Reducing usa=
ge of multicast will improve the operation on all networks, in particular w=
hen the multicast groups are large (Lorenzo); at some point even Ethernet f=
abrics end up suffering from excess of broadcast and that has consequences =
such as to limit the size of subnets (Pascal). A more immediate attention c=
ould be given to protocols that are either very chatty or for which reliabl=
e delivery of multicast is critical to the protocol operation. Work is alre=
ady taking place in DNS SD (Stuart) and IPv6 ND (Pascal).

-

-         On the other end, a reliable registration to Layer-2 multicast gr=
oups and a reliable mcast operation at Layer-2 would provide a generic solu=
tion to many problems (Lorenzo). Current IGMP / MLD snooping is broken (Pas=
cal). There is no need to support 2^24 groups to get solicited node mcast w=
orking: it is possible just select a number <<24 of trailing bits that make=
 sense for a given network size to limit the amount of false positive (unwa=
nted deliveries) to reasonable levels (Pascal). IEEE 802.1 has worked on th=
e L2 multicast years ago (Stig). The initial protocol was broken and fixes =
where provided; with the current status of the IEEE work (paperwork?) and t=
he lack of implementation (is there any?), this work may not have the requi=
red maturity yet (Pascal, based on a visit to IEEE802.1). We are unsure of =
what the state is at IEEE for all these topics and would appreciate a statu=
s (Dorothy proposes a name but I failed to remember it). Nevertheless, we n=
eed to encourage IEEE 802.1 and 802.11 to reopen L2 multicast, we need to g=
et vendors attention on the functionality and get it working and implemente=
d on wires and wireless. In particular, we remarked that Wi-Fi provides a b=
roadcast service, not a multicast one (Lorenzo). In fact all frames are bro=
adcast at the PHY level unless we beamform (Pascal) but what comes with uni=
cast is the property of being much faster (2 orders of magnitude) and much =
more reliable (L2 ARQ); multicast to few nodes should certainly be served a=
s multiple unicast.

-


Is this a fair report?

--_000_2b5f3ef210b84feaae3adcbed8e053fbXCHRCD001ciscocom_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0cm;
	margin-right:0cm;
	margin-bottom:0cm;
	margin-left:36.0pt;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri",sans-serif;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:755859079;
	mso-list-type:hybrid;
	mso-list-template-ids:-1296512742 1361865788 67698691 67698693 67698689 67=
698691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-start-at:0;
	mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Calibri",sans-serif;
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Courier New";}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Symbol;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Courier New";}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Symbol;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Courier New";}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span lang=3D"FR">Dear all&nbsp;:<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal"><span lang=3D"FR"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal">For a lot of the meeting time, we discussed a lot on=
 our views of what the problem is, and I&#8217;m not reporting on that. At =
least we agreed that the discussion is NOT IPv4 vs. IPv6, and that we do no=
t expect to see wireless broadcast become
 cheap and reliable, so we seemed to have consensus that the IETF should co=
ntribute to solving the problems that our protocols are experiencing.<o:p><=
/o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">I noted that we discussed 2 main directions that we =
should take in the future:<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-18.0pt;mso-list:l0 leve=
l1 lfo1"><![if !supportLists]><span style=3D"mso-list:Ignore">-<span style=
=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;
</span></span><![endif]>On the one hand, IETF should protect its future and=
 work on reducing the amount of multicast that we are using in our protocol=
s, for protocols that we already have and for the ones we are designing now=
. Reducing usage of multicast will
 improve the operation on all networks, in particular when the multicast gr=
oups are large (Lorenzo); at some point even Ethernet fabrics end up suffer=
ing from excess of broadcast and that has consequences such as to limit the=
 size of subnets (Pascal). A more
 immediate attention could be given to protocols that are either very chatt=
y or for which reliable delivery of multicast is critical to the protocol o=
peration. Work is already taking place in DNS SD (Stuart) and IPv6 ND (Pasc=
al).
<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-18.0pt;mso-list:l0 leve=
l1 lfo1"><![if !supportLists]><span style=3D"mso-list:Ignore">-<span style=
=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;
</span></span><![endif]><o:p>&nbsp;</o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-18.0pt;mso-list:l0 leve=
l1 lfo1"><![if !supportLists]><span style=3D"mso-list:Ignore">-<span style=
=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;
</span></span><![endif]>On the other end, a reliable registration to Layer-=
2 multicast groups and a reliable mcast operation at Layer-2 would provide =
a generic solution to many problems (Lorenzo). Current IGMP / MLD snooping =
is broken (Pascal). There is no
 need to support 2^24 groups to get solicited node mcast working: it is pos=
sible just select a number &lt;&lt;24 of trailing bits that make sense for =
a given network size to limit the amount of false positive (unwanted delive=
ries) to reasonable levels (Pascal). IEEE
 802.1 has worked on the L2 multicast years ago (Stig). The initial protoco=
l was broken and fixes where provided; with the current status of the IEEE =
work (paperwork?) and the lack of implementation (is there any?), this work=
 may not have the required maturity
 yet (Pascal, based on a visit to IEEE802.1). We are unsure of what the sta=
te is at IEEE for all these topics and would appreciate a status (Dorothy p=
roposes a name but I failed to remember it). Nevertheless, we need to encou=
rage IEEE 802.1 and 802.11 to reopen
 L2 multicast, we need to get vendors attention on the functionality and ge=
t it working and implemented on wires and wireless. In particular, we remar=
ked that Wi-Fi provides a broadcast service, not a multicast one (Lorenzo).=
 In fact all frames are broadcast
 at the PHY level unless we beamform (Pascal) but what comes with unicast i=
s the property of being much faster (2 orders of magnitude) and much more r=
eliable (L2 ARQ); multicast to few nodes should certainly be served as mult=
iple unicast.<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-18.0pt;mso-list:l0 leve=
l1 lfo1"><![if !supportLists]><span style=3D"mso-list:Ignore">-<span style=
=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;
</span></span><![endif]><o:p>&nbsp;</o:p></p>
<p class=3D"MsoListParagraph"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Is this a fair report?<o:p></o:p></p>
</div>
</body>
</html>

--_000_2b5f3ef210b84feaae3adcbed8e053fbXCHRCD001ciscocom_--


From nobody Wed Jul 19 10:41:28 2017
Return-Path: <mark.hamilton2152@gmail.com>
X-Original-To: mcast-wifi@ietfa.amsl.com
Delivered-To: mcast-wifi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7CC4B13167D for <mcast-wifi@ietfa.amsl.com>; Wed, 19 Jul 2017 10:41:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.738
X-Spam-Level: 
X-Spam-Status: No, score=-1.738 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 XWg5AQ2Ph5rN for <mcast-wifi@ietfa.amsl.com>; Wed, 19 Jul 2017 10:41:25 -0700 (PDT)
Received: from mail-io0-x243.google.com (mail-io0-x243.google.com [IPv6:2607:f8b0:4001:c06::243]) (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 DB09512EBF4 for <mcast-wifi@ietf.org>; Wed, 19 Jul 2017 10:41:24 -0700 (PDT)
Received: by mail-io0-x243.google.com with SMTP id l7so415983iof.5 for <mcast-wifi@ietf.org>; Wed, 19 Jul 2017 10:41:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:thread-index:content-language; bh=4XCWNq+IJ6Ho5bYC7qOw/bFYcj+wJ9Hj0zpC8ZcDgig=; b=tZBmYtfT35aHdUrht0Aq5/joqVS81m3TJsZz3AucYtHHsU0AtlfsrggSW+K0BjYm7z NyMpyYtgGjee0GgbikwdYFU6R7uXN8HcfoN1dcZgqgEjcmk5ssF5Twrnr4ssn9G66/+O oDaORPdhqMmlFPnnlmIh/OhX2FxdcvDvtjGvJhqeYveeaplTLXPr6zv1GeWGlHtRXwAs f8N9ijEGyuDZuoC7sor6YutegMptUkhbf4Byq/l98G6WRguRHI98qrsLy6XoZ9c+gnir oC+QfsRhpH8iC4gQ9a4tG95yju9edtay4utYeGD2r/KdUcEe/uqsRzkskTTKgs+d25ug OlTA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:references:in-reply-to:subject:date :message-id:mime-version:thread-index:content-language; bh=4XCWNq+IJ6Ho5bYC7qOw/bFYcj+wJ9Hj0zpC8ZcDgig=; b=g3I6b5DYZfiz658KBD5buvmRxs7R1Pwx3La4acEj5AOrtiJXskpwx/e2BPqHYBkgK7 CjK1vrKG7jV3AiniWSKlvBvMT5fXqLDfx8WHPSSIfItl/R3VZW9kl5ue+yqDqiIanvRU fLBxChH4EXtRkLgXXVjS4KQC6RJpQeADxIZ7cOza8TZvQ5OwVzAm1SVR4vG1JFyot4/E TV8FgrWta07qKoAab0SmqmRAKpIzWVLPQV6l7VebdT5V/uU4o8bhb3e6GAsb9XLoC54x ArPg4dsh+3DFgKMhUHERWFJ3OHFhpLBzDw0oxsxOW5a5F3SoWjWLfSYpxmPK/REcZGd5 KFog==
X-Gm-Message-State: AIVw110+3Y+QMEzLjljVt5gfCNQtsItio3OxVRBe/RKv9pYp4OCxP1lp m6BuB87QEKkfhg==
X-Received: by 10.107.157.9 with SMTP id g9mr1039366ioe.46.1500486084200; Wed, 19 Jul 2017 10:41:24 -0700 (PDT)
Received: from MarkPC ([144.49.197.22]) by smtp.gmail.com with ESMTPSA id o17sm282290ioe.1.2017.07.19.10.41.22 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 19 Jul 2017 10:41:23 -0700 (PDT)
From: "Mark Hamilton" <mark.hamilton2152@gmail.com>
To: "'Mikael Abrahamsson'" <swmike@swm.pp.se>, <mcast-wifi@ietf.org>
Cc: "'Donald Eastlake'" <d3e3e3@gmail.com>
References: <alpine.DEB.2.02.1707191842270.29742@uplift.swm.pp.se>
In-Reply-To: <alpine.DEB.2.02.1707191842270.29742@uplift.swm.pp.se>
Date: Wed, 19 Jul 2017 11:41:17 -0600
Message-ID: <00ef01d300b6$3b9dc6c0$b2d95440$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_00F0_01D30083.F106B220"
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQJVV+Ij3AEer2MTFLPMSOS5lRe/qqFWtMKw
Content-Language: en-us
Archived-At: <https://mailarchive.ietf.org/arch/msg/mcast-wifi/zeZcIOnwvWdOY2wa-Xq2vbvvhIw>
Subject: Re: [Mcast-wifi] Multicast and Wireless (fwd)
X-BeenThere: mcast-wifi@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Discussions related to issues with multicast in 802.11 Wi-Fi networks & solutions/optimizations targeted at resolving these issues." <mcast-wifi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mcast-wifi>, <mailto:mcast-wifi-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mcast-wifi/>
List-Post: <mailto:mcast-wifi@ietf.org>
List-Help: <mailto:mcast-wifi-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mcast-wifi>, <mailto:mcast-wifi-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Jul 2017 17:41:26 -0000

This is a multipart message in MIME format.

------=_NextPart_000_00F0_01D30083.F106B220
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Thanks for the update, and prod, Mikael.  One clarification, and one
question/remark:

 

802.1ak has been pulled into 802.1Q as of 802.1Q-2011.  So just for clarity,
I think we're talking about 802.1Q-2014 [
http://www.ieee802.org/1/pages/802.1Q-2014.html ] (I assume we should
reference the latest), and its specification of MRP (clause 10, and
related).

 

The question/remark: I apologize that I'm not up-to-speed on the discussions
during this gathering.  But, I am concerned with a consideration that 802.11
could somehow use MRP to help with this.  Typically, 802.11 is limited in
scope to being a "MAC/PHY stack" under (within?) a Bridge Port, and it is
does not understand or directly interact with any of the Bridging protocols
flowing over its links.  There is a project underway in 802.11 (802.11ak)
which will catch up 802.11 to the latest 802.1 specs for such links
(802.1AC, etc.), but I don't believe that will add sufficient understanding
of Bridging protocols to provide direct information from MRP, either.  Is
the suggestion that 802.11 be further enhanced to be able to participate in
MRP?  Or, is there confusion about 802.11 acting like a Bridge (and an
assumption that it would therefore participate in MRP, etc.), which is a
common issue?

 

Mark

 

-----Original Message-----
From: Mcast-wifi [mailto:mcast-wifi-bounces@ietf.org] On Behalf Of Mikael
Abrahamsson
Sent: Wednesday, July 19, 2017 10:51 AM
To: mcast-wifi@ietf.org
Subject: Re: [Mcast-wifi] Multicast and Wireless (fwd)

 

 

Hi,

 

Below is an email I wrote to the approximately 10 people who were "gathered"
to discuss how to proceed with the wifi-multicast "problem".

 

In the meeting, there were lots of discussions, some regarding catching up
with what had been discussed before, but the last 30 minutes (in my

opinion) were productive. There were solutions proposed, and I'd like to get
shared here in writing. Please invite more interested people and make them
aware of this list, and let's do the discussions here. I will do some
announcements on other lists to bring awareness to this list.

 

One proposal was that we could make sure
<http://www.ieee802.org/1/pages/802.1ak.html>
http://www.ieee802.org/1/pages/802.1ak.html was available in end systems,
and this could be adapted by 802.11 as one way to help the APs handle
multicast load by letting them more easily identify how to turn multicast
packets into unicast packets.

 

Another proposal was to just do less multicast by redesigning IETF protocols
and how they behave.

 

WHen we're saying multicast here, we're talking L1/L2 multicast, ie sending
multicast/broadcast packets over wifi between devices connected to the same
L2 domain. This can be IPv6 ND/RA packets, but also service discover such as
Bonjour packets.

 

I would like to have the people who proposed the solutions to elaborate on
what their thinking was.

 

----

 

Hi,

 

there is nothing concrete being proposed as far as I know. Alia indicated to
me she was still looking for a problem statement.

 

The problem statement I was involved in writing 2 years ago:

 

 
<https://www.iab.org/wp-content/IAB-uploads/2013/01/multicast-problem-statem
ent.pptx>
https://www.iab.org/wp-content/IAB-uploads/2013/01/multicast-problem-stateme
nt.pptx

 

 <https://www.ietf.org/mail-archive/web/int-area/current/msg04903.html>
https://www.ietf.org/mail-archive/web/int-area/current/msg04903.html

 

 <https://www.ietf.org/proceedings/94/slides/slides-94-intarea-1.pdf>
https://www.ietf.org/proceedings/94/slides/slides-94-intarea-1.pdf

At the end there are multiple links to problem statements etc.

 

>From what I can tell, there is a problem. It's unclear what should be 

>done

about it, if this is a IEEE problem to make sure wifi works well with
multicast, or if IETF should adapt its protocols to handle the way IEEE does
multicast over 802.11 without the special mechanisms for improved multicast
reliability that isn't widely implemented in currently shipping devices.

 

So I guess this is what we're supposed to consider.

 

_______________________________________________

Mcast-wifi mailing list

 <mailto:Mcast-wifi@ietf.org> Mcast-wifi@ietf.org

 <https://www.ietf.org/mailman/listinfo/mcast-wifi>
https://www.ietf.org/mailman/listinfo/mcast-wifi


------=_NextPart_000_00F0_01D30083.F106B220
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 15 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:"Calibri",sans-serif;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri",sans-serif;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US =
link=3D"#0563C1" vlink=3D"#954F72"><div class=3DWordSection1><p =
class=3DMsoPlainText>Thanks for the update, and prod, Mikael.&nbsp; One =
clarification, and one question/remark:<o:p></o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>802.1ak has been pulled into 802.1Q as of =
802.1Q-2011.&nbsp; So just for clarity, I think we're talking about =
802.1Q-2014 [ <a =
href=3D"http://www.ieee802.org/1/pages/802.1Q-2014.html">http://www.ieee8=
02.org/1/pages/802.1Q-2014.html</a> ] (I assume we should reference the =
latest), and its specification of MRP (clause 10, and =
related).<o:p></o:p></p><p class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>The question/remark: I apologize that I&#8217;m not =
up-to-speed on the discussions during this gathering.&nbsp; But, I am =
concerned with a consideration that 802.11 could somehow use MRP to help =
with this.&nbsp; Typically, 802.11 is limited in scope to being a =
&#8220;MAC/PHY stack&#8221; under (within?) a Bridge Port, and it is =
does not understand or directly interact with any of the Bridging =
protocols flowing over its links.&nbsp; There is a project underway in =
802.11 (802.11ak) which will catch up 802.11 to the latest 802.1 specs =
for such links (802.1AC, etc.), but I don&#8217;t believe that will add =
sufficient understanding of Bridging protocols to provide direct =
information from MRP, either.&nbsp; Is the suggestion that 802.11 be =
further enhanced to be able to participate in MRP?&nbsp; Or, is there =
confusion about 802.11 acting like a Bridge (and an assumption that it =
would therefore participate in MRP, etc.), which is a common =
issue?<o:p></o:p></p><p class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>Mark<o:p></o:p></p><p class=3DMsoPlainText><a =
name=3D"_MailEndCompose"><o:p>&nbsp;</o:p></a></p><span =
style=3D'mso-bookmark:_MailEndCompose'></span><p =
class=3DMsoPlainText>-----Original Message-----<br>From: Mcast-wifi =
[mailto:mcast-wifi-bounces@ietf.org] On Behalf Of Mikael =
Abrahamsson<br>Sent: Wednesday, July 19, 2017 10:51 AM<br>To: =
mcast-wifi@ietf.org<br>Subject: Re: [Mcast-wifi] Multicast and Wireless =
(fwd)</p><p class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>Hi,<o:p></o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p class=3DMsoPlainText>Below =
is an email I wrote to the approximately 10 people who were =
&quot;gathered&quot; to discuss how to proceed with the wifi-multicast =
&quot;problem&quot;.<o:p></o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p class=3DMsoPlainText>In the =
meeting, there were lots of discussions, some regarding catching up with =
what had been discussed before, but the last 30 minutes (in =
my<o:p></o:p></p><p class=3DMsoPlainText>opinion) were productive. There =
were solutions proposed, and I'd like to get shared here in writing. =
Please invite more interested people and make them aware of this list, =
and let's do the discussions here. I will do some announcements on other =
lists to bring awareness to this list.<o:p></o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p class=3DMsoPlainText>One =
proposal was that we could make sure <a =
href=3D"http://www.ieee802.org/1/pages/802.1ak.html"><span =
style=3D'color:windowtext;text-decoration:none'>http://www.ieee802.org/1/=
pages/802.1ak.html</span></a> was available in end systems, and this =
could be adapted by 802.11 as one way to help the APs handle multicast =
load by letting them more easily identify how to turn multicast packets =
into unicast packets.<o:p></o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>Another proposal was to just do less multicast by =
redesigning IETF protocols and how they behave.<o:p></o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p class=3DMsoPlainText>WHen =
we're saying multicast here, we're talking L1/L2 multicast, ie sending =
multicast/broadcast packets over wifi between devices connected to the =
same L2 domain. This can be IPv6 ND/RA packets, but also service =
discover such as Bonjour packets.<o:p></o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p class=3DMsoPlainText>I =
would like to have the people who proposed the solutions to elaborate on =
what their thinking was.<o:p></o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>----<o:p></o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>Hi,<o:p></o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p class=3DMsoPlainText>there =
is nothing concrete being proposed as far as I know. Alia indicated to =
me she was still looking for a problem statement.<o:p></o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p class=3DMsoPlainText>The =
problem statement I was involved in writing 2 years =
ago:<o:p></o:p></p><p class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText><a =
href=3D"https://www.iab.org/wp-content/IAB-uploads/2013/01/multicast-prob=
lem-statement.pptx"><span =
style=3D'color:windowtext;text-decoration:none'>https://www.iab.org/wp-co=
ntent/IAB-uploads/2013/01/multicast-problem-statement.pptx</span></a><o:p=
></o:p></p><p class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText><a =
href=3D"https://www.ietf.org/mail-archive/web/int-area/current/msg04903.h=
tml"><span =
style=3D'color:windowtext;text-decoration:none'>https://www.ietf.org/mail=
-archive/web/int-area/current/msg04903.html</span></a><o:p></o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p class=3DMsoPlainText><a =
href=3D"https://www.ietf.org/proceedings/94/slides/slides-94-intarea-1.pd=
f"><span =
style=3D'color:windowtext;text-decoration:none'>https://www.ietf.org/proc=
eedings/94/slides/slides-94-intarea-1.pdf</span></a><o:p></o:p></p><p =
class=3DMsoPlainText>At the end there are multiple links to problem =
statements etc.<o:p></o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;From what I can tell, there is a problem. It's =
unclear what should be <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;done<o:p></o:p></p><p =
class=3DMsoPlainText>about it, if this is a IEEE problem to make sure =
wifi works well with multicast, or if IETF should adapt its protocols to =
handle the way IEEE does multicast over 802.11 without the special =
mechanisms for improved multicast reliability that isn't widely =
implemented in currently shipping devices.<o:p></o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p class=3DMsoPlainText>So I =
guess this is what we're supposed to consider.<o:p></o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>_______________________________________________<o:p>=
</o:p></p><p class=3DMsoPlainText>Mcast-wifi mailing =
list<o:p></o:p></p><p class=3DMsoPlainText><a =
href=3D"mailto:Mcast-wifi@ietf.org"><span =
style=3D'color:windowtext;text-decoration:none'>Mcast-wifi@ietf.org</span=
></a><o:p></o:p></p><p class=3DMsoPlainText><a =
href=3D"https://www.ietf.org/mailman/listinfo/mcast-wifi"><span =
style=3D'color:windowtext;text-decoration:none'>https://www.ietf.org/mail=
man/listinfo/mcast-wifi</span></a><o:p></o:p></p></div></body></html>
------=_NextPart_000_00F0_01D30083.F106B220--


From nobody Wed Jul 19 16:14:59 2017
Return-Path: <charliep@computer.org>
X-Original-To: mcast-wifi@ietfa.amsl.com
Delivered-To: mcast-wifi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7D613131BCF for <mcast-wifi@ietfa.amsl.com>; Wed, 19 Jul 2017 16:14:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.953
X-Spam-Level: 
X-Spam-Status: No, score=-1.953 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
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 11YwjyZ98pfv for <mcast-wifi@ietfa.amsl.com>; Wed, 19 Jul 2017 16:14:55 -0700 (PDT)
Received: from elasmtp-mealy.atl.sa.earthlink.net (elasmtp-mealy.atl.sa.earthlink.net [209.86.89.69]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A33A4126CD6 for <mcast-wifi@ietf.org>; Wed, 19 Jul 2017 16:14:55 -0700 (PDT)
Received: from [31.133.157.127] by elasmtp-mealy.atl.sa.earthlink.net with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.67) (envelope-from <charliep@computer.org>) id 1dXyBC-000Eqm-7G for mcast-wifi@ietf.org; Wed, 19 Jul 2017 19:14:54 -0400
References: <150050561543.24146.13881541422679319061.idtracker@ietfa.amsl.com>
To: mcast-wifi@ietf.org
From: Charlie Perkins <charliep@computer.org>
Organization: Blue Sky Meadows
X-Forwarded-Message-Id: <150050561543.24146.13881541422679319061.idtracker@ietfa.amsl.com>
Message-ID: <6065704e-7f4a-de33-f6fd-643b1fa2139f@computer.org>
Date: Wed, 19 Jul 2017 16:14:51 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <150050561543.24146.13881541422679319061.idtracker@ietfa.amsl.com>
Content-Type: multipart/alternative; boundary="------------150D5F81DA7A0082095F5B38"
Content-Language: en-US
X-ELNK-Trace: 137d7d78656ed6919973fd6a8f21c4f2d780f4a490ca6956846b590522b13c95820ea9e9a79f51dc5e07287e8405d30a350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 31.133.157.127
Archived-At: <https://mailarchive.ietf.org/arch/msg/mcast-wifi/-uFosfJtMP6gIz6ZAIgF-E0lqYQ>
Subject: [Mcast-wifi] Fwd: New Version Notification for draft-perkins-intarea-multicast-ieee802-03.txt
X-BeenThere: mcast-wifi@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Discussions related to issues with multicast in 802.11 Wi-Fi networks & solutions/optimizations targeted at resolving these issues." <mcast-wifi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mcast-wifi>, <mailto:mcast-wifi-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mcast-wifi/>
List-Post: <mailto:mcast-wifi@ietf.org>
List-Help: <mailto:mcast-wifi-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mcast-wifi>, <mailto:mcast-wifi-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Jul 2017 23:14:57 -0000

This is a multi-part message in MIME format.
--------------150D5F81DA7A0082095F5B38
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

Hello folks,

Please check the updated draft that I have just posted.  It is 
incomplete but I think has the basic organization and topics that would 
be very helpful in this discussion.  If anyone wants to contribute text 
to fill in the holes in this draft that would be very much appreciated.  
Or, if the basic organization could be improved, please don't hesitate 
to suggest changes.  I believe this draft starts to answer many of the 
needs that were expressed during our discussion Wednesday afternoon.

Regards,
Charlie P.



-------- Forwarded Message --------
Subject: 	New Version Notification for 
draft-perkins-intarea-multicast-ieee802-03.txt
Date: 	Wed, 19 Jul 2017 16:06:55 -0700
From: 	internet-drafts@ietf.org
To: 	Charles Perkins <charliep@computer.org>, Warren Kumari 
<warren@kumari.net>, Juan Carlos Zuniga <j.c.zuniga@ieee.org>, Dorothy 
Stanley <dstanley@arubanetworks.com>, Charles E. Perkins 
<charliep@computer.org>, Juan Zuniga <j.c.zuniga@ieee.org>



A new version of I-D, draft-perkins-intarea-multicast-ieee802-03.txt
has been successfully submitted by Charles E. Perkins and posted to the
IETF repository.

Name:		draft-perkins-intarea-multicast-ieee802
Revision:	03
Title:		Multicast Considerations over IEEE 802 Wireless Media
Document date:	2017-07-19
Group:		Individual Submission
Pages:		17
URL:            https://www.ietf.org/internet-drafts/draft-perkins-intarea-multicast-ieee802-03.txt
Status:         https://datatracker.ietf.org/doc/draft-perkins-intarea-multicast-ieee802/
Htmlized:       https://tools.ietf.org/html/draft-perkins-intarea-multicast-ieee802-03
Htmlized:       https://datatracker.ietf.org/doc/html/draft-perkins-intarea-multicast-ieee802-03
Diff:           https://www.ietf.org/rfcdiff?url2=draft-perkins-intarea-multicast-ieee802-03

Abstract:
    Performance issues have been observed when multicast packet
    transmissions of IETF protocols are used over IEEE 802 wireless
    media.  Even though enhamcements for multicast transmissions have
    been designed at both IETF and IEEE 802, there seems to exist a
    disconnect between specifications, implementations and configuration
    choices.  This draft describes the different issues that have been
    observed, the multicast enhancement features that have been specified
    at IETF and IEEE 802 for wireless media, as well as the operational
    chioces that can be taken to improve the performace of the network.
    Finally, it provides some recommendations about the usage and
    combination of these features and operational choices.

                                                                                   


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat



--------------150D5F81DA7A0082095F5B38
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <p>Hello folks,</p>
    <p>Please check the updated draft that I have just posted.  It is
      incomplete but I think has the basic organization and topics that
      would be very helpful in this discussion.  If anyone wants to
      contribute text to fill in the holes in this draft that would be
      very much appreciated.  Or, if the basic organization could be
      improved, please don't hesitate to suggest changes.  I believe
      this draft starts to answer many of the needs that were expressed
      during our discussion Wednesday afternoon.<br>
    </p>
    <p>Regards,<br>
      Charlie P.<br>
    </p>
    <div class="moz-forward-container"><br>
      <br>
      -------- Forwarded Message --------
      <table class="moz-email-headers-table" cellspacing="0"
        cellpadding="0" border="0">
        <tbody>
          <tr>
            <th nowrap="nowrap" valign="BASELINE" align="RIGHT">Subject:
            </th>
            <td>New Version Notification for
              draft-perkins-intarea-multicast-ieee802-03.txt</td>
          </tr>
          <tr>
            <th nowrap="nowrap" valign="BASELINE" align="RIGHT">Date: </th>
            <td>Wed, 19 Jul 2017 16:06:55 -0700</td>
          </tr>
          <tr>
            <th nowrap="nowrap" valign="BASELINE" align="RIGHT">From: </th>
            <td><a class="moz-txt-link-abbreviated" href="mailto:internet-drafts@ietf.org">internet-drafts@ietf.org</a></td>
          </tr>
          <tr>
            <th nowrap="nowrap" valign="BASELINE" align="RIGHT">To: </th>
            <td>Charles Perkins <a class="moz-txt-link-rfc2396E" href="mailto:charliep@computer.org">&lt;charliep@computer.org&gt;</a>, Warren
              Kumari <a class="moz-txt-link-rfc2396E" href="mailto:warren@kumari.net">&lt;warren@kumari.net&gt;</a>, Juan Carlos Zuniga
              <a class="moz-txt-link-rfc2396E" href="mailto:j.c.zuniga@ieee.org">&lt;j.c.zuniga@ieee.org&gt;</a>, Dorothy Stanley
              <a class="moz-txt-link-rfc2396E" href="mailto:dstanley@arubanetworks.com">&lt;dstanley@arubanetworks.com&gt;</a>, Charles E. Perkins
              <a class="moz-txt-link-rfc2396E" href="mailto:charliep@computer.org">&lt;charliep@computer.org&gt;</a>, Juan Zuniga
              <a class="moz-txt-link-rfc2396E" href="mailto:j.c.zuniga@ieee.org">&lt;j.c.zuniga@ieee.org&gt;</a></td>
          </tr>
        </tbody>
      </table>
      <br>
      <br>
      <pre>A new version of I-D, draft-perkins-intarea-multicast-ieee802-03.txt
has been successfully submitted by Charles E. Perkins and posted to the
IETF repository.

Name:		draft-perkins-intarea-multicast-ieee802
Revision:	03
Title:		Multicast Considerations over IEEE 802 Wireless Media
Document date:	2017-07-19
Group:		Individual Submission
Pages:		17
URL:            <a class="moz-txt-link-freetext" href="https://www.ietf.org/internet-drafts/draft-perkins-intarea-multicast-ieee802-03.txt">https://www.ietf.org/internet-drafts/draft-perkins-intarea-multicast-ieee802-03.txt</a>
Status:         <a class="moz-txt-link-freetext" href="https://datatracker.ietf.org/doc/draft-perkins-intarea-multicast-ieee802/">https://datatracker.ietf.org/doc/draft-perkins-intarea-multicast-ieee802/</a>
Htmlized:       <a class="moz-txt-link-freetext" href="https://tools.ietf.org/html/draft-perkins-intarea-multicast-ieee802-03">https://tools.ietf.org/html/draft-perkins-intarea-multicast-ieee802-03</a>
Htmlized:       <a class="moz-txt-link-freetext" href="https://datatracker.ietf.org/doc/html/draft-perkins-intarea-multicast-ieee802-03">https://datatracker.ietf.org/doc/html/draft-perkins-intarea-multicast-ieee802-03</a>
Diff:           <a class="moz-txt-link-freetext" href="https://www.ietf.org/rfcdiff?url2=draft-perkins-intarea-multicast-ieee802-03">https://www.ietf.org/rfcdiff?url2=draft-perkins-intarea-multicast-ieee802-03</a>

Abstract:
   Performance issues have been observed when multicast packet
   transmissions of IETF protocols are used over IEEE 802 wireless
   media.  Even though enhamcements for multicast transmissions have
   been designed at both IETF and IEEE 802, there seems to exist a
   disconnect between specifications, implementations and configuration
   choices.  This draft describes the different issues that have been
   observed, the multicast enhancement features that have been specified
   at IETF and IEEE 802 for wireless media, as well as the operational
   chioces that can be taken to improve the performace of the network.
   Finally, it provides some recommendations about the usage and
   combination of these features and operational choices.

                                                                                  


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat


</pre>
    </div>
  </body>
</html>

--------------150D5F81DA7A0082095F5B38--

