Re: [homenet] Routing protocol comparison document

"STARK, BARBARA H" <bs7652@att.com> Fri, 20 February 2015 14:38 UTC

Return-Path: <bs7652@att.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 481DA1A87DF for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 06:38:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level:
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 TAZ2gRduNa6g for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 06:38:04 -0800 (PST)
Received: from nbfkord-smmo07.seg.att.com (nbfkord-smmo07.seg.att.com [209.65.160.93]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6D1221A87D1 for <homenet@ietf.org>; Fri, 20 Feb 2015 06:38:04 -0800 (PST)
Received: from unknown [144.160.229.23] (EHLO alpi154.enaf.aldc.att.com) by nbfkord-smmo07.seg.att.com(mxl_mta-7.2.4-5) with ESMTP id cc647e45.2b5e9a803940.2961118.00-2424.8364993.nbfkord-smmo07.seg.att.com (envelope-from <bs7652@att.com>); Fri, 20 Feb 2015 14:38:04 +0000 (UTC)
X-MXL-Hash: 54e746cc2f22adf0-43e41d29f831618261676b8de8633480bbe12754
Received: from unknown [144.160.229.23] (EHLO alpi154.enaf.aldc.att.com) by nbfkord-smmo07.seg.att.com(mxl_mta-7.2.4-5) over TLS secured channel with ESMTP id 9b647e45.0.2960989.00-2122.8364607.nbfkord-smmo07.seg.att.com (envelope-from <bs7652@att.com>); Fri, 20 Feb 2015 14:37:46 +0000 (UTC)
X-MXL-Hash: 54e746ba60013737-1d3cb55644dfa9c73d86208411467767bb1dc638
Received: from enaf.aldc.att.com (localhost [127.0.0.1]) by alpi154.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id t1KEbia6018539; Fri, 20 Feb 2015 09:37:44 -0500
Received: from alpi132.aldc.att.com (alpi132.aldc.att.com [130.8.217.2]) by alpi154.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id t1KEbfsb018532 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 20 Feb 2015 09:37:42 -0500
Received: from GAALPA1MSGHUBAD.ITServices.sbc.com (GAALPA1MSGHUBAD.itservices.sbc.com [130.8.218.153]) by alpi132.aldc.att.com (RSA Interceptor); Fri, 20 Feb 2015 14:37:38 GMT
Received: from GAALPA1MSGUSRBF.ITServices.sbc.com ([169.254.5.126]) by GAALPA1MSGHUBAD.ITServices.sbc.com ([130.8.218.153]) with mapi id 14.03.0224.002; Fri, 20 Feb 2015 09:37:38 -0500
From: "STARK, BARBARA H" <bs7652@att.com>
To: 'Toerless Eckert' <eckert@cisco.com>, Mikael Abrahamsson <swmike@swm.pp.se>
Thread-Topic: [homenet] Routing protocol comparison document
Thread-Index: AQHQSU32GNhjW8WFi0qWgaveVMetmJz2sruAgAAaSQCAABl7AIAABlyAgAAB2ICAAHYtgIAAi9MAgACD2oCAAAHHgIAAAyGAgAAURoCAAA90gIAAAkAAgAABTQCAAAKJAIAAX5aAgAClmgCAAEmQgP//rgRw
Date: Fri, 20 Feb 2015 14:37:38 +0000
Message-ID: <2D09D61DDFA73D4C884805CC7865E61130F3035D@GAALPA1MSGUSRBF.ITServices.sbc.com>
References: <871tllhq2u.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191639010.4007@uplift.swm.pp.se> <3E7E9C84-7EC3-4343-AC87-31D03A67ED79@fugue.com> <alpine.DEB.2.02.1502191804380.4007@uplift.swm.pp.se> <EA65B4B3-01D1-4332-BF55-0FEB1DCD0C31@fugue.com> <alpine.DEB.2.02.1502191905490.4007@uplift.swm.pp.se> <8B98F698-983D-4D2A-B5D1-7ACED27C275E@fugue.com> <alpine.DEB.2.02.1502191920560.4007@uplift.swm.pp.se> <CAPRuP3mpNJTu6mP+RAVKKO0kt60PogNtNbCUCRRqxe9im3EzjA@mail.gmail.com> <alpine.DEB.2.02.1502201042330.4007@uplift.swm.pp.se> <20150220142041.GC8096@cisco.com>
In-Reply-To: <20150220142041.GC8096@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.61.166.72]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-RSA-Inspected: yes
X-RSA-Classifications: public
X-AnalysisOut: [v=2.0 cv=KNft+i5o c=1 sm=1 a=VXHOiMMwGAwA+y4G3/O+aw==:17 a]
X-AnalysisOut: [=vKzWRVGcsRAA:10 a=BLceEmwcHowA:10 a=kj9zAlcOel0A:10 a=zQP]
X-AnalysisOut: [7CpKOAAAA:8 a=XIqpo32RAAAA:8 a=0HtSIViG9nkA:10 a=48vgC7mUA]
X-AnalysisOut: [AAA:8 a=ZyAdMjAvPDAnrEWUhLEA:9 a=CjuIK1q_8ugA:10]
X-Spam: [F=0.2000000000; CM=0.500; S=0.200(2014051901)]
X-MAIL-FROM: <bs7652@att.com>
X-SOURCE-IP: [144.160.229.23]
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/DvIOxsnTAClfVVPCbqd8zW1ZiDQ>
Cc: Andrew Mcgregor <andrewmcgr@google.com>, "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet/>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homenet>, <mailto:homenet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Feb 2015 14:38:06 -0000

> There are good proposal how to do servicce discovery in homenets or the
> like with DNS-SD (/mDNS), but i think we should still worry about
> compatibility with UPnP. Both of these requirements (UPnP and DNS-SD) are
> IMHO better solved with router-level "proxy"
> solutions than with ASM IP multicast.

FYI. I did a presentation to DLNA (which has a lot of key UPnP people) that warned them to start thinking about service discovery in the multi-router world, and the world where more and more Wi-Fi APs are limiting the multicast that makes it to Wi-Fi devices. I mentioned the DNS-SD proxy work, homenet, and told them:
" - People have started to study the current quantity of multicast traffic and its impact on power consumption by battery-operated Wi-Fi devices.
http://tools.ietf.org/html/draft-desmouceaux-ipv6-mcast-wifi-power-usage-00
http://tools.ietf.org/html/draft-vyncke-6man-mcast-not-efficient-00
 - Concern is growing and proposals are starting to appear for ways to decrease the quantity of multicast messages.
http://tools.ietf.org/html/draft-yourtchenko-colitti-nd-reduce-multicast-00 "

My recommendations were that they had 2 basic options of either also supporting DNS-SD / mDNS for service discovery, or defining a SSDP proxy similar to what I expect will be done for DNS-SD. Anyway, I told them I'd keep them updated on the state of affairs regarding this issue.
Barbara