IETF Logo Mail Archive

Re: [homenet] RFC 7788-bis

Michael Richardson <mcr+ietf@sandelman.ca> Fri, 17 June 2016 01:55 UTC

Return-Path: <mcr+ietf@sandelman.ca>
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 B015612D84A for <homenet@ietfa.amsl.com>; Thu, 16 Jun 2016 18:55:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.327
X-Spam-Level:
X-Spam-Status: No, score=-3.327 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-1.426, SPF_PASS=-0.001] 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 9U0Nds91cOcv for <homenet@ietfa.amsl.com>; Thu, 16 Jun 2016 18:55:29 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 010EB12D7A7 for <homenet@ietf.org>; Thu, 16 Jun 2016 18:55:28 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 0FF562009E; Thu, 16 Jun 2016 22:03:06 -0400 (EDT)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id B0D5D638BF; Thu, 16 Jun 2016 21:55:26 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Ray Bellis <ray@bellis.me.uk>
In-Reply-To: <85ba77d3-6e59-f457-2e7f-bbf223e12da8@bellis.me.uk>
References: <76ed7404-35ff-9cc8-262b-d5785595465c@isc.org> <39B7D708-1CC3-4AB1-8242-4FEAE5CAA272@gmail.com> <85ba77d3-6e59-f457-2e7f-bbf223e12da8@bellis.me.uk>
X-Mailer: MH-E 8.6; nmh 1.6+dev; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha1"; protocol="application/pgp-signature"
Date: Thu, 16 Jun 2016 21:55:26 -0400
Message-ID: <26262.1466128526@obiwan.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/VpguPu4lZevDEXIeBbcLoXWlEeE>
Cc: homenet@ietf.org
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: Fri, 17 Jun 2016 01:55:31 -0000

Ray Bellis <ray@bellis.me.uk> 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.

Yes, agreed. When you as for printer.home, you expect a ULA that you can reach.
When you ask for printer.delegatedomain.isp.example.net, you could get a
number of things: GUAs, or even ULAs that you can't reach (because they are
in my home, or because they are in your *other* home [and the VPN is down?]...)

    > 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.

Agreed... and AS112?

-- 
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-

v2.23.0 | Report a Bug | By Email