IETF Logo Mail Archive

Re: [i2rs] network-type: container vs. identity?

Robert Varga <nite@hq.sk> Tue, 12 July 2016 16:53 UTC

Return-Path: <nite@hq.sk>
X-Original-To: i2rs@ietfa.amsl.com
Delivered-To: i2rs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5761D12D17B for <i2rs@ietfa.amsl.com>; Tue, 12 Jul 2016 09:53:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.287
X-Spam-Level:
X-Spam-Status: No, score=-3.287 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-1.287] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=hq.sk
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 nozP1CVPZwAj for <i2rs@ietfa.amsl.com>; Tue, 12 Jul 2016 09:53:41 -0700 (PDT)
Received: from mail.hq.sk (hq.sk [81.89.59.181]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 88FA012D100 for <i2rs@ietf.org>; Tue, 12 Jul 2016 09:53:41 -0700 (PDT)
Received: from [10.137.1.13] (46.229.239.158.host.vnet.sk [46.229.239.158]) by mail.hq.sk (Postfix) with ESMTPSA id 8D5BE24376B; Tue, 12 Jul 2016 18:53:39 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=hq.sk; s=mail; t=1468342419; bh=tVrzdpWlmTecFNELreRoQtf/s0WGI6IhVJUQzHoZ9ps=; h=Subject:To:References:Cc:From:Date:In-Reply-To; b=kv35nCVR/V+gsyapOUBbMyNc95dozBY5YlwqKG549EaMNVkLBc7T3z4Z235BmemrG 9xuwtiDisNjbX2kTA+FX4kV52S3Bc/2khIORb2NgcW6TZUrsPdnKshz7FiuFZrmWk6 Opi9THGc7HAPKEUXNJZ9MAz7/LN55l1ibyqfTqL0=
To: "Alexander Clemm (alex)" <alex@cisco.com>, "Zhangxian (Xian)" <zhang.xian@huawei.com>, "draft-ietf-i2rs-yang-network-topo@tools.ietf.org" <draft-ietf-i2rs-yang-network-topo@tools.ietf.org>
References: <C636AF2FA540124E9B9ACB5A6BECCE6B7DEDFCE6@SZXEMA512-MBS.china.huawei.com> <5c0b2dee-fe0b-139d-1b1e-dc6936ff747d@hq.sk> <C636AF2FA540124E9B9ACB5A6BECCE6B7DEFF3AF@SZXEMA512-MBS.china.huawei.com> <6a5706ada23a4354b08fdc543571453c@XCH-RTP-001.cisco.com>
From: Robert Varga <nite@hq.sk>
Message-ID: <f69d671f-e5b9-2ec9-ee68-d6312468f39e@hq.sk>
Date: Tue, 12 Jul 2016 18:53:32 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.1.1
MIME-Version: 1.0
In-Reply-To: <6a5706ada23a4354b08fdc543571453c@XCH-RTP-001.cisco.com>
Content-Type: multipart/signed; micalg="pgp-sha512"; protocol="application/pgp-signature"; boundary="dNo92X5QMf6E55FbmCaGCAgBF0MUCbPx0"
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2rs/dGfBVLhTR_24MGIbKge3mPZ0c-U>
Cc: "i2rs@ietf.org" <i2rs@ietf.org>
Subject: Re: [i2rs] network-type: container vs. identity?
X-BeenThere: i2rs@ietf.org
X-Mailman-Version: 2.1.17
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: Tue, 12 Jul 2016 16:53:43 -0000

On 07/12/2016 06:29 PM, Alexander Clemm (alex) wrote:
> Per Robert's point, if for some reason you have multiple traits and want to "compose" a network to encompass multiple types, this is straightforward to do with the current pattern, not so straightforward with identities.   

There is also an issue of consistency within the models. While it may
not be obvious to have more 'topology types', it certainly makes sense
for nodes within a topology -- for example in ODL we tag topology nodes
with capabilities based on the southbound protocol (like PCEP, OpenFlow,
NETCONF).

Bye,
Robert

v2.23.0 | Report a Bug | By Email