Joint Inter-Domain Management

Joint Inter-Domain Management (JIDM) <a href="/facts/Task_force/gaNGe3se">task force</a>, jointly sponsored by <a href="/facts/X/Open/btwVKbX2">X/Open</a> and the Network Management Forum, has defined a mapping between <a href="/facts/Simple_Network_Management_Protocol/UNYPVA1C">SNMP</a>, <a href="/facts/Common_management_interface_protocol/Q9yV0p5e">CMIP</a> and <a href="/facts/CORBA/VUDlTHs5">CORBA</a>. The JIDM specification was adopted as a standard by <a href="/facts/The_Open_Group/uRoDdEae">the Open Group</a> in 2000.
The mapping specification is in two parts: the Specification Translation and the Interactive Translation. The Specification Translation spells out translation of the <a href="/facts/Object_oriented/TxNMEcao">object oriented</a> <a href="/facts/Object_model/sAjjBb7V">object models</a> among the <a href="/facts/Network_management/w344Ubfp">network management</a> protocols that allow for data transfer across protocols. The Interactive Translation concerns the dynamic translation of objects in use that allows for the construction of <a href="/facts/Network_management_software/lmtS9A3x">network management software</a> that operates across protocols.
The JIDM specification was considered the most significant work to use the CORBA framework in network management mapping. The JIDM specification led to CORBA's further use in specifications in the telecommunications industry, such as the ITU-T GDMO specifications. But the object framework led to performance problems, such as requiring a <a href="/facts/Remote_method_invocation/boz8jDHe">remote method invocation</a> for each object attribute and scalability problems coming from large numbers of objects generated from all the network connections. This led to network management data mapping approaches where sets of attributes and lists of connections were transferred instead of individual objects.

Joint Inter-Domain Management open-in-new

Joint Inter-Domain Management