March 2015 - Gnso-impl-irtpc-rt

question re: FOA expiration and COR
by Caitlin Tubergen March 17, 2015

March 17, 2015

Hi All, Thank you to everyone for your helpful feedback on the Transfer Policy. An IRT member flagged an issue with respect to section I.2.2.3(c), or the FOA expiration in conjunction with a Change of Registrant. The text of section I.2.2.3(c) is: "The FOA labeled "Initial Authorization for Registrar Transfer" shall expire under the following circumstances (c) a Change of Registrant is completed further to Section II.3." The issue is that it may be difficult for the gaining registrar to know if there has been a Change of Registrant. (1) One option would be to leave the text as is, which would require the Gaining Registrar to determine if certain contact information (registrant name, registrant org, registrant email) matches at the time the transfer is requested and the time the transfer is completed, by taking Whois snapshots, for example. The consistent Whois format of the 2013 RAA may mitigate this burden, since the data should be easier to parse. (2) Another option would be to remove this section, since Section II.3.3 requires a registrar to lock the domain name for 60 days after a Change of Registrant. Since the new language of I.2.2.3(a) provides that FOAs will expire after 60 days, this may make the requirement for an FOA to expire after a Change of Registrant unnecessary. I welcome everyone¹s thoughts, preferences, or other proposed solutions on this issue. I would appreciate any feedback by Tuesday, 17 March. Thank you! Kind regards, Caitlin

2 1

For your review: Change of Registrant/Transfer Policy - by Thursday 12 March
by Caitlin Tubergen March 12, 2015

March 12, 2015

Hi All, Thank you to everyone who participated in the call today. For those of you who were unable to attend, please find a link to the recording here: https://icann.adobeconnect.com/p4howkg3hce/ During the call, we discussed the outstanding issue from our last call, which was the issue of third party privacy/proxy providers and the potential challenge of transmitting the change of registrant credential to the underlying registrant. The members of the IRT that were on the call with okay with the proposed solution, which you will find in footnote 1. The P/P issue was the last outstanding issue to discuss before we post the draft policy for public comment. I have attached the draft policy for your final review. You will note that this is the hybrid ³Transfer Policy,² which will go out for public comment. The Transfer Policy has two sections: the IRTP in section I, and the Change of Registrant in section II. The hybrid policy was recommended by the WG. As you may remember, we had already worked through recommendation 2, the time limiting of FOAs, before we began discussing the Change of Registrant function. If you have any final questions or comments on the draft policy, please submit them to me by Thursday, 12 March. Thank you! Kind regards, Caitlin

4 5

Re: [gnso-impl-irtpc-rt] Reminder: Comments on Change of Registrant/Transfer Policy - due Thursday 12 March
by James M. Bladel March 11, 2015

March 11, 2015

Hi Caitlin and Team: First, I should apologize for missing the last 2 calls. I have had frequent schedule conflicts with this group, including an "off the grid" vacation last week. So please accept my apologies if these edits/comments appear to be "last minute". Next, I have noted a few changes to this draft (attached). Here are the highlights: * I think we should call Section II. "Inter-Registrant Transfer (Change of Registrant)" to keep it consistent with Section I. "Inter-Registrar Transfer". * Also, I think we should allow for non-material changes to Registrant information to include "equivalent" data, such as changing "Inc." to "Incorporated" or "Mike" to "Michael." I welcome ideas form the group on how to define this (or set some boundaries). * I'm still unclear whehter or not the Registrar has the right to refuse a Change of Registrant. What if there is some reason that the Registrar cannot legally serve or enter in to an agreement with the new Registrant? For example, in the US we cannot serve Registrants in Cuba or North Korea. Similarly, the US and several other nations have levied sanctions against individuals and organizations in Crimea. I would hate to see this policy used as a backdoor to compel Registrars to violate local law. Finally, there is the case where a Registrar has simply banned a particular Registrant from using their services. This right to refuse service should be maintained in the new policy. * Speaking of the Registration Agreement, I do not see where in the Draft Process (Sec. II(3)) where the Registrar presents this agreement to the new Registrant, and obtain their explicit acceptance. This is required buy the RAA (Sec. 3.7.7). Thanks- J. From: Caitlin Tubergen <caitlin.tubergen(a)icann.org<mailto:caitlin.tubergen@icann.org>> Date: Wednesday, March 11, 2015 at 13:40 To: "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: [gnso-impl-irtpc-rt] Reminder: Comments on Change of Registrant/Transfer Policy - due Thursday 12 March Hi All, Please note that the deadline for the Implementation Review Team to provide comments on the attached draft COR policy is tomorrow, Thursday, 12 March. If you are unable to provide feedback by that time, you are welcome to submit any comments during the public comment period. Thank you. Kind regards, Caitlin 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 Caitlin Tubergen Sent: Thursday, March 05, 2015 10:19 PM To: gnso-impl-irtpc-rt(a)icann.org<mailto:gnso-impl-irtpc-rt@icann.org>; Theo Geurts Subject: [gnso-impl-irtpc-rt] For your review: Change of Registrant/Transfer Policy - by Thursday 12 March Hi All, Thank you to everyone who participated in the call today. For those of you who were unable to attend, please find a link to the recording here: https://icann.adobeconnect.com/p4howkg3hce/ During the call, we discussed the outstanding issue from our last call, which was the issue of third party privacy/proxy providers and the potential challenge of transmitting the change of registrant credential to the underlying registrant. The members of the IRT that were on the call with okay with the proposed solution, which you will find in footnote 1. The P/P issue was the last outstanding issue to discuss before we post the draft policy for public comment. I have attached the draft policy for your final review. You will note that this is the hybrid "Transfer Policy," which will go out for public comment. The Transfer Policy has two sections: the IRTP in section I, and the Change of Registrant in section II. The hybrid policy was recommended by the WG. As you may remember, we had already worked through recommendation 2, the time limiting of FOAs, before we began discussing the Change of Registrant function. If you have any final questions or comments on the draft policy, please submit them to me by Thursday, 12 March. Thank you! Kind regards, Caitlin

1 0

Reminder: Comments on Change of Registrant/Transfer Policy - due Thursday 12 March
by Caitlin Tubergen March 11, 2015

March 11, 2015

Hi All, Please note that the deadline for the Implementation Review Team to provide comments on the attached draft COR policy is tomorrow, Thursday, 12 March. If you are unable to provide feedback by that time, you are welcome to submit any comments during the public comment period. Thank you. Kind regards, Caitlin From: owner-gnso-impl-irtpc-rt(a)icann.org [mailto:owner-gnso-impl-irtpc-rt@icann.org] On Behalf Of Caitlin Tubergen Sent: Thursday, March 05, 2015 10:19 PM To: gnso-impl-irtpc-rt(a)icann.org; Theo Geurts Subject: [gnso-impl-irtpc-rt] For your review: Change of Registrant/Transfer Policy - by Thursday 12 March Hi All, Thank you to everyone who participated in the call today. For those of you who were unable to attend, please find a link to the recording here: https://icann.adobeconnect.com/p4howkg3hce/ <https://icann.adobeconnect.com/p4howkg3hce/> During the call, we discussed the outstanding issue from our last call, which was the issue of third party privacy/proxy providers and the potential challenge of transmitting the change of registrant credential to the underlying registrant. The members of the IRT that were on the call with okay with the proposed solution, which you will find in footnote 1. The P/P issue was the last outstanding issue to discuss before we post the draft policy for public comment. I have attached the draft policy for your final review. You will note that this is the hybrid ³Transfer Policy,² which will go out for public comment. The Transfer Policy has two sections: the IRTP in section I, and the Change of Registrant in section II. The hybrid policy was recommended by the WG. As you may remember, we had already worked through recommendation 2, the time limiting of FOAs, before we began discussing the Change of Registrant function. If you have any final questions or comments on the draft policy, please submit them to me by Thursday, 12 March. Thank you! Kind regards, Caitlin

1 0

REMINDER: IRTP C Implementation Review Team call on Thursday 5 March 2015 1700UTC
by Caitlin Tubergen March 4, 2015

March 4, 2015

Hi All, Please save the date for the next IRTP C call on Thursday, 5 March 2015 at 1700 UTC 09:00 PST, 12:00 EST, 17:00 London, 18:00 CET, 03:00 (+1 day) Sydney. We will discuss the outstanding issue from the last call, which was how the use of a privacy/proxy provider could affect a change of registrant. This is the last outstanding issue to discuss before the draft policy goes out for public comment. Please find Adobe Connect and dial in instructions below. Link to Adobe Connect (with audio enabled):https://icann.adobeconnect.com/irtppartc/ *Upon logging into Adobe Connect, a pop up window will provide you the option to Dial Out to your Phone. Enter your Phone Number* (Remember to change the Country Code if needed). After joining the call, as a courtesy to others and the presenters, please MUTE your phone. This can be done by selecting *6 on your keypad. To UNMUTE select *6 again. If you are Unable to log into Adobe Connect and can only join via phone: List of International Dial In Numbers:https://www.myrcplus.com/cnums.asp?bwebid=8369444&ppc=6458688446&num =1-719-457-6209 <https://www.myrcplus.com/cnums.asp?bwebid=8369444&ppc=6458688446&num=1-719- 457-6209> Participant Passcode: 6458688446. Best regards, Caitlin Tubergen Registrar Relations and Contracts Manager ICANN

1 0