IETF Logo Mail Archive

[i2rs] rib-data-model and routing-cfg

Ladislav Lhotka <lhotka@nic.cz> Fri, 09 October 2015 08:13 UTC

Return-Path: <lhotka@nic.cz>
X-Original-To: i2rs@ietfa.amsl.com
Delivered-To: i2rs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 92E881A8839; Fri, 9 Oct 2015 01:13:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.661
X-Spam-Level:
X-Spam-Status: No, score=-5.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, RCVD_IN_DNSWL_HI=-5, 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 cb2KAWjziAlF; Fri, 9 Oct 2015 01:13:12 -0700 (PDT)
Received: from mail.nic.cz (mail.nic.cz [217.31.204.67]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C9AD71A8835; Fri, 9 Oct 2015 01:13:10 -0700 (PDT)
Received: from [IPv6:2001:718:1a02:1:1c2:d14c:7ffc:4360] (unknown [IPv6:2001:718:1a02:1:1c2:d14c:7ffc:4360]) by mail.nic.cz (Postfix) with ESMTPSA id E477E181899; Fri, 9 Oct 2015 10:13:08 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nic.cz; s=default; t=1444378388; bh=GMmxRAvTU4m57gPSKSeMb89a/eIPAzzkpwd4ifGhzuA=; h=From:Date:To; b=TwFxGJ/EF8q4apW837kf3wimQtcHVXNM2JkIXFJOxP+qLT1OAxk7jGe/3G448s7ik pT7MyaQDCBFFWaznlDFKQT0RC7H3f8adeGgTcBJeJLIgYknG2xW8CuvsQzLwJZjzDm 3w7RgoADO+xw9faJZ6Vm8YiGBUyel6gvVx0NSTyQ=
From: Ladislav Lhotka <lhotka@nic.cz>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Message-Id: <7E24547E-B42B-46E2-AF76-F7639D61963F@nic.cz>
Date: Fri, 09 Oct 2015 10:13:09 +0200
To: i2rs@ietf.org, NETMOD WG <netmod@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 9.0 \(3094\))
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/i2rs/rT_FfkOVDpds2samFUJba1tmsUQ>
Subject: [i2rs] rib-data-model and routing-cfg
X-BeenThere: i2rs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Interface to The Internet Routing System \(IRS\)" <i2rs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/i2rs>, <mailto:i2rs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/i2rs/>
List-Post: <mailto:i2rs@ietf.org>
List-Help: <mailto:i2rs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/i2rs>, <mailto:i2rs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Oct 2015 08:13:13 -0000

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.

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.

Opinions?

Thanks, Lada

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

v2.23.0 | Report a Bug | By Email