[Ntp] RFC 9249 on A YANG Data Model for NTP

rfc-editor@rfc-editor.org Wed, 06 July 2022 02:02 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 50844C15C6B8; Tue, 5 Jul 2022 19:02:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.657
X-Spam-Level:
X-Spam-Status: No, score=-6.657 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, 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=ham 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 9TdaJTx4VDSq; Tue, 5 Jul 2022 19:02:00 -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 97E4DC15C6BA; Tue, 5 Jul 2022 19:02:00 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 89A64AEA0; Tue, 5 Jul 2022 19:02:00 -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: <20220706020200.89A64AEA0@rfcpa.amsl.com>
Date: Tue, 05 Jul 2022 19:02:00 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/LxSTFJEj0Mrncb2yz45qs4VhEa4>
Subject: [Ntp] RFC 9249 on A YANG Data Model for NTP
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: Wed, 06 Jul 2022 02:02:04 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 9249

        Title:      A YANG Data Model for NTP 
        Author:     N. Wu,
                    D. Dhody, Ed.,
                    A. Sinha, Ed.,
                    A. Kumar S N,
                    Y. Zhao
        Status:     Standards Track
        Stream:     IETF
        Date:       July 2022
        Mailbox:    eric.wu@huawei.com,
                    dhruv.ietf@gmail.com,
                    ankit.ietf@gmail.com,
                    anil.ietf@gmail.com,
                    yi.z.zhao@ericsson.com
        Pages:      56
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-ntp-yang-data-model-17.txt

        URL:        https://www.rfc-editor.org/info/rfc9249

        DOI:        10.17487/RFC9249

This document defines a YANG data model that can be used to configure
and manage Network Time Protocol (NTP) version 4.  It can also be
used to configure and manage version 3.  The data model includes
configuration data and state data.

This document is a product of the Network Time Protocols Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  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