Re: [Netconf] Netconf Light or Netconf for constrained devices

Andy Bierman <andy@netconfcentral.org> Sat, 31 March 2012 07:08 UTC

Return-Path: <andy@netconfcentral.org>
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 5977021E802B for <netconf@ietfa.amsl.com>; Sat, 31 Mar 2012 00:08:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sckjBQbfiOlx for <netconf@ietfa.amsl.com>; Sat, 31 Mar 2012 00:08:10 -0700 (PDT)
Received: from p3plsmtpa06-09.prod.phx3.secureserver.net (p3plsmtpa06-09.prod.phx3.secureserver.net [173.201.192.110]) by ietfa.amsl.com (Postfix) with SMTP id D136621E8020 for <netconf@ietf.org>; Sat, 31 Mar 2012 00:08:10 -0700 (PDT)
Received: (qmail 17573 invoked from network); 31 Mar 2012 07:08:09 -0000
Received: from unknown (93.158.42.164) by p3plsmtpa06-09.prod.phx3.secureserver.net (173.201.192.110) with ESMTP; 31 Mar 2012 07:08:09 -0000
Message-ID: <4F76AD57.5000604@netconfcentral.org>
Date: Sat, 31 Mar 2012 00:08:07 -0700
From: Andy Bierman <andy@netconfcentral.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:11.0) Gecko/20120310 Thunderbird/11.0
MIME-Version: 1.0
To: netconf@ietf.org
References: <80A0822C5E9A4440A5117C2F4CD36A640398E384@DEMUEXC006.nsn-intra.net> <4F757326.8090002@bwijnen.net> <4F75E862.8000509@netconfcentral.org> <20120331051051.GA70150@elstar.local>
In-Reply-To: <20120331051051.GA70150@elstar.local>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: Re: [Netconf] Netconf Light or Netconf for constrained devices
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 31 Mar 2012 07:08:11 -0000

On 03/30/2012 10:10 PM, Juergen Schoenwaelder wrote:
> On Fri, Mar 30, 2012 at 10:07:46AM -0700, Andy Bierman wrote:
>
>> But assuming one insisted on using a subset of NETCONF for some reason,
>> one can write an applicability statement that documented how to
>> advertise the ietf-netconf module plus some deviations to
>> identify what is missing from the implementation.  (The AS is only needed
>> because we are assuming implementers are too dumb to understand RFC 6020
>> I suppose.)
>
> This is kind of funny. The I-D actually says an incomplete NETCONF
> implementation calls itself 'NETCONF Light' (and not 'NETCONF'2) while
> you seem to prefer that an incomplete NETCONF implementation calls
> itself 'NETCONF' and then posts some deviations.
>

You probably need to re-read section 5.6.4 of RFC 6020.
Advertising <uri> + deviations is the way YANG is designed.

>
> /js
>


Andy