Re: [CCAMP] Microwave Topology - Exporting tunnel as a link

Italo Busi <Italo.Busi@huawei.com> Tue, 10 December 2019 16:10 UTC

Return-Path: <Italo.Busi@huawei.com>
X-Original-To: ccamp@ietfa.amsl.com
Delivered-To: ccamp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7C1B212013B; Tue, 10 Dec 2019 08:10:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, 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 twGwIb6IW6_f; Tue, 10 Dec 2019 08:10:37 -0800 (PST)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (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 C2854120024; Tue, 10 Dec 2019 08:10:36 -0800 (PST)
Received: from LHREML711-CAH.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id 9632961EB3AE8CD2399D; Tue, 10 Dec 2019 16:10:32 +0000 (GMT)
Received: from fraeml720-chm.china.huawei.com (10.206.15.16) by LHREML711-CAH.china.huawei.com (10.201.108.34) with Microsoft SMTP Server (TLS) id 14.3.408.0; Tue, 10 Dec 2019 16:10:31 +0000
Received: from fraeml715-chm.china.huawei.com (10.206.15.34) by fraeml720-chm.china.huawei.com (10.206.15.16) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1713.5; Tue, 10 Dec 2019 17:10:31 +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.1713.004; Tue, 10 Dec 2019 17:10:31 +0100
From: Italo Busi <Italo.Busi@huawei.com>
To: Stephen Cheng <Stephen.Cheng@Aviatnet.com>, ccamp <ccamp@ietf.org>
CC: "teas@ietf.org" <teas@ietf.org>
Thread-Topic: Microwave Topology - Exporting tunnel as a link
Thread-Index: AdWEpP7IdqO7CXelTnaU/dkiPzW5wwqza2Sg
Date: Tue, 10 Dec 2019 16:10:31 +0000
Message-ID: <a2a6112cd4294225a1c86ff993de7ad2@huawei.com>
References: <MWHPR2201MB12158D30B9C33CFCD58AF8E2996D0@MWHPR2201MB1215.namprd22.prod.outlook.com>
In-Reply-To: <MWHPR2201MB12158D30B9C33CFCD58AF8E2996D0@MWHPR2201MB1215.namprd22.prod.outlook.com>
Accept-Language: it-IT, en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [10.203.246.192]
Content-Type: multipart/related; boundary="_004_a2a6112cd4294225a1c86ff993de7ad2huaweicom_"; type="multipart/alternative"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/ccamp/ADLQaOAr8K7Q15ml_6ujBBlruj8>
Subject: Re: [CCAMP] Microwave Topology - Exporting tunnel as a link
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ccamp/>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Dec 2019 16:10:39 -0000

Hi Stephen,

We have discussed your technical concerns during the TEAS call last Friday and this is the suggestions we have got:


1)      How to model the scenario where a server-layer TE Link (e.g., a MW TE Link) is used by a client-layer non-TE Link (e.g., an IP Link)



The suggestion is to use the L3 TE Link (which augments the IP Link). The L3 TE link can point to the MW TE link.



2)      How to model the scenario where a server-layer TE Tunnel (e.g., an Optical TE Link) is used by a client-layer non-TE Link (e.g., an IP Link)



The TE tunnel has hierarchical TE Link (pointer). The Optical TE tunnel can point to the Packet TE link. The L3 TE link points to the same packet TE link.



3)      How to model Ethernet LAG using the TE Topology YANG model



This is possible but not fully described. We have agreed to provide some description in the TE Tutorial document:



https://tools.ietf.org/html/draft-ietf-teas-te-topo-and-tunnel-modeling



An open issue has been added in github to track this action:



https://github.com/tsaad-dev/te/issues/61

Italo

Italo Busi
Principal Optical Transport Network Research Engineer
Huawei Technologies Co., Ltd.
Tel : +39 345 4721946
Email : italo.busi@huawei.com
[cid:image002.png@01D5AF7C.B705BDF0]

This e-mail and its attachments contain confidential information from HUAWEI, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it!

From: Stephen Cheng [mailto:Stephen.Cheng@Aviatnet.com]
Sent: giovedì 17 ottobre 2019 06:42
To: Italo Busi <Italo.Busi@huawei.com>om>; ccamp <ccamp@ietf.org>rg>; CCAMP Working Group <ccamp-chairs@ietf.org>
Subject: Microwave Topology - Exporting tunnel as a link

Italo,

In previous Microwave Topology meeting, you mentioned that it is possible to export a tunnel in a ietf-te-topology as a link for use in a non ietf-te-topology instance.
I would love to hear your thoughts on how to actually export a tunnel as a link, to allow a non te topology layering over a te topology instance. It certainly is one of my concern on basing microwave l1 topology on te topology.

Thanks,
Stephen Cheng