[Mcast-wifi] draft-ietf-mboned-ieee802-mcast-problems-03

"Holland, Jake" <jholland@akamai.com> Tue, 06 November 2018 06:53 UTC

Return-Path: <jholland@akamai.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 39682130DCB for <mcast-wifi@ietfa.amsl.com>; Mon, 5 Nov 2018 22:53:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.17
X-Spam-Level:
X-Spam-Status: No, score=-1.17 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.47, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, KHOP_DYNAMIC=1.999, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=akamai.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 c5CQDWr60vWN for <mcast-wifi@ietfa.amsl.com>; Mon, 5 Nov 2018 22:53:26 -0800 (PST)
Received: from mx0b-00190b01.pphosted.com (mx0b-00190b01.pphosted.com [IPv6:2620:100:9005:57f::1]) (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 7A1E112777C for <mcast-wifi@ietf.org>; Mon, 5 Nov 2018 22:53:26 -0800 (PST)
Received: from pps.filterd (m0050102.ppops.net [127.0.0.1]) by m0050102.ppops.net-00190b01. (8.16.0.27/8.16.0.27) with SMTP id wA66prrU010514 for <mcast-wifi@ietf.org>; Tue, 6 Nov 2018 06:53:25 GMT
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; h=from : to : subject : date : message-id : content-type : mime-version; s=jan2016.eng; bh=N+Y6KhIXe1b3bPosbNLf406bUK7vWVSJ+jYxEvsK99I=; b=McMCrzqPqt4dJ9goJ2tLTrVxNjtosoIIC2ebrjlFe5dUgBYrm/cuz8XqEjvBeyDr66qT fE34RKJoeRPHz5elxEPja11MV50ztzBhvcmqqERW5ESLJafyxPhRfvSD51xeNsqeotYR jilnoSlF3oNDOehgVuNdG+rAhZqzEh8L9KGMGm4cCmtNRcecUFwvkt1CLYEr/PO01kAT iBSUJd64QyOm90pHZc+buL7ujeyTZrmg942huS3Fsg8Ujeu77WN1k1X8K/zWl86vQMsT U22W7JqpQ3S2ErQzlGxyljes00Bx/xpzp+OFeE/IiTnSMLWb0Jnf8ehlt5wakJ0fVk0V aA==
Received: from prod-mail-ppoint4 (a96-6-114-87.deploy.static.akamaitechnologies.com [96.6.114.87] (may be forged)) by m0050102.ppops.net-00190b01. with ESMTP id 2njqu8jg4g-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for <mcast-wifi@ietf.org>; Tue, 06 Nov 2018 06:53:25 +0000
Received: from pps.filterd (prod-mail-ppoint4.akamai.com [127.0.0.1]) by prod-mail-ppoint4.akamai.com (8.16.0.21/8.16.0.21) with SMTP id wA66oLNO006950 for <mcast-wifi@ietf.org>; Tue, 6 Nov 2018 01:53:24 -0500
Received: from email.msg.corp.akamai.com ([172.27.27.25]) by prod-mail-ppoint4.akamai.com with ESMTP id 2njxersg6x-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT) for <mcast-wifi@ietf.org>; Tue, 06 Nov 2018 01:53:24 -0500
Received: from USTX2EX-DAG1MB4.msg.corp.akamai.com (172.27.27.104) by ustx2ex-dag1mb6.msg.corp.akamai.com (172.27.27.107) with Microsoft SMTP Server (TLS) id 15.0.1365.1; Mon, 5 Nov 2018 22:53:11 -0800
Received: from USTX2EX-DAG1MB4.msg.corp.akamai.com ([172.27.6.134]) by ustx2ex-dag1mb4.msg.corp.akamai.com ([172.27.6.134]) with mapi id 15.00.1365.000; Tue, 6 Nov 2018 00:53:11 -0600
From: "Holland, Jake" <jholland@akamai.com>
To: "mcast-wifi@ietf.org" <mcast-wifi@ietf.org>
Thread-Topic: draft-ietf-mboned-ieee802-mcast-problems-03
Thread-Index: AQHUdZ1h+Dop/6g+/UqAa/rIwN5GKg==
Date: Tue, 6 Nov 2018 06:53:10 +0000
Message-ID: <7C782491-3AA7-4BF5-A071-04354D8B70E4@akamai.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.12.0.181014
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [172.19.152.160]
Content-Type: multipart/alternative; boundary="_000_7C7824913AA74BF5A07104354D8B70E4akamaicom_"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-11-06_02:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 mlxscore=0 mlxlogscore=591 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1807170000 definitions=main-1811060059
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-11-06_02:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=588 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1807170000 definitions=main-1811060060
Archived-At: <https://mailarchive.ietf.org/arch/msg/mcast-wifi/ShNWqVMwPchUhDkz8YHGfYmqGXA>
Subject: [Mcast-wifi] draft-ietf-mboned-ieee802-mcast-problems-03
X-BeenThere: mcast-wifi@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 06 Nov 2018 06:53:28 -0000

Hello,

I was re-reading the excellent https://tools.ietf.org/html/draft-ietf-mboned-ieee802-mcast-problems-03 earlier today.

Section 4.5 only says this:

   It is often possible to transmit multicast control and data messages
   by using unicast transmissions to each station individually.


It would be nice to see a slightly more in-depth explanation, and I saw a couple of patch reports that might be useful to reference, or use to describe the implementation status:
https://lore.kernel.org/patchwork/patch/752538/
https://gitlab.labs.nic.cz/turris/openwrt/commit/f0c747dee5f0175a5f57ab232eebcf311429c788

I don’t at the moment have a specific suggestion on how to integrate the information, but I thought I’d send these links along, because before I saw them I didn’t know about this part of the implementation and deployment status, and I thought it might be helpful to review.

Best,
Jake