February 2014 - Gnso-impl-irtpc-rt

Meeting invitation: IRTP C IRT call on 06 March 2014
by Caitlin Tubergen Feb. 26, 2014

Feb. 26, 2014

Dear all, The next Inter-Registrar Transfer Policy (IRTP) Part C Implementation Review Team teleconference is scheduled for Thursday 06 March 2014 at 16:00 UTC. 08:00 PDT, 11:00 EDT, 16:00 London, 17:00 CET, 03:00 (+1 day) Sydney Adigo Conference ID: 28462745 Adigo numbers: http://adigo.com/icann/ Adobe Connect with audio enabled: http://icann.adobeconnect.com/irtppartc/ Please let me know if you have any questions. Kind regards, Caitlin Tubergen Registrar Relations and Contracts Manager ICANN

2 1

Standing Meeting Time for IRTP C Implementation Review Team
by Caitlin Tubergen Feb. 24, 2014

Feb. 24, 2014

Greetings IRTP C IRT: ICANN Staff is currently working together to finalize a proposed implementation plan which we would like to share with you on our next call. Going forward, I am estimating that we will hold calls every 2-3 weeks (if needed) at a standing time. I have proposed a few times in the below Doodle Poll to see which "standing time" works the best for everyone on the IRT. http://doodle.com/ukuy47shzt8zuxup Please respond to the Doodle Poll at your earliest convenience, and I will revert to you with further information when we have agreed on a standing meeting time. Kind regards, Caitlin Tubergen Registrar Relations and Contracts Manager ICANN

1 0

RE: A possible fix?
by Michele Neylon - Blacknight Feb. 12, 2014

Feb. 12, 2014

Sorry I missed the call James: 1 - which registrar? Gaining? Losing? Both? 2 - um .. hangon, unless I'm missing something that would also prevent a nameserver update, wouldn't it? (Bear in mind I'm quite tired this evening, so I could be wrong) Regards Michele -- Mr Michele Neylon Blacknight Solutions Hosting & Colocation, Domains http://www.blacknight.co/ http://blog.blacknight.com/ http://www.technology.ie Intl. +353 (0) 59 9183072 Locall: 1850 929 929 Direct Dial: +353 (0)59 9183090 Fax. +353 (0) 1 4811 763 Twitter: http://twitter.com/mneylon ------------------------------- Blacknight Internet Solutions Ltd, Unit 12A,Barrowside Business Park,Sleaty Road,Graiguecullen,Carlow,Ireland Company No.: 370845 From: owner-gnso-impl-irtpc-rt(a)icann.org [mailto:owner-gnso-impl-irtpc-rt@icann.org] On Behalf Of James M. Bladel Sent: Wednesday, February 12, 2014 10:44 PM To: gnso-impl-irtpc-rt(a)icann.org Subject: [gnso-impl-irtpc-rt] A possible fix? Hi folks. Hope no one was discouraged following todays call. These things are very difficult (if they weren't anyone could do them)...but not impossible! So thinking a bit more, I believe we can address some of these issues by requiring two practices: (1) Registrars must take two WHOIS "snapshots": One to obtain the FOA, and one at Transfer execution. (2) Registries must "lock" (ServerUpdateProhibited, ServerTransferProhibited,ServerDeleteProhibited) on all names known to be subject to a UDRP or TDRP. Reasoning: By comparing the WHOIS record at both occasions, the Gaining Registrar can spot any differences in Registrant data or Domain Status. This will provide the necessary visibility to invalidate the FOA and re-authorize the transfer. Thoughts? J.

3 4

RE: A possible fix?
by Michele Neylon - Blacknight Feb. 12, 2014

Feb. 12, 2014

One could argue that with the upcoming changes to whois and a switch to thick for all that this might be better handled by the registry .. Or am I missing something? -- Mr Michele Neylon Blacknight Solutions Hosting & Colocation, Domains http://www.blacknight.co/ http://blog.blacknight.com/ http://www.technology.ie Intl. +353 (0) 59 9183072 Locall: 1850 929 929 Direct Dial: +353 (0)59 9183090 Fax. +353 (0) 1 4811 763 Twitter: http://twitter.com/mneylon ------------------------------- Blacknight Internet Solutions Ltd, Unit 12A,Barrowside Business Park,Sleaty Road,Graiguecullen,Carlow,Ireland Company No.: 370845 From: owner-gnso-impl-irtpc-rt(a)icann.org [mailto:owner-gnso-impl-irtpc-rt@icann.org] On Behalf Of James M. Bladel Sent: Wednesday, February 12, 2014 11:03 PM To: Batteiger, Simonetta; Michele Neylon - Blacknight; gnso-impl-irtpc-rt(a)icann.org Subject: [gnso-impl-irtpc-rt] Re: A possible fix? Hi Simonetta. The new policy lays out several situations under which an FOA would no longer be valid. T he problem discussed during today's call was: How will the (would be) Gaining Registrar know that the FOA they are holding is invalid? J. From: <Batteiger>, Simonetta <simonetta(a)sedo.com<mailto:simonetta@sedo.com>> Date: Wednesday, February 12, 2014 at 16:59 To: Michele Neylon - Blacknight <michele(a)blacknight.com<mailto:michele@blacknight.com>>, James Bladel <jbladel(a)godaddy.com<mailto:jbladel@godaddy.com>>, "gnso-impl-irtpc-rt(a)icann.org<mailto:gnso-impl-irtpc-rt@icann.org>" <gnso-impl-irtpc-rt(a)icann.org<mailto:gnso-impl-irtpc-rt@icann.org>> Subject: RE: A possible fix? Also sorry for having missed today's call. I'm not entirely sure which problem you're trying to solve with the ideas below. Is this about verifying if an FOA is still valid? Simonetta From: owner-gnso-impl-irtpc-rt(a)icann.org<mailto:owner-gnso-impl-irtpc-rt@icann.org> [mailto:owner-gnso-impl-irtpc-rt@icann.org] On Behalf Of Michele Neylon - Blacknight Sent: Wednesday, February 12, 2014 5:53 PM To: James M. Bladel; gnso-impl-irtpc-rt(a)icann.org<mailto:gnso-impl-irtpc-rt@icann.org> Subject: [gnso-impl-irtpc-rt] RE: A possible fix? Sorry I missed the call James: 1 - which registrar? Gaining? Losing? Both? 2 - um .. hangon, unless I'm missing something that would also prevent a nameserver update, wouldn't it? (Bear in mind I'm quite tired this evening, so I could be wrong) Regards Michele -- Mr Michele Neylon Blacknight Solutions Hosting & Colocation, Domains http://www.blacknight.co/ http://blog.blacknight.com/ http://www.technology.ie Intl. +353 (0) 59 9183072 Locall: 1850 929 929 Direct Dial: +353 (0)59 9183090 Fax. +353 (0) 1 4811 763 Twitter: http://twitter.com/mneylon ------------------------------- Blacknight Internet Solutions Ltd, Unit 12A,Barrowside Business Park,Sleaty Road,Graiguecullen,Carlow,Ireland Company No.: 370845 From:owner-gnso-impl-irtpc-rt@icann.org<mailto:owner-gnso-impl-irtpc-rt@icann.org> [mailto:owner-gnso-impl-irtpc-rt@icann.org] On Behalf Of James M. Bladel Sent: Wednesday, February 12, 2014 10:44 PM To: gnso-impl-irtpc-rt(a)icann.org<mailto:gnso-impl-irtpc-rt@icann.org> Subject: [gnso-impl-irtpc-rt] A possible fix? Hi folks. Hope no one was discouraged following todays call. These things are very difficult (if they weren't anyone could do them)...but not impossible! So thinking a bit more, I believe we can address some of these issues by requiring two practices: (1) Registrars must take two WHOIS "snapshots": One to obtain the FOA, and one at Transfer execution. (2) Registries must "lock" (ServerUpdateProhibited, ServerTransferProhibited,ServerDeleteProhibited) on all names known to be subject to a UDRP or TDRP. Reasoning: By comparing the WHOIS record at both occasions, the Gaining Registrar can spot any differences in Registrant data or Domain Status. This will provide the necessary visibility to invalidate the FOA and re-authorize the transfer. Thoughts? J.

1 0

A possible fix?
by James M. Bladel Feb. 12, 2014

Feb. 12, 2014

Hi folks. Hope no one was discouraged following todays call. These things are very difficult (if they weren't anyone could do them)...but not impossible! So thinking a bit more, I believe we can address some of these issues by requiring two practices: (1) Registrars must take two WHOIS "snapshots": One to obtain the FOA, and one at Transfer execution. (2) Registries must "lock" (ServerUpdateProhibited, ServerTransferProhibited,ServerDeleteProhibited) on all names known to be subject to a UDRP or TDRP. Reasoning: By comparing the WHOIS record at both occasions, the Gaining Registrar can spot any differences in Registrant data or Domain Status. This will provide the necessary visibility to invalidate the FOA and re-authorize the transfer. Thoughts? J.

1 0

Meeting Invitation Take 2: IRTP C IRT Call on Wednesday 12 February 2014
by Caitlin Tubergen Feb. 7, 2014

Feb. 7, 2014

Thank you for letting me know about your other call, Mikey and Chris. I apologize for the double-booking; the Advisory Group Call was not published on the GNSO calendar. I have moved the call back one hour to accommodate the Advisory Group for Digital Engagement group members. Please find the new details below: Name of teleconference: IRTP Part C Implementation Review Team Meeting Date: Wednesday 12th February 2014 Time: (in UTC): 1600 UTC Estimated duration: 60min Adigo code: 28462745 Adigo numbers: http://adigo.com/icann/ Adobe Connect: http://icann.adobeconnect.com/irtppartc/ Please take a look at the attached document, which incorporates IRTP C Rec. 2, before the call. Kind regards, Caitlin Tubergen Registrar Relations and Contracts Manager ICANN From: Chris Chaplow <chris(a)andaluciaws.com> Date: Tuesday, February 4, 2014 10:59 AM To: 'Mike O'Connor' <mike(a)haven2.com>, Caitlin Tubergen <caitlin.tubergen(a)icann.org> Cc: "gnso-impl-irtpc-rt(a)icann.org" <gnso-impl-irtpc-rt(a)icann.org> Subject: RE: [gnso-impl-irtpc-rt] Meeting invitation: IRTP C IRT Call on Wednesday 12 February 2014 That would help, if possible. I have same conflict as Mikey. Chris Chaplow Managing Director Andalucia.com S.L. Avenida del Carmen 9 Ed. Puertosol, Puerto Deportivo 1ª Planta, Oficina 30 Estepona, 29680 Malaga, Spain Tel: + (34) 952 897 865 Fax: + (34) 952 897 874 E-mail: chris(a)andalucia.com <mailto:chris@andalucia.com> Web: www.andalucia.com <http://www.andalucia.com/> Information about Andalucia, Spain. De: owner-gnso-impl-irtpc-rt(a)icann.org [mailto:owner-gnso-impl-irtpc-rt@icann.org] En nombre de Mike O'Connor Enviado el: martes, 04 de febrero de 2014 3:46 Para: Caitlin Tubergen CC: gnso-impl-irtpc-rt(a)icann.org Asunto: Re: [gnso-impl-irtpc-rt] Meeting invitation: IRTP C IRT Call on Wednesday 12 February 2014 argh. that¹s an exact conflict with the Advisory Group for Digital Engagement standing meeting. any chance of bumping this one forward or backward an hour? or forward or backward a week? mikey On Feb 3, 2014, at 5:57 PM, Caitlin Tubergen <caitlin.tubergen(a)icann.org> wrote: Greetings IRTP-C Implementation Review Team, The next IRTP C IRT Call will be held Wednesday 12 February 2014 at 1500 UTC. ICANN staff has begun work on IRTP C Recommendation 2 (time limiting of FOAs), and I have included a draft of the revised IRTP. We can discuss the revised IRTP on our next call. Please find details for the call below. Name of teleconference: IRTP Part C Implementation Review Team Meeting Date: Wednesday 12th February 2014 Time: (in UTC): 1500 UTC Adigo code: 28462745 Adigo numbers: http://adigo.com/icann/ Adobe Connect: http://icann.adobeconnect.com/irtppartc/ Thank you. Kind regards, Caitlin Tubergen Registrar Relations and Contracts Manager ICANN <Revised Inter-Registrar Transfer Policy IRTPC2.docx> PHONE: 651-647-6109, FAX: 866-280-2356, WEB: www.haven2.com <http://www.haven2.com> , HANDLE: OConnorStP (ID for Twitter, Facebook, LinkedIn, etc.)

3 2

Meeting invitation: IRTP C IRT Call on Wednesday 12 February 2014
by Caitlin Tubergen Feb. 4, 2014

Feb. 4, 2014

Greetings IRTP-C Implementation Review Team, The next IRTP C IRT Call will be held Wednesday 12 February 2014 at 1500 UTC. ICANN staff has begun work on IRTP C Recommendation 2 (time limiting of FOAs), and I have included a draft of the revised IRTP. We can discuss the revised IRTP on our next call. Please find details for the call below. Name of teleconference: IRTP Part C Implementation Review Team Meeting Date: Wednesday 12th February 2014 Time: (in UTC): 1500 UTC Adigo code: 28462745 Adigo numbers: http://adigo.com/icann/ Adobe Connect: http://icann.adobeconnect.com/irtppartc/ Thank you. Kind regards, Caitlin Tubergen Registrar Relations and Contracts Manager ICANN

2 1