[Ntp] RFC 9327 on Control Messages Protocol for Use with Network Time Protocol Version 4
rfc-editor@rfc-editor.org Tue, 01 November 2022 21:15 UTC
Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: ntp@ietfa.amsl.com
Delivered-To: ntp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A43BFC14CF0E; Tue, 1 Nov 2022 14:15:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.658
X-Spam-Level:
X-Spam-Status: No, score=-6.658 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UbkltkDp2169; Tue, 1 Nov 2022 14:15:26 -0700 (PDT)
Received: from rfcpa.amsl.com (rfc-editor.org [50.223.129.200]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 75580C14CF17; Tue, 1 Nov 2022 14:15:26 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 5FF6ED8457; Tue, 1 Nov 2022 14:15:26 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, ntp@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20221101211526.5FF6ED8457@rfcpa.amsl.com>
Date: Tue, 01 Nov 2022 14:15:26 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/aUGF5L9gmE0aLrdmNqjy3FPdx5c>
Subject: [Ntp] RFC 9327 on Control Messages Protocol for Use with Network Time Protocol Version 4
X-BeenThere: ntp@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Network Time Protocol <ntp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ntp>, <mailto:ntp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ntp/>
List-Post: <mailto:ntp@ietf.org>
List-Help: <mailto:ntp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ntp>, <mailto:ntp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Nov 2022 21:15:30 -0000
A new Request for Comments is now available in online RFC libraries. RFC 9327 Title: Control Messages Protocol for Use with Network Time Protocol Version 4 Author: B. Haberman, Ed. Status: Historic Stream: IETF Date: November 2022 Mailbox: brian@innovationslab.net Pages: 21 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-ntp-mode-6-cmds-11.txt URL: https://www.rfc-editor.org/info/rfc9327 DOI: 10.17487/RFC9327 This document describes the structure of the control messages that were historically used with the Network Time Protocol (NTP) before the advent of more modern control and management approaches. These control messages have been used to monitor and control the NTP 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 an updated description of the control messages described in RFC 1305 in order to conform with the updated NTP specification documented in RFC 5905. The publication of this document is not meant to encourage the development and deployment of these control messages. This document is only providing a current reference for these control messages given the current status of RFC 1305. This document is a product of the Network Time Protocols Working Group of the IETF. HISTORIC: This memo defines a Historic Document for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC