Re: [DNSOP] faux BNAME, was abandoning ANAME and standardizing CNAME at apex

"John Levine" <johnl@taugh.com> Wed, 20 June 2018 22:04 UTC

Return-Path: <johnl@iecc.com>
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 1EEBF130EBF for <dnsop@ietfa.amsl.com>; Wed, 20 Jun 2018 15:04:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.752
X-Spam-Level:
X-Spam-Status: No, score=-1.752 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=H/mzBOAX; dkim=pass (1536-bit key) header.d=taugh.com header.b=iN6mq8Ea
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 sgQ8kO2dFKq2 for <dnsop@ietfa.amsl.com>; Wed, 20 Jun 2018 15:04:27 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 F2F16130EC6 for <dnsop@ietf.org>; Wed, 20 Jun 2018 15:04:26 -0700 (PDT)
Received: (qmail 49617 invoked from network); 20 Jun 2018 22:04:25 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=c1cf.5b2acf69.k1806; bh=ctsPr9AAi099T5/ZDf9uI9CCtkGqHc6eKsTTmjBz0sw=; b=H/mzBOAX7xLjlfJGMgbHmxgYzswq9lJObh5suwxZ3pX6K8t8YtN3k73VHt68FHicHfnqP533hVrNVRaK3WRbz7d4cqvpl9XIET5iEx29rZDQnQ/JkK6ZijrQFCX6jtXMY4Phyjh8htAmJ4TbkjzS11/YMdc9SzfcsrygSjQGomQyqQuTPEBjl2X6bjsgWgSUoiZaSINnUJT65TNjiLW62IOUvBWNUsIJnci4hKmcLierTzPGvpfFvokyQLqiflct
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=c1cf.5b2acf69.k1806; bh=ctsPr9AAi099T5/ZDf9uI9CCtkGqHc6eKsTTmjBz0sw=; b=iN6mq8EaeRg6g3GOzVUjY9LROMy4f5HNKCE7v5Gp6sPscbiP7zvKpxldHTP74HfMPVmg/Hf1HDOPFl4BFx2YAiTAFVRfg2IPgg/W9SgJXjyKn2uZ4hBWxUKC/PWivu0qVyBX+4qwDRomwT7ktjd1yPPjWQBd47jiKJFrklAfimnnz8tpt9losxzXg1rGRVDiSw+XJDEvRBwKsOanxTOFc7lNN0ykA4SVWIjrNWeAQqWYIBimvtGzIDHev2n1jxaj
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTP via TCP6; 20 Jun 2018 22:04:25 -0000
Received: by ary.qy (Postfix, from userid 501) id 4B03D2855D7E; Wed, 20 Jun 2018 18:04:24 -0400 (EDT)
Date: 20 Jun 2018 18:04:24 -0400
Message-Id: <20180620220425.4B03D2855D7E@ary.qy>
From: "John Levine" <johnl@taugh.com>
To: dnsop@ietf.org
Cc: ondrej@isc.org
In-Reply-To: <38B08915-4649-454C-ADDF-B21422386D1F@isc.org>
Organization: Taughannock Networks
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/joXTXZh50I_Bd4iSiINxMvIRkI4>
Subject: Re: [DNSOP] faux BNAME, was abandoning ANAME and standardizing CNAME at apex
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.26
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: Wed, 20 Jun 2018 22:04:30 -0000

In article <38B08915-4649-454C-ADDF-B21422386D1F@isc.org>; you write:
>Oh, what about this?
>
>https://tools.ietf.org/html/draft-sury-dnsext-cname-dname-00
>
>:-)

I think it would work in the DNS but it wouldn't solve any real
problems.

If you want to make your applications work with parallel or variant
domain names, the work is about 5% getting the names into the DNS, and
95% getting your web and mail and other application servers to do the
right thing when they see the names.  I can imagine some approaches
but they all involve provisioning systems that should be able to spit
out the required DNS zones while they do everything else, no CNAME or
ANAME or DNAME required.

R's,
John