
Deliverables
The purpose of these documents is to define the technical requirements for an open and disaggregated aggregation router (DAR) solution that operators can deploy in their backhaul transport networks. It describes the required hardware and proposes non-mutually exclusive software packages for the support of additional services or functionalities.
This document represents the technical requirements for a distributed and disaggregated PE router (DDBR-PE) that operators can deploy in current and future networks for the provision of backbone services. It describes the required hardware and proposes non-mutually exclusive software packages for the support of additional services or functionalities.
The purpose of these documents is to describe a set of technical requirements and recommendations for:
1. A shift in the IP backbone architecture from monolithic chassis-based, to a disaggregated Spine & Leaf architecture
2. Describes the technical aspects of a Distributed Disaggregated Backbone Routers (DDBR) which is a versatile architecture that can be deployed in IP core/backbone networks, to fullfil different IP transport use cases (P, PE, Internal-gateway).
The purpose of these documents is to describe a set of guidelines and recommendations for a standard use of the SDN Northbound interface (NBI) of the Optical SDN domain controller for the implementation of the interface between network systems in charge of the control/management of networks based on WDM/OTN technologies.
The NBI of the SDN Domain controller entity (e.g., a SDN-C) is intended to expose the management/control capabilities of any use case such as activation/configuration, service provisioning, path-computation, fault management and monitoring over a WDM/OTN network.
These new deliverable set covers the base requirements for a new version of MUST Optical SDN Controller Northbound Interface solution based on Transport API (TAPI) version 2.5.x. The reason for this new major revision of the requirements is the transition of TAPI versions from 2.1.3+ to 2.5.0+ is not backward compatible. Thus this new version of the Optical SDN Controller NBI requirements intends to cover new management/control capabilities enabled by recent TAPI versions such as TAPI Streaming and Fault Management.
MUST Use Cases and Technical Requirements for Wireless Backhaul SDN Domain Controller & Network Equipment
Currently wireless networks are operated through vendor Network Management Systems (NMS) using proprietary interfaces. Operations and configuration/maintenance activities are performed manually and statically.
This adds complexity toward the higher-level applications and OSS systems that need to manage many proprietary interfaces. In the case of Microwave (MW) networks, these scale upward to non-reasonable levels due to technical complexity.
TIP Greenlight addresses these issues by the application of common and standards-based technologies:
This first release of TIP Greenlight focuses on the initial deployment of network elements with disaggregated hardware (e.g. a router or a transponder) and software components (“disaggregated devices”)
Future iterations of TIP Greenlight will build upon the flexible and extensible mechanisms contained in this document to deliver additional use cases.
IPoDWDM-capable routers’ coherent pluggable integration and management.
This Use Cases Definition document extends the current MANTRA Whitepaper: IPoWDM convergent SDN architecture – Motivation, technical definition & challenges with an extended description of the target applicability scenarios and use cases targeted by the TIP OOPT MANTRA operators subgroup.
The purpose of describing the optical planning use cases is to provide a base for reviewing how the function of online optical planning should be incorporated into the TIP MUST Open Transport SDN Architecture. The scope of the optical planning is to plan the properties of Open-Optical Networks O-ON with its O-OLS (Open-Optical Line System) and connected O-OLI (Open Optical Line Interfaces). To prepare a proposal for implementation of the use case functionality, all necessary topics of relevance should be reviewed. In section 4, input is given for consideration on a solution, however this is not a complete description but the first set of important topics shared by the operators. Any other topics of relevance have to be identified during the continuing work.
