Re: [dnssd] multicast over wireless links

Tom Pusateri <pusateri@bangj.com> Thu, 24 July 2014 23:47 UTC

Return-Path: <pusateri@bangj.com>
X-Original-To: dnssd@ietfa.amsl.com
Delivered-To: dnssd@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7FEA21A0648 for <dnssd@ietfa.amsl.com>; Thu, 24 Jul 2014 16:47:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.038
X-Spam-Level:
X-Spam-Status: No, score=-1.038 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=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 pvbdu6-445u2 for <dnssd@ietfa.amsl.com>; Thu, 24 Jul 2014 16:47:35 -0700 (PDT)
Received: from oj.bangj.com (amt0.gin.ntt.net [129.250.11.170]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 745BD1A0537 for <dnssd@ietf.org>; Thu, 24 Jul 2014 16:47:34 -0700 (PDT)
Received: from dhcp-8c7d.meeting.ietf.org (dhcp-8c7d.meeting.ietf.org [31.133.140.125]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by oj.bangj.com (Postfix) with ESMTPSA id AC32F134B3; Thu, 24 Jul 2014 19:47:34 -0400 (EDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 8.0 \(1971.5\))
From: Tom Pusateri <pusateri@bangj.com>
In-Reply-To: <7414908D-B2A9-4935-912F-EF3E4995065F@nominum.com>
Date: Thu, 24 Jul 2014 19:47:32 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <0696C085-C817-44F1-8CC1-2355A9704623@bangj.com>
References: <331F9173-DB56-4D9A-B09F-956FF6D8DA2B@gmail.com> <DBA73077-1A9F-4E5E-89C7-AF80544F7235@nominum.com> <1F1E6B22-5FF2-41DF-BA86-20A9D57E74CC@gmail.com> <7414908D-B2A9-4935-912F-EF3E4995065F@nominum.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
X-Mailer: Apple Mail (2.1971.5)
Archived-At: http://mailarchive.ietf.org/arch/msg/dnssd/fJFHHx3-nCUvdvD7CmznrgYX9Gc
Cc: dnssd@ietf.org, RJ Atkinson <rja.lists@gmail.com>
Subject: Re: [dnssd] multicast over wireless links
X-BeenThere: dnssd@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Discussion of extensions to Bonjour \(mDNS and DNS-SD\) for routed networks." <dnssd.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnssd>, <mailto:dnssd-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnssd/>
List-Post: <mailto:dnssd@ietf.org>
List-Help: <mailto:dnssd-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnssd>, <mailto:dnssd-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Jul 2014 23:47:36 -0000

> On Jul 24, 2014, at 1:25 PM, Ted Lemon <Ted.Lemon@nominum.com> wrote:
> 
> Asking IEEE to fix WiFi is not really a good approach to addressing the problem of inefficient multicast for existing deployments, and this work is intended to address existing deployments.
> 
> Therefore, I think that if we want to address this use case, the right way to do it is to come up with a mechanism for doing multicast distribution of DNSSD updates on broadcast-friendly networks, and not to just make this the default operational mode for DNSSD.
> 

Having spent a good portion of my career on IP multicast (from Token Ring to IP Multicast VPNs), it baffles me how a radio can have such a difficult time doing IP multicast. The 802.11 link layer clearly needs improvement in this area. Access points regularly fall over dead when bridging an ethernet wired connection to wireless when there is a high data rate multicast stream (actually 4Mbps isn't that high). This is just unacceptable.

With most radios, multicast is the most efficient form of transmission. But in 802.11, every receiver in range currently receives N copies of the multicast to their antenna before throwing all of them but one away. Surely, this can be improved. Multi-unicast over radio broadcast has to be the least efficient mechanism to achieve this.

With so many wireless devices now, streaming live sports events over multicast should be ultra efficient but this isn't the case on 802.11.

There is work to be done in the IEEE and I think that the PIM and MBONED WGs would be pleased to see us open a dialog with IEEE to improve this deficiency.

Optimizing for a single link layer is a rathole that we should avoid if you can take a step back and look at things from a long term perspective. Coming up with an optimization or work-around for a single link layer is fine as a short term solution.

Tom