Edge Based Admission Control with Class Based Resource Management
draft-rawlins-admctl-ds-mgt-03
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Diana J. Rawlins | ||
| Last updated | 2002-06-14 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
New value-added IP services such as VoIP requires per-flow admission control to be performed in order to ensure the admission of new traffic flows does not degrade the performance of the existing traffic flows in the network. Resource Reservation Protocol (RSVP) for Intserv [2205] is proposed to support per-flow admission control. However, RSVP requires per-flow state installation, per-flow state refreshment, per-flow traffic management and resource reservation on each node along a forwarding path, which cause significant scalability issues, especially on the boundary routers and core routers of service provides’ networks, which need to process thousands of traffic flows as network aggregation points. Intserv over Diffserv networks proposed in [2998] requires the RSVP/Intserv processing only on boundary routers and edge routers. Nevertheless, RSVP/Intserv has still rarely been supported by boundary router vendors because of the scalability issue. The use of edge-based admission control with per-class resource management and policy control offers a scalable approach to manage per-flow admission control for QoS sensitive applications.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)