The NSIS Transport Layer Protocol (NTLP)
draft-shore-ntlp-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Melinda Shore | ||
| Last updated | 2003-06-24 | ||
| 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 RSVP [RFC2205] model for communicating requests to network devices along a datapath has proven useful for a variety of appli- cations beyond what the protocol designers envisioned, and while the architectural model generalizes well the protocol itself has a number of features that limit its applicability to applications other than IntServ [RFC1633]. The NSIS working group is developing a modernized version that, among other things, is based on a 'two- layer' architecture that divides protocol function into transport and application. This document describes the transport protocol.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)