IETF Logo Mail Archive

Re: Unicode newsgroup name options

Simon Josefsson <simon+ietf-822@josefsson.org> Sun, 23 February 2003 06:46 UTC

Received: (from majordomo@localhost) by above.proper.com (8.11.6/8.11.3) id h1N6k9l28849 for ietf-822-bks; Sat, 22 Feb 2003 22:46:09 -0800 (PST)
Received: from nixon.xkey.com (h42-rt.sv.meer.net [205.217.153.42]) by above.proper.com (8.11.6/8.11.3) with SMTP id h1N6jvd28803 for <ietf-822@imc.org>; Sat, 22 Feb 2003 22:45:58 -0800 (PST)
Received: (qmail 21894 invoked by uid 1087); 23 Feb 2003 06:45:49 -0000
MBOX-Line: From owner-ietf-822@mail.imc.org Sat Feb 22 15:03:05 2003
Delivered-To: dan@xkey.com
Received: (qmail 25570 invoked from network); 22 Feb 2003 23:03:05 -0000
Received: from ns11.dnsprotect.com (HELO velocity.dnsprotect.com) (209.50.252.235) by h42-rt.sv.meer.net with SMTP; 22 Feb 2003 23:03:05 -0000
Received: from mail.proper.com ([208.184.76.45] helo=above.proper.com) by velocity.dnsprotect.com with esmtp (Exim 3.36 #1) id 18mieh-00013P-00 for dan@dankohn.com; Sat, 22 Feb 2003 18:02:03 -0500
Received: (from majordomo@localhost) by above.proper.com (8.11.6/8.11.3) id h1MMk9319105 for ietf-822-bks; Sat, 22 Feb 2003 14:46:09 -0800 (PST)
Received: from yxa.extundo.com (178.230.13.217.in-addr.dgcsystems.net [217.13.230.178]) by above.proper.com (8.11.6/8.11.3) with ESMTP id h1MMk7d19098 for <ietf-822@imc.org>; Sat, 22 Feb 2003 14:46:07 -0800 (PST)
Received: from latte.josefsson.org (yxa.extundo.com [217.13.230.178]) (authenticated bits=0) by yxa.extundo.com (8.12.7/8.12.7) with ESMTP id h1MMk6Xf018384 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=OK); Sat, 22 Feb 2003 23:46:07 +0100
Old-To: kaih@khms.westfalen.de (Kai Henningsen)
Cc: usenet-format@landfield.com, ietf-822@imc.org
Subject: Re: Unicode newsgroup name options
X-Payment: hashcash 1.1 0:030222:kaih@khms.westfalen.de:e7d91cfa31f06de9
X-Hashcash: 0:030222:kaih@khms.westfalen.de:e7d91cfa31f06de9
X-Payment: hashcash 1.1 0:030222:usenet-format@landfield.com:3d88fd9b6bb9a501
X-Hashcash: 0:030222:usenet-format@landfield.com:3d88fd9b6bb9a501
X-Payment: hashcash 1.1 0:030222:ietf-822@imc.org:8b89bbb423cc2485
X-Hashcash: 0:030222:ietf-822@imc.org:8b89bbb423cc2485
From: Simon Josefsson <simon+ietf-822@josefsson.org>
Date: Sat, 22 Feb 2003 23:46:06 +0100
In-Reply-To: <8gKr5UIXw-B@khms.westfalen.de> (kaih@khms.westfalen.de's message of "22 Feb 2003 23:10:00 +0200")
Message-ID: <iluof547x3l.fsf@latte.josefsson.org>
User-Agent: Gnus/5.090016 (Oort Gnus v0.16) Emacs/21.3.50
References: <yl7kbu7au6.fsf@windlord.stanford.edu> <yl7kbt475y.fsf@windlord.stanford.edu> <Pine.LNX.4.55.0302211423000.9666@shiva1.cac.washington.edu> <Pine.LNX.4.55.0302211423000.9666@shiva1.cac.washington.edu> <01KSPHV89YF2002O3W@mauve.mrochek.com> <8gKr5UIXw-B@khms.westfalen.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Spam-Status: No, hits=-31.7 required=5.0 tests=EMAIL_ATTRIBUTION, FROM_ENDS_IN_NUMS, IN_REP_TO, QUOTED_EMAIL_TEXT, REFERENCES, REPLY_WITH_QUOTES, USER_AGENT_GNUS_UA autolearn=ham version=2.50
X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp)
List-Archive: <http://www.imc.org/ietf-822/mail-archive/>
List-ID: <ietf-822.imc.org>
List-Unsubscribe: <mailto:ietf-822-request@imc.org?body=unsubscribe>
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - velocity.dnsprotect.com
X-AntiAbuse: Original Domain - dankohn.com
X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [0 0]
X-AntiAbuse: Sender Address Domain - mail.imc.org
Status: O
To: dmk@skymv.com
Sender: owner-ietf-822@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-822/mail-archive/>
List-ID: <ietf-822.imc.org>
List-Unsubscribe: <mailto:ietf-822-request@imc.org?body=unsubscribe>

kaih@khms.westfalen.de (Kai Henningsen) writes:

>> I also note that Dan Kohn's alternative News Article Format draft uses
>> punycode, which already includes a stringprep profile.
>
> Some detective work finds draft-ietf-idn-nameprep-11.txt (that *is* the  
> current one, yes?). We obviously can't use a profile that says it must be  
> used together with extra restrictions specific to IDN, but otherwise it  
> seems that we could mostly just copy this one ... except shouldn't these  
> profiles be reusable?

Yes.  Using nameprep for usefor is a bad idea, but the contents of
nameprep can be copied, renamed, polished, and then, IMHO, it would
turn into a good idea.

> It's hard to figure this out by looking at current registrations (as  
> recommended by the stringprep RFC, 2454) if there aren't any.

There are a few drafts with stringprep profile, here are links to
those I'm familiar with.  Note that most of them contain some minor
technical problems.

http://www.ietf.org/internet-drafts/draft-ietf-idn-nameprep-11.txt
http://www.ietf.org/internet-drafts/draft-ietf-xmpp-nodeprep-00.txt
http://www.ietf.org/internet-drafts/draft-ietf-xmpp-resourceprep-00.txt
http://www.ietf.org/internet-drafts/draft-ietf-sasl-anon-00.txt
http://www.ietf.org/internet-drafts/draft-ietf-ips-iscsi-string-prep-03.txt

v2.23.0 | Report a Bug | By Email