Slashdot Mirror


RIPE NCC Responds to ICANN CEO's Proposal

An anonymous reader sends in: "RIPE NCC (the European IP address registry) responds to the ICANN proposals for reducing their own accountability even further whilst spending millions of everyone else's money." ICANN will be meeting next week in Ghana - ought to be a feisty meeting.

52 of 146 comments (clear)

  1. Well at least someone's likely to get attention.. by dagoalieman · · Score: 2, Interesting

    It seems to me this could be a good thing, to open up the full flood gates of complaints towards ICANN. I mean seriously, I think almost every organization affiliated with them, plus many of us (cough /.) is just about fed up with them and some of the not quite brilliant things they're doing.

    Let's just hope this gets something rolling, because obviously our voices are next to unheard.

    --
    We don't need no Net Explorer We don't need no Thought control
  2. ICANN should have been gone long ago by afidel · · Score: 4, Interesting

    When they refused to create the .XXX TLD they showed complete disregard for the future of the net as a self regulating entity. If they had created an .XXX TLD then we could banish net nany, cyber sitter, government intervention "to protect the children" and many other anoyances in one easy swoop.

    --
    There are 4 boxes to use in the defense of liberty: soap, ballot, jury, ammo. Use in that order. Starting now.
    1. Re:ICANN should have been gone long ago by Knightmare · · Score: 3, Insightful

      To put it simply you are wrong. You mean to tell me that if they had approved a .xxx TDL that all the porn sites in the world would just change their domain names and live happily ever after quarantined in the .xxx TDL. No, you are out of your idealistic mind if you truly believe this. If you don't and were trying to be witty, then I look to the moderators and ask why oh why is this rated 4 (at the time of my post)

    2. Re:ICANN should have been gone long ago by demaria · · Score: 2

      So all the porn sites are going to be lumped together into one top level domain that's completely easy and 100% effective to filter against.

      I'm sure they'll jump on that possibility. After all, we have so much trouble trying to find porn on the net.

    3. Re:ICANN should have been gone long ago by thesolo · · Score: 3, Interesting

      Hear, hear!

      Jesse Berst first began talking about the ICANN and the .XXX domain proposal back in the spring & summer of 99. I remember thinking to myself, "Man, that is a great idea, I wonder why no one thought of it before."

      And yet, nothing came of it. Moving adult content to a .XXX server would be ideal for so many reasons, I fail to see why they wouldn't do anything with it. Is there any way to get that movement started back up?

    4. Re:ICANN should have been gone long ago by room101 · · Score: 4, Insightful

      Sorry, I don't think so.

      1. the porn sites aren't going to switch just because there is a .xxx tld.

      2. the ICANN can't/won't enforce any kind of consistency for consumer/civilian based tld. (that is, you won't be able to know for sure that a XXX site didn't try to "slip in" with a .com tld)

      The ICANN has been asked to create content-based tld before and they have refused because they don't want to play policeman. I for one agree, I don't want them to decide what goes on the web and what doesn't.

      --
      room101 -- how much can you stand before they break you?
      (they always break you eventually)
    5. Re:ICANN should have been gone long ago by dillon_rinker · · Score: 2

      No content based .TLDs...so they're doing away with .com (commercial content), .edu (educational content) and .mil (military content)?

    6. Re:ICANN should have been gone long ago by Bonker · · Score: 5, Insightful

      To put it simply you are wrong. You mean to tell me that if they had approved a .xxx TDL that all the porn sites in the world would just change their domain names and live happily ever after quarantined in the .xxx TDL.

      And you're an idiot.

      Pornographers were the ones arguing hardest for an XXX TLD during the TLD proposal a while back.

      First of all, you fail to make a distinction between real porn sites-- individuals and companies interested in selling explicit material to consenting adults-- and scam sites who are interested in trying to get as many eyeballs as they can, frequently with pornographic material.

      Real pornographers know that they are running location-independant businesses. That's why in the real world the best strip clubs and adult bookstores and novelty shops will always be outside whatever city limits you happen to live inside. They have less to worry about in the way of police interference, angry neighbors, and intolerant church groups.

      The intelligent ones *want* to be segregated. Because it is considered a 'vice', Porn is a unique business in that its customers will come to it rather than the other way around. Pornographers are interested in making money, not corrupting your children or your neighborhood's youth, regardless of what your religious leaders. They don't make money unless they sell to consenting adults. They make money off people who know what they want and know where to find it, and not people who 'browse' like you would in a department store.

      By creating an .XXX or .adult TLD, Pornographers get all the benifits of opening a store five miles outside the city limits while at the same time giving those who are intolerant to porn every opportunity to shut them out of the 'communities'. Parasitic scammers who try to lure people to illigitamate sites would quickly find themselves without the stronger, legitimate pornographers to shield their activity, and fade away.

      Now, I'm not saying that Porno is not a dirty, manipulative business without a lot of problems. Most of that, however, is due to the same kind of neglect and intolerance that ICANN showed during the TLD fiasco. Look at the state of Nevada, which has legalized sex work to a great deal. Adult actors, models, and prostitutes in that state not only make more money than sex workers anywhere else in the world, but are also better protected from rape, STD's, harrassment, and abuse. If ICANN had approved the XXX tld, I can't help but think that would have had a little of the same effect on internet porn.

      --
      The next Slashdot story will be ready soon, but subscribers can beat the rush and slashdot the links early!
    7. Re:ICANN should have been gone long ago by Mnemia · · Score: 2

      I do agree with your point in that I don't want ICANN playing policeman to the domains, but then again, I think that if someone doesn't do that, there is really no point in having seperate TLDs at all...

      It doesn't have to be ICANN, they could give out the contract to run the TLD to a couple different registrars who would actually do the policing. Maybe we could simply move all the porn sites presently in .com into .xxx space. Something like that will have to happen if .com is going to return to any semblance of organization.

      If ICANN doesn't want the job of policing for content, they should've done a better job in the past of preventing the situation we now have where everything commercial is all in one TLD.

      And, I think that the porn sites would be more than willing to switch over (at least the legit ones). It could be a way for them to escape more onerous regulation and only serve their content to those customers who want it.

    8. Re:ICANN should have been gone long ago by Knightmare · · Score: 2, Insightful

      Actually I don't fail to make a distinction, I don't need to make a distinction. The intension of the company doesn't affect the impression such material could make on a child, which is what net nanny etc are (in theory) there to provide. Protection from such content, just because the "upstanding" (oxymoron?) porn sites move to .xxx wouldn't validate the original posters comment that netnanny wouldn't be needed. Please pay attention to the scope of the comment you are replying too.

      Because there are all the other sites out there that are either scams or just get a chuckle out of posting nude pictures of something on the web. Take the explosion of personal websites + cheap webcams in consideration. Do you really believe that every teenage girl that decides to do naughty things in front of a webcam is going to spring for a .xxx domain before doing so?

    9. Re:ICANN should have been gone long ago by Zeinfeld · · Score: 2
      Pornographers were the ones arguing hardest for an XXX TLD during the TLD proposal a while back.

      There are actually two distinct overlapping issues here. The first is do the pornographers want a .xxx domain, hell yes they do! It is a great advertising mechanism.

      The other issue is, will pornographers allow themselves to be confined to .xxx? Here the answer is absolutely not. They are not going to agree to any mechanism that supports censorship as long as there are politicians out there trying to outlaw their business entirely.

      Ponography is on balance a force for good. Look at what western society was like when the censoship gang were in charge, women had no rights over their bodies, not even the right to use contraception. As Simmone de Beuvoir pointed out, conservatives put women on a pedestal to control her, not to worship her.

      If we are going to effect change in the brutal regimes of the muslim world pornography is the best tool we have. The dictators of Saudi Arabia are rightly fearful of the effect of sack loads of Western porn comming through the Internet.

      --
      Looking for an Information Security student project suggestion?
      Try http://dotcrimeManifesto.com/
    10. Re:ICANN should have been gone long ago by Zeinfeld · · Score: 3, Insightful
      It doesn't have to be ICANN, they could give out the contract to run the TLD to a couple different registrars who would actually do the policing.

      The mind boggles.

      It appears that you would have the .xxx registrars carefully check the sites in their domain to make sure that they all had sufficiently pornographic content. While I could see that VeriSign could probably find a willing army of applicants eager to perform that task at minimum wage I cannot see what purpose would be served that could not be served by a quality control association such as the Germans set up in response to complaints of insufficiently hard core porn.

      What I suspect you mean is that companies in the dotcom domain should be scanned to see if they have porno content up. That is a considerably harder prospect and you would not find registrars willing to do it without a substantial increase in the registration fee.

      Maybe we could simply move all the porn sites presently in .com into .xxx space. Something like that will have to happen if .com is going to return to any semblance of organization.

      Why on earth does there have to be any semblance of organization in dotcom? There is no technical reason for having the namespace partitioned at the toplevel. The DNS could be run perfectly well if registrations were offered into the root directly. It would require considerably more resources than it does at present but it is certainly feasible from an operational point of view. There would still be hierarchy but that would happen below the name you registered. So slashdot could use www.slashdot as their web address if they chose, or they could use just slashdot and a NAPTR record.

      --
      Looking for an Information Security student project suggestion?
      Try http://dotcrimeManifesto.com/
    11. Re:ICANN should have been gone long ago by room101 · · Score: 2

      Sigh,

      for consumer/civilian based tld

      That is, .edu, .mil, and .gov (forgot one) are not consumer or civilian based tlds. This is my definition, but I find it good enough. Basicly, anyone that can get a tld can choose between .net, .org or .com, they don't really care in most if not all cases.

      Hope that clears up my points.

      --
      room101 -- how much can you stand before they break you?
      (they always break you eventually)
    12. Re:ICANN should have been gone long ago by Ami+Ganguli · · Score: 2

      Ok, I know this is off-topic, but...

      What do you perceive the effect of porn to be on children? I have a vague recollection of stumbling on some porn when I was a child, and it didn't traumatize me. I was curious for about 30 seconds, and then decided it was boring and a little gross. Kids are like that.

      Right now I'm living in Finland where there's tons of porn on regular late-night television. Kids aren't going to be exposed to the stuff constantly (it's past their bedtimes), but I'm sure they all see it occasionally. It doesn't seem to have much effect on them.

      My conclusion is that it's the parents who are traumatized by porn - kids just couldn't care less.

      --
      It is tempting, if the only tool you have is a hammer, to treat everything as if it were a nail. - Abraham Maslow
    13. Re:ICANN should have been gone long ago by room101 · · Score: 2

      Yep, I agree with most of this. I say that they either do a good job of policing the tld's, or they just don't bother, making tld's meaningless, which isn't a totaly bad thing, just different.

      I wish we could fix this mess.

      --
      room101 -- how much can you stand before they break you?
      (they always break you eventually)
    14. Re:ICANN should have been gone long ago by Archfeld · · Score: 3, Insightful

      So...what qualifies as a pornographic site ? Nudity ? Does this include medical sites ? Art sites with nude paintings ? How about sites that just tell obscene jokes ? What if "jenny cam" gets a bit racey some night ? Might as well call for a board of censorship to judge the content of all web pages. While I can see your point, I think you've failed to think through some of the consequnces of being human, frail and ultimately corruptable.

      --
      errr....umm...*whooosh* *whoosh* Is this thing on ?
  3. In Ghana? by Coward+Anonymous · · Score: 4, Insightful

    And this is because Ghana is a world Internet power, right?

    For kripe's sake, just look at their "meeting" calendar - it looks like a travel agency billboard.

    What additional proof do you need that ICANN is into frittering other people's money for their own entertainment?

    1. Re:In Ghana? by Alkaiser · · Score: 4, Insightful

      They reason they meet in obscure locations is because everyone who signed up to vote and stuff gets to vote at meetings. If they have them where you, me, everyone in the pissant public can't get to, then they pretty much eliminate the possibility of people discussing pertinent things at their meetings, and instead get to wonder, "What the heck do you call people from Ghana? Ghana-reans?"

      Then they'll vote on it and go home.

      --
      Netjak.com independent reviews of domestic & import video ga
    2. Re:In Ghana? by SubtleNuance · · Score: 3, Insightful

      And this is because Ghana is a world Internet power, right?


      Um, they are going to Ghana hopefully because* ICANN is meant to serve as a World Body, the International Congress of Nations. Which the honourable and respected nation of Ghana is a member.

      Holy-f'ing-christ, do you two (this and a post below) not realize just how myopic and jingoistic your posts are(!!)?

      *PLUS the Plutocratic-whore$ of ICANN love a good boon-doggle, Im sure it wasnt hard to sell to themselves (who would probably align with the mindset/thinking, with-regards-to Ghana, as the two of you.) a fun trip to that backwards-3rd-World Ghana.

    3. Re:In Ghana? by 4of12 · · Score: 2

      Um, they are going to Ghana hopefully because* ICANN is meant to serve as a World Body, the International Congress of Nations.

      I'm glad you explained it.

      Here was me, clueless, wondering if Ghana was going to become the country of choice for "registration of new TLDs" due to cozy licensing and restriction terms.

      That is, they're jealous of Liberia getting to register all those supertankers, freighters and cruise ships in the maritime industries and wanted to make sure that they got a cut of the new pie, having missed that old one.

      Imagine those newly-registered, lumbering Ghananian-registered Pr0n sites on the high seas of the Internet, running aground and leaking due to lack of stringent registration requirements...

      --
      "Provided by the management for your protection."
    4. Re:In Ghana? by Rupert · · Score: 2

      Ghanaians
      GahNayAns
      I never learned to spell phonetically. Sorry.

      --

      --
      E_NOSIG
    5. Re:In Ghana? by Ho-Lee-Cow! · · Score: 2
      Nope. Sorry. Holding the meeting in Ghana is designed to keep the public at large and other interested parties out of the ICANN Star Chamber. ICANN has proven absolutely ineffective at being anything other than a political whore to the interests of the Corporate Plutocracy that wants to take the internet away from everyone.

      It's really good to see that RIPE NCC is standing up to these losers.

      --
      In space, no one can hear you moo.
    6. Re:In Ghana? by mzito · · Score: 2

      A better reason is that ICANN wants to demonstrate that it wants to be representative of the whole world. If they meet only in the US and EU, then they're Euro-centric, but then they meet outside of the US, and they're trying to party it up in Africa....can't have it both ways.

      Also, one of the heads of the steering committee (I think - one of the heads of ICANN, anyway) is from Ghana.

      Thanks,
      Matt

      --
      me@mzi.to
  4. Oops... by Schwamm · · Score: 3, Informative

    Finally, let us say that we are quite surprised by the way this proposal was published. The document contains proposals for change of such fundamental scope, in a field that is of utmost importance to our community, that we wish that you had discussed these with us beforehand.... Seeing that you are proposing fundamental changes to ICANN and the principles behind the ICANN - RIR MoU, signed in 1999, we believe that in the interest of our members, we have to thoroughly re-assess our relationship with ICANN.

    We are looking forward to discussing these issues with you at the earliest possible opportunity.


    In general, it's a good idea to let the people you're working with know things before you make them public.

    ICANN can't like how the note ends... The tone makes it sound like it's buh-bye for ICANN...

    1. Re:Oops... by Amazing+Quantum+Man · · Score: 2

      I love it. It's "Dudes, you don't have all the power you think you have. You'd better play nice, or we'll take our ball and go play somewhere else."

      Someone's been needing to tell this to ICANN for a long time.

      --
      Fascism starts when the efficiency of the government becomes more important than the rights of the people.
  5. an issue of fault tolerance... by dj_whitebread · · Score: 4, Interesting
    Binding them contractually to one entity, ICANN, would create a single point of failure, possibly subject to capture.
    This is a fabulous point. From a technical standpoint, one of the fault tolerance features of the internet is its inherent sense of "multiple backups." Abstracting this to the organizational side, it becomes clear that to put all of the power into one group's hands is a weakness. There should be one standard way of doing things, but several different groups doing it.
  6. ROFLMAO by Dr+Kool,+PhD · · Score: 5, Funny

    FOUR acronyms in the story title. Compared to three non-acronyms. That's some kind of record, IIRC.

  7. Uh...Ghana? by waldoj · · Score: 5, Funny

    This is a country with 8,000 Internet users, 110 hosts, 82 domain names, 4 ISPs and a 2,048bps connection to the outside world. They don't have much going on.

    So, why are they meeting in Ghana?

    -Waldo Jaquith

    1. Re:Uh...Ghana? by qslack · · Score: 4, Interesting

      Maybe it's to foster the growth of the Internet in Ghana?

      Imagine how much richer the Internet would be with a whole new set of opinions from Africans and members of other countries that are currently too poor to offer their citizens the Internet.

      Not everyone in Africa is starving, some live like "normal" people. The Internet might just bring in commerce to end the starvation in Africa, too.

      It's not completely pointless to meet in Ghana!

    2. Re:Uh...Ghana? by dillon_rinker · · Score: 2

      Imagine how much richer the Internet would be with a whole new set of opinions from Africans...Not everyone in Africa is starving, some live like "normal" people

      Your prejudice is showing. That's right, folks, not EVERYONE in Africa thinks like a third-worlder...some of them think just like you and me! Imagine how much richer the world would be if we could communicate with "normal" people in Africa without actually having to see how funny-looking they are! (Oh, and for the humor impaired...&lt/sarcasm&gt)

      The Internet might just bring in commerce to end the starvation in Africa
      News flash...Africa can produce enough food to feed Africa. Governments who control the food supply can control the population.

    3. Re:Uh...Ghana? by Zeinfeld · · Score: 2
      This is a country with 8,000 Internet users, 110 hosts, 82 domain names, 4 ISPs and a 2,048bps connection to the outside world. They don't have much going on

      The UN does not find it necessary to spend as much time globe trotting, in fact they do most of their work out of their NYC and Geneva hubs.

      Most people in the third world would probably prefer to have meetings at places that are near to first tier air connections. Cairo is much more accessible than Ghana if you are going to have a meeting in Africa.

      --
      Looking for an Information Security student project suggestion?
      Try http://dotcrimeManifesto.com/
  8. Re:run you r own nameservers by Snootch · · Score: 4, Insightful

    Screw ICANN. DNS itself is a bad idea, anyway, recentralising a decentralised network...

    Hmm...and how exactly would you look up a web server's address? I know, remember an IP for each host you'll ever visit, and get that IP in the first place from...well...good question, isn't it? Even the old HOSTS.TXT file was centralised, and, by your logic, a Bad Thing.

  9. My biggest annoyance with the ICANN by Kiwi · · Score: 5, Interesting
    My personal biggest annoyance with the ICANN is that they have been dragging their feet with regard to support for internationalized characters in domain names. The problem is this: Domain names traditionally only had English language letters [A-Za-z] and the '-' symbol as part of domain names. (The '.' character signifies a delimiter in domain name labels; it isn't there in the DNS packet sent over the wire.)

    The problem with this is that this has a western-centric point of view which does not take in to account the writing systems that foreign languages use.

    Now, the ICANN was in a position to officially push forward some specification, any specification to allow international characters in domain names. Unfortunatly, they were too busy spending million of dollars on international conferences, staying in five star hotels, to actually do anything about this problem.

    International domain labels work right now with current DNS servers and DNS client software. One can type in, say español.example.com in Mozilla, and MaraDNS, not to mantion DjbDNS, will correctly resolve this domain name. The trick: Mozilla uses UTF-8 to encode international characters in domain names, and both MaraDNS and DjbDNS can handle domain names with UTF-8 characters.

    - Sam

    --

    The secret to enjoying Slashdot is to realize that it should not be taken too seriously.

    1. Re:My biggest annoyance with the ICANN by Merry_B.Buck · · Score: 3, Informative
      My personal biggest annoyance with the ICANN is that they have been dragging their feet...
      Well, the RIR's (APNIC, ARIN, and RIPE) can certainly handle policy without dragging their feet. Check out ARIN's last trustee meeting:
      >John Curran called the meeting to order at 10:20 a.m. EST.
      [new officers elected]
      [multihoming and address space issues decided]
      >Scott Bradner moved to adjourn the meeting at 10:40 a.m. EST.
    2. Re:My biggest annoyance with the ICANN by room101 · · Score: 2

      But the problem is, what happens when I want to go to a site in a different language, but the URL has chars that aren't even in my code page? What do I do then? Yes, I won't understand the page, but I can sometimes translate it using tech found on the web; but if I can't even type in the address, it is lost to me. And there is no way I can have all of the characters of all the character sets active at once. What's more, I couldn't remember what those characters were.

      My point is that these should have some common denominator when it comes to URI elements. Maybe [A-Za-Z] and - isn't the right thing, but it isn't too bad either.

      --
      room101 -- how much can you stand before they break you?
      (they always break you eventually)
    3. Re:My biggest annoyance with the ICANN by dvdeug · · Score: 2

      Yes, I won't understand the page, but I can sometimes translate it using tech found on the web; but if I can't even type in the address, it is lost to me.

      Ever heard of cut and paste?

      And there is no way I can have all of the characters of all the character sets active at once.

      Welcome to the 21st Century! It's called Unicode (UTF-8 being one encoding thereof that was mentioned in post you responded to), and Windows NT and BeOS supported it inherently, and MacOS and Linux have been getting increasingly better support of it.

      What's more, I couldn't remember what those characters were.

      Then you probably weren't their audience. Yes, if you want an international audience, then you don't have a name that most people can't enter. But if you are a small computer shop in downtown Tehran, and the last time you had a customer that didn't speak Farsi was 1973, then why not get www..com?

    4. Re:My biggest annoyance with the ICANN by dentin · · Score: 2

      Think twice before you wish for this thing. One of the beauties of the net as it stands is that I can get to anywhere I want to go, just by typing in a small amount of stuff in the location bar. The small allowed character set means that the urls stay accessible for all languages, and that everyone can type them.

      Think for a minute - how am I going to go to a chinese site if I am on an american keyboard? Suppose I know how to read german, but don't know how to type an umlaut? By giving out bastardized urls that only a small subset of the population can even type, you break the internet into cliques based on language, even more so than they already are. In my mind, this defeats the purpose of a net that everyone, everywhere, can use.

      URLs and URIs should contain only characters from a small, standardized set. The english alphabet plus a few other symbols is already the defacto standard, and while not perfect I see no point or advantage to anyone in changing it now.

      -dentin

      --
      Alter Aeon Multiclass MUD - http://www.alteraeon.com
    5. Re:My biggest annoyance with the ICANN by mzito · · Score: 2


      The holdup on IDN is based in the IETF - the protocol standard for IDN has not yet been finalized, although chances are good it will be at the next IETF in a few weeks. It would be premature and equally bad for ICANN to declare a standard outside of the scope of the IETF, where standards are supposed to be made.

      And while Mara and Djbdns may support UTF-8 encoding within the DNS, as far as I know, that is not the IETF's proposed standard solution.

      Thanks,
      Matt

      --
      me@mzi.to
    6. Re:My biggest annoyance with the ICANN by karl.auerbach · · Score: 2, Informative

      I was on ICANN's original internationalized domain name committee. We pretty much decided to do whatever the IETF says to do. That still feels like an appropriate answer and is consistent with the notion that ICANN ought to merely coordinate rather than dictate technology.

      Although DNS is defined to be 8-bit clean, there are ancient relics in the standards about how some names have to be in a reduced alphanumeric plus hyphen character set.

      What scares me is this: There are a lot of DNS engines out there that might be surprised to suddenly find characters outside of that character set. And some of these engines are in surprising places - firewalls, NATs, web caches, etc. I had an experience in which someone was tunneling audio via DNS UDP packets and for some reason a mongo sized Cisco in the middle was parsing those packets and crashing IOS.

      And internationalized names can creep in even when it appears that standard ascii is being used - imagine an ascii name that maps to an internationalized CNAME.

      I tend to agree with John Klensien that the best way to deal with things is to push for new things to be layered on top of DNS, thus making DNS largely invisible, and to try to get people to start being blind to the semantics of the DNS character strings. Sounds impossible until one realizes that the method adopted by the IETF - ACE encoding - will mean that we start seeing DNS names that look like bq--3kdhyekjayy.org floating around.

      Just wait until gethostbyname() sees some of these things - imagine a domain name that contains things like dots, nulls, asterisks, etc inside each of the DNS "labels". I'm dreding the day when I see see "rm -rf /" as a DNS label!

    7. Re:My biggest annoyance with the ICANN by gorilla · · Score: 2

      Even if the base OS doesn't understand it, browsers must understand Unicode nowadays.

    8. Re:My biggest annoyance with the ICANN by dvdeug · · Score: 2

      The small allowed character set means that the urls stay accessible for all languages

      Typeable, maybe. Understandable, no.

      how am I going to go to a chinese site if I am on an american keyboard? Suppose I know how to read german, but don't know how to type an umlaut?

      Ever heard of cut and paste? You're welcome to start up an IM or switch keyboards - most modern operating systems let you do that easily.

      Why shouldn't a computer shop in Tehran be www..com? You aren't part of his audience, so why should he have to mangle his shop name so you can access it easier? If you want to attract international customers, you use English names. If your site's only in Farsi, and your audience all speaks Farsi, why shouldn't you have a Farsi name?

      you break the internet into cliques based on language, even more so than they already are.

      Why? I entered www..com from a standard American keyboard. I won't be able to read that page, though, because it will most likely be Arabic or some other language using the Arabic script. Sure, I may be able to run it though Babelfish, and get some meaning out of it, but how did the name stop me from doing that?

  10. "NCC?" by Guppy06 · · Score: 4, Funny

    Am I the only one that thought of Star Trek when they saw that acronym?

  11. Re:run you r own nameservers by Aanallein · · Score: 5, Informative

    People are actually running their own nameservers outside of ICANN in a quite ordered way - there's a host of .ocean, .dot, .children, and similar top level domains out there - all you need to do is use one of those nameservers. Go take a look at OpenNIC - through which you can also use the top level domains from PacificRoot and AlterNIC.

  12. Spank! by jcr · · Score: 5, Insightful

    IOW, "Do your damn job, and quit trying to become a bloated government agency."

    Well said, indeed!

    -jcr

    --
    The only title of honor that a tyrant can grant is "Enemy of the State."
  13. Re:run you r own nameservers by MavEtJu · · Score: 2

    recentralising a decentralised network

    And where would you start to look for information?

    Right now there are 13 globally spread root-servers which know all the locations of the ccTLD and TLD servers. Without this piece of centralisation it will be hard++ to add new (cc)TLD, because everybody has to update their root.hints (or equivalent) file.

    Centralisation an sich is not good, but distributed centralisation is good.

    --
    bash$ :(){ :|:&};:
  14. Hold the meeting on the Space Shuttle... by dpbsmith · · Score: 3, Funny

    ...THAT should prove an effective barrier to those pesky would-be participants that don't have barrels of corporate money behind them...

  15. It doesn't scale by keithmoore · · Score: 4, Insightful
    This doesn't cause too many problems on a small scale. But if everybody picked his own root, it would be a disaster.

    If you want domain names (and URLs) to work reliably and consistently from one location to another, there needs to be some mechanism to sort out conflicts over the meaning of a name. That job is inherently fraught with controversy, because it will pit people with vastly different interests, cultures, and expectations against one another. I don't particularly like the result of UDRP, but the bottom line is that dispute resolution is a difficult job no matter how it's done.

    On the other hand if everybody picks his own root (or his own root search path) then URLs won't have the same meaning from one client to another, and instead of having ICANN handle disputes about who owns a TLD or SLD, we'll have the same disputes being handled by people trying to tell random users to change their root servers. or by interception proxies forced on users by ISPs. In some parts of the world there will be government edicts insisting that a particular root be used, with different roots required in different parts of the world.

    Granted that ICANN is seriously screwed up and that its current proposal is not a step in the right direction. But having one authority responsible for dispute resolution at the TLD level makes a lot more sense than inviting wide variation in the meanings of DNS names.

    RFC 2826 still says it pretty well.

  16. Re:Wow, plagIArizing my post to the letter. by danielrose · · Score: 2, Funny

    In fact, tosser, you will realise that I did not write the subject! It is a reply, and the subject is intact, as all good replies should be. Have a nice troll.

    --
    i hate pansy republicans
  17. wants their cake and to eat it too by cluge · · Score: 2

    RIPE was one of the parties pressuring ICANN because they couldn't guarantee the root servers.

    Now in this response they say "The so called "volunteers" operating the rootserver system are well funded and very well co-ordinated. Binding them contractually to one entity, ICANN, would create a single point of failure, possibly subject to capture. The current form of organisation works well, and is resistant to capture through the multitude of different operators and organisations housing and operating the servers. This system has been stable for many
    years. We think that to change it in the way you envision would introduce risks more important than any co-ordination benefits.

    Furthermore, we feel that you would do better not to burden ICANN with the task of financing the Root Server operating system. Rather, ICANN should
    stick to the core mission of coordinating them.
    "

    Interesting

    --
    "Science is about ego as much as it is about discovery and truth " - I said it, so sue me.
    1. Re:wants their cake and to eat it too by shani · · Score: 2, Informative

      RIPE was one of the parties pressuring ICANN because they couldn't guarantee the root servers.

      I don't think this is true. I worked at ARIN and now at the RIPE NCC, and frankly neither organization has ever really tried too hard to influence ICANN.

      The reality is that ICANN wants for the Regional Internet Registries (RIR's - meaning APNIC, ARIN, and RIPE NCC, and soon LACNIC) to sign an agreement with them. Currently, only a Memorandium Of Understanding (MOU) has been signed, to the effect that the RIR's agree that in principle a contract with ICANN would be a good thing. ICANN would benefit from a contract in two ways.

      First, they would get money. ICANN is always slavering for extra cash - something that should set off warning bells. This is a sticking point with me because the only thing the RIR's get from ICANN is allocations of big (/7 or /8) blocks of IP addresses, or blocks of AS numbers. This would take about 2 hours a month to administer. Nowhere near enough effort to justify the huge piles of cash ICANN wants from the RIR's, which are all not-for-profit companies.

      Second, ICANN would get increased legitamacy. Having support from the RIR's, which are inherently bottom-up, would go a long way to making the top-down ICANN palatable to the ISP community.

      There is a genuine place in the world for something like ICANN, but the lawyer-driven, power-hungry organization we have now is not the answer.

  18. No Way Man by dnoyeb · · Score: 2, Insightful

    No way pornographers want XXX. Why? They enjoy legal battles?

    Why? because now religious groups would leave porn sites alone and go after Comcast and AOL, etc. And you know DAMN well comcast would comply and block .xxx from its network. So would AOL. they do NOT want to be seen as porn advocates. Porn would suffer HEAVILY. Sure they would win their court battle, but it would be LONG and protracted and the whole world would be against them.

    They just dont need it. Well unless it came with guarantees that it would not get blocked.

    Dont get me wrong, its stoopid, especially since comcast has porn channels anyway. But you know how hyped the net is. Come election time, they would get roasted :D

  19. Someone explain to me... by Lendrick · · Score: 2

    ...how this is either a troll or redundant--since it was modded as both. I've never posted that message before, and I was defending myself.

    Go ahead and mod this one down too. How bout Offtopic?