Transport-layer Considerations for Explicit Cross-layer Indications
draft-sarolahti-tsvwg-crosslayer-01
Document | Type |
Expired Internet-Draft
(individual in gen area)
Expired & archived
|
|
---|---|---|---|
Author | Pasi Sarolahti | ||
Last updated | 2015-10-14 (Latest revision 2007-03-08) | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Intended RFC status | (None) | ||
Formats | |||
Stream | WG state | (None) | |
Document shepherd | (None) | ||
IESG | IESG state | Expired (IESG: Dead) | |
Action Holders |
(None)
|
||
Consensus boilerplate | Unknown | ||
Telechat date | (None) | ||
Responsible AD | Lars Eggert | ||
Send notices to | floyd@icir.org |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
Several types of explicit cross-layer communication schemes have been proposed to enhance the transport protocol performance. However, various challenges with such schemes have been identified, for example concerning the interactions with the middleboxes and tunnels in the network. This document discusses different types of explicit cross-layer notification mechanisms that have been proposed to enhance end-to-end transport performance. We analyze the different mechanisms using a taxonomy based on what kind of network interactions they require, and discuss the benefits and disadvantages different approaches have. The objective is to get a common understanding of the possibilities and challenges with these mechanisms, with pointers to past discussions on this topic, and to describe the possible next steps towards removing barriers from explicit cross-layer communication in future protocols.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)