Re: [dnsext] loads of TXT records for fun and profit

"John Levine" <johnl@taugh.com> Sat, 04 May 2013 01:48 UTC

Return-Path: <johnl@iecc.com>
X-Original-To: dnsext@ietfa.amsl.com
Delivered-To: dnsext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C6A8921F8F69 for <dnsext@ietfa.amsl.com>; Fri, 3 May 2013 18:48:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.549
X-Spam-Level:
X-Spam-Status: No, score=-110.549 tagged_above=-999 required=5 tests=[AWL=0.650, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QnUbkWgdwSeK for <dnsext@ietfa.amsl.com>; Fri, 3 May 2013 18:48:51 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 6AD9421F8F44 for <dnsext@ietf.org>; Fri, 3 May 2013 18:48:50 -0700 (PDT)
Received: (qmail 40976 invoked from network); 4 May 2013 01:48:47 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 4 May 2013 01:48:47 -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=518468ff.xn--9vv.k1305; i=johnl@user.iecc.com; bh=GBYcMjWZ55X4mhHzKm+/Ytzb3vlaiF6R/JQsojlU5fs=; b=kBMCIIynYlChV9pYvzRKsxbhZWt3RuRel4oh6NDzNP1f469c68D8AcrNrFOPHuCgB4UGKd2OUf68NAKwQWOQhGHQef7p9VizxP6Zct8Z7p1omMsDvZ8vUqVFJ8c67oY32ccpj1HG+3E63hNc7bBQLbE+mLwBRmKt/CXFA32ipdg=
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=518468ff.xn--9vv.k1305; olt=johnl@user.iecc.com; bh=GBYcMjWZ55X4mhHzKm+/Ytzb3vlaiF6R/JQsojlU5fs=; b=p/9GneuHv/4esECMtslEgeoHOgFn0xg2BQ83eEKTLAZyjfPvZtTfmndcf83Tyo4gPGF0N4F9s9AzQz7crFggdVOey/2LJWsZ/5A3s/6bx4KnuM7c+tr9QYkHYSeMcYawMrjzX0zCeBVw3ia/EhynZKbv+4ZWcUrlzw76nGoRwf8=
Date: Sat, 04 May 2013 01:48:25 -0000
Message-ID: <20130504014825.42875.qmail@joyce.lan>
From: John Levine <johnl@taugh.com>
To: dnsext@ietf.org
In-Reply-To: <51843A93.3010109@dougbarton.us>
Organization:
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Subject: Re: [dnsext] loads of TXT records for fun and profit
X-BeenThere: dnsext@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: DNS Extensions working group discussion list <dnsext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsext>, <mailto:dnsext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsext>
List-Post: <mailto:dnsext@ietf.org>
List-Help: <mailto:dnsext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsext>, <mailto:dnsext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 04 May 2013 01:48:55 -0000

>> No, that section is all about having a single TXT RR whose complete
>> content doesn't fit in 255 characters.  It illustrates how to achieve
>> this within a single RR in zone file format.
>
>... which doesn't prevent people from splitting them across multiple 
>records.

Section 3.1.2 of RFC 4408 forbids an SPF checker from looking at
multiple records at the same name.  Section 3.2 of the current draft
has the same language.  SPF has to forbid multiple records at the same
name, since their semantics are obviously impossible to define.

A single TXT record can, of course, contain any number of strings and
can be arbitrarily long.  See RFC 1035 sec 3.3.14.

Is there some reason it's preferable to guess rather than reading the
spec?

R's,
John