IETF Logo Mail Archive

Re: [DNSOP] L-Root Maintenance 2010-01-27 1800 UTC - 2000 UTC

Nicholas Weaver <nweaver@ICSI.Berkeley.EDU> Thu, 28 January 2010 17:41 UTC

Return-Path: <nweaver@ICSI.Berkeley.EDU>
X-Original-To: dnsop@core3.amsl.com
Delivered-To: dnsop@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0804E3A6AB1 for <dnsop@core3.amsl.com>; Thu, 28 Jan 2010 09:41:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3hhogcAzwYqL for <dnsop@core3.amsl.com>; Thu, 28 Jan 2010 09:41:07 -0800 (PST)
Received: from fruitcake.ICSI.Berkeley.EDU (fruitcake.ICSI.Berkeley.EDU [192.150.186.11]) by core3.amsl.com (Postfix) with ESMTP id 177A63A6AAD for <dnsop@ietf.org>; Thu, 28 Jan 2010 09:41:07 -0800 (PST)
Received: from [IPv6:::1] (jack.ICSI.Berkeley.EDU [192.150.186.73]) by fruitcake.ICSI.Berkeley.EDU (8.12.11.20060614/8.12.11) with ESMTP id o0SHfPvC028859; Thu, 28 Jan 2010 09:41:25 -0800 (PST)
References: <20100128165911.GA20811@dul1mcmlarson-l1-2.local>
In-Reply-To: <20100128165911.GA20811@dul1mcmlarson-l1-2.local>
Mime-Version: 1.0 (Apple Message framework v1077)
Content-Type: text/plain; charset="us-ascii"
Message-Id: <6C5745D7-2529-4FD4-AB71-3A8B8E5E4483@icsi.berkeley.edu>
Content-Transfer-Encoding: quoted-printable
From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
Date: Thu, 28 Jan 2010 09:41:25 -0800
To: Matt Larson <mlarson@verisign.com>
X-Mailer: Apple Mail (2.1077)
Cc: "dnsop@ietf.org" <dnsop@ietf.org>, Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
Subject: Re: [DNSOP] L-Root Maintenance 2010-01-27 1800 UTC - 2000 UTC
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Thu, 28 Jan 2010 17:41:08 -0000

On Jan 28, 2010, at 8:59 AM, Matt Larson wrote:

> On Thu, 28 Jan 2010, Mark Andrews wrote:
>> The DNSKEY RRset size seems small for testing.  We really should
>> be looking the biggest key set sizes that occur during rollover
>> simultaneous ZSK/KSK rollovers.  Hopefully that is in the planning.
> 
> The design allows for ZSK rollovers at calendar quarter boundaries and
> KSK rollovers in the middle of a quarter, which are intentionally
> non-overlapping so that the are never more than three keys in the root
> DNSKEY RRset.  (Please see the diagram on page five of
> http://www.root-dnssec.org/wp-content/uploads/2009/12/draft-icann-dnssec-arch-v1dot2dot1.pdf,
> which Tony already referred to.)
> 


Stupid question on Figure 2:  What is the approximate size of responses during these different periods?  In particular, do any particular "magic limits" in the network (namely the 1500B ethernet MTU, the 1492 PPPoE MTU, the "likely to be in path MTU hole" of 1480-1500B MTU, or the somewhat common 1280 EDNS MTU) get hit?

v2.23.0 | Report a Bug | By Email