RFC 4330: Simple Network Time Protocol (SNTP) Version 4 for IPv4, IPv6 and OSI
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 5905.
Current document in this lineage: RFC 5905 — Network Time Protocol Version 4: Protocol and Algorithms Specification
In plain English — editorial summary, not part of the RFC
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. SNTPv4 can be used when the ultimate performance of a full NTP 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) mode with accuracy and reliability expectations similar to the UDP/TIME protocol described in RFC 868. This memorandum obsoletes RFC 1769, which describes SNTP Version 3 (SNTPv3), and RFC 2030, which describes SNTPv4. Its purpose is to correct certain inconsistencies in the previous documents and to clarify header formats and protocol operations for NTPv3 (IPv4) and SNTPv4 (IPv4, IPv6, and OSI), which are also used for SNTP. A further purpose is to provide guidance for home and business client implementations for routers and other consumer devices to protect the server population from abuse. A working knowledge of the NTPv3 specification, RFC 1305, is not required for an implementation of SNTP. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4330
- Published
- January 2006
- Authors
- D. Mills
- Status
- INFORMATIONAL
- Stream
- INDEPENDENT
- Area
- —
- Pages
- 27
- Also known as
- —
- Obsoleted by:
- RFC 5905
Topics
Standards lineage
This document is one revision in a chain of 9 RFCs, each formally replacing the one before it.
- RFC 958 (1985)
- RFC 1059 (1988)
- RFC 1119 (1989)
- RFC 1305 (1992)
- RFC 1361 (1992)
- RFC 1769 (1995)
- RFC 2030 (1996)
- RFC 4330 (2006)
- RFC 5905 (2010) ✓
Read the full history of Network Time Protocol Version 4: Protocol and Algorithms Specification →
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2783Pulse-Per-Second API for UNIX-like Operating Systems, Version 1.0Current
March 2000
- RFC 1119Network Time Protocol (version 2) specification and implementationObsoleted
September 1989
- RFC 1059Network Time Protocol (version 1) specification and implementationObsoleted
July 1988
- RFC 958Network Time Protocol (NTP)Obsoleted
September 1985
- RFC 1589A Kernel Model for Precision TimekeepingCurrent
March 1994
- RFC 10030Network Time Protocol (NTP) over the Precision Time Protocol (PTP)Current
August 2026
- RFC 1361Simple Network Time Protocol (SNTP)Obsoleted
August 1992
- RFC 9616Delay-Based Metric Extension for the Babel Routing ProtocolCurrent
September 2024
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?