Re: [Teas] Poll on making draft-liu-teas-yang-te-topo-01 a WG document

"BELOTTI, SERGIO (SERGIO)" <sergio.belotti@alcatel-lucent.com> Wed, 22 April 2015 13:51 UTC

Return-Path: <sergio.belotti@alcatel-lucent.com>
X-Original-To: teas@ietfa.amsl.com
Delivered-To: teas@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 254711A90FD for <teas@ietfa.amsl.com>; Wed, 22 Apr 2015 06:51:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.909
X-Spam-Level:
X-Spam-Status: No, score=-6.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, 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 Qt8rZvjJvNwk for <teas@ietfa.amsl.com>; Wed, 22 Apr 2015 06:51:39 -0700 (PDT)
Received: from smtp-fr.alcatel-lucent.com (fr-hpida-esg-02.alcatel-lucent.com [135.245.210.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 046B91A90F3 for <teas@ietf.org>; Wed, 22 Apr 2015 06:51:39 -0700 (PDT)
Received: from fr712usmtp2.zeu.alcatel-lucent.com (unknown [135.239.2.42]) by Websense Email Security Gateway with ESMTPS id 14D9EE591D463; Wed, 22 Apr 2015 13:51:34 +0000 (GMT)
Received: from FR711WXCHHUB01.zeu.alcatel-lucent.com (fr711wxchhub01.zeu.alcatel-lucent.com [135.239.2.111]) by fr712usmtp2.zeu.alcatel-lucent.com (GMO) with ESMTP id t3MDpZZ4006049 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 22 Apr 2015 15:51:35 +0200
Received: from FR711WXCHMBA05.zeu.alcatel-lucent.com ([169.254.1.213]) by FR711WXCHHUB01.zeu.alcatel-lucent.com ([135.239.2.111]) with mapi id 14.03.0195.001; Wed, 22 Apr 2015 15:51:35 +0200
From: "BELOTTI, SERGIO (SERGIO)" <sergio.belotti@alcatel-lucent.com>
To: Igor Bryskin <IBryskin@advaoptical.com>, Susan Hares <shares@ndzh.com>, "Beller, Dieter (Dieter)" <dieter.beller@alcatel-lucent.com>, 'Lou Berger' <lberger@labn.net>, 'TEAS WG' <teas@ietf.org>
Thread-Topic: [Teas] Poll on making draft-liu-teas-yang-te-topo-01 a WG document
Thread-Index: AQHQey2FIBj7yF4xq06Iqba2nJF52J1XTOMAgADeyACAALdPgIAAK6TA
Date: Wed, 22 Apr 2015 13:51:35 +0000
Message-ID: <B9FEE68CE3A78C41A2B3C67549A96F48B75CC0A5@FR711WXCHMBA05.zeu.alcatel-lucent.com>
References: <552C0611.70500@labn.net> <55315820.70304@alcatel-lucent.com> <002b01d07b2d$7e45c1f0$7ad145d0$@ndzh.com> <553648A8.5070800@alcatel-lucent.com> <00c101d07ca1$c8b3f480$5a1bdd80$@ndzh.com> <9079b663ee6646f0b7b083ba56b236db@ATL-SRV-MBX1.advaoptical.com>
In-Reply-To: <9079b663ee6646f0b7b083ba56b236db@ATL-SRV-MBX1.advaoptical.com>
Accept-Language: it-IT, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.239.27.40]
Content-Type: multipart/alternative; boundary="_000_B9FEE68CE3A78C41A2B3C67549A96F48B75CC0A5FR711WXCHMBA05z_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/teas/jt6IO-n953NC7AehNgFE1uS-jHc>
Subject: Re: [Teas] Poll on making draft-liu-teas-yang-te-topo-01 a WG document
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Traffic Engineering Architecture and Signaling working group discussion list <teas.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/teas>, <mailto:teas-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/teas/>
List-Post: <mailto:teas@ietf.org>
List-Help: <mailto:teas-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/teas>, <mailto:teas-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Apr 2015 13:51:44 -0000

Hi Igor,
while we all agree in the needs of both type of topology requirements , I would just clarify that the Dieter's comment, that I have shared during my positive vote for "support" of the draft, is addressing "recursion" , and I do not see recursion is linked to "independent topologies" but only to hierarchies (overlay/underlay relationship in the draft).

Thanks
Cheers

Sergio



From: Teas [mailto:teas-bounces@ietf.org] On Behalf Of Igor Bryskin
Sent: mercoledì 22 aprile 2015 15:09
To: Susan Hares; Beller, Dieter (Dieter); 'Lou Berger'; 'TEAS WG'
Subject: Re: [Teas] Poll on making draft-liu-teas-yang-te-topo-01 a WG document

Sue,

I think you are exactly right. The model supports arbitrary number of TE topologies. Some of them are bound  in hierarchies. There could be multiple independent hierarchies.
For example, topologies cooked by provider on per- client or VPN is an example of independent topologies. Topology overlay/underlay relationships form topology hierarchies. For example, a topology cooked for a particular client (overlay) is supported by provider native topology (underlay), and this is an example of a hierarchy.

Cheers,
Igor

From: Teas [mailto:teas-bounces@ietf.org] On Behalf Of Susan Hares
Sent: Tuesday, April 21, 2015 10:12 PM
To: 'Dieter Beller'; 'Lou Berger'; 'TEAS WG'
Subject: Re: [Teas] Poll on making draft-liu-teas-yang-te-topo-01 a WG document

Dieter:

Thank you for answer the hierarchy question.   Your abstract topologies reates arbitrary number of levels in a hierarchy.

The question for the wide-topologies can be restated at Layer 3 as multiple VPNS.   In IP, You can create 1-N number of VPNs.  This is n-wide topologies. Does this fit into your abstract topologies?

Sue

From: Dieter Beller [mailto:Dieter.Beller@alcatel-lucent.com]
Sent: Tuesday, April 21, 2015 8:55 AM
To: Susan Hares; 'Lou Berger'; 'TEAS WG'
Subject: Re: [Teas] Poll on making draft-liu-teas-yang-te-topo-01 a WG document

Hi Sue, all,
On 20.04.2015 07:47, Susan Hares wrote:
Dieter:

Do you think the arbitrary number of TE topologies are arbitrary in a hierarchy (1-N levels) or a wide topologies (1-N topologies).
I am having some difficulties to really understand your question. Let me try to clarify what I meant with my comment:

An abstract topology is according to my understanding composed of links and vertices (nodes) and a vertex could be an abstract
node that represents an underlying abstract topology. This underlying abstract topology can be decomposed again into links and
vertices (nodes) when you zoom into an abstract node.

Based on this principle of recursion, you can create a hierarchy that can have arbitrary levels and a further decomposition is possible
until you have not reached the physical node level (bottom of the hierarchy).

I hope this helps.


Thanks,
Dieter


Sue

From: Teas [mailto:teas-bounces@ietf.org] On Behalf Of Dieter Beller
Sent: Friday, April 17, 2015 3:00 PM
To: Lou Berger; TEAS WG
Subject: Re: [Teas] Poll on making draft-liu-teas-yang-te-topo-01 a WG document

Hi Lou, all,

yes/support - however, other than +1 to comments from Paul, Young, and Xian, I would like to emphasize again what I commented
during the discussion in Dallas:

An introduction and a description of the information model (similar to that in draft-ietf-i2rs-yang-network-topo-00) is needed in the
beginning of the document that explains the YANG data model. This section would describe the relationships of the managed entities
(objects) and their attributes with references to the YANG model tree structure and the model definition.

Moreover, for example in the context of ACTN, the model also needs to describe how it can support an arbitrary number of TE
topology hierarchies.  I have seen that the current model already provides some means for that, but this should be described in
more detail and some examples should be provided.


Thanks,
Dieter
On 13.04.2015 20:08, Lou Berger wrote:

All,



This is start of a two week poll on making

draft-liu-teas-yang-te-topo-01 a TEAS working group document. Please

send email to the list indicating "yes/support" or "no/do not support".

If indicating no, please state your technical reservations with the

document.  If yes, please also feel free to provide comments you'd like

to see addressed once the document is a WG document.



This document is the product of the TE Topology YANG Model Design Team

and the intent is for this work to serve as the foundation for the WG's

normal activities in this area, i.e., the document is the starting point

for the WG -- not a finished product.  The DT will be closed once we

have a WG document on this topic.



The poll ends Monday April 27th

Thanks,

Lou (and Pavan, who is a co-author)



_______________________________________________

Teas mailing list

Teas@ietf.org<mailto:Teas@ietf.org>

https://www.ietf.org/mailman/listinfo/teas


_______________________________________________

Teas mailing list

Teas@ietf.org<mailto:Teas@ietf.org>

https://www.ietf.org/mailman/listinfo/teas