VeriSign, Inc. - Current Report: "On March 28, 2013, VeriSign, Inc. (“Verisign” or the “Company”) released Verisign Labs Technical Report #1130007 version 2.2: New gTLD Security and Stability Considerations (the “Report”). The Company provided the Report along with a cover letter to the Internet Corporation for Assigned Names and Numbers (ICANN) (the “Letter”) on March 28, 2013. A copy of the Letter and the Report are attached hereto as Exhibit 99.1 and Exhibit 99.2. . . . Ensuring that Internet software and sites understand all domains - not just the old three-letter domains like .COM and .NET - is called universal acceptance. For example, when is the last time you looked at your company's online contact forms? If you haven't revisited them for a while, you might discover that they are hard coded for certain domains like .NET or .ORG and may reject email addresses that use, say, a four-or- more-character domain like .INFO or .MOBI. (Full disclosure: .INFO and .MOBI are both domains managed by my company, Afilias). Or have you seen some TLDs that don't work in your browser? Some browsers, including mobile ones, screen out addresses as either “right” or “wrong,” and many modern TLDs simply don't resolve because the browser doesn't understand how to handle the TLD. A real-life example: as late as 2007, you could not email an article from the New York Times website to anybody with a .INFO email address, which was actually fun for some of my colleagues because they would try to send me articles and say, ”Oh, you didn't see it? Maybe you should get a .COM address.” . . . From that experience, I developed my three “rules” of TLD acceptance: 1. An old TLD will be accepted more often than a new TLD. 2. An ASCII-only TLD will be accepted more than an IDN TLD. 3. A three-letter gTLD will be accepted more often than a longer string, even if it's a gTLD . . . . " (read more at link above)
more news links below
Follow @expvccom
