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.
Open Information Model & Tooling

Space shortcuts

Expand all   Collapse all
Child pages
  • 2021-01-21 OIMT Meeting notes

Date

Attendees

Agenda

  • Administrative
  • Media Channel: Multi-source/destination Media channel representation
  • Core control model (CD & Exposure Context)

Discussion items

Time

Item

Who

Notes

IM-D


AdministrativeAll

Time of OIMT call 

  • Change to 0630 - 0730 Eastern Time, at least until mid April 

Media Channel

Nigel

Multi-pointed Media Channels: Multi-source multi-destination

  • TR-512.A.4 Figure 4-28
    •  Representation of topology and frequency slot occupancy
  • Agree to use the Bidirectional overlay trees approach to tackle the issue
    • Nigel Davis Start to draw simple single tree, find minimal forms, then draw the overlay tree, then use in both TAPI and Core 

  • Effective spectrum
Control modelKam

Clarification on the control model needed by ITU-T Q14/15

  • Clarification from the 2020.12.10 discussion on ExposureContext (EC), ConstriantDomain (CD), ControlConstruct (CC), ControlPort (CP)
    • The relationship among EC, CP, and CD:  
      • The client talks to EC through CP about CD.
    • EC: The "How". The gateway/agent for accessing. It defines the rule/requirement of accessing.
    • CD: The "What". The thing to be viewed by the client in the CPI (control plane interface)
    • CC/CP: The "Where". The interface port to access the CE.
    • In the current v1.4 UML, the ControlConstructExposesExposureContext association should be ControlConstructAccessesExposureContext    
    • One Vmf can provide multiple views from the same set of resource.
    • An ExposureContext can only expose one highest level (most outer) ConstraintDomain,
  • Additional clarification on 2021.01.21
    • The model allows access to multiple ExposureContext from a single ControlPort. For example, to support multiple users/applications at the same CPI (control plane interface) ControlPort.
    • Consideration of multiple ControlPort vs multiple ExposureContext
      • High-level security control and coarse grain operation control are set at the ControlPort. 
        • Additional ControlPort instances could be instantiated to meet different security requirements or operation previlage. 
      • Fine grain control (e.g., at object/attribute level) are set at the ExposureContext 
  • Additional clarification for TR-512.8 is needed.
    • Lifecycle of EC and its dependency on CD
    • Additional associations 
    • Multiplicity
  • Start up bootstrap:
    • CD representing the controller
      • Then administrator create ....
Next calls

 : 

Action items

  •