Re: [DNSOP] new DNS classes

Pete Resnick <presnick@qti.qualcomm.com> Fri, 07 July 2017 18:41 UTC

Return-Path: <presnick@qti.qualcomm.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 F07BA128DE5; Fri, 7 Jul 2017 11:41:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=qti.qualcomm.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 yu3pa78foC8V; Fri, 7 Jul 2017 11:41:28 -0700 (PDT)
Received: from alexa-out-lv-02.qualcomm.com (alexa-out.qualcomm.com [129.46.98.28]) (using TLSv1.2 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 290FA126C0F; Fri, 7 Jul 2017 11:41:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1499452888; x=1530988888; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version; bh=FZElHdLr959RonMfR2E+2l2LoxaJjUcPuAQDhl3jHWM=; b=K4W6K2ReEEHrk3gEgBZRPMoQyMjE6lIa1HXVmGMtCzV9QpeKRSMipWJL kT/J6XsqhH46hapOR0PXKdywJPlwP8N9+GTUx6mJ4zcBuu9QNvCSW9CTn PYNKmNA7DJXmiFjfE3wgYEanjZ9gKL96MHW4FsQDttdpqKPRhWbVBEkuh 0=;
X-IronPort-AV: E=Sophos;i="5.40,324,1496127600"; d="scan'208";a="454653"
Received: from ironmsg04-l-new.qualcomm.com (HELO Ironmsg04-L.qualcomm.com) ([10.53.140.111]) by alexa-out-lv-02.qualcomm.com with ESMTP; 07 Jul 2017 11:41:27 -0700
X-IronPort-AV: E=McAfee;i="5800,7501,8584"; a="1383125604"
X-MGA-submission: =?us-ascii?q?MDHtIBtne2XriEwECItyfgLXlYN6Ix2vXEmlF5?= =?us-ascii?q?JDfRquCNHVkGgI6roXfKQLIoaixN0pw9hu8o/3Ao4U8qyqQvyma2/nTt?= =?us-ascii?q?Y9C0yfYygSrb6QpfvMYFb0PdKxiMLWGJadH5WvPR57sG+uaSdsGUo3GK?= =?us-ascii?q?be?=
Received: from nasanexm01f.na.qualcomm.com ([10.85.0.32]) by Ironmsg04-L.qualcomm.com with ESMTP/TLS/RC4-SHA; 07 Jul 2017 11:41:27 -0700
Received: from [10.64.110.227] (10.80.80.8) by NASANEXM01F.na.qualcomm.com (10.85.0.32) with Microsoft SMTP Server (TLS) id 15.0.1178.4; Fri, 7 Jul 2017 11:41:26 -0700
From: Pete Resnick <presnick@qti.qualcomm.com>
To: Mark Andrews <marka@isc.org>
CC: Nico Williams <nico@cryptonector.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>
Date: Fri, 7 Jul 2017 13:41:24 -0500
Message-ID: <A94C17CD-DC4B-43C9-AD3D-69735FC6B2BC@qti.qualcomm.com>
In-Reply-To: <20170706215236.99A8C7DB2FBA@rock.dv.isc.org>
References: <m2podgxq97.wl-randy@psg.com> <5F120298-CD66-4CB6-9DC5-0C5DF6F02CC7@fugue.com> <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; format=flowed; markup=markdown
X-Mailer: MailMate (1.9.6r5347)
X-Originating-IP: [10.80.80.8]
X-ClientProxiedBy: NASANEXM01B.na.qualcomm.com (10.85.0.82) To NASANEXM01F.na.qualcomm.com (10.85.0.32)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/I8xR1V9jiUytHLBppn-h1eXtp7U>
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 18:41:30 -0000

[Apologies for the re-send. Using the correct address.]

On 6 Jul 2017, at 16:52, Mark Andrews wrote:

> 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 running the latest version of MacOS Server. I can't get a new RR 
type into the UI. Even if I use the command line "dnsconfig" tool, I 
can't add a record of a type it doesn't know about; I only get A, AAAA, 
CNAME, NS, MX, PTR, SRV, and TXT. Yes, I could go hacking around in the 
BIND configs that underly their implementation. And at that point I say, 
"New RR types are hard to deploy; not a myth." Telling me I can use a 
different operating system or not use a validating UI is not a 
reasonable response.

The fact is the DNS doesn't provide a way for implementations to 
dynamically update the RR types to provide sensible UI; it's left as an 
exercise for each individual implementer. (Yes, I know about 
draft-levine-dnsextlang; it doesn't seem to have gotten anywhere.) You 
can't much complain about the difficulty of deployment when the 
community won't provide the tools to make deployment easier.

pr
-- 
Pete Resnick <http://www.qualcomm.com/~presnick/>
Qualcomm Technologies, Inc. - +1 (858)651-4478