Re: [DNSOP] Questions on draft-ietf-dnsop-delegation-only

Joe Abley <jabley@hopcount.ca> Thu, 30 July 2020 18:05 UTC

Return-Path: <jabley@hopcount.ca>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E4DAB3A0D72 for <dnsop@ietfa.amsl.com>; Thu, 30 Jul 2020 11:05:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=hopcount.ca
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 elJQu3QgqEWi for <dnsop@ietfa.amsl.com>; Thu, 30 Jul 2020 11:05:06 -0700 (PDT)
Received: from mail-qv1-xf34.google.com (mail-qv1-xf34.google.com [IPv6:2607:f8b0:4864:20::f34]) (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 E550C3A0D6E for <dnsop@ietf.org>; Thu, 30 Jul 2020 11:05:05 -0700 (PDT)
Received: by mail-qv1-xf34.google.com with SMTP id s15so8491778qvv.7 for <dnsop@ietf.org>; Thu, 30 Jul 2020 11:05:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hopcount.ca; s=google; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=yWetShzu0cChVqYD4ViOeOdd8RhEGoM18VnlAlFYI+k=; b=a/z3yqZz/kdyz/NPdLXdiBObS34udoH31DHaZa/ZeCjnsGdDv9td26jvAOldpYf4Zo uBzKZ06lOuiyBgyKuTdsBPMPV9QRsOZGUjZJ8Ny/qlt86MAf8g38HeEQ/pcl4XctXrnh 26YTwElbcAMZ0mpXAfDiWVkKudj7pu0mPw3Fg=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=yWetShzu0cChVqYD4ViOeOdd8RhEGoM18VnlAlFYI+k=; b=iWr8rt8NFDiN3fyP0Cf0aH+RIBDDy4ooR1sN8h5dN4DFXNMNyWhkIDgDcivu6d3C/g c1AZMfBMQ0oiv0rOUy8zKgrj1mm55c3pOtyKFfgLc/X65KI6CthUWO+/OU7D4QMDVqHD BlZ3ZhPAtjce4YHYOQzhwpZZ134Tii+kepKmYlJBjz84hNduMaZi8rZp/1FxGSimx9OE 1as0L6RmSlGAJs91ucHE21XV9V0NY9cYjfY/U2/cm2ZgFZlIO0JgBaR89HZzesl6zEmq kvfH9lDOl49XgeJ12Zm6JxoGn2aX5NXfOJn86+YJBpcfTW+9EQ5tP4BAZaD5D1el5sJV Fc9w==
X-Gm-Message-State: AOAM532+NJbGjG9STNoBgHbhf6Bw1OHgvhlTzcCFJV4c+XhEjDAjNHeg VWMXxouLv2IEsLo63m8Cz5IalEEE1G0YOQ==
X-Google-Smtp-Source: ABdhPJwTo3o5YLq+C5om77clTlHR9lo8rYqDL1demf6yHZZcLNZ125jrBqWvq1F1Q0BZQB+72Ty+4g==
X-Received: by 2002:a0c:b2d6:: with SMTP id d22mr278293qvf.209.1596132304738; Thu, 30 Jul 2020 11:05:04 -0700 (PDT)
Received: from ?IPv6:2607:f2c0:e784:c7:cc64:e39d:b3f2:81cb? ([2607:f2c0:e784:c7:cc64:e39d:b3f2:81cb]) by smtp.gmail.com with ESMTPSA id o39sm5287861qtj.0.2020.07.30.11.05.03 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 30 Jul 2020 11:05:03 -0700 (PDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.1\))
From: Joe Abley <jabley@hopcount.ca>
In-Reply-To: <alpine.LRH.2.23.451.2007301253530.416340@bofh.nohats.ca>
Date: Thu, 30 Jul 2020 14:05:02 -0400
Cc: =?utf-8?B?UGV0ciDFoHBhxI1law==?= <petr.spacek@nic.cz>, dnsop@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <F16107A1-669C-41AD-9F59-1794C64B0737@hopcount.ca>
References: <CAHbrMsDWR0Yf_66f7g6sYm5Wk5vg9avGnLLT2sqezHzJzK4qJw@mail.gmail.com> <05f9f7ce-1bb7-b195-1be5-4db4c13b3145@nic.cz> <alpine.LRH.2.23.451.2007301253530.416340@bofh.nohats.ca>
To: Paul Wouters <paul@nohats.ca>
X-Mailer: Apple Mail (2.3608.120.23.2.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/8lkCv2LjWCNc1KA-Z0jYLG_czFc>
Subject: Re: [DNSOP] Questions on draft-ietf-dnsop-delegation-only
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Jul 2020 18:05:08 -0000

Hi Paul,

On 30 Jul 2020, at 13:20, Paul Wouters <paul@nohats.ca> wrote:

> On Thu, 30 Jul 2020, Petr Špaček wrote:
> 
>> It is hard to see what benefits draft-ietf-dnsop-delegation-only brings without having description of "DNSSEC Trasparency" mechanism available.
> 
> I do not believe that is correct. The first and foremost purpose is for
> the bit to signal the parent zone's behaviour in a public way that
> prevents targeted / coerced attacks from the parent. This allows
> policy violations to be rejected even if these violating DNS answers
> are DNSSEC signed.

Has anybody done a survey to find out how many TLD zones actually fits the description of "delegation-only"?

I know for a fact that ORG does not today and I would say is unlikely ever to. For example, any nameserver N that is subordinate to domain D and linked to some other domain E will be served authoritatively from the ORG zone if domain D is suspended and while E continues to be delegared. Suspensions happen regularly, e.g. for domains implicated in technical abuse. There are several thousand examples of such N today and history suggests the number is not becoming smaller. Even if the number of such N could reach zero in ORG, we could never assume the number would remain at zero and still would not be able to assert usefully that the zone is delegation-only.

I don't think ORG is particularly special in this regard; it seems possible that other (possibly many other; possibly most or all) TLD zones are similar. If there are no TLD zones that actually are delegation-only then there seems no obvious application for it, regardless of whether we consider it to be useful or not.


Joe