Capability Negotiation: The RSVP CAP Object
draft-ietf-issll-rsvp-cap-03
| Document | Type |
Expired Internet-Draft
(issll WG)
Expired & archived
|
|
|---|---|---|---|
| Author | Syed Hamid | ||
| Last updated | 2001-05-01 | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| 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
The resource reservation protocol [RSVP] is an end-to-end signaling protocol and it can be a useful mechanism to carry the upstream node or network capabilities/willingness to the downstream network/nodes. This draft proposes a capability negotiation object, CAP object, in the RSVP PATH message that can be used to convey end host/upstream node capabilities to the downstream network/nodes.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)