Re: [Teas] TE Topology profile (FW: I-D Action: draft-busi-teas-te-topology-profiles-01.txt)

Italo Busi <Italo.Busi@huawei.com> Thu, 04 March 2021 18:28 UTC

Return-Path: <Italo.Busi@huawei.com>
X-Original-To: teas@ietfa.amsl.com
Delivered-To: teas@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9C8D43A13E6; Thu, 4 Mar 2021 10:28:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] 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 IdIWM2KXuONy; Thu, 4 Mar 2021 10:28:57 -0800 (PST)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 895BF3A13DE; Thu, 4 Mar 2021 10:28:57 -0800 (PST)
Received: from fraeml712-chm.china.huawei.com (unknown [172.18.147.226]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4DrzhL4Wf1z67tXD; Fri, 5 Mar 2021 02:21:06 +0800 (CST)
Received: from fraeml715-chm.china.huawei.com (10.206.15.34) by fraeml712-chm.china.huawei.com (10.206.15.61) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2106.2; Thu, 4 Mar 2021 19:28:51 +0100
Received: from fraeml715-chm.china.huawei.com ([10.206.15.34]) by fraeml715-chm.china.huawei.com ([10.206.15.34]) with mapi id 15.01.2106.006; Thu, 4 Mar 2021 19:28:51 +0100
From: Italo Busi <Italo.Busi@huawei.com>
To: 'Daniele Ceccarelli' <daniele.ceccarelli@ericsson.com>, TEAS WG <teas@ietf.org>, CCAMP <ccamp@ietf.org>, opsawg <opsawg@ietf.org>
Thread-Topic: TE Topology profile (FW: I-D Action: draft-busi-teas-te-topology-profiles-01.txt)
Thread-Index: AdcJC4el7Quu6NIpRviLyyTXhFM/lwA5nKkQAcyHs8A=
Date: Thu, 4 Mar 2021 18:28:51 +0000
Message-ID: <a5b39b2b1dcb4efdbe0595603927c867@huawei.com>
References: <67de80d4117846fba76d42e2de2b2bb3@huawei.com> <HE1PR0701MB22820ED049F65E74C3958F70F0809@HE1PR0701MB2282.eurprd07.prod.outlook.com>
In-Reply-To: <HE1PR0701MB22820ED049F65E74C3958F70F0809@HE1PR0701MB2282.eurprd07.prod.outlook.com>
Accept-Language: it-IT, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.47.84.115]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/pVT-7tdy7CJ5AsOMwsMgcZuR6Ts>
Subject: Re: [Teas] TE Topology profile (FW: I-D Action: draft-busi-teas-te-topology-profiles-01.txt)
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.29
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 04 Mar 2021 18:29:00 -0000

Daniele,

Many thanks for your comments: you have actually got the main motivation that has triggered this work

I am fine with your proposed new title

Any other opinions/suggestions from the WGs?

Thanks, Italo

> -----Original Message-----
> From: Daniele Ceccarelli [mailto:daniele.ceccarelli@ericsson.com]
> Sent: martedì 23 febbraio 2021 15:51
> To: Italo Busi <Italo.Busi@huawei.com>om>; TEAS WG <teas@ietf.org>rg>; CCAMP
> <ccamp@ietf.org>rg>; opsawg <opsawg@ietf.org>
> Subject: RE: TE Topology profile (FW: I-D Action: draft-busi-teas-te-topology-
> profiles-01.txt)
> 
> Hi Italo, authors,
> 
> I thinks this draft is extremely useful.
> 
> There are at least two reasons that come to my mind:
> 
> 1. Many times i heard concerns about the complexity of the TE topology
> model. It's true, it's a complex model, but it's possible to create profiles out of
> it and make it as simple as it is needed in a particular use case.
> 2. Another common objection is due to the fact that people are reluctant to
> use the TE topology for non TE use cases. We needed to have written
> somewhere that the TE topology, in addition to dealing with TE aspects, is also
> covering some network topology aspects there were left outside the scope of
> RFC8345.
> 
> Probably one solution would have been to rename the TE topology into
> "augmented topology" and specify that 90% of those augmentations where
> related to TE (to show that it was not 100% TE)...but this draft could work just
> fine.
> 
> Maybe just a minor comment on the title, it could try to cover both of the
> bullets above and be changed into something like: " Profiles for TE Topology
> Data Model and applicability to non TE use cases" . It can be improved...
> 
> Thanks
> Daniele
> 
> 
> -----Original Message-----
> From: CCAMP <ccamp-bounces@ietf.org> On Behalf Of Italo Busi
> Sent: den 22 februari 2021 12:29
> To: TEAS WG <teas@ietf.org>rg>; CCAMP <ccamp@ietf.org>rg>; opsawg
> <opsawg@ietf.org>
> Subject: [CCAMP] TE Topology profile (FW: I-D Action: draft-busi-teas-te-
> topology-profiles-01.txt)
> 
> Dear TEAS, CCAMP, OPSAWG,
> 
> We would like to draw you attention to the following draft that we think it
> may be relevant for some on-going work on your WGs to address network
> scenarios being that are not classified as "Traffic Engineering" using a sub-set
> (profile) of the Traffic Engineering (TE) Topology YANG data model, defined in
> [RFC8795].
> 
> We would appreciate any feedbacks on this document.
> 
> The draft has been submitted to the TEAS WG which has been responsible for
> the development of RFC8795 so we would appreciate if you can send your
> comments at least to the TEAS WG mailing list.
> 
> Italo (on behalf of co-authors)
> 
> > -----Original Message-----
> > From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
> > Sent: sabato 20 febbraio 2021 00:21
> > To: i-d-announce@ietf.org
> > Subject: I-D Action: draft-busi-teas-te-topology-profiles-01.txt
> >
> >
> > A New Internet-Draft is available from the on-line Internet-Drafts directories.
> >
> >
> >         Title           : Profiles for Traffic Engineering (TE) Topology Data Model
> >         Authors         : Italo Busi
> >                           Xufeng Liu
> >                           Igor Bryskin
> >                           Vishnu Pavan Beeram
> >                           Tarek Saad
> >                           Oscar Gonzalez de Dios
> > 	Filename        : draft-busi-teas-te-topology-profiles-01.txt
> > 	Pages           : 16
> > 	Date            : 2021-02-19
> >
> > Abstract:
> >    This document describes how profiles of the Traffic Engineering (TE)
> >    Topology Model, defined in RFC8795, can be used to address
> >    applications beyond "Traffic Engineering".
> >
> >
> > The IETF datatracker status page for this draft is:
> > https://datatracker.ietf.org/doc/draft-busi-teas-te-topology-profiles/
> >
> > There are also htmlized versions available at:
> > https://tools.ietf.org/html/draft-busi-teas-te-topology-profiles-01
> > https://datatracker.ietf.org/doc/html/draft-busi-teas-te-topology-prof
> > iles-01
> >
> > A diff from the previous version is available at:
> > https://www.ietf.org/rfcdiff?url2=draft-busi-teas-te-topology-profiles
> > -01
> >
> >
> > Please note that it may take a couple of minutes from the time of
> > submission until the htmlized version and diff are available at tools.ietf.org.
> >
> > Internet-Drafts are also available by anonymous FTP at:
> > ftp://ftp.ietf.org/internet-drafts/
> >
> >
> 
> _______________________________________________
> CCAMP mailing list
> CCAMP@ietf.org
> https://www.ietf.org/mailman/listinfo/ccamp