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

Andy Bierman <andy@netconfcentral.org> Sat, 31 March 2012 06:48 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 3AEA121F85DB for <netconf@ietfa.amsl.com>; Fri, 30 Mar 2012 23:48:38 -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=[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 a0iuu2mLUU3g for <netconf@ietfa.amsl.com>; Fri, 30 Mar 2012 23:48:37 -0700 (PDT)
Received: from p3plsmtpa08-02.prod.phx3.secureserver.net (p3plsmtpa08-02.prod.phx3.secureserver.net [173.201.193.103]) by ietfa.amsl.com (Postfix) with SMTP id 9F63621F85D7 for <netconf@ietf.org>; Fri, 30 Mar 2012 23:48:37 -0700 (PDT)
Received: (qmail 25286 invoked from network); 31 Mar 2012 06:48:31 -0000
Received: from unknown (93.158.42.164) by p3plsmtpa08-02.prod.phx3.secureserver.net (173.201.193.103) with ESMTP; 31 Mar 2012 06:48:31 -0000
Message-ID: <4F76A8BE.6050708@netconfcentral.org>
Date: Fri, 30 Mar 2012 23:48:30 -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: "Bert Wijnen (IETF)" <bertietf@bwijnen.net>, 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 06:48:38 -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.
>
> (While server implementors might be too dumb, it might also be that
> client implementors are too dumb to handle deviations well.)
>

There is no NETCONF Light -- and I hope there never will be one.
That is just a meaningless marketing term.  NETCONF for Constrained
Devices might be OK if it provided some meaningful set of CM functionality.

Your draft assumes that customers are too dumb to know the difference.

> /js
>

Andy