- Translationtransliterationirt

T/T IRT Member Bandwidth Assessment Request
by Michael Karakash June 4, 2021

June 4, 2021

Dear T/T IRT Members, I hope this message finds you well. As you know, the implementation of the T/T IRT has been on hold since 2019 as we have awaited clarity on a variety of EPDP-related activities. With the completion of certain portions of EPDP work, the GNSO Council has asked ICANN org to gauge our ability, and the IRT members’ capacity, to undertake additional work on this effort. The GNSO Council as well as ICANN org will need to assess bandwidth and priorities to determine what can be supported. We are writing at the Council’s request to gauge your interest and ability to re-engage in work related to this IRT should this be determined to proceed. We ask that if you would wish to continue participation in future work, please respond (off list to me at michael.karakash(a)icann.org<mailto:michael.karakash@icann.org>) affirmatively to indicate your interest by Wednesday, 09 June. We will provide this numerical data to the GNSO Council to inform its deliberations. Please contact me with any questions, and thank you for your time and attention to this matter. Best, Michael Karakash Policy Research Specialist Internet Corporation for Assigned Names and Numbers (ICANN) Telephone: +1 424 416 9205 www.icann.org<http://www.icann.org/>

1 0

Next steps?
by Maxim Alzoba Dec. 16, 2019

Dec. 16, 2019

Hello All, I do understand that we have almost hit the vacations season, but asking just in case - do we envision any next steps with T/T IRT in Jan 2020? -- Sincerely Yours, Maxim Alzoba Special projects manager, International Relations Department, FAITID Current UTC offset: +3.00 (Moscow)

2 1

Update: Translation and Transliteration of Contact Information Implementation
by Brian Aitchison Oct. 31, 2019

Oct. 31, 2019

Dear T/T IRT, As you’re aware, implementation of the T/T PDP recommendations has been on hold pending deployment of RDAP. Over the summer, we worked to assess the T/T Working Group’s recommendations in terms of RDAP, as well as the new recommendations stemming from Phase 1 of the Temporary Specification for gTLD Registration Data Expedited Policy Development Process<https://gnso.icann.org/en/group-activities/active/gtld-registration-data-ep…>(EPDP). We identified the EPDP Team’s Recommendation 27 as pertinent to the T/T implementation: The EPDP Team recommends that, as part of the implementation of [its] policy recommendations, updates are made to the following existing policies / procedures, and any others that may have been omitted [emphasis added], to ensure consistency with these policy recommendations as, for example, a number of these refer to administrative and/or technical contact which will no longer be required data elements: • Registry Registration Data Directory Services Consistent Labeling and Display Policy • Thick WHOIS Transition Policy for .COM, .NET, .JOBS • Rules for Uniform Domain Name Dispute Resolution Policy • WHOIS Data Reminder Policy • Transfer Policy • Uniform Rapid Suspension System (URS) Rules • Transfer Dispute Resolution Policy Given the implementation’s relationship to the evolution of registration data policies and procedures, we propose that the T/T recommendations be added to this list to ensure policy and implementation consistency across the many work streams in this area. This proposal is part practical, and part mandate. The mandate stems from T/T Recommendation 7, which states that implementation of the policy recommendations be “coordinated with other WHOIS modifications where necessary and…implemented and/or applied as soon as a WHOIS replacement system that can receive, store and display non-ASCII characters, becomes operational.” As a practical matter, assessing the T/T recommendations in the context of Recommendation 27 would provide insight into any potential conflicts and/or dependencies as they relate to the EPDP Team’s work. It would also allow for an assessment of whether the T/T recommendations could be “bundled” into the broader implementation work likely to emerge as a result of EPDP recommendations. Please let us know if you have any input on this plan (I’ll be in Montreal if you’d like to catch up in-person). Otherwise, we’ll begin work on assessing the T/T recommendations per Recommendation 27, and will follow up as it progresses. Thank you all very much for your continued support and participation. Brian -- Brian Aitchison, PhD Lead Researcher Operations and Policy Research Global Domains Division Internet Corporation for Assigned Names and Numbers (ICANN) Los Angeles, CA p. 424 353 9041 e. brian.aitchison(a)icann.org<mailto:brian.aitchison@icann.org> Sk. brian.aitchison.icann

3 4

Re: [Translationtransliterationirt] Update: Translation and Transliteration of Contact Information Implementation
by Tan Tanaka, Dennis Oct. 30, 2019

Oct. 30, 2019

Make sense, Brian. Best, Dennis From: Translationtransliterationirt <translationtransliterationirt-bounces(a)icann.org> on behalf of Brian Aitchison <brian.aitchison(a)icann.org> Date: Monday, October 28, 2019 at 3:20 PM To: "translationtransliterationirt(a)icann.org" <translationtransliterationirt(a)icann.org> Cc: Maxim Alzoba <m.alzoba(a)gmail.com> Subject: [EXTERNAL] [Translationtransliterationirt] Update: Translation and Transliteration of Contact Information Implementation Dear T/T IRT, As you’re aware, implementation of the T/T PDP recommendations has been on hold pending deployment of RDAP. Over the summer, we worked to assess the T/T Working Group’s recommendations in terms of RDAP, as well as the new recommendations stemming from Phase 1 of the Temporary Specification for gTLD Registration Data Expedited Policy Development Process<https://gnso.icann.org/en/group-activities/active/gtld-registration-data-ep…>(EPDP). We identified the EPDP Team’s Recommendation 27 as pertinent to the T/T implementation: The EPDP Team recommends that, as part of the implementation of [its] policy recommendations, updates are made to the following existing policies / procedures, and any others that may have been omitted [emphasis added], to ensure consistency with these policy recommendations as, for example, a number of these refer to administrative and/or technical contact which will no longer be required data elements: • Registry Registration Data Directory Services Consistent Labeling and Display Policy • Thick WHOIS Transition Policy for .COM, .NET, .JOBS • Rules for Uniform Domain Name Dispute Resolution Policy • WHOIS Data Reminder Policy • Transfer Policy • Uniform Rapid Suspension System (URS) Rules • Transfer Dispute Resolution Policy Given the implementation’s relationship to the evolution of registration data policies and procedures, we propose that the T/T recommendations be added to this list to ensure policy and implementation consistency across the many work streams in this area. This proposal is part practical, and part mandate. The mandate stems from T/T Recommendation 7, which states that implementation of the policy recommendations be “coordinated with other WHOIS modifications where necessary and…implemented and/or applied as soon as a WHOIS replacement system that can receive, store and display non-ASCII characters, becomes operational.” As a practical matter, assessing the T/T recommendations in the context of Recommendation 27 would provide insight into any potential conflicts and/or dependencies as they relate to the EPDP Team’s work. It would also allow for an assessment of whether the T/T recommendations could be “bundled” into the broader implementation work likely to emerge as a result of EPDP recommendations. Please let us know if you have any input on this plan (I’ll be in Montreal if you’d like to catch up in-person). Otherwise, we’ll begin work on assessing the T/T recommendations per Recommendation 27, and will follow up as it progresses. Thank you all very much for your continued support and participation. Brian -- Brian Aitchison, PhD Lead Researcher Operations and Policy Research Global Domains Division Internet Corporation for Assigned Names and Numbers (ICANN) Los Angeles, CA p. 424 353 9041 e. brian.aitchison(a)icann.org<mailto:brian.aitchison@icann.org> Sk. brian.aitchison.icann

1 0

T/T Implementation Update
by Brian Aitchison June 14, 2019

June 14, 2019

Dear T/T IRT, I’d like to update you on some plans we’ve discussed for the T/T implementation: With the RDAP implementation scheduled for late August, we’re working on our end to assess how the RDAP profile and the T/T policy will work together. We believe it would be best to have RDAP deployed and operational before discussing any modifications to it as a result of the T/T policy (recall T/T WG Rec 7: “The Working Group recommends that these recommendations are coordinated with other WHOIS modifications where necessary and are implemented and/or applied as soon as a WHOIS replacement system that can receive, store and display non-ASCII characters, becomes operational.”) We’ll continue working on this while we await RDAP’s deployment, and re-evaluate our progress in August-September. Also note Recommendation 27 from the Expedited Policy Development Process (EPDP) Working Group, which calls for a review of policies that may be affected by the Group’s recommendations.* The T/T policy/recommendations may fall into this for analysis. That’s all for now. Let me know of any questions or concerns. Otherwise I’ll be in touch as our work progresses. All best, Brian -- Brian Aitchison, PhD Lead Researcher Operations and Policy Research Global Domains Division Internet Corporation for Assigned Names and Numbers (ICANN) Los Angeles, CA p. 424 353 9041 e. brian.aitchison(a)icann.org<mailto:brian.aitchison@icann.org> Sk. brian.aitchison.icann * EPDP Team Recommendation #27. The EPDP Team recommends that as part of the implementation of these policy recommendations, updates are made to the following existing policies / procedures, and any others that may have been omitted, to ensure consistency with these policy recommendations as, for example, a number of these refer to administrative and/or technical contact which will no longer be required data elements: * Registry Registration Data Directory Services Consistent Labeling and Display Policy * Thick WHOIS Transition Policy for .COM, .NET, .JOBS * Rules for Uniform Domain Name Dispute Resolution Policy * WHOIS Data Reminder Policy * Transfer Policy * Uniform Rapid Suspension System (URS) Rules * Transfer Dispute Resolution Policy

2 3

Re: [Translationtransliterationirt] T/T Implementation Update
by Tan Tanaka, Dennis June 13, 2019

June 13, 2019

Sounds good, Brian. Thank you for the update. -Dennis From: Translationtransliterationirt <translationtransliterationirt-bounces(a)icann.org> on behalf of Brian Aitchison <brian.aitchison(a)icann.org> Date: Thursday, June 13, 2019 at 2:32 PM To: "translationtransliterationirt(a)icann.org" <translationtransliterationirt(a)icann.org> Subject: [EXTERNAL] [Translationtransliterationirt] T/T Implementation Update Dear T/T IRT, I’d like to update you on some plans we’ve discussed for the T/T implementation: With the RDAP implementation scheduled for late August, we’re working on our end to assess how the RDAP profile and the T/T policy will work together. We believe it would be best to have RDAP deployed and operational before discussing any modifications to it as a result of the T/T policy (recall T/T WG Rec 7: “The Working Group recommends that these recommendations are coordinated with other WHOIS modifications where necessary and are implemented and/or applied as soon as a WHOIS replacement system that can receive, store and display non-ASCII characters, becomes operational.”) We’ll continue working on this while we await RDAP’s deployment, and re-evaluate our progress in August-September. Also note Recommendation 27 from the Expedited Policy Development Process (EPDP) Working Group, which calls for a review of policies that may be affected by the Group’s recommendations.* The T/T policy/recommendations may fall into this for analysis. That’s all for now. Let me know of any questions or concerns. Otherwise I’ll be in touch as our work progresses. All best, Brian -- Brian Aitchison, PhD Lead Researcher Operations and Policy Research Global Domains Division Internet Corporation for Assigned Names and Numbers (ICANN) Los Angeles, CA p. 424 353 9041 e. brian.aitchison(a)icann.org<mailto:brian.aitchison@icann.org> Sk. brian.aitchison.icann * EPDP Team Recommendation #27. The EPDP Team recommends that as part of the implementation of these policy recommendations, updates are made to the following existing policies / procedures, and any others that may have been omitted, to ensure consistency with these policy recommendations as, for example, a number of these refer to administrative and/or technical contact which will no longer be required data elements: · Registry Registration Data Directory Services Consistent Labeling and Display Policy · Thick WHOIS Transition Policy for .COM, .NET, .JOBS · Rules for Uniform Domain Name Dispute Resolution Policy · WHOIS Data Reminder Policy · Transfer Policy · Uniform Rapid Suspension System (URS) Rules · Transfer Dispute Resolution Policy

1 0

Update: Translation and Transliteration of Contact Information
by Brian Aitchison March 22, 2019

March 22, 2019

Dear T/T IRT and observers, With RDAP now officially in the pipeline, we’re ready to pick up this implementation project again. I had a quick informal chat with Roger and Jim in Kobe, and they agreed it’s a good time to get back on it. I’m dusting off the policy draft, which we’ll review during our next call. We’ll also go over a “to-do” list for the upcoming months. We have a few folks out of the office following the Kobe meeting, but aim to get things moving in early April. I’ll send out a meeting invite around that time. In the meantime, let me know of any questions or suggestions. Hope all are well! Brian -- Brian Aitchison, PhD Lead Researcher Operations and Policy Research Internet Corporation for Assigned Names and Numbers (ICANN) Los Angeles, CA p. 424 353 9041 e. brian.aitchison(a)icann.org<mailto:brian.aitchison@icann.org> Sk. brian.aitchison.icann CONFIDENTIALITY NOTICE: This email and any attachments are for the sole use of the intended recipient(s) and contain information that may be confidential and/or legally privileged. If you have received this email in error, please notify the sender by reply email and delete the message. Any disclosure, copying, distribution or use of this communication by someone other than the intended recipient is prohibited.

2 2

Canceled: T/T IRT Call 16
by Brian Aitchison Aug. 21, 2018

Aug. 21, 2018

Dear T/T IRT, We've decided to postpone tomorrow's T/T IRT call until a later date. It seems that the RDAP profile still needs work and, as you know, T/T is dependent on RDAP for implementation. Once RDAP progresses a bit further, I'll reach out to schedule our next T/T discussion. Thanks very much everyone, and please let me know of any questions. All best, Brian -- Brian Aitchison Lead Researcher Operations & Policy Research Internet Corporation for Assigned Names and Numbers (ICANN) Los Angeles, CA p. 310 578 8688 m. 424 353 9041 e. brian.aitchison(a)icann.org<mailto:brian.aitchison@icann.org> Sk. brian.aitchison.icann CONFIDENTIALITY NOTICE: This email and any attachments are for the sole use of the intended recipient(s) and contain information that may be confidential and/or legally privileged. If you have received this email in error, please notify the sender by reply email and delete the message. Any disclosure, copying, distribution or use of this communication by someone other than the intended recipient is prohibited.

1 0

T/T Call 16 Agenda and Updated Policy Document
by Brian Aitchison Aug. 16, 2018

Aug. 16, 2018

Dear T/T IRT, Looking forward to our meeting next Wednesday. Here’s an agenda for our talk: 1. Review updated T/T policy document 2. Discuss plans for T/T policy in terms of RDAP 3. EPP extensions 4. Proposal for “phased” implementation 5. AOB We have a new ability to use a “team drive” for our working documents. I’ve added Roger, Jim, and Dennis to it. Please check that the following link to the latest policy draft works for you, and let me know if you have any issues: https://docs.google.com/document/d/18VYxsie-nPZ3rCE214IWFUXZADm2NofnZWPlhOR… Once we finalize each subsequent draft, I’ll post it to the T/T wiki for all to view. All best, Brian -- Brian Aitchison Lead Researcher Operations & Policy Research Internet Corporation for Assigned Names and Numbers (ICANN) Los Angeles, CA p. 310 578 8688 m. 424 353 9041 e. brian.aitchison(a)icann.org<mailto:brian.aitchison@icann.org> Sk. brian.aitchison.icann CONFIDENTIALITY NOTICE: This email and any attachments are for the sole use of the intended recipient(s) and contain information that may be confidential and/or legally privileged. If you have received this email in error, please notify the sender by reply email and delete the message. Any disclosure, copying, distribution or use of this communication by someone other than the intended recipient is prohibited.

2 1

T/T IRT Call 16
by Brian Aitchison July 19, 2018

July 19, 2018

* Agenda, updated policy document, and other relevant discussion materials to be circulated about a week ahead of this meeting. Link to Adobe Connect: https://participate.icann.org/aitchison/ * Upon logging into Adobe Connect, a pop-up window will provide you the option to dial out to your phone. Enter your phone number (remember to change the country code if needed). * After joining the call, as a courtesy to others and the presenters, please MUTE your phone. This can be done by entering *6 on your keypad. To UNMUTE enter *6 again. * If you are unable to log into Adobe Connect and can only join via phone: Have the meeting call you (no need to dial in). Click the “Connect Me” link below and enter your phone number when prompted: Connect Me<https://go.conferencinghub.com/1wiwe> Not at your computer? You can join by dialing one of the access numbers below. Mobile: tel://17193252630,*,,1441442688#<tel://17193252630,*,,1441442688/> Phone Only Controls : https://go.conferencinghub.com/1wiwe Primary Access Number: 1-719-325-2630 Guest Passcode: 144 144 2688 Additional Access: USA: 1-719-325-2630 Canada, Calgary: +1 403 407 5780 Canada, Montreal: +1 514 669 5909 Canada, Toronto: +1 416 915 3615 Canada, Vancouver: +1 604 205 5118 Argentina (toll free): 0800 800 1250 Argentina, Buenos Aires: +54 (0) 11 5172 6019 Australia (toll free): 1 800 720 493 Australia, Brisbane: +61 (0) 7 3015 0608 Australia, Melbourne: +61 (0) 3 8687 0614 Australia, Sydney: +61 (0) 2 8017 6391 Austria (toll free): 0800 886 63404 Austria, Vienna: +43 (0) 1 25302 1775 Bahrain (toll free): 8008 1214 Bahrain, Manama: +973 1650 0402 Belarus (toll free): 8 820 0011 0353 Belgium (toll free): 0800 39 268 Belgium, Brussels: +32 (0) 2 400 1980 Brazil (toll free): 0800 887 0283 Brazil, Rio de Janeiro: +55 21 4560 0023 Brazil, Sao Paulo: +55 11 4935 7122 Bulgaria (toll free): 00800 111 4944 Bulgaria, Sofia: +359 (0) 2 491 7244 Canada (toll free): 1 855 950 3706 Chile (toll free): 171 800 835 943 Chile, Santiago: +56 (0) 2 2666 0711 China (national): +400 681 8104 China, Beijing: +86 10 5667 0005 China, Shanghai: +86 21 2039 7079 Colombia (toll free): 01 800 755 0043 Colombia, Bogota: +57 1 508 8112 Costa Rica (toll free): 800 542 5331 Croatia (toll free): 0800 223 004 Cyprus (toll free): 800 97400 Czech Republic (toll free): 800 701 236 Czech Republic, Prague: +420 225 986 505 Denmark (toll free): 80 70 35 78 Denmark, Copenhagen: +45 32 71 16 70 Egypt (toll free): 0800 000 0401 Estonia (toll free): 800 011 1569 Estonia, Tallinn: +372 622 6519 Fiji (toll free): 00800 3317 Finland (toll free): 0800 772 230 Finland, Helsinki: +358 (0) 9 2310 1611 France (national): 0811 655 134 France (national): 0821 231 687 France (toll free): 0800 946 112 France, Paris: +33 (0) 1 76 77 22 50 Germany (national): 01801 001 378 Germany (toll free): 0800 588 9225 Germany, Frankfurt: +49 (0) 69 5060 9515 Germany, Munich: +49 (0) 89 24443 2900 Greece (toll free): 00800 128 811 Greece, Athens: +30 211 181 3815 Hong Kong: +852 3018 9103 Hong Kong (toll free): 800 968 082 Hungary (toll free): 068 001 9662 Hungary, Budapest: +36 1 808 8134 Iceland (toll free): 800 9841 India (toll free): 1800 200 9471 India, Bangalore: +91 (0)80 4803 0619 India, Chennai: +91 (0)44 6688 6057 India, Delhi: +91 (0) 11 6641 1378 India, Mumbai: +91 (0)22 6187 5027 Indonesia (toll free): 007 803 321 8120 Indonesia, Jakarta: +62 21 2188 9079 Ireland (national): 0818 270 287 Ireland (national): 1890 907 722 Ireland (toll free): 1800 937 695 Ireland, Dublin: +353 (0) 1 246 5614 Israel (toll free): 180 921 2890 Israel, Tel Aviv: +972 (0)3 763 0384 Italy (toll free): 800 148 288 Italy, Milan: +39 02 3046 4837 Italy, Rome: +39 06 4523 6635 Japan (mobile): 0120 270 611 Japan (national): 0570 005 744 Japan (toll free): 0120 286 011 Japan, Chiba: +81 (0) 43 321 6880 Japan, Fukuoka: +81 (0) 92 290 6880 Japan, Hiroshima: +81 (0) 82 558 6880 Japan, Nagoya: +81 (0) 52 850 6880 Japan, Osaka: +81 (0) 6 4560 0303 Japan, Sapporo: +81 (0) 11 234 6880 Japan, Sendai: +81 (0) 22 708 6880 Japan, Shizuoka: +81 (0) 54 902 6880 Japan, Tachikawa: +81 (0) 42 841 6880 Japan, Tokyo: +81 (0) 3 4560 1274 Japan, Toyama: +81 (0) 76 408 6880 Japan, Urawa: +81 (0) 48 698 6880 Japan, Yokohama: +81 (0) 45 677 6880 Kazakhstan (toll free): 8800 333 7552 Latvia (toll free): 8000 4374 Latvia, Riga: +371 6778 2598 Lithuania (toll free): 8800 31445 Lithuania, Vilnius: +370 5205 5239 Luxembourg: +352 2730 2276 Luxembourg (toll free): 800 28428 Malaysia (toll free): 1 800 815 805 Malaysia,Kuala Lumpur: +60 (0) 3 7723 7140 Mexico (toll free): 01 800 283 3129 Mexico, Guadalajara: +52 33 4162 5891 Mexico, Mexico City: +52 55 8421 0857 Mexico, Monterrey: +52 81 4770 2472 Morocco (toll free): 0800 092 258 Morocco, Casablanca: +212 (0)520 480 128 Netherlands (toll free): 0800 020 0593 Netherlands, Amsterdam: +31 (0) 20 716 8266 New Zealand (toll free): 0800 459 127 New Zealand, Auckland: +64 (0) 9 929 1769 New Zealand, Christchurch: +64 (0) 3 974 2597 New Zealand, Wellington: +64 (0) 4 909 4676 Nigeria, Lagos: +234 1 277 5140 Norway (toll free): 800 58459 Norway, Oslo: +47 2162 4054 Oman (toll free): 800 77269 Panama (toll free): 00800 223 1430 Panama, Panama City: +507 8 339 782 Peru (toll free): 0800 78125 Peru, Lima: +51 (0) 1 700 9587 Philippines (toll free): 1800 111 017 51 Philippines, Manila: +63 (0)2 395 3365 Poland (toll free): 00800 121 4340 Poland, Warsaw: +48 22 295 3504 Portugal (toll free): 800 784 434 Portugal, Lisbon: +351 21 316 4041 Qatar (toll free): 00 800 100 499 Romania (toll free): 0800 801 030 Romania, Bucharest: +40 (0) 21 529 3969 Russia (toll free): 8 800 500 9319 Russia, Moscow: +7 495 213 0988 Saudi Arabia (toll free): 800 844 4963 Saudi Arabia (toll free): 800 850 0227 Serbia (toll free): 0800 190 698 Singapore: +65 6622 1773 Singapore (toll free): 800 616 3175 Slovakia (toll free): 0800 001 661 Slovakia, Bratislava: +421 (0)2 3321 5333 Slovenia (toll free): 0800 80994 Slovenia, Ljubljana: +386 1 600 1622 South Africa (toll free): 0800 988 886 South Africa, Johannesburg: +27 (0)11 019 7087 South Korea (toll free): 007 986 136 2233 South Korea, Seoul: +82 (0) 2 6007 0072 Spain (toll free): 900 803 689 Spain, Barcelona: +34 93 800 1935 Spain, Madrid: +34 91 114 6640 Sweden (toll free): 0200 125 456 Sweden, Stockholm: +46 (0) 8 5065 3944 Switzerland (toll free): 0800 841 702 Switzerland, Geneva: +41 (0) 22 595 4857 Switzerland, Zurich: +41 (0) 44 580 7246 Taiwan (toll free): 00 801 615 184 Taiwan, Taipei: +886 (0) 2 2656 7213 Thailand (toll free): 001 800 6136 2243 Turkey (toll free): 00 800 448 828 358 Turkey, Istanbul: +90 212 375 50 13 UAE (toll free): 8000 3570 2638 UK (03): +44 (0)330 336 6010 UK (national): 0844 473 5003 UK (national): 0845 545 0040 UK (toll free): 0800 368 0950 Ukraine (toll free): 0800 500 732 Uruguay (toll free): 0004 019 0561 USA /Canada (toll free): 1-855-747-8824 Venezuela (toll free): 0800 102 9660 Venezuela, Caracas: +58 212 720 2342 Vietnam (toll free): 1800 9228

1 0