Open Transport Configuration & Control
Space shortcuts
Expand all   Collapse all
Child pages
  • 2020-06-03 5G-xHaul Meeting notes
Skip to end of metadata
Go to start of metadata

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://onf.zoom.us/j/853336915 -Zoom is blocked by more and more ITs.

Please use the following link: https://thorsten-heinze-telefonica-de.webex.com/join/andreas.lattoch.external 

Attendees

(please feel free to correct, 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-06-03: Martin Skorupski

2020-06-10: Martin Skorupski

2020-06-17: Martin Skorupski

2020-06-24: Martin Skorupski

00:01RadioSignalIDThorsten HeinzeProposal:

Need for parallel configuration of transmitted-radio-signal-id and expected-radio-signal-id shall be avoided for simplifying configuration processes.

So in case AirInterfaceCapability::expectedEqualsTransmittedRadioSignalID==true, the AirInterfaceConfiguration:: expectedRadioSignalID shall be implemented like an unsupported attribute (always sticks with its default value).

This means

  • AirInterfaceConfiguration:: expectedRadioSignalID::numericRadioSignalID=-1 and AirInterfaceConfiguration:: expectedRadioSignalID::alphanumericRadioSignalID=”Not yet defined.”
  • any attempt to configure expectedRadioSignalID shall be answered with error-tag "operation-failed" and error-message phrase "#[onf:Attribute/feature not supported by the hardware.]#".


The following changes have to be made on the modeling:

  • numericRadioSignalID datatype has to change from uint16 to int32
  • numericRadioSignalID default value has to change from 0 to -1
  • numericRadioSignalID comment to be complemented with “-1 = to be used, if numericRadioSignalID is not supported or for expectedRadioSignalID, if it has to equal transmittedRadioSignalID.”
  • alphanumericRadioSignalID comment to be complemented with “Not yet defined. = to be used, if alphanumericRadioSignalID is not supported or for expectedRadioSignalID, if it has to equal transmittedRadioSignalID.”
  • AirInterfaceConfiguration::expectedRadioSignalID comment to be complemented with “Only relevant, if expectedEqualsTransmittedRadioSignalID==false.”.


Decision: as proposed above. 



00:11

TransmitterEquipment

Pawel Krecick
Thorsten Heinze

Proposal to align modeling of AirEquipment with WireEquipment

(follow link to see the email)

A new document is available: https://github.com/openBackhaul/equipment/tree/tsp

under review 2020-05-27

AI all: please provide feedback in advance in written form using the change tracker. Please send beck to Thorsten by email - and cc the group.


Feedback from 3 companies - Thanks!!!

Updated document will be delivered by Thorsten.


Review session on the agenda for 2020-06-10.

00:16VLANThorsten Heinze

VLAN Model with reduced scope. 

review period for documents from last August will end 2020-06-09


00:25dropping-behavior

Thorsten Heinze

dropping-behavior-kind on device/switch level - link to issue

AI: Danilo Pala, Michael BinderDaniela Spreafico: Please provide options how to solve the issue and a recommendation for discussion next week. 

AI: Martin SkorupskiWork out a proposal to be discussed next week. 


based on the proposal made in the issue:

Proposal:
The dropping-behavior-kind shall become part of a Profile,

  • which can be instantiated multiple times, in case the device allows independently adjusting the dropping-behavior-kind per interface,
  • or just a single time, in case the device allows adjusting the dropping-behavior-kind just on device/switch level.


further details should be agreed. 

  1. A new profile type should be created, called "PROFILE_NAME_TYPE_DROPPING_PROFILE
  2. The profile details are just extensible ENUM (yang: identity) similar like "dropping-behavior-kind-type"
  3. ethernet-container-capability: available-dropping-behavior-kind-list will be of type "identity-ref" to the PROFILE_NAME_TYPE_DROPPING_PROFILE
  4. ethernet-container-configuration: dropping-behavior-kind will be of type be of type "identity-ref" an entry in  ethernet-container-capability/available-dropping-behavior-kind-list
  5. The pointers from ethernet-container-capability and ethernet-container-configuration allow the following use cases
    1. The EthernetSwitch (FD) allows only one Profile, all capabilities and all configuration are "static" because only one Profile exists. Any dynamic configuration happens in the Profile itself.
    2. Several Profiles with different configuration/behavior exists - ("static profiles"). Any configuration happens only by switching the profile.
    3. a combination of a) and b), which is not recommended due to unnecessary complexity.


Conclusion during the discussion:

  • investigate in
    • adding another ethernet-container-capability attribute to express, if the LTP
      • can,
      • must,
      • must-not follow the configuration on device (forwarding-domain?) level
    • creating a device (forwarding-domain) PAC to uml:specify (yang:augment) ETH-Switch capabilities and configuration
  • Further discussion on agenda for 2020-06-10.
00:00ComboPort

Roberto Servadio

See contributions:

Switching the port by management interface → CoreModel solution is ForwardingConstruct with FC-Switch.

AI: Martin SkorupskiShow how this works with CoreModel 1.4


END


0minUUID

Status: discussion on-hold

core-model allows definition of both Logical Termination Points (interfaces), but also connections

  • Forwarding Domain:
    • either connection inside the same device
    • connections outside devices
  • Link:
    • any type of link, not only microwave
  • Forwarding Construct:
    • concrete forwarding between two or more LTPs / ports
      • unidirectional / bidirectional

core-model is also suitable for representing entire Networks, not only a Device

this means that Universally Unique IDs are required

Devices cannot get the UUIDs from outside, they need to be generated by the device, and cannot be overwritten from outside

Devices are unaware by their surroundings (the network), so it cannot know if a UUID is already used by some other interface in other devices

IETF defines how to create UUIDs, and the core-model references this RFC

  • we need UUIDs for documenting the network
  • we cannot write the UUIDs in the device, the device needs to create it 
  • the device does not have a network wide view
  • this is needed because of the Planning the network

Possible solutions:

  • the device generates whatever, the IDs are retrieved and a mapping table is maintained
  • we prescribe a method/algorithm that is implemented in the device for creating UUIDs (which become predictable):
    • using some prefix which is known during the implementation time of the device - (e.g. MAC address of the Management interface); vendor sends info about Order no. and MAC addr. to the operator and the Planning will be done with these prefixed values → less complex than a field technician configuring the prefix on the device with some dongle
    • fixed UUID with prefix and postfix

Suggestions:

  • use the Device name instead of the MAC addr.
  • clean-up application that handles the changing of MAC addresses

Out of time, we need to follow up: proposal, next week Tuesday 09:00 CET

--

Notes from  

Discussion about UUID and Links/Asszosations/References between object classes

ODL MountPoint is and association to a NetConf server - some NetConf servers representing some times the microwave model.


Action items