John Gilmore and Maddog Hall discuss .ORG bids 117
TreyHarris writes "Over on SAGEwire, we have posted an email exchange between John Gilmore (EFF cofounder) and Jon "maddog" Hall (Executive Director, Linux International) about the .ORG bids. It's a fascinating read, and goes much further into depth about the issues than I've seen on any news site thus far."
coveted TLDs (Score:3, Funny)
Just imagine...
moth.er fath.er lov.er teach.er
And a whole slew of naughty ones.
Re:coveted TLDs (Score:2, Funny)
Re:coveted TLDs (Score:2)
Lam.er (Score:1)
25 Cents sounds nice .. (Score:3, Informative)
HOWEVER, I do like the nothing I spend for dugnet.oss (ref OpenNIC [unrated.net])
I love OpenNIC! (Score:3, Informative)
Win-win-win-win.
Keep it high! (Score:3, Interesting)
I have about six
If anything, we need to jack up the price on
Oh, and while we're at it, the profits from the additional price shouldn't go to a company. They should go to a serious of non profits, selected by the members when they register. EFF and FSF could be on the top of the list
Re:Keep it high! (Score:1, Insightful)
Re:Keep it high! (Score:4, Insightful)
#1, you shouldn't be allowed to register "all the mis-spellings you can think of". You should have to be a valid non-profit organization.
#2, it is obvious to me that the purpose of your buying these domains is to be annoying. There is absolutely no valid reason to have a "misspelling" registered other than to be a pain in the ass.
I registered lazylightning.org with my friend. It's a Grateful Dead reference. We are actually non-profit. It's not a misspelling and it isn't for any reason other than for me to have a webpage and valid name to ssh to.
If I have to start paying $100 just to stop idiots like you from registering shit that would make me even MORE annoyed than I already am about the prices.
It's people like you that ruin it for the rest of us.
Re:Keep it high! (Score:3, Insightful)
Anyway, 503c is silly to require -- it's US-only, and doesn't cover a significant portion of actual "organizations". Lazylightning.org is not a "valid non-profit organization", it's personal, and those aren't the same things (it also doesn't have any valid connection to the Grateful Dead -- it would be more appropriate for you to use your own name).
If not formally non-profit, what then? Perhaps you could ban for-profit corporations from .org. Corporations obviously could get a 503c designation if they were validly non-profit (or the not-for-profit designation which is slightly different). This might work okay, and a "corporation" is a well-defined international concept.
But it's still difficult to determine what the limit for domain names registered would be. There are innumerable valid reasons for one organization/person to own multiple domains. Where would you draw the line?
Mostly, if we could get rid of blatantly invalid domain registrations (e.g., mispellings that point to those stupid search engines) and domains that are registered but not used (or have "under construction" for two years), then it would probably be a lot better. Of course, keeping aggressive trademark owners from manipulating the system is also important.
This is difficult as long as individuals have access to the system, as the system would continue to be manipulated by multi-level marketing companies, who work "through" individuals for their nefarious (or rather annoying) schemes.
And there's nothing wrong with registering a misspelling, so long as it's a misspelling of a domain you own (which I think is what the original poster is refering to). At a certain point it gets silly, but sometimes it is important (for instance, if you used lazy-lightning.org, you'd probably also want lazylightning.org, as it's hard to remember the difference between the two).
Re:Keep it high! (Score:1)
By your rationale any organization that is not turning a profit, which in light of current economic trends is about any commercial entity, can pick up a
problem is not the price (Score:1)
Re:problem is not the price (Score:1)
Re:problem is not the price (Score:1)
It seems totally logical to me that these losers would dry up and blow away over night after they contemplated the possibility of being lynched if they had to _by law_ provide real contact information.
The obfuscaters are tougher, but from my unfortunately _vast_ experience with this, they are the minority.
Re:Keep it high! (Score:1)
Re:Keep it high! (Score:1)
domain names are stupid (Score:3, Interesting)
So what should domains be? Well, just what they sound like, "domains" of servers. Go.com does this right. They have a web server for espn.go.com and another for abcnews.go.com. Don't want to remember those? Fine, then bookmark espn.go.com and call it "sportz."
Registering names for domains that will only ever have websites is also extremely stupid. What is at ftp.hotornot.com? Are there any groups at news.onion.com?
In conclusion, I will concede that the
A rose is a rose....... (Score:2)
Yes, perhaps it would be better if we all had domain names without meaning and then relied on indexing services. Great, but how do I find that web site again? Bookmarking is great, but it only works on one computer. How can I tell you to check out www.643sda453fgasdf.org or would you rather I told you to check out www.xyz.org? Especially if xyz was a reasonable form of the name.
Final point, I hope I catch up with the mod of the poster as troll in m2. Tps12 makes a very good point, he isn't just stiring things.
Re:A rose is a rose....... (Score:2)
Um, how about you tell me enough about the site that a Google search brings it up? And the more people who use that search pattern, the higher it appears on my page.
Maybe what we need is a good protocol for storing and sharing bookmarks.
Re:A rose is a rose....... (Score:2)
I have been involved with a couple of non-profits with web sites. Both are of reasonable size and we often get telephone inquiries. It is much easier to say to somebody over the phone "check out www.xyz.org" than some horribly long name.
Re:A rose is a rose....... (Score:1)
How do you tell someone what your snail-mail address is now?
You don't think anything of saying, "Apartment 123, West Home Building, 223 Rainier Drive, Rinky-dink Township, Mass. 001728-0013.
It's all in what you are used to. You are used to www.abc.org, but you don't expect to be able to tell your mother to mail your Christmas present to "joe's house".
Re:A rose is a rose....... (Score:2)
In any case, the contact info for many organisations now comes from their web pages. For example, if I want to contribute money to the German Red Cross [www.drk.de] for their relief work for those caught out by the flooding, then just look them up on the web, their address is there, as well as how to contribute (incidentally, a good cause as nature can outdo Osama every time).
Re:A rose is a rose....... (Score:2)
In any case, the contact info for many organisations now comes from their web pages. For example, if I want to contribute money to the German Red Cross [www.drk.de] for their relief work for those caught out by the flooding, then just look them up on the web, their address is there, as well as how to contribute (incidentally, a good cause as nature can outdo Osama every time).
Domain names aren't stupid (Score:4, Insightful)
Network hosts have conventionally borne the names of their organizations since the 1970s -- in fact, before the creation of TCP/IP. The reason the domain name system was created was to facilitate use of easily memorized, meaningful names rather than numeric addresses.
Read RFCs 597, 606, 608, 810, 952, and 1034 for a start.
If you really believe "you do not need a domain name to have a website," then by all means feel free to use numeric addresses. You won't need to pay a registrar one red cent, and no corporations will sue you for infringing their trademarks.
Re:Domain names aren't stupid (Score:1)
The smartest way to set up a site under such a system would be that the default www..com would point you to an index or search engine of the rest of the domain. This would probably clean up a lot of the crap on the web if we even remotely enforced the concept of a "domain" in reference to registration. We would possibly put some limit on the number of squatters if there was actually some kinda of tribunal or something that could say "your company/organization is called Spam And Squatters Inc., you get to choose between SpamAndSquatters.com or SpamAndSquatters.net".
Yeah, yeah, yeah, some of you whackos will go nuts over some organization telling you that you can't have 3000 addresses or that you can't buy "3rdGradeStudies.org" and toss death-porn up at the domain but I think that's reasonable. Go lobby for the
Re:Domain names aren't stupid (Score:1)
But what if the name of my company was 216.239.51.101 or something similar?
Re:domain names are stupid (Score:1)
DNS is for name->address mapping, _not_ for finding what you are looking for. LDAP is for searching through and accessing categorized directories.
LDAP isn't nearly as popular as DNS (Score:1)
[Unlike DNS,] LDAP is for searching through and accessing categorized directories.
But is there a popular free public LDAP server that covers the whole Internet? Or is LDAP designed primarily for use on a company LAN?
Re:LDAP isn't nearly as popular as DNS (Score:1)
Re:domain names are stupid (Score:2)
Fine, that is, until you change service providers, and are obliged to change domain names to the name of your new provider. At that point, you lose all the links that anyone ever created to your website, and your search engine rankings. Ditto for email addresses, as you have to tell everyone who ever emails you to update their address book.
What you've come up with here is not an argument for "get a subdomain wherever your site is hosted," but rather for, "there should be a very large number of meaningless top level domains, so that everyone everywhere can have a not-particularly-meaningful but permanent domain name which remains theirs in perpetuity."
Re:domain names are stupid (Score:1)
Let's add a
And we can all tell a porn site when we see one, right? They should all be moved to the
$0.25 a name? Get Real! (Score:2, Insightful)
$625k a year to run a 2.5 million name database? In the real world that pays for 5 high end people after you count business expenses. This is a hgih availability application. Lets get network transit and co-lo with security and backup power. You walso want to replicate this database in a remote location so that doubles those expenses. You also want maintenance contracts with relatively short turn around time. Don't forget staff to man the phones for international operations (Perhaps 24x7). Yes, they may have bought higher end hardware than they needed, but that's a small part of the overall expenses. Finally, these folks are trying to do a professional job and do deserve to make some money in the process.
How did Gilmore make his money? As I recall it was from being an early employee in Sun. He seems to think that everyone else should give away their profits and live in cardboard boxes, but he sure lives well himself. Let's also be clear that Gilmore has had a very public feud with Paul Vixie about MAPS. Gilmore thinks he has a right to run an open relay and make life easier for spammers, but MAPS does not have a right to list his system. How's the for libertarian ideals? I suspect that's coloring his review.
Re:$0.25 a name? Get Real! (Score:2)
And what would this achieve? Only some mindless beureaucrats idea of consistency and correctness. There are plenty of registered non-profits that are out and out commercial organizations sheltering behind the tax code. A non profit can pay its CEO whatever it likes so quite a few 'non-profits' are actually worth millions to the people who control them.
If you want a high reliability Internet you cannot do the DNS system on the cheap. At present .org is hosted in multiple data centers spread arround the world. $625K would not come close to covering costs for rent and connectivity.
The problem with multi-millionaire hippies like Gilmore is that they have absolutely no understanding of money. It is not a constraint to them so they don't understand that it could be a constraint to anyone. The folk pontificating on the cost of running the DNS system are the same type of people who get into a state when they are told that it costs several million dollars to paint the golden gate bridge. After thinking about the issue for ten seconds they will assert that it should cost no more than $25,000 and if pressed will claim to have based their estimate on how much it cost to paint their house ten years ago. If told that it would cost more than $250K for the paint alone they will give a flat denial.
Incidentally it is the same type of thinking that is preventing the deployment of DNS Security. An IETF faction is trying to make the protocol as expensive to deploy as possible in the large zones by blocking required engineering changes. The fact that all the registries and all the people who maintain the major DNS codebases support the changes is ignored.
CyberSquatters New friends? (Score:1)
and then lost them due to trademark and name infringement and the like through WIPO proceedings..
I don't think WIPO needs any more work than it has right now.. and this woudl just open org domains up to cyber squatters.. we have enough problems with this issue of cyber squatters not to make changes that might increase the problem..
An approach not yet considered (Score:2)
An approach I haven't seen mentioned yet for making sure
Re:An approach not yet considered (Score:1)
global tlds - require some sort of evidence of being a global company (there are country codes for a reason)
and finally a tld where there are no such restrictions, but it is strictly first come first serve - if I want to register microsoft.whatever, fine - and it can't be taken back for using their name, companies have .com and .co.cc and so on.
Are you serious? (Score:2)
You're telling me you want 200+ contries to agree to start spending huge amounts of money to validate the people registering stuff live in their countries?
Even ones that make tons of money selling their ccTLD as a defacto gTLD (niue, tuvalu, christmas islands (.nu,.tv,.cx))
Re:An approach not yet considered (Score:1)
Re:An approach not yet considered (Score:1)
Any of the above, I'd imagine, as long as they can prove it and so on.
Why not?
Considered... and rejected! (Score:3, Interesting)
When I got this domain, the rules on
I, for one, would be extremely pissed if the rules on
If you are going to do that to
Ut-oh... I guess it's now obvious that limiting domains by lexicography is a stupid thing. If you want to be a lexicographer, and you think you know better than the rest of us, by all means, start a search engine company or a portal site, and let people who agree with you use it and validate your judgement... or ignore you, if that's what their tastes dictate.
-- Terry
Re:Considered... and rejected! (Score:2, Interesting)
.org has already been assimilated by the Borg (Score:2)
Re:.org has already been assimilated by the Borg (Score:2)
Misunderstanding of what the DNS can do for you (Score:2)
The DNS is good at looking up strings. It's a lousy search engine.
The idea that one should try to "control" a name in all domains is silly - but happened BECAUSE people tried DNS as a search engine.
Personally, I type names into Google when I want to look them up, not my browser bar.
There are other angles of attack - see draft-klensin-dns-search [ietf.org], for instance - but currently that works.
AND Google gives me enough context to show me WHAT kind of "good vibrations" I'm headed for....
This just bothered me... (Score:2)
Why don't you ask your friend the actual name of the site? Instead of a potentially confusing shorthand? When I order books online and then tell someone about it, I say "I got it from bn.com", not "I got it from bn". Why? Because logically the
Of course, the other solution is, do a Google search and avoid the whole issue. Hopefully your friend told something about why "gumby" was a cool site. Go look for it. You know the risk in trying to use a telephone number as a search handle. Why should it be different for domain names?
Re:This just bothered me... (Score:3, Insightful)
Don't you mean "google dot com"?
lol... (Score:2)
(bleh, fucking 2 minute timeout)
Many TLDs isn't the answer (Score:3, Insightful)
Real people, however, want meaningful domain names. If you have a hundred TLDs, many of them will overlap conceptually. Who can remember the difference between .biz and .bus, or .game and .toy? They might remember your carefully chosen second-level domain, but with generic TLDs they won't be able to get to it. Unless you register the name in all related TLDs. But isn't that what we were trying to get away from?
We have been attacked by multi-level marketers and spammers, and those people are damaging the system greatly. But we can't win by trying to beat them at their game -- by diluting the system so greatly that they can't play. That just ruins the game for everyone, and the MLMers and spammers will still be there anyway. I don't like ICANN, but I do think that well-defined, meaningful, sometimes regulated, and non-overlapping TLDs are essential. This makes ICANN all the worse, because something like it is essential, but done the wrong way (with the wrong people influencing it) it will again damage the system.
Re:Many TLDs isn't the answer (Score:1)
Meaningful domains, brought to you by Google (Score:2)
Wow, that's really useful. Just as useful as:
Call me! My phone number is 523-555-3125!
When I want to find out, say, where I can train in kendo, I could start dialing phone numbers that spell out "KENDO" on the numberpad. That would get me exactly nowhere. I could, however, go to the phone book, and look at that. The phone book approach is far more likely to be successful.
Content-based oversight of domains is useless if not done right, and too costly to do right. Let's not do any of it at all, and rely on the phone books of the Internet to do the work for us. Furthermore, the phone book approach provides a built-in quality control- if one phone book puts dealers of Kawasaki Ninjas and Teenage Mutant Ninja Turtles under the Martial Arts section, word will get around, and their usage will decrease in favor of those phone books that manage to put the right things in the right places. There is no "Ministry of Directories" that makes sure that every directory of anything is correct. Quality control is gained through verification with other humans.
Google got to the top because their search results are remarkably good. If someone puts out better results, they'll go higher than Google. A central, condition-immune TLD registrar has no such incentive.
Re:Meaningful domains, brought to you by Google (Score:2)
Second, I didn't say domain names should be a search system. They are an address. Your arbitrary addresses have been used in Brasilia for house addresses, and my understanding is they suck -- the address says nothing about the location, and there is no good way to remember what something's address is. Phone numbers are also arbitrary, and very hard to remember, hence 1-800-CALLATT and the like -- you don't think, "hey, I bet AT&T offers calling service!", you remember the name after its been specifically told to you. And I believe Sprint (or MCI?) even got 1-800-ATTCALL and redirected it to 1-800-COLLECT, just like the problems with DNS. In the early days of phone numbers, even individuals had mnemonic phone numbers; the advantages have long been clear.
Using arbitrary domain names is a step backward. Just because the problem is hard, you're saying we should give up. I think we can do better.
Re:Meaningful domains, brought to you by Google (Score:2)
This way of thinking only works if there are few such people advertising addresses like that. That is, there are few telco collect services, so it's easy to remember the few 1-800-CALL-THIS-FOR-COLLECT numbers that exist. The domain names for the internet were similarly 'nice' back in the day when there few names being spewed around. However, imagine several thousand advertisers on TV spouting off call-collect numbers; your 'meaningful' name just lost its value, since it gets lost in the crowd.
The same thing has happened to the internet, and yet hardly signficant percentage of the world owns their own domain. As the number of owners grows, the value of 'meaningful' domains will continue to plummet.
I've also covered the issue of arbitrary domain names in another post [slashdot.org].
Re:Many TLDs isn't the answer (Score:2)
Those 'real people' can pay a premium for
Unless you register the name in all related TLDs. But isn't that what we were trying to get away from?
So add so many TLDs it becomes impossible. If anyone is using your trademarked name in an illegal manner, fight that in the courts, don't pre-empt it through the DNS and mess things up for the rest of us. Yes, this might make it hard to protect ubiquitous names like cars.com -- tough, you shouldn't try to pretend you own a generic word.
Jon and John don't know about domain registrars (Score:3, Informative)
About US$10/year (EUR12/year) to have any of .COM, .NET, or .ORG domains. I have had all my domains registered through them for about three years.
They even do DNS for you, if you don't have it. And their entire system is automated. I've never had to make a phone call, send a letter, or a FAX. Everything, and I mean everything is done through their web interface.
And just in case you wonder, I'm a U.S. citizen... the fact these guys are based out of France and charge me in Euros doesn't seem to make any difference. I've never had a problem with these guys. They're clued.
You did not mention the best part... (Score:1)
A more subtle distinction that it appears at first, IMHO.
Re:You did not mention the best part... (Score:1)
Thank you for filling in that vitally-important detail.
Re:Jon and John don't know about domain registrars (Score:1)
Re:Jon and John don't know about domain registrars (Score:2)
gkg.net charge $9.95/yr, joker.com EUR 13.92 including DNS (reseller prices as low as $6.98 in volumes, godaddy also has an extensive reseller program).
Re:Jon and John don't know about domain registrars (Score:1)
Still thinking.inside.box (Score:2)
The problem with the domain system is that it is a huge, nearly flat namespace. Just adding new TLD's to the current system is a poor way of fixing its problems (although it was a much better idea back when Jon Postel first suggested it). No company with a .com is going to willingly give it
up now.
Do you think Nissan Motors is going to settle for "nissan.auto"? Or that the fellow they're trying to take nissan.com from is going to give it up for "nissan.name"? There's only one way to level the playing field: eliminate the current TLD's and force everyone (whether corporation, organization, or individual) to choose a new one from a reasonably large and comprehensive list.
There are various restictions that might rationalize the system even more (e.g. restrict each entity to a single 2nd-level name per TLD and use further levels to subdivide, e.g. "suvs.nissan.auto") but I'm not sure such regulation would be necessary (or desirable). But one thing for sure: there is too much vested interest in the current system for incremental changes to work.
Heh... (Score:2)
Or you could just ask your friend for the URL...
Pronounceability (Score:2)
Or you could just ask your friend for the URL...
Uniform Resource Locators were not designed to be easily pronounced in situations such as giving a URL over the radio or over the telephone. Canonical example: hotel tango tango papa colon slash slash Slashdot dot org [slashdot.org]. A natural language keyword system, such as what DNS has mutated into, produces better results for name spaces that are restricted by the phonotactics [google.com] of a spoken natural language (go to Google.com, as in Barney Google, and type in Slashdot, all one word [google.com]).
An alternative view of lookup systems (Score:2)
A co-worker of mine thought of this idea; it seems like a good view of how DNS should be.
DNS is best at providing a mapping from a static legal designators to a dynamic technical namespace. In our case, that means we are mapping from a legally-owned and recognized domain name to a potentially dynamic IP address.
The problem is that the legal referers, domain names, are valuable, since they are human-readable (e.g., example.com). This value causes all the fighting over them that we see today.
To resolve this, domain names not be human readable; they should be more like an IP address, except that it is static, can map to a dynamic address. That is, domain names could be, say, numbers only, e.g., "23598263596".
As to the problem of 'finding' a website, which is currently done by novices by simply typing "company.com", this is what directory services are for. Example of directory services are Google, or DMOZ, where your amount legal power does not equal the size of your presence. That is, just because you are large, you do not automatically get the first hit on Google for "yourname"; your 'site' has to be popular.
It is also important to note that directory services can provide multiple results for a name. DNS only provides one place to go to for "company.com". However, if looked up "company" in Google, you will see multiple results; from those results you can decide whether or not you might be ending up at the correct site. A good example of this is "whitehouse". "whitehouse.com", of course, is porn. But the first hit on Google is whitehouse.gov, and you can easily tell from the Google summary that whitehouse.com is porn.
Furthermore, this system also eliminates squatting, since the static legal addresses have little value. That is, there is no real value beteween "5982352569" and "2352356" as addresses.
Re:An alternative view of lookup systems (Score:1)
It doesn't hurt to make suggestions and this one was logical but not real-world workable.
Re:An alternative view of lookup systems (Score:1)
This won't work for e-mail: do you think that sendmail will run a google search and make an intelligent choice as to which domain hosts ``ftobin''?
Re:An alternative view of lookup systems (Score:2)
I think you miunderstand. The email address would be something like ftobin@23523523523525. Doing a directory lookup is used when you only know a weak, non-technical name of something online, such as a legal name, e.g., "Sears". Email addresses don't fall into that category; they are technical descriptions of where to deliver mail.
Please correct me if I'm miunderstanding you.
Re:An alternative view of lookup systems (Score:1)
Re:An alternative view of lookup systems (Score:2)
There is a difference between an address being memorable and and its being to use. True, something like ftobin@2353252352 isn't memorable or easy to use. However the easy-to-use problem can be solved:
The number-domain could be encoded into words (like PGP did for its hex fingerprints) each 2 bytes or so can correspond to a word in a known dictionary. That way, something like ftobin@32523590 could be encoded to ftobin@[charlie whiskey banana paper]. This solution also helps memorability, but doesn't "solve" it in the manner you hope to.
I'm aware that my encoding scheme creates some degree of desirable for certain names, but not to any real great extent, I feel. And it certainly eliminates trademark issues.
However, I'm not so sure the problem of memorable addresses can be solved in the long run. True, right now we can do name@my.domain.org, because there are so few people actually having addresses. But as as each individual gets at least one address (I highly think that each individual should get many addresses), names almost by definition get less memorable, due to people just being swamped with names.
Remember, the problem with "desirable" memorable addresses is that they create this situation where everyone's climbing over each other for a scarce resource. People get along fine with non-controlled house addresses; hence, I don't quite see a problem with using some sort of encoding scheme as suggested above.
Logical vrs Physical vrs Conceptual vrs Legal (Score:2, Interesting)
This cannot work.
While directory services function moderately well at locating references to concepts, they don't do it REAL well. I went looking for HTMLView a few days ago and had to slog through pages of results that pointed to the wrong product that happened to have the same name. And most people are not experts at using search engines.
Maybe we need to consider Ted Nelson's Xanadu Project all over again. ie., we need something to allow entities on the Net to be conceptually identified and categorized so that people can put a name or concept in a search engine and find an INTELLIGENTLY ORGANIZED (unlike Google where the results are a hodgepodge of whatever the Web server operator put in his HTML) list that describes the entity in sufficient terms to determine WHAT KIND of entity it is and WHICH entity of that kind it is.
Then you hit the button and you get the legal address which has no more importance than "1055 Market Street" does (or wouldn't if we didn't live on a physical street) and IT takes you to 455.622.012.5 which only the routers care about.
Simpler Solution (Score:2)
Gilmore seems to have won out (Score:1)
I certainly don't think making domain names more expensive will help anything.
The cooling off period idea of Hall's was good, too.
However, I don't think that having a bunch more top level domains will solve cybersquatting either. In fact, I think there probably isn't a clean solution to cybersquatting.
perhaps openNIC could eventually find a better compromise than the current system, however (and perhaps not, who knows?)
-- bayle