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

Douglas Otis <> Wed, 16 July 2014 02:06 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 7029B1B2A07 for <>; Tue, 15 Jul 2014 19:06:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 4Tlhkrmz-7UQ for <>; Tue, 15 Jul 2014 19:06:47 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:400e:c03::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id AF5D51B29EE for <>; Tue, 15 Jul 2014 19:06:46 -0700 (PDT)
Received: by with SMTP id lf10so355580pab.30 for <>; Tue, 15 Jul 2014 19:06:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=eXbbl9QP2EYtdq+UtA/PMQP+QxcoA7vAsZ4DICzN/pY=; b=nBO2p/B6tU7AgRoy6FjFas9X+Fw/wmvjvnzLz1JCMWGJVOIul3us/Xv1iHyMrqv97h ZAawOlAnLZxC3xZEfglHVPZF2i9sF7rW8YssK4y7bStcHs05YAIpHWlkYUhwwmk7Hf4B oJ2ta4D+A42IzSKJg0kHIKN3oJgJAKGdHZSlPIIRkdqImLUHdLkKke0KeUq0JQYREFSx FDgOoz0vcfd8A0AvIsq+YvwetNM24Nd8ap+77feAOEGg2CCHriCLvKbCdJSWbra87Va4 lLhVHQCqCM4hQL4LclZ02ZHi++65BeCKbJTx9t4J96Xl6FchkFq3aH2iCu6Vu6kFv/BG P2/g==
X-Received: by with SMTP id wz2mr18718171pab.96.1405476406332; Tue, 15 Jul 2014 19:06:46 -0700 (PDT)
Received: from [] ( []) by with ESMTPSA id fu12sm64429683pad.42.2014. for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 15 Jul 2014 19:06:45 -0700 (PDT)
Content-Type: multipart/alternative; boundary="Apple-Mail=_CA9B274A-6B4C-414A-B6E1-E564F9521F37"
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Douglas Otis <>
In-Reply-To: <>
Date: Tue, 15 Jul 2014 19:06:43 -0700
Message-Id: <>
References: <> <> <> <> <> <> <> <> <> <> <> <> <53C58350.3020006@mt> <> <> <> < > <> <53C59926.9020704> <> <>
To: Michael Thomas <>
X-Mailer: Apple Mail (2.1878.6)
Cc:, Ted Lemon <>, Douglas Otis <>
Subject: Re: [homenet] New version draft-mglt-homenet-naming-architecture-dhc-options-02.txt
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 16 Jul 2014 02:06:49 -0000

On Jul 15, 2014, at 5:46 PM, Michael Thomas <> wrote:

> On 07/15/2014 04:42 PM, Ted Lemon wrote:
>> On Jul 15, 2014, at 5:12 PM, Michael Thomas <> wrote:
>>> 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.
>> That's not the point.   If you look at most of the consumer-grade IoT devices that have been announced recently, they all keep the data on their portal and do not allow you to use the device without sending them your data, so chances are the device is going to just talk to their portal using a proprietary scheme and ignore what we want.   Which is fine; my point is not that they are evil, but just that the use case for this may not be quite as broad as we imagine.   I still think it's worth doing, and I hope that over time this stuff moves in the direction of more flexibility.   What we do in homenet can easily either make that easy or make it hard, so we should try to make it easy.
> Oh, ok. But this entire area is going to be pretty darn tricksey to get right, and we can have some hope
> that after enough proprietary we-need-to-get-something-done from vendors, they'll be somewhat relieved
> to have exactly One something that's standardized to support. I've seen this many times at $routervendor,
> even when they have their own business model in mind. So we shouldn't be too fatalistic... the game is still
> young on this account.

Dear Mike, offers a fair amount of detail about safely leveraging home networks.  Further examination of this scheme shows selective publications of devices in DNS and expects other services to be indirectly shared by these devices.  It makes extensive use of ULAs that offer a stable basis for publishing addresses in DNS. and homenet arch also references use of ULAs.

3.6.6.  ULAs as a hint of connection origin

The basic security related premise employed by mDNS can be confirmed by use of ULAs.  It is also conceivable anti-distribution protection schemes can be satisfied when ULAs have a common prefix.  There are also many home routers already able to combine GUA and ULAs.  Add L2TP and it seems we are done.

Douglas Otis