Re: [Add] Comparative DoH Discovery DNS RR Types

Michael Richardson <mcr@sandelman.ca> Mon, 29 June 2020 23:57 UTC

Return-Path: <mcr@sandelman.ca>
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 33E633A0E6B for <add@ietfa.amsl.com>; Mon, 29 Jun 2020 16:57:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 aZoZFX5h83Mg for <add@ietfa.amsl.com>; Mon, 29 Jun 2020 16:57:53 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 39A383A0E6D for <add@ietf.org>; Mon, 29 Jun 2020 16:57:52 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 9908C389A8; Mon, 29 Jun 2020 19:55:04 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 5FoXtq4mfVsA; Mon, 29 Jun 2020 19:55:03 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id AFE54389A7; Mon, 29 Jun 2020 19:55:03 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id D9C77111E; Mon, 29 Jun 2020 19:57:49 -0400 (EDT)
From: Michael Richardson <mcr@sandelman.ca>
To: Paul Vixie <paul@redbarn.org>, ADD Mailing list <add@ietf.org>
In-Reply-To: <26559974.PdTMpzyJZD@linux-9daj>
References: <7325C546-587D-4CD9-8059-0887C33F3503@cable.comcast.com> <26559974.PdTMpzyJZD@linux-9daj>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Mon, 29 Jun 2020 19:57:49 -0400
Message-ID: <18350.1593475069@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/add/EwbFNn1esRyUzDH3Th6H9RTDj8A>
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 23:57:55 -0000

Paul Vixie <paul@redbarn.org> 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

I'm with Paul. I prefer creating new RR types.
There aren't that many dumbass middleboxes around, and those that are there,
are usually put there intentionally, and they deserve what they get.

I was among the first who did that back in 2002, and it wasn't that hard.

--
]               Never tell me the odds!                 | ipv6 mesh networks [
]   Michael Richardson, Sandelman Software Works        |    IoT architect   [
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [