Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Could you please provide a proof (e.g. and RFC section) that 7bit ASCII characters (like plain old ASCII space, code 0x20) that were previously illegal are still disallowed in IDNs?

share|improve this question

closed as not a real question by Tom O'Connor, Dan, gWaldo, Mike Pennington, pauska Aug 7 '12 at 23:37

It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.If this question can be reworded to fit the rules in the help center, please edit the question.

This question actually asks for a formal proof of the accepted answer in… – Yury Kartynnik Aug 1 '12 at 17:05
up vote 0 down vote accepted

How about RFC5894, section 3.

IDNA2008 adopts the inclusion model. A code point is assumed to be invalid for IDN use unless it is included as part of a Unicode property-based rule or, in rare cases, included individually by an exception.

And in Section 3.1:

IDNA2008 divides all possible Unicode code points into four categories: PROTOCOL-VALID, CONTEXTUAL RULE REQUIRED, DISALLOWED, and UNASSIGNED.

And now, RFC5892 sections 2 and 3 name the allowed code points.


2.1. allows "LetterDigits" note that doesn't say punctuation...

2.2. disallows "Unstable" things that are disputed or variable or not yet confirmed.

2.3. disallows "IgnorableProperties" includes Default_Ignorable_Code_Point, White_Space, & Noncharacter_Code_Point

2.4. disallows "IgnorableBlocks" including diacritical marks and formatting characters

2.5. specifically allows "LDH" which is the usual ASCII allowed by old-skool DNS within Unicode {002D, 0030..0039, 0061..007A}

2.6. specifies "Exceptions" which covers certain characters marked in Unicode as one of the disallowed classes that nevertheless are needed for one language or another

2.7. through 2.10. covers even more obscure cases and future proofing for things that change status as Unicode evolves.

share|improve this answer
So LDH is the only ASCII subset that is allowed for IDNs, right? – Yury Kartynnik Aug 2 '12 at 8:42
Best I can tell. You'd have to read the Unicode spec for each character to see what categories it falls into. Ugly. ;-) – Mark Aug 2 '12 at 18:49

Could you please provide a proof (e.g. and RFC section) that 7bit ASCII characters (like plain old ASCII space, code 0x20) that were previously illegal are still disallowed in IDNs?

Quoting RFC 5564, Section 2.3.2:

The space character is strictly disallowed in domain names, as it is a control character. Instead, the hyphen (Al-sharta, i.e., u+02D) is proposed as a separator between Arabic words to avoid confusion that can take place if the words are typed without a separator.

It is acceptable to use the hyphen to separate between words within the same domain name label.

share|improve this answer
The document you are citing is titled "Linguistic Guidelines for the Use of Arabic Language in Internet Domains", and it states that "This document is not an Internet Standards Track specification; it is published for informational purposes." As such, it doesn't seem to be a general IDN guideline. – Yury Kartynnik Aug 1 '12 at 16:55
The second point is: space was only an example, what about an apostrophe or a question mark? – Yury Kartynnik Aug 1 '12 at 16:57

Not the answer you're looking for? Browse other questions tagged or ask your own question.