Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Architecture, Semantic and Behavior

Date

7am PDT | 10am EDT | 14:00 UTC | 16:00 CEST | 17:00 EEST | 19:30 IST | 22:00 CST | 23:00 JST |


Web Conference:

Please use the following link: https://thorsten-heinze-telefonica-de.webex.com/thorsten-heinze-telefonica-de/j.php?MTID=maf8277c6d77a05591e22f736ba1061c6  

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-05-06: Martin Skorupski

2020-05-13: Martin Skorupski

2020-05-20: Martin Skorupski

2020-05-27: Martin Skorupski

00:00

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

AI: Danilo PalaMichael Binder Daniela Spreafico: Please provide options how to solve the issue and a recommendation for discussion next week. 

We think there are more attributes.

On the agenda for tomorrow. 

00:00
Thorsten Heinze

Default value for header-compression-name - link to issue

Discussed and decided - please see link

00:00
Roberto Servadio

radio-signal-id: proposal of simplification - link to issue

Answer: ??? to be discussed

00:00
Alex Stancu

pyang warning for must statement - link to issue

Discussion:

Decision:

01:11ValidationThorsten Heinze

Info:

  • Profiles are now part of the interface validation.
  • Preferred for next implementations: error-messages. 




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


  • No labels