Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Pulse-Per-Second API for UNIX-like Operating Systems, Version 1.0 (RFC2783)

IP.com Disclosure Number: IPCOM000003382D
Original Publication Date: 2000-Mar-01
Included in the Prior Art Database: 2000-Sep-13
Document File: 24 page(s) / 57K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

J. Mogul: AUTHOR [+5]

Abstract

RFC 1589 describes a UNIX kernel implementation model for high- precision time-keeping. This model is meant for use in conjunction with the Network Time Protocol (NTP, RFC 1305), or similar time synchronization protocols. One aspect of this model is an accurate interface to the high-accuracy, one pulse-per-second (PPS) output typically available from precise time sources (such as a GPS or GOES receiver). 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 text was extracted from a ASCII document.
This is the abbreviated version, containing approximately 5% of the total text.

Network Working Group J. Mogul

Request for Comments: 2783 Compaq WRL

Category: Informational D. Mills

University of Delaware

J. Brittenson

Sun

J. Stone

Stanford

U. Windl

Universitaet Regensburg

March 2000

Pulse-Per-Second API for UNIX-like Operating Systems, Version 1.0

Status of this Memo

This memo provides information for the Internet community. It does

not specify an Internet standard of any kind. Distribution of this

memo is unlimited.

Copyright Notice

Copyright (C) The Internet Society (2000). All Rights Reserved.

Abstract

RFC 1589 describes a UNIX kernel implementation model for high-

precision time-keeping. This model is meant for use in conjunction

with the Network Time Protocol (NTP, RFC 1305), or similar time

synchronization protocols. One aspect of this model is an accurate

interface to the high-accuracy, one pulse-per-second (PPS) output

typically available from precise time sources (such as a GPS or GOES

receiver). 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.

Table of Contents

1 Introduction................................................... 2

2 Data types for representing timestamps......................... 4

2.1 Resolution................................................... 4

2.2 Time scale................................................... 5

3 API............................................................ 5

3.1 PPS abstraction.............................................. 6

3.2 New data structures.......................................... 7

3.3 Mode bit definitions......................................... 10

3.4 New functions................................................ 12

3.4.1 New functions: obtaining PPS sources....................... 13

3.4.2 New functions: setting PPS parameters...................... 14

3.4.3 New functions: access to PPS timestamps.................... 16

3.4.4 New functions: disciplining the kernel timebase............ 18

3.5 C...