IETF Logo Mail Archive

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

Patrik Fältström <paf@cisco.com> Mon, 26 July 2010 07:07 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 4C6473A69F4; Mon, 26 Jul 2010 00:07:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.186
X-Spam-Level:
X-Spam-Status: No, score=-9.186 tagged_above=-999 required=5 tests=[AWL=-0.991, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_HI=-8, RDNS_NONE=0.1]
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 RtUf0czDy4mm; Mon, 26 Jul 2010 00:07:26 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 4E6993A69D5; Mon, 26 Jul 2010 00:07:25 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.72 (FreeBSD)) (envelope-from <owner-namedroppers@ops.ietf.org>) id 1OdHgx-0007it-UL for namedroppers-data0@psg.com; Mon, 26 Jul 2010 07:01:39 +0000
Received: from [64.102.122.149] (helo=rtp-iport-2.cisco.com) by psg.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.72 (FreeBSD)) (envelope-from <paf@cisco.com>) id 1OdHgt-0007i7-IP for namedroppers@ops.ietf.org; Mon, 26 Jul 2010 07:01:35 +0000
Authentication-Results: rtp-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none
X-Files: PGP.sig : 186
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAMfPTExAZnwN/2dsb2JhbACfYHGlBJl7hTYEiGQ
X-IronPort-AV: E=Sophos; i="4.55,260,1278288000"; d="sig'?scan'208"; a="139104754"
Received: from rtp-core-2.cisco.com ([64.102.124.13]) by rtp-iport-2.cisco.com with ESMTP; 26 Jul 2010 07:01:34 +0000
Received: from dhcp-10-55-91-144.cisco.com (dhcp-10-55-91-144.cisco.com [10.55.91.144]) by rtp-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id o6Q71X2n006154; Mon, 26 Jul 2010 07:01:34 GMT
Subject: Re: [dnsext] URI RRTYPE review - Comments period end Aug 15th
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg="pgp-sha1"; boundary="Apple-Mail-435--974700954"
From: Patrik Fältström <paf@cisco.com>
In-Reply-To: <87y6cy955x.fsf@mid.deneb.enyo.de>
Date: Mon, 26 Jul 2010 09:01:33 +0200
Cc: namedroppers@ops.ietf.org
Content-Transfer-Encoding: 7bit
Message-Id: <CF0277A9-3D72-449F-A1F3-F77BB668F3EB@cisco.com>
References: <20100725184119.GA42253@registro.br> <87y6cy955x.fsf@mid.deneb.enyo.de>
To: Florian Weimer <fw@deneb.enyo.de>
X-Pgp-Agent: GPGMail 1.2.3
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.

You talk about a subset of the NAPTR regexp now are you not...

http://cloud-4711.example.com/${domain}/foo/bar

The problem with any such thing is that you immediately end up in a discussion on how to encode the '$' that should be in the URI.

   Patrik

v2.23.0 | Report a Bug | By Email