Re: [DNSOP] new DNS classes

Nico Williams <nico@cryptonector.com> Fri, 07 July 2017 05:53 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 E0D0A12EA58; Thu, 6 Jul 2017 22:53:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.3
X-Spam-Level:
X-Spam-Status: No, score=-4.3 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, RCVD_IN_MSPIKE_H2=-2.8, RCVD_IN_SORBS_SPAM=0.5] 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 HMKlTdQ0X7lu; Thu, 6 Jul 2017 22:53:19 -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 A54CE126D45; Thu, 6 Jul 2017 22:53:19 -0700 (PDT)
Received: from homiemail-a35.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a35.g.dreamhost.com (Postfix) with ESMTP id D85E1C0028BA; Thu, 6 Jul 2017 22:53:18 -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=bZLi8BEwlnk1FP hFiOr7zO3DpBw=; b=fFPg68NI3ud7kVns8FcFhb7OE2Ftq7vQ0XvGDu0VKzeUZk jafTDJXtCpE+XrU97pgbbQ5Sy4VmpaMGDmBjXTfX4C6rTCB26tTs817dWksBE/ED PQhJUMePIpzJDY7JDpPTrYGt5R6ndAs31gyAiKnRJKSiDjye0Eq1ML38YEP3g=
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 2DD34C0028B8; Thu, 6 Jul 2017 22:53:18 -0700 (PDT)
Date: Fri, 7 Jul 2017 00:53:16 -0500
From: Nico Williams <nico@cryptonector.com>
To: Mark Andrews <marka@isc.org>
Cc: John C Klensin <john-ietf@jck.com>, dnsop <dnsop@ietf.org>, Phillip Hallam-Baker <phill@hallambaker.com>, Paul Vixie <paul@redbarn.org>, IETF Rinse Repeat <ietf@ietf.org>
Message-ID: <20170707055315.GC3393@localhost>
References: <CACfw2hhx+-Z=7ZnnaOkToc+Bd7aKDpBFt+nFUxkt9sKqLn4D8Q@mail.gmail.com> <2DF1AFC7-643B-4610-8EB8-0616D3D0B024@fugue.com> <595BD53E.60701@redbarn.org> <E739C1CB-E60E-4B4B-99CF-1E6C68CB6926@rfc1035.com> <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>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20170706215236.99A8C7DB2FBA@rock.dv.isc.org>
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/fFx8WKGM6VIvCmtuHy8qaQOKPt0>
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: Fri, 07 Jul 2017 05:53:21 -0000

On Fri, Jul 07, 2017 at 07:52:36AM +1000, Mark Andrews wrote:
> In message <20170706153955.GB3393@localhost>, Nico Williams writes:
> > So new classes will only be useful to extend the IN-class RR type
> > namespace.  We won't get there.  New RR types can be very difficult to
> > deploy due to lack of interest by registrars and domain hosting
> > services.  TXT RRs forever.  :(
> 
> Or you could stop trying to reinforce the myth that new RR types
> are hard to deploy.  They really aren't.  They actually get used
> all the time.

I'm well aware that as to clients and servers, deploying new RR types is
easy.  The hard part is the management backend and UIs.  Not all of them
allow you to enter raw RDATA (hex-encoded or whatever).

We've struggled with this in KITTEN WG.  Deploying the URI RR type when
you're using a hosting service can be anywhere from annoying (must enter
raw RDATA) to impossible (the hosting service doesn't give a damn).  I
suppose it's just a matter of time; perhaps things have improved since
we last looked.

Nico
--