Re: [DNSOP] Fwd: New Version Notification for draft-bellis-dnsext-multi-qtypes-04.txt

Tim Wicinski <> Tue, 04 July 2017 10:40 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 34D12131DEA for <>; Tue, 4 Jul 2017 03:40:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id kfOQsMl7h71Z for <>; Tue, 4 Jul 2017 03:40:24 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:4001:c0b::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 7F0A6131DE5 for <>; Tue, 4 Jul 2017 03:40:24 -0700 (PDT)
Received: by with SMTP id m68so99508476ith.1 for <>; Tue, 04 Jul 2017 03:40:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=/bdbJIUTWzCU6dClwKu3rcv3HHTyXlXcLheHNmXqoI4=; b=JJnTbmcY+M9WrpPpF+PtXzM8M5RS2eo9LVeHa8WdiZL7hBLmOncxyi6E40wQ/SiHgm yNgKx5R8FkJhT62ffpW29lfzGuR28M2sVbqi/1Mkh74hTNRGnPpxZxR0QDvxRZ8hQaFD OGysPbIiZs9idsGxCwkyM3EvdeEMJF7oJoFWHOGT6fbi0ah8dug4dNk/7JDHLg2lsRT/ +RQ0S56bH0Q+MtBL9b8aCX2P1Nna+GFVjN71ro3aqQHmy9mTB1KqRaTomfcm/ekM/DSl WLE+a88ArvYIz+O4VMPL9yMmJBWQtk+qCdrYo2WyG2phblNY+BIQVKm3sVidemIN0OMl NxCw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=/bdbJIUTWzCU6dClwKu3rcv3HHTyXlXcLheHNmXqoI4=; b=npXdbAPsSliqlQq9z4SmOpnZAnQXZDcIOANaMKJKs81opLd/p1Azh0pMXTBZnTY0PC 1ACqHoyVlc1DOthXNgIRFZDH5Cd0YxXFwhczGFc7kPfJbfNB38ye7ipIa6nMa/GESCVs C3u59twUI3bA0V0VYSF9AObdXdjhmY0jYNgr+PJKqMr/jvJDJF0o1adFjbcbwPlvYEaY E65nXqmqKdyYoEFbCfgb/CsbTz4sph3JlvyCa5/jXSHNYb6yP6qnq59jLCm8lLbzTZlj Bc91gS85JoscjhrDejiPKv8JOTipcxIftK8eRZGuHcoi0oRaTgXR2Az9tpFFVIc5stYf 7rLg==
X-Gm-Message-State: AKS2vOxILyEbjOn2yvbxSIl3isqToaiqdsG5aSi1iRhFs1s+Y4UJIpz5 UWWKA9Jq3ffbnDHropo=
X-Received: by with SMTP id y193mr34986496itc.111.1499164823639; Tue, 04 Jul 2017 03:40:23 -0700 (PDT)
Received: from ([]) by with ESMTPSA id t5sm4117318ita.22.2017. for <> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 04 Jul 2017 03:40:22 -0700 (PDT)
References: <> <> <> <>
From: Tim Wicinski <>
Message-ID: <>
Date: Tue, 04 Jul 2017 06:40:21 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <>
Subject: Re: [DNSOP] Fwd: New Version Notification for draft-bellis-dnsext-multi-qtypes-04.txt
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 04 Jul 2017 10:40:26 -0000

On 7/4/17 6:13 AM, Paul Wouters wrote:
> On Mon, 3 Jul 2017, Dave Lawrence wrote:
>>> This is just a "keep alive" so as to keep this draft in consideration as
>>> one of the multiple solutions in this problem space while DNSOP decides
>>> whether this is a problem worth solving.
>>> I still think it's the most elegant of those proposed ;-)
>> I whole-heartedly agree, as Ray's idea was the basic conclusion I'd
>> arrived at independently.
> I agree.

I remember we discussed the various drafts in a meeting (city of which 
escapes me) and the sense of the people in the room, and the folks I 
talked to afterward was that the preference was for a client to *ask* 
for extra things, rather than the server *forcing* extra answers back.

I think Ray's qtype draft fits this.   The chairs should finally discuss 
having a Call for Adoption on this after we've heard the updates

> And I think any ANAME/ALIAS record should be used in combination with
> these, and of itself not define any new special handling.

Well that's an interesting way to approach it.

> Although, we should also be a bit careful not to create a new ANY type
> query that will get abused for amplification, so it should really all
> have source verified IP transports (DNS-COOKIES, TCP, etc)

The is good guidance, and some wording like this would be useful in the 
qtypes draft.

> Another issue to look at is returning any prefix special records,
> such as TLSA records which do not match the QNAME, but are strongly
> related to the QNAME and would benefit from being returned along.

Excellent idea.  One reason we know why SRV records are not used by many 
is no one wants to do additional lookups.