[ntpwg] RFC 5907 on Definitions of Managed Objects for Network Time Protocol Version 4 (NTPv4)

rfc-editor@rfc-editor.org Mon, 21 June 2010 22:58 UTC

Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@core3.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D5D3E28C162 for <ietfarch-ntp-archives-ahFae6za@core3.amsl.com>; Mon, 21 Jun 2010 15:58:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.481
X-Spam-Level:
X-Spam-Status: No, score=-1.481 tagged_above=-999 required=5 tests=[AWL=0.518, BAYES_00=-2.599, J_CHICKENPOX_93=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bMcCyuXYoUQR for <ietfarch-ntp-archives-ahFae6za@core3.amsl.com>; Mon, 21 Jun 2010 15:58:03 -0700 (PDT)
Received: from lists.ntp.org (lists.ntp.org [IPv6:2001:4f8:fff7:1::7]) by core3.amsl.com (Postfix) with ESMTP id E651128C161 for <ntp-archives-ahFae6za@lists.ietf.org>; Mon, 21 Jun 2010 15:58:02 -0700 (PDT)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by lists.ntp.org (Postfix) with ESMTP id CFD7186DBA8 for <ntp-archives-ahFae6za@lists.ietf.org>; Mon, 21 Jun 2010 22:58:09 +0000 (UTC)
X-Original-To: ntpwg@lists.ntp.org
Delivered-To: ntpwg@lists.ntp.org
Received: from mail2.ntp.org (mail2.ntp.org [IPv6:2001:4f8:fff7:1::6]) by lists.ntp.org (Postfix) with ESMTP id CE27286D34D for <ntpwg@lists.ntp.org>; Mon, 21 Jun 2010 22:58:07 +0000 (UTC)
Received: from rfc-editor.org ([2001:1890:1112:1::2f]) by mail2.ntp.org with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <wwwrun@rfc-editor.org>) id 1OQpwC-000FFY-Vg for ntpwg@lists.ntp.org; Mon, 21 Jun 2010 22:58:07 +0000
Received: by rfc-editor.org (Postfix, from userid 30) id 5064FE06BA; Mon, 21 Jun 2010 15:57:51 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20100621225751.5064FE06BA@rfc-editor.org>
Date: Mon, 21 Jun 2010 15:57:51 -0700
X-SA-Exim-Connect-IP: 2001:1890:1112:1::2f
X-SA-Exim-Rcpt-To: ntpwg@lists.ntp.org
X-SA-Exim-Mail-From: wwwrun@rfc-editor.org
X-SA-Exim-Version: 4.2
X-SA-Exim-Scanned: Yes (on mail2.ntp.org)
Cc: ntpwg@lists.ntp.org, rfc-editor@rfc-editor.org
Subject: [ntpwg] RFC 5907 on Definitions of Managed Objects for Network Time Protocol Version 4 (NTPv4)
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <http://lists.ntp.org/options/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <https://lists.ntp.org/pipermail/ntpwg>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <http://lists.ntp.org/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org

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

        
        RFC 5907

        Title:      Definitions of Managed Objects for 
                    Network Time Protocol Version 4 (NTPv4) 
        Author:     H. Gerstung, C. Elliott,
                    B. Haberman, Ed.
        Status:     Standards Track
        Stream:     IETF
        Date:       June 2010
        Mailbox:    heiko.gerstung@meinberg.de, 
                    chelliot@pobox.com, 
                    brian@innovationslab.net
        Pages:      26
        Characters: 46950
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-ntp-ntpv4-mib-07.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5907.txt

The Network Time Protocol (NTP) is used in networks of all types and
sizes for time synchronization of servers, workstations, and other
networked equipment.  As time synchronization is more and more a
mission-critical service, standardized means for monitoring and
management of this subsystem of a networked host are required to
allow operators of such a service to set up a monitoring system that
is platform- and vendor-independent.  This document provides a
standardized collection of data objects for monitoring the NTP entity
of such a network participant and it is part of the NTP version 4
standardization effort.  [STANDARDS TRACK]

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

This is now a Proposed Standard Protocol.

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 Internet
Official Protocol Standards (STD 1) 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
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

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


_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
http://lists.ntp.org/listinfo/ntpwg