Child pages
  • 2022-02-10 OIMT Meeting notes
Skip to end of metadata
Go to start of metadata

Date

Attendees

Agenda

  • Admin: vF2f dates, draft LS 
  • Action item status
  • Temporal model updates (ND, CH)
  • Challenge of LTP/LP Spec pattern (ND, IB, KL)
  • Update on refactoring of Casc for DDD Aggregate work (ND)
  • TAPI and Wireless transport: Moving away from simple packaging (ND, AM, MS) Deferred to next week due to running out of time. 
  • Discuss the intent grammar, spec grammar. Explore mechanism converting explicit property sentence into constraint statements. (ND) Deferred to next week due to running out of time.
  • Equipment property model sketch (KL, ND) Deferred to next week due to running out of time.
  • Example for separate occurrence (as per action item) and update on modeling of occurrence (ND) Deferred to next week due to running out of time.
  • AOB

Discussion items

Time

Item

Who

Notes

10 minAdminAll

OIMT 2022 Virtual F2F in 2022. 

Draft LS to SG15 and MEF on the  ONF open github https://github.com/OpenNetworkingFoundation/CoreInfoModel for the TR-512 releases 

5 minAction itemsAll

Actions

Action items completed


Action items re-dated 

The following are proposed dates for the past actions. The action list has been updated to reflect this. The actions can be reverted/adjusted as necessary. Only actions that have been moved are listed.

Note that now provided in the bullet under each action item is the link to the source minutes that created the action item.

15 minLTP/LP SpecND, IB, KL

Challenge of LTP/LP Spec pattern

  • Q14/15 is investigating how to refactor the LTP and LP object classes for the configurations in G.875 (https://www.itu.int/md/T17-SG15-211206-TD-WP3-0842/en) Figures I.2, I.7, and I.11
    • Figure I.2/G.875
      • According to TR-512 Core model (G.7711), this configuration can be modeled with one LTP instance which contains two LP instances (ordered): one LP instance with lpName=ODU and one LP instance with lpName=ODU_TCM
      • In G.875, it is considering to model this configuration as
        • One OduCtp instance (refactored from LTP and LP (lpName=ODU)), which contains
        • One OduTcm instance (refactored from LP (lpName=ODU_TCM)
    • Same approach for the configurations in Figure 1.7 and Figure I.11
    • A question is how to model the order of the auxiliary obect instances (TCM, GCC, NIM) in UML.
      • In the current G.875, there is the attribute positionSequence in the containing TP (OduCtp or OduTtp) which is an ordered list of pointers, in addtion to un-ordered associations.  
    • We could consider using an Intermediate class XYZ
      •  
        • The OduCtp (or OduTtp) is refactored from LTP and LP (with lpName=ODU)  
        • The OduCtp (or OduTtp) ccontains ordered instances of XYZ, which is either OduTcm, or Gcc12Tp, or OduNim.
          • OduTcm, or Gcc12Tp, and OduNim are refactored from LP with the respective lpName=ODU_TCM, or GCC12TP or ODU_NIM respectively.
      • The details need to be worked out, in particular the order of the auxiliary instances.

Post call consideration (IB and KL)

  • Considered also section 7.6/TR-514 (Modeling Guidelines) v1.3.04
  • Reached the following 
    • Where, the LtpIncludesLayerProtocols association (with ordered navigable-end _lp 1..*) between LTP and LP is refactored into the OduCtpIncludesOduAux association between OduCtp and OduAux.
      • The ordered navigable-end _lp points to the auxiliary instances, which could be OduTcm, Gcc12Tp, and/or OduNim according to the configuration. 
10  minTemporal expressionND, CH

Temporal expression model updates (ND, CH)

  • Updates made
    • DaysOfWeekInMonthInYearTe now merges DaysOfWeekTe, DayInMonthTe and RangeEachYearTe.
    • TeElement is specified/augmented by BoundingPeriodTe, DaysOfWeekInMonthInYearTe, ParticularDateTimePeriodTe and IteratveTe, instead of composite.

    • Will further work on PhasedPeriodTe. May make it into augment.
    • Will make a picture with Chris.
20 minRefactoring of CascND

Update on refactoring of Casc for DDD Aggregate work (ND)

  • CH noted that he has been investigating the Advaned aggregate approach and its pros and cons. Will nail down in the F2F meeting.
  • ND 
    • Showed the draft model that was presented last week, in which the three Red associations need to be worked on and checked against exmple complicate use cases.
    • Has looked at the example in Figure 3-15 of TR-512.A.11
      •    
        • Noted the internal relationship among the CASCs of the FC. 
        • Note the restrictions of the AggregateBetween and AggregateWithin association w.r.t. AggRoot and AggLeaf.
      • Has changed the <AggRoot> Casc class to <AggRoot> CascCoordinator class.
0  minTAPI and Wireless transportND, AM, MS

TAPI and Wireless transport: Moving away from simple packaging (ND, AM, MS) Deferred to next week due to running out of time. 

0  minEquipment model KL, ND

Equipment property model sketch (KL, ND) Deferred to next week due to running out of time. 

0  minIntent/Spec grammarND

Discuss the intent grammar, spec grammar. Explore mechanism converting explicit property sentence into constraint statements. (ND) Deferred to next week due to running out of time. 

0  minOccurrenceND

Example for separate occurrence (as per action item) (ND) Deferred to next week due to running out of time. 

 0 minNext calls

 

  • Admin: vF2f dates, LS 
  • TAPI and Wireless transport: Moving away from simple packaging (ND, AM, MS) 
  • Discuss the intent grammar, spec grammar. Explore mechanism converting explicit property sentence into constraint statements. (ND) 
  • Equipment property model sketch (KL, ND) If time allowed
  • Example for separate occurrence (as per action item) and update on modeling of occurrence (ND) If time allowed

Future calls agenda items

  • TIP/MUST papers (CH, ND)
  • Catalog / inventory storage application (CH, ND)
  • MEF W130 device physical & environmental specification. OIMT may need to engage MEF on that. (CH)
  • IETF work on physical inventory model (ND)
  • RBAC vs ABAC (June 2021 F2F meeting Tue 1.2 ) 
  • Finalize the write up on Multi-point Media Channel (later call) (Candidate for v1.6)
  • To recap the previous OIMT discussion on synchronization management IM (later call)
  • YANG augmenting 
  • Leo on location model

Action items

  •