Re: [netconf] RFC6241/RFC7952 model-level interop?

Martin Bjorklund <mbj@tail-f.com> Sat, 02 March 2019 13:57 UTC

Return-Path: <mbj@tail-f.com>
X-Original-To: netconf@ietfa.amsl.com
Delivered-To: netconf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D3121129441 for <netconf@ietfa.amsl.com>; Sat, 2 Mar 2019 05:57:12 -0800 (PST)
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 maksd9JcUyi9 for <netconf@ietfa.amsl.com>; Sat, 2 Mar 2019 05:57:10 -0800 (PST)
Received: from mail.tail-f.com (mail.tail-f.com [46.21.102.45]) by ietfa.amsl.com (Postfix) with ESMTP id 2E8C7128CF3 for <netconf@ietf.org>; Sat, 2 Mar 2019 05:57:10 -0800 (PST)
Received: from localhost (h-4-215.A165.priv.bahnhof.se [158.174.4.215]) by mail.tail-f.com (Postfix) with ESMTPSA id C39941AE0493; Sat, 2 Mar 2019 14:57:07 +0100 (CET)
Date: Sat, 02 Mar 2019 14:57:07 +0100
Message-Id: <20190302.145707.1083539826475521165.mbj@tail-f.com>
To: kent@watsen.net
Cc: nite@hq.sk, netconf@ietf.org
From: Martin Bjorklund <mbj@tail-f.com>
In-Reply-To: <01000169371e0725-87668eaf-d19c-4fb0-9e60-f5c3c209776e-000000@email.amazonses.com>
References: <dc890e1b-e456-96f6-3ac2-be3c9395df18@hq.sk> <01000169371e0725-87668eaf-d19c-4fb0-9e60-f5c3c209776e-000000@email.amazonses.com>
X-Mailer: Mew version 6.7 on Emacs 25.2 / Mule 6.0 (HANACHIRUSATO)
Mime-Version: 1.0
Content-Type: Text/Plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/D5IPCO7BF5xz275kn2o-Bd_Tomg>
Subject: Re: [netconf] RFC6241/RFC7952 model-level interop?
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: NETCONF WG list <netconf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netconf>, <mailto:netconf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netconf/>
List-Post: <mailto:netconf@ietf.org>
List-Help: <mailto:netconf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netconf>, <mailto:netconf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 02 Mar 2019 13:57:13 -0000

Kent Watsen <kent@watsen.net> wrote:
> Hi Robert,
> 
> There is currently no plan to do this, nor is there an rfc6241bis in sight,
> though one may be prompted by the YANG-next discussion happening
> in NETMOD.
> 
> Options (open to comments):
> 
> a) file an Errata

An RFC errata is not appropriate for enhancing an existing module with
new definitions.

> b) file a feature request (start a NETCONF-next issue tracker?) 

It is probably a good idea to have such a tracker.

> c) submit an I-D that *updates* just this aspect of RFC 6241
> d) submit an I-D for rfc6241bis  (we're probably not ready for this yet)
> e) any other choices?


/martin


> 
> Kent
> 
> 
> > On Feb 28, 2019, at 11:04 AM, Robert Varga <nite@hq.sk> wrote:
> > 
> > Hello,
> > 
> > as an implementer of both RFC6241 and RFC7952, I would find it very
> > useful if there were an ietf-netconf.yang which includes the annotation
> > definition of edit-config's operation attribute (Section 7.2).
> > 
> > Are there any plans for RFC6241bis or similar, bringing only an update
> > to ietf-netconf.yang?
> > 
> > Thanks,
> > Robert
> > 
> > _______________________________________________
> > netconf mailing list
> > netconf@ietf.org
> > https://www.ietf.org/mailman/listinfo/netconf
> 
> _______________________________________________
> netconf mailing list
> netconf@ietf.org
> https://www.ietf.org/mailman/listinfo/netconf
>