[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[idn] Re: about NSI ML-testbed and i-DNS proxy's vulnerability
- To: "Soobok Lee" <lsb@postel.co.kr>, <idn@ops.ietf.org>
- Subject: [idn] Re: about NSI ML-testbed and i-DNS proxy's vulnerability
- From: "James Seng" <James@Seng.cc>
- Date: Mon, 30 Oct 2000 09:48:26 +0800
- Cc: <wissorh@ar.com>
- Delivery-date: Sun, 29 Oct 2000 17:53:21 -0800
- Envelope-to: idn-data@psg.com
Cant comment on NSI.
However, I am kind of interested to know what 'i-DNS Proxy' you talking about
because there i-DNS.net has no "DNS-PROXY" solution. Neither has any of our
product is dependent on Netscape or IE or any platform in particular.
Secondly, ML.com is a special testbed and i-DNS.net has not even release any
software which is meant for ML.com yet. We are going to release certain
software designed to work with ML.com when the testbed starts.
So I don't know where you get these informations below and how you arrived to
the conclusion. Please clarify.
-James "speaking as i-DNS.net I suppose" Seng
> NSI's early Resolution phase appears to need a transistion solution ,
i-dnx proxy.
> But, i-DNS's DNS-PROXY fails to resolve
> native-code ML-queries from Netscape 4.X on WIN9X plaforms
> without CCS conflicts. NN on WIN9X does not speak UTF8 on HTTP and DNS
queries.
> It may mislead web surfers to wrong sites and may cause security
problems.
> It may isolate Netscape users from others, contrary to IAB's
recommendation RFC 2825.
> I-DNS proxy is dangerous to be deployed as a transition solution.
>
> Would you comment on this?