Closed jbouqui153 closed 8 months ago
Within the ## 5. More to be added, it could be considered the use case specific for the Coherent pluggable optics:
o ### a. Provisioning of the Coherent pluggable optics and related parameters (e.g. Client Interface Speed, Line Interface Speed, Frequency, FEC, Modulation, Transmitted Power, SFP Identifier or Reference Number, etc.). Different phases of the implementation shall require different actions for setting the parameters either automatically or by user-defined specifications manually. It included the Network Controllers and the MDSC interactions (e.g. P-PNC to Coherent Pluggable, P-PNC / MDSC, etc.). o ### b. Discovery / Visibility of the Coherent pluggable optics and related parameters. The above discovery includes inventory discovery by each controller and exposure to the MDSC of the required information for a complete view of the network. o ### c. Event/fault management of the Coherent pluggable optics and related parameters. o ### d. Performance management of the Coherent pluggable optics and related parameters. o ### e. Reconfiguration management of the Coherent pluggable optics following network changes, faults or and related parameters o ### f. Correlation of coherent pluggable optics with related nodes and services items (e.g., Port/Interface, Board, Node, Services, etc.).
Please find, as promised, an updated input from my side in word format, keeping the base use cases as they are in my Pull Request but adding now sub-use cases for use cases 1, 2, 3. You can add your comments/additional sub use cases directly in the word document by activating change control. Tomorrow we can agree with Oscar and all how to proceed further using github or for moment working on this word input. Thank you. (2024.02.12) Jeff input for use cases in draft-poidt-ccamp-actn-poi-pluggable-usecases-gaps v1.docx
Here is a first draft proposal from Manolo and myself for the use cases section 5 that we can discuss in our next Tuesday call.