Child pages
  • 2020-08-27 OIMT Meeting notes
Skip to end of metadata
Go to start of metadata

Date

Attendees

Apology

Agenda

  • Administrative
  • MEF Liaison
  • Spec Occurrence model 

Discussion items

Time

Item

Who

Notesm

IM-D


AdministrativeAll

ITU-T SG15 plenary meeting on 7 - 18 September 2020, at 13:00 - 17:00 Geneva time daily.

  • Amd.1 of G.807 (media architecture) and Amd.1 of G.872 (OTN architecture) will be for consent (initial step of the approval process) in this SG15 meeting.
  • Several OIMT regular participants will be in the SG15 meeting and not available for the Sept. 10th & 17th OIMT calls.

In the OIMT call next week, will provide a heads up on ITU-T SG15 September meeting key topics that are of interests to ONF OIMT & OTCC

MEF Liaison

 All

Incoming LS from MEF (LS00312_002) on Network Slicing

  • Informing its draft standards MEF 84 Network Slicing, which is in CFC stage
  • Should provide any comment soon, within 2 weeks if possible. 
  • This standard specifies Network Slicing in the context of MEF Lifecycle Service Orchestration (LSO) and MEF Services. Key concepts of
    Network Slicing, Network Slices and Network Services are described. Network Services as defined in this Standard enables Service
    Providers to offer Network Slices in the Service Provider domain as Services to Subscribers in the Customer domain.
  • MEF Draft Standards are available at: http://www.mef.net/draft-standards

The discussion noted that the status of the Draft MEF 84 (R1) is not clear from the liaison statement., specifically regarding the cut-off date for comments.

Brief look at sections 6 & 7 of the draft. Some concerns raised

  • The network slicing concepts and examples in section 6.1. Missing the link end aspects.
  • Management requirements section 6.4 ar very shallow. 
  • Section 7.1 Figure 2. Seems missing the administrative aspects.
  • Will also cc the response LS to SG15 
Occurrence modelNigel

Nigel explained the thoughts & rationale behind the Spec Occurrence model

  • Examples of occurrence model:
    • ChassesSpec, SlotSpec, & ModuleSpec are occurrences of EquipmentSpec (see Figure 5 below)
    • OtnLtpSpec & EthLtpSpec are occurrences of LtpSpec
  • Class points to Spec
    • Examples:
      • Class1DefinedBySpec (see diagram below)
      • LtpDefinedByLtpSpec (exists in the Core model)
        • This association direction should not be confused with the direction of the《Specify》stereotype , in which the Spec class specifies (decorates) the base class and is mapped to the augment statement in YANG.
  • The Occurrence model is a knowledge layer model
  • Distinction of instance vs occurrence
    • Comment raised: Is Spec Occurrence = Instance of Spec?
      • I.e., Instance in the meta class model?

  • Will have follow up discussion
Next calls

Action items

  •