Re: [DNSOP] DNSKEY RRset size and the root

Liang Zhu <liangzhu@usc.edu> Mon, 26 January 2015 17:58 UTC

Return-Path: <liangzhu@usc.edu>
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 191561ACD1E for <dnsop@ietfa.amsl.com>; Mon, 26 Jan 2015 09:58:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.979
X-Spam-Level:
X-Spam-Status: No, score=-1.979 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] 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 VhhTRKl5iO9N for <dnsop@ietfa.amsl.com>; Mon, 26 Jan 2015 09:58:01 -0800 (PST)
Received: from mail-wi0-f169.google.com (mail-wi0-f169.google.com [209.85.212.169]) (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 5E4161ACCE4 for <dnsop@ietf.org>; Mon, 26 Jan 2015 09:58:01 -0800 (PST)
Received: by mail-wi0-f169.google.com with SMTP id h11so5780927wiw.0 for <dnsop@ietf.org>; Mon, 26 Jan 2015 09:58:00 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=hb5ALXwW0j/ydgJkB/iNiYbB8CpihWfkv/65+yo7Zcc=; b=Mry7rOKJryxfpHvtOANydlXfckkBTUfCy3rzDu3Hb4AkDykFmxEvtsQQv+oF9BqPFv cGjzezhCUmEQhjyw1uUegvL5GJGn5vkh0lSG8ERXTGfjiYA06sp4S3qdP283PV2JRWpy uKT6wbvaykJ1BNnaaoH+63ghU2DecqOCNPnVVmbGT7+evD3LsTKjOkGWdo8TfjQrm9lz XasDP8IckMi2elAI2AZOPamjr6ORdSAscHR9Xqytpu546JqYOodFVSau7W3KdQj2wth6 TryAmzdudRVJPkaW4tch0Q4ktm7RczaShTyt+bp1OPtXi9l9djXuWgUcY1knI09m7dTj GmzA==
X-Gm-Message-State: ALoCoQmH5yuAb0IdOhQoNp61X2SkFmHUfd5NXby51PDPPbz09ZoikosLXSvbvK/s6u1OBa4YV4vv
MIME-Version: 1.0
X-Received: by 10.194.248.201 with SMTP id yo9mr45481233wjc.75.1422295080098; Mon, 26 Jan 2015 09:58:00 -0800 (PST)
Received: by 10.194.123.39 with HTTP; Mon, 26 Jan 2015 09:58:00 -0800 (PST)
In-Reply-To: <48AE7501-A80A-40B1-8FDA-34984AA4D42A@icsi.berkeley.edu>
References: <alpine.LFD.2.10.1501191417240.2981@bofh.nohats.ca> <273A9C85-EC12-4916-99E4-C4839E553555@virtualized.org> <alpine.LFD.2.10.1501221308540.14274@bofh.nohats.ca> <CAC3z6OjZB=3JjLFDY=dt7kA8W993af5VSz6Gaa-B9Eb7Z40Kmw@mail.gmail.com> <F5BB5028-12FD-4D08-B631-055344BE4FC3@vpnc.org> <48AE7501-A80A-40B1-8FDA-34984AA4D42A@icsi.berkeley.edu>
Date: Mon, 26 Jan 2015 09:58:00 -0800
Message-ID: <CAC3z6OhoYkmSiJLqHA55W_3i8GN94QR9fQbndDOj=wSP3PGULg@mail.gmail.com>
From: Liang Zhu <liangzhu@usc.edu>
To: Nicholas Weaver <nweaver@icsi.berkeley.edu>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/VoUmw8_ZQCmw3tSR9w-vrdM5oLw>
Cc: IETF DNSOP WG <dnsop@ietf.org>, Paul Hoffman <paul.hoffman@vpnc.org>
Subject: Re: [DNSOP] DNSKEY RRset size and the root
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: Mon, 26 Jan 2015 17:58:03 -0000

On Fri, Jan 23, 2015 at 10:12 AM, Nicholas Weaver
<nweaver@icsi.berkeley.edu> wrote:
>
>> On Jan 23, 2015, at 10:01 AM, Paul Hoffman <paul.hoffman@vpnc.org> wrote:
>>
>> What is the problem with #2? IP fragmentation happens, and The Internet is expected to work with it. That is, of what possible value is "inform their customers"?
>
> The Internet has unfortunately decreed that Fragmentation Does Not Work with IPv4, and Really Does Not Work with IPv6.
>
> This will cause timeouts until the resolver realizes it should use a smaller EDNS0 MTU and in that case, the resolver will failover to TCP for that query, which some in the DNS community view as anathema...
>

Besides the additional latency caused by loss recovery, as Nicholas
said, fragments may also bring problem of fragmentation attack
described in:
A. Herzberg and H. Shulmanz. Fragmentation considered poisonous. In
Proc. of IEEE Conference on Communications and NetworkSecurity (CNS),
Oct. 2013.

-Liang Zhu