Re: [dnsext] URI RRTYPE review - Comments period end Aug 15th

Patrik Fältström <paf@cisco.com> Mon, 11 October 2010 14:18 UTC

Return-Path: <owner-namedroppers@ops.ietf.org>
X-Original-To: ietfarch-dnsext-archive@core3.amsl.com
Delivered-To: ietfarch-dnsext-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0E8C73A6A94; Mon, 11 Oct 2010 07:18:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.224
X-Spam-Level:
X-Spam-Status: No, score=-4.224 tagged_above=-999 required=5 tests=[AWL=-1.925, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GBcWcHM-g6VJ; Mon, 11 Oct 2010 07:18:21 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id DEE493A6A95; Mon, 11 Oct 2010 07:18:20 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.72 (FreeBSD)) (envelope-from <owner-namedroppers@ops.ietf.org>) id 1P5J6T-0009n8-Bk for namedroppers-data0@psg.com; Mon, 11 Oct 2010 14:11:49 +0000
Received: from ams-iport-2.cisco.com ([144.254.224.141]) by psg.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.72 (FreeBSD)) (envelope-from <paf@cisco.com>) id 1P5J6Q-0009mi-Jf for namedroppers@ops.ietf.org; Mon, 11 Oct 2010 14:11:47 +0000
Authentication-Results: ams-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AmcEAEu4skyQ/khNgWdsb2JhbACiDRUBARYiIqN6nDCFSASKQQ
X-IronPort-AV: E=Sophos;i="4.57,314,1283731200"; d="scan'208";a="11093385"
Received: from ams-core-4.cisco.com ([144.254.72.77]) by ams-iport-2.cisco.com with ESMTP; 11 Oct 2010 14:11:44 +0000
Received: from ams3-vpn-dhcp5444.cisco.com (ams3-vpn-dhcp5444.cisco.com [10.61.85.67]) by ams-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id o9BEBXcR012952; Mon, 11 Oct 2010 14:11:44 GMT
Subject: Re: [dnsext] URI RRTYPE review - Comments period end Aug 15th
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset="us-ascii"
From: Patrik Fältström <paf@cisco.com>
In-Reply-To: <87y6cy955x.fsf@mid.deneb.enyo.de>
Date: Mon, 11 Oct 2010 15:03:15 +0200
Cc: namedroppers@ops.ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <45711F9C-BA11-40D1-8B1B-57A950191D6C@cisco.com>
References: <20100725184119.GA42253@registro.br> <87y6cy955x.fsf@mid.deneb.enyo.de>
To: Florian Weimer <fw@deneb.enyo.de>
X-Mailer: Apple Mail (2.1081)
Sender: owner-namedroppers@ops.ietf.org
Precedence: bulk
List-ID: <namedroppers.ops.ietf.org>
List-Unsubscribe: To unsubscribe send a message to namedroppers-request@ops.ietf.org with
List-Unsubscribe: the word 'unsubscribe' in a single line as the message text body.
List-Archive: <http://ops.ietf.org/lists/namedroppers/>

On 26 jul 2010, at 07.35, Florian Weimer wrote:

> * Frederico A. C. Neves:
> 
>>     The wire format of the RDATA is as follows:
>> 
>> 
>>                         1 1 1 1 1 1 1 1 1 1 2 2 2 2 2 2 2 2 2 2 3 3
>>     0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
>>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>    |          Priority             |          Weight               |
>>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>    /                                                               /
>>    /                             Target                            /
>>    /                                                               /
>>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> 
> Would it make sense to include an "insert original domain here"
> placeholder in the target part?  This would help with aliasing.

I am working on an update to this document given the comments on the mailing list.

For this issue, to have some rewrite rules for the URI, I pushed back slightly on the mailing list, and I interpret your response to that (Florian) as if you agree it is dangerous.

My take is, given noone else ask for this, that such rewrite should not happen.

Because of this, I will not include any change because of this comment in the upcoming release.

   Patrik