IETF Logo Mail Archive

Re: [DNSOP] raising the bar: requiring implementations

Mukund Sivaraman <muks@isc.org> Wed, 28 March 2018 20:02 UTC

Return-Path: <muks@isc.org>
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 88ACC126DC2 for <dnsop@ietfa.amsl.com>; Wed, 28 Mar 2018 13:02:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level:
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=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 nqIp7NA45GS9 for <dnsop@ietfa.amsl.com>; Wed, 28 Mar 2018 13:02:28 -0700 (PDT)
Received: from mail.banu.com (mail.banu.com [IPv6:2a01:4f8:140:644b::225]) by ietfa.amsl.com (Postfix) with ESMTP id 63AF6120227 for <dnsop@ietf.org>; Wed, 28 Mar 2018 13:02:28 -0700 (PDT)
Received: from jurassic (unknown [49.203.219.212]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.banu.com (Postfix) with ESMTPSA id B6E8D32C0A4F; Wed, 28 Mar 2018 20:02:26 +0000 (UTC)
Date: Thu, 29 Mar 2018 01:32:23 +0530
From: Mukund Sivaraman <muks@isc.org>
To: Matthijs Mekking <matthijs@pletterpet.nl>
Cc: dnsop@ietf.org
Message-ID: <20180328200223.GA14777@jurassic>
References: <20180324110756.GE69302@vurt.meerval.net> <9a03dbfb-a4c7-9ca2-22c4-d00a0d0d0223@nlnetlabs.nl> <CADyWQ+G7oR5M9pHgj5Ty+4yL1nsep2mpujLiE7nf__kVmN13fQ@mail.gmail.com> <20180328151939.GA19504@jurassic> <a1a97166-453f-08bb-72d4-120012bfa6bd@pletterpet.nl>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <a1a97166-453f-08bb-72d4-120012bfa6bd@pletterpet.nl>
User-Agent: Mutt/1.9.2 (2017-12-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/2-p1atN1h6GAfyEqjZKiPfgP7LI>
Subject: Re: [DNSOP] raising the bar: requiring implementations
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, 28 Mar 2018 20:02:29 -0000

Also, this "Camel" in the presentation may have been a mythological
beast, but the real and existing DNS Camels that struggle with their
backs breaking under the weight of DNS are the DNS implementations,
especially the open source ones that are underfunded and understaffed.

If someone wants to add more weight on top, do so by helping by
implementing it for one or more of the majorly used open source
implementations. I can't agree that a closed-source or an example
implementation of itself will suffice, when the burden eventually comes
onto us.

Other than that, the "Camel" that everyone feels sorry for doesn't
exist.

		Mukund

v2.23.0 | Report a Bug | By Email