ICANN ICANN Email List Archives


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

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

  • To: "gnso-impl-irtpc-rt@xxxxxxxxx" <gnso-impl-irtpc-rt@xxxxxxxxx>
  • Subject: [gnso-impl-irtpc-rt] Re: Outstanding Issue from today's IRT Call (email/account holder)
  • From: Caitlin Tubergen <caitlin.tubergen@xxxxxxxxx>
  • Date: Fri, 12 Dec 2014 01:22:15 +0000

Please find the draft COR policy attached and accept my apologies for a
double email.

Kind regards,


From:  Caitlin Tubergen <caitlin.tubergen@xxxxxxxxx>
Date:  Thursday, December 11, 2014 at 5:00 PM
To:  "gnso-impl-irtpc-rt@xxxxxxxxx" <gnso-impl-irtpc-rt@xxxxxxxxx>
Subject:  Outstanding Issue from today's IRT Call (email/account holder)

Hi, All,

Thank you to everyone who attended the call;  it was a very robust

For those who were unable to attend, I have attached instructions on how to
listen to the recording.

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
because their email account no longer exists. (Perhaps they left their
company, university, etc.)  Similarly, if someone were to move and suddenly
have a new address, telephone, email address, ISP provider, it would be
impossible to ACK a COR via email, postal mail, phone, etc.  While this is
narrow use case, ICANN staff and the IRT are trying to ensure that we are
not creating an unworkable scenario where a Prior Registrant cannot update
his or her email address.

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.  This
gets around the non-existent email address issue, but some have expressed
concerns about the risk of hijacking since resellers, hosting providers, et.
al., may be an account holder.

ICANN staff is currently seeking solutions to the problem mentioned above.
Specifically, we are looking for alternative authentication methods besides
the exchange of pin.

A couple of suggestions mentioned on the call include:
1. FOAs for change of registrant.  (The Prior Registrant would receive an
informative FOA at its email address (listed in Whois) and if it doesn¹t
contact the registrar within a certain number of days, the email change
would go through.)
2. Alternative authentication depending on the type of registrant change,
i.e., a different authentication method could be used if the name is staying
in the same account rather than a ³push² between accounts
Please feel free to elaborate on the above or provide new suggestions
entirely.  We discussed the difficulty with the resolution of this
particular problem and 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 representative body of the ICANN community.

Please provide any suggestions to me by COB Thursday, 18 December.  Thank
you in advance for your feedback.

Kind regards,


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

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

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

Privacy Policy | Terms of Service | Cookies Policy