Re: [DNSOP] new ANAME draft: draft-hunt-dnsop-aname-00.txt

Paul Wouters <paul@nohats.ca> Tue, 11 April 2017 19:11 UTC

Return-Path: <paul@nohats.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 AFDAF1294C3 for <dnsop@ietfa.amsl.com>; Tue, 11 Apr 2017 12:11:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-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=nohats.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 u1wE4TlzlymB for <dnsop@ietfa.amsl.com>; Tue, 11 Apr 2017 12:11:11 -0700 (PDT)
Received: from mx.nohats.ca (mx.nohats.ca [193.110.157.68]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 239E712EC34 for <dnsop@ietf.org>; Tue, 11 Apr 2017 12:11:09 -0700 (PDT)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 3w2c8q0R1Yz38S; Tue, 11 Apr 2017 21:11:07 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1491937867; bh=qcu4MNSp8cHTKiv1OgiKxV7YybYemAYJCEQFAik0q5M=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=Rmys32Ey59W0zFUHuVBPylWY80njOIXa7tsQTA9AMrw+zTVU4qeMTfuld0+J+6VW4 MawzLiGe39O0Q7ShnkcytqqXHBsdwrQwEJCgveMKEhKtknDooeJeJ4SiasY54P5FRh k1dzoWaclRxg3ZuG3zh+KY0lMNTPBXt9p2uD+ahA=
X-Virus-Scanned: amavisd-new at mx.nohats.ca
Received: from mx.nohats.ca ([IPv6:::1]) by localhost (mx.nohats.ca [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id Xx6MYQDAEZvR; Tue, 11 Apr 2017 21:11:05 +0200 (CEST)
Received: from bofh.nohats.ca (bofh.nohats.ca [76.10.157.69]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx.nohats.ca (Postfix) with ESMTPS; Tue, 11 Apr 2017 21:11:04 +0200 (CEST)
Received: by bofh.nohats.ca (Postfix, from userid 1000) id 1DEF4418516; Tue, 11 Apr 2017 15:11:04 -0400 (EDT)
DKIM-Filter: OpenDKIM Filter v2.11.0 bofh.nohats.ca 1DEF4418516
Received: from localhost (localhost [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id 1345540D3585; Tue, 11 Apr 2017 15:11:04 -0400 (EDT)
Date: Tue, 11 Apr 2017 15:11:03 -0400 (EDT)
From: Paul Wouters <paul@nohats.ca>
To: Tony Finch <dot@dotat.at>
cc: dnsop <dnsop@ietf.org>
In-Reply-To: <alpine.DEB.2.11.1704111928520.4393@grey.csi.cam.ac.uk>
Message-ID: <alpine.LRH.2.20.999.1704111506120.15830@bofh.nohats.ca>
References: <20170407181139.GB66383@isc.org> <cc3bbc7a-3f48-2f7f-a3d9-3f752874fc00@redhat.com> <alpine.DEB.2.11.1704111641290.4393@grey.csi.cam.ac.uk> <alpine.LRH.2.20.999.1704111147390.8670@bofh.nohats.ca> <alpine.DEB.2.11.1704111928520.4393@grey.csi.cam.ac.uk>
User-Agent: Alpine 2.20.999 (LRH 202 2017-01-01)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/87afjwhZyhNiDPqUDxERNy-F7c0>
Subject: Re: [DNSOP] new ANAME draft: draft-hunt-dnsop-aname-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
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, 11 Apr 2017 19:11:13 -0000

On Tue, 11 Apr 2017, Tony Finch wrote:

> Paul Wouters <paul@nohats.ca> wrote:
>>
>> Can you give me an example of deploying ANAME outside the zone APEX that
>> is not solved by allowing a CNAME to point to a CNAME (which most code I
>> think already allows anyway)
>
> https://www.ietf.org/mail-archive/web/dnsop/current/msg19909.html
>
> If you have a subdomain that needs to be a mail domain and a web site, you
> need an MX pointing at your mail server and address records pointing at
> your web server. You can't use a CNAME because they are usually different
> servers.

Hmm okay. Although you could just make a real zone cut there and then it
becomes the APEX case again :P

> Also, mail domains cannot in practice be CNAMEs because of the disaster of
> RFC 821 / RFC 1122 mail domain canonicalization.

I'm not sure ANAME's make deployment corner cases easier :P

I still feel using ANAME without preprocessing by auth nameservers and
fixing returning multiple record type to a single query is the more
generic and fix for this problem.

Paul