Koch, T. et al.: Policy Definition Language for Automated Management of Distributed System. 2 nd IEEE Int. Workshop on Systems Management, Toronto, June 1996, 55-64.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....but we do not have tools to support the refinement process. We are investigating the use of requirements engineering tools and techniques for refinement and analysis of policies. 8 Related Work There are a number of groups working on policies for network and distributed systems management [9] [20], 21] Some of this has been based on our early proposals for policy notation. Another approach is to define policies using the full power of a general purpose scripting or interpreted language (e.g. TCL) and load this into network components. Bos [22] takes this approach to specify application ....

Koch, T. et al.: Policy Definition Language for Automated Management of Distributed System. 2 nd IEEE Int. Workshop on Systems Management, Toronto, June 1996, 55-64.

....concepts for expressing a policy already exist which are discussed, e.g. in [17] Our main decision objective for choosing a specific policy concept is that it already comes with a proven implementation. Thus, we decided to apply the concept of policy objects with attributes as proposed in [14, 15, 16]. A policy is seen as an object with several attributes like subject, target, activity and constraints. Herein, a subject is seen as a set of objects, for which the specified activities are performed on a set of targets (in case that the specified constraints evaluate to true) Our research ....

T. Koch, C. Krell, and B Kr amer. Policy Definition Language for Automated Management of Distributed Systems. In IEEE Workshop on Systems Management. IEEE, 1996.

....offered or required and also supports arithmetic expressions and computations involving real numbers in determining a match. A more general scheme devised by Koch et al..i. entails the use of a Policy Definition Language (PDL) to specify executable rules suitable for automation of management policy [6]. The PDL supports logical expressions used as the precondition for triggering management actions. The IETF s Security Policy Specification Language [7] although specialized for security and Internet communications, generally follows the PDL in terms of functionality. Here the management actions ....

Thomas Koch, Christoph Krell, Bernd Krmer, Policy Definition Language for Automated Management of Distributed Systems, IEEE Computer Society, June 1996.

....and enforce service level agreement with minimum costs to the service provider. Some of the active policies can be reused for different situations just by changing the variables they control and the configuration parameters, like the thresholds in the previous examples. The works of [9][10] also present policy hierarchies. However, these works do not integrate with service level management, nor refine the requirements through several policy abstraction levels that act over the network down to the equipment, nor allow easy policy reuse. The policies of [11] restrict the network ....

Thomas Koch, Christoph Krell, Bernd Krmer, "Policy Definition Language for Automated Management of Distributed Systems", in 2 nd International Workshop on Systems Management, IEEE Computer Society, 19-21 June 1996, Canada.

....to qualify the service offered or required and also supports arithmetic expressions and computations involving real numbers. A more general scheme devised by Koch et al..i. entails the use of a Policy Definition Language (PDL) to specify executable rules suitable for automation of management policy [Koc96]. The PDL supports logical expressions used as the precondition for triggering management actions. The IETF s Security Policy Specification Language [Con00] although specialized for security and Internet communications, generally follows the PDL in terms of functionality. Here the management ....

Thomas Koch, Christoph Krell, Bernd Krmer, "Policy Definition Language for Automated Management of Distributed Systems," IEEE Computer Society, June 1996.

....concerned with each network; and element, managing individual network elements. Moffet 93] proposes three levels: goals, specifying objectives; policies, defining rules; and plans, corresponding to procedures of actions. The same notation [Marriot 96] is used for all the abstraction levels. Koch 96] also proposes three levels: requirements, described in prose; goal oriented, using templates of attributes specifying events, constraints and actions; and an operational level, where a Policy Description Language and an Event Definition Language are used. Wies 95] proposes four levels: ....

....[Lupu 97] identify rights, duties, functions and interactions associated with a position in the company, resulting in a definition of a set of policies for each role. Wies 94] proposes a policy hierarchy and a formal definition of policies to raise the abstraction level seen by the operators. Koch 96] also proposes a policy hierarchy, using different language constructs for each abstraction level. Although policies represent a high level 394 abstraction, at a level a human manager would expect, they usually restrict the network behaviour, instead of improving its operation. In addition, the ....

Thomas Koch, Christoph Krell, Bernd Krmer. Policy Definition Language for Automated Management of Distributed Systems. 2 nd International Workshop on Systems Management, IEEE Computer Society, 19-21 June 1996, Canada.

....introduced in 12 is that Pi P has been replaced by exec(A) We are using the current implementation to evaluate the policy and leave only the resolution of conflicts to the logic program. 8 Related work Several languages have been proposed for policy based network management (see for example [18, 24, 11, 14]) Much of the work in these papers is dedicated to implementation issues. Similarly, there are several implementations of event notification systems available but all have informal specifications (see for example [10] and the references therein) To address problems like conflict resolution it is ....

T. Koch, C. Krell, and B. Kramer. Policy definition language for automated management of distributed systems. In Second International Workshop on Systems Management, Toronto, Canada, June 1996.

....low level, very detailed, technically oriented form. To analyze the concept of policy and its use, it is necessary to clarify the meaning of the notion of policy and derive criteria for policy classification. The work in [19, 26, 27] has taken the first steps. Policy Distribution and Enforcement [25, 10, 11, 12, 16] Policy distribution refers to the distribution of management functionality into independent intelligent management agents and, subsequently, how to rescind or modify management functionality distributed to agents when policies change. Policy enforcement in this context refers to a formal ....

T. Koch, C. Krell, and B. Kramer. Policy Definition Language for Automated Management of Distributed Systems. Proceedings of the Second International IEEE Workshop on Systems Management, Toronto, Ontario, Canada, June 1996.

....management activities amongst multiple administrators and automated agents. In addition it must be possible to dynamically load and retract policies from agents to change the behaviour and strategy of the management system without re coding or interrupting their activities (DSOM 1994; Sloman 1994; Koch 1996; Magee 1996) In this section we outline some aspects of the management policy notation and show how roles can be conceived as groups of policies. 2.1 Management Policies Policies express a relationship between a domain of subjects (managers) and a domain of target managed objects. Domains are ....

Koch, T. and et al. (1996). "Policy Definition Language for Automated Management of Distributed Systems", IEEE 2nd. Int. Workshop on Systems Management, Toronto (Canada).

....techniques to resolve situations with incompatible goals. Planning techniques for conflict management are also used in Distributed Artificial Intelligence (Lander, 1994) In the case of our management policies such techniques could be used only in conjunction with the refinement of the policies. Koch (1996) uses a policy notation based on ours and establishes a semantic graph model to detect ill behaved policy sets with unsatisfiable pre conditions. This can also be used to perform what if analysis on chains of policies prior to execution. Deontic Logic provides the closest approximation of our ....

Koch, T. et al. (1996). Policy Definition Language for Automated Management of Distributed System. IEEE 2nd. Int. Workshop on Systems Management, Toronto (Canada).

....scripts which are interpreted by agents. The proposed architecture stores and processes validation rules at a lower level. Finally, the proposed research attempts to reconcile its architecture with the concepts introduced by the CORBA System Management Common Management Facilities. Koch et al. [15] also propose a policy driven architecture similar to the current one. The policy and domain concepts are similar to other work. They deal more with the policy hierarchy issue than we have done to date. As in our work, policies and events are separated and each has its own formal syntax. They ....

....Instead, the proposed management system deals only with low level structured policies. In general terms, low level policies associate management actions with the occurrence of events throughout the system. Many of the basic policy concepts used in this thesis are based loosely on other research [1, 2, 15, 19, 20]. It is not intended that policy specification and maintenance be a focal point of the thesis. In general, policies fall into one of two general categories [21] Authorization policies define what activities are permitted while obligation policies define what activities must be carried out. While ....

[Article contains additional citation context not shown here]

Thomas Koch, Christoph Krell, and Bernd Kramer. Policy Definition Language for Automated Management of Distributed Systems. In Proceedings of the IEEE Second International Workshop on Systems Management, Toronto, Canada, June 1996.

....usually given in plain text on a very abstract level, and the formal description of appropriate procedures in terms of executable commands. To support a stepwise refinement of policies from an informal strategic level to a formalized operational level, we introduced a three level policy hierarchy [8]. On the lowest level, we use a Policy Description Language (PDL) that enables the computer to check the syntax of the policy description and to translate policies into executable rules. Our hierarchy also reflects another important aspect of management implementation. While the highest level ....

T. Koch, C. Krell, and B. Kramer. Policy Definition Language for Automated Management of Distributed Systems. In 2nd Int. IEEE Workshop on Systems Management, Toronto, Canada, June 1996. IEEE.

No context found.

Koch, T. et al. (1996). Policy Definition Language for Automated Management of Distributed System. Proceedings of the 2 nd IEEE International Workshop on Systems Management, Toronto (Canada), June 1996, pp. 55-64.

No context found.

Koch, T., and Krell, C., and Kramer, B. (1996) Policy Definition Language for Automated Management of Distributed Systems. Proceedings of the IEEE Second International Workshop on Systems Management, Toronto, Canada.

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC