IETF Logo Mail Archive

Re: [YANG] how to signal revision?

Balazs Lengyel <balazs.lengyel@ericsson.com> Wed, 16 January 2008 13:38 UTC

Return-path: <yang-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1JF8TO-00059z-Oi; Wed, 16 Jan 2008 08:38:30 -0500
Received: from yang by megatron.ietf.org with local (Exim 4.43) id 1JF8TN-00059s-IW for yang-confirm+ok@megatron.ietf.org; Wed, 16 Jan 2008 08:38:29 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JF8TN-00059k-8E for yang@ietf.org; Wed, 16 Jan 2008 08:38:29 -0500
Received: from mailgw4.ericsson.se ([193.180.251.62]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JF8TM-0002CU-Qh for yang@ietf.org; Wed, 16 Jan 2008 08:38:29 -0500
Received: from mailgw4.ericsson.se (unknown [127.0.0.1]) by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id 504FB212A5; Wed, 16 Jan 2008 14:38:27 +0100 (CET)
X-AuditID: c1b4fb3e-ae69ebb00000459d-0d-478e08d2e422
Received: from esealmw127.eemea.ericsson.se (unknown [153.88.254.122]) by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id DDB60210FC; Wed, 16 Jan 2008 14:38:26 +0100 (CET)
Received: from esealmw127.eemea.ericsson.se ([153.88.254.175]) by esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Wed, 16 Jan 2008 14:38:21 +0100
Received: from [159.107.197.224] ([159.107.197.224]) by esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Wed, 16 Jan 2008 14:38:20 +0100
Message-ID: <478E08CC.5040901@ericsson.com>
Date: Wed, 16 Jan 2008 14:38:20 +0100
From: Balazs Lengyel <balazs.lengyel@ericsson.com>
User-Agent: Thunderbird 2.0.0.4 (X11/20070604)
MIME-Version: 1.0
To: Ladislav Lhotka <lhotka@cesnet.cz>
Subject: Re: [YANG] how to signal revision?
References: <1200478981.7029.27.camel@missotis> <20080116.123549.140000433.mbj@tail-f.com> <1200485337.7029.43.camel@missotis> <478DF9B5.40006@ericsson.com> <1200489477.7029.92.camel@missotis>
In-Reply-To: <1200489477.7029.92.camel@missotis>
Content-Type: text/plain; charset=UTF-8; format=flowed
X-OriginalArrivalTime: 16 Jan 2008 13:38:21.0027 (UTC) FILETIME=[0F272330:01C85845]
X-Brightmail-Tracker: AAAAAA==
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Cc: yang@ietf.org
X-BeenThere: yang@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: YANG modeling Language for NETCONF <yang.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/yang>, <mailto:yang-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/yang>
List-Post: <mailto:yang@ietf.org>
List-Help: <mailto:yang-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/yang>, <mailto:yang-request@ietf.org?subject=subscribe>
Errors-To: yang-bounces@ietf.org

So we have two combinations
1) old manager new node (my case)
2) new manager old node

Both are interesting questions.
YANG's primary aim is to define what model the node provides, so I think we should define here 
what is a compatible change in the node's model.
Balazs

Ladislav Lhotka wrote:
> Balazs Lengyel píše v St 16. 01. 2008 v 13:33 +0100:
>> We should first define, what we mean with compatible. My definition is that a management system 
>> that knows only the old version can handle the node i.e. anything it writes into the node will 
>> work as in the previous version. An old management client will not send the new data.
> 
> OK, so by compatibility you essentialy mean "compatible from server's
> viewpoint".
> 
> Lada
> 

-- 
Balazs Lengyel                       Ericsson Hungary Ltd.
TSP System Manager
ECN: 831 7320                        Fax: +36 1 4377792
Tel: +36-1-437-7320     email: Balazs.Lengyel@ericsson.com


_______________________________________________
YANG mailing list
YANG@ietf.org
https://www1.ietf.org/mailman/listinfo/yang

v2.8.7 | Report a Bug | By Email