Re: [DNSOP] Current DNS standards, drafts & charter

Matthew Pounsett <matt@conundrum.com> Sun, 01 April 2018 21:51 UTC

Return-Path: <matt@conundrum.com>
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 A15A7120227 for <dnsop@ietfa.amsl.com>; Sun, 1 Apr 2018 14:51:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=conundrum-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 FHGhZHRJql7L for <dnsop@ietfa.amsl.com>; Sun, 1 Apr 2018 14:51:51 -0700 (PDT)
Received: from mail-io0-x229.google.com (mail-io0-x229.google.com [IPv6:2607:f8b0:4001:c06::229]) (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 3CD351201F2 for <dnsop@ietf.org>; Sun, 1 Apr 2018 14:51:51 -0700 (PDT)
Received: by mail-io0-x229.google.com with SMTP id 141so16069035iou.12 for <dnsop@ietf.org>; Sun, 01 Apr 2018 14:51:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=conundrum-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=soHbPVaZ5amU505tPpaDTugbNkDbF3csovcbXURC5QA=; b=CTTqpQ2IkzIKA6QKmojqHbCpaws+PN8ORoZFhdFW2UAyBhFthNSzqBKef4/I/BctVr Sw2rDgymo+8BCOGvhhvb7atiwEWeOwBKJE2xo82BEWFIFdVmNybx6e/54guzHBx8WLaU 2ys3FZdXsPpvr/Pc2flNVV4+8RQqWwSg6Wsiv8P988RT4KEFEzRiOAHwL+cElla1bve6 za2ct5d/lOCNN3B5zsO2aon+V8IW8xkxjQ+xHBR6bbt86Q7f+nU/ELXAXs4rQeK4cZfM bKpzo3gfOBo6yWgGnvLtOqSFRItGjoGDse8JyJYImLKLaLpHYoaHAJ8IQT8JmvTB1lrx 3b/Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=soHbPVaZ5amU505tPpaDTugbNkDbF3csovcbXURC5QA=; b=CLpcqUh2OBlO8/vNLZGFDlJ2WLQbvrMkL0OvHB1JV1nZHVz9nUnhlodtJxLF42jwRe Br84Sq+6hHMNCFJJU+xq4CjEVU7aZPHpOXmeAvVFxmr5oiEQVgNSNnIuRs6LAhGLyWjy lH3Y9wHYTuFHllcry2P/Bt+YCwVmdr+UHAhGqAsVIg/UO9EYk2zk5ktJyeISDvHIAMI3 /etJOK9PlL1NsxIQQCipLhBmYuM/IHQpv69q6NYJNq2jfiazwVDQ/VZx/QKlu7y0JHWO n3cKIwq7vRmokmFdA3asEdas5CKP8AtAtDETugqrpx7Ug41P+EaVSj4y7oI2Wd5FfqOz 1uwg==
X-Gm-Message-State: AElRT7HKJTZMLdRRoQfHNXkBUE5SEQuyGvPZybqUUf/FxLk0G2C1Yj0u KtQVVsVQSMv2Ui/xAh2eIeIVUXJivbqEL+wp4glWmA==
X-Google-Smtp-Source: AIpwx4//wn8nbp07AEHlJDJoOmyWo2bzwkJCg9ezaqbag65JP8pup09MCn9athQNji9suGe5/hApU4X0tGQ2ah88FdE=
X-Received: by 10.107.105.26 with SMTP id e26mr6233067ioc.249.1522619510407; Sun, 01 Apr 2018 14:51:50 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.2.112.197 with HTTP; Sun, 1 Apr 2018 14:51:49 -0700 (PDT)
In-Reply-To: <20180331213429.GB31712@server.ds9a.nl>
References: <20180326154645.GB24771@server.ds9a.nl> <CA3D81B6-164F-4607-A7E6-B999B90C4DA8@gmail.com> <5852643C-B414-4C3E-A1B9-553054D3DD46@isc.org> <CAAiTEH8aA3J1j4iUQDisDHiUJXopykKkssuhOK=v+iVV_XZWyA@mail.gmail.com> <5ABAB891.3010306@redbarn.org> <937cde61-3e8e-ea65-b2fd-ed4030f2e311@gmail.com> <20180331210906.GA11628@jurassic> <20180331213429.GB31712@server.ds9a.nl>
From: Matthew Pounsett <matt@conundrum.com>
Date: Sun, 01 Apr 2018 17:51:49 -0400
Message-ID: <CAAiTEH8FYHuLQ5wEO9kV0Et4S48TG+UW2RAUEu=cFowkm7mwCA@mail.gmail.com>
To: bert hubert <bert.hubert@powerdns.com>
Cc: Mukund Sivaraman <muks@isc.org>, Tim Wicinski <tjw.ietf@gmail.com>, Ondřej Surý <ondrej@isc.org>, Suzanne Woolf <suzworldwide@gmail.com>, Paul Vixie <paul@redbarn.org>, dnsop <dnsop@ietf.org>
Content-Type: multipart/alternative; boundary="089e08e55d1f0bf1010568d07b53"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/yr3In3wSe30cvgyXUvPYHdqWtQQ>
Subject: Re: [DNSOP] Current DNS standards, drafts & charter
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
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: Sun, 01 Apr 2018 21:51:54 -0000

On 31 March 2018 at 17:34, bert hubert <bert.hubert@powerdns.com> wrote:

> First, I agree it is necessary. I don't think anyone would really disagree.
> The issue is the stupendous amount of work it would be and if we are going
> to do it.
>
> A secondary question is how hard we are going to make this on ourselves if
> we do it. This comprises a number of things: 1) which RFCs would be
> obsoleted
> by the rewrite (2181?)and which ones are we going to leave in place (403x?)
>
> 2) What 'optional' things are we going to move into scope of DNS basics. In
> other words, what will 1034/1035-bis say about DNSSEC?
>
>
> I think that's another question of organization in here too, which is
whether the document is operations or implementation, and if it's
implementation what part of the architecture is being implemented (e.g.
client, server, authority, recursion, ...).

I can't decide whether it makes more sense to split up things like stubs,
full resolvers, or authoritative servers into separate documents, or to try
to describe the whole beast in one document like 1035 did.  But, for the
core, I'm leaning toward the former.