IETF Logo Mail Archive

Re: [YANG] keyref

Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de> Tue, 22 January 2008 08:59 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 1JHEyz-0006AE-PF; Tue, 22 Jan 2008 03:59:49 -0500
Received: from yang by megatron.ietf.org with local (Exim 4.43) id 1JHEyy-0006A1-Nl for yang-confirm+ok@megatron.ietf.org; Tue, 22 Jan 2008 03:59:48 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JHEyy-00069s-DQ for yang@ietf.org; Tue, 22 Jan 2008 03:59:48 -0500
Received: from hermes.jacobs-university.de ([212.201.44.23]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JHEyy-0001uW-1R for yang@ietf.org; Tue, 22 Jan 2008 03:59:48 -0500
Received: from localhost (demetrius.jacobs-university.de [212.201.44.32]) by hermes.jacobs-university.de (Postfix) with ESMTP id 8A3D58A413; Tue, 22 Jan 2008 09:59:47 +0100 (CET)
Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id 20857-03-12; Tue, 22 Jan 2008 09:59:42 +0100 (CET)
Received: from elstar.local (elstar.iuhb02.iu-bremen.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id 173888A430; Tue, 22 Jan 2008 09:59:20 +0100 (CET)
Received: by elstar.local (Postfix, from userid 501) id BF414477B88; Tue, 22 Jan 2008 09:59:18 +0100 (CET)
Date: Tue, 22 Jan 2008 09:59:18 +0100
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: Martin Bjorklund <mbj@tail-f.com>
Subject: Re: [YANG] keyref
Message-ID: <20080122085918.GC5210@elstar.local>
Mail-Followup-To: Martin Bjorklund <mbj@tail-f.com>, ietf@andybierman.com, yang@ietf.org
References: <47954F24.905@andybierman.com> <20080122.091246.105352306.mbj@tail-f.com> <20080122081821.GA5210@elstar.local> <20080122.094430.48542159.mbj@tail-f.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20080122.094430.48542159.mbj@tail-f.com>
User-Agent: Mutt/1.5.17 (2007-11-01)
X-Virus-Scanned: amavisd-new 2.3.3 (20050822) at jacobs-university.de
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Cc: yang@ietf.org
X-BeenThere: yang@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: j.schoenwaelder@jacobs-university.de
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

On Tue, Jan 22, 2008 at 09:44:30AM +0100, Martin Bjorklund wrote:

> That's why we don't want to allow keyrefs from config to non-config.
> 
> Maybe this is a use case that we want to support as well.  But I don't
> see the difference between such a ref and a InterfaceIndex type
> solution.

Well, the InterfaceIndex type just says "the value identifies an
interface" - no more no less. The keyref is much more ambitiuous.
Despite the fact that it is only usable for keys, your aim is to bind
things together such that value changes automatically propagate. This
somehow sounds like you want to do several things at once with a
single construct.

/js

-- 
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: +49 421 200 3587         Campus Ring 1, 28759 Bremen, Germany
Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>


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

v2.8.7 | Report a Bug | By Email