From owner-idn@ops.ietf.org Wed Feb 5 02:15:13 2003 Received: from psg.com (mailnull@psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA28705 for ; Wed, 5 Feb 2003 02:15:13 -0500 (EST) Received: from lserv by psg.com with local (Exim 3.36 #1) id 18gJdG-000P4P-00 for idn-data@psg.com; Tue, 04 Feb 2003 23:06:06 -0800 Received: from bean.ar.com ([66.123.187.68]) by psg.com with esmtp (Exim 3.36 #1) id 18gJdE-000P4D-00 for idn@ops.ietf.org; Tue, 04 Feb 2003 23:06:04 -0800 Received: from flash.ar.com (wessorh@flash [66.123.187.80]) by bean.ar.com (8.12.6/8.12.6) with ESMTP id h15764mn013154 for ; Tue, 4 Feb 2003 23:06:04 -0800 (PST) Date: Tue, 4 Feb 2003 23:06:08 -0800 (PST) From: Rick Wesson To: Subject: [idn] punnycode in java? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Status: No, hits=0.2 required=5.0 tests=SPAM_PHRASE_00_01,USER_AGENT_PINE version=2.43 Sender: owner-idn@ops.ietf.org Precedence: bulk anyone know of a implementation of punny code in java? If I can't find a LGPL'ed version I'll go off an write one, but I wanted to check if someone else hand't done it first. thanks, -rick From owner-idn@ops.ietf.org Thu Feb 6 03:14:18 2003 Received: from psg.com (mailnull@psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA07962 for ; Thu, 6 Feb 2003 03:14:18 -0500 (EST) Received: from lserv by psg.com with local (Exim 3.36 #1) id 18gh1v-0007lX-00 for idn-data@psg.com; Thu, 06 Feb 2003 00:05:07 -0800 Received: from [2001:700:1:4::1:0] (helo=tyholt.uninett.no) by psg.com with esmtp (Exim 3.36 #1) id 18gh1p-0007kd-00 for idn@ops.ietf.org; Thu, 06 Feb 2003 00:05:02 -0800 Received: from valgrind.uninett.no (valgrind.uninett.no [IPv6:2001:700:1:4:290:27ff:fe55:4a0c] (may be forged)) by tyholt.uninett.no (8.12.6/8.12.6) with ESMTP id h1684xn4015235 for ; Thu, 6 Feb 2003 09:04:59 +0100 Received: from valgrind.uninett.no (hmg@localhost) by valgrind.uninett.no (8.11.6/8.11.6) with ESMTP id h1684x718385 for ; Thu, 6 Feb 2003 09:04:59 +0100 Message-Id: <200302060804.h1684x718385@valgrind.uninett.no> X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: idn@ops.ietf.org Subject: [idn] Using draft-jseng-idn-admin-01.txt Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Date: Thu, 06 Feb 2003 09:04:59 +0100 From: Hilde Margrethe Thunem X-Spam-Status: No, hits=0.8 required=5.0 tests=MAY_BE_FORGED,SPAM_PHRASE_00_01 version=2.43 Sender: owner-idn@ops.ietf.org Precedence: bulk Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id DAA07962 I've been looking at the "Internationalized Domain Names Registration and Administration Guideline for Chinese, Japanese and Korean" (draft-jseng-idn-admin-01.txt) It looked rather interesting as a language to express a policy in if there is characters that could be seen as variants of each other. As I'm from a Norwegian background I've looked at using the guidelines in the draft to describe an administrative domain name policy for the Norwegian language, with a language character variant table. In Norwegian there are few (if any) characters that may be said to be variants of each others in all instances where they are used. The closest we get is perhaps by dropping the accents (using o as a predominant variant of ó and ò) but as e.g. "for", "fór" and "fòr" has three different meanings (for, travelled and furrow) it is not immideately given that they should be stuck together in one IDL package. There is also certain characters that is imported fom neighbouring languages and used in Norwegian names, that sound similar in speech to already existing Norwegian characters (e.g ø and ö). These may be considered variants of each others. (And even if in the end the administrative policy is that all characthers has no variants, the draft does give a way of easily expressing both that fact, and expressing which characters are within the set of valid code points.) Having tried to use it, I have a few questions concerning the interpretation of the different groups in the language character variant table. As far as I can see the recommended variants must also be valid codepoints, and result in domain names that are in the zonefile, while character variants are merely reserved when a valid combination is registered and are not in themselves added to the zonefile. In addition, character variants that aren't valid codepoints can't be the "starting point" for an IDL package. In other words, given a language character variant table where the letters a-z is among the valid codepoints, but does not have any recommended variants or character variants (except the letter itself), and the following lines in addition: 00F8; 00F8; 00F6; 00F6; 00F8; 00F8; (ø; ø; ö; o; ø; ø;) If I've understood correctly an application for the domain name bjørn.no will result in an IDL package consisting of bjørn.no and björn.no, where bjørn.no is added to the zonefile and björn.no is reserved. (As the ø is the recommended variant, while the poor ö is just a character variant). What happens according to this policy if the domain name applied for is björn.no? Will the registered name still be bjørn.no while björn.no is reserved? And if the language table only had a-z and 00F8; 00F8; 00F6; (ø; ø; ö;) would that mean that while one could still apply for bjørn.no (and get björn.no as a reserved name), someone applying for björn.no would get rejected as that name contains a character that is not part of the valid codepoints? Sorry for asking the basic questions :-) but as the draft states, the quality of the language table is critical for the result... which means that the logic behind how the table is built is important. And while I'm asking questions, has any of you in the WG used the draft for creating a draft policy for a language? - Hilde Thunem From owner-idn@ops.ietf.org Thu Feb 6 05:23:21 2003 Received: from psg.com (mailnull@psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA11397 for ; Thu, 6 Feb 2003 05:23:21 -0500 (EST) Received: from lserv by psg.com with local (Exim 3.36 #1) id 18gj94-000Bby-00 for idn-data@psg.com; Thu, 06 Feb 2003 02:20:38 -0800 Received: from smtp.denic.de ([194.246.96.22]) by psg.com with esmtp (Exim 3.36 #1) id 18gj90-000BbP-00 for idn@ops.ietf.org; Thu, 06 Feb 2003 02:20:34 -0800 Received: from notes.denic.de (denics15.denic.de [194.246.96.18]) by smtp.denic.de with esmtp id 18gj8y-0006lU-00; Thu, 6 Feb 2003 11:20:33 +0100 Subject: Re: [idn] punnycode in java? To: Rick Wesson Cc: idn@ops.ietf.org X-Mailer: Lotus Notes Release 5.0.6a January 17, 2001 Message-ID: From: "Marcos Sanz/Denic" Date: Thu, 6 Feb 2003 11:21:35 +0100 X-MIMETrack: Serialize by Router on notes/Denic(Release 5.0.11 |July 24, 2002) at 06.02.2003 11:20:32 MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii X-Spam-Status: No, hits=0.0 required=5.0 tests=QUOTED_EMAIL_TEXT,SPAM_PHRASE_00_01 version=2.43 Sender: owner-idn@ops.ietf.org Precedence: bulk On 05.02.2003 08:06 Rick Wesson wrote: > > anyone know of a implementation of punny code in java? If I can't find a > LGPL'ed version I'll go off an write one, but I wanted to check if someone > else hand't done it first. I haven't found any. If this is confirmed, I would contribute to write one. Regards, Marcos Sanz DENIC eG From owner-idn@ops.ietf.org Thu Feb 6 13:34:00 2003 Received: from psg.com (mailnull@psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA29552 for ; Thu, 6 Feb 2003 13:33:59 -0500 (EST) Received: from lserv by psg.com with local (Exim 3.36 #1) id 18gqki-0009qH-00 for idn-data@psg.com; Thu, 06 Feb 2003 10:28:00 -0800 Received: from mail.proper.com ([208.184.76.45] helo=above.proper.com) by psg.com with esmtp (Exim 3.36 #1) id 18gqkf-0009pl-00; Thu, 06 Feb 2003 10:27:57 -0800 Received: from [165.227.249.18] (165-227-249-18.client.dsl.net [165.227.249.18]) by above.proper.com (8.11.6/8.11.3) with ESMTP id h16IRmd23834; Thu, 6 Feb 2003 10:27:48 -0800 (PST) Mime-Version: 1.0 X-Sender: phoffman@mail.imc.org Message-Id: X-Habeas-SWE-1: winter into spring X-Habeas-SWE-2: brightly anticipated X-Habeas-SWE-3: like Habeas SWE (tm) X-Habeas-SWE-4: Copyright 2002 Habeas (tm) X-Habeas-SWE-5: Sender Warranted Email (SWE) (tm). The sender of this X-Habeas-SWE-6: email in exchange for a license for this Habeas X-Habeas-SWE-7: warrant mark warrants that this is a Habeas Compliant X-Habeas-SWE-8: Message (HCM) and not spam. Please report use of this X-Habeas-SWE-9: mark in spam to . Date: Thu, 6 Feb 2003 10:23:02 -0800 To: (Many IETF lists) From: Paul Hoffman / IMC Subject: [idn] New draft on internationalizing email addresses Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Spam-Status: No, hits=-2.3 required=5.0 tests=HABEAS_SWE,SPAM_PHRASE_03_05,TO_MALFORMED version=2.43 Sender: owner-idn@ops.ietf.org Precedence: bulk Greetings. This message is Bcc'd to many IETF-related lists that are discussing internationalization, Internet mail and Usenet. With the imminent release of the RFCs for IDNA, Adam Costello and I have a proposal for allowing internationalized characters in email addresses (on both sides of the @). Instead of having it discussed on a bunch of different lists, there is a new list for discussing the draft and other ideas related to internationalizing email address. If you are interested, please see for information on the Internet Draft and the mailing list. --Paul Hoffman, Director --Internet Mail Consortium From owner-idn@ops.ietf.org Sun Feb 9 13:42:54 2003 Received: from psg.com (mailnull@psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA03969 for ; Sun, 9 Feb 2003 13:42:53 -0500 (EST) Received: from lserv by psg.com with local (Exim 3.36 #1) id 18hwDf-000N9X-00 for idn-data@psg.com; Sun, 09 Feb 2003 10:30:23 -0800 Received: from sina.sharif.edu ([81.31.160.35]) by psg.com with esmtp (Exim 3.36 #1) id 18hwDb-000N9H-00 for idn@ops.ietf.org; Sun, 09 Feb 2003 10:30:20 -0800 Received: from bamdad.org (IDENT:root@bamdad.org [81.31.160.190]) by sina.sharif.edu (8.11.6/8.11.6) with ESMTP id h19IU7b16285; Sun, 9 Feb 2003 22:00:09 +0330 Received: from localhost (roozbeh@localhost) by bamdad.org (8.11.6/8.11.6) with ESMTP id h19IWqH21591; Sun, 9 Feb 2003 22:02:54 +0330 X-Authentication-Warning: gilas.bamdad.org: roozbeh owned process doing -bs Date: Sun, 9 Feb 2003 22:02:51 +0330 (IRT) From: Roozbeh Pournader X-X-Sender: roozbeh@gilas To: Hilde Margrethe Thunem cc: idn@ops.ietf.org Subject: Re: [idn] Using draft-jseng-idn-admin-01.txt In-Reply-To: <200302060804.h1684x718385@valgrind.uninett.no> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by amavisd-milter (http://amavis.org/) X-Spam-Status: No, hits=-2.4 required=5.0 tests=EMAIL_ATTRIBUTION,IN_REP_TO,SPAM_PHRASE_00_01, USER_AGENT_PINE,X_AUTH_WARNING version=2.43 Sender: owner-idn@ops.ietf.org Precedence: bulk On Thu, 6 Feb 2003, Hilde Margrethe Thunem wrote: > And while I'm asking questions, has any of you in the WG used the draft for > creating a draft policy for a language? I am writing an I-D based on draft-jseng-idn-admin for policies for Arabic, Persian, Urdu, and Pashto. I will post it here when I finished it. roozbeh From owner-idn@ops.ietf.org Sun Feb 9 20:56:42 2003 Received: from psg.com (mailnull@psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA11553 for ; Sun, 9 Feb 2003 20:56:41 -0500 (EST) Received: from lserv by psg.com with local (Exim 3.36 #1) id 18i2zE-000A3P-00 for idn-data@psg.com; Sun, 09 Feb 2003 17:43:56 -0800 Received: from sentosa.post1.com ([202.27.17.100]) by psg.com with smtp (Exim 3.36 #1) id 18i2zB-000A3D-00 for idn@ops.ietf.org; Sun, 09 Feb 2003 17:43:53 -0800 Received: (qmail 55573 invoked from network); 10 Feb 2003 01:36:08 -0000 Received: from ida120.ida.gov.sg (HELO JSENGTOSHIBA) (210.24.194.120) by sentosa.post1.com with SMTP; 10 Feb 2003 01:36:08 -0000 Message-ID: <03db01c2d0a5$ecc30420$17a1fea9@JSENGTOSHIBA> From: "James Seng" To: , "Hilde Margrethe Thunem" References: <200302060804.h1684x718385@valgrind.uninett.no> Subject: Re: [idn] Using draft-jseng-idn-admin-01.txt Date: Mon, 10 Feb 2003 09:44:17 +0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-Spam-Status: No, hits=-0.3 required=5.0 tests=QUOTED_EMAIL_TEXT,REFERENCES,SPAM_PHRASE_00_01, USER_AGENT_OE version=2.43 Sender: owner-idn@ops.ietf.org Precedence: bulk Content-Transfer-Encoding: 8bit Hi Hilde, > It looked rather interesting as a language to express a policy in if > there is characters that could be seen as variants of each other. As I'm > from a Norwegian background I've looked at using the guidelines in the > draft to describe an administrative domain name policy for the Norwegian > language, with a language character variant table. To be exact, you can break the document into two sections: a) How to generate variants of an IDN? b) How do you handle all these variants? For (a), the document describe a mechanism using language variants tables and also an aglorithm to generate variants. This designed specifically for CJK so I am not sure much Norwegian can use the same concept. For (b), the document describe a mechanism of an IDN Package (IDL), how this is registered, transferred, deleted, activiated, de-activated etc. I believe this would be more or less consistent across different languages. > Having tried to use it, I have a few questions concerning the interpretation > of the different groups in the language character variant table. As far as I > can see the recommended variants must also be valid codepoints, and result > in domain names that are in the zonefile, while character variants are merely > reserved when a valid combination is registered and are not in themselves > added to the zonefile. In addition, character variants that aren't valid > codepoints can't be the "starting point" for an IDL package. Yes, recommended variants usually are also valid codepoint. > In other words, given a language character variant table where the letters > a-z is among the valid codepoints, but does not have any recommended variants > or character variants (except the letter itself), and the following lines in > addition: > > 00F8; 00F8; 00F6; > 00F6; 00F8; 00F8; > (ø; ø; ö; > o; ø; ø;) Yes. > If I've understood correctly an application for the domain name bjørn.no > will result in an IDL package consisting of bjørn.no and björn.no, where > bjørn.no is added to the zonefile and björn.no is reserved. (As the ø is the > recommended variant, while the poor ö is just a character variant). Yes. > What > happens according to this policy if the domain name applied for is björn.no? > Will the registered name still be bjørn.no while björn.no is reserved? If björn.no is registered, then the zone file {ZV} will have two entry, björn.no and bjørn.no. The first is because the registered names always get into the zone file. The latter is because it is the recommended variant. > And if the language table only had a-z and > > 00F8; 00F8; 00F6; > (ø; ø; ö;) > > would that mean that while one could still apply for bjørn.no (and get > björn.no as a reserved name), someone applying for björn.no would get > rejected as that name contains a character that is not part of the valid > codepoints? Yes. Since ö is not in the entry of the first column (valid code point), it björn.no will not be allowed to be registered. > Sorry for asking the basic questions :-) but as the draft states, the > quality of the language table is critical for the result... which means that > the logic behind how the table is built is important. Not a problem at all. But having said all these, I like to reminded you again that the algorithm is designed for CJK. If it works for Norwegian, it occurs not by design. If there is another algorithm to generate variants which is more suitable for Norwegina, I am very interested to know. > And while I'm asking questions, has any of you in the WG used the draft for > creating a draft policy for a language? Yes. The JET (CNNIC, TWNIC, KRNIC, JPNIC) are using this document as a base-line for registration of CJK. -James Seng From owner-idn@ops.ietf.org Mon Feb 10 18:04:09 2003 Received: from psg.com (mailnull@psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA29579 for ; Mon, 10 Feb 2003 18:04:09 -0500 (EST) Received: from lserv by psg.com with local (Exim 3.36 #1) id 18iMmt-000JAL-00 for idn-data@psg.com; Mon, 10 Feb 2003 14:52:31 -0800 Received: from santee.icann.org ([192.0.35.122]) by psg.com with esmtp (Exim 3.36 #1) id 18iMmm-000JA5-00 for idn@ops.ietf.org; Mon, 10 Feb 2003 14:52:25 -0800 Received: from tarim (tarim.icann.org [192.0.35.80]) by santee.icann.org (8.11.6/8.11.6) with SMTP id h1AMqNL09358; Mon, 10 Feb 2003 14:52:24 -0800 From: "IANA" To: Cc: "Patrik Falstrom" , "Harald Tveit Alvestrand" , "Erik Nordmark" Subject: [idn] FW: IANA Selection of IDNA Prefix Date: Mon, 10 Feb 2003 14:43:34 -0800 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Importance: Normal X-Spam-Status: No, hits=0.9 required=5.0 tests=LINES_OF_YELLING,OUTLOOK_FW_MSG,SPAM_PHRASE_00_01, USER_AGENT_OUTLOOK version=2.43 Sender: owner-idn@ops.ietf.org Precedence: bulk Content-Transfer-Encoding: 7bit IDN Working Group-- This is the final version of the Protocol and Schedule for Selecting the IDNA Prefix. Best regards, Michelle S. Cotton IANA Administrator This document sets forth the protocol by which the IANA will select a two-character code to be used as the first two characters of the ACE prefix referred to as "IESG--" in Section 5 of draft-ietf-idn-idna-14.txt. It also specifies the schedule for the selection. This document is based on the IANA's proposed Protocol and Schedule distributed on 30 January 2003 and reflects changes to address comments received by 6 February 2003. The IANA thanks Adam Costello and Simon Josefsson for their comments. A. Protocol The following steps will be used to select the two-character code: 1. The code will be selected from among a subset of the entries on the ISO 3166-1:1997, clause 8.1.3 User-assigned alpha-2 code elements: AA, QM to QZ, XA to XZ, and ZZ. The selection is limited to these codes because of the following: a) The use of numeric characters, while permitted by the Internet-Draft, would create visual ambiguities concerning the digits "0", "1", and "5". (For similar reasons, codes including the letters O, I, L, and S are eliminated in step 3.) b) The use of ISO 3166-1 the user-assigned elements removes the possibility that the code will duplicate a present or future ccTLD code. 2. An eligible subset of that list of 42 entries will be determined by eliminating the following codes due to their use, in one or more top-level domain zone files that have been reviewed, as the first two characters of second-level domain labels that have hyphens in their third and fourth character positions: AA, QM to QZ, XA, XZ, and ZZ. 3. This leaves the following subset of twenty-four candidate codes: XB, XC, XD, XE, XF, XG, XH, XI, XJ, XK, XL, XM, XN, XO, XP, XQ, XR, XS, XT, XU, XV, XW, XX, and XY. Of those codes, XI, XL, XO, and XS are eliminated due to potential confusion with X1, X1, X0, and X5, and XU and XV are eliminated due to potential confusion with each other. This leaves eighteen candidate codes. 4. A random selection will be made from among the eighteen candidates. The algorithm for the random selection will generally follow that stated in RFC 2777. First, the eighteen candidates will be arranged in an ordered list as follows: 1. XB 7. XH 13. XQ 2. XC 8. XJ 14. XR 3. XD 9. XK 15. XT 4. XE 10. XM 16. XW 5. XF 11. XN 17. XX 6. XG 12. XP 18. XY Next, the trading volume of twelve stocks on the Reference Day (see schedule below), as listed in the U.S. National Edition of the Wall Street Journal on the Selection Day (see schedule below), will be used to generate a key string in the manner specified on page 5 of RFC 2777. The twelve stocks are: (NYSE) IMS Hlth RX (NYSE) IL Tool ITW (NYSE) IntRectifr IRF (NYSE) IBM IBM (NYSE) IntPaper IP (NYSE) Interpublic IPG (NASDAQ) Inamed IMDC (NASDAQ) Informatica INFA (NASDAQ) Inktomi INKT (NASDAQ) i2 Tch ITWO (NASDAQ) IDEC Pharm IDPH (NASDAQ) Intel INTC Although the IANA's investigation indicates that all copies of the U.S. National Edition (on any day other than a Wednesday) of the Wall Street Journal should be identical, to eliminate any ambiguity the IANA will purchase a copy, which will be authoritative, on the morning of the Selection Day at a local store. In the event that the trading volume of any of the above twelve stocks is not reported in that paper, the value 0 will be used for that stock. In the event that more than six of the stocks then have a zero value, the selection will be deemed invalid and re-run in a manner decided according to the circumstances. A key string will be constructed with the numeric trading volumes of the twelve stocks (denoted in 100s and not including any thousands-separating punctuation), in the order stated above, according to page 5 of RFC 2777. An MD5 hash [RFC 1321] of the string, prefixed and suffixed with a zero byte, will be calculated. That value will be divided by eighteen, and the remainder of the division plus one will be the position of the selected candidate in the ordered list above. (Note: The Wall Street Journal currently reports share volumes in 100s. Thus, a volume of 7,660,900 shares would be reported in the Wall Street Journal as "76609" and would be represented as "76609" within the key.) The selection mechanism uses the reference implementation in RFC 2777 and the reference MD5 implementation from RFC 1321. 5. A message will be sent to the IETF Announce list to announce the selected code as well as the details of the selection. This message will be sent immediately after the selection is made on the Selection Day, according to the schedule described below. 6. If anyone disagrees with the computation of the result under the above protocol as announced by the IANA on the Selection Day, please send a note to no later than the day before the Notification Day. The RFC Editor will be notified of the selected code on the Notification Day. B. Schedule The following schedule will be followed for the selection process: 30 January 2003 - Protocol and Schedule published, including to IETF Announce list. Comments invited to . 6 February 2003 - Last day for comments. 10 February 2003 (Monday) - Reference Day (see above). 11 February 2003 (Tuesday) - Selection Day (see above). 14 February 2003 (Friday) - Notification Day. From owner-idn@ops.ietf.org Tue Feb 11 21:41:22 2003 Received: from psg.com (mailnull@psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA25850 for ; Tue, 11 Feb 2003 21:41:21 -0500 (EST) Received: from lserv by psg.com with local (Exim 3.36 #1) id 18imbT-000PWE-00 for idn-data@psg.com; Tue, 11 Feb 2003 18:26:27 -0800 Received: from santee.icann.org ([192.0.35.122]) by psg.com with esmtp (Exim 3.36 #1) id 18imbQ-000PVy-00 for idn@ops.ietf.org; Tue, 11 Feb 2003 18:26:24 -0800 Received: from tarim (tarim.icann.org [192.0.35.80]) by santee.icann.org (8.11.6/8.11.6) with SMTP id h1C2QML07613; Tue, 11 Feb 2003 18:26:23 -0800 From: "IANA" To: Cc: "IESG" Subject: [idn] Results of IANA Selection of IDNA Prefix Date: Tue, 11 Feb 2003 18:17:31 -0800 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Importance: Normal X-Spam-Status: No, hits=0.9 required=5.0 tests=LINES_OF_YELLING,LINES_OF_YELLING_2,SPAM_PHRASE_01_02, USER_AGENT_OUTLOOK version=2.43 Sender: owner-idn@ops.ietf.org Precedence: bulk Content-Transfer-Encoding: 7bit Results of IANA Selection of IDNA Prefix As described in section B of the Protocol and Schedule (see below), today 11 February 2003 (Tuesday), is the Selection Day. The IANA followed the steps described in section 4 (see below). The twelve stocks and their trading volumes (in 100s) were: (NYSE) IMS Hlth RX 22157 (NYSE) IL Tool ITW 11795 (NYSE) IntRectifr IRF 5742 (NYSE) IBM IBM 78719 (NYSE) IntPaper IP 16609 (NYSE) Interpublic IPG 34961 (NASDAQ) Inamed IMDC 1567 (NASDAQ) Informatica INFA 4357 (NASDAQ) Inktomi INKT 6085 (NASDAQ) i2 Tch ITWO 37777 (NASDAQ) IDEC Pharm IDPH 18754 (NASDAQ) Intel INTC 524545 These trading volumes have been used to generate a key string in the manner specified on page 5 of RFC 2777. The key string is 22157./11795./5742./78719./16609./34961./1567./4357./6085./37777./18754./524 545./ The hex value of MD5 is BDEC8317C50316D67B688D1C9A34C682 The hex value of MD5 was then divided by eighteen. The remainder of the division (10) plus one (11) is the position of the selected candidate in the ordered list below. According to the ordered list, the selected code is "XN". 1. XB 7. XH 13. XQ 2. XC 8. XJ 14. XR 3. XD 9. XK 15. XT 4. XE 10. XM 16. XW 5. XF 11. XN 17. XX 6. XG 12. XP 18. XY As stated in section 6 of our message below: If anyone disagrees with the computation of the result under the above protocol as announced by the IANA on the Selection Day, please send a note to no later than the day before the Notification Day. The RFC Editor will be notified of the selected code on the Notification Day (Friday, 14 February 2003). Thank you, The Internet Assigned Numbers Authority ************************************************************************ -----Original Message----- From: IANA [mailto:iana@iana.org] Sent: Monday, February 10, 2003 2:44 PM To: idn@ops.ietf.org Subject: FW: IANA Selection of IDNA Prefix This document sets forth the protocol by which the IANA will select a two-character code to be used as the first two characters of the ACE prefix referred to as "IESG--" in Section 5 of draft-ietf-idn-idna-14.txt. It also specifies the schedule for the selection. This document is based on the IANA's proposed Protocol and Schedule distributed on 30 January 2003 and reflects changes to address comments received by 6 February 2003. The IANA thanks Adam Costello and Simon Josefsson for their comments. A. Protocol The following steps will be used to select the two-character code: 1. The code will be selected from among a subset of the entries on the ISO 3166-1:1997, clause 8.1.3 User-assigned alpha-2 code elements: AA, QM to QZ, XA to XZ, and ZZ. The selection is limited to these codes because of the following: a) The use of numeric characters, while permitted by the Internet-Draft, would create visual ambiguities concerning the digits "0", "1", and "5". (For similar reasons, codes including the letters O, I, L, and S are eliminated in step 3.) b) The use of ISO 3166-1 the user-assigned elements removes the possibility that the code will duplicate a present or future ccTLD code. 2. An eligible subset of that list of 42 entries will be determined by eliminating the following codes due to their use, in one or more top-level domain zone files that have been reviewed, as the first two characters of second-level domain labels that have hyphens in their third and fourth character positions: AA, QM to QZ, XA, XZ, and ZZ. 3. This leaves the following subset of twenty-four candidate codes: XB, XC, XD, XE, XF, XG, XH, XI, XJ, XK, XL, XM, XN, XO, XP, XQ, XR, XS, XT, XU, XV, XW, XX, and XY. Of those codes, XI, XL, XO, and XS are eliminated due to potential confusion with X1, X1, X0, and X5, and XU and XV are eliminated due to potential confusion with each other. This leaves eighteen candidate codes. 4. A random selection will be made from among the eighteen candidates. The algorithm for the random selection will generally follow that stated in RFC 2777. First, the eighteen candidates will be arranged in an ordered list as follows: 1. XB 7. XH 13. XQ 2. XC 8. XJ 14. XR 3. XD 9. XK 15. XT 4. XE 10. XM 16. XW 5. XF 11. XN 17. XX 6. XG 12. XP 18. XY Next, the trading volume of twelve stocks on the Reference Day (see schedule below), as listed in the U.S. National Edition of the Wall Street Journal on the Selection Day (see schedule below), will be used to generate a key string in the manner specified on page 5 of RFC 2777. The twelve stocks are: (NYSE) IMS Hlth RX (NYSE) IL Tool ITW (NYSE) IntRectifr IRF (NYSE) IBM IBM (NYSE) IntPaper IP (NYSE) Interpublic IPG (NASDAQ) Inamed IMDC (NASDAQ) Informatica INFA (NASDAQ) Inktomi INKT (NASDAQ) i2 Tch ITWO (NASDAQ) IDEC Pharm IDPH (NASDAQ) Intel INTC Although the IANA's investigation indicates that all copies of the U.S. National Edition (on any day other than a Wednesday) of the Wall Street Journal should be identical, to eliminate any ambiguity the IANA will purchase a copy, which will be authoritative, on the morning of the Selection Day at a local store. In the event that the trading volume of any of the above twelve stocks is not reported in that paper, the value 0 will be used for that stock. In the event that more than six of the stocks then have a zero value, the selection will be deemed invalid and re-run in a manner decided according to the circumstances. A key string will be constructed with the numeric trading volumes of the twelve stocks (denoted in 100s and not including any thousands-separating punctuation), in the order stated above, according to page 5 of RFC 2777. An MD5 hash [RFC 1321] of the string, prefixed and suffixed with a zero byte, will be calculated. That value will be divided by eighteen, and the remainder of the division plus one will be the position of the selected candidate in the ordered list above. (Note: The Wall Street Journal currently reports share volumes in 100s. Thus, a volume of 7,660,900 shares would be reported in the Wall Street Journal as "76609" and would be represented as "76609" within the key.) The selection mechanism uses the reference implementation in RFC 2777 and the reference MD5 implementation from RFC 1321. 5. A message will be sent to the IETF Announce list to announce the selected code as well as the details of the selection. This message will be sent immediately after the selection is made on the Selection Day, according to the schedule described below. 6. If anyone disagrees with the computation of the result under the above protocol as announced by the IANA on the Selection Day, please send a note to no later than the day before the Notification Day. The RFC Editor will be notified of the selected code on the Notification Day. B. Schedule The following schedule will be followed for the selection process: 30 January 2003 - Protocol and Schedule published, including to IETF Announce list. Comments invited to . 6 February 2003 - Last day for comments. 10 February 2003 (Monday) - Reference Day (see above). 11 February 2003 (Tuesday) - Selection Day (see above). 14 February 2003 (Friday) - Notification Day. From owner-idn@ops.ietf.org Thu Feb 13 11:25:46 2003 Received: from psg.com (mailnull@psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16832 for ; Thu, 13 Feb 2003 11:25:46 -0500 (EST) Received: from lserv by psg.com with local (Exim 3.36 #1) id 18jLpX-0005im-00 for idn-data@psg.com; Thu, 13 Feb 2003 08:03:19 -0800 Received: from mailgw.prontomail.com ([207.183.238.63] helo=c0mailgw05.prontomail.com) by psg.com with esmtp (Exim 3.36 #1) id 18jLpT-0005iX-00 for idn@ops.ietf.org; Thu, 13 Feb 2003 08:03:15 -0800 Received: from c0web111 (207.183.238.63) by c0mailgw05.prontomail.com (NPlex 6.0.045) id 3E481080000CB36C for idn@ops.ietf.org; Thu, 13 Feb 2003 08:03:47 -0800 X-Version: go2net 6.2.3 .3385.0 From: "John Wall" Message-Id: <1511CE6F14D7EA84E81374BE4552D703@johwal.go2netmail.com> Date: Thu, 13 Feb 2003 11:03:18 -0500 X-Priority: Normal Content-Type: text/plain; charset=iso-8859-1 To: idn@ops.ietf.org Reply-To: johwal@go2netmail.com Subject: [idn] Punycode conversion tool X-Mailer: Web Based Pronto Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.5 required=5.0 tests=SPAM_PHRASE_01_02 version=2.43 Sender: owner-idn@ops.ietf.org Precedence: bulk Content-Transfer-Encoding: 7bit I am looking for an IDNA conversion tool using the ACE prefix available since yesterday. Can anybody help me? Thank you J.W. Sent by Go2net Mail! From owner-idn@ops.ietf.org Thu Feb 13 11:48:24 2003 Received: from psg.com (mailnull@psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA18275 for ; Thu, 13 Feb 2003 11:48:23 -0500 (EST) Received: from lserv by psg.com with local (Exim 3.36 #1) id 18jMPG-000904-00 for idn-data@psg.com; Thu, 13 Feb 2003 08:40:14 -0800 Received: from mail1.ics.ntts.co.jp ([202.32.24.45]) by psg.com with esmtp (Exim 3.36 #1) id 18jMP8-0008zH-00 for idn@ops.ietf.org; Thu, 13 Feb 2003 08:40:06 -0800 Received: from mail26.silk.ntts.co.jp by mail1.ics.ntts.co.jp (8.9.3/3.7W-NTTSOFT-SUR2.0) id BAA13235 for ; Fri, 14 Feb 2003 01:40:04 +0900 (JST) (envelope-from yone@po.ntts.co.jp) Received: from daemon.inl.ntts.co.jp by mail26.silk.ntts.co.jp (8.11.6/3.7W-silk-4.6) id h1DGe3705588 for ; Fri, 14 Feb 2003 01:40:03 +0900 (JST) (envelope-from yone@po.ntts.co.jp) Received: (qmail 71217 invoked by alias); 14 Feb 2003 01:40:02 +0900 Received: (qmail 71173 invoked from network); 14 Feb 2003 01:40:00 +0900 Received: from daemon.inl.ntts.co.jp (HELO localhost) by daemon.inl.ntts.co.jp with SMTP; 14 Feb 2003 01:40:00 +0900 To: johwal@go2netmail.com Cc: idn@ops.ietf.org Subject: Re: [idn] Punycode conversion tool In-Reply-To: <1511CE6F14D7EA84E81374BE4552D703@johwal.go2netmail.com> References: <1511CE6F14D7EA84E81374BE4552D703@johwal.go2netmail.com> X-Mailer: Mew version 1.94.2 on Emacs 20.7 / Mule 4.1 (AOI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20030214013955U.yone@po.ntts.co.jp> Date: Fri, 14 Feb 2003 01:39:55 +0900 (JST) From: Yoshiro YONEYA X-Dispatcher: imput version 20000414(IM141) Lines: 21 X-Spam-Status: No, hits=-2.7 required=5.0 tests=EMAIL_ATTRIBUTION,IN_REP_TO,REFERENCES, SIGNATURE_SHORT_DENSE,SPAM_PHRASE_01_02 version=2.43 Sender: owner-idn@ops.ietf.org Precedence: bulk Content-Transfer-Encoding: 7bit On Thu, 13 Feb 2003 11:03:18 -0500, "John Wall" wrote: > I am looking for an IDNA conversion tool using > the ACE prefix available since yesterday. > > Can anybody help me? Sure :-) Try idnkit which is available from following URL: http://www.nic.ad.jp/ja/idn/mdnkit/download/#sources ==> idnkit-1.0pr2 By default, the idnkit-1.0pr2 uses 'zq--' as ACE prefix. But it can be changed to 'xn--' by using '--with-punycode-prefix=xn--' configure option. Please read 'INSTALL' for more detail. -- Yoshiro YONEYA aka From owner-idn@ops.ietf.org Thu Feb 13 13:04:01 2003 Received: from psg.com (mailnull@psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA20449 for ; Thu, 13 Feb 2003 13:04:00 -0500 (EST) Received: from lserv by psg.com with local (Exim 3.36 #1) id 18jNeR-000Hb6-00 for idn-data@psg.com; Thu, 13 Feb 2003 09:59:59 -0800 Received: from 178.230.13.217.in-addr.dgcsystems.net ([217.13.230.178] helo=yxa.extundo.com) by psg.com with esmtp (Exim 3.36 #1) id 18jNeO-000Ham-00 for idn@ops.ietf.org; Thu, 13 Feb 2003 09:59:56 -0800 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 h1DHxmXf006580 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=OK); Thu, 13 Feb 2003 18:59:49 +0100 To: johwal@go2netmail.com Cc: idn@ops.ietf.org Subject: [idn] Re: Punycode conversion tool X-Payment: hashcash 1.1 0:030213:johwal@go2netmail.com:e892b2021696ce6e X-Hashcash: 0:030213:johwal@go2netmail.com:e892b2021696ce6e X-Payment: hashcash 1.1 0:030213:idn@ops.ietf.org:5421a485956e9a63 X-Hashcash: 0:030213:idn@ops.ietf.org:5421a485956e9a63 From: Simon Josefsson Date: Thu, 13 Feb 2003 18:59:48 +0100 In-Reply-To: <1511CE6F14D7EA84E81374BE4552D703@johwal.go2netmail.com> ("John Wall"'s message of "Thu, 13 Feb 2003 11:03:18 -0500") Message-ID: User-Agent: Gnus/5.090016 (Oort Gnus v0.16) Emacs/21.2 References: <1511CE6F14D7EA84E81374BE4552D703@johwal.go2netmail.com> X-Face: %bo>yc#X1.-jVa- writes: > I am looking for an IDNA conversion tool using > the ACE prefix available since yesterday. > > Can anybody help me? From owner-idn@ops.ietf.org Fri Feb 14 09:57:57 2003 Received: from psg.com (mailnull@psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA23968 for ; Fri, 14 Feb 2003 09:57:57 -0500 (EST) Received: from lserv by psg.com with local (Exim 3.36 #1) id 18jhAp-000F4e-00 for idn-data@psg.com; Fri, 14 Feb 2003 06:50:43 -0800 Received: from sina.sharif.edu ([81.31.160.35]) by psg.com with esmtp (Exim 3.36 #1) id 18jhAj-000F3Z-00 for idn@ops.ietf.org; Fri, 14 Feb 2003 06:50:38 -0800 Received: from bamdad.org (IDENT:root@bamdad.org [81.31.160.190]) by sina.sharif.edu (8.11.6/8.11.6) with ESMTP id h1EEoOb05373; Fri, 14 Feb 2003 18:20:27 +0330 Received: from localhost (roozbeh@localhost) by bamdad.org (8.11.6/8.11.6) with ESMTP id h1EEtaV06075; Fri, 14 Feb 2003 18:25:39 +0330 X-Authentication-Warning: gilas.bamdad.org: roozbeh owned process doing -bs Date: Fri, 14 Feb 2003 18:25:36 +0330 (IRT) From: Roozbeh Pournader X-X-Sender: roozbeh@gilas To: Simon Josefsson cc: johwal@go2netmail.com, Subject: Re: [idn] Re: Punycode conversion tool In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by amavisd-milter (http://amavis.org/) X-Spam-Status: No, hits=-2.4 required=5.0 tests=EMAIL_ATTRIBUTION,IN_REP_TO,SPAM_PHRASE_00_01, USER_AGENT_PINE,X_AUTH_WARNING version=2.43 Sender: owner-idn@ops.ietf.org Precedence: bulk On Thu, 13 Feb 2003, Simon Josefsson wrote: > Wow! Do you know if this will be integrated into glibc? roozbeh From owner-idn@ops.ietf.org Fri Feb 14 11:14:48 2003 Received: from psg.com (mailnull@psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA25858 for ; Fri, 14 Feb 2003 11:14:47 -0500 (EST) Received: from lserv by psg.com with local (Exim 3.36 #1) id 18jiL1-000IX7-00 for idn-data@psg.com; Fri, 14 Feb 2003 08:05:19 -0800 Received: from 178.230.13.217.in-addr.dgcsystems.net ([217.13.230.178] helo=yxa.extundo.com) by psg.com with esmtp (Exim 3.36 #1) id 18jiKp-000IWM-00 for idn@ops.ietf.org; Fri, 14 Feb 2003 08:05:07 -0800 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 h1EG50Xf005706 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=OK); Fri, 14 Feb 2003 17:05:01 +0100 To: Roozbeh Pournader Cc: johwal@go2netmail.com, Subject: [idn] Re: Punycode conversion tool X-Payment: hashcash 1.1 0:030214:roozbeh@sharif.edu:032413e301c0f91f X-Hashcash: 0:030214:roozbeh@sharif.edu:032413e301c0f91f X-Payment: hashcash 1.1 0:030214:johwal@go2netmail.com:9bbd2d312962ceec X-Hashcash: 0:030214:johwal@go2netmail.com:9bbd2d312962ceec X-Payment: hashcash 1.1 0:030214:idn@ops.ietf.org:d3a211d0dfa7c67b X-Hashcash: 0:030214:idn@ops.ietf.org:d3a211d0dfa7c67b From: Simon Josefsson Date: Fri, 14 Feb 2003 17:05:00 +0100 In-Reply-To: (Roozbeh Pournader's message of "Fri, 14 Feb 2003 18:25:36 +0330 (IRT)") Message-ID: User-Agent: Gnus/5.090016 (Oort Gnus v0.16) Emacs/21.3.50 References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Status: No, hits=-3.6 required=5.0 tests=EMAIL_ATTRIBUTION,IN_REP_TO,REFERENCES,SPAM_PHRASE_00_01, USER_AGENT,USER_AGENT_GNUS_UA version=2.43 Sender: owner-idn@ops.ietf.org Precedence: bulk Roozbeh Pournader writes: > On Thu, 13 Feb 2003, Simon Josefsson wrote: > >> > > Wow! Do you know if this will be integrated into glibc? No, I don't. The integration work has been done, so anyone that like to run with an IDN enabled glibc can do so easily. Perhaps interested distributions will pick it up, a'la initial IPv6 deployment, or the glibc maintainers will. From owner-idn@ops.ietf.org Fri Feb 14 20:47:37 2003 Received: from psg.com (mailnull@psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA11878 for ; Fri, 14 Feb 2003 20:47:36 -0500 (EST) Received: from lserv by psg.com with local (Exim 3.36 #1) id 18jrKe-000PTd-00 for idn-data@psg.com; Fri, 14 Feb 2003 17:41:32 -0800 Received: from santee.icann.org ([192.0.35.122]) by psg.com with esmtp (Exim 3.36 #1) id 18jrKb-000PTP-00 for idn@ops.ietf.org; Fri, 14 Feb 2003 17:41:29 -0800 Received: from tarim (tarim.icann.org [192.0.35.80]) by santee.icann.org (8.11.6/8.11.6) with SMTP id h1F1fRL22236 for ; Fri, 14 Feb 2003 17:41:27 -0800 From: "IANA" To: Subject: [idn] FW: Completion of IANA Selection of IDNA Prefix Date: Fri, 14 Feb 2003 17:32:23 -0800 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Importance: Normal X-Spam-Status: No, hits=0.8 required=5.0 tests=LINES_OF_YELLING,LINES_OF_YELLING_2,OUTLOOK_FW_MSG, SPAM_PHRASE_01_02,USER_AGENT_OUTLOOK version=2.43 Sender: owner-idn@ops.ietf.org Precedence: bulk Content-Transfer-Encoding: 7bit Forwarding just in case you didn't see it. Michelle IANA -----Original Message----- From: owner-ietf-announce@ietf.org [mailto:owner-ietf-announce@ietf.org]On Behalf Of IANA Sent: Friday, February 14, 2003 4:18 PM To: IETF-Announce: Subject: Completion of IANA Selection of IDNA Prefix Completion of IANA Selection of IDNA Prefix. On 11 February 2003, the IANA selected "xn--" as the IDNA Prefix. Per our message below, the IANA requested that comments be sent no later than 13 February 2003 if there was any disagreement with the results. No comments were received regarding the computation described below. The ACE prefix for IDNA is "xn--". As stated in number 6 below, the RFC Editor has been notified of the selected code. Thank you, Internet Assigned Numbers Authority ********************************************************************* Message from 11 February 2003 regarding IANA Selection of IDNA Prefix ********************************************************************* Results of IANA Selection of IDNA Prefix As described in section B of the Protocol and Schedule (see below), today 11 February 2003 (Tuesday), is the Selection Day. The IANA followed the steps described in section 4 (see below). The twelve stocks and their trading volumes (in 100s) were: (NYSE) IMS Hlth RX 22157 (NYSE) IL Tool ITW 11795 (NYSE) IntRectifr IRF 5742 (NYSE) IBM IBM 78719 (NYSE) IntPaper IP 16609 (NYSE) Interpublic IPG 34961 (NASDAQ) Inamed IMDC 1567 (NASDAQ) Informatica INFA 4357 (NASDAQ) Inktomi INKT 6085 (NASDAQ) i2 Tch ITWO 37777 (NASDAQ) IDEC Pharm IDPH 18754 (NASDAQ) Intel INTC 524545 These trading volumes have been used to generate a key string in the manner specified on page 5 of RFC 2777. The key string is 22157./11795./5742./78719./16609./34961./1567./4357./6085./37777./ 18754./524545./ The hex value of MD5 is BDEC8317C50316D67B688D1C9A34C682 The hex value of MD5 was then divided by eighteen. The remainder of the division (10) plus one (11) is the position of the selected candidate in the ordered list below. According to the ordered list, the selected code is "XN". 1. XB 7. XH 13. XQ 2. XC 8. XJ 14. XR 3. XD 9. XK 15. XT 4. XE 10. XM 16. XW 5. XF 11. XN 17. XX 6. XG 12. XP 18. XY As stated in section 6 of our message below: If anyone disagrees with the computation of the result under the above protocol as announced by the IANA on the Selection Day, please send a note to no later than the day before the Notification Day. The RFC Editor will be notified of the selected code on the Notification Day (Friday, 14 February 2003). Thank you, The Internet Assigned Numbers Authority ************************************************************************ -----Original Message----- From: IANA [mailto:iana@iana.org] Sent: Monday, February 10, 2003 2:44 PM To: idn@ops.ietf.org Subject: FW: IANA Selection of IDNA Prefix This document sets forth the protocol by which the IANA will select a two-character code to be used as the first two characters of the ACE prefix referred to as "IESG--" in Section 5 of draft-ietf-idn-idna-14.txt. It also specifies the schedule for the selection. This document is based on the IANA's proposed Protocol and Schedule distributed on 30 January 2003 and reflects changes to address comments received by 6 February 2003. The IANA thanks Adam Costello and Simon Josefsson for their comments. A. Protocol The following steps will be used to select the two-character code: 1. The code will be selected from among a subset of the entries on the ISO 3166-1:1997, clause 8.1.3 User-assigned alpha-2 code elements: AA, QM to QZ, XA to XZ, and ZZ. The selection is limited to these codes because of the following: a) The use of numeric characters, while permitted by the Internet-Draft, would create visual ambiguities concerning the digits "0", "1", and "5". (For similar reasons, codes including the letters O, I, L, and S are eliminated in step 3.) b) The use of ISO 3166-1 the user-assigned elements removes the possibility that the code will duplicate a present or future ccTLD code. 2. An eligible subset of that list of 42 entries will be determined by eliminating the following codes due to their use, in one or more top-level domain zone files that have been reviewed, as the first two characters of second-level domain labels that have hyphens in their third and fourth character positions: AA, QM to QZ, XA, XZ, and ZZ. 3. This leaves the following subset of twenty-four candidate codes: XB, XC, XD, XE, XF, XG, XH, XI, XJ, XK, XL, XM, XN, XO, XP, XQ, XR, XS, XT, XU, XV, XW, XX, and XY. Of those codes, XI, XL, XO, and XS are eliminated due to potential confusion with X1, X1, X0, and X5, and XU and XV are eliminated due to potential confusion with each other. This leaves eighteen candidate codes. 4. A random selection will be made from among the eighteen candidates. The algorithm for the random selection will generally follow that stated in RFC 2777. First, the eighteen candidates will be arranged in an ordered list as follows: 1. XB 7. XH 13. XQ 2. XC 8. XJ 14. XR 3. XD 9. XK 15. XT 4. XE 10. XM 16. XW 5. XF 11. XN 17. XX 6. XG 12. XP 18. XY Next, the trading volume of twelve stocks on the Reference Day (see schedule below), as listed in the U.S. National Edition of the Wall Street Journal on the Selection Day (see schedule below), will be used to generate a key string in the manner specified on page 5 of RFC 2777. The twelve stocks are: (NYSE) IMS Hlth RX (NYSE) IL Tool ITW (NYSE) IntRectifr IRF (NYSE) IBM IBM (NYSE) IntPaper IP (NYSE) Interpublic IPG (NASDAQ) Inamed IMDC (NASDAQ) Informatica INFA (NASDAQ) Inktomi INKT (NASDAQ) i2 Tch ITWO (NASDAQ) IDEC Pharm IDPH (NASDAQ) Intel INTC Although the IANA's investigation indicates that all copies of the U.S. National Edition (on any day other than a Wednesday) of the Wall Street Journal should be identical, to eliminate any ambiguity the IANA will purchase a copy, which will be authoritative, on the morning of the Selection Day at a local store. In the event that the trading volume of any of the above twelve stocks is not reported in that paper, the value 0 will be used for that stock. In the event that more than six of the stocks then have a zero value, the selection will be deemed invalid and re-run in a manner decided according to the circumstances. A key string will be constructed with the numeric trading volumes of the twelve stocks (denoted in 100s and not including any thousands-separating punctuation), in the order stated above, according to page 5 of RFC 2777. An MD5 hash [RFC 1321] of the string, prefixed and suffixed with a zero byte, will be calculated. That value will be divided by eighteen, and the remainder of the division plus one will be the position of the selected candidate in the ordered list above. (Note: The Wall Street Journal currently reports share volumes in 100s. Thus, a volume of 7,660,900 shares would be reported in the Wall Street Journal as "76609" and would be represented as "76609" within the key.) The selection mechanism uses the reference implementation in RFC 2777 and the reference MD5 implementation from RFC 1321. 5. A message will be sent to the IETF Announce list to announce the selected code as well as the details of the selection. This message will be sent immediately after the selection is made on the Selection Day, according to the schedule described below. 6. If anyone disagrees with the computation of the result under the above protocol as announced by the IANA on the Selection Day, please send a note to no later than the day before the Notification Day. The RFC Editor will be notified of the selected code on the Notification Day. B. Schedule The following schedule will be followed for the selection process: 30 January 2003 - Protocol and Schedule published, including to IETF Announce list. Comments invited to . 6 February 2003 - Last day for comments. 10 February 2003 (Monday) - Reference Day (see above). 11 February 2003 (Tuesday) - Selection Day (see above). 14 February 2003 (Friday) - Notification Day. From owner-idn@ops.ietf.org Tue Feb 25 09:33:49 2003 Received: from psg.com (mailnull@psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA02041 for ; Tue, 25 Feb 2003 09:33:48 -0500 (EST) Received: from lserv by psg.com with local (Exim 3.36 #1) id 18ng0O-000Hhx-00 for idn-data@psg.com; Tue, 25 Feb 2003 06:24:24 -0800 Received: from [3ffe:b00:c18:3::a] (helo=jazz.viagenie.qc.ca) by psg.com with esmtp (Exim 3.36 #1) id 18ng0K-000Hgq-00 for idn@ops.ietf.org; Tue, 25 Feb 2003 06:24:21 -0800 Received: from localhost.localdomain (retro.viagenie.qc.ca [206.123.31.22]) by jazz.viagenie.qc.ca (Viagenie/8.11.0) with ESMTP id h1PENou37885 for ; Tue, 25 Feb 2003 09:23:50 -0500 (EST) Date: Tue, 25 Feb 2003 09:23:47 -0500 From: Marc Blanchet To: idn@ops.ietf.org Subject: [idn] implementations list Message-ID: <21980000.1046183027@classic.hexago.com> In-Reply-To: References: X-Mailer: Mulberry/3.0.1 (Linux/x86 Demo) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Spam-Status: No, hits=-0.4 required=5.0 tests=IN_REP_TO,REFERENCES,SPAM_PHRASE_03_05,SUBJECT_IS_LIST version=2.43 Sender: owner-idn@ops.ietf.org Precedence: bulk Content-Transfer-Encoding: 7bit Hi, now that: - the idna prefix is defined - the stringprep RFC is out - the other RFCs are going out soon I would like to rework the http://www.i-d-n.net (which is very outdated, my apologies) to reflect the status of the idn work and to start collecting information on implementations. Could any developer/vendor/... who have an implementation of idn be kind to forward me the following information, so I'll put it on the web site: Name: Purpose: library/client/web browser/plug-in/... Programming language: (for open-source) Url: Description: (100 words max) Please send this to me directly. I'll report to the list when the new web site is up Thanks, Marc. From owner-idn@ops.ietf.org Fri Feb 28 13:00:27 2003 Received: from psg.com (mailnull@psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA07479 for ; Fri, 28 Feb 2003 13:00:26 -0500 (EST) Received: from lserv by psg.com with local (Exim 3.36 #1) id 18oofx-000JPD-00 for idn-data@psg.com; Fri, 28 Feb 2003 09:52:01 -0800 Received: from [207.65.203.98] (helo=goose.ehsco.com) by psg.com with esmtp (Exim 3.36 #1) id 18oofs-000JOc-00 for idn@ops.ietf.org; Fri, 28 Feb 2003 09:51:56 -0800 Received: from [68.53.173.31] (account ehall HELO ehsco.com) by goose.ehsco.com (CommuniGate Pro SMTP 4.0) with ESMTP-TLS id 186113 for idn@ops.ietf.org; Fri, 28 Feb 2003 11:50:46 -0600 Message-ID: <3E5FA1B8.1070009@ehsco.com> Date: Fri, 28 Feb 2003 11:51:52 -0600 From: "Eric A. Hall" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2.1) Gecko/20021130 X-Accept-Language: en-US,en MIME-Version: 1.0 To: IDN Subject: [idn] converter page? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=1.2 required=5.0 tests=RCVD_IN_RFCI,SIGNATURE_SHORT_DENSE,SPAM_PHRASE_00_01, TO_LOCALPART_EQ_REAL,USER_AGENT,USER_AGENT_MOZILLA_UA, X_ACCEPT_LANG version=2.43 X-Spam-Level: * Sender: owner-idn@ops.ietf.org Precedence: bulk Content-Transfer-Encoding: 7bit Anybody know of a web form that does IDNA conversion on-the-fly? Something that will let me enter the domain name and get the IDNA encoded form back. I find myself needing to do do some quicky conversions periodically. Thanks -- Eric A. Hall http://www.ehsco.com/ Internet Core Protocols http://www.oreilly.com/catalog/coreprot/