IETF Logo Mail Archive

Re: [YANG] how to signal revision?

Balazs Lengyel <balazs.lengyel@ericsson.com> Wed, 16 January 2008 13:34 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 1JF8PJ-00009e-08; Wed, 16 Jan 2008 08:34:17 -0500
Received: from yang by megatron.ietf.org with local (Exim 4.43) id 1JF8PI-00009T-0o for yang-confirm+ok@megatron.ietf.org; Wed, 16 Jan 2008 08:34:16 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JF8PH-00009K-NP for yang@ietf.org; Wed, 16 Jan 2008 08:34:15 -0500
Received: from mailgw4.ericsson.se ([193.180.251.62]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JF8PH-0005Wh-Ae for yang@ietf.org; Wed, 16 Jan 2008 08:34:15 -0500
Received: from mailgw4.ericsson.se (unknown [127.0.0.1]) by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id A29922139F; Wed, 16 Jan 2008 14:34:14 +0100 (CET)
X-AuditID: c1b4fb3e-b06a2bb00000459d-8b-478e07d63cf2
Received: from esealmw129.eemea.ericsson.se (unknown [153.88.254.124]) by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id 80D44215ED; Wed, 16 Jan 2008 14:34:14 +0100 (CET)
Received: from esealmw129.eemea.ericsson.se ([153.88.254.177]) by esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Wed, 16 Jan 2008 14:34:14 +0100
Received: from [159.107.197.224] ([159.107.197.224]) by esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Wed, 16 Jan 2008 14:34:14 +0100
Message-ID: <478E07D5.2090801@ericsson.com>
Date: Wed, 16 Jan 2008 14:34:13 +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:34:14.0083 (UTC) FILETIME=[7BF67930:01C85844]
X-Brightmail-Tracker: AAAAAA==
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: -1.0 (-)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
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

Yes. How would you like to define it?
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