Policy Control (IP and ATM)

Version

1.0, Nov. 5th, 1998

Experiment leader

Victor Reijs, SURFnet bv, The Netherlands

Participants

BE, CH, ES, FR, IT, NL, ???

Goals

Description

As well as in the ATM as in the IP world, Policy Control is becoming important because some users(groups) could have more rights in quality than other users(groups). To provide at a user(groups) level a policy, one also needs to have identification of that user/group. Although this generic service identification is not the issue in this activity, the relation must be studied though!
The Policy Control service that possible emerges from this activity, will be used in the activities on intergrated and differentiated services and SVC services, to control who/what gets which part of the (scarce) bandwidth. the bandwidth brokers model is also are part of this activity.

Pre-requisites

None

Dates and phases

Network infrastructure

Low speed (max. 1 Mbit/s, possibly over production IP network), because Policy Control will be more a kind of signaling/control issue.

Local infrastructure

The generic service identification will be handy to test WAN Policy Controlled services.

Hard- and software

Hardware/software on routers and policy servers that will be able to do policy based decisions. Also the generic service identification is needed (but not tested).

Related work

References

To be filled in
Last major content related changes: Nov. 5th, 1998