Re: [Supa] Network Topology Data Model and Network Configration Data Model

Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de> Tue, 11 November 2014 20:16 UTC

Return-Path: <j.schoenwaelder@jacobs-university.de>
X-Original-To: supa@ietfa.amsl.com
Delivered-To: supa@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 322131A9085 for <supa@ietfa.amsl.com>; Tue, 11 Nov 2014 12:16:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.144
X-Spam-Level:
X-Spam-Status: No, score=-2.144 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.594] 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 is-k_rvoEftW for <supa@ietfa.amsl.com>; Tue, 11 Nov 2014 12:16:19 -0800 (PST)
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 CED481A8ADD for <supa@ietf.org>; Tue, 11 Nov 2014 12:15:19 -0800 (PST)
Received: from localhost (demetrius5.irc-it.jacobs-university.de [10.70.0.222]) by atlas3.jacobs-university.de (Postfix) with ESMTP id 9D109F9D; Tue, 11 Nov 2014 21:15:18 +0100 (CET)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from atlas3.jacobs-university.de ([10.70.0.220]) by localhost (demetrius5.jacobs-university.de [10.70.0.222]) (amavisd-new, port 10030) with ESMTP id TFQEQrcNcxnR; Tue, 11 Nov 2014 21:15:07 +0100 (CET)
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, 11 Nov 2014 21:15:17 +0100 (CET)
Received: from localhost (demetrius1.jacobs-university.de [212.201.44.46]) by hermes.jacobs-university.de (Postfix) with ESMTP id 83D1920013; Tue, 11 Nov 2014 21:15:16 +0100 (CET)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius1.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id jzGY0NypH1Mc; Tue, 11 Nov 2014 21:15:14 +0100 (CET)
Received: from elstar.local (elstar.jacobs.jacobs-university.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id CD43220017; Tue, 11 Nov 2014 21:15:13 +0100 (CET)
Received: by elstar.local (Postfix, from userid 501) id BA1772F7C2B3; Tue, 11 Nov 2014 21:15:13 +0100 (CET)
Date: Tue, 11 Nov 2014 21:15:13 +0100
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: "Wunan (Eric)" <eric.wu@huawei.com>
Message-ID: <20141111201513.GC52088@elstar.local>
Mail-Followup-To: "Wunan (Eric)" <eric.wu@huawei.com>, "supa@ietf.org" <supa@ietf.org>, Tina TSOU <Tina.Tsou.Zouting@huawei.com>
References: <0F26584357FD124DB93F1535E4B0A650372A4414@szxema508-mbx.china.huawei.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <0F26584357FD124DB93F1535E4B0A650372A4414@szxema508-mbx.china.huawei.com>
User-Agent: Mutt/1.4.2.3i
Archived-At: http://mailarchive.ietf.org/arch/msg/supa/ENVUn5NiqpE-OGLMXFSjdcSd32c
Cc: "supa@ietf.org" <supa@ietf.org>, Tina TSOU <Tina.Tsou.Zouting@huawei.com>
Subject: Re: [Supa] Network Topology Data Model and Network Configration Data Model
X-BeenThere: supa@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
List-Id: "This list is to discuss SUPA \(Shared Unified Policy Automation\) related issues." <supa.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/supa>, <mailto:supa-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/supa/>
List-Post: <mailto:supa@ietf.org>
List-Help: <mailto:supa-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/supa>, <mailto:supa-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Nov 2014 20:16:24 -0000

On Tue, Nov 11, 2014 at 08:04:33PM +0000, Wunan (Eric) wrote:
> 
> 
> In the IP world, we usually talk about nodes, links, and interfaces.
> And interfaces have been generalized to cover multiple layers. Is
> there a specific reason why you prefer the term 'TerminationPoint'?
> How is a 'TerminationPoint' different from an interface (and what
> is the relationship between them)?
> 
> [Eric]: As the draft said, network topology DM is supposed to be defined in a hierachy manner.
> 
> When "IP world" is the concern, we are acutally talking about the topology DM for IP.
> 
> You are right that people are more familar with "interface", I am.
> 
> Actually in the IP Topology DM, "TerminationPoint" is interface.
> 
> Per my understanding, this word may be prefered because network topology is not only focusing on IP.
> 
> As you know some protocols don't have to depend on "interface", they got their own vacabulary.
> 
> For example, IS-IS was using "circuit" and VLAN got "port".
> 
> When speaking "interface", i feel it will be more proper when CLI is used.

A VLAN port is just another interface. See the IF-MIB or the
ietf-interfaces YANG model or the IANA interface registry. If a
TerminationPoint is just a different name for 'interface', then I
clearly prefer to stick to terms we are all familiar with.
 
> What is the difference of this topology data model from other
> proposals on the table, such as draft-clemm-i2rs-yang-network-topo-01
> and draft-hares-i2rs-info-model-service-topo-01 (there there might
> be more)?
> 
> [Eric]: I would say both of them are talking about topology data model.
> 
> One difference may be the position they are used in the architecture.
> 
> For draft-hares-i2rs-info-model-service-topo-01,
> 
> I think it is the topology for service, another layer in the hierarchy.

I was hoping for a more technical answer. Why do we need N topology
data models? If I look at the YANG snippets, I do not see what makes
them specific to a 'position in the architecture'.

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