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

Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de> Tue, 12 July 2016 16:44 UTC

Return-Path: <j.schoenwaelder@jacobs-university.de>
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 4EDC912D100 for <i2rs@ietfa.amsl.com>; Tue, 12 Jul 2016 09:44:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.487
X-Spam-Level:
X-Spam-Status: No, score=-5.487 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-1.287] autolearn=ham autolearn_force=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 w3jxvUtfPZZu for <i2rs@ietfa.amsl.com>; Tue, 12 Jul 2016 09:44:50 -0700 (PDT)
Received: from atlas3.jacobs-university.de (atlas3.jacobs-university.de [212.201.44.18]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9BF3C12B047 for <i2rs@ietf.org>; Tue, 12 Jul 2016 09:44:50 -0700 (PDT)
Received: from localhost (demetrius5.irc-it.jacobs-university.de [10.70.0.222]) by atlas3.jacobs-university.de (Postfix) with ESMTP id 641EBE55; Tue, 12 Jul 2016 18:44:49 +0200 (CEST)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from atlas3.jacobs-university.de ([10.70.0.205]) by localhost (demetrius5.jacobs-university.de [10.70.0.222]) (amavisd-new, port 10030) with ESMTP id jt_ZWsDVOFxJ; Tue, 12 Jul 2016 18:44:46 +0200 (CEST)
Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hermes.jacobs-university.de", Issuer "Jacobs University CA - G01" (verified OK)) by atlas3.jacobs-university.de (Postfix) with ESMTPS; Tue, 12 Jul 2016 18:44:48 +0200 (CEST)
Received: from localhost (demetrius3.jacobs-university.de [212.201.44.48]) by hermes.jacobs-university.de (Postfix) with ESMTP id 7BDD820069; Tue, 12 Jul 2016 18:44:48 +0200 (CEST)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius3.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id UhYsXGIs1G6K; Tue, 12 Jul 2016 18:44:47 +0200 (CEST)
Received: from elstar.local (elstar.jacobs.jacobs-university.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id A629020063; Tue, 12 Jul 2016 18:44:46 +0200 (CEST)
Received: by elstar.local (Postfix, from userid 501) id 657BE3BCDA27; Tue, 12 Jul 2016 18:44:45 +0200 (CEST)
Date: Tue, 12 Jul 2016 18:44:45 +0200
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: "Alexander Clemm (alex)" <alex@cisco.com>
Message-ID: <20160712164445.GA36091@elstar.local>
Mail-Followup-To: "Alexander Clemm (alex)" <alex@cisco.com>, "Zhangxian (Xian)" <zhang.xian@huawei.com>, Robert Varga <nite@hq.sk>, "draft-ietf-i2rs-yang-network-topo@tools.ietf.org" <draft-ietf-i2rs-yang-network-topo@tools.ietf.org>, "i2rs@ietf.org" <i2rs@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>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <6a5706ada23a4354b08fdc543571453c@XCH-RTP-001.cisco.com>
User-Agent: Mutt/1.6.0 (2016-04-01)
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2rs/qWbMren4B6Vqd3c8Jd-OavdzOlo>
Cc: "draft-ietf-i2rs-yang-network-topo@tools.ietf.org" <draft-ietf-i2rs-yang-network-topo@tools.ietf.org>, "i2rs@ietf.org" <i2rs@ietf.org>, "Zhangxian (Xian)" <zhang.xian@huawei.com>, Robert Varga <nite@hq.sk>
Subject: Re: [i2rs] network-type: container vs. identity?
X-BeenThere: i2rs@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
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:44:52 -0000

On Tue, Jul 12, 2016 at 04:29:48PM +0000, Alexander Clemm (alex) wrote:
> 
> You could model a hierarchy of network types also through a hierarchy of identities, as you indicate in your example.  Sure, in your example this is a viable alternative, but it is not clear what you would gain through that.  For one, in the case of "otn-topology", the fact that the same topology is also an ietf-te-topology is rather implicit, not explicit.  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.   
>

Alex,

can you further detail why a hierarchy of containers is more
straightforward in some cases than a hierarchy of identities?

/js

-- 
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/>