Re: [DNSOP] Closing out issues in draft-ietf-dnsop-resolver-priming

"Joe Abley" <jabley@hopcount.ca> Fri, 16 October 2015 21:18 UTC

Return-Path: <jabley@hopcount.ca>
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 6B1991A004A for <dnsop@ietfa.amsl.com>; Fri, 16 Oct 2015 14:18:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1] 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 ek1wiQZdkI7B for <dnsop@ietfa.amsl.com>; Fri, 16 Oct 2015 14:18:06 -0700 (PDT)
Received: from mail-io0-x230.google.com (mail-io0-x230.google.com [IPv6:2607:f8b0:4001:c06::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 302F01A21A7 for <dnsop@ietf.org>; Fri, 16 Oct 2015 14:18:06 -0700 (PDT)
Received: by iofl186 with SMTP id l186so137480011iof.2 for <dnsop@ietf.org>; Fri, 16 Oct 2015 14:18:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hopcount.ca; s=google; h=from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-type; bh=R/AAU106WEIZ70hwKG+PdlozWFJhY7vl/DZDJDHEB6g=; b=QaSDyyhBd59ILYYCDGDaVn2PdeD4i+ff3MR1j452v2dQmMp3/noKClqJcq+Ksu0MJc IOWCbWKWNPTtZ2r9bQ++W1jezVCP5VsrG7YQK56oNx3raF/KRlANLQUN328HFN2bY85V 7DltCYL/uyMeQHtcMujNzwgb3MibESjY5t7bs=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references:mime-version:content-type; bh=R/AAU106WEIZ70hwKG+PdlozWFJhY7vl/DZDJDHEB6g=; b=mF42twcSz+QiupKB540G85SPmX8Aa9TG5k9Mh672Dp6SYpuCDf+TQv6CRPcASe5b0K oEzeaw67TmBS9jKYZNyEfqDZlQMJjBhhmHonVz3n92RZC1Zbk3epAfscEhC3mCn7MnSR ydGNIwcaLaBsLpgbBPhThOGdr08niJiIIdf9VFfIGu62nJTX/bEfXCO2s649XGwzyIjI BBwEYf+yUCuPsJjTGzzUg4CsPI8/FYphABPo9YVrqiKGft6qX27bopxt1Fya2sm4dFdD F109XI5LNYvAkCKgcYZKi/Ol+VBMvJatU56x0ZIberpnVLw28LFrU9si+NHo2WtWzHjN PzGA==
X-Gm-Message-State: ALoCoQnkdBGedXSW48JiA6+w8KQSskrkMPNbraJ2UvZ400MRU/qgnGJ+cXKkltlFdDYFk7Ykv95S
X-Received: by 10.107.136.216 with SMTP id s85mr16180930ioi.142.1445030284785; Fri, 16 Oct 2015 14:18:04 -0700 (PDT)
Received: from [199.212.92.19] (135-23-68-43.cpe.pppoe.ca. [135.23.68.43]) by smtp.gmail.com with ESMTPSA id i15sm8891885ioe.6.2015.10.16.14.18.03 (version=TLSv1 cipher=RC4-SHA bits=128/128); Fri, 16 Oct 2015 14:18:04 -0700 (PDT)
From: Joe Abley <jabley@hopcount.ca>
To: Darcy Kevin <kevin.darcy@fcagroup.com>
Date: Fri, 16 Oct 2015 17:18:05 -0400
Message-ID: <77A9ADD7-7198-4547-B257-EBD607990D0E@hopcount.ca>
In-Reply-To: <78e1865f9d794271aeddac4e8f2bb986@mxph4chrw.fgremc.it>
References: <8149BC4D-F11E-4E4F-BBB8-C38D865A4184@vpnc.org> <20151016161831.58bdf78d@pallas.home.time-travellers.org> <56211942.20206@redbarn.org> <CAJE_bqcxjC=zS8tj6tKGX18UeEFm6GHcyRhjC7AFdh3x9-L=vA@mail.gmail.com> <d2f5212cbf9b4f46a5cae9f3af3f1f50@mxph4chrw.fgremc.it> <A7B11A56-A66F-4E13-9675-56344E25C403@vpnc.org> <BCE894DC-01B6-42C4-9589-1C19CA395250@hopcount.ca> <20151016204202.677f3be3@pallas.home.time-travellers.org> <8D54A560-B4A8-457C-8883-7C2B04394C0F@hopcount.ca> <20151016222102.50590900@pallas.home.time-travellers.org> <78e1865f9d794271aeddac4e8f2bb986@mxph4chrw.fgremc.it>
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"
X-Mailer: MailMate (1.9.2r5141)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/9ZP0siAu6jUfQ5pmvN-_qagmOKA>
Cc: dnsop WG <dnsop@ietf.org>
Subject: Re: [DNSOP] Closing out issues in draft-ietf-dnsop-resolver-priming
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, 16 Oct 2015 21:18:07 -0000


On 16 Oct 2015, at 16:36, Darcy Kevin (FCA) wrote:

> It would be wise to get a clear statement of preference from the 
> Internet root operators on this, but don't forget that whatever gets 
> defined in IETF standards, and implemented in leading DNS software 
> packages, also affects private enterprises too. Many of us run 
> internal roots and I, for one, don't want to see an influx of traffic 
> and/or spiky saturation of bandwidth, because priming suddenly morphed 
> from UDP to TCP in the latest software update.

Let's make sure we put this in perspective, though -- how often do your 
resolvers restart? If it's once per few months to apply a kernel patch, 
then we're talking about far less traffic than your printers, phones and 
laptops are spewing every second onto the network with mDNS (or ARP, 
even :-)

Real root servers deal with internet-scale numbers of resolvers. It 
seems unlikely you have that problem in your campus network.


Joe