MIME-Version: 1.0
In-Reply-To: <rt-4.2.8-43911-1494545813-37.41976-0-0@isc.org>
X-Mailer: MIME-tools 5.505 (Entity 5.505)
Content-Disposition: inline
X-RT-Interface: Web
References: <RT-Ticket-41976@isc.org>
 <143325082.244893.1458230693053.JavaMail.yahoo.ref@mail.yahoo.com>
 <143325082.244893.1458230693053.JavaMail.yahoo@mail.yahoo.com>
 <1436676531.343933.1458236010909.JavaMail.yahoo@mail.yahoo.com>
 <2136884451.1058356.1458326519850.JavaMail.yahoo@mail.yahoo.com>
 <195690069.1268703.1458348413110.JavaMail.yahoo@mail.yahoo.com>
 <182005532.1332564.1458348598299.JavaMail.yahoo@mail.yahoo.com>
 <rt-4.2.8-23330-1494441757-1941.41976-5-0@isc.org>
 <1604477229.7685346.1494545808414@mail.yahoo.com>
 <rt-4.2.8-43911-1494545813-37.41976-0-0@isc.org>
Content-Type: text/plain; charset="utf-8"
Message-ID: <rt-4.2.8-78629-1494574497-1437.41976-0-0@isc.org>
Content-Transfer-Encoding: binary
X-RT-Original-Encoding: utf-8
RT-Send-CC:
X-RT-Encrypt: 0
X-RT-Sign: 0
Content-Length: 473

On Thu May 11 23:36:53 2017, alessandro.gherardi@yahoo.com wrote:
> Hi Thomas,Thank you for the update.
> I have a question: Since the failover protocol uses 32-bits
> timestamps, it is not y2k38 safe. Correct?

=> half correct: the failover uses unsigned timestamps,
the y2k38 issue is for signed timestamps, e.g. ANSI time_t.

> Does your fix include changing protocol to make it y2k38 safe,
> or will that still be an issue?

=> no, it should break in 21 years...