- registrars - lists.icann.org

registrars@icann.org mailing list retirement
by Andee Hill July 30, 2021

July 30, 2021

Dear Subscriber, Please be advised that the mailing list address registrars(a)icann.org<mailto:registrars@icann.org> will be retired at 23:59 UTC on 30 July 2021. If you wish to continue receiving notifications regarding RRA Amendment requests, please subscribe to the new address rra(a)icann.org<mailto:rra@icann.org> at https://mm.icann.org/mailman/listinfo/rra. Thank you, Andee Hill Director, GDD Accounts Internet Corporation for Assigned Names and Numbers (ICANN)

1 0

Re: [registrars] [Ext] Re: RE: RRA Amendment Notification for xn--vuq861b [ ref:_00D616tJk._5004MgGPMH:ref ]
by Robert Gomez July 21, 2021

July 21, 2021

Dear Lynn Xing, Thank you for contacting us and for your continued patience. Currently, ICANN org is reviewing internally and anticipate additional feedback within the next two weeks. We will notify you immediately if more information becomes available sooner. Please let us know if you have further questions. Kind Regards, Robert Gomez GDS Service Delivery From: "xingna(a)teleinfo.cn" <xingna(a)teleinfo.cn> Date: Monday, July 19, 2021 at 7:47 PM To: globalsupport <globalsupport(a)icann.org> Cc: Andrew Dickson <andrew.dickson(a)icann.org>, Jeanne Gregg <jeanne.gregg(a)icann.org>, "secretariat(a)icannregistrars.org" <secretariat(a)icannregistrars.org>, "registrars(a)icann.org" <registrars(a)icann.org>, "ceo(a)teleinfo.cn" <ceo(a)teleinfo.cn>, Andee Hill <andee.hill(a)icann.org>, "aheineman(a)godaddy.com" <aheineman(a)godaddy.com>, Camia Frank <camia.frank(a)icann.org>, Robert Gomez <robert.gomez(a)icann.org> Subject: Re: Re: [Ext] Re: RE: RRA Amendment Notification for xn--vuq861b [ ref:_00D616tJk._5004MgGPMH:ref ] Dear Robert, Just want to follow up with the progress with the RRA Amendment, any feedback? Thanks! Best Regards, ________________________________ 邢娜 Lynn Xing 手机/Mobile：+86 189 1028 3591 邮箱/Email：xingna(a)teleinfo.cn [teleinfo.cn]<https://urldefense.com/v3/__http:/liuwei@teleinfo.cn/__;!!PtGJab4!t0LA6I2l3…> www.teleinfo.cn [teleinfo.cn]<https://urldefense.com/v3/__http:/www.teleinfo.cn/__;!!PtGJab4!t0LA6I2l3fzo…> 数字网络运营商北京泰尔英福网络科技有限责任公司北京市海淀区中关村科技园翠湖云中心21号楼，100095 From: ICANN - Global Support<mailto:globalsupport@icann.org> Date: 2021-06-23 04:04 To: xingna(a)teleinfo.cn<mailto:xingna@teleinfo.cn> CC: andrew.dickson(a)icann.org<mailto:andrew.dickson@icann.org>; jeanne.gregg(a)icann.org<mailto:jeanne.gregg@icann.org>; secretariat(a)icannregistrars.org<mailto:secretariat@icannregistrars.org>; registrars(a)icann.org<mailto:registrars@icann.org>; ceo(a)teleinfo.cn<mailto:ceo@teleinfo.cn>; andee.hill(a)icann.org<mailto:andee.hill@icann.org>; aheineman(a)godaddy.com<mailto:aheineman@godaddy.com>; camia.frank(a)icann.org<mailto:camia.frank@icann.org>; robert.gomez(a)icann.org<mailto:robert.gomez@icann.org> Subject: Re: Re: [Ext] Re: RE: RRA Amendment Notification for xn--vuq861b [ ref:_00D616tJk._5004MgGPMH:ref ] Dear Lynn Xing, Thank you for your follow up message. We appreciate your patience as ICANN org and the RrSG continue to review and discuss the feedback. Once more information is available, we will update you immediately. Please let us know if you have further questions. Kind Regards, Robert Gomez GDS Service Delivery --------------- Original Message --------------- From: xingna(a)teleinfo.cn [xingna(a)teleinfo.cn] Sent: 6/21/2021 12:09 AM To: globalsupport(a)icann.org; camia.frank(a)icann.org; aheineman(a)godaddy.com Cc: andrew.dickson(a)icann.org; ceo(a)teleinfo.cn; andee.hill(a)icann.org; jeanne.gregg(a)icann.org; secretariat(a)icannregistrars.org; registrars(a)icann.org Subject: Re: Re: [Ext] Re: RE: RRA Amendment Notification for xn--vuq861b [ ref:_00D616tJk._5004MgGPMH:ref ] Dear ICANN team? Just to follow-up with our RRA Amendment case. Any feedback? Thanks! Best Regards, ________________________________ ?? Lynn Xing ??/Mobile?+86 189 1028 3591 ??/Email?xingna(a)teleinfo.cn [teleinfo.cn]<https://urldefense.com/v3/__http:/liuwei@teleinfo.cn/__;!!PtGJab4!t0LA6I2l3…> www.teleinfo.cn [teleinfo.cn]<https://urldefense.com/v3/__http:/www.teleinfo.cn/__;!!PtGJab4!t0LA6I2l3fzo…> ??????? ???????????????? ?????????????????21???100095 From: Camia Frank<mailto:camia.frank@icann.org> Date: 2021-06-03 08:45 To: xingna(a)teleinfo.cn<mailto:xingna@teleinfo.cn>; aheineman(a)godaddy.com<mailto:aheineman@godaddy.com>; globalsupport<mailto:globalsupport@icann.org> CC: Andrew Dickson<mailto:andrew.dickson@icann.org>; Jeanne Gregg<mailto:jeanne.gregg@icann.org>; secretariat(a)icannregistrars.org<mailto:secretariat@icannregistrars.org>; registrars(a)icann.org<mailto:registrars@icann.org>; ceo(a)teleinfo.cn<mailto:ceo@teleinfo.cn>; Andee Hill<mailto:andee.hill@icann.org> Subject: Re: [Ext] Re: RE: RRA Amendment Notification for xn--vuq861b [ ref:_00D616tJk._5004MgGPMH:ref ] Dear Lynn Xing, Thank you for your patience. ICANN org and the RrSG are still in discussion about the feedback and will revert back with more information as soon as possible. Please let us know if you have further questions. Warm Regards, Camia Frank GDS Service Delivery From: "xingna(a)teleinfo.cn" <xingna(a)teleinfo.cn> Date: Tuesday, June 1, 2021 at 7:40 PM To: "aheineman(a)godaddy.com" <aheineman(a)godaddy.com>, globalsupport <globalsupport(a)icann.org> Cc: Andrew Dickson <andrew.dickson(a)icann.org>, Jeanne Gregg <jeanne.gregg(a)icann.org>, "secretariat(a)icannregistrars.org" <secretariat(a)icannregistrars.org>, "registrars(a)icann.org" <registrars(a)icann.org>, "ceo(a)teleinfo.cn" <ceo(a)teleinfo.cn>, Andee Hill <andee.hill(a)icann.org>, Camia Frank <camia.frank(a)icann.org> Subject: [Ext] Re: RE: RRA Amendment Notification for xn--vuq861b [ ref:_00D616tJk._5004MgGPMH:ref ] Dear Ashley, Robert and all, Thanks a quick question. Any chance to let us know the expected date for the feedback? Thannks! Best Regards, ________________________________ ?? Lynn Xing ??/Mobile?+86 189 1028 3591 ??/Email?xingna(a)teleinfo.cn [teleinfo.cn]<https://urldefense.com/v3/__http:/liuwei@teleinfo.cn/__;!!PtGJab4!pZS4Iv9HW…> www.teleinfo.cn [teleinfo.cn]<https://urldefense.com/v3/__http:/www.teleinfo.cn/__;!!PtGJab4!pZS4Iv9HWFf9…> ??????? ???????????????? ?????????????????21???100095 From: aheineman(a)godaddy.com<mailto:aheineman@godaddy.com> Date: 2021-05-25 23:31 To: ICANN - Global Support<mailto:globalsupport@icann.org> CC: andrew.dickson(a)icann.org<mailto:andrew.dickson@icann.org>; jeanne.gregg(a)icann.org<mailto:jeanne.gregg@icann.org>; secretariat(a)icannregistrars.org<mailto:secretariat@icannregistrars.org>; registrars(a)icann.org<mailto:registrars@icann.org>; ceo(a)teleinfo.cn<mailto:ceo@teleinfo.cn>; andee.hill(a)icann.org<mailto:andee.hill@icann.org>; xingna(a)teleinfo.cn<mailto:xingna@teleinfo.cn>; camia.frank(a)icann.org<mailto:camia.frank@icann.org> Subject: RE: Re: RRA Amendment Notification for xn--vuq861b [ ref:_00D616tJk._5004MgGPMH:ref ] Dear Robert, all. My sincerest apologies, but didn’t receive the email from 5/15 (spam folder!). Let me and the registrars review and get back soonest. From: ICANN - Global Support <globalsupport(a)icann.org> Sent: Tuesday, May 25, 2021 10:51 AM To: Ashley Heineman <aheineman(a)godaddy.com> Cc: andrew.dickson(a)icann.org; jeanne.gregg(a)icann.org; secretariat(a)icannregistrars.org; registrars(a)icann.org; ceo(a)teleinfo.cn; andee.hill(a)icann.org; xingna(a)teleinfo.cn; camia.frank(a)icann.org Subject: Re: Re: RRA Amendment Notification for xn--vuq861b [ ref:_00D616tJk._5004MgGPMH:ref ] Caution: This email is from an external sender. Please do not click links or open attachments unless you recognize the sender and know the content is safe. Forward suspicious emails to isitbad@. Dear Ashley, On 15 May 2021, the registry operator provided a response to the RrSG's (30 April 2021) feedback. This is a follow up to confirm if your Stakeholder Group has concerns, does not have concerns, or if additional review time is required. Kind regards, Robert Gomez GDS Service Delivery --------------- Original Message --------------- From: xingna(a)teleinfo.cn<mailto:xingna@teleinfo.cn> [xingna(a)teleinfo.cn] Sent: 5/15/2021 2:20 AM To: globalsupport(a)icann.org<mailto:globalsupport@icann.org>; secretariat(a)icannregistrars.org<mailto:secretariat@icannregistrars.org> Cc: andrew.dickson(a)icann.org<mailto:andrew.dickson@icann.org>; jeanne.gregg(a)icann.org<mailto:jeanne.gregg@icann.org>; registrars(a)icann.org<mailto:registrars@icann.org>; ceo(a)teleinfo.cn<mailto:ceo@teleinfo.cn>; andee.hill(a)icann.org<mailto:andee.hill@icann.org>; aheineman(a)godaddy.com<mailto:aheineman@godaddy.com>; xingna(a)teleinfo.cn<mailto:xingna@teleinfo.cn>; camia.frank(a)icann.org<mailto:camia.frank@icann.org> Subject: Re: Re: RRA Amendment Notification for xn--vuq861b [ ref:_00D616tJk._5004MgGPMH:ref ] Dear ICANN team, Thank you for your feedback and advice! In order to improve the financial stability, we (as the Registry Operator) have proposed the new prepayment scheme in the Amendment RRA, the main reason is that we would like to promote .???xn--vuQ861B?domain names via all registrars, specially to the registrars who had rich experience in IDN market and sales. They have strong customer base for IDN, we are trying to push our domain sales to a new level. Our registration number were used to be over 50,000. We expect the number of .???xn--vuQ861B?domain names to create a new record. Thus, we want to raise the bar for the new registrar who really wants to cooperate with us and promote .???xn--vuQ861B?domain names together. This prepayment change will only affect the new registrar, and have minimal impact on the existing registrar. Alternatively, we can reduce the prepayment amount from $153,000 to $76,500. We would like to try this process as the first step, if things go well, we will see if we need to take any further actions. We will follow the ICANN procedure and keep you posted. Please don't hesitate to contact us if you have any further questions. Looking forward to hearing from you! Best Regards, ________________________________ ?? Lynn Xing ??/Mobile?+86 189 1028 3591 ??/Email?xingna(a)teleinfo.cn [teleinfo.cn]<https://urldefense.com/v3/__http:/liuwei@teleinfo.cn/__;!!PtGJab4!pZS4Iv9HW…> www.teleinfo.cn [teleinfo.cn]<https://urldefense.com/v3/__http:/www.teleinfo.cn/__;!!PtGJab4!pZS4Iv9HWFf9…> ??????? ???????????????? ?????????????????21???100095 From: ICANN - Global Support<mailto:globalsupport@icann.org> Date: 2021-05-05 01:42 To: secretariat(a)icannregistrars.org<mailto:secretariat@icannregistrars.org> CC: andrew.dickson(a)icann.org<mailto:andrew.dickson@icann.org>; jeanne.gregg(a)icann.org<mailto:jeanne.gregg@icann.org>; registrars(a)icann.org<mailto:registrars@icann.org>; ceo(a)teleinfo.cn<mailto:ceo@teleinfo.cn>; andee.hill(a)icann.org<mailto:andee.hill@icann.org>; aheineman(a)godaddy.com<mailto:aheineman@godaddy.com>; camia.frank(a)icann.org<mailto:camia.frank@icann.org>; xingna(a)teleinfo.cn<mailto:xingna@teleinfo.cn> Subject: Re: RRA Amendment Notification for xn--vuq861b [ ref:_00D616tJk._5004MgGPMH:ref ] Dear Zoe Bonython, Thank you for the update. The Registry Operator is copied on this thread and can directly respond to the RrSG's feedback provided below for convenience: "The registrars have one material comment on a new requirement in the Amended RRA which essentially states that registrars pre-pay 1 million RMB within 1 month of the signing of the new Agreement. This amounts to approximately US $153,000. Failure to pay this amount will result in “suspension or termination of the authority of Registrar in creating new Standard names.” In general, the Registrars do not comment on the price of domain name registrars so long as the pricing changes are done in accordance with what is required by ICANN and as reflected in the Registry Agreement. In this case, we believe that in a Registry where the price of a registration is less than $ US 20, and no registrars has more than 1000 registrations (most have less than 100 names), a prepayment of $153,000 by each Registrar cannot be said to be reasonably related to the proper functioning of the TLD (as is required in Section 2.9 of the Registry Agreement). We therefore ask that the Registry Operator either remove this new requirement, or in the alternative, explain the purpose of this new requirement and adjust the amount to something more commensurate with what is “reasonably related to the proper functioning of the TLD." Kind regards, Robert Gomez GDS Service Delivery --------------- Original Message --------------- From: Zoe Bonython [secretariat(a)icannregistrars.org] Sent: 4/30/2021 8:17 AM To: globalsupport(a)icann.org<mailto:globalsupport@icann.org>; registrars(a)icann.org<mailto:registrars@icann.org>; aheineman(a)godaddy.com<mailto:aheineman@godaddy.com> Cc: ceo(a)teleinfo.cn<mailto:ceo@teleinfo.cn>; andrew.dickson(a)icann.org<mailto:andrew.dickson@icann.org>; robert.gomez(a)icann.org<mailto:robert.gomez@icann.org>; andee.hill(a)icann.org<mailto:andee.hill@icann.org>; jeanne.gregg(a)icann.org<mailto:jeanne.gregg@icann.org>; camia.frank(a)icann.org<mailto:camia.frank@icann.org> Subject: Re: RRA Amendment Notification for xn--vuq861b [ ref:_00D616tJk._5004MgGPMH:ref ] Hi Robert & All, Apologies for the late reply, Ashley is on leave this week. Please see below for the response from RrSG: The registrars have one material comment on a new requirement in the Amended RRA which essentially states that registrars pre-pay 1 million RMB within 1 month of the signing of the new Agreement. This amounts to approximately US $153,000. Failure to pay this amount will result in “suspension or termination of the authority of Registrar in creating new Standard names.” In general, the Registrars do not comment on the price of domain name registrars so long as the pricing changes are done in accordance with what is required by ICANN and as reflected in the Registry Agreement. In this case, we believe that in a Registry where the price of a registration is less than $ US 20, and no registrars has more than 1000 registrations (most have less than 100 names), a prepayment of $153,000 by each Registrar cannot be said to be reasonably related to the proper functioning of the TLD (as is required in Section 2.9 of the Registry Agreement). We therefore ask that the Registry Operator either remove this new requirement, or in the alternative, explain the purpose of this new requirement and adjust the amount to something more commensurate with what is “reasonably related to the proper functioning of the TLD.” Kind regards, Zoe Bonython RrSG Secretariat From: ICANN - Global Support <globalsupport(a)icann.org<mailto:globalsupport@icann.org>> Date: Tuesday, April 27, 2021 at 4:32 PM To: "secretariat(a)icannregistrars.org<mailto:secretariat@icannregistrars.org>" <secretariat(a)icannregistrars.org<mailto:secretariat@icannregistrars.org>>, "registrars(a)icann.org<mailto:registrars@icann.org>" <registrars(a)icann.org<mailto:registrars@icann.org>>, "aheineman(a)godaddy.com<mailto:aheineman@godaddy.com>" <aheineman(a)godaddy.com<mailto:aheineman@godaddy.com>> Cc: "ceo(a)teleinfo.cn<mailto:ceo@teleinfo.cn>" <ceo(a)teleinfo.cn<mailto:ceo@teleinfo.cn>>, "robert.gomez(a)icann.org<mailto:robert.gomez@icann.org>" <robert.gomez(a)icann.org<mailto:robert.gomez@icann.org>>, "andrew.dickson(a)icann.org<mailto:andrew.dickson@icann.org>" <andrew.dickson(a)icann.org<mailto:andrew.dickson@icann.org>>, "camia.frank(a)icann.org<mailto:camia.frank@icann.org>" <camia.frank(a)icann.org<mailto:camia.frank@icann.org>>, "andee.hill(a)icann.org<mailto:andee.hill@icann.org>" <andee.hill(a)icann.org<mailto:andee.hill@icann.org>>, "jeanne.gregg(a)icann.org<mailto:jeanne.gregg@icann.org>" <jeanne.gregg(a)icann.org<mailto:jeanne.gregg@icann.org>> Subject: RE: RRA Amendment Notification for xn--vuq861b [ ref:_00D616tJk._5004MgGPMH:ref ] Dear Ashley, On 05 April 2021 ICANN org provided the cover letter and red-lined RRA Amendment for xn--vuq861b submitted by Beijing Tele-info Network Technology Co., Ltd. This is a follow up to confirm if your Stakeholder Group has concerns, does not have concerns, or if additional review time is required. If the Stakeholder Group has concerns, ICANN org will continue with the next step of the RRA Amendment Procedure, which is to consult with the RrSG and the Registry Operator to attempt to resolve any such concerns. Kind regards, Robert Gomez GDS Service Delivery --------------- Original Message --------------- From: ICANN - Global Support [globalsupport(a)icann.org] Sent: 4/5/2021 2:31 PM To: secretariat(a)icannregistrars.org<mailto:secretariat@icannregistrars.org>; registrars(a)icann.org<mailto:registrars@icann.org>; aheineman(a)godaddy.com<mailto:aheineman@godaddy.com> Cc: andee.hill(a)icann.org<mailto:andee.hill@icann.org>; andrew.dickson(a)icann.org<mailto:andrew.dickson@icann.org>; jeanne.gregg(a)icann.org<mailto:jeanne.gregg@icann.org>; camia.frank(a)icann.org<mailto:camia.frank@icann.org>; robert.gomez(a)icann.org<mailto:robert.gomez@icann.org>; ceo(a)teleinfo.cn<mailto:ceo@teleinfo.cn> Subject: RRA Amendment Notification for xn--vuq861b [ ref:_00D616tJk._5004MgGPMH:ref ] Hello Ashley, Attached, please find the cover letter and the red-lined RRA Amendment for the following TLD submitted by Beijing Tele-info Network Technology Co., Ltd. to be shared with your Stakeholder Group: xn--vuq861b Please respond by 23:59 UTC on Monday, 26 April 2021 to let us know if your Stakeholder Group has concerns, does not have concerns, or if additional review time is required. If the Stakeholder Group has concerns, ICANN org will continue with the next step of the RRA Amendment Procedure, which is to consult with the RrSG and the Registry Operator to attempt to resolve any such concerns. Thank you, Robert Gomez GDS Service Delivery[Image removed by sender.] ref:_00D616tJk._5004MgGPMH:ref Kind regards, Robert Gomez GDS Service Delivery Internet Corporation for Assigned Names and Numbers (ICANN)[Image removed by sender.] Kind regards, Robert Gomez GDS Service Delivery Internet Corporation for Assigned Names and Numbers (ICANN)HtmlEditor(07-20-10-26-30).html<cid:_Foxmail.1@97365d14-f5ed-5d0c-4843-858d128a25cd> Kind regards, Robert Gomez GDS Service Delivery Internet Corporation for Assigned Names and Numbers (ICANN)HtmlEditor(07-20-10-26-30).html<cid:_Foxmail.1@97365d14-f5ed-5d0c-4843-858d128a25cd> Kind regards, Robert Gomez GDS Service Delivery Internet Corporation for Assigned Names and Numbers (ICANN)[Image removed by sender.]

1 0

Re: [registrars] [Ext] RE: RRA Amendment Notification for .BLOG [ ref:_00D616tJk._5004Mj8dZ0:ref ]
by Camia Frank June 11, 2021

June 11, 2021

Dear Ashley, Thank you for the follow-up message to inform us that you require additional review time. We approve your request for an extension. We look forward to hearing back from you by Wednesday, 16 June 2021. Warm Regards, Camia Frank GDS Service Delivery From: "aheineman(a)godaddy.com" <aheineman(a)godaddy.com> Date: Friday, June 11, 2021 at 2:34 PM To: Camia Frank <camia.frank(a)icann.org>, ICANN Global Support Center <globalsupport(a)icann.org>, "secretariat(a)icannregistrars.org" <secretariat(a)icannregistrars.org>, "registrars(a)icann.org" <registrars(a)icann.org> Cc: Robert Gomez <robert.gomez(a)icann.org>, Jeanne Gregg <jeanne.gregg(a)icann.org>, Andrew Dickson <andrew.dickson(a)icann.org>, Andee Hill <andee.hill(a)icann.org>, "lillian.fosteris(a)fairwindspartners.com" <lillian.fosteris(a)fairwindspartners.com>, "rra-review(a)rrsg.org" <rra-review(a)rrsg.org> Subject: RE: [Ext] RE: RRA Amendment Notification for .BLOG [ ref:_00D616tJk._5004Mj8dZ0:ref ] Dear Camia, all, My sincerest apologies, but the RrSG will need another extension. May we please have until Wednesday of next week? From: Camia Frank <camia.frank(a)icann.org> Sent: Friday, June 4, 2021 5:35 PM To: Ashley Heineman <aheineman(a)godaddy.com>; ICANN Global Support Center <globalsupport(a)icann.org>; secretariat(a)icannregistrars.org; registrars(a)icann.org Cc: Robert Gomez <robert.gomez(a)icann.org>; Jeanne Gregg <jeanne.gregg(a)icann.org>; Andrew Dickson <andrew.dickson(a)icann.org>; Andee Hill <andee.hill(a)icann.org>; lillian.fosteris(a)fairwindspartners.com; rra-review(a)rrsg.org Subject: Re: [Ext] RE: RRA Amendment Notification for .BLOG [ ref:_00D616tJk._5004Mj8dZ0:ref ] Caution: This email is from an external sender. Please do not click links or open attachments unless you recognize the sender and know the content is safe. Forward suspicious emails to isitbad@. Dear Ashley, Thank you for the follow-up message to inform us that you require additional review time. We approve your request for an extension. We look forward to hearing back from you by Friday, 11 June 2021. Warm Regards, Camia Frank GDS Service Delivery From: "aheineman(a)godaddy.com<mailto:aheineman@godaddy.com>" <aheineman(a)godaddy.com<mailto:aheineman@godaddy.com>> Date: Friday, June 4, 2021 at 1:59 PM To: ICANN Global Support Center <globalsupport(a)icann.org<mailto:globalsupport@icann.org>>, "secretariat(a)icannregistrars.org<mailto:secretariat@icannregistrars.org>" <secretariat(a)icannregistrars.org<mailto:secretariat@icannregistrars.org>>, "registrars(a)icann.org<mailto:registrars@icann.org>" <registrars(a)icann.org<mailto:registrars@icann.org>> Cc: Camia Frank <camia.frank(a)icann.org<mailto:camia.frank@icann.org>>, Robert Gomez <robert.gomez(a)icann.org<mailto:robert.gomez@icann.org>>, Jeanne Gregg <jeanne.gregg(a)icann.org<mailto:jeanne.gregg@icann.org>>, Andrew Dickson <andrew.dickson(a)icann.org<mailto:andrew.dickson@icann.org>>, Andee Hill <andee.hill(a)icann.org<mailto:andee.hill@icann.org>>, "lillian.fosteris(a)fairwindspartners.com<mailto:lillian.fosteris@fairwindspartners.com>" <lillian.fosteris(a)fairwindspartners.com<mailto:lillian.fosteris@fairwindspartners.com>>, "rra-review(a)rrsg.org<mailto:rra-review@rrsg.org>" <rra-review(a)rrsg.org<mailto:rra-review@rrsg.org>> Subject: [Ext] RE: RRA Amendment Notification for .BLOG [ ref:_00D616tJk._5004Mj8dZ0:ref ] Hello all. The RrSG is still reviewing the RRA Amendment notification for .BLOG. May we have a week extension? Thanks. Ashley Heineman Chair, RrSG From: ICANN Global Support Center <globalsupport(a)icann.org<mailto:globalsupport@icann.org>> Sent: Friday, May 14, 2021 5:38 PM To: secretariat(a)icannregistrars.org<mailto:secretariat@icannregistrars.org>; registrars(a)icann.org<mailto:registrars@icann.org>; Ashley Heineman <aheineman(a)godaddy.com<mailto:aheineman@godaddy.com>> Cc: camia.frank(a)icann.org<mailto:camia.frank@icann.org>; robert.gomez(a)icann.org<mailto:robert.gomez@icann.org>; jeanne.gregg(a)icann.org<mailto:jeanne.gregg@icann.org>; andrew.dickson(a)icann.org<mailto:andrew.dickson@icann.org>; andee.hill(a)icann.org<mailto:andee.hill@icann.org>; lillian.fosteris(a)fairwindspartners.com<mailto:lillian.fosteris@fairwindspartners.com> Subject: RRA Amendment Notification for .BLOG [ ref:_00D616tJk._5004Mj8dZ0:ref ] Caution: This email is from an external sender. Please do not click links or open attachments unless you recognize the sender and know the content is safe. Forward suspicious emails to isitbad@. Hello Ashley, Attached, please find the cover letter and the red-lined RRA Amendment for the following TLD submitted by Knock Knock WHOIS There, LLC to be shared with your Stakeholder Group: .BLOG Please respond by 23:59 UTC on Friday, 04 June 2021 to let us know if your Stakeholder Group has concerns, does not have concerns, or if additional review time is required. If the Stakeholder Group has concerns, ICANN org will continue with the next step of the RRA Amendment Procedure, which is to consult with the RrSG and the Registry Operator to attempt to resolve any such concerns. Warm Regards, Camia Frank GDS Service Delivery [Image removed by sender.] ref:_00D616tJk._5004Mj8dZ0:ref

1 0

Re: [registrars] [Ext] RE: RRA Amendment Notification for .BLOG [ ref:_00D616tJk._5004Mj8dZ0:ref ]
by Camia Frank June 4, 2021

June 4, 2021

Dear Ashley, Thank you for the follow-up message to inform us that you require additional review time. We approve your request for an extension. We look forward to hearing back from you by Friday, 11 June 2021. Warm Regards, Camia Frank GDS Service Delivery From: "aheineman(a)godaddy.com" <aheineman(a)godaddy.com> Date: Friday, June 4, 2021 at 1:59 PM To: ICANN Global Support Center <globalsupport(a)icann.org>, "secretariat(a)icannregistrars.org" <secretariat(a)icannregistrars.org>, "registrars(a)icann.org" <registrars(a)icann.org> Cc: Camia Frank <camia.frank(a)icann.org>, Robert Gomez <robert.gomez(a)icann.org>, Jeanne Gregg <jeanne.gregg(a)icann.org>, Andrew Dickson <andrew.dickson(a)icann.org>, Andee Hill <andee.hill(a)icann.org>, "lillian.fosteris(a)fairwindspartners.com" <lillian.fosteris(a)fairwindspartners.com>, "rra-review(a)rrsg.org" <rra-review(a)rrsg.org> Subject: [Ext] RE: RRA Amendment Notification for .BLOG [ ref:_00D616tJk._5004Mj8dZ0:ref ] Hello all. The RrSG is still reviewing the RRA Amendment notification for .BLOG. May we have a week extension? Thanks. Ashley Heineman Chair, RrSG From: ICANN Global Support Center <globalsupport(a)icann.org> Sent: Friday, May 14, 2021 5:38 PM To: secretariat(a)icannregistrars.org; registrars(a)icann.org; Ashley Heineman <aheineman(a)godaddy.com> Cc: camia.frank(a)icann.org; robert.gomez(a)icann.org; jeanne.gregg(a)icann.org; andrew.dickson(a)icann.org; andee.hill(a)icann.org; lillian.fosteris(a)fairwindspartners.com Subject: RRA Amendment Notification for .BLOG [ ref:_00D616tJk._5004Mj8dZ0:ref ] Caution: This email is from an external sender. Please do not click links or open attachments unless you recognize the sender and know the content is safe. Forward suspicious emails to isitbad@. Hello Ashley, Attached, please find the cover letter and the red-lined RRA Amendment for the following TLD submitted by Knock Knock WHOIS There, LLC to be shared with your Stakeholder Group: .BLOG Please respond by 23:59 UTC on Friday, 04 June 2021 to let us know if your Stakeholder Group has concerns, does not have concerns, or if additional review time is required. If the Stakeholder Group has concerns, ICANN org will continue with the next step of the RRA Amendment Procedure, which is to consult with the RrSG and the Registry Operator to attempt to resolve any such concerns. Warm Regards, Camia Frank GDS Service Delivery [Image removed by sender.] ref:_00D616tJk._5004Mj8dZ0:ref

1 0

Re: [registrars] [Ext] Re: RE: RRA Amendment Notification for xn--vuq861b [ ref:_00D616tJk._5004MgGPMH:ref ]
by Camia Frank June 2, 2021

June 2, 2021

Dear Lynn Xing, Thank you for your patience. ICANN org and the RrSG are still in discussion about the feedback and will revert back with more information as soon as possible. Please let us know if you have further questions. Warm Regards, Camia Frank GDS Service Delivery From: "xingna(a)teleinfo.cn" <xingna(a)teleinfo.cn> Date: Tuesday, June 1, 2021 at 7:40 PM To: "aheineman(a)godaddy.com" <aheineman(a)godaddy.com>, globalsupport <globalsupport(a)icann.org> Cc: Andrew Dickson <andrew.dickson(a)icann.org>, Jeanne Gregg <jeanne.gregg(a)icann.org>, "secretariat(a)icannregistrars.org" <secretariat(a)icannregistrars.org>, "registrars(a)icann.org" <registrars(a)icann.org>, "ceo(a)teleinfo.cn" <ceo(a)teleinfo.cn>, Andee Hill <andee.hill(a)icann.org>, Camia Frank <camia.frank(a)icann.org> Subject: [Ext] Re: RE: RRA Amendment Notification for xn--vuq861b [ ref:_00D616tJk._5004MgGPMH:ref ] Dear Ashley, Robert and all, Thanks a quick question. Any chance to let us know the expected date for the feedback? Thannks! Best Regards, ________________________________ 邢娜 Lynn Xing 手机/Mobile：+86 189 1028 3591 邮箱/Email：xingna(a)teleinfo.cn [teleinfo.cn]<https://urldefense.com/v3/__http:/liuwei@teleinfo.cn/__;!!PtGJab4!pZS4Iv9HW…> www.teleinfo.cn [teleinfo.cn]<https://urldefense.com/v3/__http:/www.teleinfo.cn/__;!!PtGJab4!pZS4Iv9HWFf9…> 数字网络运营商北京泰尔英福网络科技有限责任公司北京市海淀区中关村科技园翠湖云中心21号楼，100095 From: aheineman(a)godaddy.com<mailto:aheineman@godaddy.com> Date: 2021-05-25 23:31 To: ICANN - Global Support<mailto:globalsupport@icann.org> CC: andrew.dickson(a)icann.org<mailto:andrew.dickson@icann.org>; jeanne.gregg(a)icann.org<mailto:jeanne.gregg@icann.org>; secretariat(a)icannregistrars.org<mailto:secretariat@icannregistrars.org>; registrars(a)icann.org<mailto:registrars@icann.org>; ceo(a)teleinfo.cn<mailto:ceo@teleinfo.cn>; andee.hill(a)icann.org<mailto:andee.hill@icann.org>; xingna(a)teleinfo.cn<mailto:xingna@teleinfo.cn>; camia.frank(a)icann.org<mailto:camia.frank@icann.org> Subject: RE: Re: RRA Amendment Notification for xn--vuq861b [ ref:_00D616tJk._5004MgGPMH:ref ] Dear Robert, all. My sincerest apologies, but didn’t receive the email from 5/15 (spam folder!). Let me and the registrars review and get back soonest. From: ICANN - Global Support <globalsupport(a)icann.org> Sent: Tuesday, May 25, 2021 10:51 AM To: Ashley Heineman <aheineman(a)godaddy.com> Cc: andrew.dickson(a)icann.org; jeanne.gregg(a)icann.org; secretariat(a)icannregistrars.org; registrars(a)icann.org; ceo(a)teleinfo.cn; andee.hill(a)icann.org; xingna(a)teleinfo.cn; camia.frank(a)icann.org Subject: Re: Re: RRA Amendment Notification for xn--vuq861b [ ref:_00D616tJk._5004MgGPMH:ref ] Caution: This email is from an external sender. Please do not click links or open attachments unless you recognize the sender and know the content is safe. Forward suspicious emails to isitbad@. Dear Ashley, On 15 May 2021, the registry operator provided a response to the RrSG's (30 April 2021) feedback. This is a follow up to confirm if your Stakeholder Group has concerns, does not have concerns, or if additional review time is required. Kind regards, Robert Gomez GDS Service Delivery --------------- Original Message --------------- From: xingna(a)teleinfo.cn<mailto:xingna@teleinfo.cn> [xingna(a)teleinfo.cn] Sent: 5/15/2021 2:20 AM To: globalsupport(a)icann.org<mailto:globalsupport@icann.org>; secretariat(a)icannregistrars.org<mailto:secretariat@icannregistrars.org> Cc: andrew.dickson(a)icann.org<mailto:andrew.dickson@icann.org>; jeanne.gregg(a)icann.org<mailto:jeanne.gregg@icann.org>; registrars(a)icann.org<mailto:registrars@icann.org>; ceo(a)teleinfo.cn<mailto:ceo@teleinfo.cn>; andee.hill(a)icann.org<mailto:andee.hill@icann.org>; aheineman(a)godaddy.com<mailto:aheineman@godaddy.com>; xingna(a)teleinfo.cn<mailto:xingna@teleinfo.cn>; camia.frank(a)icann.org<mailto:camia.frank@icann.org> Subject: Re: Re: RRA Amendment Notification for xn--vuq861b [ ref:_00D616tJk._5004MgGPMH:ref ] Dear ICANN team, Thank you for your feedback and advice! In order to improve the financial stability, we (as the Registry Operator) have proposed the new prepayment scheme in the Amendment RRA, the main reason is that we would like to promote .???xn--vuQ861B?domain names via all registrars, specially to the registrars who had rich experience in IDN market and sales. They have strong customer base for IDN, we are trying to push our domain sales to a new level. Our registration number were used to be over 50,000. We expect the number of .???xn--vuQ861B?domain names to create a new record. Thus, we want to raise the bar for the new registrar who really wants to cooperate with us and promote .???xn--vuQ861B?domain names together. This prepayment change will only affect the new registrar, and have minimal impact on the existing registrar. Alternatively, we can reduce the prepayment amount from $153,000 to $76,500. We would like to try this process as the first step, if things go well, we will see if we need to take any further actions. We will follow the ICANN procedure and keep you posted. Please don't hesitate to contact us if you have any further questions. Looking forward to hearing from you! Best Regards, ________________________________ ?? Lynn Xing ??/Mobile?+86 189 1028 3591 ??/Email?xingna(a)teleinfo.cn [teleinfo.cn]<https://urldefense.com/v3/__http:/liuwei@teleinfo.cn/__;!!PtGJab4!pZS4Iv9HW…> www.teleinfo.cn [teleinfo.cn]<https://urldefense.com/v3/__http:/www.teleinfo.cn/__;!!PtGJab4!pZS4Iv9HWFf9…> ??????? ???????????????? ?????????????????21???100095 From: ICANN - Global Support<mailto:globalsupport@icann.org> Date: 2021-05-05 01:42 To: secretariat(a)icannregistrars.org<mailto:secretariat@icannregistrars.org> CC: andrew.dickson(a)icann.org<mailto:andrew.dickson@icann.org>; jeanne.gregg(a)icann.org<mailto:jeanne.gregg@icann.org>; registrars(a)icann.org<mailto:registrars@icann.org>; ceo(a)teleinfo.cn<mailto:ceo@teleinfo.cn>; andee.hill(a)icann.org<mailto:andee.hill@icann.org>; aheineman(a)godaddy.com<mailto:aheineman@godaddy.com>; camia.frank(a)icann.org<mailto:camia.frank@icann.org>; xingna(a)teleinfo.cn<mailto:xingna@teleinfo.cn> Subject: Re: RRA Amendment Notification for xn--vuq861b [ ref:_00D616tJk._5004MgGPMH:ref ] Dear Zoe Bonython, Thank you for the update. The Registry Operator is copied on this thread and can directly respond to the RrSG's feedback provided below for convenience: "The registrars have one material comment on a new requirement in the Amended RRA which essentially states that registrars pre-pay 1 million RMB within 1 month of the signing of the new Agreement. This amounts to approximately US $153,000. Failure to pay this amount will result in “suspension or termination of the authority of Registrar in creating new Standard names.” In general, the Registrars do not comment on the price of domain name registrars so long as the pricing changes are done in accordance with what is required by ICANN and as reflected in the Registry Agreement. In this case, we believe that in a Registry where the price of a registration is less than $ US 20, and no registrars has more than 1000 registrations (most have less than 100 names), a prepayment of $153,000 by each Registrar cannot be said to be reasonably related to the proper functioning of the TLD (as is required in Section 2.9 of the Registry Agreement). We therefore ask that the Registry Operator either remove this new requirement, or in the alternative, explain the purpose of this new requirement and adjust the amount to something more commensurate with what is “reasonably related to the proper functioning of the TLD." Kind regards, Robert Gomez GDS Service Delivery --------------- Original Message --------------- From: Zoe Bonython [secretariat(a)icannregistrars.org] Sent: 4/30/2021 8:17 AM To: globalsupport(a)icann.org<mailto:globalsupport@icann.org>; registrars(a)icann.org<mailto:registrars@icann.org>; aheineman(a)godaddy.com<mailto:aheineman@godaddy.com> Cc: ceo(a)teleinfo.cn<mailto:ceo@teleinfo.cn>; andrew.dickson(a)icann.org<mailto:andrew.dickson@icann.org>; robert.gomez(a)icann.org<mailto:robert.gomez@icann.org>; andee.hill(a)icann.org<mailto:andee.hill@icann.org>; jeanne.gregg(a)icann.org<mailto:jeanne.gregg@icann.org>; camia.frank(a)icann.org<mailto:camia.frank@icann.org> Subject: Re: RRA Amendment Notification for xn--vuq861b [ ref:_00D616tJk._5004MgGPMH:ref ] Hi Robert & All, Apologies for the late reply, Ashley is on leave this week. Please see below for the response from RrSG: The registrars have one material comment on a new requirement in the Amended RRA which essentially states that registrars pre-pay 1 million RMB within 1 month of the signing of the new Agreement. This amounts to approximately US $153,000. Failure to pay this amount will result in “suspension or termination of the authority of Registrar in creating new Standard names.” In general, the Registrars do not comment on the price of domain name registrars so long as the pricing changes are done in accordance with what is required by ICANN and as reflected in the Registry Agreement. In this case, we believe that in a Registry where the price of a registration is less than $ US 20, and no registrars has more than 1000 registrations (most have less than 100 names), a prepayment of $153,000 by each Registrar cannot be said to be reasonably related to the proper functioning of the TLD (as is required in Section 2.9 of the Registry Agreement). We therefore ask that the Registry Operator either remove this new requirement, or in the alternative, explain the purpose of this new requirement and adjust the amount to something more commensurate with what is “reasonably related to the proper functioning of the TLD.” Kind regards, Zoe Bonython RrSG Secretariat From: ICANN - Global Support <globalsupport(a)icann.org<mailto:globalsupport@icann.org>> Date: Tuesday, April 27, 2021 at 4:32 PM To: "secretariat(a)icannregistrars.org<mailto:secretariat@icannregistrars.org>" <secretariat(a)icannregistrars.org<mailto:secretariat@icannregistrars.org>>, "registrars(a)icann.org<mailto:registrars@icann.org>" <registrars(a)icann.org<mailto:registrars@icann.org>>, "aheineman(a)godaddy.com<mailto:aheineman@godaddy.com>" <aheineman(a)godaddy.com<mailto:aheineman@godaddy.com>> Cc: "ceo(a)teleinfo.cn<mailto:ceo@teleinfo.cn>" <ceo(a)teleinfo.cn<mailto:ceo@teleinfo.cn>>, "robert.gomez(a)icann.org<mailto:robert.gomez@icann.org>" <robert.gomez(a)icann.org<mailto:robert.gomez@icann.org>>, "andrew.dickson(a)icann.org<mailto:andrew.dickson@icann.org>" <andrew.dickson(a)icann.org<mailto:andrew.dickson@icann.org>>, "camia.frank(a)icann.org<mailto:camia.frank@icann.org>" <camia.frank(a)icann.org<mailto:camia.frank@icann.org>>, "andee.hill(a)icann.org<mailto:andee.hill@icann.org>" <andee.hill(a)icann.org<mailto:andee.hill@icann.org>>, "jeanne.gregg(a)icann.org<mailto:jeanne.gregg@icann.org>" <jeanne.gregg(a)icann.org<mailto:jeanne.gregg@icann.org>> Subject: RE: RRA Amendment Notification for xn--vuq861b [ ref:_00D616tJk._5004MgGPMH:ref ] Dear Ashley, On 05 April 2021 ICANN org provided the cover letter and red-lined RRA Amendment for xn--vuq861b submitted by Beijing Tele-info Network Technology Co., Ltd. This is a follow up to confirm if your Stakeholder Group has concerns, does not have concerns, or if additional review time is required. If the Stakeholder Group has concerns, ICANN org will continue with the next step of the RRA Amendment Procedure, which is to consult with the RrSG and the Registry Operator to attempt to resolve any such concerns. Kind regards, Robert Gomez GDS Service Delivery --------------- Original Message --------------- From: ICANN - Global Support [globalsupport(a)icann.org] Sent: 4/5/2021 2:31 PM To: secretariat(a)icannregistrars.org<mailto:secretariat@icannregistrars.org>; registrars(a)icann.org<mailto:registrars@icann.org>; aheineman(a)godaddy.com<mailto:aheineman@godaddy.com> Cc: andee.hill(a)icann.org<mailto:andee.hill@icann.org>; andrew.dickson(a)icann.org<mailto:andrew.dickson@icann.org>; jeanne.gregg(a)icann.org<mailto:jeanne.gregg@icann.org>; camia.frank(a)icann.org<mailto:camia.frank@icann.org>; robert.gomez(a)icann.org<mailto:robert.gomez@icann.org>; ceo(a)teleinfo.cn<mailto:ceo@teleinfo.cn> Subject: RRA Amendment Notification for xn--vuq861b [ ref:_00D616tJk._5004MgGPMH:ref ] Hello Ashley, Attached, please find the cover letter and the red-lined RRA Amendment for the following TLD submitted by Beijing Tele-info Network Technology Co., Ltd. to be shared with your Stakeholder Group: xn--vuq861b Please respond by 23:59 UTC on Monday, 26 April 2021 to let us know if your Stakeholder Group has concerns, does not have concerns, or if additional review time is required. If the Stakeholder Group has concerns, ICANN org will continue with the next step of the RRA Amendment Procedure, which is to consult with the RrSG and the Registry Operator to attempt to resolve any such concerns. Thank you, Robert Gomez GDS Service Delivery[Image removed by sender.] ref:_00D616tJk._5004MgGPMH:ref Kind regards, Robert Gomez GDS Service Delivery Internet Corporation for Assigned Names and Numbers (ICANN)[Image removed by sender.] Kind regards, Robert Gomez GDS Service Delivery Internet Corporation for Assigned Names and Numbers (ICANN) Kind regards, Robert Gomez GDS Service Delivery Internet Corporation for Assigned Names and Numbers (ICANN)

1 0

Test message - please disregard
by Pete Elsesser May 4, 2021

May 4, 2021

This is a test message, please disregard. -- Pete Elsesser End User Support Internet Corporation for Assigned Names and Numbers (ICANN) Email: peter.elsesser(a)icann.org Direct: +1 310 578 8666 www.icann.org

1 0

Re: [registrars] [Ext] Re: RRA Amendment Notification for .TICKETS [ ref:_00D616tJk._5004Mj6mlt:ref ]
by Camia Frank May 3, 2021

May 3, 2021

Hi Zoe, Thank you for the message. We look forward to receiving the feedback from the RrSG upon Ashley’s return. Warm Regards, Camia Frank GDS Service Delivery From: Zoe Bonython <secretariat(a)icannregistrars.org> Date: Friday, April 30, 2021 at 8:29 AM To: ICANN Global Support Center <globalsupport(a)icann.org>, "registrars(a)icann.org" <registrars(a)icann.org>, "aheineman(a)godaddy.com" <aheineman(a)godaddy.com> Cc: Robert Gomez <robert.gomez(a)icann.org>, Andee Hill <andee.hill(a)icann.org>, Jeanne Gregg <jeanne.gregg(a)icann.org>, Andrew Dickson <andrew.dickson(a)icann.org>, Camia Frank <camia.frank(a)icann.org>, "gc(a)xyz.xyz" <gc(a)xyz.xyz> Subject: [Ext] Re: RRA Amendment Notification for .TICKETS [ ref:_00D616tJk._5004Mj6mlt:ref ] Hi Camia & All, I’m aware that comments on .TICKETS are also due today, but with Ashely being on leave this week, we are slightly behind on the full member review of comments prepared by the RRA Amendment Review. We kindly ask that the comments be provided on Monday, 3 May 2021 and apologize for the delay. Kind regards, Zoe From: ICANN Global Support Center <globalsupport(a)icann.org> Date: Friday, April 9, 2021 at 7:48 PM To: "secretariat(a)icannregistrars.org" <secretariat(a)icannregistrars.org>, "registrars(a)icann.org" <registrars(a)icann.org>, "aheineman(a)godaddy.com" <aheineman(a)godaddy.com> Cc: "robert.gomez(a)icann.org" <robert.gomez(a)icann.org>, "andee.hill(a)icann.org" <andee.hill(a)icann.org>, "jeanne.gregg(a)icann.org" <jeanne.gregg(a)icann.org>, "andrew.dickson(a)icann.org" <andrew.dickson(a)icann.org>, "camia.frank(a)icann.org" <camia.frank(a)icann.org>, "gc(a)xyz.xyz" <gc(a)xyz.xyz> Subject: RRA Amendment Notification for .TICKETS [ ref:_00D616tJk._5004Mj6mlt:ref ] Hello Ashley, Attached, please find the cover letter and the red-lined RRA Amendment for the following TLD submitted by XYZ.COM LLC to be shared with your Stakeholder Group: .TICKETS Please respond by 23:59 UTC on Friday, 30 April 2021 to let us know if your Stakeholder Group has concerns, does not have concerns, or if additional review time is required. If the Stakeholder Group has concerns, ICANN org will continue with the next step of the RRA Amendment Procedure, which is to consult with the RrSG and the Registry Operator to attempt to resolve any such concerns. Warm Regards, Camia Frank GDS Service Delivery [Image removed by sender.] ref:_00D616tJk._5004Mj6mlt:ref

1 0

Re: [registrars] [Ext] RRA Amendment Notification for .PHARMACY [ ref:_00D616tJk._5004MgG63v:ref ]
by Camia Frank April 15, 2021

April 15, 2021

Dear Ashley, On 24 March 2021 ICANN org provided the cover letter and red-lined RRA Amendment for .PHARMACY submitted by National Association of Boards of Pharmacy This is a follow up to confirm if your Stakeholder Group has concerns, does not have concerns, or if additional review time is required. If the Stakeholder Group has concerns, ICANN org will continue with the next step of the RRA Amendment Procedure, which is to consult with the RrSG and the Registry Operator to attempt to resolve any such concerns. Warm Regards, Camia Frank GDS Service Delivery From: ICANN Global Support Center <globalsupport(a)icann.org> Date: Wednesday, March 24, 2021 at 5:12 PM To: "aheineman(a)godaddy.com" <aheineman(a)godaddy.com>, "secretariat(a)icannregistrars.org" <secretariat(a)icannregistrars.org>, "registrars(a)icann.org" <registrars(a)icann.org> Cc: Andrew Dickson <andrew.dickson(a)icann.org>, Andee Hill <andee.hill(a)icann.org>, Jeanne Gregg <jeanne.gregg(a)icann.org>, Robert Gomez <robert.gomez(a)icann.org>, Camia Frank <camia.frank(a)icann.org>, "glevine(a)nabp.pharmacy" <glevine(a)nabp.pharmacy> Subject: [Ext] RRA Amendment Notification for .PHARMACY [ ref:_00D616tJk._5004MgG63v:ref ] Hello Ashley, Attached, please find the cover letter and the red-lined RRA Amendment for the following TLD submitted by National Association of Boards of Pharmacy to be shared with your Stakeholder Group: .PHARMACY Please respond by 23:59 UTC on Wednesday, 14 April 2021 to let us know if your Stakeholder Group has concerns, does not have concerns, or if additional review time is required. If the Stakeholder Group has concerns, ICANN org will continue with the next step of the RRA Amendment Procedure, which is to consult with the RrSG and the Registry Operator to attempt to resolve any such concerns. Warm Regards, Camia Frank GDS Service Delivery [Image removed by sender.] ref:_00D616tJk._5004MgG63v:ref

1 0

Re: [registrars] [Ext] RRA Amendment Notification for .DESIGN, .INK, & .WIKI [ ref:_00D616tJk._5004MgDdR8:ref ]
by Camia Frank March 10, 2021

March 10, 2021

Hi Ashley, I wanted to follow up and get confirmation that the changes that were made have been approved by the RrSG. If there are no further concerns and the changes are accepted ICANN org will continue the process. Warm Regards, Camia Frank GDS Service Delivery From: Andrew Merriam <andrew(a)toplevel.design> Date: Thursday, February 25, 2021 at 10:57 AM To: "aheineman(a)godaddy.com" <aheineman(a)godaddy.com> Cc: Zoe Bonython <secretariat(a)icannregistrars.org>, "registrars(a)icann.org" <registrars(a)icann.org>, Jeanne Gregg <jeanne.gregg(a)icann.org>, Robert Gomez <robert.gomez(a)icann.org>, Andee Hill <andee.hill(a)icann.org>, Andrew Dickson <andrew.dickson(a)icann.org>, Camia Frank <camia.frank(a)icann.org>, "rra-review(a)rrsg.org" <rra-review(a)rrsg.org>, "excom(a)rrsg.org" <excom(a)rrsg.org> Subject: Re: [registrars] [Ext] RRA Amendment Notification for .DESIGN, .INK, & .WIKI [ ref:_00D616tJk._5004MgDdR8:ref ] Hi all, Ashley, It was nice to meet with you and the group today. I've made edits to all areas under discussion in the attached. I've summarized the changes below. (My Microsoft no longer knows who I am, apparently, and has ascribed the edits to "Microsoft User". While strange, it does mean that they stick out from the prior edits.) We both noted on the call that we are unsure of the ICANN org process from here but I suspect if you review these changes with your group as needed and then confirm with ICANN that the attached reflects your input and you approve of the changes, then I assume ICANN will work with us at the registry from that point forward to close this out. ICANN team, please do let us know if anything beyond Ashley's pending approval is required. Thank you, -A --Edit Summary-- Most importantly, * 7.1 * Added suggested language on pricing directly from Ashley's email to 7.1. Additionally, * 4.7 * Reverted to "will", thereby striking suggested "may" (in reference to g pricing list, RO will provide etc.) * 5.9.6 * Struck in its entirety, "for violation of any RO policy" * 5.16 * Reverted to inclusion of "reasonable" (in reference to policies published re: written complains pertaining to inaccurate Whois data) * 6.1 * Struck reference to "any other dispute resolution policy" and related details. All edits from the attached .design draft that arose via collaboration with RrSG are to be reflected on updated .wiki and .ink documents to be submitted to ICANN as we move forward. On Fri, Feb 19, 2021 at 8:58 AM Andrew Merriam <andrew(a)toplevel.design> wrote: That does indeed work for me. I'll look for an invite. Thank you. Have a nice weekend, -A On Fri, Feb 19, 2021 at 7:59 AM aheineman(a)godaddy.com<mailto:aheineman@godaddy.com> <aheineman(a)godaddy.com<mailto:aheineman@godaddy.com>> wrote: Thanks Andrew. Would a zoom meeting next Thursday (2/25) at 16:30 UTC work for you? From: Andrew Merriam <andrew(a)toplevel.design> Sent: Wednesday, February 17, 2021 7:19 PM To: Ashley Heineman <aheineman(a)godaddy.com<mailto:aheineman@godaddy.com>> Cc: Zoe Bonython <secretariat(a)icannregistrars.org<mailto:secretariat@icannregistrars.org>>; registrars(a)icann.org<mailto:registrars@icann.org>; Jeanne Gregg <jeanne.gregg(a)icann.org<mailto:jeanne.gregg@icann.org>>; Robert Gomez <robert.gomez(a)icann.org<mailto:robert.gomez@icann.org>>; Andee Hill <andee.hill(a)icann.org<mailto:andee.hill@icann.org>>; Andrew Dickson <andrew.dickson(a)icann.org<mailto:andrew.dickson@icann.org>>; Camia Frank <camia.frank(a)icann.org<mailto:camia.frank@icann.org>>; rra-review(a)rrsg.org<mailto:rra-review@rrsg.org>; excom(a)rrsg.org<mailto:excom@rrsg.org> Subject: Re: [registrars] [Ext] RRA Amendment Notification for .DESIGN, .INK, & .WIKI [ ref:_00D616tJk._5004MgDdR8:ref ] Notice: This email is from an external sender. Thank you, Ashley, for your time leading the group, and to the wider RrSG for being engaged. It was certainly not our intention to put you and the group to work with what we saw as routine updates! The proposed, italicized language in your email looks good. I do not see that entered in this "RrSG" marked .docx redline attachment but we can add that in following a call. I assume this language would be inserted in 7.1, where we currently suggest striking the "180 days prior notice". I am available as soon as Friday for a call and am based in the Pacific time zone. I am also largely available Tue 23 - Fri 26 next week and will allow you to suggest a time that works for you and any subset of your members. I do not feel we need ICANN org nor the full membership on this call and so am hoping we can make something quickly happen with yourself and/or any designated leaders. To make that call more efficient, and just to provide some insight to everyone, I have created a list of responses to your comments below. Thanks, again, Ashley! I look forward to wrapping this up. -A --- 4.7 Price list * "will" v. "must" of current price list * "will" is fine. A price list is created in order to program the premium name anyways, so it does exist. It is a machine-ready .csv file. * I note that the format of the list is not specified here, our intent was only to get away from the expectation that registrars have had about a certain formatted list (e.g., tag all increases and decreases) as well as recognize that we do not like to distribute these en masse as attachments in emails as we view it as a proprietary work product (and prefer to provide at registrar request or to direct registrars to the CentralNic console). Also timing and version control en masse of the lists can be finicky (and I can talk through examples on the call as needed). * As I understand it, the lists themselves always have and will be available for registrar download via the CentralNic console. 5.5 Registrar's Registration Agreement * "and any other terms RO may from time to time promulgate" * I view this as routine language that entered into the agreement by way of the CentralNic master agreement and/or legal review as we prepared the .gay RRA (on which the updates are based). In my reading, this language was likely carved out in the case of some emerging policies we would need to stay ahead of (e.g. new legislation that ICANN org/community does not adequately get in front of and requires us/registries to create our own policies). * Per your note, I am open to understanding how we would notify registrars of any changes. In our 7 years as a registry operator, we have never "promulgated" anything, let alone something that would need to be inserted in the Registration Agreement. 5.9.4 (6) Reserve the right to cancel [etc] * "for violation of any RO policy" * I agree that this does seem broad and am open to a "reasonableness" clause. I think it is not strange or surprising that Registries reserve the rights to intervene with a given name for broad reasons. I suspect this is fairly common, especially as it has roots in the CentralNic master agreement. I also believe that this is hardly ever exercised by any Registry. 5.16 Written Complaints * strike of word "reasonable". * I am open to leaving this in. I suspect in this case that legal review didn't like how mushy this word is. I personally do not understand the legal definition of "reasonable" and suspect many here could have a field day with that topic. 6.1 Domain Name Dispute Resolution * "And any other dispute resolution policy that RO may establish". * We have nothing envisioned specifically here. We created unique content restrictions and related processes for .gay (which are not carried over here) but I would define that as Acceptable Use and Abuse policies and not a Dispute Resolution Policy and so I do not view this as directly related to any existing system or envisioned system. On Sat, Feb 13, 2021 at 7:55 AM aheineman(a)godaddy.com<mailto:aheineman@godaddy.com> <aheineman(a)godaddy.com<mailto:aheineman@godaddy.com>> wrote: Dear Andrew, Thank you very much for your patience as the RrSG discussed the .DESIGN, .INK, & .WIKI RRA amendments. After lengthy discussions, we would like to withdraw our request to insert a 180 day notification period for all price changes and hopefully clarify our intent. Understanding that the RA outlines a commitment from the RO to ICANN and therefore sets the baseline minimum requirement for fee notifications, there are situations where that minimum isn’t sufficient. For standard-fee domains, the commitments made to ICANN in the RA are sufficient, we are asking to have them stated explicitly in the RRA for the avoidance of confusion should the RA change in the future. Succinctly summarizing sections 2.10(a) and 2.10(b) from the RA, something to the effect of: With respect to domain name registrations that are NOT designated as Premium Domain Names, RO will provide Registrar with 30 day notice for increases to fees for initial registrations, and 180 day notice for renewal domain name registrations. With respect to Premium Domain Names, notice shall be in accordance with Exhibit B. In addition, we would like to have a conversation directly with you about a handful of other amendments that were proposed for .DESIGN, .INK, & .WIKI. We have highlighted the edits in the attached for your reference (applicable to all three RRA amendments), but we feel that a conversation would be much easier to resolve our questions/concerns rather than attempt to address them via email. Thank you very much and looking forward to arranging a time to discuss. Ashley Heineman RrSG Chair aheineman(a)godaddy.com<mailto:aheineman@godaddy.com> From: Andrew Merriam <andrew(a)toplevel.design<mailto:andrew@toplevel.design>> Sent: Friday, February 5, 2021 2:52 PM To: Ashley Heineman <aheineman(a)godaddy.com<mailto:aheineman@godaddy.com>> Cc: Zoe Bonython <secretariat(a)icannregistrars.org<mailto:secretariat@icannregistrars.org>>; registrars(a)icann.org<mailto:registrars@icann.org>; Jeanne Gregg <jeanne.gregg(a)icann.org<mailto:jeanne.gregg@icann.org>>; Robert Gomez <robert.gomez(a)icann.org<mailto:robert.gomez@icann.org>>; Andee Hill <andee.hill(a)icann.org<mailto:andee.hill@icann.org>>; Andrew Dickson <andrew.dickson(a)icann.org<mailto:andrew.dickson@icann.org>>; Camia Frank <camia.frank(a)icann.org<mailto:camia.frank@icann.org>> Subject: Re: [registrars] [Ext] RRA Amendment Notification for .DESIGN, .INK, & .WIKI [ ref:_00D616tJk._5004MgDdR8:ref ] Notice: This email is from an external sender. Hi Ashley, We esteem you and all of our registrar partners and the collective RrSG highly. I'm happy to accommodate another one week extension from my end and look to ICANN org to confirm anything else needed from us at this time. This is true that the relevant language is in the .DESIGN, .INK, and .WIKI amendments (which is why initially singling out .ink felt especially arbitrary). This is of course, as mentioned, already implemented in the 2020 .gay agreement. I would additionally note that on the topic of price changes (could be GA price changes and/or premium price changes), there is not a default that I know of. Aside from the .gay example, I know of other registries that have contracts ranging from 30 - 90 days. Many of us likely saw that just this week, .qpon sent out a 90 day notice of price increase of its standard names. So, continuing to require 180 days on .DESIGN, .INK, and .WIKI per your Jan 28th email does not feel equitable. I hope we can agree on something that respects your needs as well as recognizes the many other counter-examples already in the market. Thanks! Wishing you well, -A On Fri, Feb 5, 2021 at 11:31 AM aheineman(a)godaddy.com<mailto:aheineman@godaddy.com> <aheineman(a)godaddy.com<mailto:aheineman@godaddy.com>> wrote: Dear Andrew. RrSG membership has been discussing the price change notification issue at length as it applies to the .DESIGN, .INK, and .WIKI amendments. Through this discussion a number of additional issues have been identified. May I request another week to get back to you with a consolidated RrSG response? I admit that this is new territory for me with respect to process. Any guidance from ICANN staff would be greatly appreciated. From: Andrew Merriam <andrew(a)toplevel.design<mailto:andrew@toplevel.design>> Sent: Thursday, January 28, 2021 3:11 PM To: Ashley Heineman <aheineman(a)godaddy.com<mailto:aheineman@godaddy.com>> Cc: Zoe Bonython <secretariat(a)icannregistrars.org<mailto:secretariat@icannregistrars.org>>; registrars(a)icann.org<mailto:registrars@icann.org>; Jeanne Gregg <jeanne.gregg(a)icann.org<mailto:jeanne.gregg@icann.org>>; Robert Gomez <robert.gomez(a)icann.org<mailto:robert.gomez@icann.org>>; Andee Hill <andee.hill(a)icann.org<mailto:andee.hill@icann.org>>; Andrew Dickson <andrew.dickson(a)icann.org<mailto:andrew.dickson@icann.org>> Subject: Re: [registrars] [Ext] RRA Amendment Notification for .DESIGN, .INK, & .WIKI [ ref:_00D616tJk._5004MgDdR8:ref ] Notice: This email is from an external sender. Yes, please do. I didn't want to respond to the full group as I didn't know if this communication was in bounds of the imagined ICANN process, let alone the fact that it's likely a giant group :) On Thu, Jan 28, 2021 at 12:08 PM aheineman(a)godaddy.com<mailto:aheineman@godaddy.com> <aheineman(a)godaddy.com<mailto:aheineman@godaddy.com>> wrote: Andrew, may I share your email with the RrSG so that we may respond? I assure you this was not an arbitrary issue and is in fact a point we have taken issue with for multiple past RRA amendments. The fact that this was not raised for .gay was an oversight I am pretty sure, but would need to check with membership. Get Outlook for Android [aka.ms]<https://urldefense.com/v3/__https:/aka.ms/ghei36__;!!PtGJab4!qFW2WP4tn5BnYk…> ________________________________ From: Andrew Merriam <andrew(a)toplevel.design<mailto:andrew@toplevel.design>> Sent: Thursday, January 28, 2021 3:02:57 PM To: Ashley Heineman <aheineman(a)godaddy.com<mailto:aheineman@godaddy.com>> Cc: Zoe Bonython <secretariat(a)icannregistrars.org<mailto:secretariat@icannregistrars.org>>; registrars(a)icann.org<mailto:registrars@icann.org> <registrars(a)icann.org<mailto:registrars@icann.org>>; Jeanne Gregg <jeanne.gregg(a)icann.org<mailto:jeanne.gregg@icann.org>>; Robert Gomez <robert.gomez(a)icann.org<mailto:robert.gomez@icann.org>>; Andee Hill <andee.hill(a)icann.org<mailto:andee.hill@icann.org>>; Andrew Dickson <andrew.dickson(a)icann.org<mailto:andrew.dickson@icann.org>> Subject: Re: [registrars] [Ext] RRA Amendment Notification for .DESIGN, .INK, & .WIKI [ ref:_00D616tJk._5004MgDdR8:ref ] Notice: This email is from an external sender. Hello all, I have removed the full group and left Ashley, Zoe, and those from ICANN org. I believe I am cc'd as a courtesy, as the Registry representative, but thought to respond to this point to help with any further consultation. The point for .ink specifically seems arbitrary. This redline language matches our 2020 .gay RRA which was accepted and signed by GoDaddy and the vast majority of Registrar Stakeholder Group members. The current language leaves in place the requirements as defined by our RA with ICANN [icann.org]<https://urldefense.com/v3/__https:/www.icann.org/sites/default/files/tlds/i…> (2.1), which I believe is a minimum of 30 days. So, this exact same language has already been accepted for our other TLD. I look forward to remediating any further issues efficiently. Thanks, have good days, A On Thu, Jan 28, 2021 at 7:07 AM aheineman(a)godaddy.com<mailto:aheineman@godaddy.com> <aheineman(a)godaddy.com<mailto:aheineman@godaddy.com>> wrote: With respect to .INK – under section 7, the requirement for 180 day notice for price increases and decreases should be maintained. Let me know if you have any questions. Thanks. ##- Please type your reply above this line -## You are registered as a CC on this request (369075). Reply to this email to add a comment to the request. This email is a service from Ascio Fulfillment. Delivered by Zendesk [zendesk.com]<https://urldefense.com/v3/__https:/www.zendesk.com/support/?utm_campaign=te…> [V02L6Y-KP99] -- Andrew Merriam (he / him) Vice President of Business Development Top Level Design, LLC toplevel.design [toplevel.design]<https://urldefense.com/v3/__http:/toplevel.design/__;!!PtGJab4!qFW2WP4tn5Bn…> -- Andrew Merriam (he / him) Vice President of Business Development Top Level Design, LLC toplevel.design [toplevel.design]<https://urldefense.com/v3/__http:/toplevel.design/__;!!PtGJab4!qFW2WP4tn5Bn…> -- Andrew Merriam (he / him) Vice President of Business Development Top Level Design, LLC toplevel.design [toplevel.design]<https://urldefense.com/v3/__http:/toplevel.design/__;!!PtGJab4!qFW2WP4tn5Bn…> -- Andrew Merriam (he / him) Vice President of Business Development Top Level Design, LLC toplevel.design [toplevel.design]<https://urldefense.com/v3/__http:/toplevel.design/__;!!PtGJab4!qFW2WP4tn5Bn…> -- Andrew Merriam (he / him) Vice President of Business Development Top Level Design, LLC toplevel.design [toplevel.design]<https://urldefense.com/v3/__http:/toplevel.design/__;!!PtGJab4!qFW2WP4tn5Bn…> -- Andrew Merriam (he / him) Vice President of Business Development Top Level Design, LLC toplevel.design [toplevel.design]<https://urldefense.com/v3/__http:/toplevel.design/__;!!PtGJab4!qFW2WP4tn5Bn…>

3 2

Re: [registrars] [Ext] RRA Amendment Notification for .DESIGN, .INK, & .WIKI [ ref:_00D616tJk._5004MgDdR8:ref ]
by Camia Frank Feb. 25, 2021

Feb. 25, 2021

Hi Everyone, Thank you for this message and providing the updated documentation. We do not require anything further than Ashley’s approval of the proposed changes. Once provided, we will finish up the process and close out the request. Please let me know if you have any further questions or comments. Warm Regards, Camia Frank GDS Service Delivery From: Andrew Merriam <andrew(a)toplevel.design> Date: Thursday, February 25, 2021 at 10:57 AM To: "aheineman(a)godaddy.com" <aheineman(a)godaddy.com> Cc: Zoe Bonython <secretariat(a)icannregistrars.org>, "registrars(a)icann.org" <registrars(a)icann.org>, Jeanne Gregg <jeanne.gregg(a)icann.org>, Robert Gomez <robert.gomez(a)icann.org>, Andee Hill <andee.hill(a)icann.org>, Andrew Dickson <andrew.dickson(a)icann.org>, Camia Frank <camia.frank(a)icann.org>, "rra-review(a)rrsg.org" <rra-review(a)rrsg.org>, "excom(a)rrsg.org" <excom(a)rrsg.org> Subject: Re: [registrars] [Ext] RRA Amendment Notification for .DESIGN, .INK, & .WIKI [ ref:_00D616tJk._5004MgDdR8:ref ] Hi all, Ashley, It was nice to meet with you and the group today. I've made edits to all areas under discussion in the attached. I've summarized the changes below. (My Microsoft no longer knows who I am, apparently, and has ascribed the edits to "Microsoft User". While strange, it does mean that they stick out from the prior edits.) We both noted on the call that we are unsure of the ICANN org process from here but I suspect if you review these changes with your group as needed and then confirm with ICANN that the attached reflects your input and you approve of the changes, then I assume ICANN will work with us at the registry from that point forward to close this out. ICANN team, please do let us know if anything beyond Ashley's pending approval is required. Thank you, -A --Edit Summary-- Most importantly, * 7.1 * Added suggested language on pricing directly from Ashley's email to 7.1. Additionally, * 4.7 * Reverted to "will", thereby striking suggested "may" (in reference to g pricing list, RO will provide etc.) * 5.9.6 * Struck in its entirety, "for violation of any RO policy" * 5.16 * Reverted to inclusion of "reasonable" (in reference to policies published re: written complains pertaining to inaccurate Whois data) * 6.1 * Struck reference to "any other dispute resolution policy" and related details. All edits from the attached .design draft that arose via collaboration with RrSG are to be reflected on updated .wiki and .ink documents to be submitted to ICANN as we move forward. On Fri, Feb 19, 2021 at 8:58 AM Andrew Merriam <andrew(a)toplevel.design> wrote: That does indeed work for me. I'll look for an invite. Thank you. Have a nice weekend, -A On Fri, Feb 19, 2021 at 7:59 AM aheineman(a)godaddy.com<mailto:aheineman@godaddy.com> <aheineman(a)godaddy.com<mailto:aheineman@godaddy.com>> wrote: Thanks Andrew. Would a zoom meeting next Thursday (2/25) at 16:30 UTC work for you? From: Andrew Merriam <andrew(a)toplevel.design> Sent: Wednesday, February 17, 2021 7:19 PM To: Ashley Heineman <aheineman(a)godaddy.com<mailto:aheineman@godaddy.com>> Cc: Zoe Bonython <secretariat(a)icannregistrars.org<mailto:secretariat@icannregistrars.org>>; registrars(a)icann.org<mailto:registrars@icann.org>; Jeanne Gregg <jeanne.gregg(a)icann.org<mailto:jeanne.gregg@icann.org>>; Robert Gomez <robert.gomez(a)icann.org<mailto:robert.gomez@icann.org>>; Andee Hill <andee.hill(a)icann.org<mailto:andee.hill@icann.org>>; Andrew Dickson <andrew.dickson(a)icann.org<mailto:andrew.dickson@icann.org>>; Camia Frank <camia.frank(a)icann.org<mailto:camia.frank@icann.org>>; rra-review(a)rrsg.org<mailto:rra-review@rrsg.org>; excom(a)rrsg.org<mailto:excom@rrsg.org> Subject: Re: [registrars] [Ext] RRA Amendment Notification for .DESIGN, .INK, & .WIKI [ ref:_00D616tJk._5004MgDdR8:ref ] Notice: This email is from an external sender. Thank you, Ashley, for your time leading the group, and to the wider RrSG for being engaged. It was certainly not our intention to put you and the group to work with what we saw as routine updates! The proposed, italicized language in your email looks good. I do not see that entered in this "RrSG" marked .docx redline attachment but we can add that in following a call. I assume this language would be inserted in 7.1, where we currently suggest striking the "180 days prior notice". I am available as soon as Friday for a call and am based in the Pacific time zone. I am also largely available Tue 23 - Fri 26 next week and will allow you to suggest a time that works for you and any subset of your members. I do not feel we need ICANN org nor the full membership on this call and so am hoping we can make something quickly happen with yourself and/or any designated leaders. To make that call more efficient, and just to provide some insight to everyone, I have created a list of responses to your comments below. Thanks, again, Ashley! I look forward to wrapping this up. -A --- 4.7 Price list * "will" v. "must" of current price list * "will" is fine. A price list is created in order to program the premium name anyways, so it does exist. It is a machine-ready .csv file. * I note that the format of the list is not specified here, our intent was only to get away from the expectation that registrars have had about a certain formatted list (e.g., tag all increases and decreases) as well as recognize that we do not like to distribute these en masse as attachments in emails as we view it as a proprietary work product (and prefer to provide at registrar request or to direct registrars to the CentralNic console). Also timing and version control en masse of the lists can be finicky (and I can talk through examples on the call as needed). * As I understand it, the lists themselves always have and will be available for registrar download via the CentralNic console. 5.5 Registrar's Registration Agreement * "and any other terms RO may from time to time promulgate" * I view this as routine language that entered into the agreement by way of the CentralNic master agreement and/or legal review as we prepared the .gay RRA (on which the updates are based). In my reading, this language was likely carved out in the case of some emerging policies we would need to stay ahead of (e.g. new legislation that ICANN org/community does not adequately get in front of and requires us/registries to create our own policies). * Per your note, I am open to understanding how we would notify registrars of any changes. In our 7 years as a registry operator, we have never "promulgated" anything, let alone something that would need to be inserted in the Registration Agreement. 5.9.4 (6) Reserve the right to cancel [etc] * "for violation of any RO policy" * I agree that this does seem broad and am open to a "reasonableness" clause. I think it is not strange or surprising that Registries reserve the rights to intervene with a given name for broad reasons. I suspect this is fairly common, especially as it has roots in the CentralNic master agreement. I also believe that this is hardly ever exercised by any Registry. 5.16 Written Complaints * strike of word "reasonable". * I am open to leaving this in. I suspect in this case that legal review didn't like how mushy this word is. I personally do not understand the legal definition of "reasonable" and suspect many here could have a field day with that topic. 6.1 Domain Name Dispute Resolution * "And any other dispute resolution policy that RO may establish". * We have nothing envisioned specifically here. We created unique content restrictions and related processes for .gay (which are not carried over here) but I would define that as Acceptable Use and Abuse policies and not a Dispute Resolution Policy and so I do not view this as directly related to any existing system or envisioned system. On Sat, Feb 13, 2021 at 7:55 AM aheineman(a)godaddy.com<mailto:aheineman@godaddy.com> <aheineman(a)godaddy.com<mailto:aheineman@godaddy.com>> wrote: Dear Andrew, Thank you very much for your patience as the RrSG discussed the .DESIGN, .INK, & .WIKI RRA amendments. After lengthy discussions, we would like to withdraw our request to insert a 180 day notification period for all price changes and hopefully clarify our intent. Understanding that the RA outlines a commitment from the RO to ICANN and therefore sets the baseline minimum requirement for fee notifications, there are situations where that minimum isn’t sufficient. For standard-fee domains, the commitments made to ICANN in the RA are sufficient, we are asking to have them stated explicitly in the RRA for the avoidance of confusion should the RA change in the future. Succinctly summarizing sections 2.10(a) and 2.10(b) from the RA, something to the effect of: With respect to domain name registrations that are NOT designated as Premium Domain Names, RO will provide Registrar with 30 day notice for increases to fees for initial registrations, and 180 day notice for renewal domain name registrations. With respect to Premium Domain Names, notice shall be in accordance with Exhibit B. In addition, we would like to have a conversation directly with you about a handful of other amendments that were proposed for .DESIGN, .INK, & .WIKI. We have highlighted the edits in the attached for your reference (applicable to all three RRA amendments), but we feel that a conversation would be much easier to resolve our questions/concerns rather than attempt to address them via email. Thank you very much and looking forward to arranging a time to discuss. Ashley Heineman RrSG Chair aheineman(a)godaddy.com<mailto:aheineman@godaddy.com> From: Andrew Merriam <andrew(a)toplevel.design<mailto:andrew@toplevel.design>> Sent: Friday, February 5, 2021 2:52 PM To: Ashley Heineman <aheineman(a)godaddy.com<mailto:aheineman@godaddy.com>> Cc: Zoe Bonython <secretariat(a)icannregistrars.org<mailto:secretariat@icannregistrars.org>>; registrars(a)icann.org<mailto:registrars@icann.org>; Jeanne Gregg <jeanne.gregg(a)icann.org<mailto:jeanne.gregg@icann.org>>; Robert Gomez <robert.gomez(a)icann.org<mailto:robert.gomez@icann.org>>; Andee Hill <andee.hill(a)icann.org<mailto:andee.hill@icann.org>>; Andrew Dickson <andrew.dickson(a)icann.org<mailto:andrew.dickson@icann.org>>; Camia Frank <camia.frank(a)icann.org<mailto:camia.frank@icann.org>> Subject: Re: [registrars] [Ext] RRA Amendment Notification for .DESIGN, .INK, & .WIKI [ ref:_00D616tJk._5004MgDdR8:ref ] Notice: This email is from an external sender. Hi Ashley, We esteem you and all of our registrar partners and the collective RrSG highly. I'm happy to accommodate another one week extension from my end and look to ICANN org to confirm anything else needed from us at this time. This is true that the relevant language is in the .DESIGN, .INK, and .WIKI amendments (which is why initially singling out .ink felt especially arbitrary). This is of course, as mentioned, already implemented in the 2020 .gay agreement. I would additionally note that on the topic of price changes (could be GA price changes and/or premium price changes), there is not a default that I know of. Aside from the .gay example, I know of other registries that have contracts ranging from 30 - 90 days. Many of us likely saw that just this week, .qpon sent out a 90 day notice of price increase of its standard names. So, continuing to require 180 days on .DESIGN, .INK, and .WIKI per your Jan 28th email does not feel equitable. I hope we can agree on something that respects your needs as well as recognizes the many other counter-examples already in the market. Thanks! Wishing you well, -A On Fri, Feb 5, 2021 at 11:31 AM aheineman(a)godaddy.com<mailto:aheineman@godaddy.com> <aheineman(a)godaddy.com<mailto:aheineman@godaddy.com>> wrote: Dear Andrew. RrSG membership has been discussing the price change notification issue at length as it applies to the .DESIGN, .INK, and .WIKI amendments. Through this discussion a number of additional issues have been identified. May I request another week to get back to you with a consolidated RrSG response? I admit that this is new territory for me with respect to process. Any guidance from ICANN staff would be greatly appreciated. From: Andrew Merriam <andrew(a)toplevel.design<mailto:andrew@toplevel.design>> Sent: Thursday, January 28, 2021 3:11 PM To: Ashley Heineman <aheineman(a)godaddy.com<mailto:aheineman@godaddy.com>> Cc: Zoe Bonython <secretariat(a)icannregistrars.org<mailto:secretariat@icannregistrars.org>>; registrars(a)icann.org<mailto:registrars@icann.org>; Jeanne Gregg <jeanne.gregg(a)icann.org<mailto:jeanne.gregg@icann.org>>; Robert Gomez <robert.gomez(a)icann.org<mailto:robert.gomez@icann.org>>; Andee Hill <andee.hill(a)icann.org<mailto:andee.hill@icann.org>>; Andrew Dickson <andrew.dickson(a)icann.org<mailto:andrew.dickson@icann.org>> Subject: Re: [registrars] [Ext] RRA Amendment Notification for .DESIGN, .INK, & .WIKI [ ref:_00D616tJk._5004MgDdR8:ref ] Notice: This email is from an external sender. Yes, please do. I didn't want to respond to the full group as I didn't know if this communication was in bounds of the imagined ICANN process, let alone the fact that it's likely a giant group :) On Thu, Jan 28, 2021 at 12:08 PM aheineman(a)godaddy.com<mailto:aheineman@godaddy.com> <aheineman(a)godaddy.com<mailto:aheineman@godaddy.com>> wrote: Andrew, may I share your email with the RrSG so that we may respond? I assure you this was not an arbitrary issue and is in fact a point we have taken issue with for multiple past RRA amendments. The fact that this was not raised for .gay was an oversight I am pretty sure, but would need to check with membership. Get Outlook for Android [aka.ms]<https://urldefense.com/v3/__https:/aka.ms/ghei36__;!!PtGJab4!qFW2WP4tn5BnYk…> ________________________________ From: Andrew Merriam <andrew(a)toplevel.design<mailto:andrew@toplevel.design>> Sent: Thursday, January 28, 2021 3:02:57 PM To: Ashley Heineman <aheineman(a)godaddy.com<mailto:aheineman@godaddy.com>> Cc: Zoe Bonython <secretariat(a)icannregistrars.org<mailto:secretariat@icannregistrars.org>>; registrars(a)icann.org<mailto:registrars@icann.org> <registrars(a)icann.org<mailto:registrars@icann.org>>; Jeanne Gregg <jeanne.gregg(a)icann.org<mailto:jeanne.gregg@icann.org>>; Robert Gomez <robert.gomez(a)icann.org<mailto:robert.gomez@icann.org>>; Andee Hill <andee.hill(a)icann.org<mailto:andee.hill@icann.org>>; Andrew Dickson <andrew.dickson(a)icann.org<mailto:andrew.dickson@icann.org>> Subject: Re: [registrars] [Ext] RRA Amendment Notification for .DESIGN, .INK, & .WIKI [ ref:_00D616tJk._5004MgDdR8:ref ] Notice: This email is from an external sender. Hello all, I have removed the full group and left Ashley, Zoe, and those from ICANN org. I believe I am cc'd as a courtesy, as the Registry representative, but thought to respond to this point to help with any further consultation. The point for .ink specifically seems arbitrary. This redline language matches our 2020 .gay RRA which was accepted and signed by GoDaddy and the vast majority of Registrar Stakeholder Group members. The current language leaves in place the requirements as defined by our RA with ICANN [icann.org]<https://urldefense.com/v3/__https:/www.icann.org/sites/default/files/tlds/i…> (2.1), which I believe is a minimum of 30 days. So, this exact same language has already been accepted for our other TLD. I look forward to remediating any further issues efficiently. Thanks, have good days, A On Thu, Jan 28, 2021 at 7:07 AM aheineman(a)godaddy.com<mailto:aheineman@godaddy.com> <aheineman(a)godaddy.com<mailto:aheineman@godaddy.com>> wrote: With respect to .INK – under section 7, the requirement for 180 day notice for price increases and decreases should be maintained. Let me know if you have any questions. Thanks. ##- Please type your reply above this line -## You are registered as a CC on this request (369075). Reply to this email to add a comment to the request. This email is a service from Ascio Fulfillment. Delivered by Zendesk [zendesk.com]<https://urldefense.com/v3/__https:/www.zendesk.com/support/?utm_campaign=te…> [V02L6Y-KP99] -- Andrew Merriam (he / him) Vice President of Business Development Top Level Design, LLC toplevel.design [toplevel.design]<https://urldefense.com/v3/__http:/toplevel.design/__;!!PtGJab4!qFW2WP4tn5Bn…> -- Andrew Merriam (he / him) Vice President of Business Development Top Level Design, LLC toplevel.design [toplevel.design]<https://urldefense.com/v3/__http:/toplevel.design/__;!!PtGJab4!qFW2WP4tn5Bn…> -- Andrew Merriam (he / him) Vice President of Business Development Top Level Design, LLC toplevel.design [toplevel.design]<https://urldefense.com/v3/__http:/toplevel.design/__;!!PtGJab4!qFW2WP4tn5Bn…> -- Andrew Merriam (he / him) Vice President of Business Development Top Level Design, LLC toplevel.design [toplevel.design]<https://urldefense.com/v3/__http:/toplevel.design/__;!!PtGJab4!qFW2WP4tn5Bn…> -- Andrew Merriam (he / him) Vice President of Business Development Top Level Design, LLC toplevel.design [toplevel.design]<https://urldefense.com/v3/__http:/toplevel.design/__;!!PtGJab4!qFW2WP4tn5Bn…> -- Andrew Merriam (he / him) Vice President of Business Development Top Level Design, LLC toplevel.design [toplevel.design]<https://urldefense.com/v3/__http:/toplevel.design/__;!!PtGJab4!qFW2WP4tn5Bn…>

2 1