draft-ietf-intarea-gre-ipv6-05.txt   draft-ietf-intarea-gre-ipv6-06.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 12, 2015 S. Krishnan Expires: October 13, 2015 S. Krishnan
Ericsson Ericsson
April 10, 2015 April 11, 2015
IPv6 Support for Generic Routing Encapsulation (GRE) IPv6 Support for Generic Routing Encapsulation (GRE)
draft-ietf-intarea-gre-ipv6-05 draft-ietf-intarea-gre-ipv6-06
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 12, 2015. This Internet-Draft will expire on October 13, 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 36 skipping to change at page 2, line 36
3. IPv6 As GRE Payload . . . . . . . . . . . . . . . . . . . . . 4 3. IPv6 As GRE Payload . . . . . . . . . . . . . . . . . . . . . 4
3.1. GRE Protocol Type Considerations . . . . . . . . . . . . 4 3.1. GRE Protocol Type Considerations . . . . . . . . . . . . 4
3.2. MTU Considerations . . . . . . . . . . . . . . . . . . . 4 3.2. MTU Considerations . . . . . . . . . . . . . . . . . . . 4
3.3. Fragmentation Considerations . . . . . . . . . . . . . . 4 3.3. Fragmentation Considerations . . . . . . . . . . . . . . 4
4. IPv6 As GRE Delivery Protocol . . . . . . . . . . . . . . . . 5 4. IPv6 As GRE Delivery Protocol . . . . . . . . . . . . . . . . 5
4.1. Next Header Considerations . . . . . . . . . . . . . . . 5 4.1. Next Header Considerations . . . . . . . . . . . . . . . 5
4.2. Checksum Considerations . . . . . . . . . . . . . . . . . 5 4.2. Checksum Considerations . . . . . . . . . . . . . . . . . 5
4.3. MTU Considerations . . . . . . . . . . . . . . . . . . . 6 4.3. MTU Considerations . . . . . . . . . . . . . . . . . . . 6
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6
6. Security Considerations . . . . . . . . . . . . . . . . . . . 6 6. Security Considerations . . . . . . . . . . . . . . . . . . . 6
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 6 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 7
8. Normative References . . . . . . . . . . . . . . . . . . . . 7 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 7
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 7 8.1. Normative References . . . . . . . . . . . . . . . . . . 7
8.2. Informative References . . . . . . . . . . . . . . . . . 8
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8
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 6, line 43 skipping to change at page 6, line 46
delivery header. However, implementations MAY support an optional delivery header. However, implementations MAY support an optional
configuration in which the GRE egress node can reassemble the IPv6 configuration in which the GRE egress node can reassemble the IPv6
delivery header. delivery header.
5. IANA Considerations 5. IANA Considerations
This document makes no request of IANA. This document makes no request of IANA.
6. Security Considerations 6. Security Considerations
The Security Considerations section of [RFC4023] addresses MPLS in The Security Considerations section of [RFC4023] identifies threats
GRE. However, it applies equally to the current specification. encountered when MPLS is deliver over GRE. These threats apply to
Beyond that, the current specification introduces no security any GRE payload. As stated in RFC 4023, these threats can be
considerations beyond those mentioned in RFC 2784. mitigated by authenticating and/or encrypting the delivery packet
using IPSec [RFC4301]. Alternatively when the payload is IPv6, these
threats can also be mitigated by authenticating and/or encrypting the
payload using IPSec, instead of the delivery packet. Otherwise, the
current specification introduces no security considerations beyond
those mentioned in RFC 2784.
More generically, security considerations for IPv6 are discussed in
[RFC4942]. operational security for IPv6 is discussed in
[I-D.ietf-opsec-v6], and security concerns for tunnels in general are
discussed in [RFC6169].
7. Acknowledgements 7. Acknowledgements
The authors would like to thank Fred Baker, Stewart Bryant, Dino The authors would like to thank Fred Baker, Stewart Bryant, Dino
Farinacci, Tom Herbert, Fred Templin, Joe Touch, Andrew Yourtchenko Farinacci, David Farmer, Tom Herbert, Fred Templin, Joe Touch, Andrew
and Lucy Yong for their thorough review and useful comments. Yourtchenko and Lucy Yong for their thorough review and useful
comments.
8. Normative References 8. References
8.1. 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.
[RFC1981] McCann, J., Deering, S., and J. Mogul, "Path MTU Discovery [RFC1981] McCann, J., Deering, S., and J. Mogul, "Path MTU Discovery
for IP version 6", RFC 1981, August 1996. for IP version 6", RFC 1981, August 1996.
skipping to change at page 7, line 34 skipping to change at page 7, line 50
Traina, "Generic Routing Encapsulation (GRE)", RFC 2784, Traina, "Generic Routing Encapsulation (GRE)", RFC 2784,
March 2000. March 2000.
[RFC2890] Dommety, G., "Key and Sequence Number Extensions to GRE", [RFC2890] Dommety, G., "Key and Sequence Number Extensions to GRE",
RFC 2890, September 2000. RFC 2890, September 2000.
[RFC4023] Worster, T., Rekhter, Y., and E. Rosen, "Encapsulating [RFC4023] Worster, T., Rekhter, Y., and E. Rosen, "Encapsulating
MPLS in IP or Generic Routing Encapsulation (GRE)", RFC MPLS in IP or Generic Routing Encapsulation (GRE)", RFC
4023, March 2005. 4023, March 2005.
[RFC4301] Kent, S. and K. Seo, "Security Architecture for the
Internet Protocol", RFC 4301, December 2005.
[RFC4443] Conta, A., Deering, S., and M. Gupta, "Internet Control [RFC4443] Conta, A., Deering, S., and M. Gupta, "Internet Control
Message Protocol (ICMPv6) for the Internet Protocol Message Protocol (ICMPv6) for the Internet Protocol
Version 6 (IPv6) Specification", RFC 4443, March 2006. Version 6 (IPv6) Specification", RFC 4443, March 2006.
8.2. Informative References
[I-D.ietf-opsec-v6]
Chittimaneni, K., Kaeo, M., and E. Vyncke, "Operational
Security Considerations for IPv6 Networks", draft-ietf-
opsec-v6-06 (work in progress), March 2015.
[RFC4942] Davies, E., Krishnan, S., and P. Savola, "IPv6 Transition/
Co-existence Security Considerations", RFC 4942, September
2007.
[RFC6169] Krishnan, S., Thaler, D., and J. Hoagland, "Security
Concerns with IP Tunneling", RFC 6169, April 2011.
Authors' Addresses Authors' Addresses
Carlos Pignataro Carlos Pignataro
Cisco Systems Cisco Systems
7200-12 Kit Creek Road 7200-12 Kit Creek Road
Research Triangle Park, North Carolina 27709 Research Triangle Park, North Carolina 27709
USA USA
Email: cpignata@cisco.com Email: cpignata@cisco.com
Ron Bonica Ron Bonica
Juniper Networks Juniper Networks
2251 Corporate Park Drive 2251 Corporate Park Drive
Herndon, Virginia Herndon, Virginia
USA USA
Email: rbonica@juniper.net Email: rbonica@juniper.net
Suresh Krishnan Suresh Krishnan
Ericsson Ericsson
 End of changes. 11 change blocks. 
14 lines changed or deleted 47 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/