Re: [dnsext] getting TLDs to fix other people's problems

Patrik Fältström <paf@frobbit.se> Sun, 21 December 2014 05:34 UTC

Return-Path: <paf@frobbit.se>
X-Original-To: dnsext@ietfa.amsl.com
Delivered-To: dnsext@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 902FD1A0161 for <dnsext@ietfa.amsl.com>; Sat, 20 Dec 2014 21:34:08 -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 kXrI-ITe8HSR for <dnsext@ietfa.amsl.com>; Sat, 20 Dec 2014 21:34:07 -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 EB09D1A015F for <dnsext@ietf.org>; Sat, 20 Dec 2014 21:34:06 -0800 (PST)
Received: from [IPv6:2a02:80:3ffc::b0a7:8760:fd77:de4d] (unknown [IPv6:2a02:80:3ffc:0:b0a7:8760:fd77:de4d]) by mail.frobbit.se (Postfix) with ESMTPSA id 20520205BC; Sun, 21 Dec 2014 06:34:03 +0100 (CET)
Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\))
Content-Type: multipart/signed; boundary="Apple-Mail=_7B804A95-CD46-4E34-8FC8-AA3C06756B15"; protocol="application/pgp-signature"; micalg="pgp-sha1"
X-Pgp-Agent: GPGMail 2.5b3
From: Patrik Fältström <paf@frobbit.se>
In-Reply-To: <7A31183A-CC1E-4F0A-A2EA-848B10B60A2B@insensate.co.uk>
Date: Sun, 21 Dec 2014 06:34:02 +0100
Message-Id: <E732A2F7-E467-4940-8A66-726FC894B4B3@frobbit.se>
References: <20141220125805.GB20765@xs.powerdns.com> <20141220142506.C7EA12630502@rock.dv.isc.org> <A78F8417-AEA2-42BF-A7D5-96FE99DCBBBE@rfc1035.com> <20141220204337.4F47026313BC@rock.dv.isc.org> <7A31183A-CC1E-4F0A-A2EA-848B10B60A2B@insensate.co.uk>
To: Lawrence Conroy <lconroy@insensate.co.uk>
X-Mailer: Apple Mail (2.1993)
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsext/l7B2l7vMFaK2NAOKgrWhjId7__o
Cc: bert hubert <bert.hubert@netherlabs.nl>, DNSEXT Group Working <dnsext@ietf.org>
Subject: Re: [dnsext] getting TLDs to fix other people's problems
X-BeenThere: dnsext@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DNS Extensions working group discussion list <dnsext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsext>, <mailto:dnsext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsext/>
List-Post: <mailto:dnsext@ietf.org>
List-Help: <mailto:dnsext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsext>, <mailto:dnsext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 21 Dec 2014 05:34:08 -0000

A few examples of where the world is from my perspective:

As long as...

- ...policy in some registries require NS records for registrations of a domain (i.e. no difference between registration and delegation), there will be lame delegations

- ...policy in some registries require NS records for registrations of a domain (i.e. no difference between registration and delegation), there will be proxy registrations and registrants that lie

- ...data sent to a registry/registrar, regardless of data protection legislation, is available freely "on the net", there will be proxy registrations and registrants that lie

- ...policy make it impossible to register domain names in some registries, there will be proxy registrations to circumvent the very same rules

- ...there is no agreement on what data to send to registries for DNSSEC signed zones, it will be very hard to get lots of DNSSEC signed zones

- ...policy in some registries that the registrant should contact them directly, registrars will lie to the registry during registration period so that they can give the registrant the service the registrant ask for

I.e. the world out there is so messy that what you talk about is a light warm breeze...

Just the notation of "the TLDs" to fix things is confusing to me. Does "the TLD" imply the registry, whoever is the administrative contact for the TLD in the IANA database, or the backend provider, or the technical contact or the one holding the whois record of the delegation the question is about, or...

   Patrik