Re: [mdnsext] The Scope Swamp: Wireless Considerations

"Yi Yang (yiya)" <> Tue, 06 August 2013 19:50 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 65B7021F9A06 for <>; Tue, 6 Aug 2013 12:50:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -8.846
X-Spam-Status: No, score=-8.846 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_BASE64_TEXT=1.753, RCVD_IN_DNSWL_HI=-8]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id fXtp71fJDJKr for <>; Tue, 6 Aug 2013 12:50:01 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 5FA1A21F9A4A for <>; Tue, 6 Aug 2013 12:50:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;;; l=3084; q=dns/txt; s=iport; t=1375818602; x=1377028202; h=from:to:subject:date:message-id:in-reply-to:content-id: content-transfer-encoding:mime-version; bh=nyyxoS0tH3YuP8VTag+YfcR6IwAp1rdLJOJkgp+Eb7A=; b=m5A5NAr/42xq2FcX+iLucx0GYu30wlpsE2e1aWGRJZBMEEujLDNfv5HC DIbLBWjBKOmIpgtti/k+mwESoB8MyIu2uceISNZ7kuAGDDxh90zo+/8cY suFYWv+EFxWDMErb2Zi3mnhAeQzwncy2eg4eJ7j3BBlzxK4bkllxW+0gJ 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhAFAMJSAVKtJXG9/2dsb2JhbABagwY1UIMQu20XgQgWdIImAQQBAQExOh0BCBwGIgQlCyUCBAESCIgIDIoem0AGhGKMfIEijkc4gmE5dAOpL4MXgio
X-IronPort-AV: E=Sophos;i="4.89,827,1367971200"; d="scan'208";a="241254430"
Received: from ([]) by with ESMTP; 06 Aug 2013 19:50:02 +0000
Received: from ( []) by (8.14.5/8.14.5) with ESMTP id r76Jo0sC012813 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 6 Aug 2013 19:50:00 GMT
Received: from ([]) by ([]) with mapi id 14.02.0318.004; Tue, 6 Aug 2013 14:50:00 -0500
From: "Yi Yang (yiya)" <>
To: Alf Watt <>, "" <>
Thread-Topic: [mdnsext] The Scope Swamp: Wireless Considerations
Thread-Index: AQHOkiVfwNYZDvz0TEi43x6OJpyGy5mIqLkA
Date: Tue, 6 Aug 2013 19:49:59 +0000
Message-ID: <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-MacOutlook/
x-originating-ip: []
Content-Type: text/plain; charset="euc-kr"
Content-ID: <>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Subject: Re: [mdnsext] The Scope Swamp: Wireless Considerations
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Discussion of extensions to Bonjour \(mDNS and DNS-SD\) for routed networks." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 06 Aug 2013 19:50:06 -0000

I agree we must consider difference between wired/wireless networks.

Actually, even for a smaller scope, multicast over 802.11 is still an
expensive operation.

On the other hand, we should de-couple discovery scope from
broadcast/multicast domain.



On 8/5/13 5:47 PM, "Alf Watt" <> wrote:

>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.
>mdnsext mailing list