Re: [YANG] how to signal revision?

Martin Bjorklund <mbj@tail-f.com> Wed, 16 January 2008 12:35 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 1JF7U8-0001CH-TS; Wed, 16 Jan 2008 07:35:12 -0500
Received: from yang by megatron.ietf.org with local (Exim 4.43) id 1JF7U7-0001CC-3q for yang-confirm+ok@megatron.ietf.org; Wed, 16 Jan 2008 07:35:11 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JF7U6-0001C4-Po for yang@ietf.org; Wed, 16 Jan 2008 07:35:10 -0500
Received: from [213.180.94.162] (helo=mail.tail-f.com) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JF7U6-0000hU-DT for yang@ietf.org; Wed, 16 Jan 2008 07:35:10 -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 C9E3D1B80C3; Wed, 16 Jan 2008 13:35:08 +0100 (CET)
Date: Wed, 16 Jan 2008 13:36:15 +0100 (CET)
Message-Id: <20080116.133615.104403392.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: <1200485337.7029.43.camel@missotis>
References: <1200478981.7029.27.camel@missotis> <20080116.123549.140000433.mbj@tail-f.com> <1200485337.7029.43.camel@missotis>
X-Mailer: Mew version 5.1.51 on Emacs 22.1 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
X-Spam-Score: 0.1 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
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>
Content-Type: multipart/mixed; boundary="===============1818684764=="
Errors-To: yang-bounces@ietf.org

Ladislav Lhotka <lhotka@cesnet.cz> wrote:
> Hi Martin,
> 
> Martin Bjorklund píše v St 16. 01. 2008 v 12:35 +0100:
> > 
> > The idea is that we use the uri query argument to indicate the
> > revision number (see 7.1.3):
> > 
> >    <capability>http://acme.example.com/system?2007-06-09</capability>
> 
> This makes sense, but is the query argument allowed also in URNs?

Yes.  We also use them in rfc4741:

      urn:ietf:params:netconf:capability:url:1.0?scheme=http,ftp,file

> > 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 -
that the server accepts "an old backup" (copy-config), and that the
server can send all data is has, and let the client worry about
filtering out the stuff it doesn't understand.


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