Re: [lamps] DNS DNAME pain.

"John R Levine" <johnl@taugh.com> Thu, 09 November 2017 18:18 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 E5474129435 for <spasm@ietfa.amsl.com>; Thu, 9 Nov 2017 10:18:57 -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=ImWSg8m5; dkim=pass (1536-bit key) header.d=taugh.com header.b=iDOsOqdp
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 BtjaKvEePBzC for <spasm@ietfa.amsl.com>; Thu, 9 Nov 2017 10:18:56 -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 E234B129406 for <spasm@ietf.org>; Thu, 9 Nov 2017 10:18:43 -0800 (PST)
Received: (qmail 47631 invoked from network); 9 Nov 2017 18:18:42 -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=ba0c.5a049c02.k1711; bh=2aW/i0h++UHruhWRbULHPLeydO3kLDxwQCqEnQRzry4=; b=ImWSg8m5v5ZEsCWQIBNwIZG1qCE4525HzDbu51ta17GxeOLIzLK3n/iJ/8qh8xJMLI+SvfSFeoFZ182w+UEaUO6yVSWpVm8cBEQVt2iPBSSDULUe60Nt8vpYlXhlbk02asnwMFEUeTQZgxl2RK7HEmtVF/2A42gt6yW2UyNAcZVEStirkI1kbHy8RHq+aHbErouXL0TLEsOUO3dm9HCpe+p4M9EJ+lbjRM/ohvKDvv+yXvHfHJD/ywvMQh7IpbBN
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=ba0c.5a049c02.k1711; bh=2aW/i0h++UHruhWRbULHPLeydO3kLDxwQCqEnQRzry4=; b=iDOsOqdp5DIoscQHhWSUiYa2+HOWEsmAOFAI9eZHXkGwd+PRu67zxoe2MSXS1EIA927vFo02+WlKdix7pN5jPPlHxzFQkCjQZU5iypWz2P4PISzmwdWWVLqcuHK3g9gSiLj/25GVTAGUAly5qNmZKi9wEtb3zhFvzFVy7VIyFZMc15RILaCflApa1JV/WHHHTBLclkLhqsc9M2fPNMMUYhDxIPnyTZjYtMOAU6j3Ms3WIDYuugGwPsV5iISli3ZN
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 18:18:42 -0000
Date: 9 Nov 2017 13:18:42 -0500
Message-ID: <alpine.OSX.2.21.1711091315590.3847@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+Lwg4_0TS4b9DNV1K6OM7+26mYNCx9f2F=cMcQTJ8Ag7MsA@mail.gmail.com>
References: <CAMm+LwgMkSq7xVhVe_tYs7t46qmB9iVs92_SM3MOMeFCqWinbA@mail.gmail.com> <20171109162941.3670.qmail@ary.lan> <CAMm+LwhVPymZ3-3fmMY1onOFykfcVfy8rGxSPGB0FAddt2WTiQ@mail.gmail.com> <alpine.OSX.2.21.1711091150580.3682@ary.qy> <CAMm+Lwg4_0TS4b9DNV1K6OM7+26mYNCx9f2F=cMcQTJ8Ag7MsA@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/Inv4H4-f8C3StF24YLF2uqg9JGU>
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 18:18:58 -0000

>> 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.
>
> Like many other DNS proposals, the only way that can work is if the
> services are getting their configuration data from the same source of
> truth as the authoritative DNS server

That helps, but the meaning of "the same" when applied to web servers is 
pretty vague.  If you have names in different character sets or different 
languages, should the web content match the character set or language of 
the name you use?  It's a swamp.

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