[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [idn] Prohibit CDN code points

Dear Ko:
        You are right. In current discussion , my proposal is not interested
in DNS server approach. I talk it , because some people worry about the
prohibitation of CDN code points in IDNA will let some area can not work.
So, I give some solutions to let them can be done by area/language TLD
dependent name solving to reduce the troubles of CDN delay.
        The second reason is that some client has the caching feature, but
the caching client actually need not only just the same matching rule as
authorized zone DNS if we assume  this client will query the authorized zone
DNS at first or refresh time. I think this description can help to remove
some misunderstanding of current BIND DNS cache. For example:
1.Assume authorized zone server is case insensitive and the record:
bq--xyz   A  1.2.3.4

2.Assume client is case sensitive in matching  records in local cache. These
query will be get and copied result from authorized server.
bq--xYz   A  1.2.3.4
bq--XYZ   A  1.2.3.4
bq--xyz   A  1.2.3.4

  That means if caching client has capability of differentiating than zone
server will still work.
  To force the query information to lower case and store it in local client
is not so necessary to a case insensitive DNS server.
That is my point about IDNA nameprep.

L.M.Tseng
----- Original Message -----
From: "YangWoo Ko" <newcat@spsoft.co.kr>
To: "IETF-IDN" <idn@ops.ietf.org>
Sent: Wednesday, January 23, 2002 8:57 PM
Subject: Re: [idn] Prohibit CDN code points


> Dear Tseng,
>
> Please correct me if I am wrong. As far as I know, you are not going to
> add more rules to DNS server. Instead, some IDNA implementations may have
> more features to comply with CDN requirement. But, this specific thread
> is about whether it is good or not to make DNS server having language
> depending features. So, your answers on this specific thread made me
> be totally confused.
>
> My best regards
>
> On Wed, Jan 23, 2002 at 07:50:42PM +0800, tsenglm@計網中心.中大.tw wrote:
> >
> > ----- Original Message -----
> > From: "Patrik F??ltstr??m" <paf@cisco.com>
> > To: "Edmon" <edmon@neteka.com>; "Masahiro Sekiguchi"
<seki@jp.fujitsu.com>;
> > "IETF-IDN" <idn@ops.ietf.org>
> > Sent: Wednesday, January 23, 2002 6:08 PM
> > Subject: Re: [idn] Prohibit CDN code points
> >
> >
> > > --On 2002-01-22 15.51 -0500 Edmon <edmon@neteka.com> wrote:
> > >
> > > > This is not true. As long as the .cn DNS does the matching
internally
> > and
> > > > provide a consistent response, why would "all" servers in the world
need
> > > > to be able to fulfil the matchings?  If you are arguing how the
> > > > application then use the information to connect to the destination
> > > > server, thats another issue.  But by zone rules are possible.
> > >
> > > No, because you will have a caching DNS server which also have to be
able
> > > to do matchings for things in the .cn TLD. This means that any caching
DNS
> > > server have to have the complete set of rules used in all zones in the
> > DNS.
> > >
> >
> >          It is right, cache DNS will cause some problems. But the
caching
> > DNS need not only to have the complete set of rules used in authorized
zone
> > DNS . If  the caching DNS use the matching rule with the capability of
> > differentiation  more than authorized zone server, it will work too.
> >          It is one of the possible solution in some particular condition
but
> > this is not the current issue of this thread.
> > L.M.Tseng
> >
> >
> >
>
> --
> /*------------------------------------------------
> YangWoo Ko : newcat@spsoft.co.kr
> We Invent Enterprise Software Solutions
> and Make You Secure & Powerful.
> ------------------------------------------------*/
>