June 2017 - Gnso-impl-thickwhois-rt

FW: ICANN59 Feedback Survey
by Dennis Chang 29 Jun '17

29 Jun '17

Dear friends, Passing on the request for feedback to make our meetings better. Thanks Dennis Chang From: Josh Baulch <josh.baulch(a)icann.org> Date: Thursday, June 29, 2017 at 9:37 AM To: Josh Baulch <josh.baulch(a)icann.org> Subject: ICANN59 Feedback Survey Before you go, fill out the #ICANN59<https://twitter.com/hashtag/ICANN59?src=hash> survey! It only takes a few minutes >> https://eventmobi.com/icann59/surveys/196660/102296 Please pass this on to your groups to assist us in improving our community experience at ICANN meetings! Thank you! - - Josh Baulch Sr. Manager, Meeting Planning Operations Internet Corporation for Assigned Names and Numbers (ICANN) Direct Line: +1 310 578 8938 Mobile: +1 509 312 9711 Email: josh.baulch(a)icann.org<mailto:josh.baulch@icann.org> www.icann.org

1 0

Re: [Gnso-impl-thickwhois-rt] [Ext] Re: IRT meeting at ICANN59
by Dennis Chang 28 Jun '17

28 Jun '17

Hello Frédéric, All IRT members should have received an meeting invite with remote participation information by now. If you haven’t please reach out to Michelle. As always, the IRT meeting are recorded and posted on the IRT wiki. https://community.icann.org/display/TWCPI/Thick+Whois+IRT+Meetings%3A+Agend… Thanks Dennis Chang From: Frédéric Guillemaut <fg(a)safebrands.com> Date: Monday, June 26, 2017 at 11:16 AM To: Dennis Chang <dennis.chang(a)icann.org> Cc: Theo Geurts <gtheo(a)xs4all.nl>, Roger D Carney <rcarney(a)godaddy.com>, "gnso-impl-thickwhois-rt(a)icann.org" <gnso-impl-thickwhois-rt(a)icann.org> Subject: Re: [Gnso-impl-thickwhois-rt] [Ext] Re: IRT meeting at ICANN59? Hello all I won't attend the meeting in Africa. But I hope you can discuss this and have a good meeting. Best. Frederic Guillemaut COO SafeBrands fg(a)safebrands.com<mailto:fg@safebrands.com> Le 25 juin 2017 à 10:47, Dennis Chang <dennis.chang(a)icann.org<mailto:dennis.chang@icann.org>> a écrit : Agreed and will try. I say try because I can’t guarantee a conference room but will try. Looking at the meeting schedule, it looks like Wed. 1500-1600 would be a good time with minimum conflicts and probable conference room. Let me know right away if this time slot isn’t possible for you. Thanks Dennis Chang From: Theo Geurts <gtheo(a)xs4all.nl<mailto:gtheo@xs4all.nl>> Date: Sunday, June 25, 2017 at 10:06 AM To: Roger D Carney <rcarney(a)godaddy.com<mailto:rcarney@godaddy.com>>, Dennis Chang <dennis.chang(a)icann.org<mailto:dennis.chang@icann.org>>, "gnso-impl-thickwhois-rt(a)icann.org<mailto:gnso-impl-thickwhois-rt@icann.org>" <gnso-impl-thickwhois-rt(a)icann.org<mailto:gnso-impl-thickwhois-rt@icann.org>> Subject: [Ext] Re: [Gnso-impl-thickwhois-rt] IRT meeting at ICANN59? I somewhat disagree there Roger, in my opinion we are dealing with a larger issue here. But I do agree that timeline wise it is not bad to discuss this within an IRT setting, if only for practical reasons for contrracted parties. Dennis, can you book us a room, Wednesday or Thursday would be good, as the schedule is pretty packed the first two days. Best regards, Theo Op 24-6-2017 om 22:32 schreef Roger D Carney: Good Evening, These contract issues may be beyond the IRT scope but the timeline changes I think are well within scope and need to be discussed. Thanks Roger -------- Original message -------- From: Theo Geurts <gtheo(a)xs4all.nl><mailto:gtheo@xs4all.nl> Date: 6/24/17 9:12 PM (GMT+00:00) To: Roger D Carney <rcarney(a)godaddy.com><mailto:rcarney@godaddy.com>, Dennis Chang <dennis.chang(a)icann.org><mailto:dennis.chang@icann.org>, gnso-impl-thickwhois-rt(a)icann.org<mailto:gnso-impl-thickwhois-rt@icann.org> Subject: Re: [Gnso-impl-thickwhois-rt] IRT meeting at ICANN59? Roger, Dennis, I understand why we would want to discuss this as an IRT. We, the IRT folks put in a lot of blood and sweat and tears into this, I know I did. But, this has become a contractual issue now and outside the scope of the IRT address. Best regards, Theo Geurts Op 24-6-2017 om 21:13 schreef Roger D Carney: Good Evening, I think that it would be good to meet if we can. Thanks Roger -------- Original message -------- From: Dennis Chang <dennis.chang(a)icann.org><mailto:dennis.chang@icann.org> Date: 6/24/17 7:48 PM (GMT+00:00) To: gnso-impl-thickwhois-rt(a)icann.org<mailto:gnso-impl-thickwhois-rt@icann.org> Subject: [Gnso-impl-thickwhois-rt] IRT meeting at ICANN59? Dear IRT, Please let me know if you’d like an IRT meeting during ICANN59 to discuss this subject or others. I can ask for a conference room for those of us to come together and provide remote access if we need it. Thanks Dennis Chang From: <gnso-impl-thickwhois-rt-bounces(a)icann.org><mailto:gnso-impl-thickwhois-rt-bounces@icann.org> on behalf of Dennis Chang <dennis.chang(a)icann.org><mailto:dennis.chang@icann.org> Date: Saturday, June 24, 2017 at 6:08 PM To: "gnso-impl-thickwhois-rt(a)icann.org"<mailto:gnso-impl-thickwhois-rt@icann.org> <gnso-impl-thickwhois-rt(a)icann.org><mailto:gnso-impl-thickwhois-rt@icann.org> Subject: [Gnso-impl-thickwhois-rt] FW: Verisign request to extend Thick Whois Implementation Date Dear Thick IRT, Forwarding an email from Karla regarding Versign’s request for extension of the 1 August 2017. Thanks Dennis Chang From: Karla Hakansson <karla.hakansson(a)icann.org><mailto:karla.hakansson@icann.org> Date: Saturday, June 24, 2017 at 4:13 PM To: Dennis Chang <dennis.chang(a)icann.org><mailto:dennis.chang@icann.org> Cc: Cyrus Namazi <cyrus.namazi(a)icann.org><mailto:cyrus.namazi@icann.org> Subject: Verisign request to extend Thick Whois Implementation Date Hello Dennis, Please communicate the following update to the Thick Whois IRT: In the process of implementing the Thick Whois Policy for .com and .net, Verisign proposed certain Amendments to the COM/NET Registry Registrar Agreement (RRA) to fulfill their obligation to begin accepting Thick Whois data from the registrars beginning 1 August 2017. Per the published process[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_syste…>, ICANN forwarded the proposed RRA Amendments to the Registrar Stakeholder Group (RrSG) on 29 March 2017 to review and provide comments. On 21 April 2017 the RrSG formally objected to the proposed Amendment stating: “…the .com/.net amendments have raised serious questions in the RrSG around how we'll operate and interact with .com/.net under the upcoming European GDPR, and we feel we need clarity on these issues before the amendments can be accepted. Indeed, the RrSG is now looking towards the impact of the GDPR on the 1000s of registries we regularly work with, and it's clear that we need to ensure we have more clarity and understanding, as well as a solution for data handling that will work across ALL registries.” Following this communication, the RrSG submitted a letter to ICANN and Verisign on 4 May 2017 requesting Verisign to modify its proposed Amendment, and for ICANN to create a data protection policy in support of the RAA for both registries and registrars. Since the 4 May 2017 communication ICANN has facilitated multiple discussions between Verisign and the RrSG in an attempt to resolve the outstanding issues with the RRA Amendments. The goal of those discussions has been to resolve the concerns about the proposed RRA Amendments so they can be in place by 1 July 2017. This deadline is imposed by Verisign to provide registrars with a thirty-day period in order for changes to the RRA to become effective before Verisign begins accepting Thick Whois data in their production environment. As of 21 June 2017, the RRA Amendment has not been accepted by the RrSG. ICANN strives for consensus whenever possible before approving RRA amendments, and without further discussions, is not prepared to approve an RRA amendment that the RrSG has rejected. On 20 June 2017 Verisign formally submitted a request to ICANN[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> to extend the 1 August 2017 Thick Whois implementation enforcement date by at least 120 days, or 29 November 2017. The extension request, currently under review, is not expected to compromise the 1 May 2018 Thick Whois deadline for all new .COM and .NET registrations or the 1 February 2019 deadline for the completion of the Thick Whois transition. Please let me know if you have any questions. Karla Hakansson Director, Registry Services ICANN – Global Domains Division (e) Karla.hakansson(a)icann.org<mailto:Karla.hakansson@icann.org> (t) +1.310.699.5834 (s) karlahakansson 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094-2536 www.icann.org[icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.icann.org_&d=DwMD-g…> _______________________________________________ Gnso-impl-thickwhois-rt mailing list Gnso-impl-thickwhois-rt(a)icann.org<mailto:Gnso-impl-thickwhois-rt@icann.org> https://mm.icann.org/mailman/listinfo/gnso-impl-thickwhois-rt _______________________________________________ Gnso-impl-thickwhois-rt mailing list Gnso-impl-thickwhois-rt(a)icann.org<mailto:Gnso-impl-thickwhois-rt@icann.org> https://mm.icann.org/mailman/listinfo/gnso-impl-thickwhois-rt

1 0

Re: [Gnso-impl-thickwhois-rt] [Ext] Re: IRT meeting at ICANN59
by Dennis Chang 28 Jun '17

28 Jun '17

Yes. I plan to use our normal IRT AC room. Meeting invitation will be sent when a room is secured. Audio could be an issue and we may have to improvise. Worst case, we’ll huddle around my phone. Thanks Dennis Chang From: "Metalitz, Steven" <met(a)msk.com> Date: Sunday, June 25, 2017 at 4:30 PM To: Dennis Chang <dennis.chang(a)icann.org>, 'Theo Geurts' <gtheo(a)xs4all.nl>, 'Roger D Carney' <rcarney(a)godaddy.com>, "'gnso-impl-thickwhois-rt(a)icann.org'" <gnso-impl-thickwhois-rt(a)icann.org> Subject: RE: [Gnso-impl-thickwhois-rt] [Ext] Re: IRT meeting at ICANN59? Will remote participation be available? Sent with Good (www.good.com) -----Original Message----- From: Dennis Chang [dennis.chang(a)icann.org<mailto:dennis.chang@icann.org>] Sent: Sunday, June 25, 2017 01:47 AM Pacific Standard Time To: Theo Geurts; Roger D Carney; gnso-impl-thickwhois-rt(a)icann.org Subject: Re: [Gnso-impl-thickwhois-rt] [Ext] Re: IRT meeting at ICANN59? Agreed and will try. I say try because I can’t guarantee a conference room but will try. Looking at the meeting schedule, it looks like Wed. 1500-1600 would be a good time with minimum conflicts and probable conference room. Let me know right away if this time slot isn’t possible for you. Thanks Dennis Chang From: Theo Geurts <gtheo(a)xs4all.nl> Date: Sunday, June 25, 2017 at 10:06 AM To: Roger D Carney <rcarney(a)godaddy.com>, Dennis Chang <dennis.chang(a)icann.org>, "gnso-impl-thickwhois-rt(a)icann.org" <gnso-impl-thickwhois-rt(a)icann.org> Subject: [Ext] Re: [Gnso-impl-thickwhois-rt] IRT meeting at ICANN59? I somewhat disagree there Roger, in my opinion we are dealing with a larger issue here. But I do agree that timeline wise it is not bad to discuss this within an IRT setting, if only for practical reasons for contrracted parties. Dennis, can you book us a room, Wednesday or Thursday would be good, as the schedule is pretty packed the first two days. Best regards, Theo Op 24-6-2017 om 22:32 schreef Roger D Carney: Good Evening, These contract issues may be beyond the IRT scope but the timeline changes I think are well within scope and need to be discussed. Thanks Roger -------- Original message -------- From: Theo Geurts <gtheo(a)xs4all.nl><mailto:gtheo@xs4all.nl> Date: 6/24/17 9:12 PM (GMT+00:00) To: Roger D Carney <rcarney(a)godaddy.com><mailto:rcarney@godaddy.com>, Dennis Chang <dennis.chang(a)icann.org><mailto:dennis.chang@icann.org>, gnso-impl-thickwhois-rt(a)icann.org<mailto:gnso-impl-thickwhois-rt@icann.org> Subject: Re: [Gnso-impl-thickwhois-rt] IRT meeting at ICANN59? Roger, Dennis, I understand why we would want to discuss this as an IRT. We, the IRT folks put in a lot of blood and sweat and tears into this, I know I did. But, this has become a contractual issue now and outside the scope of the IRT address. Best regards, Theo Geurts Op 24-6-2017 om 21:13 schreef Roger D Carney: Good Evening, I think that it would be good to meet if we can. Thanks Roger -------- Original message -------- From: Dennis Chang <dennis.chang(a)icann.org><mailto:dennis.chang@icann.org> Date: 6/24/17 7:48 PM (GMT+00:00) To: gnso-impl-thickwhois-rt(a)icann.org<mailto:gnso-impl-thickwhois-rt@icann.org> Subject: [Gnso-impl-thickwhois-rt] IRT meeting at ICANN59? Dear IRT, Please let me know if you’d like an IRT meeting during ICANN59 to discuss this subject or others. I can ask for a conference room for those of us to come together and provide remote access if we need it. Thanks Dennis Chang From: <gnso-impl-thickwhois-rt-bounces(a)icann.org><mailto:gnso-impl-thickwhois-rt-bounces@icann.org> on behalf of Dennis Chang <dennis.chang(a)icann.org><mailto:dennis.chang@icann.org> Date: Saturday, June 24, 2017 at 6:08 PM To: "gnso-impl-thickwhois-rt(a)icann.org"<mailto:gnso-impl-thickwhois-rt@icann.org> <gnso-impl-thickwhois-rt(a)icann.org><mailto:gnso-impl-thickwhois-rt@icann.org> Subject: [Gnso-impl-thickwhois-rt] FW: Verisign request to extend Thick Whois Implementation Date Dear Thick IRT, Forwarding an email from Karla regarding Versign’s request for extension of the 1 August 2017. Thanks Dennis Chang From: Karla Hakansson <karla.hakansson(a)icann.org><mailto:karla.hakansson@icann.org> Date: Saturday, June 24, 2017 at 4:13 PM To: Dennis Chang <dennis.chang(a)icann.org><mailto:dennis.chang@icann.org> Cc: Cyrus Namazi <cyrus.namazi(a)icann.org><mailto:cyrus.namazi@icann.org> Subject: Verisign request to extend Thick Whois Implementation Date Hello Dennis, Please communicate the following update to the Thick Whois IRT: In the process of implementing the Thick Whois Policy for .com and .net, Verisign proposed certain Amendments to the COM/NET Registry Registrar Agreement (RRA) to fulfill their obligation to begin accepting Thick Whois data from the registrars beginning 1 August 2017. Per the published process[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_syste…>, ICANN forwarded the proposed RRA Amendments to the Registrar Stakeholder Group (RrSG) on 29 March 2017 to review and provide comments. On 21 April 2017 the RrSG formally objected to the proposed Amendment stating: “…the .com/.net amendments have raised serious questions in the RrSG around how we'll operate and interact with .com/.net under the upcoming European GDPR, and we feel we need clarity on these issues before the amendments can be accepted. Indeed, the RrSG is now looking towards the impact of the GDPR on the 1000s of registries we regularly work with, and it's clear that we need to ensure we have more clarity and understanding, as well as a solution for data handling that will work across ALL registries.” Following this communication, the RrSG submitted a letter to ICANN and Verisign on 4 May 2017 requesting Verisign to modify its proposed Amendment, and for ICANN to create a data protection policy in support of the RAA for both registries and registrars. Since the 4 May 2017 communication ICANN has facilitated multiple discussions between Verisign and the RrSG in an attempt to resolve the outstanding issues with the RRA Amendments. The goal of those discussions has been to resolve the concerns about the proposed RRA Amendments so they can be in place by 1 July 2017. This deadline is imposed by Verisign to provide registrars with a thirty-day period in order for changes to the RRA to become effective before Verisign begins accepting Thick Whois data in their production environment. As of 21 June 2017, the RRA Amendment has not been accepted by the RrSG. ICANN strives for consensus whenever possible before approving RRA amendments, and without further discussions, is not prepared to approve an RRA amendment that the RrSG has rejected. On 20 June 2017 Verisign formally submitted a request to ICANN[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> to extend the 1 August 2017 Thick Whois implementation enforcement date by at least 120 days, or 29 November 2017. The extension request, currently under review, is not expected to compromise the 1 May 2018 Thick Whois deadline for all new .COM and .NET registrations or the 1 February 2019 deadline for the completion of the Thick Whois transition. Please let me know if you have any questions. Karla Hakansson Director, Registry Services ICANN – Global Domains Division (e) Karla.hakansson(a)icann.org<mailto:Karla.hakansson@icann.org> (t) +1.310.699.5834 (s) karlahakansson 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094-2536 www.icann.org[icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.icann.org_&d=DwMD-g…> _______________________________________________ Gnso-impl-thickwhois-rt mailing list Gnso-impl-thickwhois-rt(a)icann.org<mailto:Gnso-impl-thickwhois-rt@icann.org> https://mm.icann.org/mailman/listinfo/gnso-impl-thickwhois-rt

2 2

IRT meeting at ICANN59?
by Dennis Chang 25 Jun '17

25 Jun '17

Dear IRT, Please let me know if you’d like an IRT meeting during ICANN59 to discuss this subject or others. I can ask for a conference room for those of us to come together and provide remote access if we need it. Thanks Dennis Chang From: <gnso-impl-thickwhois-rt-bounces(a)icann.org> on behalf of Dennis Chang <dennis.chang(a)icann.org> Date: Saturday, June 24, 2017 at 6:08 PM To: "gnso-impl-thickwhois-rt(a)icann.org" <gnso-impl-thickwhois-rt(a)icann.org> Subject: [Gnso-impl-thickwhois-rt] FW: Verisign request to extend Thick Whois Implementation Date Dear Thick IRT, Forwarding an email from Karla regarding Versign’s request for extension of the 1 August 2017. Thanks Dennis Chang From: Karla Hakansson <karla.hakansson(a)icann.org> Date: Saturday, June 24, 2017 at 4:13 PM To: Dennis Chang <dennis.chang(a)icann.org> Cc: Cyrus Namazi <cyrus.namazi(a)icann.org> Subject: Verisign request to extend Thick Whois Implementation Date Hello Dennis, Please communicate the following update to the Thick Whois IRT: In the process of implementing the Thick Whois Policy for .com and .net, Verisign proposed certain Amendments to the COM/NET Registry Registrar Agreement (RRA) to fulfill their obligation to begin accepting Thick Whois data from the registrars beginning 1 August 2017. Per the published process<https://www.icann.org/en/system/files/files/rra-amendment-procedure-25aug11…>, ICANN forwarded the proposed RRA Amendments to the Registrar Stakeholder Group (RrSG) on 29 March 2017 to review and provide comments. On 21 April 2017 the RrSG formally objected to the proposed Amendment stating: “…the .com/.net amendments have raised serious questions in the RrSG around how we'll operate and interact with .com/.net under the upcoming European GDPR, and we feel we need clarity on these issues before the amendments can be accepted. Indeed, the RrSG is now looking towards the impact of the GDPR on the 1000s of registries we regularly work with, and it's clear that we need to ensure we have more clarity and understanding, as well as a solution for data handling that will work across ALL registries.” Following this communication, the RrSG submitted a letter to ICANN and Verisign on 4 May 2017 requesting Verisign to modify its proposed Amendment, and for ICANN to create a data protection policy in support of the RAA for both registries and registrars. Since the 4 May 2017 communication ICANN has facilitated multiple discussions between Verisign and the RrSG in an attempt to resolve the outstanding issues with the RRA Amendments. The goal of those discussions has been to resolve the concerns about the proposed RRA Amendments so they can be in place by 1 July 2017. This deadline is imposed by Verisign to provide registrars with a thirty-day period in order for changes to the RRA to become effective before Verisign begins accepting Thick Whois data in their production environment. As of 21 June 2017, the RRA Amendment has not been accepted by the RrSG. ICANN strives for consensus whenever possible before approving RRA amendments, and without further discussions, is not prepared to approve an RRA amendment that the RrSG has rejected. On 20 June 2017 Verisign formally submitted a request to ICANN<https://www.icann.org/resources/pages/correspondence> to extend the 1 August 2017 Thick Whois implementation enforcement date by at least 120 days, or 29 November 2017. The extension request, currently under review, is not expected to compromise the 1 May 2018 Thick Whois deadline for all new .COM and .NET registrations or the 1 February 2019 deadline for the completion of the Thick Whois transition. Please let me know if you have any questions. Karla Hakansson Director, Registry Services ICANN – Global Domains Division (e) Karla.hakansson(a)icann.org<mailto:Karla.hakansson@icann.org> (t) +1.310.699.5834 (s) karlahakansson 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094-2536 www.icann.org<http://www.icann.org/>

4 6

FW: Verisign request to extend Thick Whois Implementation Date
by Dennis Chang 24 Jun '17

24 Jun '17

Dear Thick IRT, Forwarding an email from Karla regarding Versign’s request for extension of the 1 August 2017. Thanks Dennis Chang From: Karla Hakansson <karla.hakansson(a)icann.org> Date: Saturday, June 24, 2017 at 4:13 PM To: Dennis Chang <dennis.chang(a)icann.org> Cc: Cyrus Namazi <cyrus.namazi(a)icann.org> Subject: Verisign request to extend Thick Whois Implementation Date Hello Dennis, Please communicate the following update to the Thick Whois IRT: In the process of implementing the Thick Whois Policy for .com and .net, Verisign proposed certain Amendments to the COM/NET Registry Registrar Agreement (RRA) to fulfill their obligation to begin accepting Thick Whois data from the registrars beginning 1 August 2017. Per the published process<https://www.icann.org/en/system/files/files/rra-amendment-procedure-25aug11…>, ICANN forwarded the proposed RRA Amendments to the Registrar Stakeholder Group (RrSG) on 29 March 2017 to review and provide comments. On 21 April 2017 the RrSG formally objected to the proposed Amendment stating: “…the .com/.net amendments have raised serious questions in the RrSG around how we'll operate and interact with .com/.net under the upcoming European GDPR, and we feel we need clarity on these issues before the amendments can be accepted. Indeed, the RrSG is now looking towards the impact of the GDPR on the 1000s of registries we regularly work with, and it's clear that we need to ensure we have more clarity and understanding, as well as a solution for data handling that will work across ALL registries.” Following this communication, the RrSG submitted a letter to ICANN and Verisign on 4 May 2017 requesting Verisign to modify its proposed Amendment, and for ICANN to create a data protection policy in support of the RAA for both registries and registrars. Since the 4 May 2017 communication ICANN has facilitated multiple discussions between Verisign and the RrSG in an attempt to resolve the outstanding issues with the RRA Amendments. The goal of those discussions has been to resolve the concerns about the proposed RRA Amendments so they can be in place by 1 July 2017. This deadline is imposed by Verisign to provide registrars with a thirty-day period in order for changes to the RRA to become effective before Verisign begins accepting Thick Whois data in their production environment. As of 21 June 2017, the RRA Amendment has not been accepted by the RrSG. ICANN strives for consensus whenever possible before approving RRA amendments, and without further discussions, is not prepared to approve an RRA amendment that the RrSG has rejected. On 20 June 2017 Verisign formally submitted a request to ICANN<https://www.icann.org/resources/pages/correspondence> to extend the 1 August 2017 Thick Whois implementation enforcement date by at least 120 days, or 29 November 2017. The extension request, currently under review, is not expected to compromise the 1 May 2018 Thick Whois deadline for all new .COM and .NET registrations or the 1 February 2019 deadline for the completion of the Thick Whois transition. Please let me know if you have any questions. Karla Hakansson Director, Registry Services ICANN – Global Domains Division (e) Karla.hakansson(a)icann.org<mailto:Karla.hakansson@icann.org> (t) +1.310.699.5834 (s) karlahakansson 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094-2536 www.icann.org<http://www.icann.org/>

1 0