Re: [DNSOP] Review of draft-ietf-dnsop-cookies-00

Mukund Sivaraman <muks@isc.org> Wed, 17 December 2014 01:11 UTC

Return-Path: <muks@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 EB7561A1A32 for <dnsop@ietfa.amsl.com>; Tue, 16 Dec 2014 17:11:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level:
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_SOFTFAIL=0.665] autolearn=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 QtXsJlbM6KXR for <dnsop@ietfa.amsl.com>; Tue, 16 Dec 2014 17:11:53 -0800 (PST)
Received: from mail.banu.com (mail.banu.com [46.4.129.225]) by ietfa.amsl.com (Postfix) with ESMTP id 116B31A1A20 for <dnsop@ietf.org>; Tue, 16 Dec 2014 17:11:53 -0800 (PST)
Received: from totoro.home.mukund.org (unknown [115.118.144.63]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.banu.com (Postfix) with ESMTPSA id 551B0E60035; Wed, 17 Dec 2014 01:11:50 +0000 (GMT)
Date: Wed, 17 Dec 2014 06:41:46 +0530
From: Mukund Sivaraman <muks@isc.org>
To: P Vixie <paul@redbarn.org>
Message-ID: <20141217011146.GB27187@totoro.home.mukund.org>
References: <20141216152511.GA22255@totoro.home.mukund.org> <20141216171318.GA23468@totoro.home.mukund.org> <549069CC.20309@redbarn.org> <20141216174734.GA23740@totoro.home.mukund.org> <5F5DEA8F-6BFE-43C7-AEB8-EA6C9B5C3045@redbarn.org>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="pvezYHf7grwyp3Bc"
Content-Disposition: inline
In-Reply-To: <5F5DEA8F-6BFE-43C7-AEB8-EA6C9B5C3045@redbarn.org>
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/H0h9X2s1IAJrBadpfhczz2rA9t0
Cc: dnsop@ietf.org
Subject: Re: [DNSOP] Review of draft-ietf-dnsop-cookies-00
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: <http://www.ietf.org/mail-archive/web/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: Wed, 17 Dec 2014 01:11:54 -0000

Hi Paul

On Tue, Dec 16, 2014 at 10:32:08AM -0800, P Vixie wrote:
> >It's 2 round trips to get at the data, answer the question. FIN is
> >later.
> 
> The total transaction time includes all time during which state is
> held. That third round trip is in your departmental budget and will
> show up at scale or in benchmarks. So you have to count it.

Is this network traffic budget (3-4 extra frames), or CPU budget or
memory budget for the TCP contexts?

I'm not able to tell from the above, in what way you mean FIN teardowns
would affect query performance as they can be done in parallel, whereas
the roundtrips upto the point the data is received happen in lockstep.

		Mukund