RFC1589 on Kernel Model for Precision Timekeeping

"Joyce K. Reynolds" <jkrey@isi.edu> Thu, 03 March 1994 20:45 UTC

Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa10908; 3 Mar 94 15:45 EST
Received: from ietf.cnri.reston.va.us by CNRI.Reston.VA.US id aa16534; 3 Mar 94 15:45 EST
Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa10833; 3 Mar 94 15:44 EST
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa10727; 3 Mar 94 15:40 EST
Received: from zephyr.isi.edu by CNRI.Reston.VA.US id aa16424; 3 Mar 94 15:40 EST
Received: from zephyr.isi.edu by zephyr.isi.edu (5.65c/5.61+local-16) id <AA10173>; Thu, 3 Mar 1994 12:39:29 -0800
Message-Id: <199403032039.AA10173@zephyr.isi.edu>
To: IETF-Announce:;
Subject: RFC1589 on Kernel Model for Precision Timekeeping
Cc: jkrey@isi.edu
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Thu, 03 Mar 1994 12:39:29 -0800
Sender: ietf-announce-request@IETF.CNRI.Reston.VA.US
From: "Joyce K. Reynolds" <jkrey@isi.edu>

A new Request for Comments is now available in online RFC libraries.


        RFC 1589:

        Title:      A Kernel Model for Precision Timekeeping
        Author:     D. Mills
        Mailbox:    mills@udel.edu
        Pages:      37
        Characters: 92,260
        Updates/Obsoletes:  none


This memorandum describes an engineering model which implements a
precision time-of-day function for a generic operating system.  The
model is based on the principles of disciplined oscillators and
phase-lock loops (PLL) often found in the engineering literature.  It
has been implemented in the Unix kernel for several workstations,
including those made by Sun Microsystems and Digital Equipment.  The
model changes the way the system clock is adjusted in time and
frequency, as well as provides mechanisms to discipline its frequency
to an external precision timing source.  The model incorporates a
generic system-call interface for use with the Network Time Protocol
(NTP) or similar time synchronization protocol.  The NTP Version 3
daemon xntpd operates with this model to provide synchronization
limited in principle only by the accuracy and stability of the
external timing source.

This memo provides information for the Internet community.  This memo
does not specify an Internet standard of any kind.  Distribution of
this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@CNRI.RESTON.VA.US.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-REQUEST@NIC.DDN.MIL.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@ISI.EDU with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@ISI.EDU
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to admin@DS.INTERNIC.NET.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR@ISI.EDU.  Please consult RFC 1543, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.
ftp://ds.internic.net/rfc/rfc1589.txt"><ftp://ds.internic.net/rfc/rfc1589.txt>