[NGO] NETMOD charter

Andy Bierman <ietf@andybierman.com> Mon, 17 March 2008 00:32 UTC

Return-Path: <ngo-bounces@ietf.org>
X-Original-To: ietfarch-ngo-archive@core3.amsl.com
Delivered-To: ietfarch-ngo-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A19F23A6B1D; Sun, 16 Mar 2008 17:32:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.544
X-Spam-Level:
X-Spam-Status: No, score=-100.544 tagged_above=-999 required=5 tests=[AWL=-0.107, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id boDKspFwbi2W; Sun, 16 Mar 2008 17:32:29 -0700 (PDT)
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CFDE13A69C8; Sun, 16 Mar 2008 17:32:29 -0700 (PDT)
X-Original-To: ngo@core3.amsl.com
Delivered-To: ngo@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 995AF3A68B7 for <ngo@core3.amsl.com>; Sun, 16 Mar 2008 17:32:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id t4WIByQnJlS7 for <ngo@core3.amsl.com>; Sun, 16 Mar 2008 17:32:28 -0700 (PDT)
Received: from smtp119.sbc.mail.sp1.yahoo.com (smtp119.sbc.mail.sp1.yahoo.com [69.147.64.92]) by core3.amsl.com (Postfix) with SMTP id E94343A6869 for <ngo@ietf.org>; Sun, 16 Mar 2008 17:32:27 -0700 (PDT)
Received: (qmail 57086 invoked from network); 17 Mar 2008 00:30:11 -0000
Received: from unknown (HELO ?127.0.0.1?) (andybierman@att.net@67.127.97.59 with plain) by smtp119.sbc.mail.sp1.yahoo.com with SMTP; 17 Mar 2008 00:30:10 -0000
X-YMail-OSG: J_qlVp8VM1mlIat5PEJ1RkmZrkdhAz7hYXbR77xywLVSQzNR
X-Yahoo-Newman-Property: ymail-3
Message-ID: <47DDBB90.1040803@andybierman.com>
Date: Sun, 16 Mar 2008 17:30:08 -0700
From: Andy Bierman <ietf@andybierman.com>
User-Agent: Thunderbird 2.0.0.12 (Windows/20080213)
MIME-Version: 1.0
To: NETCONF Goes On <ngo@ietf.org>
Subject: [NGO] NETMOD charter
X-BeenThere: ngo@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: NETCONF Goes On - discussions on future work and extensions to NETCONF <ngo.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ngo>, <mailto:ngo-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ngo>
List-Post: <mailto:ngo@ietf.org>
List-Help: <mailto:ngo-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ngo>, <mailto:ngo-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ngo-bounces@ietf.org
Errors-To: ngo-bounces@ietf.org

Hi,

I would like to get a NETMOD WG chartered before the next IETF,
not keep having BoFs that may eventually lead to a WG some year.

I strongly support a NETCONF MIB language as the highest priority,
and next step in a workable NETCONF-based CM solution.  However,
there needs to be some agreement and clarity on what the
finished NETCONF-managed system looks like.

Just because CLI development tends to be an organic, ad-hoc,
uncontrolled process, does not mean the IETF standards process should
be the same.  Full support for vendor innovation is important,
but this must coexist with an (anticipated) ever-increasing set
of standard modules.

First the base protocol. Then notifications. Then partial locking, etc.
I really don't see much of a system-oriented development plan here,
if the end goal is supposed to be standards-based *configuration*.


Andy

_______________________________________________
NGO mailing list
NGO@ietf.org
https://www.ietf.org/mailman/listinfo/ngo