IETF Logo Mail Archive

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

Andrew Sullivan <ajs@shinkuro.com> Sun, 25 July 2010 20:21 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 0CCC63A67C0; Sun, 25 Jul 2010 13:21:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.259
X-Spam-Level: **
X-Spam-Status: No, score=2.259 tagged_above=-999 required=5 tests=[BAYES_20=-0.74, FH_RELAY_NODNS=1.451, HELO_MISMATCH_INFO=1.448, 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 XrKZ4oxM-CNk; Sun, 25 Jul 2010 13:21:38 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 396973A6765; Sun, 25 Jul 2010 13:21:38 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.72 (FreeBSD)) (envelope-from <owner-namedroppers@ops.ietf.org>) id 1Od7e3-000B95-2W for namedroppers-data0@psg.com; Sun, 25 Jul 2010 20:17:59 +0000
Received: from [208.86.224.201] (helo=mail.yitter.info) by psg.com with esmtps (TLSv1:CAMELLIA256-SHA:256) (Exim 4.72 (FreeBSD)) (envelope-from <ajs@shinkuro.com>) id 1Od7e0-000B8b-J3 for namedroppers@ops.ietf.org; Sun, 25 Jul 2010 20:17:56 +0000
Received: from crankycanuck.ca (cp820467-a.ndwrt1.lb.home.nl [84.30.38.160]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.yitter.info (Postfix) with ESMTPSA id 408AB1ECB41F for <namedroppers@ops.ietf.org>; Sun, 25 Jul 2010 20:17:55 +0000 (UTC)
Date: Sun, 25 Jul 2010 16:17:52 -0400
From: Andrew Sullivan <ajs@shinkuro.com>
To: namedroppers@ops.ietf.org
Subject: Re: [dnsext] URI RRTYPE review - Comments period end Aug 15th
Message-ID: <20100725201752.GB8017@shinkuro.com>
References: <20100725184119.GA42253@registro.br> <4C4C8FE8.8090305@knipp.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <4C4C8FE8.8090305@knipp.de>
User-Agent: Mutt/1.5.18 (2008-05-17)
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/>

No hat

On Sun, Jul 25, 2010 at 09:26:32PM +0200, Klaus Malorny wrote:
>
> dumb question: I don't consider myself an expert in that respect, but 
> wouldn't it make more sense nowadays to use UTF-8 encoded IRIs (RFC 3987) 
> instead of URIs? Or is there a need to keep everything ASCII-safe?

My impression anyway is that IRIs are being updated, so in that case
it'd be better to wait for the update.  But of course, we could add
another RRTYPE for IRIs once the update is available, I guess, and do
URIs now.

A

-- 
Andrew Sullivan
ajs@shinkuro.com
Shinkuro, Inc.

v2.23.0 | Report a Bug | By Email