Joint Inter-Domain Management: Difference between revisions
Mark viking (talk | contribs) Add historical perspective + ref |
Mark viking (talk | contribs) →top: Add some more perspective + ref |
||
| Line 9: | Line 9: | ||
The mapping specification is in two parts: the Specification Translation and the Interactive Translation.<ref name="Open2000" /> The Specification Translation spells out translation of the [[object oriented]] [[object model]]s among the [[network management]] 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 [[network management software]] that operates across protocols.<ref name="Soukouti1997" /> |
The mapping specification is in two parts: the Specification Translation and the Interactive Translation.<ref name="Open2000" /> The Specification Translation spells out translation of the [[object oriented]] [[object model]]s among the [[network management]] 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 [[network management software]] that operates across protocols.<ref name="Soukouti1997" /> |
||
The JIDM specification |
The JIDM specification was considered the most significant work to use the CORBA framework in network management mapping.<ref name="Kwon2001">{{cite book |last1=Kwon |first1=Joon-Heup |last2=Park |first2=Jong-Tae |title=Design and Implementation of CORBA–Based Integrated Network Management System |date=2001 |publisher=Springer Berlin Heidelberg |isbn=9783540477341 |page=409 |url=https://link.springer.com/chapter/10.1007/3-540-47734-9_41 |language=en}}</ref> The JIDM specification led to CORBA's further use in specifications in the telecommunications industry, such as the ITU-T GDMO specifications.<ref name="Pavlou2007">{{cite journal |last1=Pavlou |first1=George |title=On the Evolution of Management Approaches, Frameworks and Protocols: A Historical Perspective |journal=Journal of Network and Systems Management |date=13 October 2007 |volume=15 |issue=4 |pages=4441-442 |doi=10.1007/s10922-007-9082-9 |url=https://www.ee.ucl.ac.uk/~gpavlou/Publications/Journal-papers/Pavlou-07a.pdf |accessdate=24 October 2019}}</ref> But the object framework led to performance problems, such as requiring a [[remote method invocation]] 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.<ref name="Pavlou2007" /> |
||
== References == |
== References == |
||
Revision as of 03:22, 24 October 2019
An editor has nominated this article for deletion. You are welcome to participate in the deletion discussion, which will decide whether or not to retain it. |
Joint Inter-Domain Management (JIDM) task force, jointly sponsored by X/Open and the Network Management Forum, has defined a mapping between SNMP, CMIP and CORBA.[1][2] The JIDM specification was adopted as a standard by the Open Group in 2000.[3]
The mapping specification is in two parts: the Specification Translation and the Interactive Translation.[3] The Specification Translation spells out translation of the object oriented object models among the network management 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 network management software that operates across protocols.[2]
The JIDM specification was considered the most significant work to use the CORBA framework in network management mapping.[4] The JIDM specification led to CORBA's further use in specifications in the telecommunications industry, such as the ITU-T GDMO specifications.[5] But the object framework led to performance problems, such as requiring a remote method invocation 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.[5]
References
- ^ Jean-Philippe Martin-Flatin and Simon Znaty (1997-07-30). "A Simple Typology of Distributed Network Management Paradigms" (PDF). Laboratory for computer Communications and Applications, École Polytechnique Fédérale de Lausanne: 8–9.
{{cite journal}}: Cite journal requires|journal=(help) - ^ a b Soukouti, Nader; Hollberg, Ulf (1997). "Joint Inter Domain Management: CORBA, CMIP and SNMP". Integrated Network Management V: Integrated management in a virtual world Proceedings of the Fifth IFIP/IEEE International Symposium on Integrated Network Management San Diego, California, U.S.A., May 12–16, 1997. Springer US. pp. 153–164. ISBN 9780387351803.
- ^ a b "Inter-Domain Management: Specification & Interaction Translation". publications.opengroup.org. The Open Group.
- ^ Kwon, Joon-Heup; Park, Jong-Tae (2001). Design and Implementation of CORBA–Based Integrated Network Management System. Springer Berlin Heidelberg. p. 409. ISBN 9783540477341.
- ^ a b Pavlou, George (13 October 2007). "On the Evolution of Management Approaches, Frameworks and Protocols: A Historical Perspective" (PDF). Journal of Network and Systems Management. 15 (4): 4441–442. doi:10.1007/s10922-007-9082-9. Retrieved 24 October 2019.
 | This computer networking article is a stub. You can help Wikipedia by expanding it. |