Re: [DNSOP] Fundamental ANAME problems

Joe Abley <jabley@hopcount.ca> Mon, 05 November 2018 21:07 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 7CBBC1288BD for <dnsop@ietfa.amsl.com>; Mon, 5 Nov 2018 13:07:05 -0800 (PST)
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, RCVD_IN_DNSWL_NONE=-0.0001, UNPARSEABLE_RELAY=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 FqcQzVepdlmv for <dnsop@ietfa.amsl.com>; Mon, 5 Nov 2018 13:07:04 -0800 (PST)
Received: from mail-lf1-x12f.google.com (mail-lf1-x12f.google.com [IPv6:2a00:1450:4864:20::12f]) (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 881F31286E7 for <dnsop@ietf.org>; Mon, 5 Nov 2018 13:07:03 -0800 (PST)
Received: by mail-lf1-x12f.google.com with SMTP id p17so7234184lfh.4 for <dnsop@ietf.org>; Mon, 05 Nov 2018 13:07:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hopcount.ca; s=google; h=mime-version:from:in-reply-to:references:date:message-id:subject:to :cc:content-transfer-encoding; bh=6xOjBzkQEIvgFpfLAgAprSlC39cvSp8ll86lviq/dsQ=; b=kI0YctZMMGuFCG0bR7IzvII2EGZe6+tFEYkJTl3g63gaXzucsLKlgs4nbsQx0qfosy FICsPpODbSztCFO1BwgLSgaouwyuvBYBFDij2a3KOMPPrySAYNxWQxNEWISRYXAlFhSh +wgyXQ//+Hh25/3Wl6ii9ymby5hiYw7qNGRiw=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:in-reply-to:references:date :message-id:subject:to:cc:content-transfer-encoding; bh=6xOjBzkQEIvgFpfLAgAprSlC39cvSp8ll86lviq/dsQ=; b=Xe8thVuwJ25OlhH6w+lvvHkSgRzJD7bLnL1jwqJKiF7Rqwd6xisOqx6UxBRYST4PTx FyLVBWJZijeNMHiNkTnrgzkaS9oAnqesWn32ihXNTBF5Xkng6SN2/QaYOinchQnrEakn bOdi48i8XbqJJrEY4Eu6kN4v5M0BiQYHjWs8vmdQ85VIHc+2/iodJD5CN0bKc/PodRFl 3Bs93bZQQdl1y4qkWx0UajoNB0ZkWlIYzZCO7kSo51BRMKT7m6tnk9Mix2pNoQgBdB5e xrBRMYN0uyIGn0pt/jg84WA36N5gQ2+MIu6SxFr515qQokm28vDSx5dDhDPvju6kyUSf /g/w==
X-Gm-Message-State: AGRZ1gJ+A8FgSwhK5Vy+dv+/9QaN/DCq3SoBxvbmkQDjC0YURy28kTyl ktQ4xdJO8ZczEvwL+L+GWPXFXQl+TTktNXLiSeTYzQ==
X-Google-Smtp-Source: AJdET5dnhZkQqnCiOskcPX+QZ6xKk1vPq8E3ulAxYV003Mtwd0BInC41QHu56hbkRwsODo9EAVkbxfh+GMwGMs8c8qU=
X-Received: by 2002:a19:d381:: with SMTP id k123mr14150659lfg.101.1541452021575; Mon, 05 Nov 2018 13:07:01 -0800 (PST)
Received: from unknown named unknown by gmailapi.google.com with HTTPREST; Mon, 5 Nov 2018 13:07:00 -0800
Mime-Version: 1.0 (1.0)
From: Joe Abley <jabley@hopcount.ca>
In-Reply-To: <770d5dc8-b8a3-c1c3-553f-0e9504389750@bellis.me.uk>
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>
Date: Mon, 5 Nov 2018 13:07:00 -0800
Message-ID: <CAJhMdTODiJ7DvN5=sFnvEj-FP=M=2yDN_enk17Bo=En9V8bLjw@mail.gmail.com>
To: Ray Bellis <ray@bellis.me.uk>
Cc: dnsop@ietf.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/H8UgnN9RFMyPFNLqBdpkzv8rUco>
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: Mon, 05 Nov 2018 21:07:05 -0000

Hi Ray,

> On Nov 5, 2018, at 22:38, Ray Bellis <ray@bellis.me.uk>; wrote:
>
> There *is* a big failing of SRV that's independent of the CNAME apex use case, and that is its lack of support for wildcards.  Since my proposal doesn't use underscore prefix labels, wildcards will work, and this is an important requirement for some large website operators.

I realise it's 4am and I shouldn't even be awake,  ever mind replying
to dnsop mail, but it's not clear to me what the use-case is, here.

Specifically, I s the wildcard owner name a real problem in the grand
scheme of things? I understand that wildcards are used by some people
for names that feature in HTTP URIs, but I'm struggling to imagine
using a wildcard at a zone cut; if a wildcard label doesn't correspond
to a zone apex, why is it a problem that needs fixing? Didn't Ed
already clarify the use of CNAME with wildcards in RFC 4592 twelve
years ago?

> The cost to the DNS community of *trying* my proposed HTTP record is pretty negligible.

To be clear, the rules are clear and you should feel as empowered as
anybody to apply for an early assignment of an RRTYPE and start
writing code. If I sounded like I was arguing against that I
definitely apologise!

However I think that a more coordinated approach that involves people
from both web and DNS communities to understand the problem space is
more sensible, though, and more likely to be productive for this
working group. It's not clear to me that either community has a great
track record just guessing at what the other one wants.


Joe