IETF Logo Mail Archive

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

Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp> Thu, 05 September 2013 06:00 UTC

Return-Path: <mohta@necom830.hpcl.titech.ac.jp>
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 A04E711E8168 for <ietf@ietfa.amsl.com>; Wed, 4 Sep 2013 23:00:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.09
X-Spam-Level:
X-Spam-Status: No, score=-0.09 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
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 QCSGlxTByavR for <ietf@ietfa.amsl.com>; Wed, 4 Sep 2013 23:00:41 -0700 (PDT)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by ietfa.amsl.com (Postfix) with SMTP id 40D9811E811A for <ietf@ietf.org>; Wed, 4 Sep 2013 23:00:38 -0700 (PDT)
Received: (qmail 83473 invoked from network); 5 Sep 2013 05:55:36 -0000
Received: from necom830.hpcl.titech.ac.jp (HELO ?127.0.0.1?) (131.112.32.132) by necom830.hpcl.titech.ac.jp with SMTP; 5 Sep 2013 05:55:36 -0000
Message-ID: <52281D64.3090908@necom830.hpcl.titech.ac.jp>
Date: Thu, 05 Sep 2013 14:57:56 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: An IANA Registry for DNS TXT RDATA (I-D Action: draft-klensin-iana-txt-rr-registry-00.txt)
References: <2DB5A571D0F2AF43E6384B6A@[192.168.1.128]>
In-Reply-To: <2DB5A571D0F2AF43E6384B6A@[192.168.1.128]>
Content-Type: text/plain; charset="ISO-2022-JP"
Content-Transfer-Encoding: 7bit
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: Thu, 05 Sep 2013 06:00:46 -0000

John C Klensin wrote:

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

The problem is that an existing and an new usages may not be
compatible.

>> 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.

With a new RRTYPE, new usages are assured to be compatible with
existing TXT usages.

Thanks,

					Masataka Ohta

v2.23.0 | Report a Bug | By Email