Re: [homenet] Homenet Naming Architecture

Douglas Otis <> Thu, 21 January 2016 05:36 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 6AFBE1B2F8F for <>; Wed, 20 Jan 2016 21:36:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Status: No, score=-2 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, SPF_PASS=-0.001] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id ssv7rhEvSr8m for <>; Wed, 20 Jan 2016 21:36:12 -0800 (PST)
Received: from ( [IPv6:2607:f8b0:4003:c01::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 13AD31B2F8D for <>; Wed, 20 Jan 2016 21:36:12 -0800 (PST)
Received: by with SMTP id ba1so26925190obb.3 for <>; Wed, 20 Jan 2016 21:36:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20120113; h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-type:content-transfer-encoding; bh=jwTMUBXjlFmNDNHLMSql3RkDxWv8NLhQujdZzJzNqBs=; b=VHkMNYWX141hEN6w232KbcK7vZ0VvNkyj7htV0FpckF4x2d3LQYgbTmxMZDRPwLKvI QQwSzVmmox7NepqluI9t+yRo3hZmbceXmAF+VAkWBqD7aWhAAkG8W9pM1Pp5R/e4tPDr X3JqN7i1Zruvw/5fd67v8zRLveAZRzG98CJNzVLjquWFgOBDqLvE2ejut2Pcw9S/YBoE rrmOUWUN/9VP3WbiIVN9Ke+35e7H4tUJcSfPi8IW8P24fPohFsYhPAFCPTkZw7W6Ii7B O6ivwP94tzg9wIkkpDlmfQVNJ02Trl+9QseHMEcEHHga36uJFKk/m8GIoXwl9xQGbVk2 v47w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-type :content-transfer-encoding; bh=jwTMUBXjlFmNDNHLMSql3RkDxWv8NLhQujdZzJzNqBs=; b=kwxKnQf5jRwjP/dOHC1zAkQHn/EZ/KLQi5AHLjh5prV6qmXDFy5ZahQjYICeN2WCE6 zidAZNagTNeTBXHb74ygWR67bKMhVsT94/aoiLj27rzo7VcrPlgQ7SShUbYhUkdUEDha LkKJTZbMi6RYGa7iG9iLjoVjvrgaKlC4aRtKGnQ7L6wFWv9/iwNZpyVEvxcs3Vad/heR 1xZGsXrz9IB5Qiu5LQgtIdGyrOJQD5Eoer5pDhczdj4qx7D6YQvHugATSaFTGBZVUTGi meuA3YeWBXMAB/Gm2dOVicsCzsv2y6C4/iJoEqWa3s3/7Dw4zrvZEIaPsgZKYcI646As tsVQ==
X-Gm-Message-State: ALoCoQltlMrY2Mc86u7ie4/SBDKN/xidlR8NeCwUkW+MXaAEHZa/LDoWMrvu0mJJwAiD99PR5OsWbGmPi7+U0hKtXr/ANTdADQ==
X-Received: by with SMTP id oo10mr32621455obb.72.1453354571515; Wed, 20 Jan 2016 21:36:11 -0800 (PST)
Received: from US-DOUGO-MAC.local ( []) by with ESMTPSA id a128sm19786028oig.3.2016. (version=TLSv1/SSLv3 cipher=OTHER); Wed, 20 Jan 2016 21:36:10 -0800 (PST)
To: Ted Lemon <>
References: <> <> <> <> <>
From: Douglas Otis <>
X-Enigmail-Draft-Status: N1110
Message-ID: <>
Date: Wed, 20 Jan 2016 21:36:01 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <>
Cc: Stuart Cheshire <>,, Ray Bellis <>
Subject: Re: [homenet] Homenet Naming Architecture
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF Homenet WG mailing list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 21 Jan 2016 05:36:13 -0000

Dear Ted and Ray,

For many users, Internet obtainable services are fairly
limited. One major advantage offered by the Homenet approach
is an ability to cobble together several "limited"
providers to improve reliability.

The TLD '.lo' looks somewhat like a ccTLD and '.lan' has
already been suggested. Since ICANN asked '.lan' and '.home'
be set-aside, why worry about contested naming authority in
these cases? .home or .lan or .lo should not be considered
catch-all domains since they would not be visible beyond the
local network and yet function locally beyond uplink outages.

It seems counter-productive to suggest schemes where
Internet services must work in conjunction with
DNS dedicated at exposing previously private services whose
visibility is normally limited to the local network. Why
should private internal naming even depend on external DNS?
Such an approach is unlikely to be more robust and what
happens when uplinks go down?

Apple learned a valuable lesson when abandoning .me hosting.
Now it seems Homenet is intent at offering similar hosting
services. Such an effort is likely to necessitate an
inordinate level of support and incur additional risk. Are
providers interested in supporting dedicates DNS that sync
addresses and names for all internal services without
substantial cost increases?

Whether a multi-router system makes use of site dedicated
public DNS or not, a naming convention able to extend beyond
the bridge is still needed to properly support multi-device
multi-vendor system configuration, especially in cases where
trickle and babel don't meet their expectations. Naming
conventions able to span bridges would be able to adapt to
any number of strategies that might be used over Homenet
development and deployment.

Douglas Otis