Preferred PTP & NTP Formula reasoning : RS 00:00 02/08/2024

Compression competitiveness

Are you aware that LZ4 & Brotli-G are around 0.7GB/s decompression?
Both these are suitable for Mouse & Keyboard & Device Energy & data-rate cost reductions on 2.4G & WiFi & internal hardware..

Compression Formula : RS

Our main objective is to achieve universal support; NTP, DNS, Messaging & application..

Compression is faster & reduces costs on connections such as mobile,
We need to choose our compression well!
We need one that is universally supported!

Average compression level
LZ4 <> ZStandard, Brotli-G, GZip

Average speed
Brotli-G, LZ4 <> ZStandard, Brotli, GZip

https://en.wikipedia.org/wiki/Data_compression

RS

PTP timers are based on time stamps,

Time stamps are fast,
Latency between servers is calculated by a combination of accurate latency measurements combined with accurate clocks..

The basic parameter of a clock?

Time Stamp
Binary string
Numeric sequence
Timing packet

Timer signals are used for audio & video frame synchronisation on the internet..

Timer signals are used for all processes internally inside a computer system & the processor itself!

Timer signals control game actions & frame rate, They control the ticks of our clock, the motions of our Hard Drive..

Timer signals control our ram, our thread count & function cycle.

Firmware supported compressed time formula : PTP & NTP single packet multiple cycle sequence.

*

Preferred PTP & NTP Formula (c)RS

Preferring binary with GZip, Brotli & LZ4 compression is preferred,

Most network cards & motherboard firmware supports at a minimum LZ4 or GZip because the firmware bootloader has a compressed ROM,

Frequently LZ4 is supported.

Network packet exchange for supported compression with subtopic, Compression supported by the firmware!

The basic firmware support allows compression on device & not referring to the central processor for task offloading.

Preferred PTP & NTP Formula (c)RS

Compressed NTP & PTP Ultra high precision packet

processed for latency, rout & robust high precision clock adjustments.

Since buss protocols based on ethernet technology involve quick protocol scans,

Compression for storage, ram, gpu, 2.4G & wifi & other hardware; may take a maximum of 4 seconds to optimise with priority selection ML & System code..

Most likely faster! especially if generalised across class & function & thus optimised through tables of logic.

Protocol Table:

Per device internal probe & declare

Packet negotiations (cache saved for reuse)

The table will be the sum of the preferred compression & protocol methods by task optimised preference & shall not give specific details away.

Firmware supported compression per device.

Device level intrinsics : Brotli & GZip & LZ4 & LZO-modern offer advanced high quality compression..

Brotli & GZip is not necessarily going to tell all devices on the path; The time! but lz4 & lzo probably will,

We need Sync to work & for that we need an intrinsic format for compression that devices internally support!

LZ4 compression is used in most firmware's so is a very logical choice for PTP & NTP network protocols, But we can use others..

LZ4, Brotli-G, GZip, LZO; The common ones in web standards arranged in terms of speed Brotli-G, LZ4, GZip, LZO

Average compression level
LZ4 <> ZStandard, Brotli-G, GZip

Average speed
Brotli-G, LZ4 <> ZStandard, Brotli, GZip

Send preferred compression list based on parsing of closest device on the sending path:

Device to device priorities

Network card, Wifi, Router etcetera
Motherboard support
Central processor support

Packets shall then consist of time stamps & -+ latency adjusters & a detailed 1 to 32 Byte group, reason says 64Byte..
Compressed time packet : NTP & PTP Ultra high precision packet.

This shall be processed for latency, rout & robust high precision clock adjustments.

*

Compressed Context Blocks:
DNS & PTP grouped messaging & grouping menus & chat contexts in compression context blocks improves performance!
Allowing JS, JSon & PHP, HTML & CSS to be highly efficient.

Compressed Menu Context : So a menu context is like so : Menu { A=X,Y,Z, B=X,Y,Z, C=X,Y,Z, D=X,Y,Z }; Menu = A, B, C, D = Lists {X, Y, Z}

RS

*

WelcomeClient-TLS:ClintEastward-TLS

Per Site Storage & App Storage:

We can do several things that require complex support..

Universal18 Open Anonymous Rights Verifier : TLS Certificate
Personal Client Certificate,
Streamer key, personal webcam protection (while viewing u)
Compression Brotli-G, LZ4, ZStandard, GZip between worker & client saving money

(c)RS https://is.gd/DictionarySortJS

*

GZip & Brotli, Yes GZip/LZ4 DNS/NTP Works!
https://www.websiteplanet.com/webtools/gzip-compression/?gzip=https://dns.google.com
https://www.websiteplanet.com/webtools/gzip-compression/?gzip=https://www.nist.gov

Compression speed comparisons for optimised tables
https://quixdb.github.io/squash-benchmark/#results-table

Compression Z-Standard, Brotli-G : Accept-Encoding: gzip, deflate, br, zstd, dcb, dcz
https://datatracker.ietf.org/doc/draft-ietf-httpbis-compression-dictionary/

PPP Negotiated compression for System Internals, Networks & 2.4G, 3G, 4G, Ethernet:
PPP:CCP : Internet Connection Protocol compression : 4-15 Available for dcb, br, dcz zstd, gzip, deflate,
While we are unlikely to require deflate; It is supported well; Recommended list dcb, br, dcz zstd, gzip, deflate

https://datatracker.ietf.org/doc/rfc1962/

Deflate 8:1 Example! not so bad!
https://is.gd/Deflate8xdata
https://is.gd/79erNTP_Logs

LZS : Packet configuration is worthy
https://datatracker.ietf.org/doc/rfc3943/

Client Hello
https://datatracker.ietf.org/doc/draft-ietf-tls-esni/

Server to Sub-server anonymous key exchange

Random Secure Key Exchange : NTP NTS Secure hash for PTP : NTS Key Establishment protocol & NTS Time Server Registration (NTS-TSR),
I suggest Private Key, Pre shared keys, Keyshare, Server Certificate model.

https://www.ietf.org/id/draft-ietf-ntp-nts-for-ptp-00.html

NTP & PTP Time Sync
https://datatracker.ietf.org/doc/draft-guo-detnet-jitter-reduction-mechanism/

https://datatracker.ietf.org/doc/draft-ietf-ntp-over-ptp/
https://datatracker.ietf.org/doc/draft-ietf-ntp-roughtime/

https://science.n-helix.com/2022/01/ntp.html
https://science.n-helix.com/2023/06/ptp.html

Radio & equipment automatic compression (c)RS :
Negotiated Compression is formulated based on the compression support available in firmware unpacking
https://is.gd/DictionarySortJS