draft-ietf-intarea-gre-ipv6-06.txt   draft-ietf-intarea-gre-ipv6-07.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: October 13, 2015 S. Krishnan Expires: October 15, 2015 S. Krishnan
Ericsson Ericsson
April 11, 2015 April 13, 2015
IPv6 Support for Generic Routing Encapsulation (GRE) IPv6 Support for Generic Routing Encapsulation (GRE)
draft-ietf-intarea-gre-ipv6-06 draft-ietf-intarea-gre-ipv6-07
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 October 13, 2015. This Internet-Draft will expire on October 15, 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 6, line 21 skipping to change at page 6, line 21
destination destination
c. De-encapsulate the payload and forward it to a node other than c. De-encapsulate the payload and forward it to a node other than
its intended destination. For example, the payload might be its intended destination. For example, the payload might be
intended for a node on one VPN, but delivered to an identically intended for a node on one VPN, but delivered to an identically
numbered node in another VPN. numbered node in another VPN.
Behaviors a) and b) are acceptable. Behavior c) is not acceptable. Behaviors a) and b) are acceptable. Behavior c) is not acceptable.
Before deploying GRE over IPv6, network operators should consider the Before deploying GRE over IPv6, network operators should consider the
likelihood of behavior c) in their network. GRE over IPv6 is likelihood of behavior c) in their network. GRE over IPv6 is MUST
deployable only in environments where the network operator deems the NOT be deployed other than where the network operator deems the risk
risk associated with behavior c) to be acceptable. associated with behavior c) to be acceptable.
The risk associated with behavior c) could be mitigated with end-to- The risk associated with behavior c) could be mitigated with end-to-
end authentication of the payload. end authentication of the payload.
4.3. MTU Considerations 4.3. MTU Considerations
By default, the GRE ingress node cannot fragment the IPv6 delivery By default, the GRE ingress node cannot fragment the IPv6 delivery
header. However, implementations MAY support an optional header. However, implementations MAY support an optional
configuration in which the GRE ingress node can fragment the IPv6 configuration in which the GRE ingress node can fragment the IPv6
delivery header. delivery header.
 End of changes. 5 change blocks. 
7 lines changed or deleted 7 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/