A Fragmentation Strategy for Generic Routing Encapsulation (GRE)
draft-bonica-intarea-gre-mtu-04

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2014-02-14
Replaced by rfc7588, draft-ietf-intarea-gre-mtu
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
Additional URLs
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Intarea Working Group                                          R. Bonica
Internet-Draft                                          Juniper Networks
Intended status: Best Current Practice                      C. Pignataro
Expires: August 16, 2014                                   Cisco Systems
                                                                J. Touch
                                                                 USC/ISI
                                                       February 12, 2014

    A Fragmentation Strategy for Generic Routing Encapsulation (GRE)
                    draft-bonica-intarea-gre-mtu-04

Abstract

   This memo specifies a default GRE tunnel fragmentation strategy,
   which has been implemented by many vendors and widely deployed on the
   Internet.

   This memo also specifies requirements for GRE implementations.
   Having satisfied these requirements, a GRE implementation will
   execute the default GRE tunnel fragmentation strategy, specified
   herein, with minimal configuration.  However, with additional
   configuration, the GRE implementation can execute any of the tunnel
   fragmentation strategies defined in RFC 4459.

Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC 2119 [RFC2119].

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   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."

   This Internet-Draft will expire on August 16, 2014.

Bonica, et al.           Expires August 16, 2014                [Page 1]
Internet-Draft              GRE Fragmentation              February 2014

Copyright Notice

   Copyright (c) 2014 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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Strategic Overview  . . . . . . . . . . . . . . . . . . . . .   5
     2.1.  Candidate Strategies  . . . . . . . . . . . . . . . . . .   5
     2.2.  Default Strategy  . . . . . . . . . . . . . . . . . . . .   6
   3.  Generic Requirements for GRE Ingress Routers  . . . . . . . .   6
     3.1.  General . . . . . . . . . . . . . . . . . . . . . . . . .   6
     3.2.  GRE MTU (GMTU) Estimation and Discovery . . . . . . . . .   6
   4.  Procedures Affecting The GRE Deliver Header . . . . . . . . .   7
     4.1.  Tunneling GRE Over IPv4 . . . . . . . . . . . . . . . . .   7
     4.2.  Tunneling GRE Over IPv6 . . . . . . . . . . . . . . . . .   8
   5.  Procedures Affecting the GRE Payoad . . . . . . . . . . . . .   8
     5.1.  IPv4 Payloads . . . . . . . . . . . . . . . . . . . . . .   8
     5.2.  IPv6 Payloads . . . . . . . . . . . . . . . . . . . . . .   8
     5.3.  MPLS Payloads . . . . . . . . . . . . . . . . . . . . . .   8
   6.  GRE Egress Router Procedures  . . . . . . . . . . . . . . . .   8
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   9
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .   9
   9.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   9
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .   9
     10.1.  Normative References . . . . . . . . . . . . . . . . . .   9
     10.2.  Informative References . . . . . . . . . . . . . . . . .  10
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  10

1.  Introduction

   Generic Routing Encapsulation (GRE) [RFC2784] can be used to carry
   any network layer protocol over any network layer protocol.  GRE has
   been implemented by many vendors and is widely deployed in the
Show full document text