-
Notifications
You must be signed in to change notification settings - Fork 79
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
open ROADM OSC detailed requirement #35
Comments
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 , |
This is my understanding: 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 , |
Where we could find more detailed information or requirement about below items? Any source code available for review?
a. Maintenance signal for layer OTS(MW)/OMS()/NMC(Wr) like PMI/BDI/FDI/OCI for fault management
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.
The text was updated successfully, but these errors were encountered: