Due to a ransomware attack, the wiki was reverted to a July 2022 version. . We apologize for the lack of a more recent valid backup.
...
The MDSC istheonly building block of thearchitecture that is a
ble to implement all the four ACTN main functionalities, i.e. multi
domain coordination function, virtualization/abstraction function,
customer mapping function and virtual service coordination. The key
point of the MDSC and the whole ACTN framework is detaching the
network and service control from underlying technology and help
customer express the network as desired by business needs. The MDSC
envelopes the instantiation of right technology and network control
to meet business criteria. In essence it controls and manages the
primitives to achieve functionalities as desired by CNC
A hierarchy of MDSCs can be foreseen for scalability and
administrative choices. In order to allow for a hierarchy of MDSC,
the interface between the parent MDSC and a child MDSC must be theth
e same as the interface between the MDSC and the PNC. This does not
introduce any complexity as it is transparent from the perspective
of the CNCs and the PNCs and it makes use of the same interface
model and its primitives as the CMI and MPI.
A key requirement for allowing recursion of MDSCs is that a single
interface needs to be defined both for the north and the south
bounds. In order to allow for multi-domain coordination a
1:N relationship must be allowed between MDSCs and between MDSCs and PNCs
(i.e. 1 parent MDSC and N child MDSC or 1 MDSC and N PNCs)
. In addition to that it could be possible to have also a M:1 relationship
between MDSC and PNC to allow for network resource partitioning/
sharing among different customers not necessarily connected to the
same MDSC (e.g. different service providers).
Physical Network Controller
The The Physical Network Controller is the one in charge of configuring the
the network elements, monitoring the physical topology of the network
network and passing it, eitherraw either raw or abstracted, to the MDS
CMDSC.
The
The PNC, in addition to being in charge of controlling the physical network
network, is able to implement two of the four ACTN main functionalities
functionalities: multi domain coordination function and virtualization
virtualization/abstraction function
A A hierarchy of PNCs can be foreseen for scalability and administrative
administrative choices.
ImplementingACTNinONOS
via PCEP
Supporting VN operations in PCEP for ACTN
via Yang (RestConf / gRPC etc)
- Generic Info Model for ACTN - https://datatracker.ietf.org/doc/draft-leebelotti-teas-actn-info/
- TE Topology based Topologybased on https://datatracker.ietf.org/doc/draft-ietf-teas-yang-te-topo/
- TE Tunnel based on https://datatracker.ietf.org/doc/draft-ietf-teas-yang-te/
- ACTN extention are needed to extendtoextend/augemnt the above models
The Physical Network Controller is the one in charge of configuring the network elements, monitoring the physical topology of the network and passing it, either raw or abstracted, to the MDSC.
The PNC, in addition to being in charge of controlling the physical network, is able to implement two of the four ACTN main functionalities: multi domain coordination function and virtualization/abstraction function A hierarchy of PNCs can be foreseen for scalability and administrative choices.