Re: [netmod] Adoption poll for draft-wu-netmod-factory-default-02

Martin Bjorklund <mbj@tail-f.com> Wed, 08 May 2019 11:53 UTC

Return-Path: <mbj@tail-f.com>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 42EBB12006A for <netmod@ietfa.amsl.com>; Wed, 8 May 2019 04:53:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 cIu_EXXrPWgY for <netmod@ietfa.amsl.com>; Wed, 8 May 2019 04:53:27 -0700 (PDT)
Received: from mail.tail-f.com (mail.tail-f.com [46.21.102.45]) by ietfa.amsl.com (Postfix) with ESMTP id 7672C12003F for <netmod@ietf.org>; Wed, 8 May 2019 04:53:27 -0700 (PDT)
Received: from localhost (unknown [173.38.220.61]) by mail.tail-f.com (Postfix) with ESMTPSA id A529F1AE049C; Wed, 8 May 2019 13:53:24 +0200 (CEST)
Date: Wed, 08 May 2019 13:53:27 +0200 (CEST)
Message-Id: <20190508.135327.825252846107256677.mbj@tail-f.com>
To: ietfc@btconnect.com
Cc: jclarke@cisco.com, bill.wu@huawei.com, netmod@ietf.org
From: Martin Bjorklund <mbj@tail-f.com>
In-Reply-To: <065d01d50591$173d7c80$4001a8c0@gateway.2wire.net>
References: <B8F9A780D330094D99AF023C5877DABAA4909DE4@nkgeml513-mbx.china.huawei.com> <EB363D33-307A-48E7-B886-08395356BA86@cisco.com> <065d01d50591$173d7c80$4001a8c0@gateway.2wire.net>
X-Mailer: Mew version 6.7 on Emacs 25.2 / Mule 6.0 (HANACHIRUSATO)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=utf-8
Content-Transfer-Encoding: base64
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/WFczApovhyM-El38WiwES3vG3Mg>
Subject: Re: [netmod] Adoption poll for draft-wu-netmod-factory-default-02
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: NETMOD WG list <netmod.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netmod>, <mailto:netmod-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netmod/>
List-Post: <mailto:netmod@ietf.org>
List-Help: <mailto:netmod-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netmod>, <mailto:netmod-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 May 2019 11:53:30 -0000

tom petch <ietfc@btconnect.com>; wrote:
> ----- Original Message -----
> From: "Joe Clarke (jclarke)" <jclarke@cisco.com>;
> Sent: Monday, May 06, 2019 4:11 PM
> >
> > On May 6, 2019, at 08:06, Qin Wu
> <bill.wu@huawei.com<mailto:bill.wu@huawei.com>> wrote:
> >
> > Hi, Chairs:
> > Sorry for late follow up, thanks Jurgen, Andy,Joe, Joel and all others
> for good comments, here is the update based on discussion and suggestion
> on the mailing list
> > The diff is:
> > https://www.ietf.org/rfcdiff?url2=draft-wu-netmod-factory-default-03
> >
> > Hey, Qin.  I read through the changes, and I have a couple of
> additional comments.
> >
> > First, the term “YANG server” sounds odd to me.  I know what you mean,
> but I haven’t seen this defined before.  Maybe just saying a device or
> host is sufficient?
> 
> Joe
> 
> If you look at the various RFC - YANG, Netconf, NMDA - they all define
> the terms 'client' and 'server'; in the context, 'YANG server' seems
> appropriate.

I agree w/ Joe.  I had the same comment when I read
draft-ietf-netmod-yang-instance-file-format; it uses the term "YANG
server".

I think these documents should import and use the term "server" from
RFC 8342 where it is defined as:

   o  server: An entity that provides access to YANG-defined data to a
      client, over some network management protocol.

Perhaps we should have a term "YANG-based server" or something as an
alias to "server" as defined above.  In some documents the short word
"server" may sound too generic.  But "YANG server" doesn't sound right
to me.


/martin




> 
> Tom Petch
> 
> 
> 
> 
> 
> >
> > When you talk about the datastore to be reset, you list <running>,
> <startup>, and <candidate>.  You state that each will receive the
> contents of <factory-default>.  The <candidate> DS wouldn’t need that.
> I think it would just be zeroed out.
> >
> > I think the RPC should reset any and all non-derived read-write
> datastores and not imply that a specific DS’s contents (i.e., the
> factory-default DS) is copied to them.  This way, other DSes would just
> be handled by this RPC based on implementation.  The <factory-default>
> can exist as the factory default contents for <startup>.
> >
> > Joe
> >
> > We believe it is ready for second adoption poll. Thanks!
> >
> > -Qin (on behalf of authors)
> > 发件人: netmod [mailto:netmod-bounces@ietf.org] 代表 Kent Watsen
> > 发送时间: 2019年4月9日 2:36
> > 收件人: netmod@ietf.org<mailto:netmod@ietf.org>
> > 主题: Re: [netmod] Adoption poll for draft-wu-netmod-factory-default-02
> >
> > This message concludes the adoption poll for
> draft-wu-netmod-factory-default-02   The working group consensus
> supports working on the problem, but fundamental concerns were raised
> regarding the solution, specifically around reseting datastores versus
> resetting devices.  The chairs feel that these issues should be
> addressed before proceeding with the adoption.
> >
> > Authors, please update and resubmit the draft addressing the comments
> received during the adoption poll.  Another adoption poll will be issued
> when ready.
> > Thank you,
> > Kent (and Lou and Joel)
> >
> >
> >
> > On Mar 25, 2019, at 4:34 PM, Kent Watsen
> <kent+ietf@watsen.net<mailto:kent+ietf@watsen.net>> wrote:
> >
> > This email begins a 2-week adoption poll for:
> >
> >
> >     https://tools.ietf.org/html/draft-wu-netmod-factory-default-02
> >
> >
> > Please voice your support or objections before April
> 8.<x-apple-data-detectors://1>
> >
> >
> > Kent (and Lou)
> > _______________________________________________
> > netmod mailing list
> > netmod@ietf.org<mailto:netmod@ietf.org>
> > https://www.ietf.org/mailman/listinfo/netmod
> >
> > _______________________________________________
> > netmod mailing list
> > netmod@ietf.org<mailto:netmod@ietf.org>
> > https://www.ietf.org/mailman/listinfo/netmod
> >
> >
> 
> 
> ------------------------------------------------------------------------
> --------
> 
> 
> > _______________________________________________
> > netmod mailing list
> > netmod@ietf.org
> > https://www.ietf.org/mailman/listinfo/netmod
> >
> 
> _______________________________________________
> netmod mailing list
> netmod@ietf.org
> https://www.ietf.org/mailman/listinfo/netmod