IETF Logo Mail Archive

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

Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de> Tue, 11 November 2014 09:17 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 EA4B71A8893 for <supa@ietfa.amsl.com>; Tue, 11 Nov 2014 01:17:12 -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 sBsQ6ES7R5B7 for <supa@ietfa.amsl.com>; Tue, 11 Nov 2014 01:17:10 -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 7CC201A1BDF for <supa@ietf.org>; Tue, 11 Nov 2014 01:17:10 -0800 (PST)
Received: from localhost (demetrius5.irc-it.jacobs-university.de [10.70.0.222]) by atlas3.jacobs-university.de (Postfix) with ESMTP id EE6F9787; Tue, 11 Nov 2014 10:17:08 +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 m1AdKoCzXYxq; Tue, 11 Nov 2014 10:17:01 +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 10:17:08 +0100 (CET)
Received: from localhost (demetrius3.jacobs-university.de [212.201.44.48]) by hermes.jacobs-university.de (Postfix) with ESMTP id 1BB4E20017; Tue, 11 Nov 2014 10:17:08 +0100 (CET)
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 x19NW__j9s-X; Tue, 11 Nov 2014 10:17:07 +0100 (CET)
Received: from elstar.local (elstar.jacobs.jacobs-university.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id 9322620013; Tue, 11 Nov 2014 10:17:06 +0100 (CET)
Received: by elstar.local (Postfix, from userid 501) id A975E2F7B882; Tue, 11 Nov 2014 10:17:05 +0100 (CET)
Date: Tue, 11 Nov 2014 10:17:05 +0100
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: Tina TSOU <Tina.Tsou.Zouting@huawei.com>
Message-ID: <20141111091705.GA49576@elstar.local>
Mail-Followup-To: Tina TSOU <Tina.Tsou.Zouting@huawei.com>, "supa@ietf.org" <supa@ietf.org>
References: <C0E0A32284495243BDE0AC8A066631A8186601A2@szxeml557-mbs.china.huawei.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <C0E0A32284495243BDE0AC8A066631A8186601A2@szxeml557-mbs.china.huawei.com>
User-Agent: Mutt/1.4.2.3i
Archived-At: http://mailarchive.ietf.org/arch/msg/supa/OuSs2yFDG7zmR_Feez52xSdZ2u8
Cc: "supa@ietf.org" <supa@ietf.org>
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 09:17:13 -0000

On Tue, Nov 11, 2014 at 08:43:57AM +0000, Tina TSOU wrote:
> Dear all,
> 
> As time not allowed, these are the slides for agenda item: Network Topology Data Model and Network Configration Data Model, which I received.
>

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)?

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)?

If topology data models are crucial for 'northbound' applications, why
is lets say draft-zaalouk-supa-configuration-model-01 not using a
topology data model but instead coming up with its own notion of
interfaces and node identifiers?

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

v2.23.0 | Report a Bug | By Email