Re: [DNSOP] I-D Action: draft-lee-dnsop-recursion-performance-improvement-00.txt

Mark Andrews <marka@isc.org> Fri, 11 December 2015 23:15 UTC

Return-Path: <marka@isc.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1CC751A0115; Fri, 11 Dec 2015 15:15:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.911
X-Spam-Level:
X-Spam-Status: No, score=-6.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 GNNLCEA2joYW; Fri, 11 Dec 2015 15:15:40 -0800 (PST)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [199.6.1.65]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B416A1A0098; Fri, 11 Dec 2015 15:15:37 -0800 (PST)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx.ams1.isc.org (Postfix) with ESMTPS id 74FF51FDAFE; Fri, 11 Dec 2015 23:15:34 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTPS id C01F9160080; Fri, 11 Dec 2015 23:18:11 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id B1DEC16007F; Fri, 11 Dec 2015 23:18:11 +0000 (UTC)
Received: from zmx1.isc.org ([127.0.0.1]) by localhost (zmx1.isc.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id PhzVuV75FoQB; Fri, 11 Dec 2015 23:18:11 +0000 (UTC)
Received: from rock.dv.isc.org (c122-106-161-187.carlnfd1.nsw.optusnet.com.au [122.106.161.187]) by zmx1.isc.org (Postfix) with ESMTPSA id 6CE56160048; Fri, 11 Dec 2015 23:18:11 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id 5C3DE3F3251D; Sat, 12 Dec 2015 10:15:29 +1100 (EST)
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>
From: Mark Andrews <marka@isc.org>
References: <20151211172132.2410.88613.idtracker@ietfa.amsl.com> <20151211173028.GA27573@nic.fr>
In-reply-to: Your message of "Fri, 11 Dec 2015 18:30:28 +0100." <20151211173028.GA27573@nic.fr>
Date: Sat, 12 Dec 2015 10:15:29 +1100
Message-Id: <20151211231529.5C3DE3F3251D@rock.dv.isc.org>
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/4LT0anZ4E0e9ycfhupr0SAsLRDU>
Cc: dnsop@ietf.org, draft-lee-dnsop-recursion-performance-improvement.all@ietf.org
Subject: Re: [DNSOP] I-D Action: draft-lee-dnsop-recursion-performance-improvement-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
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, 11 Dec 2015 23:15:43 -0000

In message <20151211173028.GA27573@nic.fr>, Stephane Bortzmeyer writes:
> On Fri, Dec 11, 2015 at 09:21:32AM -0800,
>  internet-drafts@ietf.org <internet-drafts@ietf.org> wrote 
>  a message of 42 lines which said:
> 
> >         Title           : An approach to improve recursion performance 
> >         Authors         : Xiaodong Lee
> >                           Hongtao Li
> >                           Haikuo Zhang
> >                           Peng Zuo
> > 	Filename        : draft-lee-dnsop-recursion-performance-improvement-00.
> txt
> 
> At the first reading, I do not see the difference between your RQID
> and a cookie, as documented in draft-ietf-dnsop-cookies (currently
> past working group last call and sent to the IESG).

It's half of the client half/part of a cookie.  I would also suggest
not just accepting responses without the option but rather fall back
to port randomisation.

We were planning to switch back to a fixed port.  The only question
was for the first query and retry with a random port if one didn't
get the cookie option in a reply or to only send using the fixed
port when you know that cookies are supported by the server.  The
choice of which strategy to employ is really dependent on the uptake
of cookie support in servers.

At 50%+ deployment the first strategy should give the greatest
benefit.  Before that the second strategy should be the winning
one.

Mark

> If there is a difference, and a reason why you just don't use DNS
> cookies, please document it.
> 
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org