Use Cases and Requirements
draft-montpetit-transport-use-cases-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Marie-Jose Montpetit , Igor Zhovnirovsky | ||
| Last updated | 2014-08-07 (Latest revision 2014-02-03) | ||
| 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
This document describes some of the services and application use cases that may require specific transport services over an Internet subnetwork. It also presents, when available, some derived requirements and conditions of utilization that will allow to choose the most appropriate transport service. The use cases assume that choice of transport service is fully based on the requirements. In all cases however, the fallback is considered to be TCP or UDP.
Authors
Marie-Jose Montpetit
Igor Zhovnirovsky
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)