Child pages
  • 2020-12-17 OIMT Meeting notes
Skip to end of metadata
Go to start of metadata

Date

Attendees

Agenda

  • Administrative
  • Virtual meeting action items work plan
  • Using the Core model 
  • Media Channel (TR512.A.4 Fig. 4-28 & effective spectrum)
  • Core control model (CD & ExposureContext)

Discussion items

Time

Item

Who

Notes

IM-D


AdministrativeAll

Year end call plan

  • Dec. 24: Skip
  • Dec. 31: Skip
  • Jan. 7:
vMeeting action itemsAll

2020 30 Nov & 2-4 Dec: OIMT Virtual Face-to-Face

  • Names of task owner have been added

Using the Core model 

Leo

Leo shared

  • Mekator Network Mining solution
  • Rationale of our engagement 
  • Why Core Model, and not TAPI
  • Simple reference network:  WDM D/Mux
  • Link
  • ForwardingConstruct
  • ForwardingDomain
  • LogicalTerminationPoint
  • LayerProtocol
  • LayerProtocolNameAndQualifier
  • Further objectives - Type Libraries
  • Implementation model to core model mapping
  • Inventory project
  • Use case: incident simulation
  • Reference data set for the core model

ND: oimt2020.ND.013-ComponentPortAndAggregates.pptx on the Contributions wiki page:

AM: https://github.com/OpenNetworkingFoundation/TAPI/releases/tag/v2.1.3

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
  • Effective spectrum
Control modelKam

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

  • Background
    • G.7701 "Common control aspects "
    • G.7718 "Framework for the management of MC components and functions"
    • G.7719 (Draft) "Management information model for MC components and functions"
  • Two different interpretations/understandings/proposals of the ExposureContext object class within q14/15 for the G.7719 model
    1. Use ExposureContext to model the client/server/administrative contexts. 
      • See 2020-12-10 OIMT Meeting notes last week minutes for details
        • ExposureContext (EC) defiines the rules (requirements) of exposing/accessing stuff
        • EC itself is not exposed across the CPI. It is the contained CD being exposed.  
        • Base on TR-512.8 Figure 3-13 
    2. The exposure (things being exposed) is modeled by an ExposureContext.
      • See 2020-12-10 OIMT Meeting notes last week minutes for details
        • ExposureContext is visible across the CPI.
        • Based on the ControlConstructExposesExposureContext associsation
  • Clarification is needed.
  • Clarification from the 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 for TR-512.8 is needed.
    • Usage of EC
    • Lifecycle of EC and its dependency on CD
    • Additional associations 
    • Multiplicity
  • Start up bootstrap:
    • CD representing the controller
      • Then administrator create ....
Next calls

 : (1) Multi-source/destination Media channel representation, (2) Control model

Action items

  •