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

[Michael Thomas <[e-mail]>]

On 7/15/14, 1:09 PM, Ted Lemon wrote:
> On Jul 15, 2014, at 3:55 PM, Michael Thomas <[e-mail]> 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