Re: [DNSOP] DNS Delegation Requirements

Ólafur Guðmundsson <olafur@cloudflare.com> Mon, 08 February 2016 12:57 UTC

Return-Path: <olafur@cloudflare.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CB2391B2A62 for <dnsop@ietfa.amsl.com>; Mon, 8 Feb 2016 04:57:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.078
X-Spam-Level:
X-Spam-Status: No, score=-1.078 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001] autolearn=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 E6GiBgRXUml2 for <dnsop@ietfa.amsl.com>; Mon, 8 Feb 2016 04:57:33 -0800 (PST)
Received: from mail-yw0-x22a.google.com (mail-yw0-x22a.google.com [IPv6:2607:f8b0:4002:c05::22a]) (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 F3F8D1B2A74 for <dnsop@ietf.org>; Mon, 8 Feb 2016 04:57:32 -0800 (PST)
Received: by mail-yw0-x22a.google.com with SMTP id h129so100972381ywb.1 for <dnsop@ietf.org>; Mon, 08 Feb 2016 04:57:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cloudflare.com; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=yqmA6ToyF+1fd+zwyypn0Xn8cJWZw0tY6y0RU0Swk8s=; b=UMxSFbCs4iuF/hwgWFmkQCPNfuekwGWpA0HvwSKMtbIC+iS93p5mQhaMa3+g33fwba iUkI5OoYv2/wwQh3dGVX77O6mUivYBn8IU6lrw4MfKfuQjKn0lIFn/vPgXMeOdgOcqzb Ldrx/JAVMhHOvQ6P3UzgS+BWT3e0fOwlpI7ls=
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:date :message-id:subject:from:to:cc:content-type; bh=yqmA6ToyF+1fd+zwyypn0Xn8cJWZw0tY6y0RU0Swk8s=; b=SZlfWHDFgsej5lucqfUoA8Of/Z7oCPWFrIQwAqBs0PuAqO6InzAGMkDCMIwqoi2usE ESHArHB5li5LavzSsSddmUmxqSmvegk1hqjex5j+RZSQTUdzQHe/y0lUaQ6LO9VGtcHu RwmeJ4HHDY4kHETiARulZxo3r9RsqlhS3rNUPOgd/PRxzBIQ/yPe2w0qe0JIItdFT1H0 bx1pUOCN2svSAbJ3/75vldPNcbQsMqsjcz+C9q80X7IEpAaQlqJPMmEEuY7+uGGsJw8N Yj9MY8AsykdH8mtn59qTqoVxsbQJBkL+FX2R0msUG+tBpY/eeANlwZ4CMtcJuSdywnwE cMRg==
X-Gm-Message-State: AG10YOQvhDs5AsrC7MBIurtRV4SGamF0h7BN0Ol1xGVZBV4BdfFiqENuhb2vOrJzHDji41ILFdxCuL1pOvXXK/Xt
MIME-Version: 1.0
X-Received: by 10.129.55.199 with SMTP id e190mr5462288ywa.55.1454936252286; Mon, 08 Feb 2016 04:57:32 -0800 (PST)
Received: by 10.37.64.65 with HTTP; Mon, 8 Feb 2016 04:57:32 -0800 (PST)
In-Reply-To: <3A6EF5A0-928C-4F10-BD68-265DAE87F9A8@kirei.se>
References: <3A6EF5A0-928C-4F10-BD68-265DAE87F9A8@kirei.se>
Date: Mon, 08 Feb 2016 12:57:32 +0000
Message-ID: <CAN6NTqw=zkoMDxvyY0RN5PVe+2_WjYTdPW20utvmKC7vuqo+Yg@mail.gmail.com>
From: Ólafur Guðmundsson <olafur@cloudflare.com>
To: Jakob Schlyter <jakob@kirei.se>
Content-Type: multipart/alternative; boundary="001a1143fcc07d3b4e052b41bec8"
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/rwUuso6O0EQvn1W-oRW3NKZgq9o>
Cc: dnsop <dnsop@ietf.org>, Patrik Wallström <patrik.wallstrom@iis.se>
Subject: Re: [DNSOP] DNS Delegation Requirements
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
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: Mon, 08 Feb 2016 12:57:35 -0000

Jakob, Patrik
thanks for writing this up, a great start.

On first read this document seems to be duplicating what is in
https://tools.ietf.org/html/rfc1912
It is hard to see what is new and what is the same.

There are number of assumptions in the current draft, that only apply when
the DNS contents  are distributed as zone in "files or axfr"  which not all
operators use.
There are few other examples of "rules" that show this document is written
from a TLD's perspective which is different from what Domain operators may
want to practice.

So before we start working on exactly what is in the current draft, can we
have a discussion about what should be in the document.

For example the document omits all discussion on TTL's is that
good/bad/separate ?
Do we want to talk about how many addresses are associated with a name
server name. (common practice is 1 A and/or 1 AAAA but will more work?)
Are the "current" naming rules still something we want to promote, i.e. can
we get rid of the Hostname rules from https://tools.ietf.org/html/rfc953

IMHO this should be a BCP candidate that obsoletes all prior guidance, no
matter what RFC the guidance came from.

Olafur



On Mon, Feb 8, 2016 at 8:57 AM, Jakob Schlyter <jakob@kirei.se> wrote:

> As we've seen to good summary on requirements for on a well-behaved DNS
> delegation of a domain name, Patrik Wallström and myself has written an
> Internet-Draft [1] describing such requirements. The requirements were
> developed within the CENTR Test Requirements Task Force (TRTF) and m ost of
> the original requirements and text originate from the Zonemaster [2][3]
> project.
>
> At this point, we're seeking more public comments - on this mailing list
> (unless the chairs disapproves), on the our issue tracker [4] or via email
> to the authors.
>
>
>         jakob
>
>
> [1]
> https://www.ietf.org/id/draft-wallstrom-dnsop-dns-delegation-requirements-00.txt
> [2] https://zonemaster.net/
> [3] https://github.com/dotse/zonemaster
> [4] https://github.com/CENTRccTLDs/TRTF/issues
>
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop
>