Re: [DNSOP] Fwd: New Version Notification for draft-bellis-dnsop-edns-tags-00.txt

Ray Bellis <> Tue, 05 March 2019 08:13 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 4C448130E2B for <>; Tue, 5 Mar 2019 00:13:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_PASS=-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 jRVKvGWgJ_Rw for <>; Tue, 5 Mar 2019 00:13:15 -0800 (PST)
Received: from ( [IPv6:2a03:9800:20:1::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id DD76112958B for <>; Tue, 5 Mar 2019 00:13:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed;; s=dkim; h=Content-Transfer-Encoding:Content-Type:In-Reply-To: MIME-Version:Date:Message-ID:From:References:To:Subject:Sender:Reply-To:Cc: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=g/+dX+rLpK1NbddngaY94z23EihziG/Jw4h2Ux+90hM=; b=OrlrJUKYo6J6XqSFMgCgk5X6gL DRGwhKWjO06CTljH8UetJ5tdE7kl4epddeaIFKtY4tQNJ1hgo4n78n0hA9U29rfUeWSoto4l4+sDz m20II9/OCNY0P7AX6KVpNje9eufmtnGR2s5Q/WMZVHLkcHyZGcFLsDCVXvPOUXX4M1/8=;
Received: from ([]:64628 helo=Rays-MacBook-Pro.local) by ([]:465) with esmtpsa ( (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) id 1h15CL-0000N1-0L (Exim 4.89) for (return-path <>); Tue, 05 Mar 2019 08:13:13 +0000
References: <> <> <>
From: Ray Bellis <>
Message-ID: <>
Date: Tue, 5 Mar 2019 08:13:12 +0000
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:60.0) Gecko/20100101 Thunderbird/60.5.1
MIME-Version: 1.0
In-Reply-To: <>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-GB
Content-Transfer-Encoding: 7bit
Archived-At: <>
Subject: Re: [DNSOP] Fwd: New Version Notification for draft-bellis-dnsop-edns-tags-00.txt
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF DNSOP WG mailing list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 05 Mar 2019 08:13:16 -0000

On 04/03/2019 23:03, Wes Hardaker wrote:

> Hmmm..  very interesting idea, but I'm having a hard time seeing how
> this will be used in the real world in a scalable and interoperable
> way.

The use cases on the open internet are probably less interesting than 
those were client and server have a more tightly coupled relationship.

> The problem with a generic mechanism like this for DNS is that the
> number of clients per server are potentially gigantic.  And there is
> often not a documented relationship or even a known contact mechanism to
> signal changes taking place.  This all makes communication of agreed
> upon semantics of bits not exactly impossible, but likely between
> difficult to extremely difficult.  And misconfiguration could be
> potentially be dangerous, depending on the meaning of the bits.  Imagine
> if the new bit for some flipped software suddenly switched to "I trust
> MD5, go ahead and believe MD5 DS records".

I suggest that I add a sentence or two about applicability, constraining 
it to those where the client has tight coupling (be that topologically 
or contractually) to a particular set of servers.