IETF Logo Mail Archive

Re: [DNSOP] Proposal for a new record type: SNI

"John Levine" <johnl@taugh.com> Tue, 14 February 2017 22:19 UTC

Return-Path: <johnl@taugh.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 3F01B129863 for <dnsop@ietfa.amsl.com>; Tue, 14 Feb 2017 14:19:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 PB6T4PcMOjVs for <dnsop@ietfa.amsl.com>; Tue, 14 Feb 2017 14:19:48 -0800 (PST)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DD0BC1294BA for <dnsop@ietf.org>; Tue, 14 Feb 2017 14:19:47 -0800 (PST)
Received: (qmail 4456 invoked from network); 14 Feb 2017 22:19:47 -0000
Received: from unknown (64.57.183.18) by mail1.iecc.com with QMQP; 14 Feb 2017 22:19:47 -0000
Date: Tue, 14 Feb 2017 22:19:25 -0000
Message-ID: <20170214221925.15515.qmail@ary.lan>
From: John Levine <johnl@taugh.com>
To: dnsop@ietf.org
In-Reply-To: <20170214203924.5c4v6l5b3bjipcfw@mycre.ws>
Organization:
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/iE8yCs3sx190u3pNidnrw9HR35I>
Cc: edmonds@mycre.ws
Subject: Re: [DNSOP] Proposal for a new record type: SNI
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.17
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, 14 Feb 2017 22:19:49 -0000

In article <20170214203924.5c4v6l5b3bjipcfw@mycre.ws> you write:
>   We could encode this information in a TXT record, but that would
>   violate the intended purpose of TXT records: to convey information to
>   human readers.
>
>I'm not sure if it's true that TXT records are intended only for human
>consumption. TXT RRs contain "descriptive text" where "[t]he semantics
>of the text depends on the domain where it is found".

That horse left the barn at least a decade ago, before SPF, DKIM,
DMARC, and a lot of other TXT records primarily intended to be
consumed by computers.  Humans can read them, but this human can't do
much with records like this:

taugh.com. IN TXT "google-site-verification=7SCAvuZtE7dOCpG0drHDEBOqco9JnPzFUIUBSgU3eWc"

Whether to use a TXT record is of course a subsidiary question to
whether DNS SNI indirection is a good idea in the first place.

R's,
John

v2.23.0 | Report a Bug | By Email