From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.lang.hm (unknown [66.167.227.145]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id D32B93B29E for ; Tue, 22 Nov 2022 14:10:21 -0500 (EST) Received: from asgard.lang.hm (syslog [10.0.0.100]) by mail.lang.hm (Postfix) with ESMTP id 9ADC815A7D7; Tue, 22 Nov 2022 11:10:20 -0800 (PST) Date: Tue, 22 Nov 2022 11:10:20 -0800 (PST) From: David Lang X-X-Sender: dlang@asgard.lang.hm To: Kenneth Porter cc: Bufferbloat Mailing List In-Reply-To: <24245B24B6DE0F3A14466760@[192.168.69.69]> Message-ID: References: <24245B24B6DE0F3A14466760@[192.168.69.69]> User-Agent: Alpine 2.02 (DEB 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: Re: [Bloat] Precision Time Protocol (PTP) X-BeenThere: bloat@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: General list for discussing Bufferbloat List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Nov 2022 19:10:22 -0000 As I understand PTP, you can't get 'acceptable' accuracy with general purpose hardware. 'acceptable' as defined by the time geeks. unfortunantly, their insistance on perfection seems to be blocking anything better than ntp. A few years ago I found PTP and thought it would be interesting to use to try to time music playing from multiple devices (fireworks shows), but could not find any implementation that could easily be used. David Lang On Tue, 22 Nov 2022, Kenneth Porter via Bloat wrote: > A nanosecond-scale replacement for NTP? This looks useful for measuring > latency. Lots of technical implementation details here, down to the > hardware level. > > > > _______________________________________________ > Bloat mailing list > Bloat@lists.bufferbloat.net > https://lists.bufferbloat.net/listinfo/bloat >