draft-ietf-intarea-gre-ipv6-03.txt   draft-ietf-intarea-gre-ipv6-04.txt 
Intarea Working Group C. Pignataro Intarea Working Group C. Pignataro
Internet-Draft Cisco Systems Internet-Draft Cisco Systems
Updates: 2784 (if approved) R. Bonica Updates: 2784 (if approved) R. Bonica
Intended status: Standards Track Juniper Networks Intended status: Standards Track Juniper Networks
Expires: September 27, 2015 S. Krishnan Expires: September 28, 2015 S. Krishnan
Ericsson Ericsson
March 26, 2015 March 27, 2015
IPv6 Support for Generic Routing Encapsulation (GRE) IPv6 Support for Generic Routing Encapsulation (GRE)
draft-ietf-intarea-gre-ipv6-03 draft-ietf-intarea-gre-ipv6-04
Abstract Abstract
Generic Routing Encapsulation (GRE) can be used to carry any network- Generic Routing Encapsulation (GRE) can be used to carry any network-
layer payload protocol over any network-layer delivery protocol. GRE layer payload protocol over any network-layer delivery protocol. GRE
procedures are specified for IPv4, used as either the payload or procedures are specified for IPv4, used as either the payload or
delivery protocol. However, GRE procedures are not specified for delivery protocol. However, GRE procedures are not specified for
IPv6. IPv6.
This document specifies GRE procedures for IPv6, used as either the This document specifies GRE procedures for IPv6, used as either the
skipping to change at page 1, line 47 skipping to change at page 1, line 47
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on September 27, 2015. This Internet-Draft will expire on September 28, 2015.
Copyright Notice Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the Copyright (c) 2015 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 30 skipping to change at page 2, line 30
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3
2. GRE Header Fields . . . . . . . . . . . . . . . . . . . . . . 3 2. GRE Header Fields . . . . . . . . . . . . . . . . . . . . . . 3
2.1. Checksum Present . . . . . . . . . . . . . . . . . . . . 3 2.1. Checksum Present . . . . . . . . . . . . . . . . . . . . 3
2.2. Protocol Type . . . . . . . . . . . . . . . . . . . . . . 3 2.2. Protocol Type . . . . . . . . . . . . . . . . . . . . . . 3
3. IPv6 as a GRE Payload . . . . . . . . . . . . . . . . . . . . 4 3. IPv6 as a GRE Payload . . . . . . . . . . . . . . . . . . . . 4
3.1. MTU Considerations . . . . . . . . . . . . . . . . . . . 4 3.1. MTU Considerations . . . . . . . . . . . . . . . . . . . 4
4. IPv6 as a GRE Delivery Protocol . . . . . . . . . . . . . . . 5 4. IPv6 as a GRE Delivery Protocol . . . . . . . . . . . . . . . 5
4.1. MTU Considerations . . . . . . . . . . . . . . . . . . . 5 4.1. Checksum Considerations . . . . . . . . . . . . . . . . . 5
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 4.2. MTU Considerations . . . . . . . . . . . . . . . . . . . 5
6. Security Considerations . . . . . . . . . . . . . . . . . . . 5 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6
6. Security Considerations . . . . . . . . . . . . . . . . . . . 6
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 6 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 6
8. Normative References . . . . . . . . . . . . . . . . . . . . 6 8. Normative References . . . . . . . . . . . . . . . . . . . . 6
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 6 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 7
1. Introduction 1. Introduction
Generic Routing Encapsulation (GRE) [RFC2784] [RFC2890] can be used Generic Routing Encapsulation (GRE) [RFC2784] [RFC2890] can be used
to carry any network-layer payload protocol over any network-layer to carry any network-layer payload protocol over any network-layer
delivery protocol. GRE procedures are specified for IPv4 [RFC0791], delivery protocol. GRE procedures are specified for IPv4 [RFC0791],
used as either the payload or delivery protocol. However, GRE used as either the payload or delivery protocol. However, GRE
procedures are not specified for IPv6 [RFC2460]. procedures are not specified for IPv6 [RFC2460].
This document specifies GRE procedures for IPv6, used as either the This document specifies GRE procedures for IPv6, used as either the
skipping to change at page 5, line 26 skipping to change at page 5, line 26
immediately follow the GRE delivery header. Alternatively, IPv6 immediately follow the GRE delivery header. Alternatively, IPv6
extension headers MAY be inserted between the GRE delivery header and extension headers MAY be inserted between the GRE delivery header and
the GRE header. the GRE header.
If the GRE header immediately follows the GRE delivery header, the If the GRE header immediately follows the GRE delivery header, the
Next Header field in the IPv6 header of the GRE delivery packet MUST Next Header field in the IPv6 header of the GRE delivery packet MUST
be set to 47. If extension headers are inserted between the GRE be set to 47. If extension headers are inserted between the GRE
delivery header and the GRE header, the Next Header field in the last delivery header and the GRE header, the Next Header field in the last
IPv6 extension header MUST be set to 47. IPv6 extension header MUST be set to 47.
4.1. MTU Considerations 4.1. Checksum Considerations
As stated in [RFC2784], the Checksum field contains the IP (one's
complement) checksum sum of the all the 16 bit words in the GRE
header and the payload packet. Therefore, the checksum does not
ensure the integrity of the IPv6 delivery header.
Because the IPv6 delivery header does not include a checksum of its
own, it is subject to corruption. However, even if the delivery
header is corrupted, to likelihood of that corruption resulting in
misdelivery of the payload is extremely low.
4.2. MTU Considerations
"IPv6 requires that every link in the Internet have an MTU of 1280 "IPv6 requires that every link in the Internet have an MTU of 1280
octets or greater. On any link that cannot convey a 1280-octet octets or greater. On any link that cannot convey a 1280-octet
packet in one piece, link-specific fragmentation and reassembly must packet in one piece, link-specific fragmentation and reassembly must
be provided at a layer below IPv6" [RFC2460]. be provided at a layer below IPv6" [RFC2460].
IP adjacencies formed by GRE over IPv6 share this requirement. The IP adjacencies formed by GRE over IPv6 share this requirement. The
IP adjacency MUST have an MTU of 1280 octets or greater. This IP adjacency MUST have an MTU of 1280 octets or greater. This
requirement is fulfilled if all permissible paths between the GRE requirement is fulfilled if all permissible paths between the GRE
ingress and GRE egress have PMTU greater than the 1280 plus the GRE ingress and GRE egress have PMTU greater than the 1280 plus the GRE
skipping to change at page 6, line 8 skipping to change at page 6, line 20
6. Security Considerations 6. Security Considerations
This document adds no additional security risks to GRE, beyond what This document adds no additional security risks to GRE, beyond what
is specified in [RFC2784]. It also does not provide any additional is specified in [RFC2784]. It also does not provide any additional
security for GRE. security for GRE.
7. Acknowledgements 7. Acknowledgements
The authors would like to thank Fred Baker, Dino Farinacci, Tom The authors would like to thank Fred Baker, Dino Farinacci, Tom
Herbert, Fred Templin, Joe Touch and Andrew Yourtchenko for their Herbert, Fred Templin, Joe Touch, Andrew Yourtchenko and Lucy Yong
thorough review and useful comments. for their thorough review and useful comments.
8. Normative References 8. Normative References
[ETYPES] IANA, "ETHER TYPES", 2014, [ETYPES] IANA, "ETHER TYPES", 2014,
<http://www.iana.org/assignments/ieee-802-numbers/ <http://www.iana.org/assignments/ieee-802-numbers/
ieee-802-numbers.xhtml#ieee-802-numbers-1>. ieee-802-numbers.xhtml#ieee-802-numbers-1>.
[RFC0791] Postel, J., "Internet Protocol", STD 5, RFC 791, September [RFC0791] Postel, J., "Internet Protocol", STD 5, RFC 791, September
1981. 1981.
 End of changes. 8 change blocks. 
11 lines changed or deleted 24 lines changed or added

This html diff was produced by rfcdiff 1.42. The latest version is available from http://tools.ietf.org/tools/rfcdiff/