Re: Tilde

Martin:

>>-- and that's my point -- and has remained my unanswered question. 
>>So, specifically why does the "process" (nameprep, rule #3, "plan 9 
>>from outer space", or whatever) prohibit code point 07E?
>
>Nameprep (RFC 1391) does not prohibit the character. Step 3 of ToASCII
>prohibits it for backwards compatibility, in order to protect the
>stability of the Domain Name System.

Okay, so rule #3 does prohibits the TILDE because of backward 
compatibility issues. I can understand that, if there are backward 
compatibility issues -- are there?

>>In summary, my claim is that if you can map uppercase "A" to 
>>lowercase "a", then you can map the TILDE to the TILDE OPERATOR.
>
>Yes, but that would have no effect to IDNA, as I have explained.
>Even though Nameprep also maps "A" to "a", that mapping has no effect
>for a pure ASCII label. Nameprep simply does not affect pure ASCII
>labels.

Okay, so Nameprep has nothing to do with it -- I picked the wrong 
procedure, my fault.

While using the TILDE might break previous 
protocols/procedures/whatever -- does that also mean: 1) the use of a 
replacement character (such as the TILDE OPERATOR) would break 
anything; 2) if the end-user entered a tilde character, is there no 
way for the IDNA protocol to map it to the TILDE OPERATOR; 3) is this 
just something that has not been, or will not be, considered; 4) or, 
is my ignorance of these issues just so bad that I'm not making any 
sense?

Respectfully,

tedd
-- 
--------------------------------------------------------------------------------
http://sperling.com/