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

Ted Lemon <Ted.Lemon@nominum.com> Fri, 03 May 2013 14:03 UTC

Return-Path: <Ted.Lemon@nominum.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 EC62021F9625 for <dnsext@ietfa.amsl.com>; Fri, 3 May 2013 07:03:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.593
X-Spam-Level:
X-Spam-Status: No, score=-106.593 tagged_above=-999 required=5 tests=[AWL=0.005, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, 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 30L66nNf4+6q for <dnsext@ietfa.amsl.com>; Fri, 3 May 2013 07:03:32 -0700 (PDT)
Received: from exprod7og128.obsmtp.com (exprod7og128.obsmtp.com [64.18.2.121]) by ietfa.amsl.com (Postfix) with ESMTP id 0815821F962D for <dnsext@ietf.org>; Fri, 3 May 2013 07:03:31 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob128.postini.com ([64.18.6.12]) with SMTP ID DSNKUYPDs+JL7IavZa3OXN0tUrs3tJY8fQdK@postini.com; Fri, 03 May 2013 07:03:32 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 6F6E81B80F4 for <dnsext@ietf.org>; Fri, 3 May 2013 07:03:31 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 66994190061; Fri, 3 May 2013 07:03:31 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.02.0318.004; Fri, 3 May 2013 07:03:26 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Phillip Hallam-Baker <hallam@gmail.com>
Thread-Topic: [dnsext] loads of TXT records for fun and profit
Thread-Index: AQHOROzyhfjGSq7i9UmyqVzThMYc8Jjz0ggAgAAa0oCAAAsOgIAAAYuA
Date: Fri, 03 May 2013 14:03:26 +0000
Message-ID: <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>
In-Reply-To: <CAMm+LwhqwT+9sqH5K4fJP3sUhmaTuPBMq8zE+4BdaTgBem9QDw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [192.168.1.10]
Content-Type: multipart/alternative; boundary="_000_8D23D4052ABE7A4490E77B1A012B63077516EA82mbx01winnominum_"
MIME-Version: 1.0
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:03:41 -0000

On May 3, 2013, at 9:57 AM, Phillip Hallam-Baker <hallam@gmail.com<mailto: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.