Usage and Format of the DCLASS Object With RSVP Signaling
draft-bernet-dclass-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Yoram Bernet | ||
| Last updated | 1999-03-04 | ||
| 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
RSVP signaling may be used to enhance the manageability of application traffic's QoS in a differentiated service (diff-serv) network [intdiff]. In this model, certain network elements within or at the edges of the diff-serv network may use RSVP messages to effect admission control or to apply QoS policy. One mechanism by which network elements may apply QoS policy is by causing a DCLASS object to be returned to a sending host in an RSVP RESV message. The DCLASS object indicates the diff-serv DSCP that the sender should include when submitting packets on the admitted flow, to the diff- serv network. This draft describes the usage and format of the DCLASS object.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)