#7 IRM should be a "node" component, not a component of the application

1.0
closed
edugrasa
IRM (1) bug (2) application (1)
2015-01-14
2014-11-04
edugrasa
No

The Application should just have an "IRM client" that forwards flow allocation requests to the "IRM" within a node. The "IRM" within the node (machine) is the one that will select the proper IPC Process to use, and/or interact with the DIF Allocator in order to create a new DIF. Rhe model of the "RINA node" should include Application Processes, IPC Processes and the mediator between the two - can call IPC Manager for example (as in IRATI), or similar - check the reference model for a better name.

Discussion

  • edugrasa
    edugrasa
    2014-11-04

    • Description has changed:

    Diff:

    --- old
+++ new
@@ -1 +1 @@
-The Application should just have an "IRM client" that forwards flow allocation requests to the "IRM" within a node. The "IRM" within the node (machine) is the one that will select the proper IPC Process to use, and/or interact with the DIF Allocator in order to create a new DIF. 
+The Application should just have an "IRM client" that forwards flow allocation requests to the "IRM" within a node. The "IRM" within the node (machine) is the one that will select the proper IPC Process to use, and/or interact with the DIF Allocator in order to create a new DIF. Rhe model of the "RINA node" should include Application Processes, IPC Processes and the mediator between the two - can call IPC Manager for example (as in IRATI), or similar - check the reference model for a better name.
     
    Link

  • Vladimír Veselý
    Vladimír Veselý
    2015-01-14

    Successfully resolved in yesterdays RINASim version. Current Host node is depicted in attached picture. It contains APs, IPCs and IRM (blue circle) as separate module mediating between them.

     
    Attachments
    Thumbnail
    D24-host2ap.png
    Link

  • Vladimír Veselý
    Vladimír Veselý
    2015-01-14

    • status: open --> closed
     
    Link