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

The information below is for an old version of the document
Document Type Active Internet-Draft (intarea WG)
Last updated 2015-06-22 (latest revision 2015-06-08)
Replaces draft-pignataro-intarea-gre-ipv6
Stream IETF
Intended RFC status Proposed Standard
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 AD Evaluation::Revised I-D Needed
Consensus Boilerplate Unknown
Telechat date
Responsible AD Brian Haberman
Send notices to draft-ietf-intarea-gre-ipv6.ad@ietf.org, draft-ietf-intarea-gre-ipv6.shepherd@ietf.org, draft-ietf-intarea-gre-ipv6@ietf.org, cjbc@it.uc3m.es, intarea-chairs@ietf.org
Intarea Working Group                                       C. Pignataro
Internet-Draft                                             Cisco Systems
Updates: 2784 (if approved)                                    R. Bonica
Intended status: Standards Track                        Juniper Networks
Expires: December 10, 2015                                   S. Krishnan
                                                                Ericsson
                                                            June 8, 2015

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

Abstract

   Generic Routing Encapsulation (GRE) can be used to carry any network-
   layer payload protocol over any network-layer delivery protocol.  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.  It updates the GRE specification, RFC
   2784.

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 December 10, 2015.

Pignataro, et al.       Expires December 10, 2015               [Page 1]
Internet-Draft                  GRE IPv6                       June 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 . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  GRE Header Fields . . . . . . . . . . . . . . . . . . . . . .   3
     2.1.  Checksum Present  . . . . . . . . . . . . . . . . . . . .   3
   3.  IPv6 As GRE Payload . . . . . . . . . . . . . . . . . . . . .   4
     3.1.  GRE Protocol Type Considerations  . . . . . . . . . . . .   4
     3.2.  MTU Considerations  . . . . . . . . . . . . . . . . . . .   4
     3.3.  Fragmentation Considerations  . . . . . . . . . . . . . .   5
   4.  IPv6 As GRE Delivery Protocol . . . . . . . . . . . . . . . .   5
     4.1.  Next Header Considerations  . . . . . . . . . . . . . . .   5
     4.2.  Checksum Considerations . . . . . . . . . . . . . . . . .   6
     4.3.  MTU Considerations  . . . . . . . . . . . . . . . . . . .   6
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   7
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   7
   7.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   7
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   7
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .   7
     8.2.  Informative References  . . . . . . . . . . . . . . . . .   8
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   8

1.  Introduction

   Generic Routing Encapsulation (GRE) [RFC2784] [RFC2890] can be used
   to carry any network-layer payload protocol over any network-layer
   delivery protocol.  GRE procedures are specified for IPv4 [RFC0791],
   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

Pignataro, et al.       Expires December 10, 2015               [Page 2]
Internet-Draft                  GRE IPv6                       June 2015
Show full document text