Using RSVPv1 as NTLP (NSIS Transport Layer Protocol): suggestions for modifications on RFC2205
draft-westberg-nsis-rsvp-as-ntlp-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Lars Westberg | ||
| Last updated | 2003-02-28 | ||
| 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
The Resource ReSerVation Protocol (RSVPv1) has been on the standards track within the IETF for a number of years. During that time, the level of vendor support and deployment has been relatively slow, despite the desire of many to deploy technology to deliver services with different levels of quality of service (QoS) to their customers. The reasons for this are arguably well-understood and documented and are not the focus of this memo. This memo is proposing a (NSIS Transport Layer Protocol) NTLP, that is a modified version of RSVPv1 specified in RFC2205. Furthermore, it provides design guidelines and specifications for the development of the NLTP that is based on a modified version of RSVPv1.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)