- Gnso-igo-ingo-ip-irt - lists.icann.org

**REMINDER** Meeting Invitation: GO/INGO Identifiers Protection teleconference on Thursday, 25 January 2018 20:00 UTC
by Michelle DeSmyter Jan. 24, 2018

Jan. 24, 2018

Dear Colleagues, There will be an IGO/INGO Identifiers Protection teleconference scheduled for Thursday, 25 January 2018 from 20:00 to 21:00 UTC (other time zones:https://tinyurl.com/y8fk8rxp) Remote Participation: Adobe Connect: https://participate.icann.org/iiip-irt/ Guest code: 9744659233 USA: 1-719-457-1414 Canada, Calgary: +1 403 407 5792 Canada, Montreal: +1 514 669 5944 Canada, Toronto: +1 647 426 9168 Canada, Vancouver: +1 604 224 1367 Argentina (toll free): 0800 800 1222 Argentina, Buenos Aires: +54 (0) 11 5172 6012 Australia (toll free): 1 800 804 723 Australia, Brisbane: +61 (0) 7 3015 0541 Australia, Melbourne: +61 (0) 3 8687 0557 Australia, Sydney: +61 (0) 2 8017 6141 Austria (toll free): 0800 8866 3406 Austria, Vienna: +43 (0) 1 25302 1913 Bahrain (toll free): 800 04075 Bahrain, Manama: +973 1619 8740 Belarus (toll free): 8 820 0011 0349 Belgium (toll free): 0800 39270 Belgium, Brussels: +32 (0) 2 400 6949 Brazil (toll free): 0800 887 0276 Brazil, Rio de Janeiro: +55 21 4560 0000 Brazil, Sao Paulo: +55 11 4935 7173 Bulgaria (toll free): 00800 111 4994 Bulgaria, Sofia: +359 (0) 2 491 6046 Canada (toll free): 1 855 950 3716 Chile (toll free): 171 800 835 779 Chile, Santiago: +56 (0) 2 2666 0695 China (national): +400 613 8102 China, Beijing: +86 10 5667 0002 China, Shanghai: +86 21 2039 7080 Colombia (toll free): 01 800 755 0091 Colombia, Bogota: +57 1 508 8134 Costa Rica (toll free): 800 542 5354 Croatia (toll free): 0800 7744 Cyprus (toll free): 800 97414 Czech Republic (toll free): 800 142 926 Czech Republic, Prague: +420 225 986 562 Denmark (toll free): 80 25 00 00 Denmark, Copenhagen: +45 32 72 78 89 Egypt (toll free): 0800 000 0540 Estonia (toll free): 800 011 1585 Estonia, Tallinn: +372 622 6557 Fiji (toll free): 00800 3321 Finland (toll free): 0800 770 321 Finland, Helsinki: +358 (0) 9 2310 1662 France (national): 0811 655 104 France (national): 0821 231 670 France (toll free): 0805 101 205 France, Paris: +33 (0) 1 76 77 22 58 Germany (national): 01801 001 073 Germany (toll free): 0800 588 9227 Germany, Frankfurt: +49 (0) 69 5060 9538 Germany, Munich: +49 (0) 89 7104 3510 Greece (toll free): 00800 128 827 Greece, Athens: +30 211 181 3858 Hong Kong: +852 3018 9110 Hong Kong (toll free): 800 930 242 Hungary (toll free): 068 002 0141 Hungary, Budapest: +36 1408 8955 Iceland (toll free): 800 8378 India (toll free): 1800 200 9413 India, Bangalore: +91 (0)80 4803 0601 India, Chennai: +91(0)44 6688 6079 India, Delhi: +91 (0) 11 6641 1352 India, Mumbai: +91 (0)22 6187 5038 Indonesia (toll free): 007 803 321 8932 Ireland (national): 0818 270 270 Ireland (national): 1890 907 633 Ireland (toll free): 1800 936 896 Ireland, Dublin: +353 (0) 1 246 5616 Israel (toll free): 1809 246 054 Israel, Tel Aviv: +972 (0)3 721 7933 Italy (toll free): 800 148 223 Italy, Milan: +39 02 3600 8021 Italy, Rome: +39 06 8750 0695 Japan (mobile): 0120 526 211 Japan (national): 0570 039 744 Japan (toll free): 0120 625 211 Japan, Osaka: +81 (0) 6 4560 2415 Japan, Tokyo: +81 (0) 3 4560 1269 Kazakhstan (toll free): 8800 333 7569 Latvia (toll free): 8000 3408 Latvia, Riga: +371 6601 3632 Lithuania (toll free): 8800 31460 Lithuania, Vilnius: +370 5205 5473 Luxembourg: +352 2088 1756 Luxembourg (toll free): 800 24393 Malaysia (toll free): 1 800 816 163 Malaysia,Kuala Lumpur: +60 (0) 3 7724 8015 Mexico (toll free): 01 800 733 4101 Mexico, Guadalajara: +52 33 4162 4503 Mexico, Mexico City: +52 55 8421 0117 Mexico, Monterrey: +52 81 4162 3884 Morocco (toll free): 0800 091 309 Morocco, Casablanca: +212 (0) 525 06 0228 Netherlands (toll free): 0800 023 0691 Netherlands, Amsterdam: +31 (0) 20 715 3980 New Zealand (toll free): 0800 452 941 New Zealand, Auckland: +64 (0) 9 929 1833 New Zealand, Christchurch: +64 (0) 3 974 2594 New Zealand, Wellington: +64 (0) 4 909 4677 Nigeria, Lagos: +234 1 277 3943 Norway (toll free): 800 51061 Norway, Oslo: +47 21 00 26 03 Panama (toll free): 00800 223 1389 Panama, Panama City: +507 8 335 912 Peru (toll free): 0800 78101 Peru, Lima: +51 (0) 1 700 9570 Philippines (toll free): 1 800 111 014 10 Philippines, Manila: +63 (0)2 395 3425 Poland (toll free): 00 800 121 4362 Poland, Warsaw: +48 22 295 3578 Portugal (toll free): 800 784 436 Portugal, Lisbon: 2131 80031 Qatar (toll free): 00 800 100 490 Romania (toll free): 0800 885 830 Romania, Bucharest: +40 (0) 31 810 7132 Russia (toll free): 810 800 2504 1012 Russia, Moscow: +7 495 646 1861 Saudi Arabia (toll free): 800 844 8424 Saudi Arabia (toll free): 800 850 0218 Serbia (toll free): 0800 190 709 Singapore: +65 6622 1961 Singapore (toll free): 800 616 3196 Slovakia (toll free): 0800 002 007 Slovakia, Bratislava: +421 (0)2 3321 5499 Slovenia (toll free): 0800 81127 Slovenia, Ljubljana: +386 1888 8188 South Africa (toll free): 0800 999 287 South Africa, Johannesburg: +27 (0)11 589 8329 South Korea (toll free): 00798 6136 1459 South Korea, Seoul: +82 (0) 2 6007 0078 Spain (toll free): 900 803 691 Spain, Barcelona: +34 93 800 1968 Spain, Madrid: +34 91 114 7290 Sweden (toll free): 0200 883 444 Sweden, Stockholm: +46 (0) 8 5066 2770 Switzerland (toll free): 0800 841 704 Switzerland, Geneva: +41 (0) 22 595 4798 Switzerland, Zurich: +41 (0) 44 580 7251 Taiwan (toll free): 0800 666 672 Taiwan, Taipei: +886 (0) 2 2650 7334 Thailand (toll free): 001 800 6136 1477 Turkey (toll free): 00 800 4488 28190 Turkey, Istanbul: +90 212 375 5021 UAE (toll free): 8000 3570 2669 UK (03): +44 (0)330 336 6001 UK (national): 0844 473 5009 UK (national): 0845 545 0018 UK (toll free): 0800 368 0952 Ukraine (toll free): 0800 500 689 Uruguay (toll free): 0004 019 0188 USA /Canada (toll free): 1-888-619-1583 Venezuela (toll free): 0 800 100 8300 Venezuela, Caracas: +58 212 720 2159 Vietnam (toll free): 1201 1445

1 0

Announced: Protection of IGO and INGO Identifiers Policy published on 16 January 2018
by Dennis Chang Jan. 16, 2018

Jan. 16, 2018

Dear IRT, Congratulations! Our policy has now been published. https://www.icann.org/news/announcement-2018-01-16-en — Kind Regards, Dennis S. Chang GDD Services & Engagement Program Director +1 213 293 7889 Skype: dennisSchang www.icann.org "One World, One Internet"

5 4

Protection of IGO and INGO Identifiers Policy to be published - Thanks to the IRT!
by Dennis Chang Jan. 12, 2018

Jan. 12, 2018

Dear IRT, Happy New Year! 2018 is starting out with a bang for us. Thank you and congratulations! I am happy to report to you that our policy is now scheduled to be published next week. I’ll let you know as soon as I see the announcement. My sincere gratitude and respect for your contribution and guidance over the past two years. We’ve overcame many obstacles. How many can you count - why we can’t implement? Of course, implementation isn’t complete until the policy effective date or dates in our case. And I’ll write again soon for our next steps but I just wanted to take a moment now and share the good news with you all. By You All, I mean: 1 Brian Cimbolic Public Interest Registry (PIR) 2 Crystal Ondo Donuts 3 Jean-Francois Vanden Eynde Nameshield SAS 4 Jim Bikoff Smith, Gambrell & Russell LLP 5 Keith Drazek - GNSO Council Liaison Verisign 6 Lori Schulman International Trademark Association (INTA) 7 Michael Flemming GMO Brights Consulting Inc. 8 Mike Rodenbaugh Rodenbaugh Law 9 Petter Rindforth Fenix Legal KB 10 Dennis Tanaka Verisign Here is to IGOs and INGOs! — Kind Regards, Dennis S. Chang GDD Services & Engagement Program Director +1 213 293 7889 Skype: dennisSchang www.icann.org "One World, One Internet"

2 1

Doodle poll reminder - IGO INGO IRT 2018 meeting schedule
by Michelle DeSmyter Jan. 2, 2018

Jan. 2, 2018

Hello IGO INGO IRT members and Happy New Year! I wanted to touch base with you for those who have not filled out the doodle poll yet to determine out 2018 meeting schedule, if you would do so by no later than tomorrow, Wednesday, 03 January. https://doodle.com/poll/v9mihpk5faweu53v[doodle.com] Thank you so much, Kind regards, Michelle Michelle DeSmyter GDD / GNSO SO/AC Support coordinator Internet Corporation for Assigned Names and Numbers (ICANN) Email: michelle.desmyter(a)icann.org <michelle.desmyter(a)icann.org>

1 1

Doodle poll 2018 meeting schedule for IGO INGO IRT
by Michelle DeSmyter Dec. 15, 2017

Dec. 15, 2017

Dear IGO INGO IRT members, Would you please fill out this Doodle poll to help us determine a good time for our meetings scheduled in 2018. Please keep in mind all of these dates listed land on a Thursday, thank you so much! https://doodle.com/poll/v9mihpk5faweu53v Kind regards, Michelle DeSmyter

1 0

IGO/INGO Identifiers Protection - IRT Meeting
by Michelle DeSmyter Dec. 13, 2017

Dec. 13, 2017

Dear Colleagues, There will be an IGO/INGO Identifiers Protection teleconference scheduled for Thursday, 14 December 2017 from 19:00 to 20:00 UTC (other time zones:http://tinyurl.com/hqqveqf) Please also find attached meeting invite for your convenience. Remote Participation: Adobe Connect: https://participate.icann.org/iiip-irt/ Guest code: 9744659233 USA: 1-719-457-1414 Canada, Calgary: +1 403 407 5792 Canada, Montreal: +1 514 669 5944 Canada, Toronto: +1 647 426 9168 Canada, Vancouver: +1 604 224 1367 Argentina (toll free): 0800 800 1222 Argentina, Buenos Aires: +54 (0) 11 5172 6012 Australia (toll free): 1 800 804 723 Australia, Brisbane: +61 (0) 7 3015 0541 Australia, Melbourne: +61 (0) 3 8687 0557 Australia, Sydney: +61 (0) 2 8017 6141 Austria (toll free): 0800 8866 3406 Austria, Vienna: +43 (0) 1 25302 1913 Bahrain (toll free): 800 04075 Bahrain, Manama: +973 1619 8740 Belarus (toll free): 8 820 0011 0349 Belgium (toll free): 0800 39270 Belgium, Brussels: +32 (0) 2 400 6949 Brazil (toll free): 0800 887 0276 Brazil, Rio de Janeiro: +55 21 4560 0000 Brazil, Sao Paulo: +55 11 4935 7173 Bulgaria (toll free): 00800 111 4994 Bulgaria, Sofia: +359 (0) 2 491 6046 Canada (toll free): 1 855 950 3716 Chile (toll free): 171 800 835 779 Chile, Santiago: +56 (0) 2 2666 0695 China (national): +400 613 8102 China, Beijing: +86 10 5667 0002 China, Shanghai: +86 21 2039 7080 Colombia (toll free): 01 800 755 0091 Colombia, Bogota: +57 1 508 8134 Costa Rica (toll free): 800 542 5354 Croatia (toll free): 0800 7744 Cyprus (toll free): 800 97414 Czech Republic (toll free): 800 142 926 Czech Republic, Prague: +420 225 986 562 Denmark (toll free): 80 25 00 00 Denmark, Copenhagen: +45 32 72 78 89 Egypt (toll free): 0800 000 0540 Estonia (toll free): 800 011 1585 Estonia, Tallinn: +372 622 6557 Fiji (toll free): 00800 3321 Finland (toll free): 0800 770 321 Finland, Helsinki: +358 (0) 9 2310 1662 France (national): 0811 655 104 France (national): 0821 231 670 France (toll free): 0805 101 205 France, Paris: +33 (0) 1 76 77 22 58 Germany (national): 01801 001 073 Germany (toll free): 0800 588 9227 Germany, Frankfurt: +49 (0) 69 5060 9538 Germany, Munich: +49 (0) 89 7104 3510 Greece (toll free): 00800 128 827 Greece, Athens: +30 211 181 3858 Hong Kong: +852 3018 9110 Hong Kong (toll free): 800 930 242 Hungary (toll free): 068 002 0141 Hungary, Budapest: +36 1408 8955 Iceland (toll free): 800 8378 India (toll free): 1800 200 9413 India, Bangalore: +91 (0)80 4803 0601 India, Chennai: +91(0)44 6688 6079 India, Delhi: +91 (0) 11 6641 1352 India, Mumbai: +91 (0)22 6187 5038 Indonesia (toll free): 007 803 321 8932 Ireland (national): 0818 270 270 Ireland (national): 1890 907 633 Ireland (toll free): 1800 936 896 Ireland, Dublin: +353 (0) 1 246 5616 Israel (toll free): 1809 246 054 Israel, Tel Aviv: +972 (0)3 721 7933 Italy (toll free): 800 148 223 Italy, Milan: +39 02 3600 8021 Italy, Rome: +39 06 8750 0695 Japan (mobile): 0120 526 211 Japan (national): 0570 039 744 Japan (toll free): 0120 625 211 Japan, Osaka: +81 (0) 6 4560 2415 Japan, Tokyo: +81 (0) 3 4560 1269 Kazakhstan (toll free): 8800 333 7569 Latvia (toll free): 8000 3408 Latvia, Riga: +371 6601 3632 Lithuania (toll free): 8800 31460 Lithuania, Vilnius: +370 5205 5473 Luxembourg: +352 2088 1756 Luxembourg (toll free): 800 24393 Malaysia (toll free): 1 800 816 163 Malaysia,Kuala Lumpur: +60 (0) 3 7724 8015 Mexico (toll free): 01 800 733 4101 Mexico, Guadalajara: +52 33 4162 4503 Mexico, Mexico City: +52 55 8421 0117 Mexico, Monterrey: +52 81 4162 3884 Morocco (toll free): 0800 091 309 Morocco, Casablanca: +212 (0) 525 06 0228 Netherlands (toll free): 0800 023 0691 Netherlands, Amsterdam: +31 (0) 20 715 3980 New Zealand (toll free): 0800 452 941 New Zealand, Auckland: +64 (0) 9 929 1833 New Zealand, Christchurch: +64 (0) 3 974 2594 New Zealand, Wellington: +64 (0) 4 909 4677 Nigeria, Lagos: +234 1 277 3943 Norway (toll free): 800 51061 Norway, Oslo: +47 21 00 26 03 Panama (toll free): 00800 223 1389 Panama, Panama City: +507 8 335 912 Peru (toll free): 0800 78101 Peru, Lima: +51 (0) 1 700 9570 Philippines (toll free): 1 800 111 014 10 Philippines, Manila: +63 (0)2 395 3425 Poland (toll free): 00 800 121 4362 Poland, Warsaw: +48 22 295 3578 Portugal (toll free): 800 784 436 Portugal, Lisbon: 2131 80031 Qatar (toll free): 00 800 100 490 Romania (toll free): 0800 885 830 Romania, Bucharest: +40 (0) 31 810 7132 Russia (toll free): 810 800 2504 1012 Russia, Moscow: +7 495 646 1861 Saudi Arabia (toll free): 800 844 8424 Saudi Arabia (toll free): 800 850 0218 Serbia (toll free): 0800 190 709 Singapore: +65 6622 1961 Singapore (toll free): 800 616 3196 Slovakia (toll free): 0800 002 007 Slovakia, Bratislava: +421 (0)2 3321 5499 Slovenia (toll free): 0800 81127 Slovenia, Ljubljana: +386 1888 8188 South Africa (toll free): 0800 999 287 South Africa, Johannesburg: +27 (0)11 589 8329 South Korea (toll free): 00798 6136 1459 South Korea, Seoul: +82 (0) 2 6007 0078 Spain (toll free): 900 803 691 Spain, Barcelona: +34 93 800 1968 Spain, Madrid: +34 91 114 7290 Sweden (toll free): 0200 883 444 Sweden, Stockholm: +46 (0) 8 5066 2770 Switzerland (toll free): 0800 841 704 Switzerland, Geneva: +41 (0) 22 595 4798 Switzerland, Zurich: +41 (0) 44 580 7251 Taiwan (toll free): 0800 666 672 Taiwan, Taipei: +886 (0) 2 2650 7334 Thailand (toll free): 001 800 6136 1477 Turkey (toll free): 00 800 4488 28190 Turkey, Istanbul: +90 212 375 5021 UAE (toll free): 8000 3570 2669 UK (03): +44 (0)330 336 6001 UK (national): 0844 473 5009 UK (national): 0845 545 0018 UK (toll free): 0800 368 0952 Ukraine (toll free): 0800 500 689 Uruguay (toll free): 0004 019 0188 USA /Canada (toll free): 1-888-619-1583 Venezuela (toll free): 0 800 100 8300 Venezuela, Caracas: +58 212 720 2159 Vietnam (toll free): 1201 1445

1 0

IRT: IGO and INGO Identifier Protection Policy
by Dennis Chang Dec. 13, 2017

Dec. 13, 2017

Dear IRT, In preparation of our meeting tomorrow, I’d like to provide you with the summary of suggested edits. Most of the suggestions as you’ll see are editorial in nature: clarification, simplification, strengthening of examples and templates, and punctuation correction. My favorite is replacement of all the Dumb Quotes with Smart Quotes. https://docs.google.com/document/d/1cAVS27yshnZIVrbwQQ_zFXWMnOXtcQasj4fnmPO… We’ve benefitted from having fresh eyes on the policy language indeed. One substantive change I’d like to point out for you is in Section 5.1.10 INGO Identifier List Change. We deleted the requirement for the 10 days’ notice to registry operators and registrars. We should have seen this earlier but this requirement has no value since there is no action the registry operators and registrars to take upon the notice. The way the claims system work, each request for registration will require checking the claims system at that time. We can explain further in detail at our meeting tomorrow. Thank you for your contribution. I’ll see you tomorrow. — Kind Regards, Dennis S. Chang GDD Services & Engagement Program Director +1 213 293 7889 Skype: dennisSchang www.icann.org "One World, One Internet"

1 0

Re: [Gnso-igo-ingo-ip-irt] [IRT action by 29 November 2017] IGO&INGO Policy Implementation: call for the iRT support for the final draft and publication
by Tan Tanaka, Dennis Dec. 7, 2017

Dec. 7, 2017

Hi Dennis, What are the next steps from now? Thanks, D.Tanaka From: Dennis Chang <dennis.chang(a)icann.org> Date: Monday, November 27, 2017 at 6:40 PM To: Dennis Tan Tanaka <dtantanaka(a)verisign.com>, "gnso-igo-ingo-ip-irt(a)icann.org" <gnso-igo-ingo-ip-irt(a)icann.org> Cc: Gustavo Lozano <gustavo.lozano(a)icann.org> Subject: [EXTERNAL] [IRT action by 29 November 2017] IGO&INGO Policy Implementation: call for the iRT support for the final draft and publication Thanks Mr. Tanaka for your initiation for discussion and the suggestion for the resolution. Dear IGO&INGO IRT, With this one change, I’ve revised the version number to 19 as you’ll note. https://docs.google.com/document/d/1cAVS27yshnZIVrbwQQ_zFXWMnOXtcQasj4fnmPO… Since no other issues have been raised, we will proceed with the announcement and publication as we had planned. We currently have the following list as Thick IRT members. 1 Brian Cimbolic Public Interest Registry (PIR) 2 Crystal Ondo Donuts 3 Jean-Francois Vandeneynde 4 Jim Bikoff Smith, Gambrell & Russell LLP 5 Keith Drazek - GNSO Council Liaison Verisign 6 Kristine Dorrain Amazon Registry Services 7 Lori Schulman International Trademark Association (INTA) 8 Michael Flemming GMO Brights Consulting Inc. 9 Mike Rodenbaugh Rodenbaugh Law 10 Petter Rindforth Fenix Legal KB 11 Dennis Tanaka Verisign https://community.icann.org/display/IIPIRT/Policy+Implementation+Team+Membe… Please let us know if any members of the IRT have any last-minute issues or concerns prior to the publication. If not, we’d greatly appreciate a simple reply with “support.” Please note that this membership list will be used to document the IRT support. If any member wishes to decline from participating in the IRT, please let us know by 29 November 2017. Thank you! Best, Dennis Chang From: "Tan Tanaka, Dennis" <dtantanaka(a)verisign.com> Date: Monday, November 27, 2017 at 12:17 PM To: Dennis Chang <dennis.chang(a)icann.org>, "gnso-igo-ingo-ip-irt(a)icann.org" <gnso-igo-ingo-ip-irt(a)icann.org> Cc: Gustavo Lozano <gustavo.lozano(a)icann.org> Subject: Re: [Ext] Re: [Gnso-igo-ingo-ip-irt] IGO&INGO Policy Implementation: IRT meeting result and the plan to proceed with publication Dennis, Per our conversation with you and Gustavo Lozano, I’m fine with the current language except for the term “allocation”, which I’m suggesting being replaced by “Effective Allocation” so that it is consistent with the term used in section 5.1.1. Thanks, D.Tanaka From: Dennis Chang <dennis.chang(a)icann.org> Date: Wednesday, November 22, 2017 at 5:30 PM To: Dennis Tan Tanaka <dtantanaka(a)verisign.com>, "gnso-igo-ingo-ip-irt(a)icann.org" <gnso-igo-ingo-ip-irt(a)icann.org> Cc: Gustavo Lozano <gustavo.lozano(a)icann.org> Subject: [EXTERNAL] Re: [Ext] Re: [Gnso-igo-ingo-ip-irt] IGO&INGO Policy Implementation: IRT meeting result and the plan to proceed with publication Thanks Mr. Tanaka for the question and the interesting scenario you presented. The notification Appendix A is designed to list all INGOs. The current example shows two. Names. For your other questions I’ve replied to your comment on the doc and you should have received an email of my reply. I’ve duplicated it here for everyone for convenience. Tanaka Comment: I think we need more time to think this through vis-a-vis registries and registrars requirements. If say, an applied-for string has 10 idn variants, the registry would need to do 10 separate claims checks to the Claims System (CS) (assuming the INGO only registered one name and no variants). Then, would the registry get 10 different Claims Notices IDs from the CS? Will these 10 CNIDs be passed to the registrar and the registrar would present 10 notices to the registrant, to which he/she need to accept? what is registrant accepts two but rejects the other 9. How would that scenario work? Chang Reply Agree that we need to think this through. My thought is that this is the detail we will deal with in the Claims Spec which we will be creating. We will consult with the larger community before releasing it. I have ideas but I'd like wait till the implementation after our publication of this policy if you agree. This is the reason of defining our effective date as we did in section 2.2. Please feel free to give me call on Monday if you’d like or let me know a good time for me to call you. +1 213 293 7889 Skype: dennisSchang When we decide on a design, let’s capture it on our FAQ. I can see this coming up again. Thanks Dennis Chang From: "Tan Tanaka, Dennis" <dtantanaka(a)verisign.com> Date: Wednesday, November 22, 2017 at 1:31 PM To: Dennis Chang <dennis.chang(a)icann.org>, "gnso-igo-ingo-ip-irt(a)icann.org" <gnso-igo-ingo-ip-irt(a)icann.org> Cc: Gustavo Lozano <gustavo.lozano(a)icann.org> Subject: [Ext] Re: [Gnso-igo-ingo-ip-irt] IGO&INGO Policy Implementation: IRT meeting result and the plan to proceed with publication Hi Dennis, I’m processing Section 5.1.8 and have more questions which I posted directly in the document. I can jump on a call after the long weekend if you prefer. Thanks. D.Tanaka From: Gnso-igo-ingo-ip-irt <gnso-igo-ingo-ip-irt-bounces(a)icann.org> on behalf of Dennis Chang <dennis.chang(a)icann.org> Date: Tuesday, November 21, 2017 at 9:00 PM To: "gnso-igo-ingo-ip-irt(a)icann.org" <gnso-igo-ingo-ip-irt(a)icann.org> Cc: Gustavo Lozano <gustavo.lozano(a)icann.org> Subject: [EXTERNAL] [Gnso-igo-ingo-ip-irt] IGO&INGO Policy Implementation: IRT meeting result and the plan to proceed with publication Dear IGO&INGO IRT, Thank you for your valuable and insightful guidance today. As a summary, we made the following decisions on the language at the meeting toay. 1. Add a hyperlink to the INGO Claims System specification. 2. Add “and GNSO” to the list update process when consulting with GAC. Section 4.4. 3. Add IDN Variant case to ensure claims notification for those ROs with IDN Variant policy. Section 5.1.8 4. Add Integration testing requirement for INGO Claims system for clarity and avoid assumption that this will be done since it’s a standard practice. 5.1.9 5. Do not add the Qualified Launch Program clause but instead Add the “or prior to Effective Allocation if the domain name is not going to be available for registration during General Registration” to section 5.0 This method was chosen to make the INGO notification work for current and future QLP like programs 6. Remove INGO contact information from Appendix A. Rationale: the registrant can find the contact using the INGO name and URL on their own. This was done to avoid gathering, storing, or transmitting potentially personal information where we do need it. You’ll find a clean version attached for your convenience. It was downloaded from our collaborative on-line document here: https://docs.google.com/document/d/1cAVS27yshnZIVrbwQQ_zFXWMnOXtcQasj4fnmPO…<https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_docume…> For those IRT members not at the meeting, we are asking for your final review and support of the policy. The recording should be up on our wiki soon. Let us know if you have questions. Barring any issues or objection, we’d like to proceed with the publication process next week. Thanks Dennis Chang From: Gnso-igo-ingo-ip-irt <gnso-igo-ingo-ip-irt-bounces(a)icann.org> on behalf of Dennis Chang <dennis.chang(a)icann.org> Date: Thursday, November 16, 2017 at 8:33 AM To: "gnso-igo-ingo-ip-irt(a)icann.org" <gnso-igo-ingo-ip-irt(a)icann.org> Cc: Gustavo Lozano <gustavo.lozano(a)icann.org> Subject: [Gnso-igo-ingo-ip-irt] IGO&INGO Policy Implementation; 21 Nov 2017 meeting Dear IGO&INGO IRT, By now, you should have received a meeting invite from Michelle for next week Tuesdays, 21 November 2017 We are requesting to meet with the IRT one more time prior to publication. You will note that we have made a few suggested additions to the policy language with brief explanation. https://docs.google.com/document/d/1cAVS27yshnZIVrbwQQ_zFXWMnOXtcQasj4fnmPO…<https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_docume…> We’ll discuss this in detail at the meeting but here is the summary. 1. Add a hyperlink to the INGO Claims System specification 2. Add “and GNSO” to the list update process when consulting with GAC. 3. Add IDN Variant case to avoid registration of INGO names due to the RO Variant policy 4. Add Integration testing requirement for INGO Claims system for clarity and avoid assumption that this will be done since it’s a standard practice 5. Add clarity if need that INGO claims happens on the Qualified Launch Program. Some of these will be obvious but others are nuanced so we probably need to discuss. Please join us. — Kind Regards, Dennis S. Chang GDD Services & Engagement Program Director +1 213 293 7889 Skype: dennisSchang www.icann.org "One World, One Internet"

2 1

Re: [Gnso-igo-ingo-ip-irt] [IRT action by 29 November 2017] IGO&INGO Policy Implementation: call for the iRT support for the final draft and publication
by Tan Tanaka, Dennis Nov. 29, 2017

Nov. 29, 2017

I support the current draft and look forward to working on the INGO Claims System specs. -D.Tanaka From: Dennis Chang <dennis.chang(a)icann.org> Date: Monday, November 27, 2017 at 6:40 PM To: Dennis Tan Tanaka <dtantanaka(a)verisign.com>, "gnso-igo-ingo-ip-irt(a)icann.org" <gnso-igo-ingo-ip-irt(a)icann.org> Cc: Gustavo Lozano <gustavo.lozano(a)icann.org> Subject: [EXTERNAL] [IRT action by 29 November 2017] IGO&INGO Policy Implementation: call for the iRT support for the final draft and publication Thanks Mr. Tanaka for your initiation for discussion and the suggestion for the resolution. Dear IGO&INGO IRT, With this one change, I’ve revised the version number to 19 as you’ll note. https://docs.google.com/document/d/1cAVS27yshnZIVrbwQQ_zFXWMnOXtcQasj4fnmPO… Since no other issues have been raised, we will proceed with the announcement and publication as we had planned. We currently have the following list as Thick IRT members. 1 Brian Cimbolic Public Interest Registry (PIR) 2 Crystal Ondo Donuts 3 Jean-Francois Vandeneynde 4 Jim Bikoff Smith, Gambrell & Russell LLP 5 Keith Drazek - GNSO Council Liaison Verisign 6 Kristine Dorrain Amazon Registry Services 7 Lori Schulman International Trademark Association (INTA) 8 Michael Flemming GMO Brights Consulting Inc. 9 Mike Rodenbaugh Rodenbaugh Law 10 Petter Rindforth Fenix Legal KB 11 Dennis Tanaka Verisign https://community.icann.org/display/IIPIRT/Policy+Implementation+Team+Membe… Please let us know if any members of the IRT have any last-minute issues or concerns prior to the publication. If not, we’d greatly appreciate a simple reply with “support.” Please note that this membership list will be used to document the IRT support. If any member wishes to decline from participating in the IRT, please let us know by 29 November 2017. Thank you! Best, Dennis Chang From: "Tan Tanaka, Dennis" <dtantanaka(a)verisign.com> Date: Monday, November 27, 2017 at 12:17 PM To: Dennis Chang <dennis.chang(a)icann.org>, "gnso-igo-ingo-ip-irt(a)icann.org" <gnso-igo-ingo-ip-irt(a)icann.org> Cc: Gustavo Lozano <gustavo.lozano(a)icann.org> Subject: Re: [Ext] Re: [Gnso-igo-ingo-ip-irt] IGO&INGO Policy Implementation: IRT meeting result and the plan to proceed with publication Dennis, Per our conversation with you and Gustavo Lozano, I’m fine with the current language except for the term “allocation”, which I’m suggesting being replaced by “Effective Allocation” so that it is consistent with the term used in section 5.1.1. Thanks, D.Tanaka From: Dennis Chang <dennis.chang(a)icann.org> Date: Wednesday, November 22, 2017 at 5:30 PM To: Dennis Tan Tanaka <dtantanaka(a)verisign.com>, "gnso-igo-ingo-ip-irt(a)icann.org" <gnso-igo-ingo-ip-irt(a)icann.org> Cc: Gustavo Lozano <gustavo.lozano(a)icann.org> Subject: [EXTERNAL] Re: [Ext] Re: [Gnso-igo-ingo-ip-irt] IGO&INGO Policy Implementation: IRT meeting result and the plan to proceed with publication Thanks Mr. Tanaka for the question and the interesting scenario you presented. The notification Appendix A is designed to list all INGOs. The current example shows two. Names. For your other questions I’ve replied to your comment on the doc and you should have received an email of my reply. I’ve duplicated it here for everyone for convenience. Tanaka Comment: I think we need more time to think this through vis-a-vis registries and registrars requirements. If say, an applied-for string has 10 idn variants, the registry would need to do 10 separate claims checks to the Claims System (CS) (assuming the INGO only registered one name and no variants). Then, would the registry get 10 different Claims Notices IDs from the CS? Will these 10 CNIDs be passed to the registrar and the registrar would present 10 notices to the registrant, to which he/she need to accept? what is registrant accepts two but rejects the other 9. How would that scenario work? Chang Reply Agree that we need to think this through. My thought is that this is the detail we will deal with in the Claims Spec which we will be creating. We will consult with the larger community before releasing it. I have ideas but I'd like wait till the implementation after our publication of this policy if you agree. This is the reason of defining our effective date as we did in section 2.2. Please feel free to give me call on Monday if you’d like or let me know a good time for me to call you. +1 213 293 7889 Skype: dennisSchang When we decide on a design, let’s capture it on our FAQ. I can see this coming up again. Thanks Dennis Chang From: "Tan Tanaka, Dennis" <dtantanaka(a)verisign.com> Date: Wednesday, November 22, 2017 at 1:31 PM To: Dennis Chang <dennis.chang(a)icann.org>, "gnso-igo-ingo-ip-irt(a)icann.org" <gnso-igo-ingo-ip-irt(a)icann.org> Cc: Gustavo Lozano <gustavo.lozano(a)icann.org> Subject: [Ext] Re: [Gnso-igo-ingo-ip-irt] IGO&INGO Policy Implementation: IRT meeting result and the plan to proceed with publication Hi Dennis, I’m processing Section 5.1.8 and have more questions which I posted directly in the document. I can jump on a call after the long weekend if you prefer. Thanks. D.Tanaka From: Gnso-igo-ingo-ip-irt <gnso-igo-ingo-ip-irt-bounces(a)icann.org> on behalf of Dennis Chang <dennis.chang(a)icann.org> Date: Tuesday, November 21, 2017 at 9:00 PM To: "gnso-igo-ingo-ip-irt(a)icann.org" <gnso-igo-ingo-ip-irt(a)icann.org> Cc: Gustavo Lozano <gustavo.lozano(a)icann.org> Subject: [EXTERNAL] [Gnso-igo-ingo-ip-irt] IGO&INGO Policy Implementation: IRT meeting result and the plan to proceed with publication Dear IGO&INGO IRT, Thank you for your valuable and insightful guidance today. As a summary, we made the following decisions on the language at the meeting toay. 1. Add a hyperlink to the INGO Claims System specification. 2. Add “and GNSO” to the list update process when consulting with GAC. Section 4.4. 3. Add IDN Variant case to ensure claims notification for those ROs with IDN Variant policy. Section 5.1.8 4. Add Integration testing requirement for INGO Claims system for clarity and avoid assumption that this will be done since it’s a standard practice. 5.1.9 5. Do not add the Qualified Launch Program clause but instead Add the “or prior to Effective Allocation if the domain name is not going to be available for registration during General Registration” to section 5.0 This method was chosen to make the INGO notification work for current and future QLP like programs 6. Remove INGO contact information from Appendix A. Rationale: the registrant can find the contact using the INGO name and URL on their own. This was done to avoid gathering, storing, or transmitting potentially personal information where we do need it. You’ll find a clean version attached for your convenience. It was downloaded from our collaborative on-line document here: https://docs.google.com/document/d/1cAVS27yshnZIVrbwQQ_zFXWMnOXtcQasj4fnmPO…<https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_docume…> For those IRT members not at the meeting, we are asking for your final review and support of the policy. The recording should be up on our wiki soon. Let us know if you have questions. Barring any issues or objection, we’d like to proceed with the publication process next week. Thanks Dennis Chang From: Gnso-igo-ingo-ip-irt <gnso-igo-ingo-ip-irt-bounces(a)icann.org> on behalf of Dennis Chang <dennis.chang(a)icann.org> Date: Thursday, November 16, 2017 at 8:33 AM To: "gnso-igo-ingo-ip-irt(a)icann.org" <gnso-igo-ingo-ip-irt(a)icann.org> Cc: Gustavo Lozano <gustavo.lozano(a)icann.org> Subject: [Gnso-igo-ingo-ip-irt] IGO&INGO Policy Implementation; 21 Nov 2017 meeting Dear IGO&INGO IRT, By now, you should have received a meeting invite from Michelle for next week Tuesdays, 21 November 2017 We are requesting to meet with the IRT one more time prior to publication. You will note that we have made a few suggested additions to the policy language with brief explanation. https://docs.google.com/document/d/1cAVS27yshnZIVrbwQQ_zFXWMnOXtcQasj4fnmPO…<https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_docume…> We’ll discuss this in detail at the meeting but here is the summary. 1. Add a hyperlink to the INGO Claims System specification 2. Add “and GNSO” to the list update process when consulting with GAC. 3. Add IDN Variant case to avoid registration of INGO names due to the RO Variant policy 4. Add Integration testing requirement for INGO Claims system for clarity and avoid assumption that this will be done since it’s a standard practice 5. Add clarity if need that INGO claims happens on the Qualified Launch Program. Some of these will be obvious but others are nuanced so we probably need to discuss. Please join us. — Kind Regards, Dennis S. Chang GDD Services & Engagement Program Director +1 213 293 7889 Skype: dennisSchang www.icann.org "One World, One Internet"

1 0

[IRT action by 29 November 2017] IGO&INGO Policy Implementation: call for the iRT support for the final draft and publication
by Dennis Chang Nov. 27, 2017

Nov. 27, 2017

Thanks Mr. Tanaka for your initiation for discussion and the suggestion for the resolution. Dear Thick IRT, With this one change, I’ve revised the version number to 19 as you’ll note. https://docs.google.com/document/d/1cAVS27yshnZIVrbwQQ_zFXWMnOXtcQasj4fnmPO… Since no other issues have been raised, we will proceed with the announcement and publication as we had planned. We currently have the following list as Thick IRT members. 1 Brian Cimbolic Public Interest Registry (PIR) 2 Crystal Ondo Donuts 3 Jean-Francois Vandeneynde 4 Jim Bikoff Smith, Gambrell & Russell LLP 5 Keith Drazek - GNSO Council Liaison Verisign 6 Kristine Dorrain Amazon Registry Services 7 Lori Schulman International Trademark Association (INTA) 8 Michael Flemming GMO Brights Consulting Inc. 9 Mike Rodenbaugh Rodenbaugh Law 10 Petter Rindforth Fenix Legal KB 11 Dennis Tanaka Verisign https://community.icann.org/display/IIPIRT/Policy+Implementation+Team+Membe… Please let us know if any members of the IRT have any last-minute issues or concerns prior to the publication. If not, we’d greatly appreciate a simple reply with “support.” Please note that this membership list will be used to document the IRT support. If any member wishes to decline from participating in the IRT, please let us know by 29 November 2017. Thank you! Best, Dennis Chang From: "Tan Tanaka, Dennis" <dtantanaka(a)verisign.com> Date: Monday, November 27, 2017 at 12:17 PM To: Dennis Chang <dennis.chang(a)icann.org>, "gnso-igo-ingo-ip-irt(a)icann.org" <gnso-igo-ingo-ip-irt(a)icann.org> Cc: Gustavo Lozano <gustavo.lozano(a)icann.org> Subject: Re: [Ext] Re: [Gnso-igo-ingo-ip-irt] IGO&INGO Policy Implementation: IRT meeting result and the plan to proceed with publication Dennis, Per our conversation with you and Gustavo Lozano, I’m fine with the current language except for the term “allocation”, which I’m suggesting being replaced by “Effective Allocation” so that it is consistent with the term used in section 5.1.1. Thanks, D.Tanaka From: Dennis Chang <dennis.chang(a)icann.org> Date: Wednesday, November 22, 2017 at 5:30 PM To: Dennis Tan Tanaka <dtantanaka(a)verisign.com>, "gnso-igo-ingo-ip-irt(a)icann.org" <gnso-igo-ingo-ip-irt(a)icann.org> Cc: Gustavo Lozano <gustavo.lozano(a)icann.org> Subject: [EXTERNAL] Re: [Ext] Re: [Gnso-igo-ingo-ip-irt] IGO&INGO Policy Implementation: IRT meeting result and the plan to proceed with publication Thanks Mr. Tanaka for the question and the interesting scenario you presented. The notification Appendix A is designed to list all INGOs. The current example shows two. Names. For your other questions I’ve replied to your comment on the doc and you should have received an email of my reply. I’ve duplicated it here for everyone for convenience. Tanaka Comment: I think we need more time to think this through vis-a-vis registries and registrars requirements. If say, an applied-for string has 10 idn variants, the registry would need to do 10 separate claims checks to the Claims System (CS) (assuming the INGO only registered one name and no variants). Then, would the registry get 10 different Claims Notices IDs from the CS? Will these 10 CNIDs be passed to the registrar and the registrar would present 10 notices to the registrant, to which he/she need to accept? what is registrant accepts two but rejects the other 9. How would that scenario work? Chang Reply Agree that we need to think this through. My thought is that this is the detail we will deal with in the Claims Spec which we will be creating. We will consult with the larger community before releasing it. I have ideas but I'd like wait till the implementation after our publication of this policy if you agree. This is the reason of defining our effective date as we did in section 2.2. Please feel free to give me call on Monday if you’d like or let me know a good time for me to call you. +1 213 293 7889 Skype: dennisSchang When we decide on a design, let’s capture it on our FAQ. I can see this coming up again. Thanks Dennis Chang From: "Tan Tanaka, Dennis" <dtantanaka(a)verisign.com> Date: Wednesday, November 22, 2017 at 1:31 PM To: Dennis Chang <dennis.chang(a)icann.org>, "gnso-igo-ingo-ip-irt(a)icann.org" <gnso-igo-ingo-ip-irt(a)icann.org> Cc: Gustavo Lozano <gustavo.lozano(a)icann.org> Subject: [Ext] Re: [Gnso-igo-ingo-ip-irt] IGO&INGO Policy Implementation: IRT meeting result and the plan to proceed with publication Hi Dennis, I’m processing Section 5.1.8 and have more questions which I posted directly in the document. I can jump on a call after the long weekend if you prefer. Thanks. D.Tanaka From: Gnso-igo-ingo-ip-irt <gnso-igo-ingo-ip-irt-bounces(a)icann.org> on behalf of Dennis Chang <dennis.chang(a)icann.org> Date: Tuesday, November 21, 2017 at 9:00 PM To: "gnso-igo-ingo-ip-irt(a)icann.org" <gnso-igo-ingo-ip-irt(a)icann.org> Cc: Gustavo Lozano <gustavo.lozano(a)icann.org> Subject: [EXTERNAL] [Gnso-igo-ingo-ip-irt] IGO&INGO Policy Implementation: IRT meeting result and the plan to proceed with publication Dear IGO&INGO IRT, Thank you for your valuable and insightful guidance today. As a summary, we made the following decisions on the language at the meeting toay. 1. Add a hyperlink to the INGO Claims System specification. 2. Add “and GNSO” to the list update process when consulting with GAC. Section 4.4. 3. Add IDN Variant case to ensure claims notification for those ROs with IDN Variant policy. Section 5.1.8 4. Add Integration testing requirement for INGO Claims system for clarity and avoid assumption that this will be done since it’s a standard practice. 5.1.9 5. Do not add the Qualified Launch Program clause but instead Add the “or prior to Effective Allocation if the domain name is not going to be available for registration during General Registration” to section 5.0 This method was chosen to make the INGO notification work for current and future QLP like programs 6. Remove INGO contact information from Appendix A. Rationale: the registrant can find the contact using the INGO name and URL on their own. This was done to avoid gathering, storing, or transmitting potentially personal information where we do need it. You’ll find a clean version attached for your convenience. It was downloaded from our collaborative on-line document here: https://docs.google.com/document/d/1cAVS27yshnZIVrbwQQ_zFXWMnOXtcQasj4fnmPO…<https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_docume…> For those IRT members not at the meeting, we are asking for your final review and support of the policy. The recording should be up on our wiki soon. Let us know if you have questions. Barring any issues or objection, we’d like to proceed with the publication process next week. Thanks Dennis Chang From: Gnso-igo-ingo-ip-irt <gnso-igo-ingo-ip-irt-bounces(a)icann.org> on behalf of Dennis Chang <dennis.chang(a)icann.org> Date: Thursday, November 16, 2017 at 8:33 AM To: "gnso-igo-ingo-ip-irt(a)icann.org" <gnso-igo-ingo-ip-irt(a)icann.org> Cc: Gustavo Lozano <gustavo.lozano(a)icann.org> Subject: [Gnso-igo-ingo-ip-irt] IGO&INGO Policy Implementation; 21 Nov 2017 meeting Dear IGO&INGO IRT, By now, you should have received a meeting invite from Michelle for next week Tuesdays, 21 November 2017 We are requesting to meet with the IRT one more time prior to publication. You will note that we have made a few suggested additions to the policy language with brief explanation. https://docs.google.com/document/d/1cAVS27yshnZIVrbwQQ_zFXWMnOXtcQasj4fnmPO…<https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_docume…> We’ll discuss this in detail at the meeting but here is the summary. 1. Add a hyperlink to the INGO Claims System specification 2. Add “and GNSO” to the list update process when consulting with GAC. 3. Add IDN Variant case to avoid registration of INGO names due to the RO Variant policy 4. Add Integration testing requirement for INGO Claims system for clarity and avoid assumption that this will be done since it’s a standard practice 5. Add clarity if need that INGO claims happens on the Qualified Launch Program. Some of these will be obvious but others are nuanced so we probably need to discuss. Please join us. — Kind Regards, Dennis S. Chang GDD Services & Engagement Program Director +1 213 293 7889 Skype: dennisSchang www.icann.org "One World, One Internet"

1 1