ICANN ICANN Email List Archives


<<< Chronological Index >>>    <<< Thread Index >>>

Re: [gnso-impl-irtpc-rt] Outstanding Issue from today's IRT Call (email/account holder)

  • To: "gnso-impl-irtpc-rt@xxxxxxxxx" <gnso-impl-irtpc-rt@xxxxxxxxx>
  • Subject: Re: [gnso-impl-irtpc-rt] Outstanding Issue from today's IRT Call (email/account holder)
  • From: "Mike O'Connor" <mike@xxxxxxxxxx>
  • Date: Fri, 12 Dec 2014 09:33:02 -0600

<html><head><meta http-equiv="Content-Type" content="text/html 
charset=windows-1252"></head><body style="word-wrap: break-word; 
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">oops - i 
forgot to attach the revised draft too.<div><br></div><div></div></body></html>

Attachment: Draft Change of Registrant Policy_11Dec-MO1.docx
Description: Microsoft Office

<html><head><meta http-equiv="Content-Type" content="text/html 
charset=windows-1252"></head><body style="word-wrap: break-word; 
-webkit-nbsp-mode: space; -webkit-line-break: 
after-white-space;"><div></div><div><br><div><div>On Dec 12, 2014, at 9:26 AM, 
Mike O'Connor &lt;<a href="mailto:mike@xxxxxxxxxx";>mike@xxxxxxxxxx</a>&gt; 
wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div 
style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: 
after-white-space;">hi all,<br><br>here’s a first-try at the 
revision:<br><br><blockquote style="margin: 0 0 0 40px; border: none; padding: 
0px;">3.4 The 60-day transfer lock will be&nbsp;required if an Account Holder 
updates their email address,&nbsp;thus effectively&nbsp;causing a Change of 
Registrant and simultaneously rendering impossible the&nbsp;exchange of the 
Change of Registrant Credential as described in section 3.2.&nbsp; &nbsp;If the 
Account&nbsp;Holder wishes to opt out of the&nbsp;lock, they can validate the 
change of address through other verifiable&nbsp;means.<br></blockquote><br>On 
Dec 11, 2014, at 7:22 PM, Caitlin Tubergen &lt;<a 
wrote:<br><br><blockquote type="cite">Please find the draft COR policy attached 
and accept my apologies for a double email.<br><br>Kind 
regards,<br><br>Caitlin&nbsp;<br><br>From:&nbsp;Caitlin Tubergen &lt;<a 
 December 11, 2014 at 5:00 PM<br>To:&nbsp;"<a 
 Issue from today's IRT Call (email/account holder)<br><br>Hi, 
All,<br><br>Thank you to everyone who attended the call; &nbsp;it was a very 
robust discussion.<br><br>For those who were unable to attend, I have attached 
instructions on how to listen to the recording.&nbsp;&nbsp;<br><br>At the start 
of the call, I presented a scenario whereby a Prior Registrant would be unable 
to ACK/affirm a Change of Registrant request (COR) request&nbsp;because their 
email account no longer exists. (Perhaps they left their company, university, 
etc.) &nbsp;Similarly, if someone were to move and suddenly&nbsp;have a 
new&nbsp;address, telephone, email address, ISP provider, it would be 
impossible to ACK a COR via email, postal mail, phone, etc. &nbsp;While this 
is&nbsp;narrow use case, ICANN&nbsp;staff and the IRT are trying to ensure that 
we are not creating an unworkable scenario where a Prior Registrant 
cannot&nbsp;update his or her email address.&nbsp;&nbsp;<br><br>Section 3.4 of 
the draft COR Policy would allow a registrant to log into their account and 
update their information via their verified account. &nbsp;This 
gets&nbsp;around the&nbsp;non-existent email address issue, but some have 
expressed concerns about the risk of hijacking since resellers, hosting 
providers, et. al.,&nbsp;may be an 
account&nbsp;holder.&nbsp;&nbsp;<br><br>ICANN staff is currently seeking 
solutions to the problem mentioned above. &nbsp;Specifically, we are looking 
for alternative authentication methods&nbsp;besides the&nbsp;exchange of 
pin.&nbsp;<br><br>A couple of suggestions mentioned on the call 
include:<br><span class="Apple-tab-span" style="white-space:pre">   
</span>•&nbsp;FOAs for change of registrant. &nbsp;(The Prior Registrant would 
receive an informative FOA at its email address (listed in Whois) and if it 
doesn’t&nbsp;contact the&nbsp;registrar within a certain number of days, the 
email change would go through.)<br><span class="Apple-tab-span" 
style="white-space:pre">        </span>•&nbsp;Alternative authentication 
depending on the type of registrant change, i.e., a different authentication 
method could be used if the name is&nbsp;staying in the&nbsp;same account 
rather than a “push” between accounts<br>Please feel free to elaborate on the 
above or provide new suggestions entirely. &nbsp;We discussed the difficulty 
with the resolution of this particular&nbsp;problem and&nbsp;how this may need 
to back to the GNSO for more guidance if it cannot be resolved within the IRT, 
particularly since the IRT is not a&nbsp;representative body of the&nbsp;ICANN 
community.<br><br>Please provide any suggestions to me by COB&nbsp;Thursday, 18 
December.&nbsp; Thank you in advance for your feedback.&nbsp;&nbsp;<br><br>Kind 
regards,<br><br>Caitlin&nbsp;<br><span>&lt;Draft Change of Registrant 
Policy_11Dec.docx&gt;</span><br></blockquote><br><div><br>PHONE: 651-647-6109, 
FAX: 866-280-2356, WEB: <a href="http://www.haven2.com/";>www.haven2.com</a>, 
HANDLE: OConnorStP (ID for Twitter, Facebook, LinkedIn, 
<br class="Apple-interchange-newline"><span style="color: rgb(0, 0, 0); 
font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: 
normal; font-weight: normal; letter-spacing: normal; line-height: normal; 
orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; 
white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: 
auto; -webkit-text-stroke-width: 0px; display: inline !important; float: none; 
">PHONE: 651-647-6109, FAX: 866-280-2356, WEB: <a 
href="http://www.haven2.com";>www.haven2.com</a>, HANDLE: OConnorStP (ID for 
Twitter, Facebook, LinkedIn, etc.)</span>


Attachment: smime.p7s
Description: S/MIME cryptographic signature

<<< Chronological Index >>>    <<< Thread Index >>>

Privacy Policy | Terms of Service | Cookies Policy