Re: [Ntp] WGLC: draft-ietf-ntp-yang-data-model

Dhruv Dhody <dhruv.ietf@gmail.com> Thu, 05 December 2019 14:21 UTC

Return-Path: <dhruv.ietf@gmail.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 CF930120013; Thu, 5 Dec 2019 06:21:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 yy1DilrcV_T1; Thu, 5 Dec 2019 06:21:02 -0800 (PST)
Received: from mail-il1-x12a.google.com (mail-il1-x12a.google.com [IPv6:2607:f8b0:4864:20::12a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CC14C120967; Thu, 5 Dec 2019 06:20:59 -0800 (PST)
Received: by mail-il1-x12a.google.com with SMTP id p8so3078495iln.12; Thu, 05 Dec 2019 06:20:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=vsRd4MFjniQYgLdqiXo3OM1jLMK3pKaa7XHkXU1cTKQ=; b=hRTFWv2kZWyawwYTPwt1mE45UJ/79r26kSqRE9xx0QBdse8cgaDYjhCdVUmmOxSe5P BgDIuJuGs3fLemcRn2T+FalEldeiNews8kbxIU3XPcxTZq+7WwpVwbT04Astbw7LM4Ws ig2+VR60nX+pd0Y8ZUBav/fxgiURLgBrZUIaI5YuidmigV3aMgwh6/33nhsC0DBsODWY gCmeIzU2zOYf6bz6RVSxiQ6hp82eq04it30ib9cHRnLSxFkyj7LnRaMPhcpb7vyRd9cq LGWLAkOPztKlELCqLWAq+8si4an4aPRUc1WPAZlYxHrpTrQJB3HEeHiQ5G/BrjqFowpb xvRA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=vsRd4MFjniQYgLdqiXo3OM1jLMK3pKaa7XHkXU1cTKQ=; b=RJGDwWIM2uhk7N7IQad9TCHf+zqAgalPD3/5rm6LcBluFq2kwwvj8jfsa1P5thI/R4 bQ7GEolGMNitcn3iNflRPAQi2phAD8Lvz5ypUT1avy4F5TmiMjXyR/uUB3dT9/CHo/v7 DYYl+zhNSfnBlF1D+o0Z94SRfjHVl7wkV/Nv7pJQt0DbvxWAaYxqceSzjym8aTd59VGo vGBav5UOgZcOGwdIunt2P6qM0F2cj9Lti3RLL+Bd4ddWVh/ei3BYkuBOwYMzhzA3pzrA 7+K7ruaORF54VWspyc3jKrQnubV24UpeJqBHXDsTKnYtUFhvfqPUHacfWcH2a8QIUh2e UeIw==
X-Gm-Message-State: APjAAAUvGxXJVyWUI/yiOiMC2316BrMFluTyfYGSUSV1XxCT7/1GrAZt 3U2s6CeHoAI6j2AjitAZGsXUYb8CgS0zFRwtKkg=
X-Google-Smtp-Source: APXvYqyNGZgp/1bJq1Qs7cHt3AJo2KX5006ExcCbN6OHqwmADp+2ADJDRC4lRrfC4OGCIlPD6M25WzuWvZBSjZg+hLw=
X-Received: by 2002:a92:7e59:: with SMTP id z86mr9372769ilc.1.1575555658859; Thu, 05 Dec 2019 06:20:58 -0800 (PST)
MIME-Version: 1.0
References: <BE9A0529-7638-41F2-B301-3E38C1EF1323@akamai.com>
In-Reply-To: <BE9A0529-7638-41F2-B301-3E38C1EF1323@akamai.com>
From: Dhruv Dhody <dhruv.ietf@gmail.com>
Date: Thu, 5 Dec 2019 19:50:22 +0530
Message-ID: <CAB75xn5XBJ+aHweaeMBB2D03FFn5gFOpmQS4gJfJjpsGxiodkg@mail.gmail.com>
To: "Salz, Rich" <rsalz@akamai.com>
Cc: "Karen O'Donoghue" <odonoghue@isoc.org>, "ntp@ietf.org" <ntp@ietf.org>, draft-ietf-ntp-yang-data-model@ietf.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/u5f9fLW3u8H4rngy7IDIXFzbqGY>
Subject: Re: [Ntp] WGLC: draft-ietf-ntp-yang-data-model
X-BeenThere: ntp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <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: Thu, 05 Dec 2019 14:21:07 -0000

Hi Rich,

Thanks for reading, well skimming :)

More inline...

On Thu, Dec 5, 2019 at 9:08 AM Salz, Rich <rsalz@akamai.com> wrote:
>
>     A YANG Data Model for NTP
>     https://datatracker.ietf.org/doc/draft-ietf-ntp-yang-data-model/
>
> I read this document.  (To be frank, I skimmed through much of the yang declarations.)  I have concerns with the yang intent of putting everything the IETF does into yang and its configuration. Do we really want to add remote interfaces to manipulate and configure autokey, for example? Because of this, I am opposed to having this as a standards-track document.
>

By remote interface, do you mean "peer-interface"? Note that, it is
read only and not configurable. You would notice multiple leaves in
the tree with "ro" prefix at
https://tools.ietf.org/html/draft-ietf-ntp-yang-data-model-07#section-2,
all of these are "read-only" and not configurable.

Also we do not support auto-key in this YANG model. Our authentication
is limited to basic key management
(https://tools.ietf.org/html/draft-ietf-ntp-yang-data-model-07#section-6).

If you see some "rw" nodes that should not be allowed to be
configured, please let us known?

> Was there much discussion of this document on the WG list?  I didn't see much looking for yang in the archives. Notably, I didn't see the call for adoption -- anyone have a link?
>

Here is the call for adoption -
https://mailarchive.ietf.org/arch/msg/ntp/RC77itwfYzEJl1DLYosbLYUkrp4

Draft did get some some early discussion, not much after WG adoption
though, the state of the Yang Model was updated during WG meetings.

https://mailarchive.ietf.org/arch/msg/ntp/cVLZeydJACdCqgs8EcP7jLvm3OM
https://mailarchive.ietf.org/arch/msg/ntp/qgfukmwiEkpczwKMAZAjHK_tHeQ
https://mailarchive.ietf.org/arch/msg/ntp/q9F3HNGlOtxI4FsuccDZG0BWRN4

Thanks!
Dhruv

>
>
> _______________________________________________
> ntp mailing list
> ntp@ietf.org
> https://www.ietf.org/mailman/listinfo/ntp