Re: [homenet] RFC 7788-bis

Ray Bellis <ray@bellis.me.uk> Thu, 16 June 2016 18:55 UTC

Return-Path: <ray@bellis.me.uk>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3D9FA12DAFA for <homenet@ietfa.amsl.com>; Thu, 16 Jun 2016 11:55:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=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 IKm3H2ovNAR0 for <homenet@ietfa.amsl.com>; Thu, 16 Jun 2016 11:55:55 -0700 (PDT)
Received: from hydrogen.portfast.net (hydrogen.portfast.net [188.246.200.2]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8789612DAF3 for <homenet@ietf.org>; Thu, 16 Jun 2016 11:55:55 -0700 (PDT)
Received: from [46.227.151.81] (port=54217 helo=rays-mbp.local) by hydrogen.portfast.net ([188.246.200.2]:465) with esmtpsa (fixed_plain:ray@bellis.me.uk) (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) id 1bDcSF-0006rK-2Y (Exim 4.72) for homenet@ietf.org (return-path <ray@bellis.me.uk>); Thu, 16 Jun 2016 19:55:51 +0100
To: homenet@ietf.org
References: <76ed7404-35ff-9cc8-262b-d5785595465c@isc.org> <39B7D708-1CC3-4AB1-8242-4FEAE5CAA272@gmail.com>
From: Ray Bellis <ray@bellis.me.uk>
Message-ID: <85ba77d3-6e59-f457-2e7f-bbf223e12da8@bellis.me.uk>
Date: Thu, 16 Jun 2016 19:55:53 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.1.1
MIME-Version: 1.0
In-Reply-To: <39B7D708-1CC3-4AB1-8242-4FEAE5CAA272@gmail.com>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/E33qm6IucyaUsSHzVXTR3aKfoP8>
Subject: Re: [homenet] RFC 7788-bis
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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: Thu, 16 Jun 2016 18:55:57 -0000


On 16/06/2016 19:48, Ralph Droms wrote:

> In my opinion, it is important for the exact requirements and
> semantics for the default domain be defined, perhaps even before the
> default domain itself is selected.  It's not clear to me whether the
> domain carried in the Domain-Name TLV can be a delegated domain or it
> has to be a special use domain name for location-relative name
> resolution like .local, or if either type of name is OK.

It's my understanding (albeit this may change depending on Ted's work)
that it may be either.

The particular point of ".home" (or whatever) would be to provide a
"special use" domain that is known to have "homenet site local"
semantics that should leak as little as possible outside of that.

I think it would also be appropriate to add whatever name is chosen to
the BCP 163 list of "Locally Server DNS Zones" such that any queries
that do happen to leak beyond the site get sunk by the recursive
resolver that receives them.

Ray