Re: [homenet] Updating DNS [was: How many people have installed the homenet code?]

"Ray Hunter (v6ops)" <> Wed, 11 May 2016 19:29 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id DFC2712D75C for <>; Wed, 11 May 2016 12:29:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -3.596
X-Spam-Status: No, score=-3.596 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.996, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id fxJF2XL92lU2 for <>; Wed, 11 May 2016 12:29:21 -0700 (PDT)
Received: from ( [IPv6:2001:470:1f15:62e::2]) by (Postfix) with ESMTP id C666612D7BA for <>; Wed, 11 May 2016 12:29:17 -0700 (PDT)
Received: from localhost (localhost []) by (Postfix) with ESMTP id E46EC4035E; Wed, 11 May 2016 21:29:16 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id QyehPmmaHj9z; Wed, 11 May 2016 21:29:14 +0200 (CEST)
Received: from MacBook-Pro.local ( []) (Authenticated sender: by (Postfix) with ESMTPA id 1475A4032B; Wed, 11 May 2016 21:29:11 +0200 (CEST)
Message-ID: <>
Date: Wed, 11 May 2016 21:29:09 +0200
From: "Ray Hunter (v6ops)" <>
User-Agent: Postbox 4.0.8 (Macintosh/20151105)
MIME-Version: 1.0
To: Juliusz Chroboczek <>
References: <> <> <> <> <> <> <> <> <> <> <> <> <EMEW3|87dc38b1e390496e02166dafe2490d8as44D0U03tjc||> <> <> <> <>
In-Reply-To: <>
Content-Type: multipart/alternative; boundary="------------000703020809020904030003"
Archived-At: <>
Cc: Tim Chown <>, "" <>, Markus Stenberg <>, Ted Lemon <>
Subject: Re: [homenet] Updating DNS [was: How many people have installed the homenet code?]
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 11 May 2016 19:29:24 -0000

> Juliusz Chroboczek <>
> 11 May 2016 18:29
>> Bonjour is (roughly) based on Appletalk AFAIK. I've got nothing against
>> Appletalk Phase II, so if Bonjour was extended to provide an equivalent
>> function to Appletalk Phase II Zone Information Protocol = ZIP then I'd be
>> happier. That would cover concerns on non-overlapping name spaces. And
>> Appletalk NBP/ZIP resolution also prevents loops in routed networks.
> « The AppleTalk Zone Information Protocol (ZIP) manages the relationship
>    between network numbers and zone names. »
> While I could in principle go and pick a copy of Inside Appletalk at the
> library, I'd be grateful if you could explain what you have in mind.
I do happen to have a (yellowed) copy of "Inside Appletalk" on my 
bookshelf ;)

It would be new functionality to Bonjour, so strictly speaking it's out 
of scope for Homenet.

AFAIK (and I'm sure someone will keep me honest here) Appletalk strongly 
binds network numbers/cable ranges (prefixes in IPv6) to zones (logical 
groupings). Zone associations to network numbers/links are controlled by 
the Appletalk routers (not the hosts directly) and are associated with 
either a logical or physical link. The routing of name resolution 
requests to (extended) networks is based on zones. There can be multiple 
zones per network number, but the first zone is the "default zone" that 
hosts should use if they have no other preference. Host interfaces can 
only have a single network address and be a member of a single zone 
(although I've never actually seen that defined anywhere).

I leave it as a discussion point of whether that's a good model for 
Homenet, especially since IPv6 explicitly supports multiple prefixes per 
link and multiple addresses per interface per host.

Allowing a tight binding of IPv6 prefix <-> Homenet namespace zone could 
possibly work and simplify any solution for e.g. reverse resolution.

The key characteristics (that currently seem to be missing) would be:

1) a mechanism to route name resolution requests in an L3 network

2) a mechanism to prevent/ mitigate the effect of any (transient) loops 
in the name resolution infra (could be sub-function of 1)

3) a mechanism to advertise "zones" between Homenet routers.

4) a mechanism to advertise zones to hosts.

5) a field to indicate "zone membership" of a particular name/label to 
be used by hosts when advertising/resolving names.

>> I don't like the hybrid proxy model either.  It promises the union of
>> the problems and intersection of the functionality.  Proxying flies in
>> the face of the trend of smart devices and dumb networks.
> Very well put.
> -- Juliusz