Re: [Tzdist] [tz] Timezone in Brazil

Lester Caine <lester@lsces.co.uk> Mon, 12 October 2015 08:51 UTC

Return-Path: <lester@lsces.co.uk>
X-Original-To: tzdist@ietfa.amsl.com
Delivered-To: tzdist@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9F8E41A895C for <tzdist@ietfa.amsl.com>; Mon, 12 Oct 2015 01:51:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VWAGOXzXWBJC for <tzdist@ietfa.amsl.com>; Mon, 12 Oct 2015 01:51:48 -0700 (PDT)
Received: from mail4.serversure.net (mail4.serversure.net [217.147.176.204]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 31A4B1A893C for <tzdist@ietf.org>; Mon, 12 Oct 2015 01:51:47 -0700 (PDT)
Received: (qmail 19726 invoked by uid 89); 12 Oct 2015 08:51:45 -0000
Received: by simscan 1.3.1 ppid: 19719, pid: 19723, t: 0.1042s scanners: attach: 1.3.1 clamav: 0.96/m:52/d:10677
Received: from unknown (HELO ?10.0.0.8?) (lester@rainbowdigitalmedia.org.uk@86.189.144.232) by mail4.serversure.net with ESMTPA; 12 Oct 2015 08:51:45 -0000
To: Time Zone Data Distribution Service <tzdist@ietf.org>
References: <5A4DF0AAB9712D44A68CEB0278F6ED5A2549ADA9F7@AICEXMBXCL02.LGE.NET> <FAD2916B-8E7A-49F5-A0EE-B173A3104531@mac.com> <BLU185-W6869D5866CF2840EE88B90C2340@phx.gbl> <5A4DF0AAB9712D44A68CEB0278F6ED5A2549ADB0B5@AICEXMBXCL02.LGE.NET> <BLU185-W46E73842162C12C34B0F9CC2340@phx.gbl> <87zizruzd1.fsf@fastmail.com> <F1FFEEB5-B0C0-422B-A159-3448950D448C@alum.mit.edu> <561A4544.5000308@lsces.co.uk> <B553BC64-36B2-4463-B490-D3A96648365F@alum.mit.edu> <561AC26A.6040006@lsces.co.uk> <561AD0C0.9090406@cs.ucla.edu> <561ADC8E.2070201@lsces.co.uk> <561AE1A8.50209@cs.ucla.edu> <c2c676b8-4b37-4677-9283-36d263a05acf.maildroid@localhost> <561AF378.2080904@cs.ucla.edu>
From: Lester Caine <lester@lsces.co.uk>
Message-ID: <561B74A0.5020104@lsces.co.uk>
Date: Mon, 12 Oct 2015 09:51:44 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0
MIME-Version: 1.0
In-Reply-To: <561AF378.2080904@cs.ucla.edu>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/tzdist/34s7VhyYqPPBbGmw7rUzwW4Fq6E>
Subject: Re: [Tzdist] [tz] Timezone in Brazil
X-BeenThere: tzdist@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <tzdist.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tzdist>, <mailto:tzdist-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tzdist/>
List-Post: <mailto:tzdist@ietf.org>
List-Help: <mailto:tzdist-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tzdist>, <mailto:tzdist-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Oct 2015 08:51:50 -0000

On 12/10/15 00:40, Paul Eggert wrote:
> lester@lsces.co.uk wrote:
>> But you are always gambling that the client machine has actually
>> compiled WITH backzone? If it is missing then data prior to 1970 is
>> suspect.
> 
> If backzone is used to build the tzdist server's data, then the server
> contains more data, some good and some questionable.  Some of the good
> data is before 1970, and some after.  Some of the questionable data is
> before 1970, and some after.  In this sense, it's just the same as when
> backzone is not used.  So there's no good reason to require
> implementations to reject time stamps before 1970 merely because
> backzone is being used (or is not being used).
> 
> I get the sense that you're trying to shoehorn backzone into a slot that
> it's not designed for.  It appears that you want some indication of how
> reliable data are.  There is no such indication anywhere in the formal
> part of tzdata, nor in tzdist, and this is true regardless of whether
> backzone is used.

But all YOU are saying there is exactly what *I* am saying ... you can't
use tzdb for reliable conversions prior to 1970! ... because the data is
unreliable. There IS a good reason to reject if it is important that the
correct data is used for normalizing. In my own case I need some way to
ensure that backzone IS in use by clients since this provide a lot more
correct set of rules than a generic result, but as you say ... there is
simply no way of knowing just what the client has PRIOR TO 1970! It is a
gamble when it should clearly identify the source ... so that even
faulty results can be reliably recreated.

I would prefer that the backzone data was ALWAYS included and then one
can guarantee that the client has a complete set of rules, many of which
are more accurate prior to 1970 than if that additional data is simply
ignored. What would be safer is if the extra UK aliases simply did not
exist if they are not returning the data that they should be!

-- 
Lester Caine - G8HFL
-----------------------------
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk
Rainbow Digital Media - http://rainbowdigitalmedia.co.uk