Welcome to the XOS & NEM Community wiki space. All information on this wiki is publicly accessible. If you would like to contribute to this space, you will need a CORD account: https://opencord.org/registration


XOS brings the Everything-as-a-Service (XaaS) organizing principle to the CORD architecture. In doing so, it addresses several of CORD's high-level design requirements, including a means to seamlessly integrate control plane (SDN) and data plane (NFV) based services; the ability to support both access services and conventional cloud services; support for multiple security domains; and the "end-to-end glue" needed to make CORD both extensible and controllable.

XOS is a central part of NEM (Network Edge Mediator), which plays a role in both SEBA and COMAC. XOS is a stand-alone tool, with other use cases on the horizon (e.g., multi-cloud service mesh).

Read more about XOS and NEM.

Communication Channels

To participate in the XOS project...

We expect all ONF employees, member companies, and participants to abide by our Code of Conduct. If you have any questions or concerns, please notify a member of the ONF team or email conduct@opennetworking.org.

Having trouble getting started? First, reach out to the mailing list or Slack team. If you still have questions or concerns, please email help@opennetworking.org.


Beyond-uServices.pdf (application/pdf)
Model-Driven-Design.pdf (application/pdf)
XOS Modeling-as-a-Service.pdf (application/pdf)
XOS Modeling-as-a-Service.pdf (application/pdf)
XOS Modeling-as-a-Service.pdf (application/pdf)
XOS - Extensible Control Plane.pdf (application/pdf)
XOS - Extensible Control Plane.pdf (application/pdf)
SEBA-Overview.png (image/png)
XOS-Extensible-Control-Plane.pdf (application/pdf)
NEM-Breaking-the-Dilemma.pdf (application/pdf)