IETF Logo Mail Archive

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

Jeff Tantsura <jeff.tantsura@ericsson.com> Wed, 14 January 2015 16:26 UTC

Return-Path: <jeff.tantsura@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 555291A8FD6 for <rtg-yang-coord@ietfa.amsl.com>; Wed, 14 Jan 2015 08:26:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 xWwj2ow_L1Ir for <rtg-yang-coord@ietfa.amsl.com>; Wed, 14 Jan 2015 08:26:16 -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 F0DEE1A8832 for <rtg-yang-coord@ietf.org>; Wed, 14 Jan 2015 08:26:15 -0800 (PST)
X-AuditID: c618062d-f79376d000000ceb-f1-54b64675a87b
Received: from EUSAAHC002.ericsson.se (Unknown_Domain [147.117.188.78]) by usevmg20.ericsson.net (Symantec Mail Security) with SMTP id EB.B4.03307.57646B45; Wed, 14 Jan 2015 11:35:34 +0100 (CET)
Received: from EUSAAMB109.ericsson.se ([147.117.188.126]) by EUSAAHC002.ericsson.se ([147.117.188.78]) with mapi id 14.03.0195.001; Wed, 14 Jan 2015 11:26:13 -0500
From: Jeff Tantsura <jeff.tantsura@ericsson.com>
To: Andy Bierman <andy@yumaworks.com>, Xufeng Liu <xufeng.liu@ericsson.com>
Thread-Topic: [Rtg-yang-coord] issue :R03: assignment of interfaces to routing instances
Thread-Index: AQHQLs3lKpNtcgDGLkW279NVg125yJy+HaWA///2Y7CAAIIPAIAAT5kAgADL+wCAAAz2IIAAXHAA//+siRCAAFZ3gP//f6IA
Date: Wed, 14 Jan 2015 16:26:12 +0000
Message-ID: <D0DBD855.889EB%jeff.tantsura@ericsson.com>
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> <AAB1CC9C17CBA440BDFA169056B93B9EB1128D@eusaamb107.ericsson.se> <20150114155450.GA3625@elstar.local> <AAB1CC9C17CBA440BDFA169056B93B9EB1139B@eusaamb107.ericsson.se> <CABCOCHSiWG=x0vTYKKxqhMqd69yK+Nuo0k_Y_=Y_KHkQBDi3FA@mail.gmail.com>
In-Reply-To: <CABCOCHSiWG=x0vTYKKxqhMqd69yK+Nuo0k_Y_=Y_KHkQBDi3FA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.4.4.140807
x-originating-ip: [147.117.188.10]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <5E6F393E74BE66479DE454AC40159617@ericsson.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprPIsWRmVeSWpSXmKPExsUyuXSPn26Z27YQg3NtYhaT385jtnhwZBa7 xdWNPxktLqyay2bx+/ltZgdWjym/N7J6LFnyk8ljwwFPj02X7zB6tPRfZAlgjeKySUnNySxL LdK3S+DK+LLqGGvBfJGKhvffWBsYLwl0MXJySAiYSJw+8ZQJwhaTuHBvPVsXIxeHkMARRonJ P18zgySEBJYzSlw4yghiswkYSPz/dpwFxBYR8JZ4sGUDWDOzwEFGiU8/EkFsYYFIicPHrrF3 MXIA1URJvP2gA1GeJ7FwyX5WEJtFQFXi6sU9YK28AuYSn+Y8YYHYu5ZF4uOkF2AJToFAia8P VoI1MAId9/3UGqhd4hK3nsyHOlpAYsme88wQtqjEy8f/wOpFBfQknm3YzA4RV5KYtPQcK0Sv jsSC3Z/YQG5jFrCWWN0TAhHWlli2EOJdXgFBiZMzn7BMYJSYhWTbLCTdsxC6ZyHpnoWkewEj 6ypGjtLi1LLcdCODTYzAGD0mwaa7g3HPS8tDjAIcjEo8vIWLt4YIsSaWFVfmHmKU5mBREudt ebc+REggPbEkNTs1tSC1KL6oNCe1+BAjEwenVANj6MKZ+kll3tHnPp9YfPJcYs+ezYFBy/4c FT6vb8jzdr5uTOhV2cgJK1vvRjjmWE1s2ONf8Lhfw1fXcJHeo6/HNXMcDdddv8e24aXzgZ3N RutWzs3vnRF63EtoktaKxT8fC+7p6Z32sO+nWIf6GovnuWerl79/WjeZw+31/yPv1e97dHFY Kk35o8RSnJFoqMVcVJwIADJSQQ2yAgAA
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtg-yang-coord/8NCE0pQo40lY0ohOsz_f3o1pizM>
Cc: "rtg-yang-coord@ietf.org" <rtg-yang-coord@ietf.org>, Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>, "Acee Lindem \(acee\)" <acee@cisco.com>, Ladislav Lhotka <lhotka@nic.cz>
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 16:26:19 -0000

Andy,

Agree, routing-instance+interface_name would suffice and also meet
existing implementations constrains

Cheers,
Jeff




-----Original Message-----
From: Andy Bierman <andy@yumaworks.com>
Date: Wednesday, January 14, 2015 at 8:05 AM
To: Xufeng Liu <xufeng.liu@ericsson.com>
Cc: "rtg-yang-coord@ietf.org" <rtg-yang-coord@ietf.org>rg>, "Acee Lindem
(acee)" <acee@cisco.com>om>, Juergen Schoenwaelder
<j.schoenwaelder@jacobs-university.de>de>, Ladislav Lhotka <lhotka@nic.cz>
Subject: Re: [Rtg-yang-coord] issue :R03: assignment of interfaces to
routing instances

>On Wed, Jan 14, 2015 at 7:59 AM, Xufeng Liu <xufeng.liu@ericsson.com>
>wrote:
>>
>>
>>> -----Original Message-----
>>> From: Juergen Schoenwaelder
>>>[mailto:j.schoenwaelder@jacobs-university.de]
>>> Sent: Wednesday, January 14, 2015 10:55 AM
>>> To: Xufeng Liu
>>> Cc: Ladislav Lhotka; rtg-yang-coord@ietf.org; Acee Lindem (acee)
>>> Subject: Re: [Rtg-yang-coord] issue :R03: assignment of interfaces to
>>>routing
>>> instances
>>>
>>> On Wed, Jan 14, 2015 at 03:33:02PM +0000, Xufeng Liu wrote:
>>> > > >
>>> > [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".
>>>
>>> In the RFC 7223 interface data model the interface name is used as a
>>>key and
>>> hence you can't have two different interfaces with the same name.
>>>
>>> /js
>>
>> [Xufeng] This is the issue that we'd like to solve. We have such a use
>>case.
>>
>
>
>The interfaces list is for the entire device, and we should not change
>that.
>IMO you are describing an implementation detail, not a use-case.
>The format of the name string can be "RI-1/IF-1" for example.
>If "IF-1" is not going to be unique, then make up a new arbitrary name.
>
>
>>>
>>> --
>>> 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/>
>>
>> _______________________________________________
>> Rtg-yang-coord mailing list
>> Rtg-yang-coord@ietf.org
>> https://www.ietf.org/mailman/listinfo/rtg-yang-coord
>
>Andy
>
>_______________________________________________
>Rtg-yang-coord mailing list
>Rtg-yang-coord@ietf.org
>https://www.ietf.org/mailman/listinfo/rtg-yang-coord

v2.8.7 | Report a Bug | By Email