RSVP ErrorValues Used to Modify Sender Behavior
draft-ietf-rap-modify-sender-behavior-00
| Document | Type | Expired Internet-Draft (rap WG) | |
|---|---|---|---|
| Last updated | 2001-07-19 | ||
| Stream | IETF | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized (tools)
htmlized
bibtex
|
||
| Stream | WG state | WG Document | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | Expired | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-ietf-rap-modify-sender-behavior-00.txt
Abstract
This draft defines several mechanisms by which network policies can use RSVP signaling to control the behavior of compliant sending applications. Specifically, two new error codes are defined for use in the RSVP Policy Data object [RFC 2752]. In addition, a new use of the DCLASS object [RFC 2996] is defined.
Authors
Ralph Santitoro
(rsantito@nortelnetworks.com)
Ramesh Pabbati
(rameshpa@microsoft.com)
Yoram Bernet
(yoramb@microsoft.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)