Re: [homenet] New version draft-mglt-homenet-naming-architecture-dhc-options-02.txt
Michael Thomas <mike@mtcc.com> Tue, 15 July 2014 21:12 UTC
Return-Path: <mike@mtcc.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 BD8611B2920 for <homenet@ietfa.amsl.com>; Tue, 15 Jul 2014 14:12:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.753
X-Spam-Level:
X-Spam-Status: No, score=-1.753 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_ALL=0.8, RP_MATCHES_RCVD=-0.651, 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 81_3wi0AshWG for <homenet@ietfa.amsl.com>; Tue, 15 Jul 2014 14:12:09 -0700 (PDT)
Received: from mtcc.com (mtcc.com [50.0.18.224]) (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 0D3741A007C for <homenet@ietf.org>; Tue, 15 Jul 2014 14:12:09 -0700 (PDT)
Received: from [10.1.10.25] (c-50-148-182-215.hsd1.ca.comcast.net [50.148.182.215]) (authenticated bits=0) by mtcc.com (8.14.7/8.14.7) with ESMTP id s6FLC8p0017091 for <homenet@ietf.org>; Tue, 15 Jul 2014 14:12:08 -0700
Message-ID: <53C59926.9020704@mtcc.com>
Date: Tue, 15 Jul 2014 14:12:06 -0700
From: Michael Thomas <mike@mtcc.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: homenet@ietf.org
References: <CADZyTkk6rUuFJ5Wds2hioBBQa9-kXDJxyg_gBGQ1R6u5CHF2Ww@mail.gmail.com> <87vbrcydr9.wl.jch@pps.univ-paris-diderot.fr> <CADZyTk=kST4zPaPzz4DsAcCOtmYbQo-s2du+nEvJv0MSrneEMg@mail.gmail.com> <CADZyTkmZ+rC99qeC7gFEwc4JBoX9sHBUpo7p89+VC6zY7Z8drQ@mail.gmail.com> <87d2dfb98w.wl-jch@pps.univ-paris-diderot.fr> <CADZyTk=U25=Yck8BL5nrzGAR7mPk5HWp0r0h2wYy5ruSOf6rsQ@mail.gmail.com> <87vbr6mv8t.wl-jch@pps.univ-paris-diderot.fr> <7EEF5CD0-C3B8-4559-A75D-E55931F94F61@iki.fi> <21162.1405438875@sandelman.ca> <7ioawqpqcv.wl%jch@pps.univ-paris-diderot.fr> <7B5390DD-6969-4E26-A85E-0B436F48448F@fugue.com> <87a98acvxe.wl-jch@pps.univ-paris-diderot.fr> <E01C736F-75C0-436C-A283-28763208E46E@iki.fi> <F689B456-2A87-41BE-8884-ED23BD35D748@fugue.com> <53C58350.3020006@mt cc.com> <9F076247-1C4B-4006-98D7-BA1DAE2E9438@fugue.com> <53C58719.8020209@mtcc.com> <5EEF0BDB-839A-4E97-876B-C5F66153834C@fugue.com> <53C58EC7.7020905@mtcc.com > <ABAC9C0C-307C-42FC-A680-25B6E7F80AB8@fugue.com>
In-Reply-To: <ABAC9C0C-307C-42FC-A680-25B6E7F80AB8@fugue.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/RrDcWFLf4nNbgoBzbhXRcHYI0cQ
Subject: Re: [homenet] New version draft-mglt-homenet-naming-architecture-dhc-options-02.txt
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: Tue, 15 Jul 2014 21:12:09 -0000
On 7/15/14, 1:53 PM, Ted Lemon wrote: > We can safely assume that any device that is monetized through the cloud will do everything in its power to prevent us from accessing it, so that's really not the interesting test case. The interesting test case is whether a Nest-like device that isn't operated through the manufacturer's captive portal will use this set of standard protocols. (I don't know what the policies behind Nest are specifically, but the phenomenon I'm talking about is more the rule than the exception in citizen-grade IoT devices at the moment). I believe we are at least in the fortunate situation that nobody's tried hard to do a naming provider land grab yet, so there may yet be time to do the right thing. >> Can we make this a *requirement*? If not, why not? > We can't force anybody to do anything, that's why not. But we can document a mechanism for doing it, and if implementation becomes widespread in home gateways, it's not unreasonable to think that devices that _don't_ depend on a captive portal for monetization will use these protocols rather than reinventing the wheel. But bear in mind that this is a fairly big "if." > I mean a requirement for the homenet working group, of course. I'm not entirely sure what the appetite is for wheel reinvention in this space is, but I'm guessing it's not that high if this working group comes up with something that is workable, and gives CPE vendors something to shoot for rather than a bunch of ad hoc point solutions requiring bilateral dev agreements. We should be really clear that "CPE" !== "Router" too. If the Nest wants to be my DNS name repository that gets mirrored out in Google's intrastructure somehow, that should OK too. I think its main requirement is that it: a) doesn't move around out of my homenet b) is always on Mike
- [homenet] New version draft-mglt-homenet-naming-a… Daniel Migault
- Re: [homenet] New version draft-mglt-homenet-nami… Juliusz Chroboczek
- Re: [homenet] New version draft-mglt-homenet-nami… Douglas Otis
- Re: [homenet] New version draft-mglt-homenet-nami… Mikael Abrahamsson
- Re: [homenet] New version draft-mglt-homenet-nami… Daniel Migault
- Re: [homenet] New version draft-mglt-homenet-nami… Juliusz Chroboczek
- Re: [homenet] New version draft-mglt-homenet-nami… Ray Bellis
- Re: [homenet] New version draft-mglt-homenet-nami… Mikael Abrahamsson
- Re: [homenet] New version draft-mglt-homenet-nami… Juliusz Chroboczek
- Re: [homenet] New version draft-mglt-homenet-nami… Andrew Sullivan
- Re: [homenet] New version draft-mglt-homenet-nami… Michael Richardson
- Re: [homenet] New version draft-mglt-homenet-nami… Douglas Otis
- Re: [homenet] New version draft-mglt-homenet-nami… Mikael Abrahamsson
- Re: [homenet] New version draft-mglt-homenet-nami… Daniel Migault
- Re: [homenet] New version draft-mglt-homenet-nami… Juliusz Chroboczek
- Re: [homenet] New version draft-mglt-homenet-nami… Daniel Migault
- Re: [homenet] New version draft-mglt-homenet-nami… Juliusz Chroboczek
- Re: [homenet] New version draft-mglt-homenet-nami… Daniel Migault
- Re: [homenet] New version draft-mglt-homenet-nami… Juliusz Chroboczek
- Re: [homenet] New version draft-mglt-homenet-nami… Markus Stenberg
- Re: [homenet] New version draft-mglt-homenet-nami… Michael Thomas
- Re: [homenet] New version draft-mglt-homenet-nami… Michael Richardson
- Re: [homenet] New version draft-mglt-homenet-nami… Juliusz Chroboczek
- Re: [homenet] New version draft-mglt-homenet-nami… Gert Doering
- Re: [homenet] New version draft-mglt-homenet-nami… Ted Lemon
- Re: [homenet] New version draft-mglt-homenet-nami… Juliusz Chroboczek
- Re: [homenet] New version draft-mglt-homenet-nami… Markus Stenberg
- Re: [homenet] New version draft-mglt-homenet-nami… Juliusz Chroboczek
- Re: [homenet] New version draft-mglt-homenet-nami… Ted Lemon
- Re: [homenet] New version draft-mglt-homenet-nami… Michael Thomas
- Re: [homenet] New version draft-mglt-homenet-nami… Ted Lemon
- Re: [homenet] New version draft-mglt-homenet-nami… Michael Thomas
- Re: [homenet] New version draft-mglt-homenet-nami… Ted Lemon
- Re: [homenet] New version draft-mglt-homenet-nami… Michael Thomas
- Re: [homenet] New version draft-mglt-homenet-nami… Ted Lemon
- Re: [homenet] New version draft-mglt-homenet-nami… Michael Thomas
- Re: [homenet] New version draft-mglt-homenet-nami… Mark Baugher (mbaugher)
- Re: [homenet] New version draft-mglt-homenet-nami… Ted Lemon
- Re: [homenet] New version draft-mglt-homenet-nami… Michael Thomas
- Re: [homenet] New version draft-mglt-homenet-nami… Ted Lemon
- Re: [homenet] New version draft-mglt-homenet-nami… Douglas Otis