September 2008 - NA-Discuss

Recommendation 12
by Danny Younger Sept. 3, 2008

Sept. 3, 2008

Alan, In a note to the GNSO Council regarding the agenda for the 4 September session, the BGC has expressed a particular interest in a discussion on Westlake Consulting Recommendation #12: That the ALAC should explore ways to differentiate between organizations that genuinely represent individual Internet users, and are therefore ALS candidates, as opposed to those which may be a better fit with the the NCUC. Could I trouble you for pointers to ALAC discussions on this topic (or more generally to current ALAC discussions on the ALAC Review)? Thanks, Danny

2 1

Semi-Annual Compliance Report
by Danny Younger Sept. 2, 2008

Sept. 2, 2008

Dear Ms. Burnette, I wish to discuss one particular section of the semi-annual compliance report. On the topic of the Whois Data Inaccuracy you wrote: "In addition, staff is implementing a system that will ensure staff reviews every alleged inaccuracy report for a particularized inaccuracy before sending the report to the registrar. Staff expects to implement this system by December 2008." I am very concerned by what appears to be an effort that cannot properly scale. I am aware of WDPRS submitters that have the ability to submit several thousand reports of WHOIS inaccuracies daily. One would think that a staff review process of every alleged inaccuracy will not be as efficient as audit procedures normally used by your department. Can you comment further on this new system and its potential impact on the WDPRS submitting community? Thanks, Danny Younger

1 0

Proposed ALAC statement on new amendments to RAA -- please read
by Brendler, Beau Sept. 2, 2008

Sept. 2, 2008

Hello, everyone. Attached is a draft of a proposed statement on behalf of ALAC regards the registrar accreditation agreement. This follows our briefing from Tim Cole a couple of weeks ago. As I mentioned in that briefing, I think a number of consumer and user community concerns can be traced back to this agreement and its enforcement. I think it's important to stay on top of the process and make as strong a statement as possible regarding the user community's concerns. The document is brief, and in two parts: The first part addresses possible concerns with the new amendments, as described by Tim. Some of these items are taken from the briefing discussion, some are taken from the general pool of user comments, and some have been re-worded and re-applied from "Section F" of the summary document (you can find links to all these referenced documents on the briefing page here: https://st.icann.org/alac/index.cgi?draft_amendments_to_raa) Danny Younger's expertise on this is of course acknowledged as well and you'll see some ideas and language in here from his own public comment document. I hope he will have some additions and suggestions for this. The second part revisits some of the initial comments made by the ALAC when the consultation period began. Some of these were placed in section F, but I reworded them to perhaps make them more timely and possibly acceptable for consideration. I also omitted some of the recommendations from Section F that seemed stale or probably just not doable at this point. If you have anything to add, please do so! This represents a starting point, we can add whatever else we want, but we promised to get this to Tim Cole by the end of August, and it's here. Nick has been very helpful to me in putting this together, so please send any additions or comments to this list, and/or Nick or me and we will integrate them into the final. **************************************************************************** ******** SCANNED **************************************************************************** ********

4 7

Washington Post to expose ICANN registrar ESTDomains
by Danny Younger Sept. 2, 2008

Sept. 2, 2008

A Washington Post article by Brian Krebs entitled "Report Slams U.S. Host as Major Source of Badware" promises a follow-up article on ICANN accredited registrar ESTdomains: "In a follow-up post, Security Fix will examine the activities of Atrivo's largest customer: domain name registrar ESTDomains". http://voices.washingtonpost.com/securityfix/2008/08/report_slams_us_host_a… Estdomains recently came to our attention when LegitScript and KnujOn sent a letter to EstDomains requesting they terminate an unlicensed steroid site being sponsored at EstDomains. We were told that EstDomains never responded and the site is sill active. Other online sources point to known Storm Botnet related FastFlux Domains registered by way of ESTDomains -- see http://www.disog.org/text/storm-fastflux.txt Also, Estdomains recently experienced over three weeks of downtime for their domain privacy protection service, the service failure exposing all domain registration information to the public during that episode -- see http://www.johnraul.com/estdomains-domain-privacy-down-for-three-weeks-now/ It will be interesting to see which (if any) provisions of the proposed Registrar Accreditation Agreement will deal with the revelations that emerge in the Washington Post's next article.

1 0