- Overview
- Configuration
- NTP4 Plug-In
- Hardware
- RFC 868
- RFC 2030
-
RFC 1305
- RFC 1305
- 1. Introduction
- 1.1 Related Technology
- 2. System Architecture
- 2.1 Implementation Model
- 2.2 Network Configurations
- 3. Network Time Protocol
- 3.1 Data Formats
- 3.2 State Variables and Parameters
- 3.2.1 Common Variables
- 3.2.2 System Variables
- 3.2.3 Peer Variables
- 3.2.4 Packet Variables
- 3.2.5 Clock-Filter Variables
- 3.2.6 Authentication Variables
- 3.2.7 Parameters
- 3.3 Modes of Operation
- 3.4 Event Processing
- 3.4.1 Notation Conventions
- 3.4.2 Transmit Procedure
- 3.4.3 Receive Procedure
- 3.4.4 Packet Procedure
- 3.4.5 Clock-Update Procedure
- 3.4.6 Primary-Clock Procedure
- 3.4.7 Initialization Procedures
- 3.4.7.1 Initialization Procedure
- 3.4.7.2 Initialization-Instantiation Procedure
- 3.4.7.3 Receive-Instantiation Procedure
- 3.4.7.4 Primary Clock-Instantiation Procedure
- 3.4.8 Clear Procedure
- 3.4.9 Poll-Update Procedure
- 3.5 Synchronization Distance Procedure
- 3.6 Access Control Issues
- 4. Filtering and Selection Algorithms
- 4.1 Clock-Filter Procedure
- 4.2 Clock-Selection Procedure
- 4.2.1 Intersection Algorithm
- 4.2.2. Clustering Algorithm
- 5. Local Clocks
- 5.1 Fuzzball Implementation
- 5.2 Gradual Phase Adjustments
- 5.3 Step Phase Adjustments
- 5.4 Implementation Issues
- 6. Acknowledgments
- 7. References
- Appendix A
- Appendix B
- Appendix C
- Appendix D
- Appendix E
- Appendix F
- Appendix G
- Appendix H
- Appendix I
- Time Tools
- NTP Auditor
- About
| Previous Top Next |
Windows Time Server
Network Time SynchronizationA typical network time synchronization scenario is depicted in the diagram shown below.
In this scenario, each workstation synchronizes to a central time server on the corporate LAN. The server operates PresenTense Time Server software to synchronize its own clock to both the in-house GPS Master Clock and atomic clock time sources on the internet. Each work station in turn operates PresenTense Time Client software to synchronize to the corporate server. This model gives the accuracy of a local GPS clock as well as leveraging internet based atomic clocks as a backup source.
For applications where time accuracy requirements are even higher or corporate security policies do not allow external time source synchronization, PresenTense Time Server can be configured to synchronize with multiple GPS time sources.