Re: [Rtg-yang-coord] [netmod] rib-data-model and routing-cfg

Ladislav Lhotka <lhotka@nic.cz> Tue, 13 October 2015 16:30 UTC

Return-Path: <lhotka@nic.cz>
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 EF7181B4862; Tue, 13 Oct 2015 09:30:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.661
X-Spam-Level:
X-Spam-Status: No, score=-0.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_EQ_CZ=0.445, HOST_EQ_CZ=0.904, T_RP_MATCHES_RCVD=-0.01] autolearn=no
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 uhHRVGcUXATo; Tue, 13 Oct 2015 09:30:13 -0700 (PDT)
Received: from mail.nic.cz (mail.nic.cz [IPv6:2001:1488:800:400::400]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CD50D1B4861; Tue, 13 Oct 2015 09:30:12 -0700 (PDT)
Received: from [IPv6:2a01:5e0:29:ffff:6c23:3ee3:ca1:cdc5] (unknown [IPv6:2a01:5e0:29:ffff:6c23:3ee3:ca1:cdc5]) by mail.nic.cz (Postfix) with ESMTPSA id 09DB3180A4C; Tue, 13 Oct 2015 18:30:11 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nic.cz; s=default; t=1444753811; bh=EKj9yh0A07ijJhVQYFF46oFYFlhma2MGE47FPpEtodQ=; h=From:Date:To; b=EHRoPfbDwyYBMPZptbOq80Z9xwkqM9uxU3E/0Heuaapd5qA7gyAFZvNbhLmOyIpc6 Ucip9GEEaoiPBRC5Vomo7uz646Q95kvYRNGVBFcOjCBf5KQUXhYvJhwiLW03brgT56 87/eBuGpWzdaDvQyCN/x1DEjr9V1kf4LsePkpjkU=
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.0 \(3094\))
From: Ladislav Lhotka <lhotka@nic.cz>
In-Reply-To: <D2429721.34A0E%acee@cisco.com>
Date: Tue, 13 Oct 2015 18:30:09 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <DBF22257-A7A2-4679-927A-EBCC1022FE13@nic.cz>
References: <7E24547E-B42B-46E2-AF76-F7639D61963F@nic.cz> <D23D3103.34500%acee@cisco.com> <D2429721.34A0E%acee@cisco.com>
To: "Acee Lindem (acee)" <acee@cisco.com>
X-Mailer: Apple Mail (2.3094)
X-Virus-Scanned: clamav-milter 0.98.7 at mail
X-Virus-Status: Clean
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtg-yang-coord/oR52DbGg64fqPegQb6997nXDUYo>
Cc: Routing YANG <rtg-yang-coord@ietf.org>, "i2rs@ietf.org" <i2rs@ietf.org>, NETMOD WG <netmod@ietf.org>, Routing WG <rtgwg@ietf.org>
Subject: Re: [Rtg-yang-coord] [netmod] rib-data-model and routing-cfg
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: <https://mailarchive.ietf.org/arch/browse/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: Tue, 13 Oct 2015 16:30:15 -0000

> On 13 Oct 2015, at 17:20, Acee Lindem (acee) <acee@cisco.com>; wrote:
> 
> Hi Lada, NETMOD, 
> 
> So I think we should move forward this ietf-rtg-cfg so that it can be
> augmented and other work can move forward. We are still in disagreement
> with respect to routing-instance/interface configuration.
> 
>    - We feel the IPv4/IPv6 interfaces should reference the
> routing-instance in their config state. This is consistent with
> draft-rtgyangdt-rtgwg-device-model-01.txt.
>    - You feel that the routing-instance should have a list of leaf-ref’s
> to the interface. You believe the leaf-ref provides a level of validation
> due to the fact that references can be confined to routing-instance
> references. However, heretofore, no models are referencing the interface
> leaf-refs in the list.

True, these models (ietf-isis, for instance) use leafrefs with "if:interface-ref" type. However, such leafrefs are under-constrained because they can be configured to refer to:

- interfaces of any layer, including physical interfaces, VLAN trunks etc.

- interfaces assigned to any routing instance.

I believe in all these cases the choice has to be limited to (1) L3 interfaces, and (2) belonging to "own" routing instance. These constraints will have to be checked in server code somehow - I would prefer to have them represented in the data model.

But if nobody shares this concern with me, I am not going to block the document on this issue.

Lada 

> 
> Other than the Routing YANG Design Team having chosen the first option -
> are there any other opinions?
> 
> Thanks,
> Acee
> 
> On 10/9/15, 9:00 AM, "netmod on behalf of Acee Lindem (acee)"
> <netmod-bounces@ietf.org on behalf of acee@cisco.com>; wrote:
> 
>> Hi Lada, 
>> I2RS is not chartered to do the base models. There are other routing
>> models that reference routing-cfg and even in-progress implementations.
>> 
>> On 10/9/15, 4:13 AM, "netmod on behalf of Ladislav Lhotka"
>> <netmod-bounces@ietf.org on behalf of lhotka@nic.cz>; wrote:
>> 
>>> Hi,
>>> 
>>> I am sorry for cross-posting but I think it is high time to decide the
>>> relationship between the data models in i2rs-rib-data-model and
>>> netmod-routing-cfg I-Ds because they clearly target the same management
>>> data in a router. I can see three possible scenarios:
>>> 
>>> 1. The i2rs-rib module will be modified to augment
>>> ietf-routing/ietf-ipv[46]-unicast-routing.
>> 
>> This would seem to be the obvious choice.
>> 
>>> 
>>> 2. The scope of ietf-routing will be changed so that it would address
>>> only host routing and simple routers. The modelling work for advanced
>>> routers will be done elsewhere.
>>> 
>>> 3. The work on netmod-routing-cfg will be stopped.
>> 
>> A fourth option would be for me to take over ownership, move the work to
>> the RTG WG, and we’d recruit some strong authors/reviewers from operators
>> and other vendors (involving the ADs in selection).
>> 
>> Thanks,
>> Acee 
>> 
>> 
>>> 
>>> Opinions?
>>> 
>>> Thanks, Lada
>>> 
>>> --
>>> Ladislav Lhotka, CZ.NIC Labs
>>> PGP Key ID: E74E8C0C
>>> 
>>> 
>>> 
>>> 
>>> _______________________________________________
>>> netmod mailing list
>>> netmod@ietf.org
>>> https://www.ietf.org/mailman/listinfo/netmod
>> 
>> _______________________________________________
>> netmod mailing list
>> netmod@ietf.org
>> https://www.ietf.org/mailman/listinfo/netmod
> 

--
Ladislav Lhotka, CZ.NIC Labs
PGP Key ID: E74E8C0C