6:00 am - 6:55 am EDT
7:05 am - 8:00 am EDT
In general we need to focus on agreement and actions :
Assigned to Slot
a or b for 1/2 slot
|Topic Title||Lead||Length requested||Topic Description||Meeting Notes |
with Document Links
and action items
|Tue 1.1a||Admin, welcome, 2021 Work Plan||KL||25 mins||OIMT work plan review and update|
The March 2022 date for v1.6 will be changed. Come back on Friday. Will identify stuffs to be focused on in the next 6 month.
|ND||25 mins||To discuss further progress on the streaming model and other related information flow modeling.|
Task 65 Streaming
oimt2022.ND.002_ControllerStreaming.pptx (verson 1) was presented.
Look at the content of the stream and the stream reception, not just the source of the stream.
Slide 2 (Stream source - the send part)
Side 3 (Clarifications - stream source)
Slide 4 (Stream sink - the receive part)
Due to lack of time, the remaining slides will be covered in the Thursday Overflow session
Note: oimt2022.ND.002_ControllerStreaming.pptx Versions 2 and 3 were posted after the session. Version will be used in the Thursday overflow session (Thu3.2).
|CH / ND||55 mins|
(Encapsulation 2.0 /
Reduced coupling), including refactoring
Task 64 DDD Aggregate
General discussion on use of aggregates to reduce coupling.
Discussion on above.
Chris presented Advanced DDD Aggregate
Chris presented DDD Aggregates Refactoring
Due to lack of time Nigel talked briefly without presenting any slides (slides will be refined and presented during the Overflow session).
Draft TR-512.A.15 - Zero Trust Controller
Task 78 Controller zero-trust hardening
Stephen presented oimt2022.SS-MB.001-TR512-A.15.docx, which contains further mark-up on top of the document that was liaised to OIMT from ITU-T SG15 Q12 & Q14 on 2022-03-22 that contains SG15's questions, comments, and suggested edits to the OIMT early draft of TR-512.A.15 (Controller Lifecycle and Security). As noted at the beginning of the marked up, the feedback addresses the entity relationships of service, agent, and client, but does not develop the issue of compute and storage resources. The issue of the controlling entity for links between server contexts or controllers is not addressed. Commonalities with ITU-T Recommendation G.7716 (draft) are not explored but the issue is raised in section 5.2.1.
NOTE: In the marked-up document, the main section numbers have dropped by 1 as compared to the original liaised draft.
Stephen went through the feedback.
ND: What is our plan to proceed this?
Malcolm presented oimt2022.MB.001-control loop sketch.pptx
|ND||55 mins||To discuss the Job/Task model and modeling of OAM|
Task 69 Job/Task (and Task 5 & 57?)
ND presented from oimt2021.ND.005_OAM.pptx
Building on previous work oimt2021.ND.005_OAM.pptx and discussing the latest updates (version 3) focusing on the task aspect.
OAM model MEG/MEP/MIP
ND summarized the tentative agreement. There were no objections. The items noted in the slides can be considered as agreements.
Note that CH pointed to an example of a new workflow engine - Kestra: a Scalable Open-Source Orchestration and Scheduling Platform https://www.infoq.com/news/2022/03/kestra-orchestration-platform/
ND went through basic observation on a task linking the task to intent and outcome. An outcome can be ongoing/continuous, periodic, one-off/instantaneous etc.
Need to consider the trigger of a task.
CH: The terminology in this space is messy, there are no clear definitions.
ND: So we need to have some clean terminology that we use.
AM: There is a target configuration. The task is a composition of activities working on a target.
ND: Using Outcome for the target configuration where this may be complex and changing.
AM: related to MB diagrams and a hierarchy/arrangement of target configurations. It is intertwined. Task is also for use case.
ND: As task is an activity that may lead to another activity.
AM: Noted the control loop is a task.
ND: The control loop is a task and there is control of control.
AM: There is a continuum
ND: The terminology is relative. We need to right statements of relativity. We need to tease apart the problem to get to a terminology set that is stable and usable
CH: Suggested that a task is not ongoing and workflow is longer lived.
MB: Not sure if that is true. Think about network configuration. The entity that is observing for differences is ongoing.
CH: Emphasized the challenge of terminology.
ND: The terminology needs to be fractal and relative.
CH: Kestra is a good example. Try to make the tasks small and reusable within a workflow. You need to start with something Atomic.
ND: Atomic is a problem... An atom is not atomic.
ND: I have not tried to tackle the definitions yet.
CH: All the workflows seem to have similar concepts. In the abstract, fractals are OK, but we need something implementable
ND: Well, actually in the core, we need to get the patterns right, we try to describe the problem space in the core. We do not implement the core directly (other than wireless), we refactor, e.g., in TAPI.
ND: Using the term Task here as all words have a problem.
ND: Discussed results, intermediate results,
ND: All functions (Tasks) have some flow through. Can control the flow. Can apply variable resources. Any function (Task) is constrained by an encompassing definition and It can be further constrained. E.g., Path Computation function is constrained to computed paths but any paths, so for it to do something useful it needs constraints (the topology, the specific ends etc.).
AM: Generic pattern in the core is fine but need more concrete consideration on atomic and composition. We have an implementation of a management interface. There appears to be a practical definition of "atomic" operations. There is a need to put together these atomic things into useful overall activities (use cases).
ND: Agreed with an implementation pitch that enables understanding. Human terminology enables implementation (even if the machines do not need it).
Discussion on abstraction of control and a control hierarchy. Atomic in the context at a moment.
CH: Cannot afford to make it too complex.
ND: Component-System is not complex. It is overly simple.
CH: Offered to show Kestra.
ND: Agreed, but concluded first.
AM: This looks like a use case.
ND: Yes, but artificial boundaries are a problem.
ND: Trying to pull out the common pattern. We can then refactor it in different concepts.
MB: Agreed with the general challenge and that we need to identify the pattern.
Editor's note: The challenge is terminology.
ND: Brief discussion on the Intent Task diagram.
CH: Walked through Kestra definitions (the screen shot below is from publicly available Kestra documentation).
ND: General definition of Task with specializations.
ND: Isn't a Task realizable by a subordinate Flow?
ND: Fractals bend away but there is a sweet spot of several levels.
CH: Indicated that the simple definitions help.
MB: Provided an example of recursive tasks Path Computation is a Task from the "create a connection" perspective, but Path Computation is itself formed from flows.
CH: Lots of implementations out there and all have similar concepts and definitions.
|To discuss progressing the spec model with a focus on the expression of spec properties using the sketched JSON form of Yang.|
Task 37 Spec re-work
Building on previous work (using updated version of oimt2021.ND.004_Specification.pptx (version 4) considering slides 30 to end).
|Thu 3.2||--Overflow--||--||55 mins|
Task 5 Streaming (using updated version of oimt2022.ND.002_ControllerStreaming.pptx (version 3)):
Task 64 Aggregates (using updated version of oimt2022.ND.004_ComponentPort.pptx (version 3)):
|Fri 4.1a||Temporal expression draft (instance examples)||ND||20 mins||To discuss and agree the approach for modeling of temporal expression|
Task 73 Temporal expression
Augmentation focused or subclass focused.
Discussion: To decision whether to use the subclassing form
Task 64 Aggregates
(rough notes following... to be completed)
OAM (slides 14, 15 and 16 of oimt2021.ND.005_OAM.pptx (version 4))
Service Context - to cover in future
Release plan for 1.6+ part 3
|55 mins||Review and Update the work items, document list, and release plan (Bubble chart)|