Due to a ransomware attack, the wiki was reverted to a July 2022 version. . We apologize for the lack of a more recent valid backup.
Child pages
  • 2021-03-18 OIMT Meeting notes




  • Administrative 
  • Review the writeup on multi-point MC restriction/rules
  • Equipment model
  • Control model

Discussion items





5 minAdministrativeKam/Nigel

Daylight Saving Time

Need to arrange virtual face to face meetings.

30 minMulti-point MCMalcolm/Nigel

Malcolm worked through a brief document on multi-point connections (to be uploaded).

Malcolm discussed the formation of unidirectional topologies and the construction of individual source trees for each source node A... etc.

There were no objections from the team to the approach taken.

Nigel explained how the work had first started with the assessment of the trees overlaid a link within a proposed connection to navigate to source and destination clash but that it rapidly became apparent that the ends of the unidirectional trees were the only relevant records as the restricted nature of the structure did not allow for separation of channels once merged.

Nigel noted that the FC overlay may be beneficial when assessing the impact of engineering works on a particular link.

Malcolm explained how the "down stream interference tables" would be used to determine which of a set of connections would be possible.

Nigel showed an alternative representation that was slightly more compact (see  oimt2021.ND.001-MultiPointMcCompactTable.pptx).

Chris pointed out that a bit map encoding might further increase efficiency.

It was agreed that there were various representations all derivable from the FC tree overlay.


Leo presented material on his analysis of the Equipment model

We need objects and attributes that are relevant and information that is likely to be exchanged with meaning and possible values. 

String labels are relevant for humans, but they have no real meaning.

Because we are in the core model, the property should be for broad use.

The equipment model requires a specification but this should be in the equipment model.

The functional properties are borderline (should be in the functional model).

Brief discussion on standardization. 

ONF is bringing many bodies together. We need to avoid the trap of complexity. We need to be pragmatic.

(The media channel model is interesting but the complexity may prevent adoption).

Keeping things simple will aid adoption.

Chris noted that we need to research to help us forward in some areas. 

Different interpretations from different vendors.

Discussed briefly name parsing and interesting data is in the name/value.

Chris noted a danger in pushing the problem to another place.

Nigel noted that understandable simplicity my not be sufficient to reach the inherent complexity of the problem.

Clear use cases are critical.

NVPs are OK for search and sort.

Leo proposed a model with type which seemed similar to spec. There was a brief discussion on this.

Chris discussed this in the context of a catalogue.

Discussed what might be in type. 

Temperature may not be something to be in the core model.

Serial number may cause compatibility challenges.

Leo will submit the slide pack.

Chris pointed out that we had previously propose to change the properties to decoration rather than composition.

1 minNext calls

 Planned agenda items

  • Equipment
  • Control model

 Planned agenda items

  • Multi-point Media Channel finalization

Action items