> c. It might be possible to construct a binary string in some legacy > encoding which gives the same binary representation for another domain > name (a.k.a. binary collision). > > This is a big problem in my mind. Sending unidentified codepage data > could create all sorts of opportunities for spoofing, and more mundane > problems like DNS caches giving out the wrong answer. Yes. So the workaround would involve preventing binary collision in the first place. -James Seng
- [idn] Internet Draft uname.txt James Seng/Personal
- Re: [idn] Internet Draft uname.txt Yoshiro YONEYA
- RE: [idn] Internet Draft uname.txt Brian W. Spolarich
- Re: [idn] Internet Draft uname.txt James Seng/Personal
- Re: [idn] Internet Draft uname.txt James Seng/Personal
- Re: [idn] Internet Draft uname.txt J. William Semich
- Re: [idn] Internet Draft uname.txt Yoshiro YONEYA
- Re: [idn] Internet Draft uname.txt Adam M. Costello
- Re: [idn] Internet Draft uname.txt Maynard Kang
- Re: [idn] Internet Draft uname.txt Mark Davis
- RE: [idn] Internet Draft uname.txt Kenny Huang
- Re: [idn] Internet Draft uname.txt James Seng/Personal
