Open Infinera-OR opened 5 years ago
The optical specification would be the master for OSC interop.
the 100M Ethernet is not supported as there is still an issue with laser safety/shutdown.
There isn't any dedicated messaging for ROADM-ROADM communication. No ROADM-ROADM has been specified or required.
MCN management is simply IP/Ethernet. L2 bridging and RSTP is the DCN solution.
No need to support 802.1Q tag on OAMP interface (at least not today). No 802.1Q tag on OSC either.
@fgruman , Thanks a lot for the comments! So without ROADM-ROADM communication via OSC channel, how is the consequent action and correlation being supported on layer OTS(MW)/OSC/NMC(Wr), like without PMI/BDI/FDI/OCI being defined on the corresponding layers, normally when there is OTS loss, BDI will be inserted back to the paired remote site and FDI to the down stream per G.798. Is this supported now on open ROADM via the centralized SDN controller which is aware of the whole network status? I mean the controller collect the status, and distribute it to different nodes that have MW interface interconnection?
This is my understanding: The correlation is expected to be done at the controller level or higher.
Consequent action would be a transponder function based on LOS at the OCH/OTSI interface.
there is nothing in the Yang models to have the controller distribute the status to the downstream nodes. Nodes would have to operate without this information.
@fgruman , Really appreciate for your help!
Where we could find more detailed information or requirement about below items? Any source code available for review?
b. Dedicated laser safety message c. MCN management message We want to know if similar message format defined for openROADM this time, like other standards (i.e SyncE or IEEE1588) did in the past, or unified RPC message, to make sure the interoperation with third party equipment.