IETF Logo Mail Archive

[ntpwg] Solicit comments for draft-wu-ntp-ntp-cfg-00

"Wunan (Eric)" <eric.wu@huawei.com> Tue, 21 July 2015 09:42 UTC

Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B8F0C1B2C97 for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Tue, 21 Jul 2015 02:42:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.909
X-Spam-Level:
X-Spam-Status: No, score=-6.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 TL-RKRX5wWPS for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Tue, 21 Jul 2015 02:42:03 -0700 (PDT)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by ietfa.amsl.com (Postfix) with ESMTP id 1EF881B2C96 for <ntp-archives-ahFae6za@lists.ietf.org>; Tue, 21 Jul 2015 02:42:03 -0700 (PDT)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by lists.ntp.org (Postfix) with ESMTP id 1D7E986DBDF for <ntp-archives-ahFae6za@lists.ietf.org>; Tue, 21 Jul 2015 09:42:03 +0000 (UTC)
X-Original-To: ntpwg@lists.ntp.org
Delivered-To: ntpwg@lists.ntp.org
Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id E08F886D9AC for <ntpwg@lists.ntp.org>; Tue, 21 Jul 2015 09:14:33 +0000 (UTC)
Received: from [58.251.152.64] (helo=szxga01-in.huawei.com) by mail1.ntp.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.77 (FreeBSD)) (envelope-from <eric.wu@huawei.com>) id 1ZHTd4-0000kt-6w for ntpwg@lists.ntp.org; Tue, 21 Jul 2015 09:14:33 +0000
Received: from 172.24.1.47 (EHLO SZXEMA413-HUB.china.huawei.com) ([172.24.1.47]) by szxrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id CRO29834; Tue, 21 Jul 2015 17:14:01 +0800 (CST)
Received: from SZXEMA508-MBX.china.huawei.com ([169.254.7.70]) by SZXEMA413-HUB.china.huawei.com ([10.82.72.72]) with mapi id 14.03.0158.001; Tue, 21 Jul 2015 17:13:54 +0800
From: "Wunan (Eric)" <eric.wu@huawei.com>
To: "ntpwg@lists.ntp.org" <ntpwg@lists.ntp.org>
Thread-Topic: Solicit comments for draft-wu-ntp-ntp-cfg-00
Thread-Index: AdDDlCK/cOxtnDmRStm+DecVDL66pA==
Date: Tue, 21 Jul 2015 09:13:54 +0000
Message-ID: <0F26584357FD124DB93F1535E4B0A6505FC141B2@szxema508-mbx.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.46.92.36]
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-SA-Exim-Connect-IP: 58.251.152.64
X-SA-Exim-Rcpt-To: ntpwg@lists.ntp.org
X-SA-Exim-Mail-From: eric.wu@huawei.com
X-SA-Exim-Version: 4.2
X-SA-Exim-Scanned: Yes (on mail1.ntp.org)
Subject: [ntpwg] Solicit comments for draft-wu-ntp-ntp-cfg-00
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.20
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: <http://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>
Content-Type: multipart/mixed; boundary="===============0823389462450682096=="
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Sender: ntpwg <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>

Hi Guys,



I noticed there is one draft related to NTP presented in RTGWG at Prague IETF93.

https://datatracker.ietf.org/doc/draft-rtgyangdt-rtgwg-device-model/



It seems the co-authors of this draft wishing to augment and define NTP YANG model in their next version.

Frankly speaking, if NTP YANG is going to be defined, I think it will be more reasonable to define it in NTPWG, since all NTP experts are here, what is more, NTP MIB is also define here.

To do that, I abosutely need the help from this working group.

Please help us if you guys think this makes sense.



Thank you.



Regards

Eric



________________________________

 [ntpwg] Fw: New Version Notification for draft-wu-ntp-ntp-cfg-00.txt

________________________________

  *   From: "Wunan (Eric)" <eric.wu at huawei.com<mailto:eric.wu@DOMAIN.HIDDEN>>
  *   To: "ntpwg at lists.ntp.org<mailto:ntpwg@DOMAIN.HIDDEN>" <ntpwg at lists.ntp.org<mailto:ntpwg@DOMAIN.HIDDEN>>, "odonoghue at isoc.org<mailto:odonoghue@DOMAIN.HIDDEN>" <odonoghue at isoc.org<mailto:odonoghue@DOMAIN.HIDDEN>>
  *   Cc: "Anil Kumar S N \(VRP Network BL\)" <anil.sn at huawei.com<mailto:anil.sn@DOMAIN.HIDDEN>>
  *   Date: Thu, 29 Jan 2015 07:49:57 +0000

________________________________

Hi folks,

We have submitted a draft on YANG data model for NTP.
Through this draft we hope the NTP YANG discussion may be introduced in NTPWG since we believe it is a good time to start to do it now.
Since this draft is the only individual one in NTPWG, I may want to ask the chair whether it is the proper place to do it, after all YANG data model is not in current charter.
Wish this mail can reach the chair:)

And we would like to know if there are people interested in this work, IMHO, maybe one design team can be used to promote NTP's YANG data model.
Anyway, any discussion and comments are welcomed.

Regards
Eric & Anil



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

v2.23.0 | Report a Bug | By Email