Control Messages Protocol for Use with Network Time Protocol Version 4
draft-ietf-ntp-mode-6-cmds-05

Document Type Active Internet-Draft (ntp WG)
Last updated 2018-07-16 (latest revision 2018-03-26)
Replaces draft-haberman-ntpwg-mode-6-cmds
Stream IETF
Intended RFC status Informational
Formats plain text pdf html bibtex
Stream WG state In WG Last Call
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Yes
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                           D. Mills
Internet-Draft                                    University of Delaware
Intended status: Informational                          B. Haberman, Ed.
Expires: September 27, 2018                                          JHU
                                                          March 26, 2018

 Control Messages Protocol for Use with Network Time Protocol Version 4
                     draft-ietf-ntp-mode-6-cmds-05

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 as described in RFC 1305 and any additional commands
   implemented in NTP.

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 https://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 September 27, 2018.

Copyright Notice

   Copyright (c) 2018 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
   (https://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

Mills & Haberman       Expires September 27, 2018               [Page 1]
Internet-Draft            NTP Control Messages                March 2018

   to this document.  Code Components extracted from this document must
   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.

   This document may contain material from IETF Documents or IETF
   Contributions published or made publicly available before November
   10, 2008.  The person(s) controlling the copyright in some of this
   material may not have granted the IETF Trust the right to allow
   modifications of such material outside the IETF Standards Process.
   Without obtaining an adequate license from the person(s) controlling
   the copyright in such materials, this document may not be modified
   outside the IETF Standards Process, and derivative works of it may
   not be created outside the IETF Standards Process, except to format
   it for publication as an RFC or to translate it into languages other
   than English.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Control Message Overview  . . . . . . . . . . . . . . . .   3
     1.2.  Remote Facility Message Overview  . . . . . . . . . . . .   4
   2.  NTP Control Message Format  . . . . . . . . . . . . . . . . .   4
   3.  Status Words  . . . . . . . . . . . . . . . . . . . . . . . .   7
     3.1.  System Status Word  . . . . . . . . . . . . . . . . . . .   8
     3.2.  Peer Status Word  . . . . . . . . . . . . . . . . . . . .  10
     3.3.  Clock Status Word . . . . . . . . . . . . . . . . . . . .  12
     3.4.  Error Status Word . . . . . . . . . . . . . . . . . . . .  12
   4.  Commands  . . . . . . . . . . . . . . . . . . . . . . . . . .  13
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  16
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .  16
   7.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  18
   8.  Normative References  . . . . . . . . . . . . . . . . . . . .  18
   Appendix A.  NTP Remote Facility Message Format . . . . . . . . .  18
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  20

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
Show full document text