From caitlin.tubergen at icann.org Wed Mar 4 23:18:26 2015 From: caitlin.tubergen at icann.org (Caitlin Tubergen) Date: Wed, 4 Mar 2015 23:18:26 +0000 Subject: [gnso-impl-irtpc-rt] REMINDER: IRTP C Implementation Review Team call on Thursday 5 March 2015 1700UTC Message-ID: 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 Participant Passcode: 6458688446. Best regards, Caitlin Tubergen Registrar Relations and Contracts Manager ICANN -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 5050 bytes Desc: not available URL: From caitlin.tubergen at icann.org Fri Mar 6 03:19:09 2015 From: caitlin.tubergen at icann.org (Caitlin Tubergen) Date: Fri, 6 Mar 2015 03:19:09 +0000 Subject: [gnso-impl-irtpc-rt] For your review: Change of Registrant/Transfer Policy - by Thursday 12 March Message-ID: 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Transfer Policy.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 147457 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 5050 bytes Desc: not available URL: From BKnight at verisign.com Fri Mar 6 22:38:13 2015 From: BKnight at verisign.com (Knight, Barbara) Date: Fri, 6 Mar 2015 22:38:13 +0000 Subject: [gnso-impl-irtpc-rt] RE: For your review: Change of Registrant/Transfer Policy - by Thursday 12 March In-Reply-To: References: Message-ID: <7746E0B70F47DB448101E1DA28BCFF415881E211@BRN1WNEXMBX01.vcorp.ad.vrsn.com> A non-text attachment was scrubbed... Name: smime.p7m Type: application/pkcs7-mime Size: 94297 bytes Desc: not available URL: From caitlin.tubergen at icann.org Sat Mar 7 01:24:49 2015 From: caitlin.tubergen at icann.org (Caitlin Tubergen) Date: Sat, 7 Mar 2015 01:24:49 +0000 Subject: [gnso-impl-irtpc-rt] Re: For your review: Change of Registrant/Transfer Policy - by Thursday 12 March In-Reply-To: <7746E0B70F47DB448101E1DA28BCFF415881E211@BRN1WNEXMBX01.vcorp.ad.vrsn.com> References: <7746E0B70F47DB448101E1DA28BCFF415881E211@BRN1WNEXMBX01.vcorp.ad.vrsn.com> Message-ID: Hi Barbara, Thank you for your feedback! I have incorporated your changes/comments into the attached document, which uses the most recent version of the IRTP. Also, I took the liberty of adding some section numbers into the IRTP to it slightly more organized. Kind regards, Caitlin From: "Knight, Barbara" Date: Friday, March 6, 2015 at 2:38 PM To: Caitlin Tubergen , "gnso-impl-irtpc-rt at icann.org" , Theo Geurts Subject: RE: For your review: Change of Registrant/Transfer Policy - by Thursday 12 March Caitlin, I have reviewed the latest draft and have a few comments / recommended edits (redlined in the attached). I will also be soliciting additional feedback from others in the Registry community but did not want to hold up getting my initial feedback over. I anticipate that any further feedback or comments that may be forthcoming from the Registry community can be provided during the comment period once it is posted for comments. Thanks for all of your efforts. Barbara KnightDirector of Registry Compliancebknight at Verisign.com t: 703-948-3343c: 703-622-1071 12061 Bluemont Way, Reston, VA 20190 VerisignInc.com From: owner-gnso-impl-irtpc-rt at icann.org [mailto:owner-gnso-impl-irtpc-rt at icann.org] On Behalf Of Caitlin Tubergen Sent: Thursday, March 05, 2015 10:19 PM To: gnso-impl-irtpc-rt at 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 131 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.gif Type: image/gif Size: 3105 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Transfer Policy.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 138636 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 5050 bytes Desc: not available URL: From azonnenberg at hostnet.nl Wed Mar 11 10:09:29 2015 From: azonnenberg at hostnet.nl (Arthur Zonnenberg) Date: Wed, 11 Mar 2015 11:09:29 +0100 Subject: [gnso-impl-irtpc-rt] Re: For your review: Change of Registrant/Transfer Policy - by Thursday 12 March In-Reply-To: References: <7746E0B70F47DB448101E1DA28BCFF415881E211@BRN1WNEXMBX01.vcorp.ad.vrsn.com> Message-ID: <55001459.1050602@hostnet.nl> Hi group, Thanks for the document, I have been quite busy and saw good contributions by Theo and others so was less actively present during this IRTP D. I still think registered name holder / user friendliness is not a part of ICANN policy and that more effort should be put into measuring current transfer performance. That said, I also notice the Working Group on Data & Metrics for Policy Making is brainstorming and searching for more specific input on what to do: http://gnso.icann.org/en/meetings/transcript-dmpm-24feb15-en.pdf Is there something we can do for them to provide that input? In any case, for this specific policy, please find my comments in addition to the document with Barbara's comments attached. Feedback welcome as always. Kind regards, *Arthur Zonnenberg* Product manager Hostnet Hostnet bv De Ruyterkade 6 | 1013 AA Amsterdam T: 020-7500834 | F: 020-7500825 www.hostnet.nl | weblog.hostnet.nl Facebook Twitter Linkedin On 2015-03-07 02:24, Caitlin Tubergen wrote: > Hi Barbara, > > Thank you for your feedback! > > I have incorporated your changes/comments into the attached document, > which uses the most recent version of the IRTP. > > Also, I took the liberty of adding some section numbers into the IRTP > to it slightly more organized. > > Kind regards, > > Caitlin > > > From: "Knight, Barbara" > > Date: Friday, March 6, 2015 at 2:38 PM > To: Caitlin Tubergen >, "gnso-impl-irtpc-rt at icann.org > " >, Theo Geurts > > > Subject: RE: For your review: Change of Registrant/Transfer Policy - > by Thursday 12 March > > Caitlin, > > I have reviewed the latest draft and have a few comments / recommended > edits (redlined in the attached). I will also be soliciting > additional feedback from others in the Registry community but did not > want to hold up getting my initial feedback over. I anticipate that > any further feedback or comments that may be forthcoming from the > Registry community can be provided during the comment period once it > is posted for comments. Thanks for all of your efforts. > > Description: Description: cid:image001.gif at 01CE562A.FB6F3EB0 > > *Barbara Knight* > > Director of Registry Compliance > > bknight at Verisign.com > > t: 703-948-3343 > > c: 703-622-1071 > 12061 Bluemont Way, Reston, VA 20190 > > VerisignInc.com > > > > Description: Description: Description: Description: Verisign? > > *From:*owner-gnso-impl-irtpc-rt at icann.org > > [mailto:owner-gnso-impl-irtpc-rt at icann.org] *On Behalf Of *Caitlin > Tubergen > *Sent:* Thursday, March 05, 2015 10:19 PM > *To:* gnso-impl-irtpc-rt at 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 > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo.png Type: image/png Size: 6292 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: icon_facebook.png Type: image/png Size: 3878 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: icon_twitter.png Type: image/png Size: 4057 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: icon_linkedin.png Type: image/png Size: 3942 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Transfer Policy-BK Recommended Edits AZ.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 26161 bytes Desc: not available URL: From caitlin.tubergen at icann.org Wed Mar 11 18:40:39 2015 From: caitlin.tubergen at icann.org (Caitlin Tubergen) Date: Wed, 11 Mar 2015 18:40:39 +0000 Subject: [gnso-impl-irtpc-rt] Reminder: Comments on Change of Registrant/Transfer Policy - due Thursday 12 March Message-ID: 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 at icann.org [mailto:owner-gnso-impl-irtpc-rt at icann.org] On Behalf Of Caitlin Tubergen Sent: Thursday, March 05, 2015 10:19 PM To: gnso-impl-irtpc-rt at 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Transfer Policy.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 138636 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 5050 bytes Desc: not available URL: From jbladel at godaddy.com Wed Mar 11 19:51:25 2015 From: jbladel at godaddy.com (James M. Bladel) Date: Wed, 11 Mar 2015 19:51:25 +0000 Subject: [gnso-impl-irtpc-rt] Reminder: Comments on Change of Registrant/Transfer Policy - due Thursday 12 March Message-ID: 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 > Date: Wednesday, March 11, 2015 at 13:40 To: "gnso-impl-irtpc-rt at 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 at icann.org [mailto:owner-gnso-impl-irtpc-rt at icann.org] On Behalf Of Caitlin Tubergen Sent: Thursday, March 05, 2015 10:19 PM To: gnso-impl-irtpc-rt at 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Transfer Policy--Bladel Edits.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 128585 bytes Desc: Transfer Policy--Bladel Edits.docx URL: From mail at berrycobb.com Wed Mar 11 19:58:25 2015 From: mail at berrycobb.com (Berry Cobb) Date: Wed, 11 Mar 2015 12:58:25 -0700 Subject: [gnso-impl-irtpc-rt] Re: For your review: Change of Registrant/Transfer Policy - by Thursday 12 March In-Reply-To: <55001459.1050602@hostnet.nl> References: <7746E0B70F47DB448101E1DA28BCFF415881E211@BRN1WNEXMBX01.vcorp.ad.vrsn.com> <55001459.1050602@hostnet.nl> Message-ID: <00d801d05c35$bc57ff10$3507fd30$@berrycobb.com> Hi Arthur, Thank you for your input. For a hint of clarification, this thread is in response to IRTP-C. Part D has yet to form an IRT. In regards to DMPM, should the WG choose to continue forward with that use case, the intent will be to seek input from that group. Thanks again. B Berry A. Cobb Internet Corporation for Assigned Names & Numbers 720.839.5735 mail at berrycobb.com @berrycobb From: owner-gnso-impl-irtpc-rt at icann.org [mailto:owner-gnso-impl-irtpc-rt at icann.org] On Behalf Of Arthur Zonnenberg Sent: Wednesday, March 11, 2015 03:09 To: Caitlin Tubergen; Knight, Barbara; gnso-impl-irtpc-rt at icann.org; Theo Geurts Subject: Re: [gnso-impl-irtpc-rt] Re: For your review: Change of Registrant/Transfer Policy - by Thursday 12 March Hi group, Thanks for the document, I have been quite busy and saw good contributions by Theo and others so was less actively present during this IRTP D. I still think registered name holder / user friendliness is not a part of ICANN policy and that more effort should be put into measuring current transfer performance. That said, I also notice the Working Group on Data & Metrics for Policy Making is brainstorming and searching for more specific input on what to do: http://gnso.icann.org/en/meetings/transcript-dmpm-24feb15-en.pdf Is there something we can do for them to provide that input? In any case, for this specific policy, please find my comments in addition to the document with Barbara's comments attached. Feedback welcome as always. Kind regards, Arthur Zonnenberg Product manager Hostnet Hostnet bv De Ruyterkade 6 | 1013 AA Amsterdam T: 020-7500834 | F: 020-7500825 www.hostnet.nl | weblog.hostnet.nl Facebook Twitter Linkedin On 2015-03-07 02:24, Caitlin Tubergen wrote: Hi Barbara, Thank you for your feedback! I have incorporated your changes/comments into the attached document, which uses the most recent version of the IRTP. Also, I took the liberty of adding some section numbers into the IRTP to it slightly more organized. Kind regards, Caitlin From: "Knight, Barbara" Date: Friday, March 6, 2015 at 2:38 PM To: Caitlin Tubergen , "gnso-impl-irtpc-rt at icann.org" , Theo Geurts Subject: RE: For your review: Change of Registrant/Transfer Policy - by Thursday 12 March Caitlin, I have reviewed the latest draft and have a few comments / recommended edits (redlined in the attached). I will also be soliciting additional feedback from others in the Registry community but did not want to hold up getting my initial feedback over. I anticipate that any further feedback or comments that may be forthcoming from the Registry community can be provided during the comment period once it is posted for comments. Thanks for all of your efforts. Description: Description: cid:image001.gif at 01CE562A.FB6F3EB0 Barbara Knight Director of Registry Compliance bknight at Verisign.com t: 703-948-3343 c: 703-622-1071 12061 Bluemont Way, Reston, VA 20190 VerisignInc.com Description: Description: Description: Description: VerisignT From: owner-gnso-impl-irtpc-rt at icann.org [mailto:owner-gnso-impl-irtpc-rt at icann.org] On Behalf Of Caitlin Tubergen Sent: Thursday, March 05, 2015 10:19 PM To: gnso-impl-irtpc-rt at 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 6292 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 3878 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 4057 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image004.png Type: image/png Size: 3942 bytes Desc: not available URL: From azonnenberg at hostnet.nl Thu Mar 12 10:07:06 2015 From: azonnenberg at hostnet.nl (Arthur Zonnenberg) Date: Thu, 12 Mar 2015 11:07:06 +0100 Subject: [gnso-impl-irtpc-rt] Re: For your review: Change of Registrant/Transfer Policy - by Thursday 12 March In-Reply-To: <00d801d05c35$bc57ff10$3507fd30$@berrycobb.com> References: <7746E0B70F47DB448101E1DA28BCFF415881E211@BRN1WNEXMBX01.vcorp.ad.vrsn.com> <55001459.1050602@hostnet.nl> <00d801d05c35$bc57ff10$3507fd30$@berrycobb.com> Message-ID: <5501654A.7030501@hostnet.nl> Hi Berry, This is indeed the IRTP-C and my comments are in the right document. If we ask them for input and they ask us for input, is it clear to them we are waiting for a decision from them? They seem to think their mandate is not clear to begin with, so they are unlikely to make any decisions soon. In addition for the IRTP-C, - it is necessary that the Account Holder can receive and pass the credential on behalf of the Prior Registrant, to allow resellers to correct data on the basis of their reseller agreement and a request from the Registered Name Holder sent to the reseller instead of the Registrar. Failure to do so will create situations where the data *cannot* be corrected in cases the credential *cannot* be provided to the prior registrant based on information in WHOIS or on file. I think we can all agree that it is safer to use existing Account Holder data as a last resort versus using new Registered Name Holder data which can be simulated. For our consideration later today. Kind regards, *Arthur Zonnenberg* Product manager Hostnet Hostnet bv De Ruyterkade 6 | 1013 AA Amsterdam T: 020-7500834 | F: 020-7500825 www.hostnet.nl | weblog.hostnet.nl Facebook Twitter Linkedin On 2015-03-11 20:58, Berry Cobb wrote: > > Hi Arthur, > > Thank you for your input. For a hint of clarification, this thread is > in response to IRTP-C. Part D has yet to form an IRT. In regards to > DMPM, should the WG choose to continue forward with that use case, the > intent will be to seek input from that group. > > Thanks again. B > > Berry A. Cobb > > Internet Corporation for Assigned Names & Numbers > > 720.839.5735 > > mail at berrycobb.com > > @berrycobb > > *From:*owner-gnso-impl-irtpc-rt at icann.org > [mailto:owner-gnso-impl-irtpc-rt at icann.org] *On Behalf Of *Arthur > Zonnenberg > *Sent:* Wednesday, March 11, 2015 03:09 > *To:* Caitlin Tubergen; Knight, Barbara; gnso-impl-irtpc-rt at icann.org; > Theo Geurts > *Subject:* Re: [gnso-impl-irtpc-rt] Re: For your review: Change of > Registrant/Transfer Policy - by Thursday 12 March > > Hi group, > > Thanks for the document, I have been quite busy and saw good > contributions by Theo and others so was less actively present during > this IRTP D. I still think registered name holder / user friendliness > is not a part of ICANN policy and that more effort should be put into > measuring current transfer performance. > > That said, I also notice the Working Group on Data & Metrics for > Policy Making is brainstorming and searching for more specific input > on what to do: > http://gnso.icann.org/en/meetings/transcript-dmpm-24feb15-en.pdf > Is there something we can do for them to provide that input? > > In any case, for this specific policy, please find my comments in > addition to the document with Barbara's comments attached. Feedback > welcome as always. > > Kind regards, > > *Arthur Zonnenberg* > Product manager > > Hostnet > > Hostnet bv > De Ruyterkade 6 | 1013 AA Amsterdam > T: 020-7500834 | F: 020-7500825 > www.hostnet.nl | weblog.hostnet.nl > > Facebook Twitter > Linkedin > > > On 2015-03-07 02:24, Caitlin Tubergen wrote: > > Hi Barbara, > > Thank you for your feedback! > > I have incorporated your changes/comments into the attached > document, which uses the most recent version of the IRTP. > > Also, I took the liberty of adding some section numbers into the > IRTP to it slightly more organized. > > Kind regards, > > Caitlin > > *From: *"Knight, Barbara" > > *Date: *Friday, March 6, 2015 at 2:38 PM > *To: *Caitlin Tubergen >, > "gnso-impl-irtpc-rt at icann.org > " > >, Theo Geurts > > > *Subject: *RE: For your review: Change of Registrant/Transfer > Policy - by Thursday 12 March > > Caitlin, > > I have reviewed the latest draft and have a few comments / > recommended edits (redlined in the attached). I will also be > soliciting additional feedback from others in the Registry > community but did not want to hold up getting my initial feedback > over. I anticipate that any further feedback or comments that may > be forthcoming from the Registry community can be provided during > the comment period once it is posted for comments. Thanks for all > of your efforts. > > Description: Description: cid:image001.gif at 01CE562A.FB6F3EB0 > > *Barbara Knight* > > Director of Registry Compliance > > bknight at Verisign.com > > t: 703-948-3343 > > c: 703-622-1071 > 12061 Bluemont Way, Reston, VA 20190 > > VerisignInc.com > > > > Description: Description: Description: Description: Verisign? > > *From:*owner-gnso-impl-irtpc-rt at icann.org > > [mailto:owner-gnso-impl-irtpc-rt at icann.org] *On Behalf Of *Caitlin > Tubergen > *Sent:* Thursday, March 05, 2015 10:19 PM > *To:* gnso-impl-irtpc-rt at 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 > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo.png Type: image/png Size: 6292 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: icon_facebook.png Type: image/png Size: 3878 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: icon_twitter.png Type: image/png Size: 4057 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: icon_linkedin.png Type: image/png Size: 3942 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/png Size: 6292 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/png Size: 3878 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/png Size: 4057 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/png Size: 3942 bytes Desc: not available URL: From caitlin.tubergen at icann.org Thu Mar 12 23:29:33 2015 From: caitlin.tubergen at icann.org (Caitlin Tubergen) Date: Thu, 12 Mar 2015 23:29:33 +0000 Subject: [gnso-impl-irtpc-rt] question re: FOA expiration and COR Message-ID: 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Transfer Policy.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 127447 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 5050 bytes Desc: not available URL: From rob.golding at astutium.com Tue Mar 17 04:45:16 2015 From: rob.golding at astutium.com (rob.golding at astutium.com) Date: Tue, 17 Mar 2015 04:45:16 +0000 Subject: [gnso-impl-irtpc-rt] question re: FOA expiration and COR In-Reply-To: References: Message-ID: <02396ac53673ef3fa2209fe03628a995@astutium.com> > The issue is that it may be difficult for the gaining registrar to > know if there has been a Change of Registrant. If there is a change of registrant, the domain is locked for a period, so no transfer is possible - the text should be taken out of the policy as it's superceded by other parts of the policy now :) Rob