IETF Logo Mail Archive

Re: [NGO] external module properties

"Randy Presuhn" <randy_presuhn@mindspring.com> Tue, 29 April 2008 20:08 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 4F3503A6991; Tue, 29 Apr 2008 13:08:12 -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 F1B723A6991 for <ngo@core3.amsl.com>; Tue, 29 Apr 2008 13:08:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.274
X-Spam-Level:
X-Spam-Status: No, score=-2.274 tagged_above=-999 required=5 tests=[AWL=0.325, BAYES_00=-2.599]
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 s7Kpf27bTWMd for <ngo@core3.amsl.com>; Tue, 29 Apr 2008 13:08:08 -0700 (PDT)
Received: from elasmtp-spurfowl.atl.sa.earthlink.net (elasmtp-spurfowl.atl.sa.earthlink.net [209.86.89.66]) by core3.amsl.com (Postfix) with ESMTP id 319593A68F8 for <ngo@ietf.org>; Tue, 29 Apr 2008 13:08:08 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=PNzOy7Qs/wVQ5tI7DScl6nVrfyqE8EvFP+2jxA008tszICXSfEgvmhRQP3DY9+Lb; h=Received:Message-ID:From:To:References:Subject:Date:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:X-MSMail-Priority:X-Mailer:X-MimeOLE:X-ELNK-Trace:X-Originating-IP;
Received: from [68.164.88.126] (helo=oemcomputer) by elasmtp-spurfowl.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <randy_presuhn@mindspring.com>) id 1Jqw7X-00056e-0M for ngo@ietf.org; Tue, 29 Apr 2008 16:08:11 -0400
Message-ID: <00b501c8aa2c$67959b80$6801a8c0@oemcomputer>
From: Randy Presuhn <randy_presuhn@mindspring.com>
To: NETCONF goes on <ngo@ietf.org>
References: <481742EF.5030607@andybierman.com><200804291611.m3TGBTHr088389@idle.juniper.net><20080429.191023.153396365.mbj@tail-f.com><48176253.1070102@andybierman.com> <1209495880.15947.5.camel@missotis><4817740D.5080803@andybierman.com> <1209499369.15947.22.camel@missotis>
Date: Tue, 29 Apr 2008 13:08:26 -0600
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1478
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478
X-ELNK-Trace: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d8885d2a9c731cc8911706a81373ed22d326b98bfcbd955c13d8350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 68.164.88.126
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="utf-8"
Content-Transfer-Encoding: base64
Sender: ngo-bounces@ietf.org
Errors-To: ngo-bounces@ietf.org

Hi -

> From: "Ladislav Lhotka" <lhotka@cesnet.cz>
> To: "NETCONF goes on" <ngo@ietf.org>
> Sent: Tuesday, April 29, 2008 2:02 PM
> Subject: Re: [NGO] external module properties
>
> Andy Bierman píše v Út 29. 04. 2008 v 12:16 -0700:
>
> > Excellent point.
> > I am envisioning a system which includes a mandatory standard
> > 'schema-discovery' mechanism.  The <hello> exchange is a bad
> > place for all this versioned module to namespace mapping info
> > (even though that's exactly what I have implemented now ;-)
>
> Why is it so bad? The big advantage I see is that it works with the
> existing NETCONF framework.
...

Anything that is limited to the <hello> exchange won't work well with
hot-swappable components.  Plugging a line card into a running chassis should
not require tearing down and re-establishing any connections to management
systems.  Or is netconf not intended for these systems?

Randy


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

v2.23.0 | Report a Bug | By Email