Re: [homenet] New version draft-mglt-homenet-naming-architecture-dhc-options-02.txt

Michael Thomas <mike@mtcc.com> Tue, 15 July 2014 20:27 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 8B8B21A00BF for <homenet@ietfa.amsl.com>; Tue, 15 Jul 2014 13:27:54 -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 XaoMVyLlslNB for <homenet@ietfa.amsl.com>; Tue, 15 Jul 2014 13:27:54 -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 E13C21A008C for <homenet@ietf.org>; Tue, 15 Jul 2014 13:27:53 -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 s6FKRrmb005080 for <homenet@ietf.org>; Tue, 15 Jul 2014 13:27:53 -0700
Message-ID: <53C58EC7.7020905@mtcc.com>
Date: Tue, 15 Jul 2014 13:27:51 -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> <CADZyTk=YgD=JtyDpEz8TXOQmHxKzBoiEZbbW0LhZQy2GaKLqZQ@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>
In-Reply-To: <5EEF0BDB-839A-4E97-876B-C5F66153834C@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/pckx3Y9A4SWon84TXkt77mcXjP8
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 20:27:54 -0000

On 7/15/14, 1:09 PM, Ted Lemon wrote:
> On Jul 15, 2014, at 3:55 PM, Michael Thomas <mike@mtcc.com>; wrote:
>> What I'm trying to say is that DHCP as a way of advertising a service that will host my zone, or
>> in some way make my homenet names globally available is OK, but it should just be about
>> DISCOVERY and nothing else. All of the rest of the mechanisms between my CPE and some service
>> that causes my names to be globally available ought to use standard mechanisms which are not
>> in any way tied to topology.
> Ah, yes.   Agreed, at least in theory.
>
>

Good. If that can be done at all, is there a reason that it cannot have 
those properties?
That is if, say, my Google Nest spams my local homenet advertising the 
Google Eggs-in-one-basket
DNS service, it should use the same set of protocols as a local ISP 
advertising over DHCP to
actually hook everything up between my CPE and their service.

Can we make this a *requirement*? If not, why not?

Mike