IETF Logo Mail Archive

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

"Russ White" <russw@riw.us> Sun, 18 January 2015 13:31 UTC

Return-Path: <russw@riw.us>
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 9D8761B29E7 for <rtg-yang-coord@ietfa.amsl.com>; Sun, 18 Jan 2015 05:31:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] 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 15qCxFazmXOr for <rtg-yang-coord@ietfa.amsl.com>; Sun, 18 Jan 2015 05:31:21 -0800 (PST)
Received: from server.riw.us (server.riw.us [162.144.32.236]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9C0A41B29CD for <rtg-yang-coord@ietf.org>; Sun, 18 Jan 2015 05:31:21 -0800 (PST)
Received: from 108-78-210-25.lightspeed.chrlnc.sbcglobal.net ([108.78.210.25]:60276 helo=RussPC) by server.riw.us with esmtpsa (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.84) (envelope-from <russw@riw.us>) id 1YCpwe-00009g-SE; Sun, 18 Jan 2015 13:31:13 +0000
From: "Russ White" <russw@riw.us>
To: "'Juergen Schoenwaelder'" <j.schoenwaelder@jacobs-university.de>, "'Ladislav Lhotka'" <lhotka@nic.cz>
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>
In-Reply-To: <20150113212732.GD1545@elstar.local>
Date: Sun, 18 Jan 2015 08:31:06 -0500
Message-ID: <00a201d03323$042993d0$0c7cbb70$@riw.us>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 15.0
Thread-Index: AQE6RmhwFDw7jYPOXpdztTVPovM8eAGH/4EqAjQUf5ABdAzTXgFSYRzWAW6nGiOdsi7F0A==
Content-Language: en-us
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - server.riw.us
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - riw.us
X-Get-Message-Sender-Via: server.riw.us: authenticated_id: russw@riw.us
X-Source:
X-Source-Args:
X-Source-Dir:
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtg-yang-coord/JQQoS1zpMLPTs3jOd_3iwfi4Xgs>
Cc: rtg-yang-coord@ietf.org, "'Acee Lindem \(acee\)'" <acee@cisco.com>, 'Xufeng Liu' <xufeng.liu@ericsson.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: Sun, 18 Jan 2015 13:31:22 -0000

> > > 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.

How often would we traverse the link from the interface to the routing instance? I'm trying to think of a use case where you'd be looking at an interface configuration or state, and need to find out which routing instance it's being "included" in, and -- given a single interface can be included in multiple routing instances, how would I know which one I'm actually looking for?

What specific question would I be asking that would cause me to look at this list -- in other words, when would I ask, "what routing instances is this interface included in?"

:-)

Russ

v2.8.7 | Report a Bug | By Email