Re: [DNSOP] Fundamental ANAME problems

Joe Abley <jabley@hopcount.ca> Tue, 06 November 2018 13:51 UTC

Return-Path: <jabley@hopcount.ca>
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 9A74B130DD4 for <dnsop@ietfa.amsl.com>; Tue, 6 Nov 2018 05:51:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 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, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=hopcount.ca
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 gcpEJlOuwzbA for <dnsop@ietfa.amsl.com>; Tue, 6 Nov 2018 05:51:26 -0800 (PST)
Received: from mail-lj1-x22d.google.com (mail-lj1-x22d.google.com [IPv6:2a00:1450:4864:20::22d]) (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 232CE12D4F1 for <dnsop@ietf.org>; Tue, 6 Nov 2018 05:51:26 -0800 (PST)
Received: by mail-lj1-x22d.google.com with SMTP id s15-v6so11495791lji.3 for <dnsop@ietf.org>; Tue, 06 Nov 2018 05:51:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hopcount.ca; s=google; h=from:mime-version:references:in-reply-to:date:message-id:subject:to :cc; bh=dEjEnGuyF15nw9Te5F87pWu6sKskmXmFfIL2Ixkvj/k=; b=EeMpDcXrJmQRHWD7CiVTuubDMK+rlORTD1ot/pcnmyWDY0I5NaWIECdeh5jgC5cKc9 CzkNOX5l514XRpI2xvNztdEiCLbO/V9uAINlrfPLl6HGTE/LWgTUsvkkdra5G08los5G UJgK+6ylJ1jQ2XAWe1JZUyv1p2sZQzpePedv8=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:mime-version:references:in-reply-to:date :message-id:subject:to:cc; bh=dEjEnGuyF15nw9Te5F87pWu6sKskmXmFfIL2Ixkvj/k=; b=eQPs15vq4zEG7wCU+756DofeVs7LMNeT8z+PtSiIyeQsa8wLwcgG9BhYAuxfQdpty2 aDAtIkzP9ZKlXHQnMGuwOErBuCEeylglSWeQlwDv1IN8ap3cFODV5aGFuclYmMug33UJ jG/QNjanQ3wwhKW1GP/SHDUSJ26JaxJvg/miX+/awagaN+vVsMZfoB+gPPLG9YjeRGg0 A7IQqCbqyaN2L4VxatnSJvPTzv9QQsaTNZFwZeNCWZFsKkBgiLmNOadBhDPnJqIdIVfG 85V4GLnF8x27kI3KN+sgxjv1T43CsYvWXDN/WbUFHz38+QA+nFzV//MphJU7mwUifCyT g1DA==
X-Gm-Message-State: AGRZ1gJ7XaPxELxwXnFJHeKtISsv7QmEKMbhydJN3hsAViHioQWufocM LjDysysbpM2M/8O4/LwAfMwZTo8z6YhHXCIS+RcydTQr
X-Google-Smtp-Source: AJdET5d71TkJjlTFybid5qUMBAaoBLyPdJ/avTe1B5NSZlbvksPEL9WXfckA9aYY1wePy4BbBYT/U6ntV/3va9El9hg=
X-Received: by 2002:a2e:4942:: with SMTP id b2-v6mr16663722ljd.129.1541512284209; Tue, 06 Nov 2018 05:51:24 -0800 (PST)
Received: from unknown named unknown by gmailapi.google.com with HTTPREST; Tue, 6 Nov 2018 05:51:23 -0800
From: Joe Abley <jabley@hopcount.ca>
Mime-Version: 1.0 (1.0)
References: <CAH1iCirXYsYB3sAo8f1Jy-q4meLmQAPSFO-7x5idDufdT_unXQ@mail.gmail.com> <alpine.DEB.2.20.1811021543210.24450@grey.csi.cam.ac.uk> <20181105083526.GA12204@besserwisser.org> <7704C350-256A-42E3-B718-38FD449A2ADE@hopcount.ca> <770d5dc8-b8a3-c1c3-553f-0e9504389750@bellis.me.uk> <CAJhMdTODiJ7DvN5=sFnvEj-FP=M=2yDN_enk17Bo=En9V8bLjw@mail.gmail.com> <alpine.DEB.2.20.1811061338450.24450@grey.csi.cam.ac.uk>
In-Reply-To: <alpine.DEB.2.20.1811061338450.24450@grey.csi.cam.ac.uk>
Date: Tue, 6 Nov 2018 05:51:23 -0800
Message-ID: <CAJhMdTO+tRhyUhArcNUhxqvkCXKCSBfF_-Ts+7WSOV8Qf_ToEg@mail.gmail.com>
To: Tony Finch <dot@dotat.at>
Cc: Ray Bellis <ray@bellis.me.uk>, dnsop@ietf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/RVNFwC8eLMtQcm8Z_ejmkiqDwzA>
Subject: Re: [DNSOP] Fundamental ANAME problems
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: Tue, 06 Nov 2018 13:51:29 -0000

Hi Tony.

> On Nov 6, 2018, at 20:44, Tony Finch <dot@dotat.at>; wrote:
>
> Joe Abley <jabley@hopcount.ca>; wrote:
>>
>> Specifically, I s the wildcard owner name a real problem in the grand
>> scheme of things?
>
> My understanding is that wildcards don't work for SRV because the
> _prefixes are used to disambiguate which service you are asking for,
> effectively to extend the RR TYPE number space. So if you wildcard a SRV
> record then the target port has to support every possible protocol :-)

Right, but my point was that wildcard owner names aren't seen at the
apex, so a solution to the problem of what to do at the apex doesn't
need to worry about them.

Ray has wider aspirations than just the apex. This may well be
sensible, but I think it's worth calling out the scope creep.


Joe