Re: [homenet] On the TLD question and validatably-insecure delegation

Ted Lemon <mellon@fugue.com> Wed, 16 November 2016 07:15 UTC

Return-Path: <mellon@fugue.com>
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 1D1481294D4 for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2016 23:15:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level:
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.com
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 J_ijGJsrTFdM for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2016 23:15:34 -0800 (PST)
Received: from mail-wm0-x232.google.com (mail-wm0-x232.google.com [IPv6:2a00:1450:400c:c09::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 26B6A129452 for <homenet@ietf.org>; Tue, 15 Nov 2016 23:15:34 -0800 (PST)
Received: by mail-wm0-x232.google.com with SMTP id c184so29761114wmd.0 for <homenet@ietf.org>; Tue, 15 Nov 2016 23:15:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=WIYSP8iSdnBM+nwx8b6r+zslJHvmvi3NO9m63TPiJhQ=; b=RKv1E8qdGhfhe1swD8LmDYk7iCbzvOddt0VIY2JYfDZCGhCId8BJCAZNLZ25ZwytgW 9kk3L/BskTGtRZZzK06LhLn4dO/XqV3k8kLFfI769okjJ0agBJLqzmHcgxqG5AFMcr9X I3v6y9bYT0e+KOSStclfymugQDtw8cOj5J/n3lgWyiUWO861EEd2XJrLrENwcs+sKZ1r nsbndG3YToLh/3VCqYDMDlSjoF20IyQOHSWL4Bc1b1yxQVVvOexNoaRGooDFxSkYWa7D MInaYG1IQuB8Ye8YdJr5COx8Ilk7h8sNmQWnOsmpCKM9UeXnkJyYBOOqUaq/2rdBBEYi pOpw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=WIYSP8iSdnBM+nwx8b6r+zslJHvmvi3NO9m63TPiJhQ=; b=FPNlGIBlXNRVZT5C/f/BZRBiqWcIwLqPOENTzIJZyeFiyYdMvoBwffGDiOz+6YO/VT 8aBlPb4X5/9ooNjrWgLPUI8KUwm/MEj2Y5AHj5/FRYy9Ek3qT2vg4PTK8Lp2SIpZLYgh P3cvwBMEQGjpEZWuUnu0hONh1pJsxbLkl71t2FpGgTQy/n/CctkHWCZrpS9ekBnHcteJ c560YuSQysXdcioXcinzjXD0EEVhwOVgzVw71yOTkaMEu9WgTzCvf2ipvinOZdp8ml3k VbYg1QOOV811TRgeIwzFXTTR2j2YHw0SQOUe2A/LKINyN6rWv2jcfv3APvznlja5DXzT YBHQ==
X-Gm-Message-State: ABUngvf4kMpQZXkIt8XBDz46jqG7Wd9pjPLw6gAWvTwiiuI0u5IVZoSgxpZWTZMSZn84iYxs3oKqp1cO+erHNg==
X-Received: by 10.25.202.75 with SMTP id h11mr506797lfj.8.1479280532640; Tue, 15 Nov 2016 23:15:32 -0800 (PST)
MIME-Version: 1.0
Received: by 10.25.43.210 with HTTP; Tue, 15 Nov 2016 23:14:52 -0800 (PST)
In-Reply-To: <20161116063043.0CD6C5A467BC@rock.dv.isc.org>
References: <20161116054604.GB55057@mx2.yitter.info> <20161116063043.0CD6C5A467BC@rock.dv.isc.org>
From: Ted Lemon <mellon@fugue.com>
Date: Wed, 16 Nov 2016 16:14:52 +0900
Message-ID: <CAPt1N1m_btPK8TGugoYd7iWxU6sEkPM288biBM3XSS7hRp25MQ@mail.gmail.com>
To: Mark Andrews <marka@isc.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/E4dBWde5MUxzRwYEDK5XjqF7huY>
Cc: HOMENET <homenet@ietf.org>, Andrew Sullivan <ajs@anvilwalrusden.com>
Subject: Re: [homenet] On the TLD question and validatably-insecure delegation
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: Wed, 16 Nov 2016 07:15:36 -0000

Yeah, this sunk in for all of us when we were standing around outside
the meeting room kvetching.   It's a bit of a conundrum.

On Wed, Nov 16, 2016 at 3:30 PM, Mark Andrews <marka@isc.org> wrote:
>
> In message <20161116054604.GB55057@mx2.yitter.info>, Andrew Sullivan writes:
>> Hi,
>>
>> Mark Andrews's point about a DNSSEC insecure delegation today was not
>> I think fully appreciated.
>>
>> In order to create a top-most label in the domain name that can be
>> used this way and that has the necessary properties, we cannot simply
>> instruct IANA to do it.  That is in fact creating a delegation in the
>> root zone of the DNS.  I believe that RFC 2860 (the MoU between the
>> IETF and ICANN) does allow us to create special-use domain names at
>> the top-most level.  But I do not believe it allows us to create
>> special-use domain names at the top-most level _in the DNS_, because
>> that is control of the root zone and it is unambiguously the province
>> of ICANN.
>>
>> Therefore, if the WG decides to use a top-level label for these
>> purposes, we have to apply to ICANN to get it delegated from the root
>> in a provably insecure fashion.  Interestingly, ICANN actually has a
>> policy that it won't delegate things from the root any more that are
>> _not_ DNSSEC signed, and the whole point here is in fact to add an
>> entry that is contrary to that policy, so getting such a delegation
>> would require ICANN to change its policies before it could happen.
>
> I suspect this is a mischaracterization of the policy.  GTLD
> delegations are so constrained.  This is not a GTLD delegation.
>
> New country code delegations are not so constrained.
>
> We are not asking them to delegate away from the roots.
>
> root zone:
> HOMENET. NS A.ROOT-SERVERS.NET.
> ...
> HOMENET. NS M.ROOT-SERVERS.NET.
>
> homenet zone:
> HOMENET. SOA a.root-servers.net. nstld.verisign-grs.com. 1 1800 900 604800 86400
> HOMENET. NS A.ROOT-SERVERS.NET.
> ...
> HOMENET. NS M.ROOT-SERVERS.NET.
>
> B.T.W. this should also be done for .ONION and .LOCAL if we want
> local DNS resolvers to intercept these queries.  DNSSEC keeps
> getting forgotten.  The only reason people aren't screaming
> is that there are very few validating clients and the both
> .ONION and .LOCAL don't use the DNS.  SERVFAIL is nearly as
> good as NXDOMAIN for these use cases.
>
> HOMENET uses the DNS.  If one can get a trust anchor for HOMENET
> installed in every validator there shouldn't be any queries for
> HOMENET/DS.
>
>> That is an important practical fact that ought to be taken into
>> consideration when deciding what kind of label to use.
>>
>> Best regards,
>>
>> A
>>
>> --
>> Andrew Sullivan
>> ajs@anvilwalrusden.com
>>
>> _______________________________________________
>> homenet mailing list
>> homenet@ietf.org
>> https://www.ietf.org/mailman/listinfo/homenet
> --
> Mark Andrews, ISC
> 1 Seymour St., Dundas Valley, NSW 2117, Australia
> PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org
>
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet