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|
(full or 1/2 slot)
|Topic Description||Meeting Notes |
with Document Links
and action items
|Tue 1.1a||KL||25 mins|
Synchronized the work items with the Bubble chart from end of Dec. 2020 vF2F
Review the work plan: Will be reviewed at the Fri 4.2 session
TST and ONF update: None
|30 mins||Getting everyone up to speed on the topic.|
Updates from the previous discussions.
Nigel ran through oimt2021.ND.002_ControlModelAndSecurity.pptx. It presents a sketch of business cycle as a slab of functions. It is provided as a background for the Control Model consideration.
Malcolm ran through oimt2021.MB.003-Control-architecture-outline.pptx (see version 1)
|Wed 2.1||ND||55 mins|
Functional - Config and Readings
Building on previous contribution ONF_T58_Sensor_Model.pptx
Nigel ran through the slides.
|55 mins||Security Direction and Plans|
Malcolm presented further advancements in the work in oimt2021.MB.003-Control-architecture-outline.pptx (see version 2).
Malcolm noted the client context is only put in place when a trusted commercial relationship has been achieved. The environment is relatively closed.
Malcolm noted that the ExposureContext can last for a very long period of time.
Malcolm noted that there are few groups and roles. Chris agreed.
Jonathan asked whether slicing had an effect and increased the number of contexts.
Jonathan suggested that we need to look from the whole network point of view.
Malcolm pointed out that there can be 10s/100s of client contexts. Each client context may have a few roles.
Nigel noted that the client context is relatively small compared to the whole network. Malcolm agreed that if there are 100 slices each would be ~100th of the network.
Malcolm noted that the client context is not formed until there is a commercial trust relationship and negotiation is underway. If the negotiations fail then the client context is deleted.
Malcolm discussed the views that have a mix of real, emulated and planned resources.
Brief discussion on:
Malcolm suggested that an NE may not need a PEP because it is in the operator's private network.
Andrea asked whether each green box represented a database.
Malcolm/Nigel noted that the green boxes represent data storage, cache or read-through.
Chris asked for an expansion of the diagram to show proxy objects. How many proxy objects levels are there? How many levels.
Need to explore the various cases to determine where proxy objects and where there are read only views.
Nigel suggested that it is important to exercise the the diagram with specific cases e.g., of path computation to determine where the PEPs should. There may be several levels of PEPs.
Stephen/Jonathan indicated that they had no objections.
Agreed to cover assignment state followed by security/control in the overflow slot tomorrow.
|Thu 3.1||ND||55 mins|
Focus on Equipment Spec (+ Holder and Connector)
Including use of optional spec pattern
Prior Contributions :
Nigel presented oimt2021.ND.004_Specification.pptx (Simplified Spec). Note that the slides uploaded have been updated as a result of comments made during the call.
Nigel provided the YANG & JSON examples
|Thu 3.2a||MB||25 mins|
Malcolm presented oimt2021.MB.002-Assignment-state-figures.pptx (version 2)
|Thu 3.2b||MB||30 mins|
Chris presented oimt2021.MB.003-Control-architecture-outline-CH.pptx,
Chris presented additional updates/thought on Security/Control.
Nigel provided feedback on Negotiation from implementation
|Fri 4.1a||CH||25 mins||General guiding principles for model design.|
Chris presented OIMT%20Design%20Principles.pptx
|30 mins||Comparison of Termination Point to Interface models. Look at combining the IETF (Interface) and ITU-T (Termination Point) concepts in a meaningful way.||Chris presented Interface%20and%20LTP.pptx|
|Fri 4.2||KL||55 mins|
|Person||Day 1||Day 2||Day 3||Day 4|