Re: [Rtg-yang-coord] rtg-cfg hierachy (PLEASE REPLY TO THIS ONE WITH THE CORRECT MAIL ALIASES)
Thomas Morin <thomas.morin@orange.com> Wed, 18 February 2015 11:36 UTC
Return-Path: <tmmorin.orange@gmail.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 543A91A87A5;
Wed, 18 Feb 2015 03:36:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,
DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FROM=0.001,
J_CHICKENPOX_14=0.6, RCVD_IN_DNSWL_LOW=-0.7, 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 D2uzpfUaK45S; Wed, 18 Feb 2015 03:36:13 -0800 (PST)
Received: from mail-we0-f175.google.com (mail-we0-f175.google.com
[74.125.82.175])
(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
(No client certificate requested)
by ietfa.amsl.com (Postfix) with ESMTPS id 989071A802A;
Wed, 18 Feb 2015 03:36:12 -0800 (PST)
Received: by wesw55 with SMTP id w55so578791wes.5;
Wed, 18 Feb 2015 03:36:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
h=sender:message-id:date:from:organization:user-agent:mime-version:to
:subject:references:in-reply-to:content-type
:content-transfer-encoding;
bh=IEBLgCMYZSOR/Dz8niXyx1WoKdpf4BiOaSkQ5CPn+R4=;
b=G0lJpoTJ0r1LKHZoTkDbwLnToMOJ5hqsNEmNJ50S+zN9L99Y0AQTTXrcZjblCssF/B
iJ1tCNjcLFShvJVEPLY7DTJwv/GMWJiksJZih/RHeFpRfrO3HJIFr489eFhKpbx+bgyw
S1LLrejz1DqoYusXWvO0l52xlXA/jj1/SYwNMb33zzXB/+loW+0w5OTRJZgqGbKg5C1N
dDZ4VMIvy6EYlVwrApHY7a2quV2GvEhwcvm4Kfk22ZBdMcQkAFMoJxibYlP2hYmbUacV
WL2gAABUA8A/AWyv027IyxN5oIp8HqjlRyfhOcqoDBHtdtY0gNMLiWCd9NNiiBB5jxt0
7m/Q==
X-Received: by 10.194.5.37 with SMTP id p5mr72422060wjp.20.1424259371395;
Wed, 18 Feb 2015 03:36:11 -0800 (PST)
Received: from [127.0.0.1] (ARennes-652-1-96-43.w2-11.abo.wanadoo.fr.
[2.11.199.43])
by mx.google.com with ESMTPSA id hs7sm25011528wib.4.2015.02.18.03.36.09
(version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
Wed, 18 Feb 2015 03:36:10 -0800 (PST)
Sender: Thomas Morin <tmmorin.orange@gmail.com>
Message-ID: <54E47928.8050108@orange.com>
Date: Wed, 18 Feb 2015 12:36:08 +0100
From: Thomas Morin <thomas.morin@orange.com>
Organization: Orange
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: "Acee Lindem (acee)" <acee@cisco.com>, Ladislav Lhotka <lhotka@nic.cz>,
Routing YANG <rtg-yang-coord@ietf.org>, Routing WG <rtgwg@ietf.org>
References: <14011_1423852286_54DE42FE_14011_2207_1_D103AD28.E652%acee@cisco.com>
In-Reply-To: <14011_1423852286_54DE42FE_14011_2207_1_D103AD28.E652%acee@cisco.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtg-yang-coord/NeXpZHT1wJNmtloS11rGJhJzrEs>
Subject: Re: [Rtg-yang-coord] rtg-cfg hierachy (PLEASE REPLY TO THIS ONE
WITH THE CORRECT MAIL ALIASES)
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, 18 Feb 2015 11:36:15 -0000
Hi Acee, Lada, It seems that my comment that you quote was more related to filters than to routing tables, and indeed, *filters* were moved from "router" to "global" in revision -03 that followed my review. Additionally, Lada, you say that based on my comments "in rev. -03 the list of RIBs (then called "routing-table") was the moved out of the routing instance (then called "router") and became global.". But if I look at -03, "routing-table" is still a child of "router". The change to make "routing-table" global was made in -05. I guess you need to find out what was the motivation for the change in -05, a few months after my initial comments were address. Best, -Thomas 2015-02-13, Acee Lindem (acee): > > Hi Lada, Thomas, > > On 2/13/15, 5:10 AM, "Ladislav Lhotka" <lhotka@nic.cz> wrote: > >> Hi, >> >> "Acee Lindem (acee)" <acee@cisco.com> writes: >> >>> Hi Thomas, >>> >>> It is my understanding that the RIBs were moved out of the >>> routing-instance in response to your comment that a RIB would need to be >>> attached to multiple routing instances. I don¹t agree with this >>> model. I >> >> Acee refers to this comment that Thomas made in his review of >> draft-ietf-netmod-routing-cfg-02 on 2012-03-23: >> >> "Allowing multiple "routers" is a good starting point for using these >> specs in the context of RFC4364 (MPLS/BGP IP VPNs). However, if I >> understand correctly Yang syntax, the way the filters are defined would >> not work in the context of RFC4364, where a BGP routing instance in the >> master "router" exports selected routes in each of the routing table of >> each VPN (VRF). The VRF also export routes to the master instance." >> >> And indeed, in rev. -03 the list of RIBs (then called "routing-table") >> was the moved out of the routing instance (then called "router") and >> became global. > > Then do you agree to move the RIBs back into the routing-instance? Both > the BGP YANG drafts model L3VPN definitions under the corresponding > address family in BGP. > > http://www.ietf.org/id/draft-shaikh-idr-bgp-model-00.txt > http://www.ietf.org/id/draft-zhdankin-idr-bgp-cfg-00.txt > > Thanks, > Acee > > > >> >> Lada >> >>> believe that a routing instance implies a VRF, virtual router or >>> something >>> in between and that a RIB should be associated with one and only one >>> routing instance. Additionally, I feel that RIBs are basically passive >>> entities with respect to import/export of routes between RIBs in the >>> same >>> or other routing-instances. Rather, all import/export is under the >>> control >>> of a routing-protocol. For example, this would be handled by a BGP >>> routing-protocol instance for L3VPNs. >>> >>> I¹d like to get the opinions of others on this fundamental aspect of the >>> rtg-cfg model. >>> >>> Thanks, >>> Acee >>> >>> >> >> -- >> Ladislav Lhotka, CZ.NIC Labs >> PGP Key ID: E74E8C0C > > >
- Re: [Rtg-yang-coord] rtg-cfg hierachy (PLEASE REP… Acee Lindem (acee)
- Re: [Rtg-yang-coord] rtg-cfg hierachy (PLEASE REP… Thomas Morin
- Re: [Rtg-yang-coord] rtg-cfg hierachy (PLEASE REP… Acee Lindem (acee)
- Re: [Rtg-yang-coord] rtg-cfg hierachy (PLEASE REP… Ladislav Lhotka
- Re: [Rtg-yang-coord] rtg-cfg hierachy (PLEASE REP… Martin Bjorklund
- Re: [Rtg-yang-coord] rtg-cfg hierachy (PLEASE REP… Ladislav Lhotka