RFC 2783: Pulse-Per-Second API for UNIX-like Operating Systems, Version 1.0
In plain English — editorial summary, not part of the RFC
RFC 1589 did not define an API for managing the PPS facility, leaving implementors without a portable means for using PPS sources. This document specifies such an API. This memo provides information for the Internet community.
Document record
- Document ID
- RFC2783
- Published
- March 2000
- Authors
- J. Mogul; D. Mills; J. Brittenson; J. Stone; U. Windl
- Status
- INFORMATIONAL
- Stream
- Legacy
- Area
- —
- Pages
- 31
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2030Simple Network Time Protocol (SNTP) Version 4 for IPv4, IPv6 and OSIObsoleted
October 1996
- 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 4330Simple Network Time Protocol (SNTP) Version 4 for IPv4, IPv6 and OSIObsoleted
January 2006
- RFC 1589A Kernel Model for Precision TimekeepingCurrent
March 1994
- RFC 10030Network Time Protocol (NTP) over the Precision Time Protocol (PTP)Current
August 2026
- RFC 1769Simple Network Time Protocol (SNTP)Obsoleted
March 1995
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?