Re: [DNSOP] Fwd: New Version Notification for draft-bellis-dnsop-xpf-04.txt

Ray Bellis <ray@bellis.me.uk> Thu, 15 March 2018 10:41 UTC

Return-Path: <ray@bellis.me.uk>
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 80D531270AB for <dnsop@ietfa.amsl.com>; Thu, 15 Mar 2018 03:41:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 TLSyQLhqgT7l for <dnsop@ietfa.amsl.com>; Thu, 15 Mar 2018 03:41:29 -0700 (PDT)
Received: from hydrogen.portfast.net (hydrogen.portfast.net [188.246.200.2]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7A2F71270A0 for <dnsop@ietf.org>; Thu, 15 Mar 2018 03:41:29 -0700 (PDT)
Received: from [88.212.170.147] (port=59574 helo=rays-mbp.local) by hydrogen.portfast.net ([188.246.200.2]:465) with esmtpsa (fixed_plain:ray@bellis.me.uk) (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) id 1ewQK7-0003xp-FA (Exim 4.72) for dnsop@ietf.org (return-path <ray@bellis.me.uk>); Thu, 15 Mar 2018 10:41:27 +0000
To: dnsop@ietf.org
References: <152026531853.14559.3697718467935375329.idtracker@ietfa.amsl.com> <284032BE-285A-499D-906C-9C24E5901B25@powerdns.com> <alpine.LRH.2.21.1803141744550.16094@bofh.nohats.ca> <a68742d6-b8fe-df3a-0a9c-675967a14b4d@bellis.me.uk>
From: Ray Bellis <ray@bellis.me.uk>
Message-ID: <6eba7e54-468b-eae0-49c1-e60e48e00aa5@bellis.me.uk>
Date: Thu, 15 Mar 2018 10:41:28 +0000
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <a68742d6-b8fe-df3a-0a9c-675967a14b4d@bellis.me.uk>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/9Qf5FXHlFS3zfrefbO5B94XlXnk>
Subject: Re: [DNSOP] Fwd: New Version Notification for draft-bellis-dnsop-xpf-04.txt
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: Thu, 15 Mar 2018 10:41:30 -0000


On 15/03/2018 10:01, Ray Bellis wrote:
> 
> On 14/03/2018 22:07, Paul Wouters wrote:
> 
>> It could mention DNS-COOKIES as one way to avoid spoofing issues.
> 
> That sounds like a good idea.

On reflection (and discussion with one of my co-authors) we think that
would be problematic.

Don't forget that the issue here is non-spoofability of the internal
channel _between the front-end forwarder and the back-end server_, and
not end-to-end.

Using DNS Cookies there would require manipulation of the packet
contents of exactly the sort that earlier versions of this draft had
when it used EDNS instead of a meta-RR.

Ray