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?
|
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, see the FAQ.
|
How about RFC5894, section 3. http://tools.ietf.org/html/rfc5894#page-9
And in Section 3.1:
And now, RFC5892 sections 2 and 3 name the allowed code points. http://tools.ietf.org/html/rfc5892 Specifically: 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. |
|||||
|
Quoting RFC 5564, Section 2.3.2:
|
|||||
|