Re: [DNSOP] raising the bar: requiring implementations

Matthijs Mekking <matthijs@pletterpet.nl> Wed, 28 March 2018 15:29 UTC

Return-Path: <matthijs@pletterpet.nl>
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 8E071120047 for <dnsop@ietfa.amsl.com>; Wed, 28 Mar 2018 08:29:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham 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 ZM985P0Qu2Ka for <dnsop@ietfa.amsl.com>; Wed, 28 Mar 2018 08:29:24 -0700 (PDT)
Received: from lb3-smtp-cloud8.xs4all.net (lb3-smtp-cloud8.xs4all.net [194.109.24.29]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 35E051273B1 for <dnsop@ietf.org>; Wed, 28 Mar 2018 08:29:21 -0700 (PDT)
Received: from [IPv6:2001:981:19be:1:a104:4f71:de86:2e0] ([IPv6:2001:981:19be:1:a104:4f71:de86:2e0]) by smtp-cloud8.xs4all.net with ESMTPSA id 1D0ofMW6v4EsM1D0pfI5Yx; Wed, 28 Mar 2018 17:29:19 +0200
To: dnsop@ietf.org
References: <20180324110756.GE69302@vurt.meerval.net> <9a03dbfb-a4c7-9ca2-22c4-d00a0d0d0223@nlnetlabs.nl> <CADyWQ+G7oR5M9pHgj5Ty+4yL1nsep2mpujLiE7nf__kVmN13fQ@mail.gmail.com> <20180328151939.GA19504@jurassic>
From: Matthijs Mekking <matthijs@pletterpet.nl>
Message-ID: <a1a97166-453f-08bb-72d4-120012bfa6bd@pletterpet.nl>
Date: Wed, 28 Mar 2018 17:29:18 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <20180328151939.GA19504@jurassic>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-CMAE-Envelope: MS4wfAtFan2xQd8DuRWTIWXgYh8Sfm1SsJ80JP2GBRYnJwuAUFDBxQylj8473uoM1MYupCoEFeugrH9BaMJJu8XlJG/GjKSur2ei+hYAFKvmmbI8Eqw1KZcH Ndf2kUGwVzYo0XBBs8izVtyOJnjwghZkgwFUcmU5DoYAy7JtI2WngYqb+2iMmYv3gT2q0I/e0FSQxH45lAcG96DCYZ1tf63oxwdBsQNete3QK8hCCRh470L8 IJA62DW0gfu/o9ZM5bcbP871GqKV/eHCqJFg7sVxt4A=
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/KJxrY-FNPaE41te9kjzJxSDiBuo>
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 15:29:26 -0000


On 03/28/2018 05:19 PM, Mukund Sivaraman wrote:
> On Wed, Mar 28, 2018 at 10:55:13AM -0400, tjw ietf wrote:
>> I would say that most things we have adopted in the past few years do have
>> some implementations to reference.
>> Not when drafts are adopted, but generally before we head to WGLC I've
>> always wanted to see someone
>> who implemented the option in some manner.
>>
>> But yes, agree.
> 
> I'd raise the bar even higher, to see complete implementation in a major
> open source DNS implementation when it applies. Sometimes implementation
> problems are very revealing (client-subnet should have gone through
> this).

As mentioned in the meeting, I am in favor of requiring implementations 
before drafts become standards.

However, I would be opposed to limit acceptable implementations to the 
few major open source DNS implementations (define major). It should be 
acceptable for other organizations or just persons to contribute a 
reference implementation.

Best regards,

Matthijs



> 
> 		Mukund
> 
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop
>