Open Transport Configuration & Control
Space shortcuts
Expand all   Collapse all
Child pages
  • 2020-10-07 5G-xHaul Meeting notes

Versions Compared

Old Version 2

changes.mady.by.user Martin Skorupski

Saved on

compared with

New Version Current

changes.mady.by.user Alex Stancu

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Date

| 2am PDT | 5am EDT | 9:00 UTC | 11:00 CEST | 12:00 EEST | 14:30 IST | 17:00 CST | 18:00 JST |


Web Conference:

https://thorsten-heinze-telefonica-de.webex.com/join/andreas.lattoch.external 

Attendees

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

Info to: 

Goals

  • going forward

Discussion items

TimeItemWhoNotes
00:00chair topic 
no update 

00:00

Admin

Next meetings

2020-09-30: Martin Skorupski

2020-10-07: Alex Stancu

2020-10-14: Martin Skorupski

2020-10-21: Martin Skorupski

00:00Software Inventory

Last week we started a discussion about Software Inventory.

  • Software Management (download, install, activate) is not in the current focus
  • Relation to hardware inventory (equipment) is required

An YANG example which is useful can be found here: https://wiki.o-ran-sc.org/display/OAM/Software+Management (just as inspiration and to check if there are missing parts in CoreModel 1.4)

00:00Layering discussion (FCs, FDs etc.)Thorsten Heinze
  • Will publish in wiki the latest slide which is the result of discussions
until nowpdate
  • :
  • View file
    nameslides to be published.pptx
    height250
  • link to the contribution: 2020-09-16 5G-xHaul Meeting notes

  • Continue discussion from last week
  • Question:
    • 1x VLAN FD and 2x VLAN FC
      • Impact on MAC interfaces
  • 1:1 betweeen VLAN-IF-LTP and EthernetContainer-LTP
  • 1x physical → only one MAC-Interface?
  • MacSwitch attributes: mac-address-learning, aging-time - are such attributes sufficient to instantiate a new FD/FC objects.
  • MacFC could give a better overview - further clarifications


Agenda: 2020-09-30

Discussion and agreement about the following proposal:

Discussion

The following aspects are proposed to be decided by the 5G-xhaul subproject.

-          The ForwardingDomain shall be interpreted as a Potential for Forwarding (e.g. SDH Matrix).

[sko] Potential: something which allows the creation of “forwarding” based in the FD:LTP


-          The ForwardingConstruct shall be interpreted as an Actual Forwarding (e.g. Connection between two VC-12 endpoints at the SDH Matrix).

[sko] Actual: configured Forwarding – check operational states and traffic flow


-          There might be 0 .. * ForwardingConstructs inside a ForwardingDomain.

[sko] ok


Discussion on dependencies between LTPs, FD, FC and between the layers will continue...


Agenda: 2020-10-07

  • Last week we started discussing a HUB presentation using FD and FCs: but there are several ways to represent a HUB: Depending on the chosen representation there are different consequences. ... (see attachment: link)

Action items