Re: [DNSOP] new DNS classes

Nico Williams <nico@cryptonector.com> Fri, 07 July 2017 16:37 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 E1F701316C5; Fri, 7 Jul 2017 09:37:43 -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 HhRSBEW36Ft3; Fri, 7 Jul 2017 09:37:42 -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 7FF71129AAA; Fri, 7 Jul 2017 09:37:42 -0700 (PDT)
Received: from homiemail-a35.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a35.g.dreamhost.com (Postfix) with ESMTP id 1F6DFC086D0C; Fri, 7 Jul 2017 09:37:42 -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=HfHTLw0Xajipqk WJUexbsofUDl0=; b=PMiMCnU69GThxmor1AE0iVA1ZJxwy5r7p4Y0jfKYDBeLLB 71Smoj2jKXwBC1sBsLPNUcSt1cuDzJ3d90cJI6thaiQXsNwni0f3/04lzhWXxbDF sKgi3SLRBzh6n3DSexbKC3sj0ldJC9bwlwzA8lK7GpentsljmS7Imu1Ris4zw=
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 5BC08C086D08; Fri, 7 Jul 2017 09:37:41 -0700 (PDT)
Date: Fri, 7 Jul 2017 11:37:39 -0500
From: Nico Williams <nico@cryptonector.com>
To: Paul Vixie <paul@redbarn.org>
Cc: Mark Andrews <marka@isc.org>, John C Klensin <john-ietf@jck.com>, dnsop <dnsop@ietf.org>, Phillip Hallam-Baker <phill@hallambaker.com>, IETF Rinse Repeat <ietf@ietf.org>
Message-ID: <20170707163738.GE3393@localhost>
References: <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> <20170707055315.GC3393@localhost> <595FA42A.7050604@redbarn.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <595FA42A.7050604@redbarn.org>
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/F6F4B2005mZUdNpxiqxXLXYvMjs>
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 16:37:44 -0000

On Fri, Jul 07, 2017 at 08:09:30AM -0700, Paul Vixie wrote:
> Nico Williams wrote:
> >...
> >
> >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.
> 
> that would be a prior restraint, and bad for innovation. just like middle
> boxes or the nearly universal assumption that ip means tcp or udp. i know
> this kind of thinking is common. but there is a stark choice for all of us:
> do all of our future protocol work on tcp/80 and make everything fit in
> JSON, so that we can get our work done; or keep doing what the internet used
> to mean, and eventually put enough stress on middle box makers, isp's, and
> in your case dns hosting services, that they have to learn about the
> internet rather than just the web.
> 
> i know which future i'd rather live in. i also feel in-year pressure to get
> my work done. i vacillate as to who gets to receive which burdens.

I'm with you on this.  I badly want to be able to use new RR types
without further ado.  I would prefer to push on the middleboxes and
middlepeople -- but we need to do a better job of this altogether so
that we don't have to wait a decade.  We don't have a spec police, so
all we can do is nag.

Nico
--