Re: [YANG] how to signal revision?

Ladislav Lhotka <lhotka@cesnet.cz> Wed, 16 January 2008 13:05 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 1JF7xD-00012V-0N; Wed, 16 Jan 2008 08:05:15 -0500
Received: from yang by megatron.ietf.org with local (Exim 4.43) id 1JF7xC-00012Q-2p for yang-confirm+ok@megatron.ietf.org; Wed, 16 Jan 2008 08:05:14 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JF7xB-00012I-Os for yang@ietf.org; Wed, 16 Jan 2008 08:05:13 -0500
Received: from office2.cesnet.cz ([195.113.144.244]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JF7xB-0001RU-CY for yang@ietf.org; Wed, 16 Jan 2008 08:05:13 -0500
Received: from [172.29.2.201] (asus-gx.lhotka.cesnet.cz [195.113.161.161]) by office2.cesnet.cz (Postfix) with ESMTP id 2FEBED800C1 for <yang@ietf.org>; Wed, 16 Jan 2008 14:05:13 +0100 (CET)
Subject: Re: [YANG] how to signal revision?
From: Ladislav Lhotka <lhotka@cesnet.cz>
To: yang@ietf.org
In-Reply-To: <20080116.133615.104403392.mbj@tail-f.com>
References: <1200478981.7029.27.camel@missotis> <20080116.123549.140000433.mbj@tail-f.com> <1200485337.7029.43.camel@missotis> <20080116.133615.104403392.mbj@tail-f.com>
Content-Type: text/plain; charset=utf-8
Organization: CESNET
Date: Wed, 16 Jan 2008 14:05:13 +0100
Message-Id: <1200488713.7029.87.camel@missotis>
Mime-Version: 1.0
X-Mailer: Evolution 2.12.1
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
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

Martin Bjorklund píše v St 16. 01. 2008 v 13:36 +0100:
> > > 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.
> 
> No, the client has to understand that it cannot send data that the
> server doesn't support.  We want to achive two things essentially -

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 minor revision number then could be used for indicating cosmetic
changes in the YANG document not affecting the data model.

Lada

-- 
Ladislav Lhotka, CESNET
PGP Key ID: E74E8C0C



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