Re: [DNSOP] RFC 8482 (the ANY -> HINFO hack) and DNAME

"John Levine" <johnl@taugh.com> Sat, 16 November 2019 14:41 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 E4870120131 for <dnsop@ietfa.amsl.com>; Sat, 16 Nov 2019 06:41:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.751
X-Spam-Level:
X-Spam-Status: No, score=-1.751 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_HELO_NONE=0.001, 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=kRoEHvsA; dkim=pass (1536-bit key) header.d=taugh.com header.b=M1yUlRqp
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 bBq2fUaFdLGI for <dnsop@ietfa.amsl.com>; Sat, 16 Nov 2019 06:41:55 -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 89C7112012D for <dnsop@ietf.org>; Sat, 16 Nov 2019 06:41:55 -0800 (PST)
Received: (qmail 81399 invoked from network); 16 Nov 2019 14:41:54 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=13df5.5dd00ab2.k1911; i=printer-iecc.com@submit.iecc.com; bh=RyBwnDVmE3FVOJ/cteEO+QraFkkZNuhuMfWcTkUpVQs=; b=kRoEHvsAXijN/JPICpOqdZ2eIUegVQc7a7Zm+Byrf/VbB9Yi73rRGZwvNNBreDzPJ+axNTqpmjSUTPPbsPGRadz/Mhze7qMpT5ndbD6wRKpwamK/26386mJ/IrjbpT2uMCgFxEmlqYLQ494x2Wx589dxChnIzzvu/PMOXYRPsbDovYSknfVpkEIclhfESNFIqdvLmkp6r6A30mBL9HStSaL6Rhzl/tVCdArFpiBxauhaBS+wJUtMP6aIkld9PUuS
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=13df5.5dd00ab2.k1911; olt=printer-iecc.com@submit.iecc.com; bh=RyBwnDVmE3FVOJ/cteEO+QraFkkZNuhuMfWcTkUpVQs=; b=M1yUlRqpC9q5mcog0BLvwAsSf1WPk/3Ed1gPn2nIdFfIP6/8n4rJ6smZ4d+NvcXykE2el3lhKOSJSB73b4DzIhipEWDRO/oLGyiXJDkUD/EGjTYeXQZm1RKHaxKYb2iv5mNrDBlxiZrO84sMfAikelVxGMAWMES/mCZeT1nZt614JfM7SKnnjpfS3GgJp3TTxVoyQzx97QPx5XSywoeXrgxlXZha/7ZT4WcPs9p33vx1KESfv9mPKc0eKELul4lo
Received: from ary.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPSA (TLS1.2 ECDHE-RSA AES-256-GCM AEAD, printer@iecc.com) via TCP6; 16 Nov 2019 14:41:54 -0000
Received: by ary.iecc.com (Postfix, from userid 501) id 0AB3DF61257; Sat, 16 Nov 2019 22:41:51 +0800 (+08)
Date: 16 Nov 2019 22:41:51 +0800
Message-Id: <20191116144152.0AB3DF61257@ary.iecc.com>
From: "John Levine" <johnl@taugh.com>
To: dnsop@ietf.org
In-Reply-To: <6BB18D2F-4701-41CF-9B50-9EE8541ED688@dukhovni.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/JzJBdTqUxa_uadckRHVj-ZpfVAs>
Subject: Re: [DNSOP] RFC 8482 (the ANY -> HINFO hack) and DNAME
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: Sat, 16 Nov 2019 14:41:57 -0000

In article <6BB18D2F-4701-41CF-9B50-9EE8541ED688@dukhovni.org> you write:
>> On Nov 14, 2019, at 1:50 PM, John Levine <johnl@taugh.com> wrote:
>> 
>> PS: I'm also coming to the conclusion that if you think DNAME solves
>> your problem, and your problem isn't the arcane IPv6 rDNS renumbering
>> for which it was invented, you don't understand DNAME.
>
>As you may recall,
>
>   http://mailarchive.ietf.org/arch/msg/dnsop/adrEUoWPq1EoxonkvcCJCnEkcFg
>
>the .tw registry employs a DNAME to identify their traditional and simplified
>Chinese IDN TLDs (simplified is a DNAME alias for traditional). ...

I know.  I'm wondering how many of those DNAME'd names actually work.

Remember that it's invalid for an NS or MX to point to a CNAME so I assume
it's equally invalid for them to point to a DNAME.