Child pages
  • 2022-02-24 OIMT Meeting notes

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.






0 minAdminAll

OIMT 2022 Virtual F2F in 2022. 

  • April 19 - 22

LS to SG15 and MEF on the  ONF open github for the TR-512 releases 

  • Sent on February 17 Thursday.
  • Github content to be updated
5 minMEF W130

MEF W130 "Device Physical and Environmental Attributes" draft 0.3 

  • MEF is inviting feedback.
  • It seems related to the OIMT equipment physical/environmental model, temporature, humidity, power supply, length/width/height, etc.
    • Could fit well with Intent and constraint. 
    • Could expand the Location model with the environmental info that the equipment can fit in. 
  • Try to get an ONF OIMT position on this draft, have a proposal to be discussed at the April vF2F meeting.
  •  Chris Hartley Review the MEF W130 draft v0.3 and see if it is worth to provide feedback (via ONF OIMT LS) to MEF.
0  minIntent/Spec grammarND, MS

Discuss the intent grammar, spec grammar. Explore mechanism converting explicit property sentence into constraint statements. (ND)  

  • Operation Interaction Pattern in TR-512.10
  • Discussed the generalization. Related to equipment property spec.
  • Intent-base desire outcome; could be between extreme vague & precise
  • Ltp constraint, property range,
  • Ltp constraints:
    • The grammar of the statement of desired outcome
      • allow folding-away (skipping) middle stuffs
      • the constraint could be vague (range) or precise or "don't care"
  • State the constriant of Intent/DesireOutcome: range or precise
  • MB: Need to understand which side of the negotiation is making the choice: requester or provider; cannot simultaneously.
  • MB: Some characteristics are not optional, probably do not need to state them.
  • There might be recursinon schema
  • Reference of the spec, within which there are a set of values

Conclusion from discussion:

  • Agreed that this is the right direction  
  • To provide some proper examples
  • Need meta data: legal range, is-negotiatable, true-false, 
50  minOccurrenceND

Example for separate occurrence (as per action item) (ND) Deferred to next week

10  minEquipment model ND, KL

Equipment property model sketch (ND, KL) 

  • To decide what need to state in the core model
  • Take Temporature as an example: measureable, controllable, 
  • Want a meta model
  • Same grammar as the intent grammar,
    • not negotiate but specify,
    • design time negotiation, not run-time negotiation
  • Challenge
    • Use schema-like statement
    • Play aroung using YANG JSON like schema
    • Might bend the YANG
    • Add UML stereotype


0  minModel migrationND, MS

Papyrus model migration (for LtpPort) (ND, MS) Deferred to next week

0 minAction item


Action items completed

  • Nigel Davis    Discuss the intent grammar, spec grammar. Explore mechanism converting explicit property sentence into constraint statements.  Action item from 2021-12-02 OIMT Meeting notes
  •  Hing-Kam Lam  Nigel Davis  To rebuild the equipment property model. To change from composite to decorate. Action item from 2021-12-02 OIMT Meeting notes  

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.

 0 minNext calls


  • Example for separate occurrence (as per action item) (ND)
  • Papyrus model migration (for LtpPort) (ND, MS)

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