Return-Path: Received: from murder ([unix socket]) by eikenes.alvestrand.no (Cyrus v2.2.8-Mandrake-RPM-2.2.8-4.2.101mdk) with LMTPA; Sun, 27 Mar 2005 23:57:06 +0200 X-Sieve: CMU Sieve 2.2 Received: from localhost (localhost.localdomain [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 2159761B41 for ; Sun, 27 Mar 2005 23:57:06 +0200 (CEST) Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 30895-04 for ; Sun, 27 Mar 2005 23:57:01 +0200 (CEST) Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by eikenes.alvestrand.no (Postfix) with ESMTP id 7AC5161AD5 for ; Sun, 27 Mar 2005 23:57:01 +0200 (CEST) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DFfkf-0005O8-8A; Sun, 27 Mar 2005 16:56:57 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DFfkc-0005LQ-SJ for ltru@megatron.ietf.org; Sun, 27 Mar 2005 16:56:55 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA09202 for ; Sun, 27 Mar 2005 16:56:52 -0500 (EST) Received: from [63.247.76.194] (helo=montage.altserver.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DFfqz-00058k-3M for ltru@ietf.org; Sun, 27 Mar 2005 17:03:30 -0500 Received: from lns-p19-8-idf-82-65-71-22.adsl.proxad.net ([82.65.71.22] helo=jfc.afrac.org) by montage.altserver.com with esmtpa (Exim 4.44) id 1DFfkY-00084R-Tq; Sun, 27 Mar 2005 13:56:51 -0800 Message-Id: <6.1.2.0.2.20050327234016.03784a10@mail.jefsey.com> X-Sender: jefsey+jefsey.com@mail.jefsey.com X-Mailer: QUALCOMM Windows Eudora Version 6.1.2.0 Date: Sun, 27 Mar 2005 23:56:49 +0200 To: "Jon Hanna" , From: "JFC (Jefsey) Morfin" Subject: RE: [Ltru] Re: Registry in record-jar format In-Reply-To: <20050327183644.A64EE24C1FD9A@postie2.hosting365.ie> References: <4246EB5A.6FF1@xyzzy.claranet.de> <20050327183644.A64EE24C1FD9A@postie2.hosting365.ie> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - montage.altserver.com X-AntiAbuse: Original Domain - ietf.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - jefsey.com X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9 Cc: X-BeenThere: ltru@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Language Tag Registry Update working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: ltru-bounces@lists.ietf.org Errors-To: ltru-bounces@lists.ietf.org X-Virus-Scanned: amavisd-new at alvestrand.no At 20:36 27/03/2005, Jon Hanna wrote: >What is the "dumbest" device we're likely to want to have a cache of the >registry? > >This clearly isn't an elevator-control matter, but how much smarter than >that would something have to be before having a access to the registry is >useful, and hence before the size of the cache becomes a significant matter? Could the authors (or anyone have a good command of their intent) document the exact _use_ of the IANA files as they see it. - an application reads a langtag. - what does it do? - when is it going to need a IANA originated data? - will it be usually in the application code? will be it be updated in a parameter file? will it call the IANA? Should it call a cache/mirror? Then who should manage them? - which applications will do that? - how many times a day/month/year will this happen for a single user? or ISP? or designer? For example, I understand that the non documented CLDR application mostly needs the langtag as a reference and will maintain its own files to be themselves used by OS programmers. So the load should be very low, unless someone develops an updating tool direct from the IANA and people use it at each reboot. I am not sure about HTML and XML applications? I am not sure about the need of updates? Will it be on a regular basis, or when an error is met an update will be requested? Should there be a solution to prevent an application to loop (like there are tools for Whois from hat I know)? etc. We do have to document in detail the IANA section, and I am really at loss understanding what we are talking about. I maintain a daily review of the IANA files for ccTLDs (http://afrac.org/intldate.txt). It actually decreases the load on IANA since people know if there is an update of not for them to look. But if many people made the same thing as me for their own us, or if my cron had a problem, it could create an overload. Without that information the whole Draft does not make any sense, because it is to document a IANA service and there are different strategies to address the need, depending on the load it represents. jfc _______________________________________________ Ltru mailing list Ltru@lists.ietf.org https://www1.ietf.org/mailman/listinfo/ltru