IPv6 Support for Generic Routing Encapsulation (GRE)
RFC 7676

Document Type RFC - Proposed Standard (October 2015; No errata)
Last updated 2015-10-22
Replaces draft-pignataro-intarea-gre-ipv6
Stream IETF
Formats plain text pdf html bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Document shepherd Carlos Bernardos
Shepherd write-up Show (last changed 2015-06-22)
IESG IESG state RFC 7676 (Proposed Standard)
Consensus Boilerplate Yes
Telechat date
Responsible AD Brian Haberman
Send notices to (None)
IANA IANA review state Version Changed - Review Needed
IANA action state No IC
Internet Engineering Task Force (IETF)                      C. Pignataro
Request for Comments: 7676                                 Cisco Systems
Category: Standards Track                                      R. Bonica
ISSN: 2070-1721                                         Juniper Networks
                                                             S. Krishnan
                                                                Ericsson
                                                            October 2015

          IPv6 Support for Generic Routing Encapsulation (GRE)

Abstract

   Generic Routing Encapsulation (GRE) can be used to carry any network-
   layer payload protocol over any network-layer delivery protocol.
   Currently, GRE procedures are specified for IPv4, used as either the
   payload or delivery protocol.  However, GRE procedures are not
   specified for IPv6.

   This document specifies GRE procedures for IPv6, used as either the
   payload or delivery protocol.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force
   (IETF).  It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by the
   Internet Engineering Steering Group (IESG).  Further information on
   Internet Standards is available in Section 2 of RFC 5741.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   http://www.rfc-editor.org/info/rfc7676.

Pignataro, et al.            Standards Track                    [Page 1]
RFC 7676                        GRE IPv6                    October 2015

Copyright Notice

   Copyright (c) 2015 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  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   3
     1.2.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  GRE Header Fields . . . . . . . . . . . . . . . . . . . . . .   4
     2.1.  Checksum Present  . . . . . . . . . . . . . . . . . . . .   4
   3.  IPv6 as GRE Payload . . . . . . . . . . . . . . . . . . . . .   5
     3.1.  GRE Protocol Type Considerations  . . . . . . . . . . . .   5
     3.2.  MTU Considerations  . . . . . . . . . . . . . . . . . . .   5
     3.3.  Fragmentation Considerations  . . . . . . . . . . . . . .   5
   4.  IPv6 as GRE Delivery Protocol . . . . . . . . . . . . . . . .   6
     4.1.  Next Header Considerations  . . . . . . . . . . . . . . .   6
     4.2.  Checksum Considerations . . . . . . . . . . . . . . . . .   6
     4.3.  MTU Considerations  . . . . . . . . . . . . . . . . . . .   8
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   8
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   8
     6.1.  Normative References  . . . . . . . . . . . . . . . . . .   8
     6.2.  Informative References  . . . . . . . . . . . . . . . . .   9
   Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . .  10
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  11

Pignataro, et al.            Standards Track                    [Page 2]
RFC 7676                        GRE IPv6                    October 2015

1.  Introduction

   Generic Routing Encapsulation (GRE) [RFC2784] [RFC2890] can be used
   to carry any network-layer payload protocol over any network-layer
   delivery protocol.  Currently, GRE procedures are specified for IPv4
   [RFC791], used as either the payload or delivery protocol.  However,
   GRE procedures are not specified for IPv6 [RFC2460].

   This document specifies GRE procedures for IPv6, used as either the
   payload or delivery protocol.  Like RFC 2784, this document describes
   how GRE has been implemented by several vendors.

1.1.  Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
Show full document text