Skip to content
Skip to breadcrumbs
Skip to header menu
Skip to action menu
Skip to quick search

Pages
…

Open Transport Configuration and Control Home
5G-xHaul
5G-xHaul Call-in Details & Notes

2021-09-29 5G-xHaul Meeting notes

Skip to end of metadata

Created by Martin Skorupski, last modified on Sep 29, 2021

Go to start of metadata

29 Sep 2021 | 2am PDT | 5am EDT | 09:00 UTC | 10:00 BST | 11:00 CEST | 12:00 EEST | 14:30 IST | 17:00 CST | 18:00 JST |

Web Conference:

https://thorsten-heinze-telefonica-de.webex.com/thorsten-heinze-telefonica-de/j.php?MTID=m849236edb092dffd10071725f5b8839f

Invited:

Andrea Delmonte
@Andreas Lattoch
@Alexander Wenk
Daniela Spreafico
Daniel Perez Calvo
Danilo Pala
Eduardo Yusta
Hubing
Hsudarsa
Jorge Lopez
Istvan Vencz
Jasper Yang
Leo
Ma Yong
Michael Binder
Nader Zein
Paul Parva
Pawel Krecicki
Petr Jurcik
Prathiba Jeevan
Roberto Servadio
Shuzhan
Thomas Seitz
Thomas Schulze
Tian Zhu
Thorsten Heinze
Yossi
Zhang Dong

(please feel free to correct and update your names Thank you very much!!!)

Info to:

Tracy Van Brakle

Goals

going forward

Mailings

https://groups.google.com/a/opennetworking.org/g/wireless-transport?pli=1

Discussion items

Time	Item	Who	Notes
00:00	Chair topic		no update
00:03	Admin		Next meetings 2021-10-06: Martin Skorupski 2021-10-13: Martin Skorupski 2021-10-20: Martin Skorupski 2021-10-27: Martin Skorupski
00:03	issues labeled "yang to be provided"	@Prathiba	A list of related "issues" send by email to Martin → handled "offline" to be presented next week
00:05	VLAN-FD #12	Martin Skorupski	priorityToTrafficClassMappingList to be added Decision: approved as proposed
00:08	VLAN-FD #15	Martin Skorupski	component-id lack a default value Decision: approved as proposed
00:11	MAC-FD #5 (learned MAC Addresses)	Martin Skorupski	Technology specific amendment to the ForwardingDomain class for documenting current forwarding according to IEEE 802.1 . Decision: approved as proposed
00:15	Relation between planning and actual data from the network	@Andreas Lattoch	Quick synch from last week connector types to be standardized work in progress - to be continued Current work bases on the "EquipmentModel"
00:45	Synchronization	@Alexander Wenk @Prathiba	Some answer about modeling and mappings can be found here https://www.itu.int/rec/dologin_pub.asp?lang=s&id=T-REC-G.7721-201811-I!!PDF-E&type=items Working Assumption to be proven about figure 7-21 – UML model diagram – CdSpecificView PtpDomainConstraint_Pac is a model OUTSIDE of the device (control-construct) There is the first expectation that all attributes are laready in the LTP(Sync) and CLOCK object class. NeSync_Pac under the assupbtion that "Ne..." mean "NetworkElement..." the "NeSync_Pac" could be called "ControlConstructSync_Pac" and attached to the ControlConstruct itself
	END OF THE MEETING
00:00	Mediator Instance Manager	Thorsten Heinze	Pre- Discussion happened yesterday info send by Thorsten on Monday 2021-05-177 in addition Thorsten will send the "background discussion slide".... Mediator Instance Manager What is the protocol? NETCONF or REST or RESTCONF or ... Working Assumption: not decided SIAE would like to decide based on efforts after analysis. UML include the "service" - but not the operational and maintenance layer YAML (OpenAPI3) → UML (papyrus) → YANG → 2021-05-25 Any questions? no questions 2021-06-16 please see "App layer on top of the SDN controller" above.

Action items