Re: [Netconf] Trying a consensus on the way forward with Netconf-Light

Andy Bierman <andy@netconfcentral.org> Tue, 17 April 2012 18:31 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 1315A11E80B8 for <netconf@ietfa.amsl.com>; Tue, 17 Apr 2012 11:31:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.484
X-Spam-Level:
X-Spam-Status: No, score=-2.484 tagged_above=-999 required=5 tests=[AWL=0.115, 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 luWmEPPW1pBe for <netconf@ietfa.amsl.com>; Tue, 17 Apr 2012 11:31:30 -0700 (PDT)
Received: from omr8.networksolutionsemail.com (omr8.networksolutionsemail.com [205.178.146.58]) by ietfa.amsl.com (Postfix) with ESMTP id 018E411E80A0 for <netconf@ietf.org>; Tue, 17 Apr 2012 11:31:29 -0700 (PDT)
Received: from cm-omr6 (mail.networksolutionsemail.com [205.178.146.50]) by omr8.networksolutionsemail.com (8.13.8/8.13.8) with ESMTP id q3HIVTNI019426 for <netconf@ietf.org>; Tue, 17 Apr 2012 14:31:29 -0400
Authentication-Results: cm-omr6 smtp.user=andy@andybierman.com; auth=pass (PLAIN)
X-Authenticated-UID: andy@andybierman.com
Received: from [75.84.164.152] ([75.84.164.152:37735] helo=[192.168.0.9]) by cm-omr6 (envelope-from <andy@netconfcentral.org>) (ecelerity 2.2.2.41 r(31179/31189)) with ESMTPA id 51/DE-22382-007BD8F4; Tue, 17 Apr 2012 14:31:29 -0400
Message-ID: <4F8DB701.6020305@netconfcentral.org>
Date: Tue, 17 Apr 2012 11:31:29 -0700
From: Andy Bierman <andy@netconfcentral.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:11.0) Gecko/20120329 Thunderbird/11.0.1
MIME-Version: 1.0
To: "Ersue, Mehmet (NSN - DE/Munich)" <mehmet.ersue@nsn.com>
References: <80A0822C5E9A4440A5117C2F4CD36A6403A64CAD@DEMUEXC006.nsn-intra.net>
In-Reply-To: <80A0822C5E9A4440A5117C2F4CD36A6403A64CAD@DEMUEXC006.nsn-intra.net>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: netconf@ietf.org
Subject: Re: [Netconf] Trying a consensus on the way forward with Netconf-Light
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: Tue, 17 Apr 2012 18:31:34 -0000

On 04/16/2012 06:29 AM, Ersue, Mehmet (NSN - DE/Munich) wrote:
> Dear NETCONF WG,
>

a) standards-track

b) NETCONF-Light document; but I prefer the name 'NETCONF for Constrained Devices'

c) new capability; since deviations are not widely implemented (except in yuma and confd)
    they do not really solve the problem; incompatible at layer 8 - political layer

d) the original suggested subset in the -00 draft.
      http://tools.ietf.org/html/draft-schoenw-netconf-light-00
    The -00 draft was almost done. The -01 draft was not a step forward.


Andy


> after the discussion on the Netconf-Light, we would like to get the
> sense of the WG. The WG at the end needs a consensus to prepare a
> reasonably well scoped new charter.
>
> Current Netconf-Light specification describes a profile of the NETCONF
> protocol and allows devices to announce that they only support a subset
> of the NETCONF protocol operations.
> However, Netconf-Light differs from the Netconf standard and proposes to
> use a new namespace and a reduced set of configuration features with a
> new capability. The specification also discusses TLS as the potential
> mandatory to implement secure transport protocol. 	
>
> With that, there are a few questions to answer to get a clarity on what
> the WG thinks ( questions b) and c) might be possible to combine,
> however please state your opinion separately):
>
> a) Assuming that we need a Netconf-Light document to define diverse
> details, should the Netconf-Light document be a Standard track document
> or an Experimental?
>
> b) Should the minimal set of configuration features used in
> Netconf-Light be defined in the Netconf-Light document or in an
> applicability statement.
> E.g. the Netconf-Light document would define a "minimal CM feature set".
> An applicability statement can define a few "minimal CM feature sets"
> for different purposes.
>
> c) Should the minimal set of configuration features be defined with a
> new capability or based on deviations?
>
> d) Which minimal CM feature set is appropriate for a Netconf-Light for
> constrained devices?
>
>
> Please send your response to the questions above to the Netconf ML, by
> April 26, 2011 EDT EOB.
>
> PS: If anybody wants to start additional discussion on a particular
> topic, please do so with a "new subject".
>
> Thank you.
>
> Mehmet&  Bert
>
> _______________________________________________
> Netconf mailing list
> Netconf@ietf.org
> https://www.ietf.org/mailman/listinfo/netconf
>
>