draft-ietf-tsvwg-gre-in-udp-encap-14.txt   draft-ietf-tsvwg-gre-in-udp-encap-15.txt 
Network Working Group Lucy Yong(Ed.) Network Working Group Lucy Yong(Ed.)
Internet-Draft Huawei Technologies Internet-Draft Huawei Technologies
Intended status: Standard Track E. Crabbe Intended status: Standard Track E. Crabbe
Oracle Oracle
X. Xu X. Xu
Huawei Technologies Huawei Technologies
T. Herbert T. Herbert
Facebook Facebook
Expires: January 2017 July 17, 2016 Expires: January 2017 July 18, 2016
GRE-in-UDP Encapsulation GRE-in-UDP Encapsulation
draft-ietf-tsvwg-gre-in-udp-encap-14 draft-ietf-tsvwg-gre-in-udp-encap-15
Abstract Abstract
This document specifies a method of encapsulating network protocol This document specifies a method of encapsulating network protocol
packet within GRE and UDP headers. This GRE-in-UDP encapsulation packet within GRE and UDP headers. This GRE-in-UDP encapsulation
allows the UDP source port field to be used as an entropy field. allows the UDP source port field to be used as an entropy field.
This may be used for load balancing of GRE traffic in transit This may be used for load balancing of GRE traffic in transit
networks using existing ECMP mechanisms. This document also networks using existing ECMP mechanisms. This document also
specifies GRE-in-UDP tunnel requirements for two applicability specifies GRE-in-UDP tunnel requirements for two applicability
scenarios: (1) general Internet; (2) a traffic-managed controlled scenarios: (1) general Internet; (2) a traffic-managed controlled
skipping to change at page 1, line 43 skipping to change at page 1, line 43
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 Internet-Drafts are draft documents valid for a maximum of six
months and may be updated, replaced, or obsoleted by other documents months and may be updated, replaced, or obsoleted by other documents
at any time. It is inappropriate to use Internet-Drafts as reference at any 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 January 17,2017. This Internet-Draft will expire on January 18,2017.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2016 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 5, line 26 skipping to change at page 5, line 26
Internet and GRE-in-UDP tunnel usage in a traffic-managed controlled Internet and GRE-in-UDP tunnel usage in a traffic-managed controlled
environment and uses "default GRE-in-UDP tunnel" and "TMCE GRE-in- environment and uses "default GRE-in-UDP tunnel" and "TMCE GRE-in-
UDP tunnel" terms to refer to each usage. UDP tunnel" terms to refer to each usage.
2.1. GRE-in-UDP Tunnel Requirements 2.1. GRE-in-UDP Tunnel Requirements
This section states out the requirements for a GRE-in-UDP tunnel. This section states out the requirements for a GRE-in-UDP tunnel.
Section 2.1.1 describes the requirements for a default GRE-in-UDP Section 2.1.1 describes the requirements for a default GRE-in-UDP
tunnel that is suitable for the general Internet; Section 2.1.2 tunnel that is suitable for the general Internet; Section 2.1.2
describes a set of relaxed requirements for a TMCE GRE-in-UDP tunnel describes a set of relaxed requirements for a TMCE GRE-in-UDP tunnel
used in a traffic-managed controlled environment. Both Sections used in a traffic-managed controlled environment. Both Setions 2.1.1
2.1.1 and 2.1.2 are applicable to an IPv4 or IPv6 delivery network. and 2.1.2 are applicable to an IPv4 or IPv6 delivery network.
2.1.1. Requirements for Default GRE-in-UDP Tunnel 2.1.1. Requirements for Default GRE-in-UDP Tunnel
The following is a summary of the default GRE-in-UDP tunnel The following is a summary of the default GRE-in-UDP tunnel
requirements: requirements:
1. A UDP checksum SHOULD be used when encapsulating in IPv4. 1. A UDP checksum SHOULD be used when encapsulating in IPv4.
2. A UDP checksum MUST be used when encapsulating in IPv6. 2. A UDP checksum MUST be used when encapsulating in IPv6.
skipping to change at page 6, line 17 skipping to change at page 6, line 17
single value is set, a random port SHOULD be selected in order to single value is set, a random port SHOULD be selected in order to
minimize the vulnerability to off-path attacks [RFC6056]. minimize the vulnerability to off-path attacks [RFC6056].
6. For IPv6 delivery networks, the flow entropy SHOULD also be 6. For IPv6 delivery networks, the flow entropy SHOULD also be
placed in the flow label field for ECMP per [RFC6438]. placed in the flow label field for ECMP per [RFC6438].
7. At the tunnel ingress, any fragmentation of the incoming packet 7. At the tunnel ingress, any fragmentation of the incoming packet
(e.g., because the tunnel has an MTU that is smaller than the packet) (e.g., because the tunnel has an MTU that is smaller than the packet)
SHOULD be performed before encapsulation. In addition, the tunnel SHOULD be performed before encapsulation. In addition, the tunnel
ingress MUST apply the UDP checksum to all encapsulated fragments so ingress MUST apply the UDP checksum to all encapsulated fragments so
that the tunnel egress can validate reassembly of the fragments; it that the tunnel egress can validate resemble of the fragments; it
MUST set the same DSCP value as in the DS field of the payload MUST set the same DSCP value as in the DS field of the payload
packet in all fragments [RFC2474]. To avoid unwanted forwarding over packet in all fragments [RFC2474]. To avoid unwanted forwarding over
multiple paths, the same source UDP port value SHOULD be set in all multiple paths, the same source UDP port value SHOULD be set in all
packet fragments. packet fragments.
2.1.2. Requirements for TMCE GRE-in-UDP Tunnel 2.1.2. Requirements for TMCE GRE-in-UDP Tunnel
The section contains the TMCE GRE-in-UDP tunnel requirements. It The section contains the TMCE GRE-in-UDP tunnel requirements. It
lists the changed requirements, compared with a Default GRE-in-UDP lists the changed requirements, compared with a Default GRE-in-UDP
Tunnel, for a TMCE GRE-in-UDP Tunnel, which corresponds to the Tunnel, for a TMCE GRE-in-UDP Tunnel, which corresponds to the
 End of changes. 5 change blocks. 
6 lines changed or deleted 6 lines changed or added

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