Re: [CCAMP] Webex meeting invitation: Microwave topology

"Yemin (Amy)" <amy.yemin@huawei.com> Tue, 24 September 2019 16:29 UTC

Return-Path: <amy.yemin@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 6C5D8120922; Tue, 24 Sep 2019 09:29:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.198
X-Spam-Level:
X-Spam-Status: No, score=-4.198 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_FONT_LOW_CONTRAST=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 7W6TlGSFeB9c; Tue, 24 Sep 2019 09:28:58 -0700 (PDT)
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 5A0C7120938; Tue, 24 Sep 2019 09:28:56 -0700 (PDT)
Received: from lhreml702-cah.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id 7764E31235C7FB494C60; Tue, 24 Sep 2019 17:28:51 +0100 (IST)
Received: from DGGEMM401-HUB.china.huawei.com (10.3.20.209) by lhreml702-cah.china.huawei.com (10.201.108.43) with Microsoft SMTP Server (TLS) id 14.3.408.0; Tue, 24 Sep 2019 17:28:33 +0100
Received: from DGGEMM528-MBX.china.huawei.com ([169.254.8.92]) by DGGEMM401-HUB.china.huawei.com ([10.3.20.209]) with mapi id 14.03.0439.000; Wed, 25 Sep 2019 00:28:28 +0800
From: "Yemin (Amy)" <amy.yemin@huawei.com>
To: Jonas Ahlberg <jonas.ahlberg=40ericsson.com@dmarc.ietf.org>, CCAMP Working Group <ccamp-chairs@ietf.org>, ccamp <ccamp@ietf.org>
Thread-Topic: [CCAMP] Webex meeting invitation: Microwave topology
Thread-Index: AQHVVxp7hjxRsFpiUky138Nw01bSvaczMAcQgAgLEv8=
Date: Tue, 24 Sep 2019 16:28:27 +0000
Message-ID: <9C5FD3EFA72E1740A3D41BADDE0B461FD27AD139@DGGEMM528-MBX.china.huawei.com>
References: <HE1PR0701MB2905CD665AC10208ABF4CDB589AB0@HE1PR0701MB2905.eurprd07.prod.outlook.com>, <HE1PR0701MB29058428DC15612B1E1E480589890@HE1PR0701MB2905.eurprd07.prod.outlook.com>
In-Reply-To: <HE1PR0701MB29058428DC15612B1E1E480589890@HE1PR0701MB2905.eurprd07.prod.outlook.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [10.47.90.239]
Content-Type: multipart/mixed; boundary="_004_9C5FD3EFA72E1740A3D41BADDE0B461FD27AD139DGGEMM528MBXchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/ccamp/ZnyhQ3fIGjbCn8qNvj8ynTAVArA>
Subject: Re: [CCAMP] Webex meeting invitation: Microwave topology
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, 24 Sep 2019 16:29:01 -0000

Sorry to catch up the discussion late.

Let's take the example from the ETSI 1st mWT plugtest, see attached document.
There were 7 vendors joined in 1st ETSI plugtest, which are the major suppliers in the market.
Implementation based on te-topo already shows good example of running code.

The current mw-topo model doesn’t use the all concepts from te-topo model, e.g., te-tunnel and connectivity matrix, it do use an important feature underlay topo from the te-topo. The underlay allows the links in the eth topo to be associated with mw-link.
If the mw-topo is based on ietf-network-topo, the underlay relationship between eth-topo and mw-topo is missing.
A mw controller normally doesn’t mange on mw technology only, it also need to manage other te technologies. Having a common model between those technologies would simplify the implementation.

There’re many data node definition in the te-topo which are also useful for mw domain.
ietf-te-topology:provider-id & ietf-te-topology:client-id & ietf-te-topology:te-topology-id: These attributes are useful in hierarchical domain controllers architecture to understand which controller (provider-id) is exposing the topology to which controller (client-id)
ietf-te-topology:name: The name attributes are useul to provide user-friendly labels for the operator to use
ietf-te-topology:te-node-id: The te-node-id and te-tp-id are used by the ETH topology to reference the underlying MW link supporting a logical ETH link
ietf-te-topology:oper-status: Managing the administrative and operational status of MW links is a useful feature

A model defined today should have the capability to extend for future use.
With microwave technology evolution, use case such as protection will be required, where SRLG from te-topo could be used; PtMP microwave will be introduced apart from current PtP microwave, where te-tunnel could be introduced.  te-topo provides a good basis for future extension.

BR,
Amy
________________________________
发件人: CCAMP [ccamp-bounces@ietf.org] 代表 Jonas Ahlberg [jonas.ahlberg=40ericsson.com@dmarc.ietf.org]
发送时间: 2019年9月19日 22:00
收件人: CCAMP Working Group; ccamp
主题: Re: [CCAMP] Webex meeting invitation: Microwave topology

Hi all,
Some short notes from the meeting September 19th.
Participants: Daniela Spreafico, Stephen Cheng, Dragos D, Jonas Ahlberg


  *   Applicability of ietf-te-topology for microwave radio link
The meeting didn’t see any obvious use cases or attributes for microwave radio link that would require a microwave radio link topology to be based on ietf-te-topology. This needs to be further analyzed and fully understood before a decision on way forward can be made. Next step is to review/discuss a list of applicable attributes from ietf-te-topology to be proposed by Amy and Italo.



  *   New presence container for identification of microwave specific termination points and links.
The meeting understood the purpose of the proposal from Stephen but need more time to consider the actual YANG fragments to be changed. To be further discussed at next meeting.



  *   Moving the replacement of interface-root
Stephen explained the reason for suggesting an update of how to make a reference to radio-link-terminal and carrier-termination interfaces. To be further discussed at next meeting.



  *   Simplified topology model
The removal of the dependency to te-topology and the other suggested changes have been compiled into a new simplified model presented by Stephen. A decision about if/how to make use of that proposal is pending the outcome of the other topics above, but it can still be used to illustrate the alternative approaches under discussion.



Regards
Jonas A

-----Original Appointment-----
From: CCAMP Working Group <ccamp-chairs@ietf.org>
Sent: den 20 augusti 2019 07:46
To: CCAMP Working Group; ccamp
Subject: [CCAMP] Webex meeting invitation: Microwave topology
When: den 19 september 2019 07:00-08:00 America/New_York.
Where: https://ietf.webex.com/ietf



CCAMP Working Group invites you to join this Webex meeting.





Meeting number (access code): 647 343 270


Meeting password: D7dhCJpZ





Occurs every Thursday effective Thursday, August 22, 2019 until Thursday, October 24, 2019 from 7:00 AM to 8:00 AM, (UTC-05:00) Eastern Time (US & Canada)

7:00 am  |  (UTC-05:00) Eastern Time (US & Canada)  |  1 hr





Join<https://ietf.webex.com/ietf/j.php?MTID=ma65a6a5186962890ec535e711ec3d3f9>






Join by phone

Tap to call in from a mobile device (attendees only)

1-650-479-3208<tel:%2B1-650-479-3208,,*01*647343270%23%23*01*> Call-in toll number (US/Canada)

1-877-668-4493<tel:1-877-668-4493,,*01*647343270%23%23*01*> Call-in toll free number (US/Canada)

Global call-in numbers<https://ietf.webex.com/ietf/globalcallin.php?MTID=m57c83575d64804b110f94f798d438720>  |  Toll-free calling restrictions<https://www.webex.com/pdf/tollfree_restrictions.pdf>






Need help? Go to http://help.webex.com