Re: [DNSOP] draft-fujiwara-dnsop-avoid-fragmentation-01

Bob Harold <rharolde@umich.edu> Wed, 09 October 2019 15:30 UTC

Return-Path: <rharolde@umich.edu>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4DB68120111 for <dnsop@ietfa.amsl.com>; Wed, 9 Oct 2019 08:30:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=umich.edu
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 3uz_xRv5aQGj for <dnsop@ietfa.amsl.com>; Wed, 9 Oct 2019 08:30:19 -0700 (PDT)
Received: from mail-lf1-x12c.google.com (mail-lf1-x12c.google.com [IPv6:2a00:1450:4864:20::12c]) (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 1E436120129 for <dnsop@ietf.org>; Wed, 9 Oct 2019 08:30:17 -0700 (PDT)
Received: by mail-lf1-x12c.google.com with SMTP id q12so1976615lfc.11 for <dnsop@ietf.org>; Wed, 09 Oct 2019 08:30:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=umich.edu; s=google-2016-06-03; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=jtB4+lZGXSPrqcaFQQVJB5vOj2BPYs2vd8YVV/28Wac=; b=h/OYS9lpkTSThQQf7mJqM5XZgDt8w3f+pW45X0q/BeaMUNJt5VEjV6jyLBA+QbUWqz FpCXCpDZgLoH7bbTh5IkgtLM3e4iYyYvGuvWje8NH+Z2SAQkBjCPz/SLWj0rBMmFUNpJ 8Zo0In06sPozdxCUPmHD3XzHWXeQKOsuGQCAkcN4kT4c7JGwFNx/NeJzM08f3XT/EkRj HUSCaJLcCHRxDI51kfvVNTc9iV9Mu6j5vyPE7TthpmUYeyas8Iij+BZSNIhaTSl/Mhs4 RcaoEDlrHgLwYPbus+UpYFdHLh4iK3d8Tge+sALg+rympKfWgysW8FUJwug0f6dWe0u0 eRwQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=jtB4+lZGXSPrqcaFQQVJB5vOj2BPYs2vd8YVV/28Wac=; b=nBmYGZOZOcgYUc4wgpXI+RzskO/iheeW0cpuIilJO2ZOHuUYt5tMVjU+9XyN4l8ycp TmpwCBLvXiHmRMYpaxjNa9/VuhkcUf/5uWOTIiWtvogd8PM6Fh4zu8Kuxgk4XDNAUZyM Fsjg+ipc+lFa9TY1aTU8Ttt8i4Hye3xFIHCt/Optd9oLrsjjS9B6JhpRNKWy3n3bVhFZ IOKUZ51rDXfqru1uE0ljQjohVRupmcMyWaHfJn7fQWKi5usH4rsg/Uyjy5gL0nKajwva eL3L9yjUz3LDDpIR+kdER0wko2Q/LNHbJVQEU2BS54/ZFX/w9WD1N7eVxcWqDtDx+7SU ngGQ==
X-Gm-Message-State: APjAAAXdck9NarEYBYP+7ClZk1Asf5lPr9fgmzUhfStkh1+NpnSXTUqT tTMsXO3agkLmX/vpaBpsVd6pO1VgWV8yFbqf+r0m3GTgjPI=
X-Google-Smtp-Source: APXvYqxzzrzqxs9GlnhAe3kMuTIleZUFAiIbBx7+A+EK3uTg025AQhDv84CeRoXZgwJn8+XpohWcCrEjKT873ylHZwI=
X-Received: by 2002:ac2:528f:: with SMTP id q15mr2456210lfm.25.1570635016149; Wed, 09 Oct 2019 08:30:16 -0700 (PDT)
MIME-Version: 1.0
References: <20191009.130440.1636022332681501956.fujiwara@jprs.co.jp>
In-Reply-To: <20191009.130440.1636022332681501956.fujiwara@jprs.co.jp>
From: Bob Harold <rharolde@umich.edu>
Date: Wed, 9 Oct 2019 11:30:03 -0400
Message-ID: <CA+nkc8DpytizA3qgM-CqCPoQ8kO2+WDEsckUSK5=5jn3f=50+w@mail.gmail.com>
To: fujiwara@jprs.co.jp
Cc: IETF DNSOP WG <dnsop@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000035ae6c05947bf676"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/tLGVzXQeRm1bmqeHV01l2Ev9Dcg>
Subject: Re: [DNSOP] draft-fujiwara-dnsop-avoid-fragmentation-01
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 09 Oct 2019 15:30:22 -0000

On Wed, Oct 9, 2019 at 12:04 AM <fujiwara@jprs.co.jp> wrote:

> Dear dnsop WG,
>
> Please review draft-fujiwara-dnsop-avoid-fragmentation-01.
>   https://tools.ietf.org/html/draft-fujiwara-dnsop-avoid-fragmentation-01
>
> Main differences are:
> - New Co-author
> - Refer RFC 8085 UDP Usage Guidelines
> - SHOULD send DNS responses with IP_DONTFRAG / IPV6_DONTFRAG [RFC3542]
> - Use actual path MTU information, or the default maximum DNS/UDP payload
> size
>    - Added text about how to retrieve path MTU value in appendix
>            getsockopt() IP_MTU and IPV6_MTU (Linux only)
>    - default maximum DNS/UDP payload size >= 1220, and <= 1400
> - Request to zone operator: Use smaller contents (number of RRs, DNSSEC
> key)
>
> --
> Kazunori Fujiwara, JPRS <fujiwara@jprs.co.jp>
>

Thank you for working on this.  I would like to suggest updates to two
sections so that they read better.

----- current:

1.  Introduction

   DNS has EDNS0 [RFC6891] mechanism.  It enables that DNS server can
   send large size response using UDP.  Now EDNS0 is widely deployed,
   and DNS (over UDP) is said to be the biggest user of IP
   fragmentation.

---- rewrite:

1.  Introduction

   DNS has the EDNS0 [RFC6891] mechanism, which enables a DNS server to
   send large size response using UDP.  Now that EDNS0 is widely deployed,
   DNS (over UDP) is said to be the biggest user of IP
   fragmentation.


------ current:

5.  Incremental deployment

   The proposed method supports incremental deployment.

   When a full-service resolver implements the proposed method, the
   full-service resolver becomes to avoid IP fragmentation in DNS.

   When an authoritative server implements the proposed method, the
   authoritative server becomes to avoid IP fragmentation in DNS.

---- rewrite:

5.  Incremental deployment

   The proposed method supports incremental deployment.

   When a full-service resolver implements the proposed method, the
   full-service resolver avoids IP fragmentation in DNS.

   When an authoritative server implements the proposed method, the
   authoritative server avoids IP fragmentation in DNS.


-- 
Bob Harold