Re: [YANG] how to signal revision?

Balazs Lengyel <balazs.lengyel@ericsson.com> Wed, 16 January 2008 12: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 1JF7T2-0005uQ-CH; Wed, 16 Jan 2008 07:34:04 -0500
Received: from yang by megatron.ietf.org with local (Exim 4.43) id 1JF7T0-0005uE-Nj for yang-confirm+ok@megatron.ietf.org; Wed, 16 Jan 2008 07:34:02 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JF7T0-0005u5-Dx for yang@ietf.org; Wed, 16 Jan 2008 07:34:02 -0500
Received: from mailgw3.ericsson.se ([193.180.251.60]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JF7Sz-0004PA-0a for yang@ietf.org; Wed, 16 Jan 2008 07:34:02 -0500
Received: from mailgw3.ericsson.se (unknown [127.0.0.1]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id 54E7D208B1; Wed, 16 Jan 2008 13:33:58 +0100 (CET)
X-AuditID: c1b4fb3c-ae794bb0000030cf-21-478df9b6ba1c
Received: from esealmw129.eemea.ericsson.se (unknown [153.88.254.124]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id 32C16205F9; Wed, 16 Jan 2008 13:33:58 +0100 (CET)
Received: from esealmw127.eemea.ericsson.se ([153.88.254.171]) by esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Wed, 16 Jan 2008 13:33:57 +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 13:33:57 +0100
Message-ID: <478DF9B5.40006@ericsson.com>
Date: Wed, 16 Jan 2008 13:33:57 +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>
In-Reply-To: <1200485337.7029.43.camel@missotis>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 16 Jan 2008 12:33:57.0614 (UTC) FILETIME=[106118E0:01C8583C]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: -1.0 (-)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
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

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.
Balazs

Ladislav Lhotka wrote:
>>
>>> Hmm, what could be the compatible changes, apart from correcting typos
>>> in descriptions etc.? I guess even changing a single default value
>>> renders the data model incompatible.
>> Yes, changing defaults is incompatible.  If you do that, you have to
>> change the namespace.
>>
>> But there are many common compatible changes you can do, the simplest
>> is to add new optional data.
> 
> This means that a client that uses a new revision could send data that
> the server doesn't know about. I don't think it's acceptable.
> 
> 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