Re: [NGO] external module properties

Martin Bjorklund <mbj@tail-f.com> Tue, 29 April 2008 20:00 UTC

Return-Path: <ngo-bounces@ietf.org>
X-Original-To: ngo-archive@optimus.ietf.org
Delivered-To: ietfarch-ngo-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E844228C2ED; Tue, 29 Apr 2008 13:00:31 -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 B8C5A28C2ED for <ngo@core3.amsl.com>; Tue, 29 Apr 2008 13:00:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.495
X-Spam-Level:
X-Spam-Status: No, score=-0.495 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1]
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 r-NVDmtLGoN9 for <ngo@core3.amsl.com>; Tue, 29 Apr 2008 13:00:30 -0700 (PDT)
Received: from mail.tail-f.com (unknown [213.180.94.162]) by core3.amsl.com (Postfix) with ESMTP id EAC7428C272 for <ngo@ietf.org>; Tue, 29 Apr 2008 13:00:29 -0700 (PDT)
Received: from localhost (c213-100-166-13.swipnet.se [213.100.166.13]) by mail.tail-f.com (Postfix) with ESMTP id A54921B80D2; Tue, 29 Apr 2008 22:00:32 +0200 (CEST)
Date: Tue, 29 Apr 2008 22:00:31 +0200
Message-Id: <20080429.220031.261079612.mbj@tail-f.com>
To: ietfdbh@comcast.net
From: Martin Bjorklund <mbj@tail-f.com>
In-Reply-To: <00d001c8aa2b$8b10d170$0600a8c0@china.huawei.com>
References: <00ac01c8aa19$f56ffa80$0600a8c0@china.huawei.com> <48175E87.9010604@andybierman.com> <00d001c8aa2b$8b10d170$0600a8c0@china.huawei.com>
X-Mailer: Mew version 5.2.52 on Emacs 22.1 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Cc: ngo@ietf.org
Subject: Re: [NGO] external module properties
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,

"David Harrington" <ietfdbh@comcast.net> wrote:
> Hi,
> 
> My concern also includes multiple instances of a vlan module running
> within a single (master/subagent) environment. This might be found in
> a router chassis that supports new and legacy blades, or an x86 PC
> server that can support disk drives from different vendors. 

I agree that this is a difficult problem, and I'd be happy to discuss
this more.  Is this something we want to work on?  But I think it is
orthogonal to the issue about how a module is identified.  BTW, this
problem touches other ongoing work, like schema discovery.


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