## 3 Architecture Proposed
### Management DAF  
The network management DAF is composed of several application processes that enable management characteristics in RINA nodes or RINA systems. In this case, the application processes are the MAs implemented in each RINA system and the RINA manager implemented in the SDN controller. Figure 4 shows the management DAF composed of the MAs and the RINA manager.  
The MAs are in charge of running one or more IPCPs for implementing one or more DIFs. To do so, the MAs have read and write permissions to operate over the IPCPs' RIB. In this case, the MAs can operate over the management DIF IPCPs, as shown in Figure 4. This capability allows for creating and deleting RIB objects and setting up DIF's configurations--e.g., routing table, and security policy, among others. The RINA manager controls the MAs through the interchange of CDAP messages. In that way, the RINA manager can send commands to operate over the IPCPs' RIB. In the architecture proposed, there are some MAs deployed on cloud infrastructures that are TCP/IP based and do not support the RINA protocols (EFCP and CDAP). As result, the MA deployed on cloud infrastructures cannot interchange CDAP messages to operate over the IPCPs' RIB. To overcome this limitation, MAs based on HTTP were designed and implemented to be deployed in these kinds of scenarios (cloud-based scenarios). In these cases, the HTTP-based MAs expose a well-defined REST API to facilitate the management from the SDN controller. These HTTP-based MAs do not follow the RINA MA principles of design detailed in [4] because they are considered a particular solution for enabling the progressive  
Figure 4: Network management DAF.  
adoption of RINA in the current networks' architectures. More details about the HTTP-based MA's design and implementation are explained in Section 3.3.  
On the other hand, the RINA manager is the core of this centralized network management DAF and must be implemented in the SDN controller. The RINA manager oversees the communication with the agents in each system of its management domain to provide central configuration, fault, security, and performance management. There is the possibility of implementing more than one RINA manager and reduce the area each RINA manager covers. In other words, the IoT network can be split into several management subareas, with an SDN controller for each subarea. This approach reduces the IoT network management complexity.  
The application processes require a single DIF dedicated to interconnecting the RINA manager with each MA. Figure 4 shows how the management DIF is implemented for communicating the RINA manager with the MAs of each system to be controlled. The RINA manager comprises the configuration manager module and the events manager. The configuration manager is responsible for sending a request to the agent management to create or delete IPCPs by sending CDAP messages. Meanwhile, the events manager receives and handles the events sent by the agent managements [31].  
Once the single dedicatedDIF has been established, the MAs intend to communicate with the RINA manager. To do so, the MAs and the RINA manager change several CDAP messages in the first stage of shaping the DAF management. Figure 5 shows this initial process. The MAs intend to send an M_CONNECT--CDAP message--to the RINA manager. This message contains information about the source application process, destination application process, and authentication mechanism employed. The application process will change more messages depending on the authentication mechanisms selected in each case. Once the authentication mechanisms have finished, the RINA manager responds with an M_CONNECT_R. Immediately, the RINA manager sends an M_READ to request a reading of the remote RIB objects. The MAs react with as many M_READ_R messages as the MA has RIB objects. Once this initial stage is finished, the RINA manager is ready to start operations.