Re: [NGO] external module properties

Phil Shafer <phil@juniper.net> Tue, 29 April 2008 22:47 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 BC8E13A6AFB; Tue, 29 Apr 2008 15:47:26 -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 90AF93A6B69 for <ngo@core3.amsl.com>; Tue, 29 Apr 2008 15:47:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 tkd3Hxh4cBpZ for <ngo@core3.amsl.com>; Tue, 29 Apr 2008 15:47:18 -0700 (PDT)
Received: from exprod7og106.obsmtp.com (exprod7og106.obsmtp.com [64.18.2.165]) by core3.amsl.com (Postfix) with ESMTP id B7EEB3A6AFB for <ngo@ietf.org>; Tue, 29 Apr 2008 15:47:17 -0700 (PDT)
Received: from source ([66.129.224.36]) by exprod7ob106.postini.com ([64.18.6.12]) with SMTP; Tue, 29 Apr 2008 15:47:15 PDT
Received: from magenta.juniper.net ([172.17.27.123]) by emailsmtp55.jnpr.net with Microsoft SMTPSVC(6.0.3790.1830); Tue, 29 Apr 2008 15:47:20 -0700
Received: from idle.juniper.net (idleski.juniper.net [172.25.4.26]) by magenta.juniper.net (8.11.3/8.11.3) with ESMTP id m3TMlJx33736; Tue, 29 Apr 2008 15:47:20 -0700 (PDT) (envelope-from phil@juniper.net)
Received: from idle.juniper.net (localhost [127.0.0.1]) by idle.juniper.net (8.13.8/8.13.8) with ESMTP id m3TMjgUm091505; Tue, 29 Apr 2008 22:45:42 GMT (envelope-from phil@idle.juniper.net)
Message-Id: <200804292245.m3TMjgUm091505@idle.juniper.net>
To: Randy Presuhn <randy_presuhn@mindspring.com>
In-reply-to: <00b501c8aa2c$67959b80$6801a8c0@oemcomputer>
Date: Tue, 29 Apr 2008 18:45:42 -0400
From: Phil Shafer <phil@juniper.net>
X-OriginalArrivalTime: 29 Apr 2008 22:47:20.0648 (UTC) FILETIME=[FBA86C80:01C8AA4A]
Cc: NETCONF goes on <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>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ngo-bounces@ietf.org
Errors-To: ngo-bounces@ietf.org

"Randy Presuhn" writes:
>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?

Putting it in the hello making a short-cut against having to
do schema discovery on each connections.  If the schema information
changes, the device should send a notification to tell the client
that it might want to perform schema discovery again.

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