Catch up on stories from the past week (and beyond) at the Slashdot story archive

 



Forgot your password?
typodupeerror
×
The Internet Your Rights Online

ICANN Meetings 43

ICANN's next meeting will be Nov. 13-16, 2000, in Marina del Rey, CA. The Internet Democracy Project is conducting a meeting of At Large members on the morning of Sunday, Nov. 12, same location, so you don't have work as an excuse to miss it! The new At Large directors will be speaking at the meeting. Following that, the Berkman Center will have its own meeting examining intellectual property and the proposed new TLDs, and they've helpfully provided a set of background materials if you're not quite current with the issues. Note that ICANN "updated" their bylaws to prevent the newly elected directors from actually taking part in the ICANN Board meeting next week - they won't take office until just after all the new decisions about TLDs, etc., which will be made by the unelected directors, so it is very, very important to have some public participation since there aren't any public advocates on the board.
This discussion has been archived. No new comments can be posted.

ICANN Meetings

Comments Filter:
  • by pongo000 ( 97357 ) on Friday November 10, 2000 @06:12AM (#632691)
    Then do something about it. Support OpenNIC [unrated.net].
  • So when will CmdrTaco get his hands on the .dot TLD? Will we have to go to http://slashdot.dot after that? Will the abbreviated form of Slashdot also include /...?

    Only time will tell...

  • Hey just remember, as my user ID is 70 lower than yours, I am 70 times more intelligent than you.
  • It's this pathetic need to group things that gets us to a point whre some genius says if we don't make an adult TLD then adult doesn't exist.

    Which in the case of the other sense of adult as someone over the age and maturity of an 18 year-old ends up being what is created.

    Adult maturity disappears yet adult content remains.

  • self-serving my ass. If they had been self-serving those fools would take a break breaking from being asses long enough to enjoy their servings. I hardly think there's anything in particular they want for themselves.

  • Well, I certainly am biased, since I live a few kilometers away from Dubai Internet City [dubaiinternetcity.com] (Dubai, UAE).

    I do think, however, that they propose a good idea with the ".go" TLD. It has a nice ring to it, is two letters long, and they have the resources to make it a success.

    Just in case you are interested, Dubai Internet City is the brain child fo Dubai's government. It is a free-zone metroplitan built just for internet and media companies.

    I am not related to the city in any way, other than living in Dubai.. but I think it would be great if this TLD was awarded to Dubai Internet City, as they are trying to be an e-commerce physical and cyber hub for the region between Malaysia and Africa (~1.2 Billion pop).

    Here is their proposal [icann.org] and here is the ensuing ICANN discussion. [icann.org]
  • by The Man ( 684 ) on Friday November 10, 2000 @06:39AM (#632697) Homepage
    If there's a problem, we should fix it ourselves. And once the problem has been fixed in an actual implementation, then it will become a standard of its own right.

    So what's this solution? Alternate root servers. Such a scheme might work like this:

    • I set up an alternate root server at foobazco.org. This root server functions as a "gateway" root server in that it's a root server in the alternate network but also has a name in the old network.
    • I make and distribute freely a cache file appropriate for my new root server(s).
    • I/the users of the new network set policies for name registration that actually make sense (reasonable people can disagree, but I'm sure it'll be better than what ICANN has done).
    • Users of the alternate network switch to the new root servers and register names in the new TLDs.
    • The new root servers allow access to the old network by adding a .x extension. So for example, what's now known as mycompany.com would be accessible as mycompany.com.x.
    • Conversely, users of the old network could reach the new network by appending .foobazco.org - or simply adding foobazco.org to their search path.
    • Everyone gets tired of typing the extra stuff and the old network goes away.
    • Somebody writes an RFC on the new network to make it official.

    So, what do you think? Is this viable? It doesn't require any significant amount of work on the part of sysadmins or users, and in fact it'd be pretty easy to implement here. The only problem I see is getting people to use it, especially the corporations that are abusing the current system to their advantage. The solution to this, I think, is to make sure that the new ruleset offers something for everyone. I would suggest one set of TLDs, one per broad trademark area (media, retail, food, networking, hardware, software, etc.), in which you must hold a trademark in the relevant area to register it, and one set of TLDs in which registration is strictly FCFS. Registration in the trademark-protected TLDs would be expensive, say a one-time $500 fee for legal costs of verifying the trademark. This would be worthwhile, however, because the registrants would know that their property is being protected by us, saving them legal fees down the road trying to take away names from non-trademark holders. At the same time, registering in the non-trademark TLDs would mean that nobody could ever force you to give up your name, and would be much less expensive since no legal research would ever be needed. Registration in this part of the namespace would also be quite inexpensive, maybe just a few dollars a year.

    The way I see it, this would offer something for everyone. Trademark holders will have access to a set of TLDs in which both they and the consumers will know they're getting the real thing, breeding confidence in one another and thereby encouraging people to do business. The traditional non-commercial Internet will be equally well-represented in the borderline-anarchy of the non-trademark TLDs. Registrants in this area will be permitted to register any names they like, and consumers should be discouraged from doing business with them. The point of this system would be that there is a place for everyone and no reason for protection of trademarks to be in conflict with the spirit of the Internet. While more TLDs in the current system might help, I think it's unlikely that corporation-run ICANN would ever really accept the idea of no trademark protection for registrants in any TLD.

    I'd say this is an RFC, but I haven't implemented it. So instead please consider this a Request for Discussion. :-)

  • I see why you believe that this system would offer something for everyone to get them to use it instead of the existing system. I just don't think you've got enough bait to get the corps to use it. They already have a small set of TLDs in which their trademarks take precedence over just about anything (at least according to WIPO). Yeah, they lose one every now and then, but for the most part, they get what they want. I don't see them wanting to move to a new system unless the old one really starts going against their will, and if that happens, then regular users will be more content to stick with the old system rather than switching to a new one.

    Next there's the issue of how to govern the thing. Are you proposing a new ICANN-type body to settle disputes and make policy? I can see this being done in much better ways than the existing organization does things. I just don't see corporations being interested in a more open, democratic ICANN. They like the closed, unaccountable ICANN because it's easier to influence with money and favors.

    I also don't think they'd like the idea of the FCFS TLDs. They consider their IP to be sacrosanct and I doubt they'd want to switch to a system where someone could register VerizonSucks.com AND be immune from a lawsuit.

    Then there are also legal issues. What would NSI do if they had the carpet pulled out from under them? Would the new governing body allow anybody to register domains? License registrars? How would it work? What existing laws could NSI use to put a stop to it?

    There are probably many other issues I haven't even though of yet (this was written after about 5 minutes of thought, and it probably shows :-). If an RFC was to be written, it needs to address all of these things. By all means though, let's discuss it.

  • God will forgive you.
  • You MUST register domains of the form organization...us Why on earth would anyone who wants to get trafic to their web site agree to such a long domain name. Plus, you can't even register domain names from a central location... you have to go to the people who registered the locality level (ie your city or town).

    If we had a sane system like the rest of the world for our own tld system maybe you'ld see more of them.

  • - stop yapping and start putting your honest concerns into legible language and explain them to ICANN's Chairwoman? I mean, I have mailed her several times, made suggestions, complained [pretty often] and she actually replies, explains and advises proper cause of action, etc.

    So, stop this mob-rule rampage when you talk about ICANN until you have at least tried to mail her your concerns. Don't you think this is very much the right thing to do?

    Sometimes, fellow slashdotters, you behave pretty much exactly like those imbeciles who keep calling tech support because they can't be bothered to RTFM.

    I like to let off steam, too - but alas, you could use that energy and your well-above-average intelligence to try to make a difference by telling ICANN what you think. Maybe, just maybe - if enough of you actually submit constructive critique and make workable suggestions, they might actually listen. Remember, ICANN doesn't realy make money from corporate sponsors - so their main interest is to keep the net running and getting all those yelling techies to write them their thoughts.

    Okay, now, I trust that you will NOT {P_L_E_A_S_E) start spamming or flaming her - PLEASE -
    The e-mail of the Head of ICANN is: edyson@nospam.edventure.com
    [delete the 'nospam']
  • Seems you missed the boat?

    ICANN is actually the 'Mother of all CANNs' and everyone - from anywhere - could register to vote for the 'publicly elected' portion of the ICANN reps.

    Further, every country has it's own organization, the countryNICs, which issue/assign/sell/register country level domain names. Usually the first step to get involved is to contact your countryNIC, while also visiting the ICANN site [which I bet most of the posters haven't done] and check out how you [and everyone else] can actually try to get invoved...
  • Since DNS servers are configured, ultimately, to query the root servers for name service, couldn't you just put ?I?different?/I? server IPs in first, to point your named (or whatever, flames to /dev/null) at these other servers??P? In other words, to hell with ICANN - let's make a new DNS. For instance, why couldn't you just make up a .cool TLD, and make the "root" server for it. Then have people list you in their root server lists, and when their queries with the real DNS fail, they'll check yours out.?P? Or, just add DNS servers on your clients. Say I come up with a .sux domain, and run a DNS server. Just tell your friends to point their clients DNS at "real" DNS first, then me 3rd or 4th (or whatever). Then I could "register" micros~1.sux as a domain name, and eventually your clients would find it.?BR? Sort of like ?a href="http://www.dyndns.org"?DynDNS.org?/a? does it.
  • More than half of your fellow Americans could give you an excellent reason to miss a Sunday morning meeting. It's even traditional, good for the soul, and contributes to your overall well-being.

    It's called "sleeping in."

    Interrobang, who is never out of bed before noon on a weekend if it can be helped.
  • That would be great wouldn't it. .slh maybe? hehe

    The Neo Minder!!!
    -----
    A C64 with a 300 baud modem!! WooHoo!!!
  • by Anonymous Coward
    The problem with .us domains is the fact that they also require a 2nd level, and in many cases 3rd level, domain before you even get to the actual domain name. It makes .us domains wholelu unmemorable, and pretty useless for general usage. Hence the number of American .com domains that really should be .us...
  • Since DNS servers are configured, ultimately, to query the root servers for name service, couldn't you just put ?I?different?/I? server IPs in first, to point your named (or whatever, flames to /dev/null) at these other servers.?P? In other words, to hell with ICANN - let's make a new DNS. For instance, why couldn't you just make up a .cool TLD, and make the "root" server for it. Then have people list you in their root server lists, and when their queries with the real DNS fail, they'll check yours out.?P? Or, just add DNS servers on your clients. Say I come up with a .sux domain, and run a DNS server. Just tell your friends to point their clients DNS at "real" DNS first, then me 3rd or 4th (or whatever). Then I could "register" micros~1.sux as a domain name, and eventually your clients would find it.?BR? Sort of like ?a href="http://www.dyndns.org"?DynDNS.org?/a? does it.
  • ...so I could fly out to CA right now to attend this meeting.

    In all seriousness, this is a great opportunity...I urge anyone who can attend to do so. The ICANN has way to much power with too little non-giant-corporate influence as it stands for this meeting, and any sort of public effort to protest and maybe force them to NOT fuck over most everyone on the TLD issue would be great.
  • ps .dot is in there! Submitted by a group called Neustar, Inc. [neustar.com], who are one of the applicants that merit further review (although .dot isn't their preferred string - .web is (how lame)).

    http://slashdot.dot here we come!

  • You fucken idiot, Jon Erikson is NOTHING like me. While Jon puts much information is his posts, my style was vapid and uninteresting. While Jon is constantly adding insight and thoughfulness to discussions, I only took away from the system by spouting noise and whining. In fact, you and I are a lot alike, did you know that? And for some bizarre reason, I am sure that you are as much of a fucken ignoramus in real life as you portray yourself on this web page.

    +1 bonus here, yup. I used my +1 just to flame you you Goddamned worthless piece of shit.

  • by Anonymous Coward
    I've looked at his prevous posts, he is a troll!

    Jon Erikson is a cancer eating the at the heart of Slashdot. He is endangering SLashdot's purity of essence!

    we must hound Taco via email and irc until he releases Je's IP addy.

    We Must hound JE's ISP, college or employer until they release his identity.

    We must not stop until JE is punished!
  • I dunno, they have sunday evening services here...

    ---------------------------------------------
  • ...although I'm suprised to find that half of all Americans enjoy fucking the skull of yoda as well.

  • To be fair for everyone, we should all have Unicode everything, including domain names. Hard disk capacities have grown so quickly that a 150-200% of bloat resulting from UTF-8 adaptation is minimal...

    And...I can't wait to use an 100%-Unicode Linux distro. Is anything like this going on?
  • What we need is a tld named "".

  • Someone needs to goto the timeout corner.

    BAD LITTLE SLASHDOT POSTER, BAD!

    *HUG*
  • In fact, several such alternative root registries already exist. (See, for example Alternic [alternic.org], Name.Space [name-space.com], OpenNIC [unrated.net], and eDNS [edns.net].) The problem is that there's not a critical mass of people converting to any one of them. These systems also threaten the uniqueness (if the same TLDs are set up on competing root servers), universality (the same URL should resolve to the same site for everyone, and everyone should be able to access all URLs), and technical stability of the DNS namespace. DNS cache leakage is a compounding factor.

    The DNS is not like open source software; you can't fork it and make a version of it that you like better, and let people chose which one they like best. It is (at the moment) a shared global resource. Sure, lots of people grumble about ICANN's handling of the expansion process. But the community of name server administrators and owners has consistently recoginized that the dangers of fragmenting the global name space outweigh the likely benefits of doing so.

    --Beland

  • You would, however, miss church. When are people going to realize that this kind of attitude contributes to the overall moral decline we've been seeing in the last 30 years?

    Whoever moderated this up as "insightful" needs a good, hard bitchslap in meta-moderation (and a counter moderation from someone with such priveleges today). Posting this kind of religious nonsense to a secular, intellectual and scientific discussion forum is flaimbait of the most classic and cliched kind, a practice as old as the 'net itself.

    "OFFTOPIC" "OVERRATED" or "FLAIMBAIT" would all be far more appropriate descriptions than "insightful" in this context. If one must feel positive about such trolling, the only defensible stance would be "FUNNY." But insightful? Hardly, by even the most liberal definition.
  • richard@ns1.vrx.net Sat Nov 11 10:53:13 ~
    % dig dot txt

    ; > DiG 8.1 > dot txt
    ;; res options: init recurs defnam dnsrch
    ;; got answer:
    ;; ->>HEADER- opcode: QUERY, status: NOERROR, id: 6
    ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 3, ADDITIONAL: 3
    ;; QUERY SECTION:
    ;; dot, type = TXT, class = IN

    ;; ANSWER SECTION:
    dot. 6D IN TXT "Christian@Nielsen.NET, Feb 96"

    ;; AUTHORITY SECTION:
    dot. 6D IN NS AARDVARK.WR.UMIST.AC.UK.
    dot. 6D IN NS NS1.OP.net.
    dot. 6D IN NS matterhorn.nielsen.net.

    ;; ADDITIONAL SECTION:
    AARDVARK.WR.UMIST.AC.UK. 1d23h46m40s IN A 130.88.146.3
    NS1.OP.net. 1d23h46m40s IN A 209.152.193.4
    matterhorn.nielsen.net. 1d23h59m49s IN A 216.32.171.152

    ;; Total query time: 3 msec
    ;; FROM: ns1.vrx.net to SERVER: default -- 199.166.24.1
    ;; WHEN: Sat Nov 11 10:53:24 2000
    ;; MSG SIZE sent: 21 rcvd: 205

  • we used to have a similar problem with the .ca namespace, but now that's been deregulated.
    Since it looks like ICANN is being totally anal, why don't you guys deregulate your .us namespace.
    you could keep the conventions of other countries, such as using .com.us/.co.us type namespaces.

    I agree that www.mysite.smalltown.somestate.us
    is a bit of an ugly url, but just petition the .us nic to open this up, it might have made sense to keep things hierarchically organized like this in the past, but this is the 21st century after all.

    just a thought
  • Ha ha ha ha ha...

    Oh well, at least they let you use 'fucken'. :)
    ---
    pb Reply or e-mail; don't vaguely moderate [ncsu.edu].
  • The acrimony between ICANN and its legions of critics is as thick as the peanut butter on a two-year-old's sandwich. Truth is, ICANN has manufactured most of its own troubles, starting with a stupefying bent toward secrecy, while pledging to operate in a spirit of consensus and transparency.

    --

  • by Anonymous Coward
    ..since I am not in the US. Is there anything similar for those of us in countries that can organise an election?
  • How will the fact that the elected officials are not allowed to vote in the important TLD matter doesn't really vouch for the transparency of the ICANN.

    Why don't they vote? Is it because the might be "unfamiliar" with the issue at hand? I hardly think so.
    Now could it be because they are unfamiliar with the decisions that the ICANN has already been loobied into making?

  • by wodelltech ( 168047 ) on Friday November 10, 2000 @04:31AM (#632726)
    "...the morning of Sunday, Nov. 12, same location, so you don't have work as an excuse to miss it!"

    More than half of your fellow Americans could give you an excellent reason to miss a Sunday morning meeting. Out of curiosity, have we ever had a poll here to determine the demographic makeup of /.?
  • Ugh, if there has ever been an example of how not to run an organisation, ICANN has to take the prize. Despite their promises of openness and accountability, they have been a rediculous parade of corporate pimping and self-serving behaviour.

    And this decision to update their bylaws to exclude the at-large members from the TLD decision is yet another example of how they've cunningly organised this whole thing as nothing more than an exercise in public relations, an attempt to shut people up about how crap they are.

    The at-large members, although they may be the greatest people in the world, just aren't going to make a bit of difference in what ICANN is or does. The positions were created to act as a sop to disgruntled netizens, and even then the contest was rigged to ensure more corporate frontmen would join the board. And the suprising thing is, it seemed to work! People lapped it all up without realising the utter futility of the entire process.

    Unfortunately ICANN represents the worst excesses of the American corporate replublic, in that it puts business ahead of consumers. Quite frankly, ICANN sucks.

  • And the suprising thing is, it seemed to work! People lapped it all up without realising the utter futility of the entire process.

    People who do care have spoken up and still do. Most people just don't care, though. As usual. Anyway, I can't find this surprising: ICANN very well follows business and US government agenda and even pretends to be somewhat democratic to satisfy a liberal public.

    Unfortunately ICANN represents the worst excesses of the American corporate replublic, in that it puts business ahead of consumers. Quite frankly, ICANN sucks.

    Unfortunately the truth is very well expressed here.

  • by Stormie ( 708 ) on Friday November 10, 2000 @04:49AM (#632730) Homepage

    Hmm, having a bit of a poke around those links, I came across the applications for new general-purpose TLDs [icann.org]. There are applications from 14 groups, 7 of whom "merit further review" by ICANN, mostly suggesting a few new TLDs each.

    But one of the unsuccessful groups is a mob called Name.Space [name-space.com], who proposed 117 new TLDs! Including such gems as ".nyc" (New York is a country now?), ".jazz" and ".music" (jazz isn't music?) and ".ads" (hmm there's one to avoid).

    So I had a look at them - they're a firm that sell domain names in 546 new top level domains! All of the above plus such gems as .cow, .page and .2000 that they presumably thought were too daft to try to slip by ICANN. Anyway, you can register any of these for only $30 a domain! The fact that nobody is ever going to be able to access you via that domain name unless they set up to use Name.Space's rival DNS is tucked away in the middle of their FAQ where they tell you to spread the word, and get your friends and associates to connect to their DNS..

    What a bunch of maroons..

  • Hey, what's with the personal vendetta?

    Jon posts some of the most (+5, Insightful) articles I read on Slashdot.
  • ...we should all have Unicode everything,...

    That was my attitude, too, until a few months ago. Another Slashdotter pointed out to me, though, that Unicode isn't truly Free, so I imagine that would hamper efforts for a "100%-Unicode Linux distro".

  • You americans are so spoiled.
    You've got full control of the upper level domains, and then run amock with the process for it. Not that I support ICANN, I think you guys should give them the boot.

    But don't forget you guys still have your own country domain, just like the rest of the world - .us - lucky bastards =)

    When was the last time you ever saw a .us website? nobody pays it any attention, well maybe you should start taking advantage of the luxury of having this additional upper level domain space. go register some .us websites and give icann the finger. http://www.nic.us/ [www.nic.us]

There's no sense in being precise when you don't even know what you're talking about. -- John von Neumann

Working...