IPv6 Support for Generic Routing Encapsulation (GRE)
draft-ietf-intarea-gre-ipv6-00

The information below is for an old version of the document
Document Type Active Internet-Draft (intarea WG)
Last updated 2015-02-02
Replaces draft-pignataro-intarea-gre-ipv6
Stream IETF
Intended RFC status (None)
Formats plain text pdf html bibtex
Reviews
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Intarea Working Group                                       C. Pignataro
Internet-Draft                                             Cisco Systems
Updates: 2784 (if approved)                                    R. Bonica
Intended status: Standards Track                        Juniper Networks
Expires: July 31, 2015                                       S. Krishnan
                                                                Ericsson
                                                        January 27, 2015

          IPv6 Support for Generic Routing Encapsulation (GRE)
                     draft-ietf-intarea-gre-ipv6-00

Abstract

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

   This document specifies GRE procedures for IPv6, used as either the
   payload or delivery protocol, and updates RFC 2784, the original GRE
   specification.

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 [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 July 31, 2015.

Pignataro, et al.         Expires July 31, 2015                 [Page 1]
Internet-Draft                  GRE IPv6                    January 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  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  GRE Header Fields . . . . . . . . . . . . . . . . . . . . . .   3
     2.1.  Checksum Present  . . . . . . . . . . . . . . . . . . . .   3
     2.2.  Protocol Type . . . . . . . . . . . . . . . . . . . . . .   3
   3.  IPv6 as a GRE Payload . . . . . . . . . . . . . . . . . . . .   4
   4.  IPv6 as a GRE Delivery Protocol . . . . . . . . . . . . . . .   4
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   7.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   4
   8.  Normative References  . . . . . . . . . . . . . . . . . . . .   4
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   5

1.  Introduction

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

   This document specifies GRE procedures for IPv6, used as either the
   payload or delivery protocol, and updates RFC 2784 [RFC2784].

1.1.  Terminology

   The following terms are specific to GRE and are modeled from
   [RFC2784]:

Pignataro, et al.         Expires July 31, 2015                 [Page 2]
Internet-Draft                  GRE IPv6                    January 2015

   o  GRE delivery header - an IPv4 or IPv6 header whose source address
      represents the GRE ingress node and whose destination address
      represents the GRE egress node.  The GRE delivery header
      encapsulates a GRE header.

   o  GRE header - the GRE protocol header.  The GRE header is
Show full document text