Skip to main content

Letter from Jonas Bjelfvenstam to Paul Twomey

Ministry of Industry, Employment and

State Secretary for Communications and Regional Policy
Jonas Bjelfvenstam


Dear Dr. Twomey,

First, let me thank you for the opportunity to discuss Internet matters with you at our meeting here in Stockholm October 6, 2003. Internet matters are also the reason for me addressing you now.

I have followed recent discussions by the Board of Directors of the Internet Corporation for Assigned Names and Numbers (ICANN) concerning the proposed top level domain (TLD) .xxx. I appreciate that the Board has deferred further discussions on the subject to its next meeting on September 15, 2005, taking account of requests from the applicant ICM, as well as the ICANN Governmental Advisory Committee (GAC) Chairman's and the US Department of Commerce's request to allow for additional time for comments by interested parties.

Sweden strongly supports the ICANN mission and the process making ICANN an organisation independent of the US Government. We appreciate the achievements of ICANN in the outstanding technical and innovative development of the Internet, an ICANN exercising open, transparent and multilateral procedures.

The technical development has also been a prerequisite to the enormous expansion of the quantity of pornography. This has made it easier to mainstream and normalize pornography and references to it in public spaces, like the Internet, in commercials and in the media in general. If pornographic material was hard to find earlier the situation is the opposite today - people have difficulties avoiding it.

The Swedish line on pornography is that it is not compatible with the gender equality goals. The constant exposure of pornography and degrading pictures in our everyday lives normalizes the exploitation of women and children and the pornography industry profits on the documentation.

A TLD dedicated for pornography might increase the volume of pornography on the Internet at the same time as foreseen advantages with a dedicated TLD might not materialize. These and other comments have been made in the many comments made directly to ICANN through the ICANN web site. There are a considerable amount of negative reactions within and outside the Internet community.

I know that all TLD applications are dealt with in procedures open to everyone for comment. However, in a case like this, where public interests clearly are involved, we feel it could have been appropriate for ICANN to request advice from GAC. Admittedly, GAC could have given advice to ICANN anyway at any point in time of the process and to my knowledge, no GAC members have raised the question before the GAC meeting July 9 - 12, 2005, in Luxembourg. However, we all probably rested assure that ICANN's negative opinion on .xxx, expressed in 2000, would stand.

From the ICANN decision on June 1, 2005, there was too little time for GAC to have an informed discussion on the subject at its Luxembourg summer meeting. One month would be to short time for governments independently on the subject matter. In this specific case, several countries raised serious concerns at the GAC meeting. However, there were to little information at hand to have an informed and fruitful discussion and hence no conclusions were reached on the subject.

Therefore we would ask the ICANN Board to postpone conclusive discussions on .xxx until after the upcoming GAC meeting in November 29 - 30, 2005, in Vancouver. That would give the GAC an opportunity to have an informed discussion on the subject. In due time before that meeting it would be helpful if ICANN could present in detail how it means that .xxx fulfils the criteria set in advance ("criteria for Independent Evaluators").

Jonas Bjelfvenstam

cc: Dr. Vinton Cerf (Senior Vice President, Technology
Strategy, MCI)
Mohamed Sharil Tarmizi (GAC Chairman)

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"""" is not an IDN."