Query about Time-to-check-back in TCP based Time-stamping

"Prashant Dambe" <prashant@elock.co.in> Thu, 22 March 2001 04:48 UTC

Received: from above.proper.com (above.proper.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA11154 for <pkix-archive@odin.ietf.org>; Wed, 21 Mar 2001 23:48:40 -0500 (EST)
Received: from localhost (daemon@localhost) by above.proper.com (8.9.3/8.9.3) with SMTP id UAA24000; Wed, 21 Mar 2001 20:47:46 -0800 (PST)
Received: by mail.imc.org (bulk_mailer v1.12); Wed, 21 Mar 2001 20:47:44 -0800
Received: from pdcpune.elock.co.in (pdcpune.elock.co.in [196.1.104.8]) by above.proper.com (8.9.3/8.9.3) with ESMTP id UAA23970 for <ietf-pkix@imc.org>; Wed, 21 Mar 2001 20:47:42 -0800 (PST)
Received: from insight (insight.fcpl.co.in [196.1.104.150]) by pdcpune.elock.co.in with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21) id HDBQCVZJ; Thu, 22 Mar 2001 10:17:07 +0530
Message-ID: <001e01c0b28b$34d338b0$966801c4@insight>
From: Prashant Dambe <prashant@elock.co.in>
To: ietf-pkix@imc.org
Subject: Query about Time-to-check-back in TCP based Time-stamping
Date: Thu, 22 Mar 2001 10:17:32 +0530
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_001B_01C0B2B9.4E6FFD70"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Precedence: bulk
List-Archive: http://www.imc.org/ietf-pkix/mail-archive/
List-ID: <ietf-pkix.imc.org>
List-Unsubscribe: mailto:ietf-pkix-request@imc.org?body=unsubscribe

Draft for Time-stamp says
TCP-based protocol is to be used for transport of TSA messages.
This protocol is suitable for cases where an 
entity initiates a transaction and can poll to pick up the results.
The "time-to-check-back" parameter is an unsigned 32-bit integer, 
defined to be the number of seconds that have elapsed since midnight, 
January 1, 1970, coordinated universal time.
It provides an estimate of the time that the end entity should send 
its next pollReq.

It means local clock has to synchronized with TS-Server clock to use
properly the time-to-check-back field.