Network Time Protocol | Wikipedia audio article
Channel: wikipedia tts
Date: 14/12/2018

This is an audio version of the Wikipedia Article:
Network Time Protocol


00:01:49 1 History
00:05:47 2 Clock strata
00:08:05 3 Timestamps
00:09:13 4 Clock synchronization algorithm
00:11:26 5 Software implementations
00:11:36 5.1 Reference implementation
00:12:33 5.2 SNTP
00:13:02 5.3 Windows Time service
00:14:13 5.4 OpenNTPD
00:14:54 5.5 Ntimed
00:15:34 5.6 NTPsec
00:16:14 5.7 Chrony
00:17:20 6 Leap seconds
00:18:18 7 Security concerns
00:21:04 8 See also



Listening is a more natural way of learning, when compared to reading. Written language only began at around 3200 BC, but spoken language has existed long ago.

Learning by listening is a great way to:
- increases imagination and understanding
- improves your listening skills
- improves your own spoken accent
- learn while on the move
- reduce eye strain

Now learn the vast amount of general knowledge available on Wikipedia through audio (audio article). You could even learn subconsciously by playing the audio while you are sleeping! If you are planning to listen a lot, you could try using a bone conduction headphone, or a standard speaker instead of an earphone.

You can find other Wikipedia audio articles too at:
https://www.youtube.com/channel/UCuKfABj2eGyjH3ntPxp4YeQ

You can upload your own Wikipedia articles through:
https://github.com/nodef/wikipedia-tts



"The only true wisdom is in knowing you know nothing."
- Socrates



SUMMARY
=======
The Network Time Protocol (NTP) is a networking protocol for clock synchronization between computer systems over packet-switched, variable-latency data networks. In operation since before 1985, NTP is one of the oldest Internet protocols in current use. NTP was designed by David L. Mills of the University of Delaware.
NTP is intended to synchronize all participating computers to within a few milliseconds of Coordinated Universal Time (UTC). It uses the intersection algorithm, a modified version of Marzullo's algorithm, to select accurate time servers and is designed to mitigate the effects of variable network latency. NTP can usually maintain time to within tens of milliseconds over the public Internet, and can achieve better than one millisecond accuracy in local area networks under ideal conditions. Asymmetric routes and network congestion can cause errors of 100 ms or more.The protocol is usually described in terms of a client-server model, but can as easily be used in peer-to-peer relationships where both peers consider the other to be a potential time source. Implementations send and receive timestamps using the User Datagram Protocol (UDP) on port number 123. They can also use broadcasting or multicasting, where clients passively listen to time updates after an initial round-trip calibrating exchange. NTP supplies a warning of any impending leap second adjustment, but no information about local time zones or daylight saving time is transmitted.The current protocol is version 4 (NTPv4), which is a proposed standard as documented in RFC 5905. It is backward compatible with version 3, specified in RFC 1305.