[ALAC] Compliance complaint

Alan Greenberg alan.greenberg at mcgill.ca
Thu Mar 13 14:31:31 UTC 2014


Thanks Olivier. I guess we should tell them that 
this will be a discussion item so they are not 
taken by surprise (although I would hope they 
could have figured it out for themselves).

I note on the Singapore page, there is no section 
for topics for the Compliance meeting.

Alan

At 13/03/2014 05:36 AM, Olivier MJ Crepin-Leblond wrote:
>Dear Alan,
>
>you're correct, we have heard nothing back.
>
>Since sending our official ALAC Statement to Maguy Serad on 27 February
>2014, I have received no confirmation of receipt whatsoever. Having
>CC'ed both Fadi Chehadé, ICANN CEO and Steve Crocker, ICANN Board Chair,
>I asked Steve when I had lunch with him last week at the London IETF.
>Immediately after receiving the note, Steve asked Compliance whether the
>Board should get involved and the response from Compliance was "no
>thanks, we'll work on it ourselves."
>
>I find it very poor etiquette from Compliance to not have at least
>acknowledged receipt of the ALAC Advice. Nonetheless, we should be
>pursuing this question when we meet with Compliance in Singapore.
>
>Kind regards,
>
>Olivier MJ Crépin-Leblond
>ALAC Chair
>
>On 13/03/2014 01:30, Alan Greenberg wrote:
> > I am assuming that the lack of a reply from Olivier means we have
> > heard nothing back.
> >
> > Compliance has already they don't want to spend the time with us going
> > over the same presentation that they will give in the public session,
> > so focusing on our proposal for a new submission tool seems appropriate.
> >
> > Alan
> >
> > At 12/03/2014 07:25 PM, Holly Raiche wrote:
> >> Hi Alan (and Garth)
> >>
> >> Well done - so far. My suggestion - that this be front and centre
> >> with any ALAC discussions with Compliance
> >>
> >> Holly
> >>
> >> On 12/03/2014, at 4:09 PM, Alan Greenberg wrote:
> >>
> >> > I received a message from Compliance on 10 March saying that the
> >> complaint we submitted had been closed because "Based on the current
> >> Whois data, the domain was suspended when the complaint was received
> >> by ICANN, or the registrar demonstrated that it took reasonable steps
> >> to investigate the Whois inaccuracy claim by suspending, deleting,
> >> cancelling or otherwise deactivating the domain name."
> >> >
> >> > On checking the Whois record, the domain still exists, but it is in
> >> "client Hold" status which means that it is no longer in the zone
> >> file. A DNS lookup confirmed this.
> >> >
> >> > The domain is due to expire on 24 April.
> >> >
> >> > So the result of this exercise is that the particular domain that
> >> we were complaining about is out of service. It remains to be seen
> >> whether it will pop back again or not. The fictitious e-mail address
> >> is still reported (by domaintools.com) as being in use by over 1000
> >> other domain names. It is not clear how many of them might also be
> >> unusable, but at least one that I checked (updflashplayer.com) is
> >> still in the DNS but does not seem to be live.
> >> >
> >> > To do further investigation would require more time than I have at
> >> the moment, and access to domain tools that I don't have. Perhaps
> >> Garth would like to follow0up and if so, I ask that he contact me
> >> directly to develop a plan of action.
> >> >
> >> > The bottom line seems to be that the compliance process worked in
> >> this case, but it is clearly insufficient to address the root problem
> >> that was being identified. The complaint process that we have
> >> suggested to Compliance would be far better suited. Have we had ANY
> >> response from them?
> >> >
> >> > Alan
> >> >
> >> >
> >> >
> >> > At 18/02/2014 05:03 PM, Alan Greenberg wrote:
> >> >>> The problem summary:
> >> >>>
> >> >>> Reporter Name: Alan Greenberg, on behalf of ALAC Leadership Team
> >> >>> Reporter Email: alan.greenberg at mcgill.ca
> >> >>> Domain being reported: rapetube.org
> >> >>>
> >> >>> Time of submission/processing: Tue Feb 18 16:23:13 2014
> >> >>>
> >> >>> Problem in whois block: Technical Contact
> >> >>> --- Error in address: Incorrect address
> >> >>> --- Error in email: Incorrect email
> >> >>> --- Comment: Same information as above.
> >> >>>
> >> >>> Problem in whois block: Registrant Contact
> >> >>> --- Error in address: Incorrect address
> >> >>> --- Comment: Domain given for e-mail address,
> >> "Privacy-Protect.cn" is a non-existent domain and therefore
> >> cannot possible be a valid address.
> >> >>>
> >> >>> Street address, "Rue la produit 34, Nimes,
> >> Languedoc-Roussillon, France, Postal Code:30189" is a
> >> non-existent address, and the postal code given (30189) is in fact an
> >> "area code" or "INSEE code" and not a valid
> >> postal code.
> >> >>>
> >> >>> The same registrant for other registrations gives the same
> >> invalid e-mail address, but often a valid street address (26 Rue Jean
> >> Reboul, Nimes, Languedoc-Roussillon, France 30900" which is
> >> apparetnly the address of a restaurant -
> >> 
> https://maps.google.com/maps?q=26+Rue+Jean+Reboul,+Nimes,+France&hl=en&ie=UTF8&ll=43.834047,4.357839&spn=0.010819,0.02311&sll=43.834016,4.357919&sspn=0.00136,0.002889&oq=26+jean+reboul,+&hnear=26+Rue+Jean+Reboul,+30900+N%C3%AEmes,+Gard,+Languedoc-Roussillon,+France&t=m&z=16).
> >> >>>
> >> >>> Problem in whois block: Administrative Contact
> >> >>> --- Error in address: Incorrect address
> >> >>> --- Error in email: Incorrect email
> >> >>> --- Comment: Same information as above.
> >> >>>
> >> >>> The whois at the time of processing is:
> >> >>>
> >> >>>
> >> >>> REGISTRY WHOIS:
> >> >>>
> >> >>>
> >> >>> Domain Name:RAPETUBE.ORG
> >> >>> Domain ID: D155914076-LROR
> >> >>> Creation Date: 2009-04-21T14:44:42Z
> >> >>> Updated Date: 2013-04-16T08:41:16Z
> >> >>> Registry Expiry Date: 2014-04-21T14:44:42Z
> >> >>> Sponsoring Registrar:Bizcn.com, Inc. (R1248-LROR)
> >> >>> Sponsoring Registrar IANA ID: 471
> >> >>> WHOIS Server:
> >> >>> Referral URL:
> >> >>> Domain Status: clientTransferProhibited
> >> >>> Registrant ID:orgre90683958698
> >> >>> Registrant Name:Henry Nguyen Gong
> >> >>> Registrant Organization:Privacy-Protect.cn
> >> >>> Registrant Street: Rue la produit 34
> >> >>> Registrant City:Nimes
> >> >>> Registrant State/Province:Languedoc-Roussillon
> >> >>> Registrant Postal Code:30189
> >> >>> Registrant Country:FR
> >> >>> Registrant Phone:+33.466583875
> >> >>> Registrant Phone Ext:
> >> >>> Registrant Fax: +33.466583875
> >> >>> Registrant Fax Ext:
> >> >>> Registrant Email:contact at privacy-protect.cn
> >> >>> Admin ID:orgre90683959424
> >> >>> Admin Name:Henry Nguyen Gong
> >> >>> Admin Organization:Privacy-Protect.cn
> >> >>> Admin Street: Rue la produit 34
> >> >>> Admin City:Nimes
> >> >>> Admin State/Province:Languedoc-Roussillon
> >> >>> Admin Postal Code:30189
> >> >>> Admin Country:FR
> >> >>> Admin Phone:+33.466583875
> >> >>> Admin Phone Ext:
> >> >>> Admin Fax: +33.466583875
> >> >>> Admin Fax Ext:
> >> >>> Admin Email:contact at privacy-protect.cn
> >> >>> Tech ID:orgre90683960526
> >> >>> Tech Name:Henry Nguyen Gong
> >> >>> Tech Organization:Privacy-Protect.cn
> >> >>> Tech Street: Rue la produit 34
> >> >>> Tech City:Nimes
> >> >>> Tech State/Province:Languedoc-Roussillon
> >> >>> Tech Postal Code:30189
> >> >>> Tech Country:FR
> >> >>> Tech Phone:+33.466583875
> >> >>> Tech Phone Ext:
> >> >>> Tech Fax: +33.466583875
> >> >>> Tech Fax Ext:
> >> >>> Tech Email:contact at privacy-protect.cn
> >> >>> Name Server:NS3.CNMSN.COM
> >> >>> Name Server:NS4.CNMSN.COM
> >> >>> Name Server:
> >> >>> Name Server:
> >> >>> Name Server:
> >> >>> Name Server:
> >> >>> Name Server:
> >> >>> Name Server:
> >> >>> Name Server:
> >> >>> Name Server:
> >> >>> Name Server:
> >> >>> Name Server:
> >> >>> Name Server:
> >> >>> DNSSEC:Unsigned
> >> >
> >> > _______________________________________________
> >> > ALAC mailing list
> >> > ALAC at atlarge-lists.icann.org
> >> > https://atlarge-lists.icann.org/mailman/listinfo/alac
> >> >
> >> > At-Large Online: http://www.atlarge.icann.org
> >> > ALAC Working Wiki:
> >> 
> https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)
> >
> > _______________________________________________
> > ALAC mailing list
> > ALAC at atlarge-lists.icann.org
> > https://atlarge-lists.icann.org/mailman/listinfo/alac
> >
> > At-Large Online: http://www.atlarge.icann.org
> > ALAC Working Wiki:
> > 
> https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)
> >




More information about the ALAC mailing list