Requirements for Link Adaptation over IP-in-IPv4 Tunnels
draft-templin-linkadapt-reqts-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Fred Templin | ||
| Last updated | 2005-09-30 | ||
| 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
IP-in-IPv4 tunnel endpoints present a Maximum Transmission Unit (MTU) to layer 3 via static prearrangements and/or dynamic MTU determination based on ICMPv4 messages, but these methods have known operational limitations that can cause degraded performance and communications failures. A new method for providing link adaptation over IP-in-IPv4 tunnels is needed.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)