A Proposal for Adding Flow Support to CLNP
draft-callon-addflow-support-clnp-00
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Last updated | 1994-03-18 | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
This Internet-Draft is no longer active. A copy of
the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-callon-addflow-support-clnp-00.txt
https://www.ietf.org/archive/id/draft-callon-addflow-support-clnp-00.txt
Abstract
This internet-draft proposes a general approach for adding flow support to CLNP. This is useful both for reservation of resources in routers for support of applications with specific application service requirements, and for coordination with subnet connections when operating over connection oriented subnets (for example for operation of CLNP over ATM). Futher work is needed to define the protocol in detail.
Authors
Ross Callon (rcallon@juniper.net)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)