[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[idn] Requirements: caching servers
- To: idn@ops.ietf.org
- Subject: [idn] Requirements: caching servers
- From: Paul Hoffman / IMC <phoffman@imc.org>
- Date: Wed, 02 Feb 2000 09:40:27 -0800
- Delivery-date: Wed, 02 Feb 2000 09:45:43 -0800
- Envelope-to: idn-data@psg.com
Paragraph 3 of section 2.1 says:
>The protocol should also allow creation of caching servers that do not
>understand the charset in which a request or response is encoded. Such
>caching servers should work as well for IDNs as they do for current
>domain names. The caching server performs correctly if it gives the
>essentially the same answer (without the authoritative bit) as the
>master server would have if presented with the same request.
I propose we remove this requirement. It puts a burden on the caching
server that I don't think should be there. If IDN has only one encoding,
this is a non-issue and confusing. If IDN has more than one encoding, I
think that all caching servers should be able to resolve any requests
immediately and not have to pass off the request to someone who knows about
the encoding.
--Paul Hoffman, Director
--Internet Mail Consortium