Network-Layer Signaling: Transport Layer
draft-shore-nls-tl-06
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Melinda Shore , David McGrew , Kaushik Biswas | ||
| Last updated | 2008-07-13 | ||
| 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 model for communicating requests to network devices along a datapath has proven useful for a variety of applications 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. Network Layer Signaling uses the RSVP on-path communication model and provides a lightweight transport layer for non-QoS signaling applications, such as discovery or diagnostics. It is based on a "two-layer" architecture that divides protocol function into transport and application. This document describes the transport protocol.
Authors
Melinda Shore
David McGrew
Kaushik Biswas
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)