ICANN ICANN Email List Archives

[gnso-irtp-b-jun09]


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

Re: [gnso-irtp-b-jun09] EAC Abuse

  • To: "Mike O'Connor" <mike@xxxxxxxxxx>
  • Subject: Re: [gnso-irtp-b-jun09] EAC Abuse
  • From: "Michele Neylon :: Blacknight" <michele@xxxxxxxxxxxxx>
  • Date: Tue, 3 May 2011 13:54:29 +0000


On 3 May 2011, at 14:50, Mike O'Connor wrote:

> just a knew-jerk reaction…  so this might not work…  but what if there was a 
> private ICANN mailing list that all EAC requests were copied to, and all 
> registries were subscribed to?  that would be a pretty simple/safe way to 
> document the exchanges.



that might work too :)

> 
> 
> On May 3, 2011, at 8:05 AM, Michele Neylon :: Blacknight wrote:
> 
>> 
>> 
>> On 3 May 2011, at 13:59, James M. Bladel wrote:
>> 
>>> Per our discussion, I am concerned about the potential for registrars to 
>>> abuse the EAC for non-emergency issues, or to claim EAC messages did not 
>>> receive a timely response.  This latter scenario would put the Registry in 
>>> the position of evaluating conflicting registrar claims before executing a 
>>> transfer undo.
>>> 
>>> Therefore, I believe we need an "objective observer" to the EAC exchange.  
>>> I promise I'm not seeking to over-complicate this mechanism, but if both 
>>> registrars simply copied or emailed the Registry support address when 
>>> initiating or responding to an EAC request, then this would close that 
>>> loophole.
>>> 
>>> I spoke briefly with Barbara, and while we both recognize that this is an 
>>> extra step in the process, it would effectively remove the need for the 
>>> Registry to determine which party was telling the truth.
>>> 
>>> For our "Phase II" strategy, we should recommend that this function be 
>>> added to RADAR (or a separate EAC.ICANN.ORG system be deployed).  The basic 
>>> functionality would be that registrars log in to send or respond to an EAC, 
>>> with both transactions copying ICANN and the Registry and being 
>>> timestamped.  But it is not practical to expect this at the outset.
>>> 
>>> 
>>> Thanks--
>>> 
>>> J.
>>> 
>> 
>> I agree
>> 
>> 
>> 
>> Mr Michele Neylon
>> Blacknight Solutions
>> Hosting & Colocation, Brand Protection
>> ICANN Accredited Registrar
>> http://www.blacknight.com/
>> http://blog.blacknight.com/
>> http://invadeeurope.eu/
>> http://rss.me/
>> http://mneylon.tel
>> Intl. +353 (0) 59  9183072
>> US: 213-233-1612 
>> UK: 0844 484 9361
>> Locall: 1850 929 929
>> Direct Dial: +353 (0)59 9183090
>> Twitter: http://twitter.com/mneylon
>> 
>> PS: Check out our latest offers on domains & hosting: http://domainoffers.me/
>> -------------------------------
>> Blacknight Internet Solutions Ltd, Unit 12A,Barrowside Business Park,Sleaty
>> Road,Graiguecullen,Carlow,Ireland  Company No.: 370845
>> 
>> 
>> 
>> 
>> 
> 
> - - - - - - - - -
> phone         651-647-6109  
> fax           866-280-2356  
> web   http://www.haven2.com
> handle        OConnorStP (ID for public places like Twitter, Facebook, 
> Google, etc.)
> 

Mr Michele Neylon
Blacknight Solutions
Hosting & Colocation, Brand Protection
ICANN Accredited Registrar
http://www.blacknight.com/
http://blog.blacknight.com/
http://invadeeurope.eu/
http://rss.me/
http://mneylon.tel
Intl. +353 (0) 59  9183072
US: 213-233-1612 
UK: 0844 484 9361
Locall: 1850 929 929
Direct Dial: +353 (0)59 9183090
Twitter: http://twitter.com/mneylon

PS: Check out our latest offers on domains & hosting: http://domainoffers.me/
-------------------------------
Blacknight Internet Solutions Ltd, Unit 12A,Barrowside Business Park,Sleaty
Road,Graiguecullen,Carlow,Ireland  Company No.: 370845








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

Privacy Policy | Terms of Service | Cookies Policy