IP Tunnels in the Internet Architecture
draft-ietf-intarea-tunnels-07
Internet Area WG J. Touch
Internet Draft USC/ISI
Intended status: Best Current Practice M. Townsley
Updates: 4459 Cisco
Expires: December 2017 June 8, 2017
IP Tunnels in the Internet Architecture
draft-ietf-intarea-tunnels-07.txt
Status of this Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
This document may contain material from IETF Documents or IETF
Contributions published or made publicly available before November
10, 2008. The person(s) controlling the copyright in some of this
material may not have granted the IETF Trust the right to allow
modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) controlling
the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other
than English.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html
This Internet-Draft will expire on November 8, 2017.
Touch, Townsley Expires December 8, 2017 [Page 1]
Internet-Draft Tunnels in the Internet June 2017
Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
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 are used to derive recommendations that
update MTU and fragment issues in RFC 4459.
Table of Contents
1. Introduction...................................................3
2. Conventions used in this document..............................6
2.1. Key Words.................................................6
2.2. Terminology...............................................6
3. The Tunnel Model..............................................10
3.1. What is a Tunnel?........................................11
3.2. View from the Outside....................................13
3.3. View from the Inside.....................................14
3.4. Location of the Ingress and Egress.......................15
3.5. Implications of This Model...............................15
3.6. Fragmentation............................................16
3.6.1. Outer Fragmentation.................................16
3.6.2. Inner Fragmentation.................................18
3.6.3. The Necessity of Outer Fragmentation................19
4. IP Tunnel Requirements........................................20
4.1. Encapsulation Header Issues..............................20
4.1.1. General Principles of Header Fields Relationships...20
4.1.2. Addressing Fields...................................21
4.1.3. Hop Count Fields....................................21
Touch, Townsley Expires December 8, 2017 [Page 2]
Show full document text