Re: [DNSOP] new DNS classes

Nico Williams <nico@cryptonector.com> Sun, 09 July 2017 05:55 UTC

Return-Path: <nico@cryptonector.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 94F4F127698; Sat, 8 Jul 2017 22:55:32 -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, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cryptonector.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 qZBJ-rlU7iXB; Sat, 8 Jul 2017 22:55:31 -0700 (PDT)
Received: from homiemail-a35.g.dreamhost.com (sub4.mail.dreamhost.com [69.163.253.135]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7E9AE12741D; Sat, 8 Jul 2017 22:55:31 -0700 (PDT)
Received: from homiemail-a35.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a35.g.dreamhost.com (Postfix) with ESMTP id EFA78C086D20; Sat, 8 Jul 2017 22:55:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h=date :from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=cryptonector.com; bh=AD4NqTP0FFpFpi MtB9fcXamVPaM=; b=cDpIN+rezwd/nhsuPUJEm/fOZUbVtbOYdeIsOo7EsGuZRg EaK0zDHptTqlnHJtGBuS1BtKWOUuHQ3i7LJVaiToXF+APELpxcRCZYAoF4PNHdl6 CD7ZQV+N3UjVyrxvlftYgqR/2UJtp6TK+ij5ITYkOrbJerDavJBj/cwu4sfJI=
Received: from localhost (cpe-70-123-158-140.austin.res.rr.com [70.123.158.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a35.g.dreamhost.com (Postfix) with ESMTPSA id 4C8B0C086D0C; Sat, 8 Jul 2017 22:55:30 -0700 (PDT)
Date: Sun, 9 Jul 2017 00:55:27 -0500
From: Nico Williams <nico@cryptonector.com>
To: Mark Andrews <marka@isc.org>
Cc: Pete Resnick <presnick@qti.qualcomm.com>, John C Klensin <john-ietf@jck.com>, dnsop <dnsop@ietf.org>, Phillip Hallam-Baker <phill@hallambaker.com>, Paul Vixie <paul@redbarn.org>, IETF <ietf@ietf.org>
Message-ID: <20170709055526.GI3393@localhost>
References: <7DCA3DAF1993A2E66915D0DD@JcK-HP5.jck.com> <595BE0D5.5000106@redbarn.org> <CAMm+Lwjd6xVp-EDp=doevx=AP8qws_Mv++aL733yHEyUF72EMA@mail.gmail.com> <562EC659F89FA92A09CAC4DB@PSB> <20170706153955.GB3393@localhost> <20170706215236.99A8C7DB2FBA@rock.dv.isc.org> <A94C17CD-DC4B-43C9-AD3D-69735FC6B2BC@qti.qualcomm.com> <20170708001825.2FB117DFD520@rock.dv.isc.org> <EDFEF9A1-99CF-4F25-9C1C-051E78949967@qti.qualcomm.com> <20170709015851.E5C877E07ADA@rock.dv.isc.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20170709015851.E5C877E07ADA@rock.dv.isc.org>
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/Qu-UPzgZL9OwHNQSPQS_-8w6tMc>
Subject: Re: [DNSOP] new DNS classes
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: Sun, 09 Jul 2017 05:55:33 -0000

On Sun, Jul 09, 2017 at 11:58:51AM +1000, Mark Andrews wrote:
> One can do something similar in any scripting language.

Sure.  The people on this list can, and many others too.  Still, all of
us together are a tiny proportion of the users that would need to be
able to.

> So no it isn't hard to use a new type.  You just need to stop waiting
> for the stupid DNS hoster to do it for you and organise to do it
> yourself.

Stop.  Don't tell us.  Don't tell the customers.  Start writing emails
and making calls to hosting providers instead; get them to fix their
crap.  Make, publish, and keep up to date a list of viable providers.

Nico
--