October 2017 - Gnso-igo-ingo-ip-irt

IGO/INGO IRT @ ICANN60
by Dennis Chang Oct. 31, 2017

Oct. 31, 2017

12:30 to 1:30PM Thursday, 2 November ICANN 60 - Abu Dhabi, United Arab Emirates - Capital Suite 06 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

IGO/INGO IRT Meeting at ICANN60: on 2 November 2017 at 12:30 to 1:30PM
by Dennis Chang Oct. 30, 2017

Oct. 30, 2017

Dear IGO/INGO IRT, For those at the ICANN60, per your request I’ve found a time that may work for you. 12:30 to 1:30PM Thursday, 2 November ICANN 60 - Abu Dhabi, United Arab Emirates - Capital Suite 06 Please let me know if this does or does not work for you. — 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

FW: IGO Policy Implementation status brief to GNSO: Re: [Ext] Re: Urgent Doodle poll: GNSO Chairs, IGO IRT Liaison and Staff support discussion call
by Dennis Chang Oct. 27, 2017

Oct. 27, 2017

Dear IGO&INGO IRT, FYI, I’ve replied to a follow up email from James, GNSO Council. Nothing new for you here but I wanted to ensure that IRT is in the loop. Thanks Dennis Chang From: Dennis Chang <dennis.chang(a)icann.org> Date: Thursday, October 26, 2017 at 12:56 AM To: "James M. Bladel" <jbladel(a)godaddy.com>, Nathalie Peregrine <nathalie.peregrine(a)icann.org>, "Austin, Donna" <donna.austin(a)team.neustar>, Heather Forrest <haforrestesq(a)gmail.com>, "kdrazek(a)verisign.com" <kdrazek(a)verisign.com>, Mary Wong <mary.wong(a)icann.org>, Steve Chan <steve.chan(a)icann.org>, Berry Cobb <mail(a)berrycobb.com>, Berry Cobb <Berry.Cobb(a)icann.org>, Marika Konings <marika.konings(a)icann.org> Cc: "gnso-secs(a)icann.org" <gnso-secs(a)icann.org> Subject: Re: IGO Policy Implementation status brief to GNSO: Re: [Ext] Re: Urgent Doodle poll: GNSO Chairs, IGO IRT Liaison and Staff support discussion call Dear James, I am in route to Abu Dhabi and caught your email fortunately and I hope this reply will be helpful. I would not characterize it as receiving a “green light” from RySG. The fact is that we did not receive any reply from the RySG yet; so, no light of any color. Stéphane Van Gelder, co-chair, replied at first that the group is working to coalesce around a response and requested more time; then wrote again with the following. “Although members did voice appreciation that ICANN staff reached out to the SG in this proactive fashion to determine our level of support for the proposal as drafted in your letter, the SG as a whole has not ratified a formal position of support. As such, I am loath to try and sum up an SG position for you, beyond the aforementioned appreciation for the way staff have handled this and also, I think it's fair to say, a feeling that the proposal itself is a good faith attempt at taking registry views and realities into account. I have copied the SG on this response so that any individual registry wishing to liaise with you further on this matter can do so.” Upon discussion with the IRT, we’ve decided to proceed with the implementation based on: 1. No objections are received to date 2. Those registries that inquired individually had no objections and confirmed that the approach was reasonable and implementable 3. IRT supported proceeding with the approach including those that are registries 4. There did not seem to be an expected timeline for an official reply and it did not seem appropriate for us to press for a reply and continue to wait I plan to be at the GSNO meeting on Sunday from 11 – 11:30 to brief you on the policy implementation and will be happy to provide further details. Thanks Dennis Chang From: "James M. Bladel" <jbladel(a)godaddy.com> Date: Wednesday, October 25, 2017 at 11:06 AM To: Dennis Chang <dennis.chang(a)icann.org>, Nathalie Peregrine <nathalie.peregrine(a)icann.org>, "Austin, Donna" <donna.austin(a)team.neustar>, Heather Forrest <haforrestesq(a)gmail.com>, "kdrazek(a)verisign.com" <kdrazek(a)verisign.com>, Mary Wong <mary.wong(a)icann.org>, Steve Chan <steve.chan(a)icann.org>, Berry Cobb <mail(a)berrycobb.com>, Berry Cobb <Berry.Cobb(a)icann.org>, Marika Konings <marika.konings(a)icann.org> Cc: "gnso-secs(a)icann.org" <gnso-secs(a)icann.org> Subject: Re: IGO Policy Implementation status brief to GNSO: Re: [Ext] Re: Urgent Doodle poll: GNSO Chairs, IGO IRT Liaison and Staff support discussion call Dear Dennis – Many thanks for this comprehensive update. For clarity on one point: While you still haven’t received a response from the RySG on your letter, you do have a green light from their leadership to proceed with the dual-approach (reserved and claims) plan? Thanks in advance for your response, and safe travels to Abu Dhabi. See you there. Thank you, J. ------------------ James Bladel GNSO Chair From: Dennis Chang <dennis.chang(a)icann.org> Date: Wednesday, October 18, 2017 at 11:40 To: "James M. Bladel" <jbladel(a)godaddy.com>, Nathalie Peregrine <nathalie.peregrine(a)icann.org>, "Austin, Donna" <donna.austin(a)team.neustar>, Heather Forrest <haforrestesq(a)gmail.com>, Keith Drazek <kdrazek(a)verisign.com>, Mary Wong <mary.wong(a)icann.org>, Steve Chan <steve.chan(a)icann.org>, Berry Cobb Mail <mail(a)berrycobb.com>, Berry Cobb <Berry.Cobb(a)icann.org>, Marika Konings <marika.konings(a)icann.org> Cc: "'gnso-secs(a)icann.org'" <gnso-secs(a)icann.org> Subject: IGO Policy Implementation status brief to GNSO: Re: [Ext] Re: Urgent Doodle poll: GNSO Chairs, IGO IRT Liaison and Staff support discussion call Dear GNSO Council, As suggested by James, I am providing you a written report of the status on the IGO/INGO Policy Implementation in lieu of a meeting prior to the ICANN60. Since our last meeting, the following was reported on 10 October 2017 version of the GNSO Project List: “The proposed implementation of GNSO Consensus Policy Recommendation for the Protection of IGO&INGO Identifier in All gTLDs[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_public-2…> was posted for public comment and the summary and analysis report completed. The implementation team is in the process of finalizing the policy document based on the recommendations received in the public comment in collaborations with the IRT.” Specifically, we had been working to resolve conflicting requests from registries. While some registries were requesting short implementation time frame, others asked for much longer duration. Upon research, we had learned that those requesting quick implementation were interested in taking advantage of the exceptions procedure to register reserved names which this policy allows and those who were asking for longer time were concerned about the INGO claims system development. The implementation team devised a plan where we could satisfy both needs by offering two effective dates: one for reserved names and another for claims. This plan was shared with the RySG via a letter[community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_di…>. While RySG has not responded formally, we received a reply from the vice-chair to let us know that there had not been objections voiced to our proposed plan. He also asked the registries to reach out to us individually with their questions and suggestions. As a result, we had additional opportunity to discuss the implementation and further develop it to make it easier to implement with less confusion. Our updated plan calls for an update to the existing reserved name list which avoids duplication of names and potential confusion on which names qualify for the exceptional procedure for registration. This approach has been well received by the IRT. You can view a summary of how these lists will be affected by this policy here[community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_di…>. Currently, the final draft is under review by IRT and we plan to move toward publication with the support of the IRT. While, no IRT session has been scheduled at ICANN60, we may be gathering to take advantage being able to meet in-person. The challenge with this policy implementation is that of scope confusion and we appreciate the close working relationship with the IRT. It’s our aim to keep us together on the same page throughout this implementation. The implementation process also includes collaboration with the IRT such as the creation and release of the INGO Claims system specification. At the moment, I have no request to the GNSO Council. While small in number, the IRT has been responsive and engaged. One good news is that Mr. Dennis Tanaka from Verisign has just joined us as an IRT member. He has been tracking our work having taken over from Chuck Gomes. Please express your appreciation for Mr. Tanaka’s contribution when you get a chance. You’ll note that I will refer to him as Mr. Tanaka to avoid confusion with me. Thank you for the opportunity to brief the council and please don’t hesitate to contact me or the IRT for anything further. I look forward to seeing you all at Abu Dhabi. Safe travel. — Kind Regards, Dennis S. Chang GDD Services & Engagement Program Director +1 213 293 7889 Skype: dennisSchang www.icann.org "One World, One Internet" From: Dennis Chang <dennis.chang(a)icann.org> Date: Monday, October 16, 2017 at 9:34 AM To: "James M. Bladel" <jbladel(a)godaddy.com>, Nathalie Peregrine <nathalie.peregrine(a)icann.org>, "Austin, Donna" <Donna.Austin(a)team.neustar>, Heather Forrest <haforrestesq(a)gmail.com>, "kdrazek(a)verisign.com" <kdrazek(a)verisign.com>, Mary Wong <mary.wong(a)icann.org>, Steve Chan <steve.chan(a)icann.org>, Berry Cobb <mail(a)berrycobb.com>, Berry Cobb <Berry.Cobb(a)icann.org>, Marika Konings <marika.konings(a)icann.org> Cc: "gnso-secs(a)icann.org" <gnso-secs(a)icann.org> Subject: Re: [Ext] Re: Urgent Doodle poll: GNSO Chairs, IGO IRT Liaison and Staff support discussion call Unless I hear otherwise, I’ll provide a written report in the next day or so. Thanks Dennis Chang From: "James M. Bladel" <jbladel(a)godaddy.com> Date: Friday, October 13, 2017 at 9:46 AM To: Nathalie Peregrine <nathalie.peregrine(a)icann.org>, "Austin, Donna" <Donna.Austin(a)team.neustar>, Heather Forrest <haforrestesq(a)gmail.com>, "kdrazek(a)verisign.com" <kdrazek(a)verisign.com>, Mary Wong <mary.wong(a)icann.org>, Steve Chan <steve.chan(a)icann.org>, Berry Cobb <mail(a)berrycobb.com>, Berry Cobb <Berry.Cobb(a)icann.org>, Marika Konings <marika.konings(a)icann.org>, Dennis Chang <dennis.chang(a)icann.org> Cc: "gnso-secs(a)icann.org" <gnso-secs(a)icann.org> Subject: [Ext] Re: Urgent Doodle poll: GNSO Chairs, IGO IRT Liaison and Staff support discussion call Nathalie – As we’ve been discussing in the other thread, let’s consider moving this to a written report (given the lack of availability of folks next week). Any objections? Thanks— J. From: Nathalie Peregrine <nathalie.peregrine(a)icann.org> Date: Friday, October 13, 2017 at 10:36 To: "James M. Bladel" <jbladel(a)godaddy.com>, "Austin, Donna" <Donna.Austin(a)team.neustar>, Heather Forrest <haforrestesq(a)gmail.com>, Keith Drazek <kdrazek(a)verisign.com>, Mary Wong <mary.wong(a)icann.org>, Steve Chan <steve.chan(a)icann.org>, Berry Cobb Mail <mail(a)berrycobb.com>, Berry Cobb <Berry.Cobb(a)icann.org>, Marika Konings <marika.konings(a)icann.org>, Dennis Chang <dennis.chang(a)icann.org> Cc: "'gnso-secs(a)icann.org'" <gnso-secs(a)icann.org> Subject: Urgent Doodle poll: GNSO Chairs, IGO IRT Liaison and Staff support discussion call Dear all, I apologise, the Doodle responses to this poll for the call on Monday got wiped – I am at a loss how – and I didn’t have time to view which was the preferred slot. Would you please be so kind as to re-enter your choices in this new poll and I will send the invites out shortly. https://doodle.com/poll/gwi5ads2ssnzu4tx[doodle.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__doodle.com_poll_gwi5ad…> Thank you, Nathalie From: <gnso-secs-bounces(a)icann.org> on behalf of Nathalie Peregrine <nathalie.peregrine(a)icann.org> Date: Tuesday, October 10, 2017 at 5:44 PM To: James Bladel <jbladel(a)godaddy.com>, "Austin, Donna" <Donna.Austin(a)team.neustar>, Heather Forrest <haforrestesq(a)gmail.com>, "kdrazek(a)verisign.com" <kdrazek(a)verisign.com>, Mary Wong <mary.wong(a)icann.org>, Steve Chan <steve.chan(a)icann.org>, Berry Cobb <mail(a)berrycobb.com>, Berry Cobb <Berry.Cobb(a)icann.org>, Marika Konings <marika.konings(a)icann.org>, Dennis Chang <dennis.chang(a)icann.org> Cc: "gnso-secs(a)icann.org" <gnso-secs(a)icann.org> Subject: [gnso-secs] Doodle poll: GNSO Chairs, IGO IRT Liaison and Staff support discussion call Dear all, In order to schedule a discussion next week, similar to the one held prior to ICANN59, between the GNSO Council chairs, the IGO IRT – GNSO Council liaison and staff support, please be so kind as to complete the below Doodle poll: https://icannorg.doodle.com/poll/hfmhci7r6w54qxa4[icannorg.doodle.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__icannorg.doodle.com_po…> Thank you! Kind regards, Nathalie Nathalie Peregrine Manager, Operations Support (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Email: nathalie.peregrine(a)icann.org <nathalie.peregrine(a)icann.org%20> Skype: nathalie.peregrine.icann Find out more about the GNSO by taking our interactive courses<applewebdata://EB3A6F47-9760-400D-A39B-A7EFFC56B467/learn.icann.org/courses…> and visiting the GNSO Newcomer pages<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gn…>

2 1

IGO&INGO Policy Implementation: Reserved name list - a new approach: update existing list
by Dennis Chang Oct. 23, 2017

Oct. 23, 2017

Dear IGO&INGO IRT, As we were preparing to publish the policy, we needed to produce a machine-readable reserved list as mentioned in the implementation notes. In doing so, we’ve found a better approach which will make it easier for those involved in the implementation and likely reduce confusion of having two reserved lists with duplicated names. Instead of producing a separate reserved name list for the policy as we had originally planned, we’ve decided to update the existing reserved name list that is already published. In another word, update the current machine-readable list that is already being used by the registry operators. In summary, the identifiers that are in-scope of the policy will be gathered with references to the policy while the identifiers that are out-of-scope for this policy will remain with the reference to the registry agreement. Attached is a table prepared for you to see changes from the current name list to the updated list with the policy announcement. I was going to host another IRT meeting to explain this but thought perhaps it would be clear enough for you via this email. Please let me know if you have questions on this or would like an IRT meeting to discuss with the team. Otherwise, I’d appreciate your reply in support of this new approach. — Kind Regards, Dennis S. Chang GDD Services & Engagement Program Director +1 213 293 7889 Skype: dennisSchang www.icann.org "One World, One Internet"

4 6

FW: IGO Policy Implementation status brief to GNSO: Re: [Ext] Re: Urgent Doodle poll: GNSO Chairs, IGO IRT Liaison and Staff support discussion call
by Dennis Chang Oct. 18, 2017

Oct. 18, 2017

Dear IGO/INGO IRT, Please see my email to the GNSO Council below. Normally, it would be a 30-minute call but this time around they asked for a written report due to schedule difficulties. Thanks Dennis Chang From: Dennis Chang <dennis.chang(a)icann.org> Date: Wednesday, October 18, 2017 at 9:40 AM To: "James M. Bladel" <jbladel(a)godaddy.com>, Nathalie Peregrine <nathalie.peregrine(a)icann.org>, "Austin, Donna" <Donna.Austin(a)team.neustar>, Heather Forrest <haforrestesq(a)gmail.com>, "kdrazek(a)verisign.com" <kdrazek(a)verisign.com>, Mary Wong <mary.wong(a)icann.org>, Steve Chan <steve.chan(a)icann.org>, Berry Cobb <mail(a)berrycobb.com>, Berry Cobb <Berry.Cobb(a)icann.org>, Marika Konings <marika.konings(a)icann.org> Cc: "gnso-secs(a)icann.org" <gnso-secs(a)icann.org> Subject: IGO Policy Implementation status brief to GNSO: Re: [Ext] Re: Urgent Doodle poll: GNSO Chairs, IGO IRT Liaison and Staff support discussion call Dear GNSO Council, As suggested by James, I am providing you a written report of the status on the IGO/INGO Policy Implementation in lieu of a meeting prior to the ICANN60. Since our last meeting, the following was reported on 10 October 2017 version of the GNSO Project List: “The proposed implementation of GNSO Consensus Policy Recommendation for the Protection of IGO&INGO Identifier in All gTLDs<https://www.icann.org/public-comments/igo-ingo-protection-2017-05-17-en> was posted for public comment and the summary and analysis report completed. The implementation team is in the process of finalizing the policy document based on the recommendations received in the public comment in collaborations with the IRT.” Specifically, we had been working to resolve conflicting requests from registries. While some registries were requesting short implementation time frame, others asked for much longer duration. Upon research, we had learned that those requesting quick implementation were interested in taking advantage of the exceptions procedure to register reserved names which this policy allows and those who were asking for longer time were concerned about the INGO claims system development. The implementation team devised a plan where we could satisfy both needs by offering two effective dates: one for reserved names and another for claims. This plan was shared with the RySG via a letter<https://community.icann.org/display/IIPIRT/Documentation?preview=/56136698/…>. While RySG has not responded formally, we received a reply from the vice-chair to let us know that there had not been objections voiced to our proposed plan. He also asked the registries to reach out to us individually with their questions and suggestions. As a result, we had additional opportunity to discuss the implementation and further develop it to make it easier to implement with less confusion. Our updated plan calls for an update to the existing reserved name list which avoids duplication of names and potential confusion on which names qualify for the exceptional procedure for registration. This approach has been well received by the IRT. You can view a summary of how these lists will be affected by this policy here<https://community.icann.org/display/IIPIRT/Documentation?preview=/56136698/…>. Currently, the final draft is under review by IRT and we plan to move toward publication with the support of the IRT. While, no IRT session has been scheduled at ICANN60, we may be gathering to take advantage being able to meet in-person. The challenge with this policy implementation is that of scope confusion and we appreciate the close working relationship with the IRT. It’s our aim to keep us together on the same page throughout this implementation. The implementation process also includes collaboration with the IRT such as the creation and release of the INGO Claims system specification. At the moment, I have no request to the GNSO Council. While small in number, the IRT has been responsive and engaged. One good news is that Mr. Dennis Tanaka from Verisign has just joined us as an IRT member. He has been tracking our work having taken over from Chuck Gomes. Please express your appreciation for Mr. Tanaka’s contribution when you get a chance. You’ll note that I will refer to him as Mr. Tanaka to avoid confusion with me. Thank you for the opportunity to brief the council and please don’t hesitate to contact me or the IRT for anything further. I look forward to seeing you all at Abu Dhabi. Safe travel. — Kind Regards, Dennis S. Chang GDD Services & Engagement Program Director +1 213 293 7889 Skype: dennisSchang www.icann.org "One World, One Internet" From: Dennis Chang <dennis.chang(a)icann.org> Date: Monday, October 16, 2017 at 9:34 AM To: "James M. Bladel" <jbladel(a)godaddy.com>, Nathalie Peregrine <nathalie.peregrine(a)icann.org>, "Austin, Donna" <Donna.Austin(a)team.neustar>, Heather Forrest <haforrestesq(a)gmail.com>, "kdrazek(a)verisign.com" <kdrazek(a)verisign.com>, Mary Wong <mary.wong(a)icann.org>, Steve Chan <steve.chan(a)icann.org>, Berry Cobb <mail(a)berrycobb.com>, Berry Cobb <Berry.Cobb(a)icann.org>, Marika Konings <marika.konings(a)icann.org> Cc: "gnso-secs(a)icann.org" <gnso-secs(a)icann.org> Subject: Re: [Ext] Re: Urgent Doodle poll: GNSO Chairs, IGO IRT Liaison and Staff support discussion call Unless I hear otherwise, I’ll provide a written report in the next day or so. Thanks Dennis Chang From: "James M. Bladel" <jbladel(a)godaddy.com> Date: Friday, October 13, 2017 at 9:46 AM To: Nathalie Peregrine <nathalie.peregrine(a)icann.org>, "Austin, Donna" <Donna.Austin(a)team.neustar>, Heather Forrest <haforrestesq(a)gmail.com>, "kdrazek(a)verisign.com" <kdrazek(a)verisign.com>, Mary Wong <mary.wong(a)icann.org>, Steve Chan <steve.chan(a)icann.org>, Berry Cobb <mail(a)berrycobb.com>, Berry Cobb <Berry.Cobb(a)icann.org>, Marika Konings <marika.konings(a)icann.org>, Dennis Chang <dennis.chang(a)icann.org> Cc: "gnso-secs(a)icann.org" <gnso-secs(a)icann.org> Subject: [Ext] Re: Urgent Doodle poll: GNSO Chairs, IGO IRT Liaison and Staff support discussion call Nathalie – As we’ve been discussing in the other thread, let’s consider moving this to a written report (given the lack of availability of folks next week). Any objections? Thanks— J. From: Nathalie Peregrine <nathalie.peregrine(a)icann.org> Date: Friday, October 13, 2017 at 10:36 To: "James M. Bladel" <jbladel(a)godaddy.com>, "Austin, Donna" <Donna.Austin(a)team.neustar>, Heather Forrest <haforrestesq(a)gmail.com>, Keith Drazek <kdrazek(a)verisign.com>, Mary Wong <mary.wong(a)icann.org>, Steve Chan <steve.chan(a)icann.org>, Berry Cobb Mail <mail(a)berrycobb.com>, Berry Cobb <Berry.Cobb(a)icann.org>, Marika Konings <marika.konings(a)icann.org>, Dennis Chang <dennis.chang(a)icann.org> Cc: "'gnso-secs(a)icann.org'" <gnso-secs(a)icann.org> Subject: Urgent Doodle poll: GNSO Chairs, IGO IRT Liaison and Staff support discussion call Dear all, I apologise, the Doodle responses to this poll for the call on Monday got wiped – I am at a loss how – and I didn’t have time to view which was the preferred slot. Would you please be so kind as to re-enter your choices in this new poll and I will send the invites out shortly. https://doodle.com/poll/gwi5ads2ssnzu4tx[doodle.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__doodle.com_poll_gwi5ad…> Thank you, Nathalie From: <gnso-secs-bounces(a)icann.org> on behalf of Nathalie Peregrine <nathalie.peregrine(a)icann.org> Date: Tuesday, October 10, 2017 at 5:44 PM To: James Bladel <jbladel(a)godaddy.com>, "Austin, Donna" <Donna.Austin(a)team.neustar>, Heather Forrest <haforrestesq(a)gmail.com>, "kdrazek(a)verisign.com" <kdrazek(a)verisign.com>, Mary Wong <mary.wong(a)icann.org>, Steve Chan <steve.chan(a)icann.org>, Berry Cobb <mail(a)berrycobb.com>, Berry Cobb <Berry.Cobb(a)icann.org>, Marika Konings <marika.konings(a)icann.org>, Dennis Chang <dennis.chang(a)icann.org> Cc: "gnso-secs(a)icann.org" <gnso-secs(a)icann.org> Subject: [gnso-secs] Doodle poll: GNSO Chairs, IGO IRT Liaison and Staff support discussion call Dear all, In order to schedule a discussion next week, similar to the one held prior to ICANN59, between the GNSO Council chairs, the IGO IRT – GNSO Council liaison and staff support, please be so kind as to complete the below Doodle poll: https://icannorg.doodle.com/poll/hfmhci7r6w54qxa4[icannorg.doodle.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__icannorg.doodle.com_po…> Thank you! Kind regards, Nathalie Nathalie Peregrine Manager, Operations Support (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Email: nathalie.peregrine(a)icann.org <nathalie.peregrine(a)icann.org%20> Skype: nathalie.peregrine.icann Find out more about the GNSO by taking our interactive courses<applewebdata://EB3A6F47-9760-400D-A39B-A7EFFC56B467/learn.icann.org/courses…> and visiting the GNSO Newcomer pages<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gn…>

1 0

Re: [Gnso-igo-ingo-ip-irt] [Ext] RE: New iRT member: Dennis Tanaka - Verisign
by Dennis Chang Oct. 11, 2017

Oct. 11, 2017

Thanks Lori volunteering again. You were going to provide language we could add to FAQ in lay persons term for the rather legalistic language we used for the implementation note we added regarding RPM Provided below for your convenience. 4. Rights Protection Mechanism Requirements Applicability 4.1 Section 2.4.3 of the Rights Protection Mechanism Requirements provides that, “[i]f Registry Operator reserves a domain name from registration in accordance with Section 2.6 of the Agreement and Specification 5 of the Agreement and thereafter (i) releases for Allocation or registration such reserved domain name at any time prior to the start date of the Claims Period, such domain name MUST be treated like any other domain name for any applicable Sunrise Period, Limited Registration Period, Launch Program or Claims Period, or (ii) releases for Allocation or registration such reserved domain name at any time following the start date of the Claims Period, such domain name MUST be subject to the Claims Services (as defined in Section 3) for a period of ninety (90) calendar days following the date Registry Operator releases such domain name for registration as long as the Trademark Clearinghouse (or any ICANN-designated successor thereto) remains in operation.” (emphasis added) As noted above, Section 2.4.3 provides specific requirements for names reserved in accordance with Section 2.6 of the Registry Agreement and Specification 5 of the Registry Agreement. The GNSO Policy for the Protection of IGO and INGO Identifiers in All gTLDs (the “Policy”), in section 3.1, requires registry operators to reserve “the second-level domain names corresponding to all identifiers recorded on the Red Cross, IOC and IGOs Identifier List<http://mailer.samanage.com/wf/click?upn=3sVClaOwo5uihwlrrc4Of7t0WKv3B6GenAB…>”. Because these names are reserved in accordance with the Policy, and not reserved in accordance with Section 2.6 of the Registry Agreement and Specification 5 of the Registry Agreement, Section 2.4.3 of the RPM Requirements Document does not apply to the second-level domain names corresponding to all identifiers recorded on the Red Cross, IOC and IGOs Identifier List<http://mailer.samanage.com/wf/click?upn=3sVClaOwo5uihwlrrc4Of7t0WKv3B6GenAB…>. btw, Mr. Tanaka mentioned to me that the implementation note is helpful and appreciated it being added. Thanks Dennis Chang From: Lori Schulman <lschulman(a)inta.org> Date: Wednesday, October 11, 2017 at 9:59 AM 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: "dtantanaka(a)verisign.com" <dtantanaka(a)verisign.com> Subject: [Ext] RE: New iRT member: Dennis Tanaka - Verisign Welcome Mr. Tanaka. Happy to have you in our merry little band. Dennis, I think I owe you some language. I apologize for the delay. Can you remind me of the deliverable? Lori S. Schulman Senior Director, Internet Policy International Trademark Association (INTA) +1-202-704-0408, Skype: lsschulman [017-esig] From: gnso-igo-ingo-ip-irt-bounces(a)icann.org [mailto:gnso-igo-ingo-ip-irt-bounces@icann.org] On Behalf Of Dennis Chang Sent: Wednesday, October 11, 2017 12:21 PM To: gnso-igo-ingo-ip-irt(a)icann.org Cc: dtantanaka(a)verisign.com Subject: [Gnso-igo-ingo-ip-irt] New iRT member: Dennis Tanaka - Verisign Dear IGO&INGO IRT, Mr. Dennis Tanaka from Verisign has joined our IRT. Mr. Tanaka is from Verisign and has been following the IGO/INGO policy item having taken it over from Chuck Gomes. I’ll refer to him as Mr. Tanaka to avoid confusion now we have two Dennis’ on the Implementation Team. Michelle, Please add him to the email group and the IRT wiki membership list Dennis Tanaka <dtantanaka(a)verisign.com<mailto:dtantanaka@verisign.com>> — Kind Regards, Dennis S. Chang GDD Services & Engagement Program Director +1 213 293 7889 Skype: dennisSchang www.icann.org[icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.icann.org&d=DwMFaQ&…> "One World, One Internet"

1 0

New iRT member: Dennis Tanaka - Verisign
by Dennis Chang Oct. 11, 2017

Oct. 11, 2017

Dear IGO&INGO IRT, Mr. Dennis Tanaka from Verisign has joined our IRT. Mr. Tanaka is from Verisign and has been following the IGO/INGO policy item having taken it over from Chuck Gomes. I’ll refer to him as Mr. Tanaka to avoid confusion now we have two Dennis’ on the Implementation Team. Michelle, Please add him to the email group and the IRT wiki membership list Dennis Tanaka <dtantanaka(a)verisign.com<mailto:dtantanaka@verisign.com>> — 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