IETF Logo Mail Archive

Re: [Netconf] nmda-restconf operations (was: netconf-binary-encoding comments)

Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de> Mon, 09 July 2018 18:13 UTC

Return-Path: <j.schoenwaelder@jacobs-university.de>
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 67208130E65; Mon, 9 Jul 2018 11:13:42 -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] 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 Zzp8AlY9vEJA; Mon, 9 Jul 2018 11:13:40 -0700 (PDT)
Received: from anna.localdomain (anna.eecs.jacobs-university.de [IPv6:2001:638:709:5::7]) by ietfa.amsl.com (Postfix) with ESMTP id B00A612F1AC; Mon, 9 Jul 2018 11:13:40 -0700 (PDT)
Received: by anna.localdomain (Postfix, from userid 501) id 8F51522FD577; Mon, 9 Jul 2018 20:13:38 +0200 (CEST)
Date: Mon, 09 Jul 2018 20:13:38 +0200
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: Kent Watsen <kwatsen@juniper.net>
Cc: Qin Wu <bill.wu@huawei.com>, Andy Bierman <andy@yumaworks.com>, "draft-ietf-netconf-nmda-restconf@ietf.org" <draft-ietf-netconf-nmda-restconf@ietf.org>, "netconf@ietf.org" <netconf@ietf.org>, Robert Wilton <rwilton=40cisco.com@dmarc.ietf.org>
Message-ID: <20180709181338.anv7tfsylvhypwdz@anna.jacobs.jacobs-university.de>
Reply-To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
Mail-Followup-To: Kent Watsen <kwatsen@juniper.net>, Qin Wu <bill.wu@huawei.com>, Andy Bierman <andy@yumaworks.com>, "draft-ietf-netconf-nmda-restconf@ietf.org" <draft-ietf-netconf-nmda-restconf@ietf.org>, "netconf@ietf.org" <netconf@ietf.org>, Robert Wilton <rwilton=40cisco.com@dmarc.ietf.org>
References: <82A8420F-445C-42BD-9A47-DCF62A9864BC@juniper.net> <20180709173041.xkihqyccjcucjslj@anna.jacobs.jacobs-university.de> <13FABA4A-C367-4E27-88FF-3EA48638249F@juniper.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <13FABA4A-C367-4E27-88FF-3EA48638249F@juniper.net>
User-Agent: NeoMutt/20180622
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/Eey1Ga7EkDwz6mRj5FewaosimF0>
Subject: Re: [Netconf] nmda-restconf operations (was: netconf-binary-encoding comments)
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: Network Configuration WG mailing 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: Mon, 09 Jul 2018 18:13:43 -0000

On Mon, Jul 09, 2018 at 05:48:57PM +0000, Kent Watsen wrote:
> 
> 
> >> This isn't what I meant.  To be more specific, I'm wondering if the nmda-restconf
> >> draft would benefit from having a sentence like:
> >> 
> >>    A RESTCONF server supporting NMDA datastores MAY implement the
> >>    "ietf-netconf" [RFC6241] and "ietf-netconf-nmda" [I-D. ietf-netconf-nmda-
> >>    netconf] modules to enable the NETCONF operations defined in those
> >>    drafts to appear {+restconf}/operations resource.
> >> 
> >> Note: I put "MAY" as RESTCONF may someday have a more native way to do this.
> >>
> >
> > Well, "ietf-netconf" does not really support NMDA well and this is why
> > we have "ietf-netconf-nmda". Does not make much sense to point to
> > "ietf-netconf" in an NMDA document.
> 
> But we'd still need lock, unlock, commit, commit-confirmed, etc., right?

Yep.
 
> Maybe it's a moot point, since ietf-netconf-nmda requires that ietf-netconf
> is implemented too, but I thought being explicit would be helpful here.

As long as readers get the idea that implementing lets say edit-config
is perhaps not the best idea...
 
> So, adding something like this to nmda-restconf would be good?

It likely does not hurt to be clear that this option of using NETCONF
operations in RESTCONF exists.

/js

-- 
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: +49 421 200 3587         Campus Ring 1 | 28759 Bremen | Germany
Fax:   +49 421 200 3103         <https://www.jacobs-university.de/>

v2.23.0 | Report a Bug | By Email