Slashdot Mirror


ICANN Working Group Seeks To Kill WHOIS

angry tapir writes "An Internet Corporation for Assigned Names and Numbers working group is seeking public input on a successor to the current WHOIS system used to retrieve domain name information. The Expert Working Group on gTLD Directory Services has issued a report that recommends a radical change from WHOIS, replacing the current system with a centralized data store maintained by a third party that would be responsible for authorizing 'requestors' who want to obtain domain information."

155 comments

  1. not having read TFA by Tastecicles · · Score: 5, Informative

    Is the submitter trying to tell us that this third party is potentially a commercial venture intended to collect fees on $whois$ queries, which would also be dependent on giving a damn good reason for wanting to know who owns $domain?

    BTW, I think the headline is a: alarmist and b: misleading. It would be better written as "ICANN Working Group seeks to replace WHOIS."

    --
    Operation Guillotine is in effect.
    1. Re:not having read TFA by Samantha+Wright · · Score: 5, Informative

      Here's your answer:

      "Requestors" – people who want to query the data maintained by ARDS – would have to apply for the right to access domain information.

      Basically, they'd be extracting a licensing fee from the current people you go to for WHOIS lookups. Arguably this could be called "killing" WHOIS since it means taking away its... free spirit.

      --
      Bio questions? Ask me to start a Q&A journal. Computer analogies available for most topics!
    2. Re:not having read TFA by black3d · · Score: 5, Informative

      No specific word from the article on charges per se, however I don't think "seeks to kill WHOIS" is alarmist. The plan is to basically remove the WHOIS system, and instead have all the data managed by a "third party", to whom you have to apply to if you want any information on a particular domains ownership, rather than they automated system we have now.

      FTA:
      Access to the 'live' domain records maintained by gTLD registries would also be possible via the ARDS "upon request and subject to controls to deter overuse or abuse of this option". "Requestors" – people who want to query the data maintained by ARDS – would have to apply for the right to access domain information.

      --
      "The true measure of a person is how they act when they know they won't get caught." - DSRilk
    3. Re:not having read TFA by ukpyr · · Score: 1

      There is also an anonymously queryable subset of the records in the report. I haven't read the full report yet to see what that entails. Not saying it's super-duper, but it's not quite that bad.

    4. Re:not having read TFA by Anonymous Coward · · Score: 3, Interesting

      Is the submitter trying to tell us that this third party is potentially a commercial venture intended to collect fees on $whois$ queries, which would also be dependent on giving a damn good reason for wanting to know who owns $domain?

      This is going to make it difficult for visitors to a site, to let the site owners know, personally, that they've been hacked. Ive stopped two websites so far, from spreading viruses after they've got hacked due to using old joomla 1.2. Blackhole exploit redirects, i beleive the term is.

    5. Re:not having read TFA by icebike · · Score: 5, Interesting

      I'm fine with whois, even though it has been steadily degraded by private registrations recently.

      I'm not convinced there is any realistic reason this information needs to be private, although I might feel differently if i lived somewhere else in the world where angry armed mods drag you from your home for expressing a view point. On the flip side of that, simply knowing that your information is available tends to induce better behavior on the Web.

      But by and large, I think people should be able to know who owns a site, or who is fronting for the owner. It helps a great deal when trying to track down and report abuse.

      I rather suspect mine is not a popular view.

      --
      Sig Battery depleted. Reverting to safe mode.
    6. Re:not having read TFA by icebike · · Score: 4, Insightful

      If you have to have permission, you will certainly pay a fee, ig for no other reason than to pay the wages of the permission issuers.

      --
      Sig Battery depleted. Reverting to safe mode.
    7. Re:not having read TFA by houstonbofh · · Score: 1

      Here's your answer:

      "Requestors" – people who want to query the data maintained by ARDS – would have to apply for the right to access domain information.

      Basically, they'd be extracting a licensing fee from the current people you go to for WHOIS lookups. Arguably this could be called "killing" WHOIS since it means taking away its... free spirit.

      But how does my CLI pay the fee?

    8. Re:not having read TFA by Mitchell314 · · Score: 4, Funny

      Text-based 'punch the monkey' ads. Using nCurses.

      --
      I read TFA and all I got was this lousy cookie
    9. Re:not having read TFA by Anonymous Coward · · Score: 4, Informative

      It would be better written as "ICANN Working Group seeks to replace WHOIS."

      "ICANN Working Group seeks to monetize WHOIS..." is probably more accurate.

    10. Re:not having read TFA by Anonymous Coward · · Score: 0

      I rather suspect mine is not a popular view.

      It isn't, in fact, in Europe this practice would violate the law(s) there, especially in Germany.

    11. Re:not having read TFA by Anonymous Coward · · Score: 0

      I believe the presumption is that your CLI would request information from somebody who does pay a fee, who in practice would probably end up being RedHat or the FSF or somebody.

    12. Re:not having read TFA by Anonymous Coward · · Score: 1

      I'll tell you why mine are now private... I have had a domain for a long time (since 1997) and I didn't have any address to use other than my home.

      I'm postoperative transexual (we're talking two decades post-op at this time) I once had someone who knew of my past track me down online and make some very disturbing, homophobic, and personally unsettling statements and posted my home address and phone number (from using whois) encouraging others to express their similar disdain.

      Back in the late '90s, there wasn't nearly as much acceptance and tolerance for the B/T spectrum of LGBT.

      My point is there are indeed good reasons for private registrations even here in the US.

    13. Re:not having read TFA by braoult · · Score: 2

      And... Simple question, as non-USA citizen.

      Do you want to bet where the country managing it would be?

      I guess it will not be France, not China, nor... anything but US (why not PRISM directly? it would be clearer).

      Take the bet!

    14. Re:not having read TFA by AJH16 · · Score: 1

      While I'm not sure it is relevant to the article, I do agree with you that private registrations are bothersome though I know I personally don't ever completely trust a site with a private registration. I intentionally leave WHOIS open for the world to see on my sites, but then again, you can actually find my details on the About pages of most of them without even having to go to WHOIS. Anonymity on the web is more or less a myth anyway. A determined attacker can figure out who you are unless you take lots of special precautions, so why not make your info available to those who might actually have legit uses for it too.

      --
      AJ Henderson
    15. Re:not having read TFA by azcoyote · · Score: 2

      Personally I'd like WHOIS to be semi-private; public enough that law enforcement can find out who's who easily enough (just as the ownership of cars, houses, etc. is not private), but with some privacy so that I can express controversial views without it affecting my academic career. Parts of academia are very, very political, and people sometimes scour the Internet looking for dirt on their enemies.

      --
      Incipiamus, fratres, servire Domino Deo, quia hucusque vix vel parum in nullo profecimus.
    16. Re:not having read TFA by Jason+Levine · · Score: 1

      Knowing my information is available doesn't make me act better online because 1) my WHOIS contact information points to a PO Box that isn't even in the same town I live in and 2) the only people who seem to use my WHOIS information are those "domain renewal" firms that send me such helpful letters as "your domain is going to expire so 'renew' with us... [fine print]by renew, we mean switch your domain to us and pay much more than you currently pay[/fine print]".

      I wouldn't mind if there was some sort of check against abusing WHOIS information like these domain renewal firms do. Of course, I'd want to still be able to look up information without paying exorbitant fees. For example, if I find out that some content scraper posted my writings as their own (which has happened to me and my wife multiple times), the WHOIS information can give me someone to send a DMCA notice to. Perhaps looking up small amounts (one or two at a time) of website information would be free but looking up larger numbers (like the domain renewal companies do) would require payment.

      --
      My sci-fi novel, Ghost Thief, is now available from Amazon.com.
    17. Re:not having read TFA by Anonymous Coward · · Score: 0

      That's like my county saying I have to pay a fee to see when I have to arrive in court for my speeding ticket and they'll determine if I should receive such information (Of course I'll pay a bigger fine if I miss the date). Such nonsense needs to be combated at all times.

    18. Re:not having read TFA by Anonymous Coward · · Score: 1

      Personally I'd like WHOIS to be semi-private; public enough that law enforcement can find out who's who easily enough (just as the ownership of cars, houses, etc. is not private), but with some privacy so that I can express controversial views without it affecting my academic career. Parts of academia are very, very political, and people sometimes scour the Internet looking for dirt on their enemies.

      I keep seeing people say this, and I have to wonder if you and they have any idea what WHOIS does. It tells someone who owns an IP block, it doesn't say who is using it. For example, if you run a whois lookup on an IP which an ISP is assigning out to subscribers via DHCP, it doesn't tell you which subscriber is using the IP it tells you which ISP owns the entire block. If you personally own the IP scope you're using, you have direct control of what goes into the whois information (unless you're using a really shitty fly-by-night provider). For example, the whois info for my static IP block has valid contact information for me (a special address used only for that purpose) but the street address and phone number will lead to you the local homeless shelter, not my house or business.

      WHOIS is a very important tool used for tracking down who is responsible for an IP block, particularly when you don't have any direct relationship to that IP space. I see no good reason to mess around with it, and limiting access to the records is simply the wrong kind of thinking as it completely removes any valid reason for having the tool in the first place.

    19. Re:not having read TFA by Almost-Retired · · Score: 1

      One three word phrase applies here, "screw you ICANN" .

      Whois is the common users way of being able to throw an all encompassing blanket over the internet bad guys. But it sounds as if you want to lock that info up and hold it for ransom, available ONLY to the elites will to grease your palms for that info.

      In fact, screw you is considerably too polite, there are better ways to address such, but I won't further insult the non-profane here.

      So, Go to hell ICANN will have to do. But unfortunately I am not Bobby Byrd, who could tell a fellow senator to go to hell in such flowery language that the fellow senator looked forward to the trip.

      No Cheers on this one, Gene

    20. Re:not having read TFA by rickb928 · · Score: 1

      Why is the cost of this service not included in your registration fee?

      Is this so darned hard to figure out? No.

      --
      deleting the extra space after periods so i can stay relevant, yeah.
    21. Re:not having read TFA by Krojack · · Score: 1

      Honestly I could care less.. As long as I can lookup and see 1. When domain was register & expires, 2. What company the domain is with (Godaddy, NetSol, ...), and 3. What name servers the domain is pointing to. The admin email address is a bonus so I can tell my client what email address transfer request are going to.

    22. Re: not having read TFA by Anonymous Coward · · Score: 0

      Dude, never post your real details to Whois. The only thing that has to be real is the zip code.;P

    23. Re:not having read TFA by Anonymous Coward · · Score: 0

      so you choose to undergo a transformative procedure that is socially unacceptable ...

      Tell us about some of your hobbies and predilections, so we can laugh at you (other than overly opinionated, loud mouthed coward that is, which we already know).

    24. Re:not having read TFA by Slashdot+Parent · · Score: 2

      I'm not convinced there is any realistic reason this information needs to be private, although I might feel differently if i lived somewhere else in the world where angry armed mods drag you from your home for expressing a view point.

      I keep my domain registrations private due to the spam. It's shocking how much email and snail mail spam I used to get before making my registrations private.

      --
      They don't grade fathers, but if your daughter's a stripper, you fucked up. --Chris Rock
    25. Re:not having read TFA by Anonymous Coward · · Score: 0

      My ancestors "chose" to have an unpopular skin color and often died when society did not accept it.

      Society's acceptance should not have bearing on what I do or how I live if I am not hurting others.

    26. Re:not having read TFA by icebike · · Score: 1

      I keep seeing people say this, and I have to wonder if you and they have any idea what WHOIS does. It tells someone who owns an IP block, it doesn't say who is using it.

      Shucks, and all this time I was laboring under the delusion you could type in
            whois slashdot.org
      and find out who administers that site, where they can be reached, who hosts them and a bunch of various goodies.

      --
      Sig Battery depleted. Reverting to safe mode.
    27. Re:not having read TFA by Gr8Apes · · Score: 1

      There is also an anonymously queryable subset of the records in the report. I haven't read the full report yet to see what that entails. Not saying it's super-duper, but it's not quite that bad.

      give it a year and it will be.

      --
      The cesspool just got a check and balance.
    28. Re:not having read TFA by Anonymous Coward · · Score: 0

      Wrong context. WHOIS, in this context, is regarding lookups for domain registration information.

    29. Re:not having read TFA by MutualFun · · Score: 1

      While I'm not sure it is relevant to the article, I do agree with you that private registrations are bothersome though I know I personally don't ever completely trust a site with a private registration. I intentionally leave WHOIS open for the world to see on my sites, but then again, you can actually find my details on the About pages of most of them without even having to go to WHOIS. ...snip.

      I'm not worried about the address info on any of my sites however I do get cranky with spammers who send me email about renewing my domains (when they are not even close to expiration, nor are they my registrar) and even calling to ask me to use their search engine optimization! Oh yeah. Frankly, it has made me go and change some of the actual information to invalid data just to keep them off my back. I also host a couple of private registrations due to customer requests, whatever their reason. This sounds more like another attempt to commercialize/monetize what has been a 'free' service.

    30. Re:not having read TFA by cavebison · · Score: 1

      On the flip side of that, simply knowing that your information is available tends to induce better behavior on the Web.

      If you're correct in that theory, we're in for a whole lotta good behaviour online and offline in the years to come. Let's hope so.

  2. Single point of failure. by Anonymous Coward · · Score: 5, Insightful

    A corporation is a single point of failure. As ICANN repeatedly demonstrates.

    1. Re:Single point of failure. by icebike · · Score: 1

      And yet the net survives.

      --
      Sig Battery depleted. Reverting to safe mode.
    2. Re:Single point of failure. by game+kid · · Score: 3

      ...despite ICANN, not because of.

      --
      You can hold down the "B" button for continuous firing.
    3. Re:Single point of failure. by Anonymous Coward · · Score: 0

      ICANN: Yes I Can!

    4. Re:Single point of failure. by Anonymous Coward · · Score: 0

      what a good way to fuck the casual whois user like me - like finding out who is in my bittorrent swarm just because I want to find out where the odd user is

      Its all about the almighty dollar and profit profit profit

    5. Re:Single point of failure. by Anonymous Coward · · Score: 0

      A single point of failure is something that takes down the entire system. If ICANN is a failure but the system still works then by definition there is no single point of failure.

  3. Did i just read... by Anonymous Coward · · Score: 3, Insightful

    "centralized data store maintained by a third party"

    Also the US government would certainly love to manage such entity.

    So that's a huge no.

    1. Re:Did i just read... by gandhi_2 · · Score: 5, Informative

      Once upon a time the US Government was THE Consortion for assigned names and numbers. They were THE registrar.

      They gave it up.

    2. Re:Did i just read... by Anonymous Coward · · Score: 0

      Once upon a time the US Government was THE Consortion for assigned names and numbers. They were THE registrar.

      They gave it up.

      Consortium not consortion

    3. Re:Did i just read... by Opportunist · · Score: 5, Insightful

      Good ol' times. Back when we were the free world. Remember those times? Life was good. The older ones might even remember it.

      Be honest. Do you think this would happen now?

      --
      We used to have a Bill of Rights. Now, with the rights gone, all we have left is the bill.
    4. Re:Did i just read... by icebike · · Score: 2

      Insightful.

      The Internet was built so fast that governments had no idea what was happening or what it would become.

      Of course back then, governments didn't seem to care what people did, and didn't need to control everything.
      Not likely the internet would be allowed to be built at all today, certainly not one that crossed borders.

      --
      Sig Battery depleted. Reverting to safe mode.
    5. Re:Did i just read... by Anonymous Coward · · Score: 4, Informative

      Nope--it wasn't the Gummint that kept that data, it was Jon Postel. He may have been supported indirectly by the Feds, but he sure kept his honesty and integrity. Things have sure gone downhill since he died.

      It's a bit ironic, though, that his name wasn't on any of the RFC's relating to whois.

    6. Re:Did i just read... by Somebody+Is+Using+My · · Score: 1

      Good ol' times. Back when we were the free world. Remember those times? Life was good.

      I do, however, remember when more people bought into that fabrication than they do today.

      Mind you, I still think there's a lot of freedom available in the "free world" and - both then and now - more opportunities for the common citizenry than one might find in a more totalitarian regime. That I can write this diatribe without any fear of retribution is only one example.

      But that "freedom" came at a price, usually paid by citizens of less successful nations. And even the citizens of the free world were as often censored, monitored and controlled in the past as they are today. Trust in the government (often unwarranted), fear of the Enemy (whomever he might have been) and a lack of a method to widely disseminate any abuses resulted in many of these problems being overlooked.

      Thanks to the Internet, the latter problem has been solved, greatly reducing the former (trust in government). That's why they play the terrorist angle so strongly (our new Enemy). And it's why they strive to reduce the effectiveness of the Internet with tactics like the article in question.

      So no, the "free world" was never as free as we remember it being in the past. It was always a quagmire of corruption and greed dragging down the principles on which it was built. It's just that those flaws are made more obvious to the layman thanks to the Internet.

    7. Re:Did i just read... by dkleinsc · · Score: 1

      Good ol' times. Back when we were the free world.

      When was that, exactly? Because the US (who I'm assuming you're referring to when you say "we") has been oppressing various portions of its population regularly and frequently since before it was a country. Sometimes this oppression was over race, sometimes religion, sometimes political beliefs, sometimes economic choices and association, sometimes gender, sometimes (and to a degree still) age, but it's always been there.

      --
      I am officially gone from /. Long live http://www.soylentnews.com/
    8. Re:Did i just read... by Opportunist · · Score: 1

      In short, we had our freedom because we didn't really use it. Much like the telcos could easily offer unlimited local calls as long as people didn't really stay online 24/7.

      --
      We used to have a Bill of Rights. Now, with the rights gone, all we have left is the bill.
  4. huh by Anonymous Coward · · Score: 1

    whois icann?

    1. Re:huh by BonThomme · · Score: 4, Funny

      two fitty, please

    2. Re:huh by c0lo · · Score: 1

      two fitty, please

      I see your 2 fitty and raise you to five fitty (and, if that's not enough, there you have some more)

      Now... I'll call... whois icann?

      --
      Questions raise, answers kill. Raise questions to stay alive.
    3. Re:huh by Anonymous Coward · · Score: 0

      YOU LOCH NESS MONST... oh, wait. Two fitty. Nevermind.

  5. Well there goes the neighborhood by Anonymous Coward · · Score: 4, Insightful

    Great, so we are going to privatize the WHOIS service and make it much more difficult (pay per query?) to get information out of it.

    Guessing one of the usual corrupt telcos or domain name registration companies will bid to be the 'third party' and find a way to fuck this up good.

    1. Re:Well there goes the neighborhood by icebike · · Score: 0

      Although I agree with you, I can't help but noticing the irony of posting that opinion as an AC.

      --
      Sig Battery depleted. Reverting to safe mode.
    2. Re:Well there goes the neighborhood by Anonymous Coward · · Score: 0

      Yes, because as soon as you mention 'icebike' everyone immediately knows you're John A. Smith from 746 Evergreen Terrace.

      Posting as 'icebike' or anonymous coward is exactly the same, so it is laughable for you to accuse anyone of the very same thing you're doing.

      Btw, I'm not the GP AC.

    3. Re:Well there goes the neighborhood by oobayly · · Score: 1

      Ah, so that's who Ned Flanders' other neighbours are. I always wondered.

    4. Re:Well there goes the neighborhood by Lunix+Nutcase · · Score: 1

      Unless your legal name is "icebike", then I fail to see the "irony". What is ironic about using one pseudonym over another?

  6. Horrible for network security... by marciot · · Score: 5, Informative

    As a system admin, I tend to use WHOIS to figure out who is hitting my firewall, or to investigate if traffic is flowing to suspicious domains. Would really suck if WHOIS became a pay service, making it easier for the bad guys to hide.

    1. Re:Horrible for network security... by gandhi_2 · · Score: 3, Funny

      I know, right?

      Imagine having to PAY to find out you are being attacked by.... "DOMAINS BY PROXY, LLC"

    2. Re:Horrible for network security... by Opportunist · · Score: 3, Interesting

      The tinfoil-hat enthusiast in me would say that this may be one of the intentions behind it.

      --
      We used to have a Bill of Rights. Now, with the rights gone, all we have left is the bill.
    3. Re:Horrible for network security... by Anonymous Coward · · Score: 1

      Actually, under the plan authorized requestors would be able to find out the proxy service's customer info. So if you registered through a proxy service, the little people can't find out your info, but any large corporation, or LEA can.

    4. Re:Horrible for network security... by icebike · · Score: 5, Insightful

      If i was getting paid each time you wanted to find out who was attacking you, I might be tempted to make sure you were attacked more often... Just sayin...

      --
      Sig Battery depleted. Reverting to safe mode.
    5. Re:Horrible for network security... by Frobnicator · · Score: 2

      From TFA and the report, those fields are recommended to remain public and anonymous. The biggest difference is that they recommend having a single step process instead of the current two-step process of first looking up the registrar and then using that registrar's WHOIS system.

      Network abuse mitigation is specifically listed as a use case that should not require an account.

      --
      //TODO: Think of witty sig statement
    6. Re:Horrible for network security... by Anonymous Coward · · Score: 0

      and if someone didn't like you causing me to have to pay then someone might DDOS the THIRD PARTY system and no one can look up anything.

    7. Re:Horrible for network security... by Anonymous Coward · · Score: 0

      WHOIS is next to useless for tracking abuse these days because of anonymizing services, and before they became popular owners could enter in any false info they wanted. There's nothing wrong with it in and of itself, but there really needs to be a system of verification in place and a surefire way of looking up who owns a domain. I know, I know, good luck with that.

    8. Re:Horrible for network security... by pantaril · · Score: 1

      The biggest difference is that they recommend having a single step process instead of the current two-step process of first looking up the registrar and then using that registrar's WHOIS system.

      What two-step process are you talking about? There is only one step for me to get information from current whois database:

      $ whois slashdot.org

      that is all, no second step is necessary.

      The ICANN proposal sounds very bad for me for several reasons:
      - current system is fine, no reason to change it
      - centralisation is bad. What if the U.S. controled central authority started to filter entries it doesn't like from the database? What if the central authority refuses to accept certain new entries into the database?
      - users would need to register and pay fee to access (certain info in) whois database

    9. Re:Horrible for network security... by cdrudge · · Score: 2

      So if you registered through a proxy service, the little people can't find out your info, but any large corporation, or LEA can.

      All it takes is a civil subpena to find out who is hiding behind a Domains By Proxy domain. If you've followed the Prenda copyright troll cases, Prenda's entire account history was handed over by Godaddy including customer service notes, domain registrations including proxied domains, IP addresses of sessions, etc.

    10. Re:Horrible for network security... by WaffleMonster · · Score: 1

      As a system admin, I tend to use WHOIS to figure out who is hitting my firewall, or to investigate if traffic is flowing to suspicious domains. Would really suck if WHOIS became a pay service, making it easier for the bad guys to hide.

      Number lookups are driven by a completely separate system and governance structure from domain record lookup.

    11. Re:Horrible for network security... by Frobnicator · · Score: 1

      The biggest difference is that they recommend having a single step process instead of the current two-step process of first looking up the registrar and then using that registrar's WHOIS system.

      What two-step process are you talking about? There is only one step for me to get information from current whois database:

      $ whois slashdot.org

      that is all, no second step is necessary.

      You don't see it because the *nix whois app does the both steps for you.

      It requires two queries. The first query is to find the registrar that is associated with the name, the second query is to get the data from that registrar.

      The ICANN proposal sounds very bad for me for several reasons: - current system is fine, no reason to change it - centralisation is bad. What if the U.S. controled central authority started to filter entries it doesn't like from the database? What if the central authority refuses to accept certain new entries into the database? - users would need to register and pay fee to access (certain info in) whois database

      The current system actually has several problems.

      If you have your own domain name, you know how every year you get about 50 emails and postal mailings telling you it is time to renew; they send something that looks like a bill for services but is actually an overpriced DNS transfer agreement. That is one of the problems the proposal is designed to reduce. Sadly it cannot be eliminated, but that abuse of the system will be harder and more expensive to scammers.

      The current system is also not fine in that it has too limited of information when you actually do need to contact an organization. Most people don't see it, but when a NOC needs to contact a major domain owner, and needs to do it *NOW*, there is no immediately useful record in the whois data. So the NOC will usually just blackhole the domain until they can eventually reach someone's phone or through email.

      For your other concerns, what if they do? Think about each.

      Let's assume someone filters the entries from the centralized database. Nothing in the proposal says "kill the existing WHOIS". In fact they should probably keep them running for many years to come because the existing tools will not all change overnight. If a registrar (or a nation) feels threatened, they can keep the service up indefinately (or in the case of governments, order the registrar to keep it running).

      Next, lets assume the central authority refuses to accept new entries. What does that mean? The DNS entries would still exist because it is a service contract between the individual and the registrar. If the centralized source rejects them then they're really going to piss people off. NOT collecting information is the opposite of what would happen.

      What if they required fees? The proposal actually does recommend fees for certain data, so I suggest you go actually read the proposal. Think about it carefully. If they require fees for information needed by lay people and most small businesses then the backlash would be tremendous. Overnight you would see several competitors. Also because the existing WHOIS services do not need to be removed they such an action by a central source would cause them to fail. But they do recommend charging fees for some things like bulk searches frequently done by scammers and domain squatters. They also recommend charging fees some of the new cross-TLD functionality, which again would otherwise be more abused by scammers and squatters.

      I recommend you go read the actual proposal. Don't read it with an eye for OMGWTF SPIES!. Read it with from the perspective of a NOC operations engineer.

      --
      //TODO: Think of witty sig statement
  7. How monetize "whois"... by Macdude · · Score: 5, Insightful

    This is all about setting up a system to charge for access to 'whois' information. Phrases like "authorizing 'requestors'" is code for charging users.

    --
    "Grab them by the pussy" -- President of the United States of America
    1. Re: How monetize "whois"... by Redmancometh · · Score: 0

      Which is so much different than the extortion game known as "private registration." Pay us or we put all your personal info (including address!) Into an extremely accessible, public system.

      This is the same thing as always, but now the cost burden is on the requestor instead of the proprietor.

      How horrible.

    2. Re:How monetize "whois"... by damn_registrars · · Score: 4, Insightful

      This is all about setting up a system to charge for access to 'whois' information. Phrases like "authorizing 'requestors'" is code for charging users.

      Have you tried searching for a WHOIS record lately? Well over 90% of the records I have searched for in the past 2-3 years have been intentionally obfuscated by various systems as it is. This only accelerates their profits. This is, of course, the only thing the guys at ICANN have been interested in for some time (remember the auctions for gTLDs?).

      --
      Damn_registrars has no butt-hole. Damn_registrars has no use for a butt-hole.
    3. Re:How monetize "whois"... by houstonbofh · · Score: 1

      Have you tried searching for a WHOIS record lately? Well over 90% of the records I have searched for in the past 2-3 years have been intentionally obfuscated by various systems as it is. This only accelerates their profits. This is, of course, the only thing the guys at ICANN have been interested in for some time (remember the auctions for gTLDs?).

      Actually, yes. And for finding out who owns an IP block it is still surprisingly complete. I will sure miss being able to find complete netblocks to blackhole in the firewall.

    4. Re: How monetize "whois"... by Anonymous Coward · · Score: 0

      AFAICT, most reputable registrars provide a whois privacy service for free.

    5. Re:How monetize "whois"... by Anonymous Coward · · Score: 0

      Yes all records contain bullshit because, well, ICANN is responsible for the data there.

      Great job they do for the mandatory fee, right?

      Surely, allowing them to charge for the privilege of changing that info And now for reading it surely will improve everything!

    6. Re:How monetize "whois"... by pantaril · · Score: 1

      Have you tried searching for a WHOIS record lately? Well over 90% of the records I have searched for in the past 2-3 years have been intentionally obfuscated by various systems as it is.

      This is IMO fail of various national registrars. For example our .cz domain registrar NIC.CZ forbids anonymized domains and would take such domain out of the registry if it finds out about it. As a result, whois database for .cz domain is pleasure to use.

    7. Re: How monetize "whois"... by PortHaven · · Score: 1

      Actually very few do...

    8. Re: How monetize "whois"... by Redmancometh · · Score: 1

      Most people use dreamhost, hostgator (I think that's the name), asmallorange or godaddy. I'm willing to bet that makes up 95+% of *domain registration* (not hosting), and none of them offer a free whois privacy service. On a side note I've never had a comment voted up and down this many times.

      Unfortunately the downvoters won, but for the reason (overrated) which I'm okay with.

  8. Oh no, WHOIS DATA MIGHT BE INACCURATE! by Anonymous Coward · · Score: 1

    However can we tell if someone is spoofing their WHOIS data? Quick, we have to make a completely unnecessary power grab before it's too late!

    Thanks but no thanks, ICANN.

  9. I don't like the sound of this by Sean · · Score: 5, Insightful

    What we need is a standard format for WHOIS responses. What we don't need is some monopoly gatekeeper.

    1. Re:I don't like the sound of this by Phroggy · · Score: 1

      What we need is a standard format for WHOIS responses. What we don't need is some monopoly gatekeeper.

      Yes. This. Just trying to figure out "is this domain registered, or is it available?" is a complete pain in the ass, for any sort of automated system.

      --
      $x='S24;r)>63/* h@<5+oZ)32"5cz';$me='phroggy'x$];
      $x=~y+ -xz+\0-Tx+;print$_^chop$me for split'',$x;
    2. Re:I don't like the sound of this by Sean · · Score: 4, Informative

      Everyone go here and let them know we don't want this.

      https://www.icann.org/en/groups/other/gtld-directory-services/share-24jun13-en.htm

    3. Re:I don't like the sound of this by Sean · · Score: 4, Informative

      dig @a.gtld-servers.net example.com in soa

      If you don't get NXDOMAIN then it's registered.

    4. Re:I don't like the sound of this by Phroggy · · Score: 1

      dig @a.gtld-servers.net example.com in soa

      If you don't get NXDOMAIN then it's registered.

      What about detecting domains that have just expired, but haven't been removed yet? And not just for .com but for other TLDs (and second-level domains as appropriate, see http://publicsuffix.org/) as well.

      --
      $x='S24;r)>63/* h@<5+oZ)32"5cz';$me='phroggy'x$];
      $x=~y+ -xz+\0-Tx+;print$_^chop$me for split'',$x;
    5. Re:I don't like the sound of this by markzip · · Score: 1
      Thanks for this link. I read TFA, but I'm afraid that someone with a /. number as high as mine is still not really able to answer the questions on that survey. Perhaps someone with the /. number of 422 might explain? Quoting from the survey: The EWG is eager to obtain your input, including on the following questions:

      Regarding the EWG's suggested Aggregated RDS model, are there additional advantages and disadvantages that should be considered? In such a model, which data repository (ARDS or Registry) should be considered authoritative?

      Regarding the EWG's suggested Aggregated RDS model, are there additional advantages and disadvantages that should be considered? In such a model, which data repository (ARDS or Registry) should be considered authoritative?

      Could the EWG's recommendations for purpose-driven authenticated Gated Access to validated registration data satisfy identified RDS users and their needs? In such a model, how would requestors be identified, authorized and issued RDS access credentials? In particular, who would accredit law enforcement agents, based on what criteria?

      Could the EWG's recommendations for purpose-driven authenticated Gated Access to validated registration data satisfy identified RDS users and their needs? In such a model, how would requestors be identified, authorized and issued RDS access credentials? In particular, who would accredit law enforcement agents, based on what criteria?

      Could the EWG's recommendations for addressing maximum protected registration satisfy both accountability needs and the privacy needs of at-risk individuals? How might a suitable solution be identified and funded?

      Could the EWG's recommendations for addressing maximum protected registration satisfy both accountability needs and the privacy needs of at-risk individuals? How might a suitable solution be identified and funded?

      Are the users and purposes identified by the EWG thus far sufficiently representative? Are there any significant gaps in users and purposes that must be addressed? Are the users and purposes identified by the EWG thus far sufficiently representative? Are there any significant gaps in users and purposes that must be addressed?

      Given the desire for an extensible next-generation RDS that might accommodate the needs of a rapidly-evolving global Internet, how could future new users and purposes be accommodated? Who would decide on permitted purposes, using what criteria?

      Given the desire for an extensible next-generation RDS that might accommodate the needs of a rapidly-evolving global Internet, how could future new users and purposes be accommodated? Who would decide on permitted purposes, using what criteria?

      Are the registration data elements identified by the EWG thus far sufficiently representative of the data required for each identified purpose? Are there any significant gaps in data elements that must be addressed?

      Are the registration data elements identified by the EWG thus far sufficiently representative of the data required for each identified purpose? Are there any significant gaps in data elements that must be addressed?

      How should public and gated data elements be classified? What criteria should the EWG apply to make initial recommendations in this area?

      How should public and gated data elements be classified? What criteria should the EWG apply to make initial recommendations in this area?

      What community needs should be considered during the EWG's discussion of registration dat

    6. Re:I don't like the sound of this by houstonbofh · · Score: 1

      dig @a.gtld-servers.net example.com in soa

      If you don't get NXDOMAIN then it's registered.

      Until they start serving search adds instead...

    7. Re:I don't like the sound of this by Sean · · Score: 5, Insightful

      You don't have to answer all of them. You don't have to directly answer their questions either. You could just say things like:

      - I don't want this. This system is not in my best interest.
      - I don't want to register with anyone to query this data.
      - Abuse mitigation should be handled by each registrar, this is a good way for them to differentiate themselves.
      - I don't want to pay for this system at all
      - Law enforcement should be given no special access at all. Nobody should accredit them.

      You could also contact your registrar if you own a lot of domains and let them know you don't support this move at all. Ask them to oppose it.

    8. Re:I don't like the sound of this by Sean · · Score: 1

      Yeah, registration expiry info is only available in WHOIS, not in the zone itself.

      Dealing with other TLDs that allow second-level requires knowledge of their structures. Some of them have wildcards too, and that is detectable. Anyone doing this kind of automation can figure it out. It's not hard, it just sucks.

    9. Re:I don't like the sound of this by Anonymous Coward · · Score: 0

      gtld-servers.net is only responsible for certain TLDs (ex. .com and .net). They have nothing to do with .org, or other TLDs.

      The more accurate answer (as you probably know anyway, sorry for being pedantic in that case) is "query the root servers relevant to that TLD and ask". And if you don't know what rootservers are responsible for the TLD? Ask [a-m].root-servers.net for the NS records for the tld itself (and don't forget the trailing dot!), i.e.:

      dig @a.root-servers.net org. ns

      And those may change too. The current authoritative rootserver list used by Internet-facing resolvers worldwide is here: ftp://ftp.internic.net/domain/named.cache

      Sometimes this is known as "named.root". Enjoy!

    10. Re:I don't like the sound of this by raju1kabir · · Score: 1

      Fascinating. I wondered who registered sean-is-mistaken.co.uk.

      --
      "Patriotism is your conviction that this country is superior to all other countries because you were born in it." -- GBS
    11. Re:I don't like the sound of this by SAH · · Score: 3, Informative

      What we need is a standard format for WHOIS responses. What we don't need is some monopoly gatekeeper.

      There's IETF work under way to develop standard formats for whois-like queries and responses: http://datatracker.ietf.org/wg/weirds/charter/

    12. Re:I don't like the sound of this by markhb · · Score: 1

      What about detecting domains that have just expired, but haven't been removed yet?

      Oh, you mean like the domain squatters do?

      --
      Save Maine's economy: write stuff down. All comments are exclusively my own, not my employer.
    13. Re:I don't like the sound of this by drinkypoo · · Score: 1

      If I were ICANN I would throw away all incomplete surveys as a means of filtering out people who have single-objection reasons to answer the survey. It's okay to answer questions with "yes" or "no" answers.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    14. Re:I don't like the sound of this by Phroggy · · Score: 1

      It's not hard, it just sucks.

      Precisely my point. There is clearly room for improvement.

      --
      $x='S24;r)>63/* h@<5+oZ)32"5cz';$me='phroggy'x$];
      $x=~y+ -xz+\0-Tx+;print$_^chop$me for split'',$x;
  10. Stupid Idea by Etherwalk · · Score: 5, Insightful

    There should be a way for any person to contact any domain owner or domain-owning company. Putting a service in to vet requests will make it harder.

    This is bad. And less transparent. And less distributed. And more expensive.

    1. Re:Stupid Idea by tlhIngan · · Score: 2

      There should be a way for any person to contact any domain owner or domain-owning company.

      Which is the current problem with WHOIS - because it's easily accessible by everyone, everyone abuses it. So the end result is that all information is now hidden by proxies. The fact alone pretty much makes WHOIS useless if you need to contact someone.

      A more restricted service that prevents abuse and requires all information be accurate (i.e., no proxies) and pointing to real people would be much more useful.

      Either that or ICANN can simply announce all domains are owned by the contacts listed in WHOIS - if you use a proxy service, the proxy service owns the domain and all domains as such have been handed to a third party.

    2. Re:Stupid Idea by houstonbofh · · Score: 2

      This is bad. And less transparent. And less distributed. And more expensive.

      But as long as we save one child... I mean, as long as at least one person makes a boat load of money, it will be worth it.

    3. Re:Stupid Idea by raju1kabir · · Score: 2

      The fact alone pretty much makes WHOIS useless if you need to contact someone.

      I use one of those proxy services to register domains. They require a valid email address and test periodically to make sure it works. They publish an auto-generated random-looking email address for each domain, and reliably forward mail to the address I've provided. People who need to contact me are able to do so instantly.

      --
      "Patriotism is your conviction that this country is superior to all other countries because you were born in it." -- GBS
    4. Re: Stupid Idea by Anonymous Coward · · Score: 0

      Your email forwarder is worthless; I only contact domain owners via postal mail, you insensitive clod!

  11. Why? by Reaperducer · · Score: 1

    Seems like a solution in search of a problem.

    Though it would be nice to see some of the WHOIS spam cleaned up.

    Even some of Google's WHOIS information has been jihacked by pr0n advertisers.

    --
    -- I'm old enough to have lived through six different meanings of the word "hacker."
  12. Under who's jurisdiction? by c0lo · · Score: 1

    data store maintained by a third party

    What domain privacy rules would be applicable?

    --
    Questions raise, answers kill. Raise questions to stay alive.
  13. The current solution by slashmydots · · Score: 1

    Find someone with private registration services. Record all fields. Put those fields into your website. Then some BS data request or subpoena or whatever would result in the private registration company claiming there is no associated record and some huge argument, none of which results in them getting your data. It's ridiculously insecure and a horrible idea to attach your name to a website. That's just asking for nonstop trouble, spam, scam calls, scam e-mails, domain scams, threats, etc.

    1. Re:The current solution by Animats · · Score: 1

      It's ridiculously insecure and a horrible idea to attach your name to a website. That's just asking for nonstop trouble, spam, scam calls, scam e-mails, domain scams, threats, etc.

      What trouble? My real name and phone have been on all my WHOIS records for two decades. There's some spam, but the filters stop that. Maybe two phone calls a year. One threat in the last decade, from a scammer. He's no longer in business.

      If you're running a business, you're supposed to disclose the actual name and address from which the business is conducted, at least in California and in the European Union. "Private registration" is a slimeball indicator for a site with any commercial purpose.

  14. s/Kill/Commercialize/ by Anonymous Coward · · Score: 0

    'nuff said.

  15. Outsourcing by quilombodigital · · Score: 2

    They just fired the guy responsible for this form and want to outsource it.

  16. Like or don't like, let ICANN know by Anonymous Coward · · Score: 1

    http://www.icann.org/en/groups/other/gtld-directory-services/share-24jun13-en.htm

    1. Re:Like or don't like, let ICANN know by ukpyr · · Score: 1

      ^^^ This.

  17. Aren't statists wonderful? by Anonymous Coward · · Score: 0

    Everything must be orderly. No rough edges or flaws. Nothing without permission. Submit to the designated authority and conform to the mandate.

  18. centralized, third party by gmuslera · · Score: 1

    Easy to explain what it is, and the same explanation also say why it is wrong. Anyway, this goes with the current agenda of taking control of internet.

  19. ICANN cares not about users by damn_registrars · · Score: 4, Insightful

    This action is not with your best interests in heart. This proposal comes with the intent of ICANN maximizing their own profits. They will blow smoke about privacy and other such utter bullshit to try to get people to support this but make no mistake, this will make the internet a less pleasant experience for users and a better hiding place for spammers.

    How so, you might ask? Right now the current WHOIS gives vague lipservice to requiring domain registrations (and only under a very specific list of TLDs at that) to be registered with valid information. As it is, a not-insignificant portion of all new registrations at any given time are completed with missing or completely bogus information. And yet when this happens ICANN - who is tasked with making WHOIS data legible - almost always does nothing.

    Now, they are just looking to openly embrace obfuscated, missing, and utterly bogus data in WHOIS records. The only people who benefit form this are the registrars that sell domains that benefit from that kind of lax registration requirement - spammers, scammers, and the like. If you don't think this matters to you, just wait until someone you know has their identity stolen after they mistype the web page for their bank, click on a fake ebay email, or do anything of that nature. The scum that will make money off of this will get to someone close to you, and this action will make it even less likely that those types will ever see any kind of punishment for their actions.

    In other words, fuck you ICANN. I hope you profiteering fucks get fucked in the ass. And then when someone tries to fuck me because of your fucking stupid actions I will do everything I can to direct them to fuck you instead, you stupid fucking fucks.

    --
    Damn_registrars has no butt-hole. Damn_registrars has no use for a butt-hole.
    1. Re:ICANN cares not about users by BonThomme · · Score: 2

      "In other words, fuck you ICANN. I hope you profiteering fucks get fucked in the ass. And then when someone tries to fuck me because of your fucking stupid actions I will do everything I can to direct them to fuck you instead, you stupid fucking fucks."

      odd, I was thinking exactly the same thing

    2. Re:ICANN cares not about users by fustakrakich · · Score: 2

      ...fuck you ICANN. I hope you profiteering fucks get fucked in the ass. And then when someone tries to fuck me because of your fucking stupid actions I will do everything I can to direct them to fuck you instead, you stupid fucking fucks.

      Mmm, smells like teen spirit...

      --
      “He’s not deformed, he’s just drunk!”
    3. Re:ICANN cares not about users by Anonymous Coward · · Score: 0

      "damn_registrars": "The only people who benefit form this are the registrars that sell domains that benefit from that kind of lax registration requirement - spammers, scammers, and the like"

      Excuse me, a poster above gave the counterexample, which ought to be obvious: "I'm not convinced there is any realistic reason this information needs to be private, although I might feel differently if i lived somewhere else in the world where angry armed mods drag you from your home for expressing a view point." ( icebike)

      As a matter of fact it happens. In Mexico for example, journalists are tracked down by drug gangs and murdered because they report on the drug gangs. In theocratic countries, publishers of anything certain fanatics consider blasphemous are murdered. People who post their home addresses on Facebook have been terrorized by burglaries.

      In most cases this is not due to domain registrations, but if someone is needing to publish independently and avoids giving out personal information in other ways, but follows the intent of the registration rules, he or she is subject to retaliation by revealing his/her real name and physical address to the world.

      I know everyone is angry at spammers, but think about this for a few seconds. A corporation can publish anything with impunity, because it hides behind the business address. You can look up the executives in some cases, but they can afford guards, alarms and so on. Yet individuals who have no effective defenses are subject to the same rules. They have to either limit their publishing to non-controversial fluff, or rely on someone else's domain, or be subject to violence and robbery.

      The obvious solution is for the electronic contact information to be provided, verified and published, but the personal information on individuals to be concealable. This may be orthogonal to the current proposal but your rant for every domain owner to be identifiable is either malicious or misplaced.

    4. Re:ICANN cares not about users by damn_registrars · · Score: 1

      "I'm not convinced there is any realistic reason this information needs to be private, although I might feel differently if i lived somewhere else in the world where angry armed mods drag you from your home for expressing a view point." ( icebike)

      However you do not need to have your own domain name to express your viewpoint. There are plenty of free blog services where you can do that, as well as various discussion forums and other such services. For that matter, many of the free blog services attract far more attention than what one could reasonably expect to see quickly on their own domain name.

      The obvious solution is for the electronic contact information to be provided, verified and published, but the personal information on individuals to be concealable

      The problem here lies in where you draw the line for what can be considered personal enough to be concealed.

      --
      Damn_registrars has no butt-hole. Damn_registrars has no use for a butt-hole.
    5. Re:ICANN cares not about users by bhiestand · · Score: 1

      Someone really hates sex...

      --
      SWM seeks new sig for a brief fling
  20. Ok, spill it, what's the goal? by Opportunist · · Score: 1

    Is it to milk money from me whenever I want to know who keeps trying to hack me or is it to keep me from finding out who it is because such "sensitive information" will only be available to governments and the content industry?

    --
    We used to have a Bill of Rights. Now, with the rights gone, all we have left is the bill.
    1. Re:Ok, spill it, what's the goal? by gl4ss · · Score: 1

      the goal is to give a right for a company to do this, for the company to charge and the company to kickback some cash to ICANN.

      ICANNOT.

      --
      world was created 5 seconds before this post as it is.
  21. Code word for SURVEILLANCE by Anonymous Coward · · Score: 0

    Currently the DNS Whois information is set by the DNS host which is NOT under US control. So a German domain company sees the logins and any identity documentation needed for the German .DE domain owner but the NSA doesn't.

    The published information is often just a subset of that information and often out of date.

    By 'centralizing' it, ICANN can force an identity requirement on ALL domains. e.g. require a passport or id card.

    Which in turn would let them fill the new NSA Domain to Identity Card database with the worlds identity cards.

  22. Monopoly by Tyr07 · · Score: 1

    Because, you know, we've never seen people trying to wrestle control into a single entity that is free to start with, and once total and absolute control is established, begin to start charging for the service. 'Maintenance' and other profitable excuses.

  23. Requestors is the NSA by Anonymous Coward · · Score: 0

    a) There will be one central database, it will be in the USA.
    b) Moving a database from one place to another fixes nothing. It does however change the jurisdiction of the data.
    c) The database needs an authoritative copy of your WhoIs, how will they know your identity?
    d) The DNS provider currently is the one who handles billing (and has thus has your identity confirmed). This new authority will need some for of identity document to confirm the same.
    e) So an identity document record will be added to this database and a requirement to hold a domain.
    f) Now add an NSA secret warrant and you have the ultimate goal.

    1. Re:Requestors is the NSA by Samantha+Wright · · Score: 4, Insightful

      Given ICANN's track record, I'm pretty sure they're just looking for more public resources to carve up and monetize.

      --
      Bio questions? Ask me to start a Q&A journal. Computer analogies available for most topics!
  24. begged questions: by Anonymous Coward · · Score: 1

    1. Is WHOIS actually broken?
    2. Does this proposal actually fix it?
    3. Is this proposal just a way for the proposers to privatize a free and common resource so they can make money out of it?

    4. Can we identify these jackasses by name and make sure they never have anything to do with ICANN again?

    1. Re:begged questions: by Anonymous Coward · · Score: 0

      No, those are raised questions.

  25. Follow the money by Anonymous Coward · · Score: 0

    Where ever you have a gate, you end up with a gatekeeper and you must pay a toll to pass through. If not this year, then next.

    But don't worry, it will just be a reasonable amount to cover expenses, plus a little extra if you want your information in less than a month.

    1. Re:Follow the money by Anne+Thwacks · · Score: 1

      I'm a troll, fol-de-rol ...

      --
      Sent from my ASR33 using ASCII
  26. Having read TFA and the propsal by Frobnicator · · Score: 5, Informative

    They are not talking about blocking all access to the data.

    They propose keeping a good portion of the existing data available through anonymous public requests, exactly the way current WHOIS system works today. The big difference is that there will be a single source; you won't need to do the two-step process currently in place.

    They are also proposing adding additional contact fields that have been frequently requested for WHOIS data.

    They are also proposing limiting access to some data, in particular limiting the data traditionally used to scam people with fake DNS renewals. In particular it does not talk about refusing access, simply limiting the requests to authenticated users to prevent thinks like bulk-searches that scammers frequently use. The report recommends only limited fields require authenticated access, not those used commonly by individuals or by website administrators for abuse mitigation.

    Finally, they are proposing adding new advanced search capabilities that are useful for ISPs (and also private and government surveillance) that are not currently available, but will be very useful for domain abusers spanning many TLDs.

    --
    //TODO: Think of witty sig statement
    1. Re:Having read TFA and the propsal by Anonymous Coward · · Score: 4, Insightful

      I for one prefer to have my domain details stored in my own country. We have reasonably decent privacy protection laws here, and I think the current system is adequate but am concerned about having a larger offshore database with more detail stored overseas if that country does not have sufficient privacy protection (likely).

    2. Re:Having read TFA and the propsal by Anonymous Coward · · Score: 0

      The problem is that is the current proposal, which is fine.

      I wonder how many months will pass until the "terms" are changed and ALL accesses will require a signup and a fee.

    3. Re:Having read TFA and the propsal by Forever+Wondering · · Score: 4, Interesting

      What constitutes an authorized user?

      I have a honeypot on my home server to collect phony/random/orchestrated login/breakin attempts. A log entry has time, IP, username, pw. Eventually, I'd like to do further automated scripting. Namely, take the IP address, do a whois on it, look for the abuse contact email at the ISP, and email them the relevant log entries, with a polite request to investigate.

      If they're legit, they may want to take action against one of their users who is doing massive attempts at system breakins. That is, such attempted login/breakin activity is against the law in certain countries. It's also [probably] a violation of the ISP's TOS. I've read that many ISPs don't even know that their customers are doing such things and welcome being told because the customer activity can expose the ISP to a degree of legal liability [safe harbor notwithstanding].

      Currently, in whois data, there is no [universally used] standard for the abuse mailbox. It can be:
          abuse-mailbox: ...
          Remarks: Send abuse email to ...
          % Remarks ...
          # Send abuse reports to ...
      So, standardization would be nice.

      However, an interesting wrinkle. Although I get attempts from all over the world, most of the breakin attempts I get come from .cn hosts [just sayin ...]. The whois data from these is _always_ 100% complete and well organized. I guess they're compelled to do this by the gov't there. If, as proposed, the information goes to a central repository in [presumably] another country, there would be no way to compel an ISP to provide accurate/complete information cross-border.

      So, how does this shape up under the new proposal? Which country's laws would govern this? Per-country top level domains like .cn and .uk present fewer problems. But, what about the more generic .com, .org, etc.?

      --
      Like a good neighbor, fsck is there ...
    4. Re:Having read TFA and the propsal by chihowa · · Score: 3, Interesting

      Eventually, I'd like to do further automated scripting. Namely, take the IP address, do a whois on it, look for the abuse contact email at the ISP, and email them the relevant log entries, with a polite request to investigate.

      I'm sure you will be careful with this, but I just want to post a friendly reminder. Depending on how you organize your script and how often the same person hits your network, there's a chance you'll end up flooding the abuse contact with email. Not only will they not appreciate that, but there is a chance of amplification and bogging down their abuse handling process.

      In addition to the abuse-mailbox field you mention, it would be nice to standardize on an abuse report format, too. That way we could be confident that abuse reports can be properly fed into a system without depending on a human reading them directly.

      --
      If you want a vision of the future, imagine a youtube comments section scrolling - forever.
    5. Re:Having read TFA and the propsal by Dynedain · · Score: 1

      They propose keeping a good portion of the existing data available through anonymous public requests, exactly the way current WHOIS system works today. The big difference is that there will be a single source; you won't need to do the two-step process currently in place.

      What 2 step process? I type "whois example.com" at a command line and I have the results. Granted the command itself first looks up the root registrar and then queries that registrar. But I can see all kinds of problems in this because different TLDs have different requirements for what is in WHOIS info. For example, .se domains have little more than a unique key to indicate the domain holder, whereas .com/.org/.net have all the Technical/Administrative/Owner contact info.

      --
      I'm out of my mind right now, but feel free to leave a message.....
    6. Re:Having read TFA and the propsal by Gr8Apes · · Score: 1

      Centralized means centralized control. It's hard to charge fees, disable access, or censor data on a decentralized data store. And I'm not sure what problem they're trying to solve that whois addresses. I've had 0 issues finding out who owns what, although I might have to dig a little occasionally. And that's fine. They are free to query them all too.

      --
      The cesspool just got a check and balance.
    7. Re:Having read TFA and the propsal by Forever+Wondering · · Score: 1

      I'm sure you will be careful with this but I just want to post a friendly reminder.

      Yes, one of the reasons that I haven't done it until now. My system has a dynamic IP and no DNS entry, so it's hardly a high profile target. Since 12/22/11 I have some 32,000 entries.

      Depending on how you organize your script and how often the same person hits your network, there's a chance you'll end up flooding the abuse contact with email. Not only will they not appreciate that, but there is a chance of amplification and bogging down their abuse handling process.

      I was considering a builtin delay. Delay until the volume reaches a certain number of attempts or enough time has elapsed that it indicates a one off attempt. One instance originated from Bangkhok and would do an attempt every 20 minutes. This went on for weeks.

      Yes, you're correct. Clearly a balance between excessive volume and hyper-reaction vs. timeliness must be struck. That is, for example, if the "perp" is roaming [betweeen internet cafes] to avoid detection/capture, being able to nab the person "in the act" would require frequent live updates of the abuse info.

      In addition to the abuse-mailbox field you mention, it would be nice to standardize on an abuse report format, too. That way we could be confident that abuse reports can be properly fed into a system without depending on a human reading them directly.

      I was thinking a .csv: YYMMDD-HHMMSS.uuuuuu,IP,login,pw

      This needn't actually go through email if we were to collectively come up with a dynamic system to handle such things. Either a spamhaus type organization or some decentralized database. Remember the recent [similar] attack against wordpress sites? Having dynamic abuse info passed around in realtime [via some "abuse report" protocol], would allow backbones to start dropping/blocking the traffic [near the source]. This could mitigate such an attack before it had a chance to get going.

      It would need some "web of trust" aspects to validate the abuse reports [vs. someone sending false ones just to blackball the IP of someone they didn't like].

      Actually, now that I think of it, IIRC, there are some sites that take such info already.

      Also, while some attack combos have been scattershot (e.g. login: mary, pw: mary) or dictionary (root/a, root/aa, ...), some are so obscure/unique (e.g. root/a3da50fb67a6ae5a06eca1364e2356a9) that the only explanation is that there has been a crack of a pw database somewhere and they are replaying everywhere.

      --
      Like a good neighbor, fsck is there ...
  27. None of that requires an NSA database by Anonymous Coward · · Score: 0

    None of the things you've listed require the database to be centralized in NSA land.

    " The big difference is that there will be a single source; you won't need to do the two-step process currently in place. "
    It's one step now, you're just using the wrong Whois tool.

    "They are also proposing adding additional contact fields that have been frequently requested for WHOIS data."
    By who? Not by me.

    "They are also proposing limiting access to some data, in particular limiting the data traditionally used to scam people with fake DNS renewals."
    Wait, *more* data or *less* data? So NSA gets the data but other countries don't.

    "Finally, they are proposing adding new advanced search capabilities that are useful for ISPs (and also private and government surveillance) "
    The only people who ever wanted that was the RIAA and MPAA, and they wanted it for copyright reasons. Search of whois data is already available on websites.

    " domain abusers"
    So a new crime of domain abuse ?

    1. Re:None of that requires an NSA database by Anne+Thwacks · · Score: 1
      So a new crime of domain abuse ?

      Dont think of the children - it will land you in jail!

      --
      Sent from my ASR33 using ASCII
  28. What about non-domain name related data? by MavEtJu · · Score: 1

    Like AS numbers, network blocks etc?

    Oh wait, they don't make money out of that will be thrown out?

    --
    bash$ :(){ :|:&};:
  29. A third party? by Anonymous Coward · · Score: 0

    Presumably a trusted third party like the US, or even better the NSA?

  30. Third Party? by Jane+Q.+Public · · Score: 1

    Yeah, right. Like Network Solutions turned out to be a great idea or something.

  31. really by crutchy · · Score: 2

    time to replace icann with.... fuck, just about anything would be better... even microsoft, and that's saying a lot

  32. Centralisation is stupid by Anonymous Coward · · Score: 0

    Why the fuck would you centralise whois? Just put the whole internet on one place and be done with it since we're at it (oh, wait, it's happening already - facebook, googleplus!).
    Not to mention much easier access for american agencies to the addresses of anyone who owns a domain. Whois information should be private by default.
    STUPID idea.

  33. It's for the domain squatters by Antique+Geekmeister · · Score: 1

    The proposal is aimed at charging the domain squatters for the thousands or millions of daily hits they make, which do burden the whois system profoundly. I'm aware of entire companies that were founded to do this during the "dotcom" bubble, most of which thankfully died out during the "dotbomb" burst. But the business remains intact, and is even more populated by fraudsters than it was then. And this proposal is clearly aimed at limiting the large scale data mining to a much more select clientele.

    It might help the system. The fraudulent registrations and registrars unresponsive to abuse complaints are a constant drain on network administrator resources. But there's no reason to think that this centralized data will be used to actually monitor for or prevent abuse. Like when Verisign declared "*.com" to point to automatically point to their web pages and email systems, it's likely to cause a lot of chaos and serve only a small group in a place to profit from it.

    1. Re:It's for the domain squatters by Anonymous Coward · · Score: 0

      You will not be able to control the current versions of squating as it relies not at all on whois services.

      There is one simple easy solution to this entire issue: Make Verisign with their monopoly and billions of guaranteed revenue and guaranteed 45 minutes of maintenance downtime a month actually run as a thick client (one that stores client details) and provide a standardized whois. All other registries do this. But Verisign somehow weasled out of this.

    2. Re:It's for the domain squatters by Anonymous Coward · · Score: 0

      Very few domains would be considered squatting on active TMs in the same trade space (certainly less than a hundred thousand of .coms out of 200 million). The TM holders don't need public whois info to file a UDRP, they have other methods like using legal means to query the payment account info directly at the registrar. What burden is that on the whois service?

      Your post makes little sense. Much less than little, actually.

  34. Now I'll have to pay? by Anonymous Coward · · Score: 0

    If I am reading this correctly, by giving the WHOIS functionality over to a 3rd party for database consolidation, means that in order to do queries, I'll more than likely will have to pay for access. I'm not much of a WHOIS user, except for when I get phone calls from "Microsoft Technical Support" informing me that I have viruses that their "database" is detecting. Then they want me to go to a website to download a "program" that will remove said viruses.

    I've gotten their site shutdown 3 times now by doing a WHOIS and informing their webhost provider of their scam.

    So.. now I'll have to pay to do this? What is this crap? /sigh.

  35. domain name system has to die! by Anonymous Coward · · Score: 0

    there needs to be an alternative to the old central domain name system.
    the internetz should be redundant. anything "central" and "hierarchical"
    introduces a single point of failure (failure can mean many things) and is "NOT A GOOD THING(tm)".
    the internetz is not dumb terminals connecting to datacenter-server-farms.
    it's the users with a personal computer.
    it is interesting how the fear was propagated starting with viruses, malware and firewalls to
    basically render every user a dumb terminal with no services running (out of fear).
    if you're using linux you got 99% the same code running as a datacenter server (hardware mostly different).
    basically we need a replacement to the central, hierarchical domain name system.
    if the users can agree on giving each other names, then we can continue to improve the internet instead
    of using (good for a time) old paradigms.
    what would become possible you ask? direct calling for example. no more having to ask a (possibly spying )central
    location for the "address" of a target. call direct.
    another example would be direct mail or even pull email. you send an email to friend, friend only gets a link no data,
    follows link to pick-up mail from your computer (to him). etc ...
    thanks and do think a bout it ... 'cause on a far away alien planet they are WAY beyond internet v1

  36. Welcome to the new reality... by Anonymous Coward · · Score: 0

    I think this somewhat falls under "Chicken or the Egg." Surely some of the government crackdowns have come simply because of the Internet. Suddenly, in the 90's people had access to spread information across the globe with very little resistance aside from language barriers. In the 00's, while there was an explosion of cat videos and informational noise being spread, certain organizations began accumulating all the information that the human race could bring together, resulting in a form of renaissance of global informational wealth...again, despite the (almost deafening) noise of the general public. This wealth is now starting militant reshaping of the world around us as the Old World Order tries to tighten its grasp and the New World Order attempts to break free. Ideas are spreading faster than ever, and what we're seeing now is the current regimes scrambling to reign it in so they can keep the control they are so used to... which means breaking freedoms.

    If the internet didn't exist yet, we'd still be ideologically in the early 90's where you'd have small pockets of conflict, but nothing on the order of what we have now...which wouldn't have given anyone the inkling that the Internet would be such a world changing force until it was unleashed upon the world to feed off the cumulative knowledge and become the unstoppable behemoth of ideas that will eventually turn all of humanity into the hive-minded Borg that Roddenberry warned us about. This is the direction we are moving in. Once our every thought, our every idea, our very essence is put into the Internet and translated into every language that the world will understand, the Internet will become the source of our memories and all of our collective information for each and every other person to access and reshape. The Internet is the Borg. It is The Matrix. It is Skynet. It is beautiful. It is terrifying.

  37. Whois by intermodal · · Score: 1

    Whois, much like the egregiously insecure and broken email system, does need to be replaced (you'd be amazed how upset my friend was when I let her know that her full name, address, and phone number were available to anyone due to her owning a few domains).

    Personally, what I think needs to be done is the TLD providers need to handle the information, allowing it to be run in accordance with the laws of the country corresponding with the domain. German laws for .de, UK laws for *.uk, Japanese laws for .jp, and so forth. At the same time, I think it would be nice to allow optional support for subdomains to be whois-capable, provided by the domain owner. For example, allow myexample.tld to provide information for dyndnsuser.myexample.tld or facilityname.myexample.tld on their own terms.

    --
    In SOVIET RUSSIA... erm...NSA AMERICA, the Internet logs onto YOU!
  38. ICANN new policy to cost registrars millions? by WaffleMonster · · Score: 1

    Stupid question bonus round.. wouldn't this cut into domain privacy surcharges all yer registrar friends try and rake in? I mean if records can no longer be accessed by joe spammer such privacy services become useless...don't it?

    I for one would fully support abolishing ICANN and replacing it with an institution that at least tries to care about what is actually best for the Internet. We see failure after failure in policy from ICANN consistantly doing what is good for business regardless of its effect on the network. e.g. TLD sprawl and ongoing "study" designed to greenlight "dotless" names. Sheer madness. Shame we continue to allow them to get away with being a bunch of greedy little pricks.

  39. There are both required and recommended contacts by Medievalist · · Score: 4, Interesting

    This doesn't answer all your questions. Sorry.

    There are standardized addresses. Unfortunately, people who don't understand basic systems engineering (or who do, but are extremely greedy and amoral) refuse to use them.

    Anyone providing Internet mail services is required by the SMTP protocol definition to have a human being receiving mail at the postmaster@domain.tld address. This has been true in every single revision of the protocol starting with RFC822 and continuing to the present day in RFC2821.

    If you aren't manning the postmaster address, what you're doing is simply not SMTP, so it isn't Internet email. It is something else - metaphorically a bicycle wobbling down the center of the freeway, perhaps, or in the case of the big government-owning vendors like Verizon a steamroller in a pedestrian tunnel, crewed by laughing psychopaths.

    The abuse@domain.tld address is slightly different - it is required by RFC2142, just like the hostmaster@domain.tld address is, but that RFC is not a protocol definition or a requirement for Internet connection.

    However, the following statement is objectively true: If a domain does not staff the abuse, hostmaster and postmaster accounts, they will fall in at least one of two categories: technically incompetent or ethically corrupt.

    The technically incompetent cannot handle the mail filtering required to deal with the spamload on these addresses. AOL claims that they are part of this group.

    The ethically corrupt understand that the Internet is fundamentally a system of agreements - that wires and computers cannot function as a whole unless they use agreed-upon, mutually respected protocols, just as people cannot communicate efficiently unless they share some kind of common language. However, they also know the Internet's protocols are robust enough that only the majority of users must scrupulously comply with them, and extremely wealthy and powerful players can gain commerical advantage by breaking the rules they insist everyone else respect. Verizon and Microsoft fall in this category.

    Because people continue to buy services from the technically incompetent and the ethically corrupt, they continue to prosper. This is something the free market is supposed to magically correct, but amazingly enough the same people trumpeting the power and the glory of free markets seem to be working very hard to support regional monopolies and strengthen barriers to entry in communications markets.

  40. Whois change like this? No, no and double no! by aisnota · · Score: 1

    Centralized data store maintained by a third party? What is this another gambit to help before the chronicles of whistle-blower releases reaches the next stage?

    What a farce!

    Encourage all and any participants voting on this one to slam the door shut and to suspect those proposing this centralization.

    Centralization is the gateway drug to tyranny!

    --
    http://www.aisnota.com/slashdot/ Welcome to Logic and the Future
  41. ICANN has obviously already made their decision by northcide · · Score: 2

    If you read the questions posted at ICANNs share your thoughts page : http://www.icann.org/en/groups/other/gtld-directory-services/share-24jun13-en.htm, it's clear they've already made their decision to move forward this this ridiculous plan.

    Whois is an invaluable tool for web hosters and managed service providers. To say we'll need to request access to this information in the future is absurd. I see no security "risks" with the whois information being available. If i'm able to legally look up ownership and tax records for property in the US, why is it more dangerous to view the ownership details of a domain name / ip block?

    I simply don't understand what they hope to "fix" with this system.

  42. Re:There are both required and recommended contact by Anonymous Coward · · Score: 0

    ... technically incompetent or ethically corrupt ...

    Thank you. I've never seen or heard this argument expressed as well as this. Sorry, but I just ran out of mod points.

  43. Its all Politics.. by Anonymous Coward · · Score: 0

    After having sat through a few of these meetings, and looking at who is mostly controlling the the board, it is obvious that there is a lot of parties with self interest involved in these decisions. The problem is really as simple as those who believe there should be public information on the operators, and those that want to see public information (law authorities, researchers, any many others) This WHOIS discussion has been a pinball for some time.

    Frankly, in my opinion, if you want a 'public' resource (Internet name or address) you should be able to see who operates it.

    But on one side there are people that believe it will hurt their business (Many hosting business [see board] believe this). There are also those who are worried the data can be abused. (eg. email scrapers), at least that is a reason they put up for proposing changes.

    This is a compromise proposal to appease the law agencies (oh, you get to see the info) while getting away without having to publicize the data.

    'whois' is still very important, and a world without any form of accoutability, will not be a happy place. (I think that 4-5 different proposals on whois have come and went over the last 10 years)