1 |
From owner-idn@ops.ietf.org Tue Feb 11 18:29:56 2003 |
2 |
Return-path: <owner-idn@ops.ietf.org> |
3 |
Envelope-to: idn-data@psg.com |
4 |
Delivery-date: Tue, 11 Feb 2003 18:29:56 -0800 |
5 |
Received: from lserv by psg.com with local (Exim 3.36 #1) |
6 |
id 18imbT-000PWE-00 |
7 |
for idn-data@psg.com; Tue, 11 Feb 2003 18:26:27 -0800 |
8 |
Received: from santee.icann.org ([192.0.35.122]) |
9 |
by psg.com with esmtp (Exim 3.36 #1) |
10 |
id 18imbQ-000PVy-00 |
11 |
for idn@ops.ietf.org; Tue, 11 Feb 2003 18:26:24 -0800 |
12 |
Received: from tarim (tarim.icann.org [192.0.35.80]) |
13 |
by santee.icann.org (8.11.6/8.11.6) with SMTP id h1C2QML07613; |
14 |
Tue, 11 Feb 2003 18:26:23 -0800 |
15 |
From: "IANA" <iana@iana.org> |
16 |
To: <idn@ops.ietf.org> |
17 |
Cc: "IESG" <iesg@ietf.org> |
18 |
Subject: [idn] Results of IANA Selection of IDNA Prefix |
19 |
Date: Tue, 11 Feb 2003 18:17:31 -0800 |
20 |
Message-ID: <HEEHIJAAIOLDCMKIFMKLIEDLCDAA.iana@iana.org> |
21 |
MIME-Version: 1.0 |
22 |
Content-Type: text/plain; |
23 |
charset="us-ascii" |
24 |
Content-Transfer-Encoding: 7bit |
25 |
X-Priority: 3 (Normal) |
26 |
X-MSMail-Priority: Normal |
27 |
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) |
28 |
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 |
29 |
Importance: Normal |
30 |
X-Spam-Status: No, hits=0.9 required=5.0 |
31 |
tests=LINES_OF_YELLING,LINES_OF_YELLING_2,SPAM_PHRASE_01_02, |
32 |
USER_AGENT_OUTLOOK |
33 |
version=2.43 |
34 |
X-Spam-Level: |
35 |
Sender: owner-idn@ops.ietf.org |
36 |
Precedence: bulk |
37 |
|
38 |
|
39 |
Results of IANA Selection of IDNA Prefix |
40 |
|
41 |
As described in section B of the Protocol and Schedule |
42 |
(see below), today 11 February 2003 (Tuesday), is the |
43 |
Selection Day. |
44 |
|
45 |
The IANA followed the steps described in section 4 (see |
46 |
below). |
47 |
|
48 |
The twelve stocks and their trading volumes (in 100s) were: |
49 |
|
50 |
(NYSE) IMS Hlth RX 22157 |
51 |
(NYSE) IL Tool ITW 11795 |
52 |
(NYSE) IntRectifr IRF 5742 |
53 |
(NYSE) IBM IBM 78719 |
54 |
(NYSE) IntPaper IP 16609 |
55 |
(NYSE) Interpublic IPG 34961 |
56 |
(NASDAQ) Inamed IMDC 1567 |
57 |
(NASDAQ) Informatica INFA 4357 |
58 |
(NASDAQ) Inktomi INKT 6085 |
59 |
(NASDAQ) i2 Tch ITWO 37777 |
60 |
(NASDAQ) IDEC Pharm IDPH 18754 |
61 |
(NASDAQ) Intel INTC 524545 |
62 |
|
63 |
These trading volumes have been used to generate a key |
64 |
string in the manner specified on page 5 of RFC 2777. |
65 |
|
66 |
The key string is |
67 |
|
68 |
|
69 |
22157./11795./5742./78719./16609./34961./1567./4357./6085./37777./18754./524 |
70 |
545./ |
71 |
|
72 |
The hex value of MD5 is |
73 |
|
74 |
BDEC8317C50316D67B688D1C9A34C682 |
75 |
|
76 |
The hex value of MD5 was then divided by eighteen. The remainder |
77 |
of the division (10) plus one (11) is the position of the |
78 |
selected candidate in the ordered list below. |
79 |
|
80 |
According to the ordered list, the selected code is "XN". |
81 |
|
82 |
1. XB 7. XH 13. XQ |
83 |
2. XC 8. XJ 14. XR |
84 |
3. XD 9. XK 15. XT |
85 |
4. XE 10. XM 16. XW |
86 |
5. XF 11. XN 17. XX |
87 |
6. XG 12. XP 18. XY |
88 |
|
89 |
As stated in section 6 of our message below: |
90 |
|
91 |
If anyone disagrees with the computation of the result under the |
92 |
above protocol as announced by the IANA on the Selection Day, please |
93 |
send a note to <iana@iana.org> no later than the day before the |
94 |
Notification Day. The RFC Editor will be notified of the selected code |
95 |
on the Notification Day (Friday, 14 February 2003). |
96 |
|
97 |
Thank you, |
98 |
|
99 |
The Internet Assigned Numbers Authority |
100 |
|
101 |
|
102 |
************************************************************************ |
103 |
|
104 |
-----Original Message----- |
105 |
From: IANA [mailto:iana@iana.org] |
106 |
Sent: Monday, February 10, 2003 2:44 PM |
107 |
To: idn@ops.ietf.org |
108 |
Subject: FW: IANA Selection of IDNA Prefix |
109 |
|
110 |
This document sets forth the protocol by which the IANA will select |
111 |
a two-character code to be used as the first two characters of |
112 |
the ACE prefix referred to as "IESG--" in Section 5 of |
113 |
draft-ietf-idn-idna-14.txt. It also specifies the schedule for |
114 |
the selection. |
115 |
|
116 |
This document is based on the IANA's proposed Protocol and Schedule |
117 |
distributed on 30 January 2003 and reflects changes to address |
118 |
comments received by 6 February 2003. The IANA thanks Adam Costello |
119 |
and Simon Josefsson for their comments. |
120 |
|
121 |
A. Protocol |
122 |
|
123 |
The following steps will be used to select the two-character code: |
124 |
|
125 |
1. The code will be selected from among a subset of the entries on |
126 |
the ISO 3166-1:1997, clause 8.1.3 User-assigned alpha-2 code elements: |
127 |
AA, QM to QZ, XA to XZ, and ZZ. The selection is limited to these |
128 |
codes because of the following: |
129 |
|
130 |
a) The use of numeric characters, while permitted by the |
131 |
Internet-Draft, would create visual ambiguities concerning the |
132 |
digits "0", "1", and "5". (For similar reasons, codes including |
133 |
the letters O, I, L, and S are eliminated in step 3.) |
134 |
|
135 |
b) The use of ISO 3166-1 the user-assigned elements removes the |
136 |
possibility that the code will duplicate a present or future |
137 |
ccTLD code. |
138 |
|
139 |
2. An eligible subset of that list of 42 entries will be determined |
140 |
by eliminating the following codes due to their use, in one or more |
141 |
top-level domain zone files that have been reviewed, as the first two |
142 |
characters of second-level domain labels that have hyphens in their |
143 |
third and fourth character positions: |
144 |
AA, QM to QZ, XA, XZ, and ZZ. |
145 |
|
146 |
3. This leaves the following subset of twenty-four candidate codes: |
147 |
XB, XC, XD, XE, XF, XG, XH, XI, XJ, XK, XL, XM, XN, XO, XP, XQ, XR, XS, |
148 |
XT, XU, XV, XW, XX, and XY. Of those codes, XI, XL, XO, and XS are |
149 |
eliminated due to potential confusion with X1, X1, X0, and X5, and XU |
150 |
and XV are eliminated due to potential confusion with each other. |
151 |
This leaves eighteen candidate codes. |
152 |
|
153 |
4. A random selection will be made from among the eighteen |
154 |
candidates. The algorithm for the random selection will generally |
155 |
follow that stated in RFC 2777. |
156 |
|
157 |
First, the eighteen candidates will be arranged in an ordered list |
158 |
as follows: |
159 |
|
160 |
1. XB 7. XH 13. XQ |
161 |
2. XC 8. XJ 14. XR |
162 |
3. XD 9. XK 15. XT |
163 |
4. XE 10. XM 16. XW |
164 |
5. XF 11. XN 17. XX |
165 |
6. XG 12. XP 18. XY |
166 |
|
167 |
Next, the trading volume of twelve stocks on the Reference Day (see |
168 |
schedule below), as listed in the U.S. National Edition of the Wall |
169 |
Street Journal on the Selection Day (see schedule below), will be used |
170 |
to generate a key string in the manner specified on page 5 of RFC 2777. |
171 |
The twelve stocks are: |
172 |
|
173 |
(NYSE) IMS Hlth RX |
174 |
(NYSE) IL Tool ITW |
175 |
(NYSE) IntRectifr IRF |
176 |
(NYSE) IBM IBM |
177 |
(NYSE) IntPaper IP |
178 |
(NYSE) Interpublic IPG |
179 |
(NASDAQ) Inamed IMDC |
180 |
(NASDAQ) Informatica INFA |
181 |
(NASDAQ) Inktomi INKT |
182 |
(NASDAQ) i2 Tch ITWO |
183 |
(NASDAQ) IDEC Pharm IDPH |
184 |
(NASDAQ) Intel INTC |
185 |
|
186 |
Although the IANA's investigation indicates that all copies of the U.S. |
187 |
National Edition (on any day other than a Wednesday) of the Wall Street |
188 |
Journal should be identical, to eliminate any ambiguity the IANA will |
189 |
purchase a copy, which will be authoritative, on the morning of the |
190 |
Selection Day at a local store. |
191 |
|
192 |
In the event that the trading volume of any of the above twelve stocks |
193 |
is not reported in that paper, the value 0 will be used for that stock. |
194 |
In the event that more than six of the stocks then have a zero value, |
195 |
the selection will be deemed invalid and re-run in a manner decided |
196 |
according to the circumstances. |
197 |
|
198 |
A key string will be constructed with the numeric trading volumes of the |
199 |
twelve stocks (denoted in 100s and not including any |
200 |
thousands-separating punctuation), in the order stated above, according |
201 |
to page 5 of RFC 2777. An MD5 hash [RFC 1321] of the string, prefixed |
202 |
and suffixed with a zero byte, will be calculated. That value will be |
203 |
divided by eighteen, and the remainder of the division plus one will be |
204 |
the position of the selected candidate in the ordered list above. (Note: |
205 |
The Wall Street Journal currently reports share volumes in 100s. Thus, |
206 |
a volume of 7,660,900 shares would be reported in the Wall Street |
207 |
Journal as "76609" and would be represented as "76609" within the key.) |
208 |
The selection mechanism uses the reference implementation in RFC 2777 |
209 |
and the reference MD5 implementation from RFC 1321. |
210 |
|
211 |
5. A message will be sent to the IETF Announce list to announce |
212 |
the selected code as well as the details of the selection. This |
213 |
message will be sent immediately after the selection is made on |
214 |
the Selection Day, according to the schedule described below. |
215 |
|
216 |
6. If anyone disagrees with the computation of the result under the |
217 |
above protocol as announced by the IANA on the Selection Day, please |
218 |
send a note to <iana@iana.org> no later than the day before the |
219 |
Notification Day. The RFC Editor will be notified of the selected code |
220 |
on the Notification Day. |
221 |
|
222 |
B. Schedule |
223 |
|
224 |
The following schedule will be followed for the selection process: |
225 |
|
226 |
30 January 2003 - Protocol and Schedule published, including to IETF |
227 |
Announce list. Comments invited to <iana@iana.org>. |
228 |
|
229 |
6 February 2003 - Last day for comments. |
230 |
|
231 |
10 February 2003 (Monday) - Reference Day (see above). |
232 |
|
233 |
11 February 2003 (Tuesday) - Selection Day (see above). |
234 |
|
235 |
14 February 2003 (Friday) - Notification Day. |