IETF Logo Mail Archive

Re: [YANG] how to signal revision?

Balazs Lengyel <balazs.lengyel@ericsson.com> Wed, 16 January 2008 10:32 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 1JF5Zg-0001nj-Ai; Wed, 16 Jan 2008 05:32:48 -0500
Received: from yang by megatron.ietf.org with local (Exim 4.43) id 1JF5Zf-0001nK-Ae for yang-confirm+ok@megatron.ietf.org; Wed, 16 Jan 2008 05:32:47 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JF5Ze-0001kR-Un for yang@ietf.org; Wed, 16 Jan 2008 05:32:46 -0500
Received: from mailgw3.ericsson.se ([193.180.251.60]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JF5Ze-00022y-IG for yang@ietf.org; Wed, 16 Jan 2008 05:32:46 -0500
Received: from mailgw3.ericsson.se (unknown [127.0.0.1]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id 4840620EAB; Wed, 16 Jan 2008 11:31:58 +0100 (CET)
X-AuditID: c1b4fb3c-b179abb0000030cf-63-478ddd1e70b8
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id 2B7F1209DC; Wed, 16 Jan 2008 11:31:58 +0100 (CET)
Received: from esealmw128.eemea.ericsson.se ([153.88.254.176]) by esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Wed, 16 Jan 2008 11:31:57 +0100
Received: from [159.107.197.224] ([159.107.197.224]) by esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Wed, 16 Jan 2008 11:31:57 +0100
Message-ID: <478DDD1D.2060605@ericsson.com>
Date: Wed, 16 Jan 2008 11:31: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>
In-Reply-To: <1200478981.7029.27.camel@missotis>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 16 Jan 2008 10:31:57.0893 (UTC) FILETIME=[057C4F50:01C8582B]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: -1.0 (-)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Cc: yang <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

Hello Lada,
As I understand it, the basic idea is that you have compatible and incompatible changes. 
Chapter 5.4 speaks about compatible changes. Even for these there could be a subversion 
indicator somewhere in the module.

For incompatible changes, really anything major, the module will have a new name and URI. There 
is currently an empty chapter "9.  Updating a Module" in the current draft that will describe this.

Balazs

Ladislav Lhotka wrote:
> Hi,
> 
> how can the server and client make sure they are both using the same
> revision of a given data model? Capabilities in NETCONF hello messages
> use URIs but YANG draft says in sec. 5.4 that different revisions of the
> same module should have the same namespace.
> 
> 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