Nigel DavisMalcolm Betts Provide write up of ClientContext and ServerContext relationship. Update A.15 with this text. Also provide plan for completion of TR-512.A.15 in conjunction with plan for TR-512.8
Nigel Davis Streaming: Security concern. Before attach to the ControlPort, also determine what the client can do. Enforce at the port. Security of content during transferring.
Nigel DavisStreaming: Authenticity of the record (identifies of the creator of the record) RFC5848 (this is just an example of implementation). Both directions (e.g., backpress message from the client, request of replay)
Nigel DavisAgree whether the attributes should be directly in the classes in the streaming model or whether there should be augments (as in TAPI). We could potentially use text to clarify this.
Nigel Davis Need specs for the DSR NEP (has 4 bidirectional ports) and the CEP above it to describe the flow (TR-547-TAPI Reference Implementation Agreement_v2.0_am.docx slide 16)
Nigel DavisTake the spec model, prune out the stuff that are not relevant to simple layer hierarchy, look at how to apply the general principles (slide 32) notation to the stack of layers & rules, write it in the context of the original spec structure. Note that the action "Nigel Davis To prune out the unneeded stuff from the current Spec document so that to show the Yang "when" and "must" of the Occurrence pattern. Action item from2021 Sep 07-10 : OIMT Virtual Face-to-Face" is covered by this action.
Nigel DavisConstruct simple spec example using layer hierarchy modelfor the OTN payload structure, try longhand form, correct number of occurrence set, based on some specific ports. Code it in JSON form of YANG. Note that the action "Nigel DavisLay out the spec model with sufficient occurrence pattern of equipment in it. Relate UML to Yang. Action item from2021 Sep 07-10 : OIMT Virtual Face-to-Face" is superseded by this action.
Malcolm BettsProvide review comments on TR-512.8 streaming, especially focusing on the lifecycle of interaction of client and provider (in section on "Operation of the streams").
Nigel Davis Provide a skeleton document as described in oimt2021.ND.005_OAM.pptx that sets out the rationale for use of existing FC and LTP to represent OAM entities. Note that the action "Nigel Davis Early draft of OAM document using existing model and explaining key features that enable it to be used for OAM, then projecting this model towards a TAPI-like solution. Action item from 2021-09-23 OIMT Meeting notes" is covered by this action.