BCP 223, RFC 8633 on Network Time Protocol Best Current Practices
rfc-editor@rfc-editor.org Fri, 19 July 2019 00:33 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 624BE120B5B; Thu, 18 Jul 2019 17:33:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HyMo_hJqTUzw; Thu, 18 Jul 2019 17:33:17 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 99FC0120B5A; Thu, 18 Jul 2019 17:33:17 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 1B167B80BF5; Thu, 18 Jul 2019 17:33:12 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: BCP 223, RFC 8633 on Network Time Protocol Best Current Practices
X-PHP-Originating-Script: 1005:ams_util_lib.php
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: <20190719003312.1B167B80BF5@rfc-editor.org>
Date: Thu, 18 Jul 2019 17:33:12 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/6iwIbrQC3sfebKiPmNoOMg2mY_E>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Jul 2019 00:33:25 -0000
A new Request for Comments is now available in online RFC libraries. BCP 223 RFC 8633 Title: Network Time Protocol Best Current Practices Author: D. Reilly, H. Stenn, D. Sibold Status: Best Current Practice Stream: IETF Date: July 2019 Mailbox: denis.reilly@orolia.com, stenn@nwtime.org, dieter.sibold@ptb.de Pages: 26 Characters: 60651 See Also: BCP 223 I-D Tag: draft-ietf-ntp-bcp-13.txt URL: https://www.rfc-editor.org/info/rfc8633 DOI: 10.17487/RFC8633 The Network Time Protocol (NTP) is one of the oldest protocols on the Internet and has been widely used since its initial publication. This document is a collection of best practices for the general operation of NTP servers and clients on the Internet. It includes recommendations for the stable, accurate, and secure operation of NTP infrastructure. This document is targeted at NTP version 4 as described in RFC 5905. This document is a product of the Network Time Protocol Working Group of the IETF. BCP: This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. 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