I'm weighing here as Chair of the WHOIS WG. I disagree with Wendy on this matter. To my mind, this is first and foremost a matter of compliance with a solemn contract. And it plays heavily to one of the things the community has been charged to focus on per the AoC; transparency and accountability. If we think the clause does not matter, then I challenge the parties to do the honest thing and remove it from the RAA. If however, we believe like I do that the clause has a probative value, then it should be enforced and the contracted parties must ensure compliance.
From my perspective, compliance should include a requirement for accurate data. ICANN should not connive at error and enable contracted parties to generate junk data. It is quite understandable they can do it on their own.
Carlton Samuels ============================== Carlton A Samuels Mobile: 876-818-1799 Strategy, Planning, Governance, Assessment & Turnaround =============================
----------------------------------------------------------------------
Message: 1 Date: Tue, 22 Jun 2010 16:20:04 -0700 From: "Garth Bruen at KnujOn" <gbruen@knujon.com> To: ALAC@atlarge-lists.icann.org, na-discuss@atlarge-lists.icann.org, David.Giza@icann.org Subject: [NA-Discuss] Results of today's Port 43 Test Message-ID: < 20100622162004.4ea5342b4f0c5bb9c50429b56f1eb1a7.babba9b050.wbe@email00.secureserver.net
Content-Type: text/plain; charset="utf-8"
Hello,
Following up on this morning's discussion in the ALAC session on compliance. Below is a list of Port 43 WHOIS failures. Some in the list are recently defunct and I will have to remove them permanently. Others are actually unknown WHOIS locations, because as we discussed in the report the Registrars would not tell us; these are listed as failure.
Now, we have no way of knowing for sure, but there is a slight improvement since we released the report. 3 Registrar Port 43's that failed in a test exactly one week ago all passed today.
I haven't forgotten about the knujon whois util or address list for everyone, just been busy
21-domain.com FAIL 8hy.hk FAIL abansys.com FAIL agip.com FAIL antagus.de FAIL arcticnames.com FAIL aruba.it FAIL atxdomains.com FAIL austdomains.com FAIL bestbulkregister.com FAIL bhartiairtelservices.in FAIL brights.jp FAIL china.alibaba.com FAIL chinagov.cn FAIL chinaspringboard.com FAIL cronon.org FAIL cyberegistro.com FAIL DesktopDomainer.com FAIL df.eu FAIL digitrad.com FAIL direct.co.kr FAIL dnsexit.com FAIL Domaine.fr FAIL domainjamboree.com FAIL DomainLandrush.com FAIL domainname.at FAIL DomainRegistry.com FAIL domainregistry.de FAIL domains.coop FAIL domainspa.com FAIL domaintechnik.at FAIL drophhub.com FAIL francetelecom.com FAIL geewhizdomains.com FAIL globix.hu FAIL hectamedia.com FAIL hetzner.de FAIL hostnet.com FAIL hostway.com FAIL humeia.com FAIL idgenesis.com FAIL igempresas.com FAIL instra.com FAIL interdomain.es FAIL intermedia.net FAIL intra.com FAIL inwx.de FAIL is.co.za FAIL isimtescil.com FAIL iwelt.de FAIL key-systems.net FAIL komplex.net FAIL LCN.com FAIL livedoor.com FAIL lunarpages.com FAIL mailclub.fr FAIL marcaria.com FAIL MelbourneITDBS.com FAIL metapredict.com FAIL mindgenies.com FAIL namecheap.com FAIL Nameescape.com FAIL namefrog.com FAIL nameshield.net FAIL namesystem.com FAIL net.cn FAIL net4.in FAIL netregistry.com FAIL newgreatdomains.com FAIL portingxs.com FAIL purenic.co.jp FAIL riktad.com FAIL rntd.cn FAIL sedo.com FAIL SimplyNamed.com FAIL smartyhost.com.au FAIL spiritdomains.com FAIL sundancegrp.com FAIL sync.es FAIL tellus.com FAIL twt.it FAIL uk2group.com FAIL united-domains.de FAIL uol.com.br FAIL us.hooyoo.com FAIL verelink.com FAIL websitesource.com FAIL wudomains.com FAIL zzy.cn FAIL
------------------------------
Message: 2 Date: Wed, 23 Jun 2010 04:30:31 -0400 From: <gbruen@knujon.com> To: "na-discuss@atlarge-lists.icann.org" Subject: [NA-Discuss] Cheat sheet for WHOIS Accuracy Session at 11AM in 311/312 Message-ID: <CA818820763444599F74E141C6AED01B@theseus2PC> Content-Type: text/plain; charset="iso-8859-1"
Folks,
We are proving this "Cliffs Notes" version of our WHOIS data from our Registrar audit (http://www.knujon.com/knujon_audit0610.pdf) for today's WHOIS Accuracy Session at 11AM in 311/312
For Web-based WHOIS access: 11 Registrars have "look up" service instead of WHOIS 8 have clearly non-working engines or direct the visitor to some other WHOIS service A Technology Co(Namesystem.com) is manipulating it's own WHOIS record, returns: "Sorry Domain does not exist", and since we've published our report they pulled their port 43 offline completely. Note, this was ONLY for their domain name, all other queries worked.
For Port-43 WHOIS Access 30 Registrars have bad, inconsistent service 55 would not reveal their WHOIS address 6 gave us inaccurate data or the email to them was rejected. One Registrar, Domain Factory, said they were not a Registrar
For Bulk Access (RAA 3.3.6) Namescout and Network Solutions refused to offer the service eNom, Dotster, and Moniker did not respond to our request for information and price for bulk download
Registrars are restoring or maintaining domains beyond the 45 day period of being inaccurate.
10 Registrars have false WHOIS for their own website domains
------------------------------
Message: 3 Date: Wed, 23 Jun 2010 04:46:27 -0400 From: Wendy Seltzer <wendy@seltzer.com> To: gbruen@knujon.com Cc: NA Discuss <na-discuss@atlarge-lists.icann.org> Subject: Re: [NA-Discuss] Cheat sheet for WHOIS Accuracy Session at 11AM in 311/312 Message-ID: <4C21C9E3.2020605@seltzer.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Too bad the session conflicts with the ongoing open GNSO Council meeting. I'd dispute the relevance of some of these measures to ICANN, and would argue that in many cases, no action is warranted.
--Wendy
On 06/23/2010 04:30 AM, gbruen@knujon.com wrote:
Folks,
We are proving this "Cliffs Notes" version of our WHOIS data from our Registrar audit (http://www.knujon.com/knujon_audit0610.pdf) for today's WHOIS Accuracy Session at 11AM in 311/312
For Web-based WHOIS access: 11 Registrars have "look up" service instead of WHOIS 8 have clearly non-working engines or direct the visitor to some other WHOIS service A Technology Co(Namesystem.com) is manipulating it's own WHOIS record, returns: "Sorry Domain does not exist", and since we've published our report they pulled their port 43 offline completely. Note, this was ONLY for their domain name, all other queries worked.
For Port-43 WHOIS Access 30 Registrars have bad, inconsistent service 55 would not reveal their WHOIS address 6 gave us inaccurate data or the email to them was rejected. One Registrar, Domain Factory, said they were not a Registrar
For Bulk Access (RAA 3.3.6) Namescout and Network Solutions refused to offer the service eNom, Dotster, and Moniker did not respond to our request for information and price for bulk download
Registrars are restoring or maintaining domains beyond the 45 day period of being inaccurate.
10 Registrars have false WHOIS for their own website domains
-- Wendy Seltzer -- wendy@seltzer.org Fellow, Silicon Flatirons Center at University of Colorado Law School Fellow, Berkman Center for Internet & Society at Harvard University http://cyber.law.harvard.edu/seltzer.html http://www.chillingeffects.org/ https://www.torproject.org/
------------------------------
Message: 4 Date: Wed, 23 Jun 2010 01:51:08 -0700 From: "Garth Bruen at KnujOn" <gbruen@knujon.com> To: "Wendy Seltzer" <wendy@seltzer.com> Cc: NA Discuss <na-discuss@atlarge-lists.icann.org> Subject: Re: [NA-Discuss] Cheat sheet for WHOIS Accuracy Session at 11AM in 311/312 Message-ID: < 20100623015108.4ea5342b4f0c5bb9c50429b56f1eb1a7.d5e8286029.wbe@email00.secureserver.net
Content-Type: text/plain; charset="utf-8"
I welcome you comments via lists etc...
-------- Original Message -------- Subject: Re: [NA-Discuss] Cheat sheet for WHOIS Accuracy Session at 11AM in 311/312 From: Wendy Seltzer <wendy@seltzer.com> Date: Wed, June 23, 2010 4:46 am To: gbruen@knujon.com Cc: NA Discuss <na-discuss@atlarge-lists.icann.org>
Too bad the session conflicts with the ongoing open GNSO Council meeting. I'd dispute the relevance of some of these measures to ICANN, and would argue that in many cases, no action is warranted.
--Wendy
On 06/23/2010 04:30 AM, gbruen@knujon.com wrote:
Folks,
We are proving this "Cliffs Notes" version of our WHOIS data from our Registrar audit (http://www.knujon.com/knujon_audit0610.pdf) for today's WHOIS Accuracy Session at 11AM in 311/312
For Web-based WHOIS access: 11 Registrars have "look up" service instead of WHOIS 8 have clearly non-working engines or direct the visitor to some other WHOIS service A Technology Co(Namesystem.com) is manipulating it's own WHOIS record, returns: "Sorry Domain does not exist", and since we've published our report they pulled their port 43 offline completely. Note, this was ONLY for their domain name, all other queries worked.
For Port-43 WHOIS Access 30 Registrars have bad, inconsistent service 55 would not reveal their WHOIS address 6 gave us inaccurate data or the email to them was rejected. One Registrar, Domain Factory, said they were not a Registrar
For Bulk Access (RAA 3.3.6) Namescout and Network Solutions refused to offer the service eNom, Dotster, and Moniker did not respond to our request for information and price for bulk download
Registrars are restoring or maintaining domains beyond the 45 day period of being inaccurate.
10 Registrars have false WHOIS for their own website domains
-- Wendy Seltzer -- wendy@seltzer.org Fellow, Silicon Flatirons Center at University of Colorado Law School Fellow, Berkman Center for Internet & Society at Harvard University http://cyber.law.harvard.edu/seltzer.html http://www.chillingeffects.org/ https://www.torproject.org/
------------------------------
Message: 5 Date: Wed, 23 Jun 2010 06:03:18 -0400 From: Beau Brendler <beaubrendler@earthlink.net> To: Wendy Seltzer <wendy@seltzer.com> Cc: NA Discuss <na-discuss@atlarge-lists.icann.org> Subject: Re: [NA-Discuss] Cheat sheet for WHOIS Accuracy Session at 11AM in 311/312 Message-ID: <8F4E5614-37C7-4E40-980D-0931904415CF@earthlink.net> Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes
Wendy...with all due respect, I cannot see how your statement is even remotely supportable. Port 43 access, to name a single aspect, is part of the RAA. If I'm missing something here, tell me.
Please excuse brevity and typos -sent from IPhone
On 23/06/2010, at 4:46 AM, Wendy Seltzer <wendy@seltzer.com> wrote:
Too bad the session conflicts with the ongoing open GNSO Council meeting. I'd dispute the relevance of some of these measures to ICANN, and would argue that in many cases, no action is warranted.
--Wendy
On 06/23/2010 04:30 AM, gbruen@knujon.com wrote:
Folks,
We are proving this "Cliffs Notes" version of our WHOIS data from our Registrar audit (http://www.knujon.com/knujon_audit0610.pdf) for today's WHOIS Accuracy Session at 11AM in 311/312
For Web-based WHOIS access: 11 Registrars have "look up" service instead of WHOIS 8 have clearly non-working engines or direct the visitor to some other WHOIS service A Technology Co(Namesystem.com) is manipulating it's own WHOIS record, returns: "Sorry Domain does not exist", and since we've published our report they pulled their port 43 offline completely. Note, this was ONLY for their domain name, all other queries worked.
For Port-43 WHOIS Access 30 Registrars have bad, inconsistent service 55 would not reveal their WHOIS address 6 gave us inaccurate data or the email to them was rejected. One Registrar, Domain Factory, said they were not a Registrar
For Bulk Access (RAA 3.3.6) Namescout and Network Solutions refused to offer the service eNom, Dotster, and Moniker did not respond to our request for information and price for bulk download
Registrars are restoring or maintaining domains beyond the 45 day period of being inaccurate.
10 Registrars have false WHOIS for their own website domains
-- Wendy Seltzer -- wendy@seltzer.org Fellow, Silicon Flatirons Center at University of Colorado Law School Fellow, Berkman Center for Internet & Society at Harvard University http://cyber.law.harvard.edu/seltzer.html http://www.chillingeffects.org/ https://www.torproject.org/
------ NA-Discuss mailing list NA-Discuss@atlarge-lists.icann.org
http://atlarge-lists.icann.org/mailman/listinfo/na-discuss_atlarge-lists.ica...
Visit the NARALO online at http://www.naralo.org ------
------------------------------
Message: 6 Date: 23 Jun 2010 10:51:36 -0400 From: "John R. Levine" <johnl@iecc.com> To: "Beau Brendler" <beaubrendler@earthlink.net> Cc: NA Discuss <na-discuss@atlarge-lists.icann.org> Subject: Re: [NA-Discuss] Cheat sheet for WHOIS Accuracy Session at 11AM in 311/312 Message-ID: <alpine.BSF.2.00.1006231048200.90962@joyce.lan> Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Wendy...with all due respect, I cannot see how your statement is even remotely supportable. Port 43 access, to name a single aspect, is part of the RAA. If I'm missing something here, tell me.
Please excuse brevity and typos -sent from IPhone
It's ICANN's long standing pro-crime faction, that wants to remove all accountability for everything. They think they're pro-privacy, but as anyone who has an inbox full of fake drug spam and phishes knows, they're mistaken.
R's, John