[DNSOP] Complexity and innovation in the DNS protocol: the work of DNSOP

Suzanne Woolf <suzworldwide@gmail.com> Wed, 18 April 2018 21:07 UTC

Return-Path: <suzworldwide@gmail.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 5A1FE126CD6 for <dnsop@ietfa.amsl.com>; Wed, 18 Apr 2018 14:07:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 2EEGVpCpslxe for <dnsop@ietfa.amsl.com>; Wed, 18 Apr 2018 14:07:28 -0700 (PDT)
Received: from mail-ot0-x230.google.com (mail-ot0-x230.google.com [IPv6:2607:f8b0:4003:c0f::230]) (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 05206126C3D for <dnsop@ietf.org>; Wed, 18 Apr 2018 14:07:28 -0700 (PDT)
Received: by mail-ot0-x230.google.com with SMTP id p33-v6so3512230otp.11 for <dnsop@ietf.org>; Wed, 18 Apr 2018 14:07:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:content-transfer-encoding:mime-version:subject:message-id:date :to; bh=+C8U6GqUOhv7PXf7gWUPP7G2rruX4xAe00G2cn3Cq+8=; b=PF9q+n2fqAMebS/FcNJa4JzyO6JcpZD907Ku9DqEPWvhdGSpkA77+qkNWYmN1ttXq9 LOtdElWi4rR1UyAKeJ501iUB55CT8oPM71LsiBguSV0s/qKnrtNZ/pz+yKNKWLrp7oLC N7+LzKJg/J6Ai7Ja26KzNXMkiVAfBSihs4MJd2bvEK5cCV9afYbb0IltPu/nSfDyIvaX NRTj/b7Fdbx7ILgEnhzISKK1G1UmC6IZqAZMYOjAkvPI4cOyMqqOLixMuapYoVgQ3CWz 5olqxmJ5N8FReoptM3+kREaFuP+2OxY6c4m7lDQ9h1BT012BXSe1unSLRy8X8QEUr/OC 7kuw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:content-transfer-encoding:mime-version :subject:message-id:date:to; bh=+C8U6GqUOhv7PXf7gWUPP7G2rruX4xAe00G2cn3Cq+8=; b=pFE2fvFMRJWkvd4PlZmQRwgfHDARHaK2XutNjgpnEC8/lCNAXUs4dnLUIlfx4fcIBv fK6SUvKQJ8DIgZ4MurGh0MqBLE/Llxnc/JPg5J4mqUoP+vCbSNlhWMIvzpOKKKaSmODL w+7pKpwcsZvmPoe7mTntREQQjO+QdNHJ28wqUqAv50IzlmnmJUBeEmXt0kkazzPythhN +c6YaPidQepU2fKgvzmYTH0C9N/FUBgnq/60qdhtko4mCMIBrQ47A33qrDOKuUCH79G8 JV3zf4odB6l86L3rf6XYM/5s5GYxY2A1AnGczPeysPJBrdI4Hw35B3I+N49Thqku6TOe QlPA==
X-Gm-Message-State: ALQs6tCm1RQy1tA1fAyslKKlPBhex4UxEp4ncph7voeloSs7QA6dP61O 12a6xaq4lLZh9AC9oeX8OtK/IA2I
X-Google-Smtp-Source: AIpwx48yE90byqdPTo7iOiNHbNLu2VyBH0HMNqqbNQZY0BqghSRdXwC+DCR8KL8QTRHQv7a3eT3pHg==
X-Received: by 2002:a9d:24a3:: with SMTP id z32-v6mr2472905ota.331.1524085647347; Wed, 18 Apr 2018 14:07:27 -0700 (PDT)
Received: from [172.16.27.105] (wsip-70-168-129-6.dc.dc.cox.net. [70.168.129.6]) by smtp.gmail.com with ESMTPSA id 5-v6sm1094794ote.77.2018.04.18.14.07.24 for <dnsop@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 18 Apr 2018 14:07:25 -0700 (PDT)
From: Suzanne Woolf <suzworldwide@gmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 11.3 \(3445.6.18\))
Message-Id: <F3A3177D-318B-478F-9E0B-19EA072BE667@gmail.com>
Date: Wed, 18 Apr 2018 17:07:23 -0400
To: dnsop <dnsop@ietf.org>
X-Mailer: Apple Mail (2.3445.6.18)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/gQ0qju2MPDBz4R5KkRYMKL_ioeg>
Subject: [DNSOP] Complexity and innovation in the DNS protocol: the work of DNSOP
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: Wed, 18 Apr 2018 21:07:29 -0000

Hi,

The chairs have been discussing next steps after IETF 101, particularly the very lively WG input on the complexity and stability of the DNS protocol.

There are many aspects to the questions that came up. Some are not going to be resolved within the IETF or the standards process, but it sounds to us like there are things the IETF and DNSOP can do that could improve the situation.

We heard significant support in the WG for slowing down on adoption of new work, with more attention by the chairs and in WG discussion for a couple of factors:

First, what's the applicability of this work? what problem does it solve, and for whom?

Second, does this work add significantly to the complexity of the DNS protocol, or the work of implementers and operators?

Finally, what implementation experience exists with the technology?

We're not trying to create unnecessary barriers to new work; previous generations of DNS working groups have arguably tried to preserve stability of the protocol at the expense of innovation, with the result that people simply proceeded to innovate outside of the standards process.

However, we want to see these issues discussed as part of WG consideration for adoption of new work in the future, and will explicitly consider them when deciding whether new work has adequate support to advance in the working group.



Best,
Suzanne, Tim, and Benno