Re: [DNSOP] Asking TLD's to perform checks.

"Patrik Fältström " <paf@frobbit.se> Wed, 11 November 2015 06:25 UTC

Return-Path: <paf@frobbit.se>
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 9FC4F1B29AA for <dnsop@ietfa.amsl.com>; Tue, 10 Nov 2015 22:25:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.961
X-Spam-Level:
X-Spam-Status: No, score=-1.961 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 kMHaSCHVLRBB for <dnsop@ietfa.amsl.com>; Tue, 10 Nov 2015 22:25:43 -0800 (PST)
Received: from mail.frobbit.se (mail.frobbit.se [85.30.129.185]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 354CE1B29DF for <dnsop@ietf.org>; Tue, 10 Nov 2015 22:25:43 -0800 (PST)
Received: from [10.0.1.143] (unknown [31.15.50.130]) by mail.frobbit.se (Postfix) with ESMTPSA id B531F1FEAD; Wed, 11 Nov 2015 07:25:40 +0100 (CET)
From: Patrik Fältström <paf@frobbit.se>
To: Jim Reid <jim@rfc1035.com>
Date: Wed, 11 Nov 2015 07:25:39 +0100
Message-ID: <5373DDAB-1ED2-489B-AB62-BA7CF6D3DB48@frobbit.se>
In-Reply-To: <0F2DD78A-69C4-49DA-936F-C32D0FC97CC2@rfc1035.com>
References: <20151105235402.39FFC3BF2F29@rock.dv.isc.org> <20151110152511.6f1a1c20@pallas.home.time-travellers.org> <20151110204330.C47C63C7D699@rock.dv.isc.org> <7B4B7DEA-C705-437E-8BC1-64D96D55014E@vpnc.org> <0F2DD78A-69C4-49DA-936F-C32D0FC97CC2@rfc1035.com>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=_MailMate_2CD09F6D-C252-4CF3-9E2F-9A832F3EBA5A_="; micalg="pgp-sha1"; protocol="application/pgp-signature"
X-Mailer: MailMate (1.9.3r5164)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/18oSgYcT2N08vxh3raHd_RfdPtE>
Cc: dnsop@ietf.org, Paul Hoffman <paul.hoffman@vpnc.org>
Subject: Re: [DNSOP] Asking TLD's to perform checks.
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: Wed, 11 Nov 2015 06:25:44 -0000

On 10 Nov 2015, at 22:24, Jim Reid wrote:

>> Or perhaps we should not.
>
> +1

This discussion on making tests is coming back now and then. In RIPE, in IETF, in discussions around TLDs (specifically ccTLDs).

I have run one such initiative myself.

Everything has so far collapsed into collision between tech people not agreeing on what is right and wrong. It also collapses into clashes between registry policy and the tests made. I.e. just the registration policy is setting blocks and constraints on what tests must be made (or can not be made). And harmonization of such rules is just impossible (we have seen).

That said, initiatives like the one I did run did push errors (for some definition of errors) from 22% to maybe 17% in .SE and my inspection of the rest say that getting errors down to 15% is possible, but more is very hard.

And, having a BCP or such that give suggestions on what can be viewed as "correct" would not be bad, but how to use it must be up to the reader.

I think the IETF should be careful on writing too prescriptive text, I say being one hit by "rfc compliance" people that point at old whois related RFCs that "require" things that in fact is illegal in Sweden. I.e. by being compliant to Swedish law regarding privacy, I violate a very old RFC and because of that I am black listed.

So be careful.

   Patrik