Re: [DNSOP] QNAME minimisation on the standards track?

Marek Vavruša <mvavrusa@cloudflare.com> Tue, 17 July 2018 18:54 UTC

Return-Path: <mvavrusa@cloudflare.com>
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 2BCC4130E08 for <dnsop@ietfa.amsl.com>; Tue, 17 Jul 2018 11:54:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.011
X-Spam-Level:
X-Spam-Status: No, score=-2.011 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cloudflare.com
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 bwMqBwLHeqkq for <dnsop@ietfa.amsl.com>; Tue, 17 Jul 2018 11:54:05 -0700 (PDT)
Received: from mail-yb0-x22b.google.com (mail-yb0-x22b.google.com [IPv6:2607:f8b0:4002:c09::22b]) (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 2D46113107D for <dnsop@ietf.org>; Tue, 17 Jul 2018 11:54:01 -0700 (PDT)
Received: by mail-yb0-x22b.google.com with SMTP id l16-v6so832462ybk.11 for <dnsop@ietf.org>; Tue, 17 Jul 2018 11:54:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cloudflare.com; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=Zh3Vyny2tM3QDBV/Ot9CSSztLWElenY+IxpgDwTINNs=; b=nRn9TzDy7OGfnYJaEhqhQnPrIQBIA1brmKRpregO6R+W7n6IaAgP2CW89y3khjM1v6 mgzdCYj9z2nKqbx0KEFShp+kCzFqbgRNgFQCcsaGXUZsfzdF/sJ1hPC1jHssyBpMgsRE gphM+GUTwz1mZAn+/XN++4Esqb9sQYrtDOskk=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=Zh3Vyny2tM3QDBV/Ot9CSSztLWElenY+IxpgDwTINNs=; b=jai7a4Kb9xg4sGyYcyv3wU8Sty+xY9/JXUn48CgBEeIon1ef3rgJ2e9PVwlV0oU/de LXKLwRlXqwMDt2WiwdUXcyFS1G7dF5UQCYqaFsT1XqRXVGTdR1nEHYvoZhs91yAueX5b IYNok9Abzv0J9/Qe4qhc/kRs8mmemJCtOR5H4z0y5WtiuX+W7/AIcHRjIotMdn/c9Olb Cee/IeuW56Mb6trscO7kiy396wEnESAJyTOfSgVqAAnP2QuSnX+1rfjNa44Ylgbhzmv/ Qth0IdskCfnFaQCopbYcFkzvz2iC5KU4JvZV5vvP+VG9YvsK7InTQIG9uofm1l67hUQt lbsA==
X-Gm-Message-State: AOUpUlGDjifXJclbLMrz1eKY2wA4iIlJxMGWj3Uy7AFxmvzyEHLaQtDM zGL4xAxTF0hh8xOpfqZG/yFj8JLFC9QXa5Uy828S0Q==
X-Google-Smtp-Source: AAOMgpfaSLFKTco8cxMVvFoz5XBoOeNQ5sNiULx6ZbwlML3vQUbhRUm+LJV/0Tb9nPMdMfYKnknEU83WDkkxsHtcqhk=
X-Received: by 2002:a25:ad9a:: with SMTP id z26-v6mr1564238ybi.246.1531853640481; Tue, 17 Jul 2018 11:54:00 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a25:2c8c:0:0:0:0:0 with HTTP; Tue, 17 Jul 2018 11:54:00 -0700 (PDT)
In-Reply-To: <0E1026DD-2304-43FE-BEED-B9CE2981D9E3@gmail.com>
References: <20180717121406.GA6681@laperouse.bortzmeyer.org> <0E1026DD-2304-43FE-BEED-B9CE2981D9E3@gmail.com>
From: =?UTF-8?Q?Marek_Vavru=C5=A1a?= <mvavrusa@cloudflare.com>
Date: Tue, 17 Jul 2018 11:54:00 -0700
Message-ID: <CAC=TB13XreUeWbFHMxC2XGf0QGaSM1HhXawUpF+C9pQ+02nRtw@mail.gmail.com>
To: tjw ietf <tjw.ietf@gmail.com>
Cc: Stephane Bortzmeyer <bortzmeyer@nic.fr>, dnsop <dnsop@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/tHDoZhhKhBaJNzRpHufmwVYz9tc>
Subject: Re: [DNSOP] QNAME minimisation on the standards track?
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.27
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: Tue, 17 Jul 2018 18:54:10 -0000

I'd like to see this on the standards track as well. Cloudflare has
some operational experience with it (it's enabled by default on
1.1.1.1). It mostly works, but still has to be turned off on several
delegations that either don't respond to non-terminals, respond with
positive answer that's invalid (usually when there's an LB that only
handles final name, but gives out a referral to intermediate name), or
respond with nxdomain (this is the most common one and well known).

On Tue, Jul 17, 2018 at 10:01 AM, tjw ietf <tjw.ietf@gmail.com> wrote:
> I’d like to see a more fleshed out operational considerations section.
>
> Tim
> As chair
>
> From my high tech gadget
>
>> On Jul 17, 2018, at 08:14, Stephane Bortzmeyer <bortzmeyer@nic.fr> wrote:
>>
>> Greetings. With more resolvers implementing QNAME minimisation, and
>> even turning it on by default, we thought that this is a good time to
>> update RFC 7816 and make it a standard. In order to get things moving,
>> we have published a very early draft draft-bortzmeyer-rfc7816bis-00
>> that is mostly the original RFC but with a few questions and holes
>> added (see the text near the strings "TODO"). If folks in the WG is
>> interested, feel free to comment in the non-GitHub repo listed in the
>> draft, or here on the list.
>>
>>
>>
>> _______________________________________________
>> DNSOP mailing list
>> DNSOP@ietf.org
>> https://www.ietf.org/mailman/listinfo/dnsop
>
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop