madhuvarsha
2011-01-05, 09:27 PM
SNTP PDF (http://m2vtelecom.wordpress.com/2011/01/04/rfc-4330simple-network-time-protocol-sntp-version-4-for-ipv4-ipv6-and-osi/)
Simple Network Time Protocol (http://en.wikipedia.org/wiki/Network_Time_Protocol) (SNTP) Version 4 for IPv4 (http://en.wikipedia.org/wiki/IPv4), IPv6 (http://en.wikipedia.org/wiki/IPv6) and OSI (http://en.wikipedia.org/wiki/Open_Systems_Interconnection)
This memorandum describes the Simple Network Time Protocol Version 4 (SNTPv4), which is a subset of the Network Time Protocol (NTP) used to synchronize computer clocks in the Internet (http://en.wikipedia.org/wiki/Internet). SNTPv4 can be used when the ultimate performance of a full NTP implementation (http://en.wikipedia.org/wiki/Implementation) based on RFC 1305 is neither needed nor justified. When operating with current and previous NTP and SNTP versions, SNTPv4 requires no
changes to the specifications or known implementations, but rather clarifies certain design features that allow operation in a simple,stateless remote-procedure call (RPC (http://en.wikipedia.org/wiki/Remote_procedure_call)) mode with accuracy and reliability expectations similar to the UDP/TIME protocol described in RFC 868.
Simple Network Time Protocol (http://en.wikipedia.org/wiki/Network_Time_Protocol) (SNTP) Version 4 for IPv4 (http://en.wikipedia.org/wiki/IPv4), IPv6 (http://en.wikipedia.org/wiki/IPv6) and OSI (http://en.wikipedia.org/wiki/Open_Systems_Interconnection)
This memorandum describes the Simple Network Time Protocol Version 4 (SNTPv4), which is a subset of the Network Time Protocol (NTP) used to synchronize computer clocks in the Internet (http://en.wikipedia.org/wiki/Internet). SNTPv4 can be used when the ultimate performance of a full NTP implementation (http://en.wikipedia.org/wiki/Implementation) based on RFC 1305 is neither needed nor justified. When operating with current and previous NTP and SNTP versions, SNTPv4 requires no
changes to the specifications or known implementations, but rather clarifies certain design features that allow operation in a simple,stateless remote-procedure call (RPC (http://en.wikipedia.org/wiki/Remote_procedure_call)) mode with accuracy and reliability expectations similar to the UDP/TIME protocol described in RFC 868.