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

David Miller <dmiller@tiggee.com> Sat, 04 May 2013 03:57 UTC

Return-Path: <dmiller@tiggee.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 B8B0A21F88D8 for <dnsext@ietfa.amsl.com>; Fri, 3 May 2013 20:57:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 u4OdVuQHeJTc for <dnsext@ietfa.amsl.com>; Fri, 3 May 2013 20:57:00 -0700 (PDT)
Received: from smtp1.tiggee.com (smtp1.tiggee.com [208.94.147.35]) by ietfa.amsl.com (Postfix) with ESMTP id 6C28D21F8551 for <dnsext@ietf.org>; Fri, 3 May 2013 20:57:00 -0700 (PDT)
Message-ID: <5184870C.5020904@tiggee.com>
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=tiggee.com; s=dkprod2001; t=1367639819; bh=Zpvt3D/ul5V3rF6x5GaFgw1laPgVClIPl+H9 5qY6or0=; h=DomainKey-Signature:Date:From:User-Agent:MIME-Version: To:Subject:References:In-Reply-To:X-Enigmail-Version:Content-Type: Content-Transfer-Encoding; b=Uszi0GS7Y8PalmuCZF0Z1TEINS8v9p1j9N6W6 aimuJc4N7VTUhcJ9IEx9JWCdOQ5rlm3cNXSZ8PV+Oxp0tvn0IZiVZ692P86QE6nA86E 0ayQqT3QRuVnenxXjnIelsi0tdyT/CjAEIn0sbjdPPeprRPVn/QWPq0yS427Ry1z3ms =
DomainKey-Signature: a=rsa-sha1; s=dkprod2001; d=tiggee.com; c=simple; q=dns; h=date:from:user-agent:mime-version:to:subject:references: in-reply-to:x-enigmail-version:content-type:content-transfer-encoding; b=SVX31yow5iW6nErfMUtL4w/JbIESM04BnUzoDNiW9Jq2wcojjQWA89WIc4iEq7uqf w5/QxivejmiDX39RYgs+VZU7zQ22ku6lwa+Ka4Cwyq+Gu6IebhTfdzlrnIQD4rnHzo6 e0obA/4jaMrlqLF4d6xNLh/I4tfy6X0FhbY0Co8=
Date: Fri, 03 May 2013 23:57:00 -0400
From: David Miller <dmiller@tiggee.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: dnsext@ietf.org
References: <20130504014825.42875.qmail@joyce.lan>
In-Reply-To: <20130504014825.42875.qmail@joyce.lan>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
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 03:57:04 -0000

On 5/3/2013 9:48 PM, John Levine wrote:
>>> 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.

TXT records don't have a specified maximum length, but they cannot be
arbitrarily long.  They have to fit into an RR.  RDLENGTH, which
specifies the length of the RDATA field, is an unsigned 16 bit integer
(max 65535).  See RFC 1035 sec 3.2.1.

64k is very long, but not arbitrarily long.

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

-DMM