Re: Minor fixes to draft 05

>     No.  As Ben mentioned several times, it is ludicrous to suggest that
>     HTTP *implementations* should use NTP -- instead, the hosts running
>     HTTP should also run NTP.  If you can rephrase that in a better way, fine,
>     but the existing text is just plain bogus.
> 
> OK, so your intention was not to exclude intranet hosts, but merely
> to shift the locus of the NTP suggestion from "HTTP implementation"
> to "host that uses HTTP".  (I re-read Ben's message, and this was NOT
> his main objection; he seems to have incorrectly assumed that use of
> NTP requires Internet connectivity.)

I may have expressed myself poorly but my objection was as Roy states. I did
also mention that not all networks have NTP available to them (and yes, of
course, networks not connected to the Internet can run NTP but how easily can
they get accurate time to run it from?).

Regardless of what I said, I agree with Roy's change (or your version of it)
;-)

Cheers,

Ben.

> 
> So I think you and I would be in agreement that this wording should
> be used:
> 
>     In this discussion, we use the term "now" to mean "the current
>     value of the clock at the host performing the calculation."
>     Internet or intranet hosts that use HTTP, particularly those
>     hosting origin servers and caches, should use NTP [28] or some
>     similar protocol to synchronize their clocks to a globally accurate
>     time standard.
> 
> Or simply "Hosts that use HTTP, ..."
> 
> -Jeff
> 

-- 
Ben Laurie                  Phone: +44 (181) 994 6435
Freelance Consultant and    Fax:   +44 (181) 994 6472
Technical Director          Email: ben@algroup.co.uk
A.L. Digital Ltd,           URL: http://www.algroup.co.uk
London, England.

Received on Thursday, 4 July 1996 04:21:22 UTC