Re: new DNS classes

Pete Resnick <> Fri, 07 July 2017 18:41 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id F07BA128DE5; Fri, 7 Jul 2017 11:41:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.001
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: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id yu3pa78foC8V; Fri, 7 Jul 2017 11:41:28 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 290FA126C0F; Fri, 7 Jul 2017 11:41:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple;;; 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 (HELO ([]) by 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 ([]) by with ESMTP/TLS/RC4-SHA; 07 Jul 2017 11:41:27 -0700
Received: from [] ( by ( with Microsoft SMTP Server (TLS) id 15.0.1178.4; Fri, 7 Jul 2017 11:41:26 -0700
From: Pete Resnick <>
To: Mark Andrews <>
CC: Nico Williams <>, John C Klensin <>, dnsop <>, Phillip Hallam-Baker <>, Paul Vixie <>, IETF <>
Subject: Re: new DNS classes
Date: Fri, 7 Jul 2017 13:41:24 -0500
Message-ID: <>
In-Reply-To: <>
References: <> <> <> <> <> <> <> <> <> <562EC659F89FA92A09CAC4DB@PSB> <20170706153955.GB3393@localhost> <>
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; markup=markdown
X-Mailer: MailMate (1.9.6r5347)
X-Originating-IP: []
X-ClientProxiedBy: ( To (
Archived-At: <>
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-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.

Pete Resnick <>
Qualcomm Technologies, Inc. - +1 (858)651-4478