Re: Re: 7 bits forever!

"Eric A. Hall" <[email protected]>
Newsgroups gmane.ietf.idn
Message-ID <[email protected]>
Edmon Chung wrote:

> The client app probably wont do any proactive recovery, but when the
> user initiates another query, it would try th UTF8 again, and fallback
> only if the request fails again.  In the meantime, the cache server
> will have ready the ACE respond already.  The cache resolver still
> performs its usual job, not the client app.  The client app is only
> responsible for the fallback mechanism.

All of that is true for both models. The difference is that if the cache
handles the non-fatal cases, then the application doesn't have to deal
with minor burps, and instead only has to deal with fatal failures.

> The reason really for this proposal is to make sure that DNSSEC works
> within the architecture.  If the resolver does any conversion, DNSSEC
> would have to be changed. But if the client falls back, the origination
> of the request as well as the authoritative response is not changed
> throughout the resolution path.

This is also true for both models.

-- 
Eric A. Hall                                        http://www.ehsco.com/
Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.