IETF Logo Mail Archive

Re: [netmod] YANG conformance-stmt (corrected)

"David Harrington" <ietfdbh@comcast.net> Fri, 02 May 2008 18:36 UTC

Return-Path: <netmod-bounces@ietf.org>
X-Original-To: netmod-archive@ietf.org
Delivered-To: ietfarch-netmod-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 808A83A6A56; Fri, 2 May 2008 11:36:48 -0700 (PDT)
X-Original-To: netmod@core3.amsl.com
Delivered-To: netmod@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F34253A6A56 for <netmod@core3.amsl.com>; Fri, 2 May 2008 11:36:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.56
X-Spam-Level:
X-Spam-Status: No, score=-2.56 tagged_above=-999 required=5 tests=[AWL=0.039, 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 wtRhAlfVKce6 for <netmod@core3.amsl.com>; Fri, 2 May 2008 11:36:43 -0700 (PDT)
Received: from QMTA10.emeryville.ca.mail.comcast.net (qmta10.emeryville.ca.mail.comcast.net [76.96.30.17]) by core3.amsl.com (Postfix) with ESMTP id 3FAF93A6826 for <netmod@ietf.org>; Fri, 2 May 2008 11:36:43 -0700 (PDT)
Received: from OMTA13.emeryville.ca.mail.comcast.net ([76.96.30.52]) by QMTA10.emeryville.ca.mail.comcast.net with comcast id LcZ91Z01B17UAYkAA0MC00; Fri, 02 May 2008 18:35:47 +0000
Received: from Harrington73653 ([24.128.66.199]) by OMTA13.emeryville.ca.mail.comcast.net with comcast id Licg1Z00U4HwxpC8Z00000; Fri, 02 May 2008 18:36:42 +0000
X-Authority-Analysis: v=1.0 c=1 a=ZmK9YhMPMsUA:10 a=Eay0XMiaHx_lcrZeEXgA:9 a=omtXq02P1kDkFeoOoz0Kxio-I2EA:4 a=gJcimI5xSWUA:10
From: David Harrington <ietfdbh@comcast.net>
To: netmod@ietf.org
References: <481B2EE7.5040209@andybierman.com> <200805021520.m42FKHdh016860@idle.juniper.net>
Date: Fri, 02 May 2008 14:36:40 -0400
Message-ID: <00ce01c8ac83$77417190$0600a8c0@china.huawei.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <200805021520.m42FKHdh016860@idle.juniper.net>
Thread-Index: AcisaYacQ7AgciwETVOjx7kWLcV/bgAF6R5w
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
Subject: Re: [netmod] YANG conformance-stmt (corrected)
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: NETMOD WG list <netmod.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/netmod>, <mailto:netmod-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:netmod@ietf.org>
List-Help: <mailto:netmod-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netmod>, <mailto:netmod-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: netmod-bounces@ietf.org
Errors-To: netmod-bounces@ietf.org

 
> >So, all implementers and even module readers need to maintain
> >every version of every module ever used in the system.
> 
> Nope, you only need the ones you import.  

I think agent implementers only need the ones they implement.

Manager applications and operators (and other module readers) will
need to keep a potentially-large database of versioned modules to
support multiple devices that support different versions.  

This is not a lot different than MIB modules. I believe there are
devices that support the RFC1643 Ether-MIB, and others that support
the RFC3635 MIB module. A device usually supports one or the other,
but an NMS needs to know about both versions if different devices
support different versions. 

SMIv2 set rules about how modules can be updated to prevent
incompatible differences, and we didn't have a whole tree of
dependencies, we only had one layer of IMPORTs. 

dbh

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

v2.23.0 | Report a Bug | By Email