RSVP Usage in Enterprise Networks
draft-lavers-rsvp-usage-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Glen Lavers , Karen Bailey | ||
| Last updated | 2010-03-22 | ||
| 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
This document presents a number of resource control requirements that enterprise network administrators face. It also discusses how RSVP is being used, or considered, in order to address these requirements. This document is offered as input to the IETF 77 RSVP mini-BOF. The authors recommend that the IETF continues supporting RSVP as a Standards Track protocol and continue facilitating development of necessary RSVP extensions in the Standards Track.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)