IP Tunnels in the Internet Architecture
draft-ietf-intarea-tunnels-13
| Document | Type |
Expired Internet-Draft
(intarea WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Dr. Joseph D. Touch , Mark Townsley | ||
| Last updated | 2023-09-27 (Latest revision 2023-03-26) | ||
| Replaces | draft-touch-intarea-tunnels | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| 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 discusses the role of IP tunnels in the Internet architecture. An IP tunnel transits IP datagrams as payloads in non- link layer protocols. This document explains the relationship of IP tunnels to existing protocol layers and the challenges in supporting IP tunneling, based on the equivalence of tunnels to links. The implications of this document updates RFC 4459 and its MTU and fragmentation recommendations for IP tunnels.
Authors
Dr. Joseph D. Touch
Mark Townsley
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)