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

Danny Mayer <mayer@ntp.org> Fri, 24 July 2015 03:29 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 1E28D1ABC74 for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Thu, 23 Jul 2015 20:29:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.91
X-Spam-Level:
X-Spam-Status: No, score=-6.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 78IT5p-SWqjU for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Thu, 23 Jul 2015 20:29:18 -0700 (PDT)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by ietfa.amsl.com (Postfix) with ESMTP id 21D231A8A10 for <ntp-archives-ahFae6za@lists.ietf.org>; Thu, 23 Jul 2015 20:29:18 -0700 (PDT)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by lists.ntp.org (Postfix) with ESMTP id 0CFBA86DB6F for <ntp-archives-ahFae6za@lists.ietf.org>; Fri, 24 Jul 2015 03:29:18 +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 D5E1286D55F for <ntpwg@lists.ntp.org>; Fri, 24 Jul 2015 02:38:02 +0000 (UTC)
Received: from pool-71-174-223-7.bstnma.east.verizon.net ([71.174.223.7] helo=[10.10.10.102]) by mail1.ntp.org with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.77 (FreeBSD)) (envelope-from <mayer@ntp.org>) id 1ZISs2-000PZp-LQ; Fri, 24 Jul 2015 02:38:00 +0000
Message-ID: <55B1A585.3000709@ntp.org>
Date: Thu, 23 Jul 2015 22:40:05 -0400
From: Danny Mayer <mayer@ntp.org>
Organization: NTP
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: "Wunan (Eric)" <eric.wu@huawei.com>, "ntpwg@lists.ntp.org" <ntpwg@lists.ntp.org>
References: <0F26584357FD124DB93F1535E4B0A6505FC141B2@szxema508-mbx.china.huawei.com>, <55AFE233.4000407@pdmconsulting.net> <0F26584357FD124DB93F1535E4B0A6505FC159E8@szxema508-mbx.china.huawei.com>
In-Reply-To: <0F26584357FD124DB93F1535E4B0A6505FC159E8@szxema508-mbx.china.huawei.com>
X-SA-Exim-Connect-IP: 71.174.223.7
X-SA-Exim-Rcpt-To: ntpwg@lists.ntp.org, eric.wu@huawei.com
X-SA-Exim-Mail-From: mayer@ntp.org
X-SA-Exim-Version: 4.2
X-SA-Exim-Scanned: Yes (on mail1.ntp.org)
Subject: Re: [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>
Reply-To: mayer@ntp.org
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
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>

On 7/22/2015 6:38 PM, Wunan (Eric) wrote:
> Hi Danny,
> 
> Thank you for the frankness.
> 
> Yes, ntpq supports mode 6, but does it mean mode 6 is mandatory
feature that must be supported on all ntp release?
> Actually there are lots of ntp release that don't support mode 6,
especially in carriers' networks.

That's their choice. It's available for them to use. In the meantime
milions of servers DO support mode 6 packets while you have 0 servers
that currently handle this proposal. It's easier to set up those servers
to handle mode 6 packets than get them to do something else.

> 
> NTP YANG as a protocol-neutral module, will give people one more
option to deploy and manage ntp feature.
> 

Well no. It's protocol neutral until you actually have to build this and
then you have to have something build into the NTP server to support it
and then it's no longer protocol neutral.

You then have a number of choices.

1) Interface your model with the NTP Server using mode 6 packets and
since it's already built into the reference implementation you get to
support millions of servers with it without making any changes to those
servers. None reference implementations would need to add mode 6 packets
and know what do with the requests that come in;

2) Build a Yang interface into NTP directly in which case you don't use
the NTP protocol at all and use TCP to do this. We have discussed doing
a separate management interface in the Reference implementation and it
would use TCP for this.

I have no idea what your intentions are. Have you also looked at the MIB
RFC for NTP? RFC5907 I think.

Danny


> Regards
> Eric
> ________________________________________
> 
> Frankly I have never understood the point of this draft. It seems to
> have been introduced in a vacuum. ntpq on the reference implementation
> already handles everything needed and uses ntp mode 6 packets. Is there
> something I didn't understand?
> 
> Danny
> 
> On 7/21/2015 5:13 AM, Wunan (Eric) wrote:
>> 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