Re: [Add] Comparative DoH Discovery DNS RR Types
Paul Vixie <paul@redbarn.org> Mon, 29 June 2020 21:01 UTC
Return-Path: <paul@redbarn.org>
X-Original-To: add@ietfa.amsl.com
Delivered-To: add@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1313E3A0C47 for <add@ietfa.amsl.com>; Mon, 29 Jun 2020 14:01:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 soGTuv500FiM for <add@ietfa.amsl.com>; Mon, 29 Jun 2020 14:01:56 -0700 (PDT)
Received: from family.redbarn.org (family.redbarn.org [IPv6:2001:559:8000:cd::5]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7EDA23A0C5C for <add@ietf.org>; Mon, 29 Jun 2020 14:01:54 -0700 (PDT)
Received: from linux-9daj.localnet (dhcp-166.access.rits.tisf.net [24.104.150.166]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (1024 bits) server-digest SHA256) (Client did not present a certificate) by family.redbarn.org (Postfix) with ESMTPSA id 18000B0588 for <add@ietf.org>; Mon, 29 Jun 2020 21:01:50 +0000 (UTC)
From: Paul Vixie <paul@redbarn.org>
To: ADD Mailing list <add@ietf.org>
Date: Mon, 29 Jun 2020 21:01:49 +0000
Message-ID: <26559974.PdTMpzyJZD@linux-9daj>
Organization: none
In-Reply-To: <7325C546-587D-4CD9-8059-0887C33F3503@cable.comcast.com>
References: <7325C546-587D-4CD9-8059-0887C33F3503@cable.comcast.com>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="nextPart1784631.GPElSuburT"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/add/Z-9heiwqTbY1AtfnAgM3c46L15o>
Subject: Re: [Add] Comparative DoH Discovery DNS RR Types
X-BeenThere: add@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications Doing DNS <add.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/add>, <mailto:add-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/add/>
List-Post: <mailto:add@ietf.org>
List-Help: <mailto:add-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/add>, <mailto:add-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Jun 2020 21:01:59 -0000
On Monday, 29 June 2020 15:36:42 UTC Livingood, Jason wrote: > Just noting far we have a variety of suggestions on CNAME, URI, TXT, RESINFO > and HTTPSSVC (though I don’t think all have I-Ds as yet) - always nice to > see the ideas flowing. :-) As a practical person that in IETF land is > considered an implementer, I naturally feel inclined towards RR types that > already exist as this enables something to be rapidly deployed. the community apparently lacks coherence on the importance of rapid deployment as compared to the importance of technical excellence. if we're not going to add any more new RR types because they take ten years to become usable (see the SPF RR vs. the later _spf TXT RR), we should say that, and close the RR type registry, so as to avoid confusing newcomers. if on the other hand we're going to continue to evolve DNS in ways that include adding new RR types, and all the initiators who are stuck behind dumbass middleboxes who reject or butcher unknown RR types are going to fail hard and be excluded from the new applications and protocols in order to put more pressure on middlebox users/makers/distributors, we should say that. either way, nothing is temporary. whatever we use for resolver discovery will be present as a data pattern and code path in all future software. improved signal patterns and associated logic will live alongside the unimproved ones, raising the bar for both short-term expedients and later improvement to be "worthy of its coexistence cost". for clarity, that's a _very_ high bar. > As all of these become documented a discussed a bit further - or even tested > experimentally - my humble suggestion is that it may be helpful for the WG > to develop a grid of all the options with their associated pros & cons. such grid would be well informed by the attached graphic. -- Paul
- [Add] Comparative DoH Discovery DNS RR Types Livingood, Jason
- Re: [Add] Comparative DoH Discovery DNS RR Types Paul Vixie
- [Add] DNS and middleboxes (was Re: Comparative Do… Adam Roach
- Re: [Add] Comparative DoH Discovery DNS RR Types Tommy Pauly
- Re: [Add] Comparative DoH Discovery DNS RR Types Michael Richardson
- Re: [Add] Comparative DoH Discovery DNS RR Types Daniel Migault
- Re: [Add] Comparative DoH Discovery DNS RR Types Christian Huitema
- Re: [Add] Comparative DoH Discovery DNS RR Types Martin Thomson
- Re: [Add] Comparative DoH Discovery DNS RR Types Paul Vixie
- Re: [Add] Comparative DoH Discovery DNS RR Types Rob Sayre
- Re: [Add] Comparative DoH Discovery DNS RR Types dagon
- Re: [Add] Comparative DoH Discovery DNS RR Types tirumal reddy
- Re: [Add] Comparative DoH Discovery DNS RR Types tirumal reddy
- Re: [Add] Comparative DoH Discovery DNS RR Types Paul Wouters
- Re: [Add] Comparative DoH Discovery DNS RR Types Paul Wouters