Paul Hoffman / IMC �g�J�G > At 10:36 AM +0800 10/29/01, xiang deng wrote: > >On Sunday, October 28, 2001 11:27 PM, Martin Duerst wrote: > > > >>� > > Do you have any statistic on how many mixed TC/SC registration have > >>� been > >>� > > done so far? > >>� > > >>� >If there just has 1% or 0.1% , do you mean we can ignore it? > >> > >>� It could be that we can ignore it, or that we can look for > >>� lightweight solutions. > > > >If A company register a SC-domain-name, and has a websit about it. > >if B company is the challenger of A, he register a mixed TC/SC domain > >name, and publish its websit. > > > >Do you think this kind of cases will be minority? > > Yes, and it happens all the time with the current ASCII-only names. > The traditional-simplified mappings will cause more of the same thing > we see now. > > >The A company must face the disputation.But there will be > >so many variant domain names, A company will be tired to > >deal with it, Where is the intelligent property of domain name? > >Whoes wrong? > > No one. That's the point. There is no technical means for determining > all of the names that are similar for a particular audience.
If we consider TC/SC are not the names similar but just like Uppercase/Lowercase English letter. But we do not want TC/SC to be folding to one side. User can use all TC(Uppercase) or all SC(Lowercase) or mixed TC/SC(Uppercase/Lowercase) as they presumed. And we need the DNS treat TC/SC(Uppercase/Lowercase) as the same when compare with cache RR. > There > are certainly non-technical human means for determining those names, > and we currently use non-technical human means for dealing with the > problems. If you think of TC/SC requirement is non-technical human means, then hou about Uppercase/Lowercase English letter deal in DNS? > � > --Paul Hoffman, Director > --Internet Mail Consortium Erin Chen �
