Skip to main content

Opening ICANN Blogs for Comment

ICANN blogs ought to be one of the key tools to provide a wider understanding of ICANN's role and work as well as an accessible entry point for community newcomers to understand what is happening and why.

There's work to do on the presentation and organization of the blogging platform and we're thinking about what steps we can take. But the most obvious function of a blog is as a discursive platform. So we're going to let the conversation flow and open up comments on our ICANN blogs.

It's not a technical triumph, but it is a minor gamble with our resources. No organization wants to spend time monitoring the behavior of its community, but we assume that the courtesy and respect you wish for yourself will be given to others. As such, we will rely on post-moderation. Comments are posted immediately and we review them once they are live. The Expected Standards of Behavior Policy is the same for the wider organization. View our website Terms of Service. With comments now open, we hope blog posts can open up useful exchanges between community members and the blog authors.

Of course, if you have any thoughts, you can post them below.

Comments

    Graham Schreiber  14:41 UTC on 07 November 2015

    Why do ICANN allow CentralNic, a Domain Name Registrant to violate the RAA; and Infringe Domain Names under #dotCOM which are Marks, Trade Name's & Trademarks, recognized by the USPTO as being ~ Unregistered ~ none the less covered under United States Common Law, via the Lanham Act, whose Jurisdiction & Venue is Alexandria, in the Eastern District of Virginia? Why further, when a Domain Name, Mark, Trade Name & Trademark gains official recognition by the USPTO as an ® doesn't ICANN's Contractual Compliance Department concern themselves with the fact that failing to observe "Red Flags" makes them Contributory Infringers, when told on multiple occasions? ICANN might like to read a brilliant article, unbiasedly penned by their own bespoke Attorneys at Jones Day titled: "Combating Contributory Infringement" [1] which hooks ICANN to "Instrumentality used to infringe". ICANN can't claim to be oblivious to CentralNic! After all, CentralNic lobbied ICANN long, long ago to have .UK.com transition at the DNSO [2] from lowly Domain Name to NEW gTLD, back at the ICANN Meeting in Japan, in 2000, [3] where it should be noted the elevation request was not "granted". Why too would ICANN; and the NTIA allow a #dotCOM Domain Name Registrant to evade the ACPA, a United States Law, aided abetted by WIPO? After all, #dotCOM Domain Names, even ones that are Spurious Mark #dotCOM ccNSO ccTLDs don't "fall between the cracks" [4] "of ccTLD and GTLD registries and outside the normal jurisdiction of ICANN"!. Cheers, Graham. ___________________ [1] Source: http://www.jonesday.com/files/Publication/cb405aa3-30fc-45b0-a025-6bd42493221c/Presentation/PublicationAttachment/b60b2502-8558-42ba-b2f3-447269e2d6b6/CombatingContributoryInf.pdf [2] Source: https://archive.icann.org/en/dnso/constituency_groups.html [3] Source: http://www.theguardian.com/technology/2000/sep/10/money.efinance [4] Source: http://www.wipo.int/amc/en/processes/process2/rfc/rfc3/comments/msg00060.html

    Chris Gift  14:20 UTC on 10 November 2015

    Graham I appreciate your comment and thoughts, but it's unclear how they're relevant to the blog post. Best Chris

    Graham Schreiber  05:27 UTC on 16 November 2015

    Hi Chris: ICANN Contractual Compliance talk a good game; however they don't follow through on their ... "goal, which is to ensure that the contracted parties comply with their contracts with ICANN.". Source of quote: http://www.inta.org/INTABulletin/Pages/ICANN_Interview_7013.aspx#.VabJsK5KiMc.twitter The fact of the matter is, ICANN allow a Domain Name Registrant, CentralNic to actively violate "The Lanham Act" with their Fake.CC.COMs, deployed specifically to Infringe, Dilute and Blur the Common Law protected Marks, Trade Names and Trademarks (TM) which are Common Law, with or without relief, in Virginia, contingent on being either In Rem or In Personam to Virginia. ICANN and the NTIA; have ~ knowingly ~ allowed CentralNic to construct; and maintain their own Protection Racket. Owners of USPTO ® Trademarks should not have to negotiate with a firm who actively Induce Infringement, as a Contributory aide to Wilful Infringers, inside the .COM TLD. Nor should we be obliged to Defensively RE-Register our ".COM" Brands with CentralNic, or their "ICANN Accredited" participants, via Virginia; all supported by bad actor VeriSign, who are the worlds exclusive .COM Registry, who wholesale to their supporting registrar Registries, going to retail. Simply put, ICANN support Racketeering, through their failure to enforce the RA & RAA; and are therefore complicit to Racketeering themselves, as Hosts & Sponsors of the Instrumentality used to Infringe.

    vishal kawatra  19:05 UTC on 27 November 2015

    Has anyone posted an informative youtube video on introducing ICANN or similar ? if so kindly share , it would be greatly appreciated . http://www.adlershof.de/en/news/the-perfect-place-for-us/

    Femme mature  01:22 UTC on 22 December 2015

    Thanks for this initiative

Domain Name System
Internationalized Domain Name ,IDN,"IDNs are domain names that include characters used in the local representation of languages that are not written with the twenty-six letters of the basic Latin alphabet ""a-z"". An IDN can contain Latin letters with diacritical marks, as required by many European languages, or may consist of characters from non-Latin scripts such as Arabic or Chinese. Many languages also use other types of digits than the European ""0-9"". The basic Latin alphabet together with the European-Arabic digits are, for the purpose of domain names, termed ""ASCII characters"" (ASCII = American Standard Code for Information Interchange). These are also included in the broader range of ""Unicode characters"" that provides the basis for IDNs. The ""hostname rule"" requires that all domain names of the type under consideration here are stored in the DNS using only the ASCII characters listed above, with the one further addition of the hyphen ""-"". The Unicode form of an IDN therefore requires special encoding before it is entered into the DNS. The following terminology is used when distinguishing between these forms: A domain name consists of a series of ""labels"" (separated by ""dots""). The ASCII form of an IDN label is termed an ""A-label"". All operations defined in the DNS protocol use A-labels exclusively. The Unicode form, which a user expects to be displayed, is termed a ""U-label"". The difference may be illustrated with the Hindi word for ""test"" — परीका — appearing here as a U-label would (in the Devanagari script). A special form of ""ASCII compatible encoding"" (abbreviated ACE) is applied to this to produce the corresponding A-label: xn--11b5bs1di. A domain name that only includes ASCII letters, digits, and hyphens is termed an ""LDH label"". Although the definitions of A-labels and LDH-labels overlap, a name consisting exclusively of LDH labels, such as""icann.org"" is not an IDN."