Control Messages Protocol for Use with Network Time Protocol Version 4
draft-haberman-ntpwg-mode-6-cmds-02

Document Type Active Internet-Draft (candidate for ntp WG)
Last updated 2017-03-27 (latest revision 2016-10-17)
Stream IETF
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream WG state Call For Adoption By WG Issued
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                           D. Mills
Internet-Draft                                    University of Deleware
Intended status: Historic                               B. Haberman, Ed.
Expires: April 20, 2017                                              JHU
                                                        October 17, 2016

 Control Messages Protocol for Use with Network Time Protocol Version 4
                  draft-haberman-ntpwg-mode-6-cmds-02

Abstract

   This document describes the structure of the control messages used
   with the Network Time Protocol.  These control messages can be used
   to monitor and control the Network Time Protocol application running
   on any IP network attached computer.  The information in this
   document was originally described in Appendix B of RFC 1305.  The
   goal of this document is to provide a historic description of the
   control messages.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on April 20, 2017.

Copyright Notice

   Copyright (c) 2016 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must

Mills & Haberman         Expires April 20, 2017                 [Page 1]
Internet-Draft            NTP Control Messages              October 2016

   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Control Message Overview  . . . . . . . . . . . . . . . .   2
   2.  NTP Control Message Format  . . . . . . . . . . . . . . . . .   4
   3.  Status Words  . . . . . . . . . . . . . . . . . . . . . . . .   5
     3.1.  System Status Word  . . . . . . . . . . . . . . . . . . .   6
     3.2.  Peer Status Word  . . . . . . . . . . . . . . . . . . . .   8
     3.3.  Clock Status Word . . . . . . . . . . . . . . . . . . . .   9
     3.4.  Error Status Word . . . . . . . . . . . . . . . . . . . .  10
   4.  Commands  . . . . . . . . . . . . . . . . . . . . . . . . . .  10
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  12
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .  12
   7.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  14
   8.  Normative References  . . . . . . . . . . . . . . . . . . . .  14
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  14

1.  Introduction

   RFC 1305 [RFC1305] described a set of control messages for use within
   the Network Time Protocol (NTP) when a comprehensive network
   management solution was not available.  The definitions of these
   control messages were not promulgated to RFC 5905 [RFC5905] when NTP
   version 4 was documented.  These messages were intended for use only
   in systems where no other management facilities were available or
   appropriate, such as in dedicated-function bus peripherals.  Support
   for these messages is not required in order to conform to RFC 5905
   [RFC5905].  The control messages are described here as a historical
   record given their use within NTPv4.

1.1.  Control Message Overview

   The NTP Control Message has the value 6 specified in the mode field
   of the first octet of the NTP header and is formatted as shown in
   Figure 1.  The format of the data field is specific to each command
   or response; however, in most cases the format is designed to be
   constructed and viewed by humans and so is coded in free-form ASCII.
   This facilitates the specification and implementation of simple
   management tools in the absence of fully evolved network-management
   facilities.  As in ordinary NTP messages, the authenticator field
Show full document text