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

Phillip Hallam-Baker <hallam@gmail.com> Fri, 03 May 2013 14:22 UTC

Return-Path: <hallam@gmail.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 2854121F87E0 for <dnsext@ietfa.amsl.com>; Fri, 3 May 2013 07:22:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.438
X-Spam-Level:
X-Spam-Status: No, score=-2.438 tagged_above=-999 required=5 tests=[AWL=0.162, BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
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 YlQq47MgSW9H for <dnsext@ietfa.amsl.com>; Fri, 3 May 2013 07:22:51 -0700 (PDT)
Received: from mail-we0-x232.google.com (mail-we0-x232.google.com [IPv6:2a00:1450:400c:c03::232]) by ietfa.amsl.com (Postfix) with ESMTP id E0AB721F919D for <dnsext@ietf.org>; Fri, 3 May 2013 07:22:50 -0700 (PDT)
Received: by mail-we0-f178.google.com with SMTP id t11so1317761wey.23 for <dnsext@ietf.org>; Fri, 03 May 2013 07:22:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=DMnJ2WDk6M7eS5IokmcjWpCbX59vw16/ZZBUTB+DYC4=; b=iJVo6XjKZNIGWIXV7Rrykf7p1nVy5kF8tehkn2H5QxsThaepvkGVI7fwHa1EPsW4Xs i0cipnuLY4ufwgcCeMgRgbypW04FTn7IsFo2ELkbIE+xJwMxD1z6LVf0uqQONC23K91s tOjGqOJtdU8ut/g+dmokUlci8cg2wA3SikgG/qZk7c0Im6JfRJt13+qs1nzpc68nsmDE 2sAPcYHqMUMxWwyqWM72aSpZt7hGognzETooTmW69S/GrqvPMHE4QRhbYlbEiuj17gTt 8QnnGhfdY1g5Flh8z6XgpkkJ1ofiS6UzCGySqXd2YAZypjrx8OFlUUr+UF7THkdSB9h1 njig==
MIME-Version: 1.0
X-Received: by 10.194.62.174 with SMTP id z14mr14271189wjr.20.1367590970018; Fri, 03 May 2013 07:22:50 -0700 (PDT)
Received: by 10.194.121.161 with HTTP; Fri, 3 May 2013 07:22:49 -0700 (PDT)
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B63077516EA82@mbx-01.win.nominum.com>
References: <20130425013317.36729.qmail@joyce.lan> <80ADB3EE-17FD-4628-B818-801CB71BCBFE@virtualized.org> <alpine.BSF.2.00.1304242309150.38677@joyce.lan> <46778ED3-35A2-44B4-BE3C-AAC4F7B314FF@virtualized.org> <92BBD83F-676D-4B05-B927-4101DD5CAD3E@neustar.biz> <DC121025-A014-492B-AFAD-22CDE49D866E@rfc1035.com> <CAMm+Lwi4MAjX8BAk_ro9usf6AJo=1UERhGBJ1rUa-AbrX09dqg@mail.gmail.com> <E5E3F801-6490-48A8-A12F-A6561893D78A@icsi.berkeley.edu> <CAMm+LwhqwT+9sqH5K4fJP3sUhmaTuPBMq8zE+4BdaTgBem9QDw@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B63077516EA82@mbx-01.win.nominum.com>
Date: Fri, 03 May 2013 10:22:49 -0400
Message-ID: <CAMm+LwjV1FP_FzqDs2LofY3omy=rioFNA27zzPtxqM_7JhUt3A@mail.gmail.com>
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
Content-Type: multipart/alternative; boundary="047d7b86d6d8f751ad04dbd115ce"
Cc: "dnsext@ietf.org" <dnsext@ietf.org>
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: Fri, 03 May 2013 14:22:52 -0000

The syntax of the record is an editor war.

There are arguments to be made in favor of a compact representation but the
IETF has traditionally favored verbose text headers over compact
representations for anything above the application layer.

If the WG wants to influence design choices then they have to provide an
infrastructure that supports the requirements that the applications area
people assert. Instead the interaction with this group has been that apps
area people say that they need X and this group tells them that they are
wrong. And that is not a productive way to go forward.

What it really comes down to is what the DNS server maintainers are willing
to support. Adding new RR types to my code is easy as I generate all the
code for parsing/emitting the RR data. The same is not true for BIND and
the other servers.


But for most applications, packing/unpacking binary DNS records really does
not help at all unless there is 1024-2048 bits worth of opaque binary data
involved. Which means that the only records for which binary format really
makes a difference tend to be records that involve PKI in some way.



On Fri, May 3, 2013 at 10:03 AM, Ted Lemon <Ted.Lemon@nominum.com> wrote:

>  On May 3, 2013, at 9:57 AM, Phillip Hallam-Baker <hallam@gmail.com
> > wrote:
>
> Now what could make the whole process a lot easier would be to allocate a
> band of DNS RR codes for records that would all have TXT syntax. That would
> allow BIND etc. to make one change to support the new syntax. Alternatively
> we could extend the handling of unknown RR syntax so that there was a
> string presentation option.
>
>
> I see some benefit in that if in fact TXT is the right format for storing
> the things that would get stored in these records.   However, the point has
> been made with respect to SPF that it would have been better had it not
> been just a text record.   I don't know whether this argument is correct or
> not, but if it is correct, making it easy to put in TXT records and hard to
> put in anything else is probably going to make things worse, not better.
>
>


-- 
Website: http://hallambaker.com/