RSVP Reservation Status Policy Element for End-to-End Accounting
draft-durham-pe-rstatus-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Shai Herzog , David Durham | ||
| Last updated | 1999-06-30 | ||
| 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 details an RSVP Policy Element that provides a mechanism by which RSVP reservation establishment can be reliably confirmed, end-to-end. This Policy Element provides a status update with each PATH message refresh, useful for determining the lifetime of a reservation end-to-end. Such a policy element will be useful for accounting and billing applications that are interested in reliably knowing when a reservation has been successfully established end-to-end and when a reservation is finally removed.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)