Re: [lamps] DNS DNAME pain.

"John R Levine" <johnl@taugh.com> Thu, 09 November 2017 16:53 UTC

Return-Path: <johnl@taugh.com>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2C25A127775 for <spasm@ietfa.amsl.com>; Thu, 9 Nov 2017 08:53:44 -0800 (PST)
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, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=PpRBbpML; dkim=pass (1536-bit key) header.d=taugh.com header.b=Cx4GVw9l
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 gN7dzVb5aEBW for <spasm@ietfa.amsl.com>; Thu, 9 Nov 2017 08:53:42 -0800 (PST)
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 683E7124C27 for <spasm@ietf.org>; Thu, 9 Nov 2017 08:53:42 -0800 (PST)
Received: (qmail 22600 invoked from network); 9 Nov 2017 16:53:41 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=5846.5a048815.k1711; bh=b6fp9pVmAR0sU2n7bNogfU6aMrPmCM82yxqSB5dD4tk=; b=PpRBbpMLqKfAwFtVGWjjyzROa+EV4siTOvn7T264Csmo8J8qiB6zIMAyqSL2mg+KAKS7gol+ZUVzvyeNTrJl85NZQQ7sxbgFnvjpUwz23bmvTxCqP54bkIaIQntzKtY/FmCZNHQs2QTvop9RuJNOXxgChj9Q7Y3KAtLep9AGl0MLf5S+Lo/lBJPfo4/Y03D39l6de2/JMhEzQ4HG25hqxa1hDKGyx5YfbaK45HGKM57UPoGPwjvtU23ZND5CdfwR
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=5846.5a048815.k1711; bh=b6fp9pVmAR0sU2n7bNogfU6aMrPmCM82yxqSB5dD4tk=; b=Cx4GVw9lbZTSBj+khAApyh6OTDL4d4O3lFmaRPkhBLpntIpc+cj92AnKCSp/mUwQS/2HI1FYnKyoj6sheJL7LbytDgYN5j8bS2xa8okjOARYafqYSViVHPV+VT8LfY4Tgg4mdNc+d1+IOXNSVw9TNAzbGUj9uiZBN8ZJ+hWpTKvMbHKClyDB+oDy+UEvncgkS564iR1phWdCGDOjnEWGdRI3ZNhMRYOxE8u9Iic4Z3QV/3EFLVM9hkDVL1vpx73v
Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2/X.509/AEAD) via TCP6; 09 Nov 2017 16:53:41 -0000
Date: 9 Nov 2017 11:53:40 -0500
Message-ID: <alpine.OSX.2.21.1711091150580.3682@ary.qy>
From: "John R Levine" <johnl@taugh.com>
To: "Phillip Hallam-Baker" <phill@hallambaker.com>
Cc: "SPASM" <spasm@ietf.org>
In-Reply-To: <CAMm+LwhVPymZ3-3fmMY1onOFykfcVfy8rGxSPGB0FAddt2WTiQ@mail.gmail.com>
References: <CAMm+LwgMkSq7xVhVe_tYs7t46qmB9iVs92_SM3MOMeFCqWinbA@mail.gmail.com> <20171109162941.3670.qmail@ary.lan> <CAMm+LwhVPymZ3-3fmMY1onOFykfcVfy8rGxSPGB0FAddt2WTiQ@mail.gmail.com>
User-Agent: Alpine 2.21 (OSX 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/spasm/nOHPDB5KWCcE2fLgJT-eVZoZcLI>
Subject: Re: [lamps] DNS DNAME pain.
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Nov 2017 16:53:44 -0000

On Thu, 9 Nov 2017, Phillip Hallam-Baker wrote:
>> DNAME only maps names below it, so the CAA is fine.
>
> That is my understanding from the text, the example suggests
> otherwise. I would like to check that the old behavior of not matching
> the root is still valid.

It hasn't changed.  For a long time the .CAT domain made a poor attempt to 
map ASCII and accented versions of names using DNAME, and I found out all 
about DNAME+other stuff.

>> There's a BNAME proposal kicking around that is sort of a combined
>> CNAME and DNAME, mapping everything at and below the name.  Or do you
>> mean something else like a translucent DNAME that only maps if there's
>> nothing at the actual name?
>
> I am aware that there have been proposals circulating, I have not been
> tracking them directly. They seem to always be about to happen in a
> year or two.

BNAME is going nowhere because it doesn't solve the problem it's supposed 
to solve, mapping variant names together.  If you want, say, a pair of 
traditional and simplified Chinese names to act the same, you have far 
more work provisioning web and mail servers than the DNS.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail. https://jl.ly