[mdnsext] The Scope Swamp: Wireless Considerations

Alf Watt <alf.watt@ruckuswireless.com> Mon, 05 August 2013 21:47 UTC

Return-Path: <alf.watt@ruckuswireless.com>
X-Original-To: mdnsext@ietfa.amsl.com
Delivered-To: mdnsext@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id D3AB921F9CCC for <mdnsext@ietfa.amsl.com>; Mon, 5 Aug 2013 14:47:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id 4c8VrkU+XquN for <mdnsext@ietfa.amsl.com>; Mon, 5 Aug 2013 14:47:41 -0700 (PDT)
Received: from db8outboundpool.messaging.microsoft.com (mail-db8lp0186.outbound.messaging.microsoft.com []) by ietfa.amsl.com (Postfix) with ESMTP id 29D6A21F9CEF for <mdnsext@ietf.org>; Mon, 5 Aug 2013 14:47:40 -0700 (PDT)
Received: from mail74-db8-R.bigfish.com ( by DB8EHSOBE029.bigfish.com ( with Microsoft SMTP Server id; Mon, 5 Aug 2013 21:47:30 +0000
Received: from mail74-db8 (localhost []) by mail74-db8-R.bigfish.com (Postfix) with ESMTP id 6C6B9DC00EC for <mdnsext@ietf.org>; Mon, 5 Aug 2013 21:47:30 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:; KIP:(null); UIP:(null); IPV:NLI; H:BL2PRD0810HT001.namprd08.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: 0
X-BigFish: PS0(zzzz1f42h208ch1ee6h1de0h1fdah2073h1202h1e76h1d1ah1d2ah1fc6hzz17326ah1de096hc704dh8275bh1de097hz2fh2a8h668h839h947he5bhf0ah1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h18e1h1946h19b5h19ceh1ad9h1b0ah1d0ch1d2eh1d3fh1dc1h1dfeh1dffh1e1dh1155h)
Received-SPF: pass (mail74-db8: domain of ruckuswireless.com designates as permitted sender) client-ip=; envelope-from=alf.watt@ruckuswireless.com; helo=BL2PRD0810HT001.namprd08.prod.outlook.com ; .outlook.com ;
X-Forefront-Antispam-Report-Untrusted: SFV:NSPM; SFS:(199002)(189002)(74366001)(80022001)(76176001)(74706001)(46102001)(74662001)(74502001)(79102001)(66066001)(69226001)(53806001)(76482001)(80976001)(47446002)(56776001)(59766001)(74876001)(77982001)(63696002)(54356001)(31966008)(65816001)(51856001)(81342001)(36756003)(54316002)(15202345003)(4396001)(76786001)(76796001)(56816003)(77096001)(47976001)(50986001)(49866001)(81542001)(83072001)(47736001)(16406001)(19580385001)(83322001)(19580395003); DIR:OUT; SFP:; SCL:1; SRVR:BLUPR08MB085; H:BLUPR08MB087.namprd08.prod.outlook.com; RD:InfoNoRecords; A:1; MX:1; LANG:en;
Received: from mail74-db8 (localhost.localdomain []) by mail74-db8 (MessageSwitch) id 1375739247952986_18286; Mon, 5 Aug 2013 21:47:27 +0000 (UTC)
Received: from DB8EHSMHS020.bigfish.com (unknown []) by mail74-db8.bigfish.com (Postfix) with ESMTP id DAF1DA40048 for <mdnsext@ietf.org>; Mon, 5 Aug 2013 21:47:27 +0000 (UTC)
Received: from BL2PRD0810HT001.namprd08.prod.outlook.com ( by DB8EHSMHS020.bigfish.com ( with Microsoft SMTP Server (TLS) id; Mon, 5 Aug 2013 21:47:27 +0000
Received: from BLUPR08MB085.namprd08.prod.outlook.com ( by BL2PRD0810HT001.namprd08.prod.outlook.com ( with Microsoft SMTP Server (TLS) id 14.16.341.1; Mon, 5 Aug 2013 21:47:26 +0000
Received: from BLUPR08MB087.namprd08.prod.outlook.com ( by BLUPR08MB085.namprd08.prod.outlook.com ( with Microsoft SMTP Server (TLS) id 15.0.702.21; Mon, 5 Aug 2013 21:47:25 +0000
Received: from BLUPR08MB087.namprd08.prod.outlook.com ([]) by BLUPR08MB087.namprd08.prod.outlook.com ([]) with mapi id 15.00.0702.005; Mon, 5 Aug 2013 21:47:25 +0000
From: Alf Watt <alf.watt@ruckuswireless.com>
To: "mdnsext@ietf.org" <mdnsext@ietf.org>
Thread-Topic: The Scope Swamp: Wireless Considerations
Thread-Index: AQHOkiVfwNYZDvz0TEi43x6OJpyGyw==
Date: Mon, 5 Aug 2013 21:47:24 +0000
Message-ID: <CE1E9246.8CB7%alf.watt@ruckuswireless.com>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-MacOutlook/
x-originating-ip: []
x-forefront-prvs: 0929F1BAED
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <814C820008CB324785363B7E1588DB99@namprd08.prod.outlook.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: ruckuswireless.com
Subject: [mdnsext] The Scope Swamp: Wireless Considerations
X-BeenThere: mdnsext@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Discussion of extensions to Bonjour \(mDNS and DNS-SD\) for routed networks." <mdnsext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mdnsext>, <mailto:mdnsext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mdnsext>
List-Post: <mailto:mdnsext@ietf.org>
List-Help: <mailto:mdnsext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mdnsext>, <mailto:mdnsext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Aug 2013 21:47:46 -0000

Following up from the BoF discussion in Berlin today on scoping of service

The discussion of scope needs to acknowledge the difference between wired
and wireless networks.

In all IP networks the size of the broadcast domain is a fundamental
limitation, as the number of devices on the link increases the broadcast
traffic begins to consume a larger and larger percentage of the available
bandwidth. Traditionally large wired networks were segmented along
physical lines, by floor or wing, for example, with each area being
assigned a subnet and routed to provide end-to-end connectivity.

Wi-Fi users expect (and the 802.11 protocol requires) that users on a
single SSID are connected to the same IP network and broadcast domain so
that they can roam seamlessly anywhere within a particular ESS (which can
be a building, campus or metro area). Limiting the size of these broadcast
domains means separating users onto different Wi-Fi networks depending on
their role, instead of their location.

So for wired networks we have a natural, physical scope depending on the
physical connection of hosts, in wireless networks we have scopes which
depend largely on the users access rights (since Wi-Fi is almost always
the security demarkation in networks).

It¹s also worth nothing that the BCP for broadcast domain size is only 255
hosts (a /24) which makes the 802.11 ESS requirement for a single
broadcast domain behind a given ESS difficult to achieve for large
networks, which is why many Wi-Fi vendors support multicast filtering,
client isolation and ARP proxies all of which can impact mDNS usability.


FYA http://www.youtube.com/watch?v=-FizhXOW2VM&noredirect=1