Re: An IANA Registry for DNS TXT RDATA (I-D Action: draft-klensin-iana-txt-rr-registry-00.txt)

John C Klensin <john-ietf@jck.com> Sun, 01 September 2013 19:52 UTC

Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 92C9711E8167 for <ietf@ietfa.amsl.com>; Sun, 1 Sep 2013 12:52:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 T4ycKoc-BhNx for <ietf@ietfa.amsl.com>; Sun, 1 Sep 2013 12:52:32 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 7D7EE11E8172 for <ietf@ietf.org>; Sun, 1 Sep 2013 12:52:32 -0700 (PDT)
Received: from localhost ([::1]) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1VGDhH-000OYn-VH for ietf@ietf.org; Sun, 01 Sep 2013 15:52:32 -0400
X-Vipre-Scanned: 04591B81002C3104591CCE-TDI
Date: Sun, 01 Sep 2013 15:52:31 -0400
From: John C Klensin <john-ietf@jck.com>
To: ietf@ietf.org
Subject: Re: An IANA Registry for DNS TXT RDATA (I-D Action: draft-klensin-iana-txt-rr-registry-00.txt)
Message-ID: <2DB5A571D0F2AF43E6384B6A@[192.168.1.128]>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 01 Sep 2013 19:52:37 -0000

--On Saturday, August 31, 2013 23:50 +0900 Masataka Ohta
<mohta@necom830.hpcl.titech.ac.jp> wrote:

> The draft does not assure that existing usages are compatible
> with each other.

It absolutely does not.  I actually expect it to help identify
some usages that are at least confusing and possible
incompatible.

> Still, the draft may assure new usages compatible with each
> other.

That is the hope.

> However, people who want to have new (sub)types for the new
> usages should better simply request new RRTYPEs.

I agree completely.  But that has nothing to do with this draft:
the registry is simply addressed to uses that overload TXT, not
to arguing why they shouldn't (or why the use of label prefixes
or suffixes is sufficient to make protocol use of TXT reasonable.

> If we need subtypes because 16bit RRTYPE space is not enough
> (I don't think so), the issue should be addressed by itself
> by introducing a new RRTYPE (some considerations on subtype
> dependent caching may be helpful), not TXT, which can assure
> compatibilities between subtypes.

Again, I completely agree.  But it isn't an issue for this
proposed registry.

> For the existing usages, some informational RFC, describing
> compatibilities (or lack of them) between the existing usages,
> might help.

Yes, I think so.

thanks,
   john