Re: [YANG] how to signal revision?

Martin Bjorklund <mbj@tail-f.com> Wed, 16 January 2008 13:43 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 1JF8Xt-0001Pc-SA; Wed, 16 Jan 2008 08:43:09 -0500
Received: from yang by megatron.ietf.org with local (Exim 4.43) id 1JF8Xt-0001PW-97 for yang-confirm+ok@megatron.ietf.org; Wed, 16 Jan 2008 08:43:09 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JF8Xs-0001PO-Vo for yang@ietf.org; Wed, 16 Jan 2008 08:43:08 -0500
Received: from [213.180.94.162] (helo=mail.tail-f.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JF8Xs-0005gv-KO for yang@ietf.org; Wed, 16 Jan 2008 08:43:08 -0500
Received: from localhost (138.162.241.83.in-addr.dgcsystems.net [83.241.162.138]) by mail.tail-f.com (Postfix) with ESMTP id D9EA11B80CE; Wed, 16 Jan 2008 14:43:03 +0100 (CET)
Date: Wed, 16 Jan 2008 14:44:10 +0100 (CET)
Message-Id: <20080116.144410.247903053.mbj@tail-f.com>
To: lhotka@cesnet.cz
Subject: Re: [YANG] how to signal revision?
From: Martin Bjorklund <mbj@tail-f.com>
In-Reply-To: <1200488713.7029.87.camel@missotis>
References: <1200485337.7029.43.camel@missotis> <20080116.133615.104403392.mbj@tail-f.com> <1200488713.7029.87.camel@missotis>
X-Mailer: Mew version 5.1.51 on Emacs 22.1 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2
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

Ladislav Lhotka <lhotka@cesnet.cz> wrote:
> In other words, the client has to understand that the schema it uses is
> not compatible with the one used by the server. Would it be a problem to
> require that e.g., with every change in the data model proper the major
> revision number must be increased and also the namespace URI changed?

The problem is that it is unnecessarily restrictive - it means that an
old client cannot do its job even though the new revision of a module
just added one optional leaf (for example).  Extrapolating from this,
we can define a set of rules which must be followed in order for a
module to be compatible.


/martin


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