Maybe UCANN school ICANN on whois
Raise your hand if you use whois every day. Even if your hand isn't up, and you just regard whois as an essential sysadmin tool, this post is for you.
Because if you're interested in keeping whois working for the those it was made for in the first place, you need to visit the battlefield where whois' future is being determined right now. That is, you must be Beowulf to the Grendel that is the Intellectual Property Community. Worse, you must confront him in the vast cave that is ICANN.
Except ICANN is more like Grendel's cave, only a helluva lot bigger, and far more boring. It's easy for an outsider to be daunted by ICANN's labyrinthine bureaucracy, its complex processes, its mountain of documents, the galactic scale of its influence, the ecclesiology of its high-level gatherings and its near-countless topics of concern. The relatively small topic what happens to whois would be easy to miss. For example, it's not even listed among the many current topics on ICANN's top-level topics page.
Ah, but it's there, amidst the 25,500 results in a whois topic search at the ICANN site. Among those results is a complicated Public Comments page, where it says, as if recited by Vogons,
ICANN is currently soliciting Public Comments until 30 October, 2007 on the most recent GNSO WHOIS Task Force and Working Group Reports, recommendations, and related Staff Overview of Recent GNSO Whois Activity and Staff Implementation Notes on the WHOIS Working Group Report. An overview and links to all related WHOIS documents currently available for comment can be found at: http://www.icann.org/public_comment/#whois-comments-2007
What matters are the date, which I've highlighted in red, and the link. Also this link, buried somewhere else I can't find again. It's for FINAL TASK FORCE REPORT ON WHOIS SERVICES 12 March 2007.
More scary than those are the comments themselves, which are thick with IP lawyers inveighing on behalf of something called Motion 2. This, along with two other Motions, can be found on page 9 of STAFF OVERVIEW OF RECENT GNSO WHOIS ACTIVITIES., a .pdf linked to by the document in the link of the quoted text above, prefixed by the ominous adjective "final".
Motions 1and 3, best as I can tell, call for minimal action.
Motion 2 calls for a complicated process that is obviously given the uniform enthusiasm of IP lawyer advocacy of it in public comments aimed toward turning whois into a whatis that is quite other than what it was intended for in the first place.
Elliot Noss, CEO of Tucows and an ICANN veteran of long standing, put the situation this way :
Whois started out as a way for geeks to know who to speak to, so they could manage domain name issues. This was way back when there weren't many domains around. More recently it has turned into an enforcement resource for intellectual property crime hunters. Meanwhile, as everybody knows, whois does have privacy problems, in that names and other personal information about contacts can be revealed through it.
So, at the end of the day, what everybody has been trying to do is move toward an operational point of contact, which is all somebody managing domain names needs to know. From the geek point of view, this is a way to move whois back to what it was in the first place, which was a way to manage an Internet resource.
But the intellectual property folks see whois as their enforcement database, and are working toward making that its primary purpose. Those two purposes are at odds, and that's what the debate is all about. Except so far the public comments have come mostly from just one side.
So, if you want to weigh in on this debate, to fight the suited Grendels in ICANN's cave, you have until a day before Halloween to go do that.
How, you ask? Meaning, where do you submit comments? I don't know. I'm looking around and I'm missing it. Meanwhile, I have a bus to catch, and I want to post this as soon as I can. If one of ya'll figures out how, post it in the comments below, and I'll append it here after I get to where I'm going.
Okay, the ansswer is here: whois-comments-2007@icann.org. Comment away.
[Later...] Wendy Seltzer has posted WHOIS redux: Demand privacy in domain name registration, in response to this post. Joe Andrieu has posted an open comment as well.
I've also learned that CircleID has a huge repository of whois-related intelligence.
By the way, a number of people (including Wendy and Elliot, quoted above) have told me their comments to this post are meeting some kind of obstacle. My apologies. We're working on that. [Later...] Okay, it's fixed now.
Doc Searls is Senior Editor of Linux Journal
Today’s modular x86 servers are compute-centric, designed as a least common denominator to support a wide range of IT workloads. Those generic, virtualized IT workloads have much different resource optimization requirements than hyperscale and cloud applications. They have resulted in a “one size fits all” enterprise IT architecture that is not optimized for a specific set of IT workloads, and especially not emerging hyperscale workloads, such as web applications, big data, and object storage. In this report, you will learn how shifting the focus from traditional compute-centric IT architectures to an innovative disaggregated fabric-based architecture can optimize and scale your data center.
Sponsored by AMD
Built-in forensics, incident response, and security with Red Hat Enterprise Linux 6
Every security policy provides guidance and requirements for ensuring adequate protection of information and data, as well as high-level technical and administrative security requirements for a system in a given environment. Traditionally, providing security for a system focuses on the confidentiality of the information on it. However, protecting the data integrity and system and data availability is just as important. For example, when processing United States intelligence information, there are three attributes that require protection: confidentiality, integrity, and availability.
Learn more about catching the bad guy in this free white paper.
Sponsored by DLT Solutions
| Using Salt Stack and Vagrant for Drupal Development | May 20, 2013 |
| Making Linux and Android Get Along (It's Not as Hard as It Sounds) | May 16, 2013 |
| Drupal Is a Framework: Why Everyone Needs to Understand This | May 15, 2013 |
| Home, My Backup Data Center | May 13, 2013 |
| Non-Linux FOSS: Seashore | May 10, 2013 |
| Trying to Tame the Tablet | May 08, 2013 |
- Using Salt Stack and Vagrant for Drupal Development
- Making Linux and Android Get Along (It's Not as Hard as It Sounds)
- New Products
- Validate an E-Mail Address with PHP, the Right Way
- Drupal Is a Framework: Why Everyone Needs to Understand This
- A Topic for Discussion - Open Source Feature-Richness?
- Home, My Backup Data Center
- New Products
- Readers' Choice Awards
- RSS Feeds
- Automatically updating Guest Additions
10 min 28 sec ago - I like your topic on android
56 min 56 sec ago - Reply to comment | Linux Journal
1 hour 18 min ago - This is the easiest tutorial
7 hours 32 min ago - Ahh, the Koolaid.
13 hours 11 min ago - git-annex assistant
19 hours 10 min ago - direct cable connection
19 hours 33 min ago - Agreed on AirDroid. With my
19 hours 43 min ago - I just learned this
19 hours 47 min ago - enterprise
20 hours 17 min ago
Enter to Win an Adafruit Prototyping Pi Plate Kit for Raspberry Pi

It's Raspberry Pi month at Linux Journal. Each week in May, Adafruit will be giving away a Pi-related prize to a lucky, randomly drawn LJ reader. Winners will be announced weekly.
Fill out the fields below to enter to win this week's prize-- a Prototyping Pi Plate Kit for Raspberry Pi.
Congratulations to our winners so far:
- 5-8-13, Pi Starter Pack: Jack Davis
- 5-15-13, Pi Model B 512MB RAM: Patrick Dunn
- Next winner announced on 5-21-13!
Free Webinar: Linux Backup and Recovery
Most companies incorporate backup procedures for critical data, which can be restored quickly if a loss occurs. However, fewer companies are prepared for catastrophic system failures, in which they lose all data, the entire operating system, applications, settings, patches and more, reducing their system(s) to “bare metal.” After all, before data can be restored to a system, there must be a system to restore it to.
In this one hour webinar, learn how to enhance your existing backup strategies for better disaster recovery preparedness using Storix System Backup Administrator (SBAdmin), a highly flexible bare-metal recovery solution for UNIX and Linux systems.



Comments
Very good, thanks a lot for
Very good, thanks a lot for your share ;)
That page will tell you
That page will tell you something about the process and ultimately direct you to send comments by email to this address: whois-comments-2007@icann.org.
turk mali dizisi
You'll need to send the
You'll need to send the comment, then verify that you sent the comment when ICANN's comment-bot writes you back (spam protection).
Whois comments
Doc thanks for the article. I digged through the info at Icann to post some comments. Sometimes I use whois to see who actually using domain so yes its nice to know something more than an IP or email address. But how much info should be revealed. Thats the big question.
Thanks Doc! (hyperlinked, this time)
I've added my comments and call to action.
Submitting comments to ICANN - I think...
At the bottom of http://www.icann.org/public_comment/#whois-comments-2007 there's an "add comment" mailto: link to whois-comments-2007@icann.org - that appears to be the best "submit here" that I've found thus far. I have to finish reading before I write in, however.
Where to send comments to:
Submit comments to:
whois-comments-2007@icann.org
Comments should be sent to
Comments should be sent to whois-comments-2007@icann.org *
*http://www.icann.org/announcements/announcement-2-14sep07.htm
where to submit comments
http://www.icann.org/announcements/announcement-2-14sep07.htm for more info
Submit comments to: whois-comments-2007@icann.org
how to make a comment
my bad. to make a comment, simply send an email to whois-comments-2007@icann.org.
Location of Public Comment Forum
Hi Doc,
Terrific article this morning. The link you're looking for is this one:
http://www.icann.org/public_comment/#whois-comments-2007.
That page will tell you something about the process and ultimately direct you to send comments by email to this address: whois-comments-2007@icann.org.
You'll need to send the comment, then verify that you sent the comment when ICANN's comment-bot writes you back (spam protection).
-- Bret
Comment Address
Comments may be sent to: whois-comments-2007@icann.org