Re: [Rtg-yang-coord] issue :R03: assignment of interfaces to routing instances

Xufeng Liu <xufeng.liu@ericsson.com> Wed, 14 January 2015 15:33 UTC

Return-Path: <xufeng.liu@ericsson.com>
X-Original-To: rtg-yang-coord@ietfa.amsl.com
Delivered-To: rtg-yang-coord@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 94FA71A8987 for <rtg-yang-coord@ietfa.amsl.com>; Wed, 14 Jan 2015 07:33:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.301
X-Spam-Level:
X-Spam-Status: No, score=-3.301 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_29=0.6, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id g73Ml32tO0BV for <rtg-yang-coord@ietfa.amsl.com>; Wed, 14 Jan 2015 07:33:06 -0800 (PST)
Received: from usevmg20.ericsson.net (usevmg20.ericsson.net [198.24.6.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E4C261A8820 for <rtg-yang-coord@ietf.org>; Wed, 14 Jan 2015 07:33:05 -0800 (PST)
X-AuditID: c618062d-f79376d000000ceb-f6-54b63a015f85
Received: from EUSAAHC007.ericsson.se (Unknown_Domain [147.117.188.93]) by usevmg20.ericsson.net (Symantec Mail Security) with SMTP id 49.F0.03307.10A36B45; Wed, 14 Jan 2015 10:42:25 +0100 (CET)
Received: from EUSAAMB107.ericsson.se ([147.117.188.124]) by EUSAAHC007.ericsson.se ([147.117.188.93]) with mapi id 14.03.0195.001; Wed, 14 Jan 2015 10:33:03 -0500
From: Xufeng Liu <xufeng.liu@ericsson.com>
To: Ladislav Lhotka <lhotka@nic.cz>, =?utf-8?B?SsO8cmdlbiBTY2jDtm53w6RsZGVy?= <j.schoenwaelder@jacobs-university.de>
Thread-Topic: [Rtg-yang-coord] issue :R03: assignment of interfaces to routing instances
Thread-Index: AQHQLs3lKpNtcgDGLkW279NVg125yJy+HaWA///2Y7CAAIIPAIAAT5kAgADL+wCAAAz2IA==
Date: Wed, 14 Jan 2015 15:33:02 +0000
Message-ID: <AAB1CC9C17CBA440BDFA169056B93B9EB1128D@eusaamb107.ericsson.se>
References: <m2wq6j5skf.fsf@nic.cz> <D0D9CB3F.B6C0%acee@cisco.com> <8022061D-AB8F-4A97-84E7-A6E4F898F57F@nic.cz> <AAB1CC9C17CBA440BDFA169056B93B9EB10521@eusaamb107.ericsson.se> <35023717-7EE8-4F45-B2F4-B24E0F86FA5A@nic.cz> <20150113212732.GD1545@elstar.local> <23976026-499F-4C9C-844A-DB53BE244992@nic.cz>
In-Reply-To: <23976026-499F-4C9C-844A-DB53BE244992@nic.cz>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [147.117.188.10]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrLLMWRmVeSWpSXmKPExsUyuXRPrC6j1bYQg8cTVS0mv53HbHF1409G iwur5rJZ/H5+m9mBxWPK742sHkuW/GTy2HDA02PT5TuMASxRXDYpqTmZZalF+nYJXBmTuu4x FzyQrli+6hN7A2OLdBcjJ4eEgInEtD0rGSFsMYkL99azdTFycQgJHGGUWDzxLxOEs5xR4vut d6xdjBwcbAJaEpefOoKYIgJlEr1/UkF6mQUSJFbc+cMGYgsLREp0dq1jhiiJknj7QQfCDJNo /8oKUsEioCrxYso/MJtXwFvi+aPtYLaQwG4miRk32EHKOQWsJJbv8AUJMwId9v3UGiaIReIS t57MZ4I4WEBiyZ7zzBC2qMTLxxAjJQSUJCYtPQd2LrOApsT6XfoQrYoSU7ofskNsFZQ4OfMJ ywRGsVlIps5C6JiFpGMWko4FjCyrGDlKi1PLctONDDYxAuPnmASb7g7GPS8tDzEKcDAq8fAW Lt4aIsSaWFZcmXuIUZqDRUmct+Xd+hAhgfTEktTs1NSC1KL4otKc1OJDjEwcnFINjIkcF0wn Hb36rkL6fJn0hIapv1m/bD7zZOmXIFmeJ74Tc74U/FPY3qywijFU6VdEeuST3wo1J4L3MjEn TsrvPyOhtTDliX3f3bD0vIgPNy3nn0s+ndj26bch11arqxlqlhybbu5Tb3qWononjX+7dmqn 3ZTbewTbHv/hWVnDFr+rvnT7neTFD5VYijMSDbWYi4oTAYQGlHWAAgAA
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtg-yang-coord/juvkxJMMdc5V_GVyXlmn3U_s6n4>
Cc: "rtg-yang-coord@ietf.org" <rtg-yang-coord@ietf.org>, "Acee Lindem \(acee\)" <acee@cisco.com>
Subject: Re: [Rtg-yang-coord] issue :R03: assignment of interfaces to routing instances
X-BeenThere: rtg-yang-coord@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "\"List to discuss coordination between the Routing related YANG models\"" <rtg-yang-coord.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtg-yang-coord>, <mailto:rtg-yang-coord-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtg-yang-coord/>
List-Post: <mailto:rtg-yang-coord@ietf.org>
List-Help: <mailto:rtg-yang-coord-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtg-yang-coord>, <mailto:rtg-yang-coord-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Jan 2015 15:33:13 -0000


> -----Original Message-----
> From: Ladislav Lhotka [mailto:lhotka@nic.cz]
> Sent: Wednesday, January 14, 2015 4:38 AM
> To: Jürgen Schönwälder
> Cc: Xufeng Liu; rtg-yang-coord@ietf.org; Acee Lindem (acee)
> Subject: Re: [Rtg-yang-coord] issue :R03: assignment of interfaces to routing
> instances
> 
> 
> > On 13 Jan 2015, at 22:27, Juergen Schoenwaelder <j.schoenwaelder@jacobs-
> university.de> wrote:
> >
> > On Tue, Jan 13, 2015 at 05:42:38PM +0100, Ladislav Lhotka wrote:
> >>
> >>> 2. Add an attribute routing-instance-ref (type leafref) in interface to point to
> the name attribute (key) of routing-instance.
> >>
> >> This is IMO a good idea, we would then have links in both directions.
> >>
> >
> > I assume this would be config false state data, otherwise we only add
> 
> Yes, right. I’d propose to configure this assignment under routing-instance and
> the have the reference(s) to the routing-instance as an (optional) item in
> if:interface entries (in their state data).
> 
> > configuration complexity for no real value. And this likely would have
> > to be a leaf-list.
> 
> This depends on whether we conclude that the assignment has to be disjoint or
> not. I support the latter option, so yes, I’d also prefer to have a leaf-list for this
> purpose.
> 
> Lada
> 
> >
> >>> 3. Make the new routing-instance-ref added above to be part of the key, i.e.
> create a composite key <name, routing-instance-ref> for interface.
> >>
> >> This is not possible because:
> >>
> >> - the key of the if:interface list cannot be extended by additional
> >> components;
> >>
> >> - if:interface is a flat list that contains interfaces of all layers,
> >> but an assignment to a routing-instance makes sense only for L3
> >> interfaces;
> >>
> >> - YANG module ietf-interfaces is intended for all kinds of devices, including
> those that don’t implement ietf-routing.
> >>
> >
> > +1
> >
> > /js
> >
[Xufeng] Hi Lada, I acknowledge the difficulties here. However, is there a good way to handle the following case?
	In routing-instance "RI-A", an interface named "IF-1" is already configured.
	In routing-instance "RI-B", I'd like to configure an different interface with the same name "IF-1".
Thanks,
- Xufeng
> > --
> > 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/>
> 
> --
> Ladislav Lhotka, CZ.NIC Labs
> PGP Key ID: E74E8C0C
> 
> 
>