Re: [homenet] [DNSOP] WGLC on "redact" and "homenet-dot"

Ray Bellis <ray@bellis.me.uk> Thu, 15 December 2016 16:59 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 AE06C129B20; Thu, 15 Dec 2016 08:59:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, 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 JjrW5Z_vGXop; Thu, 15 Dec 2016 08:58:59 -0800 (PST)
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 B25DA129B6D; Thu, 15 Dec 2016 08:58:59 -0800 (PST)
Received: from [46.227.151.81] (port=50795 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 1cHZMt-0000RG-5Z (Exim 4.72) (return-path <ray@bellis.me.uk>); Thu, 15 Dec 2016 16:58:55 +0000
To: Bob Harold <rharolde@umich.edu>, Jacques Latour <jacques.latour@cira.ca>
References: <4ab2a538-603e-4e7a-3be9-ad75ed459006@bellis.me.uk> <B192A1B3-03FF-43D1-AD30-12BBA2D65DF0@gmail.com> <9fe0e34d-51e9-bdf3-a650-d8b3681f1cd8@bellis.me.uk> <CAPt1N1=Z2xERw68-=iFGgYYnEO3eDW-8tvhmTmaf4+vU-24grQ@mail.gmail.com> <C059877D829F76429F49E0B48705D888F7FD2C7B@EXCH-01.CORP.CIRA.CA> <CA+nkc8Aj=Ut1-Wp1nu--9WYNNwWjoa6BnpdgazWYTOBLMwRyNQ@mail.gmail.com>
From: Ray Bellis <ray@bellis.me.uk>
Message-ID: <7e907b95-7c00-136d-6632-46ecac0f2edb@bellis.me.uk>
Date: Thu, 15 Dec 2016 16:59:00 +0000
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.5.1
MIME-Version: 1.0
In-Reply-To: <CA+nkc8Aj=Ut1-Wp1nu--9WYNNwWjoa6BnpdgazWYTOBLMwRyNQ@mail.gmail.com>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/uTGdi1RFNjuXl61DaKfaeVaiveg>
Cc: HOMENET <homenet@ietf.org>, Ted Lemon <mellon@fugue.com>, "dnsop@ietf.org WG" <dnsop@ietf.org>
Subject: Re: [homenet] [DNSOP] WGLC on "redact" and "homenet-dot"
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, 15 Dec 2016 16:59:02 -0000


On 15/12/2016 16:57, Bob Harold wrote:
> If an insecure delegation can be made in the root, then could a local
> trust anchor be used by those who want their .homenet domain DNSSEC
> validated?

That's what I would have expected to happen.

> That seems easier than sharing keys or creating subdomains with
> nsupdate.  But I don't know much about trust anchors.

Shared keys would be a nightmare.

Ray