Integrating the UCON technology into a SNMP-based environment requires a careful mapping between the entities of UCON and those entities and components of the SNMP. Following is a list of integrated components which require such mapping:
Subjects: Are entities that can perform certain rights on objects.
Objects: Are entities where rights are exercised upon them by subjects.
1. –
The concept of a Manger in SNMP is represented as a subject component in the UCON.
2. –
The concept of an Agent in SNMP is represented as a subject component in the UCON, in the cases when the agent is operating on system objects (I.e., when operating on MIB objects).
3. –
The concept of an Agent in SNMP can also be represented by an object in UCON, in the case when the agent is operated upon by the manager (I.e., when it is configured by the manager).
Permissions/Rights: The concept of Permissions in UCON will reflect all the privileges that an SNMP entity needs to complete a task.
Authorization Rules: Authorization rules in UCON are the set of requirements that should be satisfied before any SNMP active entity is permitted to operate on any MIB objects, or to be permitted to communicate with other entities within the SNMP community.
Obligations: The concept of Obligation in UCON can be represented in SNMP as the set of actions that SNMP entity is required to perform before and after the connection has been established.
Conditions: Conditions in UCON are represented in SNMP by the set of environmental and system decision factors that must be continuously evaluated to make sure that their changes do not lead to changes in the access status.