draft-ietf-nvo3-geneve-02.txt   draft-ietf-nvo3-geneve-03.txt 
Network Working Group J. Gross, Ed. Network Working Group J. Gross, Ed.
Internet-Draft VMware Internet-Draft
Intended status: Standards Track I. Ganga, Ed. Intended status: Standards Track I. Ganga, Ed.
Expires: January 9, 2017 Intel Expires: March 24, 2017 Intel
July 8, 2016 T. Sridhar, Ed.
VMware
September 20, 2016
Geneve: Generic Network Virtualization Encapsulation Geneve: Generic Network Virtualization Encapsulation
draft-ietf-nvo3-geneve-02 draft-ietf-nvo3-geneve-03
Abstract Abstract
Network virtualization involves the cooperation of devices with a Network virtualization involves the cooperation of devices with a
wide variety of capabilities such as software and hardware tunnel wide variety of capabilities such as software and hardware tunnel
endpoints, transit fabrics, and centralized control clusters. As a endpoints, transit fabrics, and centralized control clusters. As a
result of their role in tying together different elements in the result of their role in tying together different elements in the
system, the requirements on tunnels are influenced by all of these system, the requirements on tunnels are influenced by all of these
components. Flexibility is therefore the most important aspect of a components. Flexibility is therefore the most important aspect of a
tunnel protocol if it is to keep pace with the evolution of the tunnel protocol if it is to keep pace with the evolution of the
skipping to change at page 1, line 39 skipping to change at page 1, line 41
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 January 9, 2017. This Internet-Draft will expire on March 24, 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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Requirements Language . . . . . . . . . . . . . . . . . . 4 1.1. Requirements Language . . . . . . . . . . . . . . . . . . 4
1.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 4 1.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 4
2. Design Requirements . . . . . . . . . . . . . . . . . . . . . 5 2. Design Requirements . . . . . . . . . . . . . . . . . . . . . 5
2.1. Control Plane Independence . . . . . . . . . . . . . . . 6 2.1. Control Plane Independence . . . . . . . . . . . . . . . 6
2.2. Data Plane Extensibility . . . . . . . . . . . . . . . . 7 2.2. Data Plane Extensibility . . . . . . . . . . . . . . . . 7
2.2.1. Efficient Implementation . . . . . . . . . . . . . . 7 2.2.1. Efficient Implementation . . . . . . . . . . . . . . 7
2.3. Use of Standard IP Fabrics . . . . . . . . . . . . . . . 8 2.3. Use of Standard IP Fabrics . . . . . . . . . . . . . . . 8
3. Geneve Encapsulation Details . . . . . . . . . . . . . . . . 9 3. Geneve Encapsulation Details . . . . . . . . . . . . . . . . 9
3.1. Geneve Packet Format Over IPv4 . . . . . . . . . . . . . 9 3.1. Geneve Packet Format Over IPv4 . . . . . . . . . . . . . 9
3.2. Geneve Packet Format Over IPv6 . . . . . . . . . . . . . 10 3.2. Geneve Packet Format Over IPv6 . . . . . . . . . . . . . 10
skipping to change at page 2, line 40 skipping to change at page 2, line 42
4.1.2. DSCP and ECN . . . . . . . . . . . . . . . . . . . . 17 4.1.2. DSCP and ECN . . . . . . . . . . . . . . . . . . . . 17
4.1.3. Broadcast and Multicast . . . . . . . . . . . . . . . 18 4.1.3. Broadcast and Multicast . . . . . . . . . . . . . . . 18
4.1.4. Unidirectional Tunnels . . . . . . . . . . . . . . . 18 4.1.4. Unidirectional Tunnels . . . . . . . . . . . . . . . 18
4.2. Constraints on Protocol Features . . . . . . . . . . . . 19 4.2. Constraints on Protocol Features . . . . . . . . . . . . 19
4.3. NIC Offloads . . . . . . . . . . . . . . . . . . . . . . 19 4.3. NIC Offloads . . . . . . . . . . . . . . . . . . . . . . 19
4.4. Inner VLAN Handling . . . . . . . . . . . . . . . . . . . 20 4.4. Inner VLAN Handling . . . . . . . . . . . . . . . . . . . 20
5. Interoperability Issues . . . . . . . . . . . . . . . . . . . 20 5. Interoperability Issues . . . . . . . . . . . . . . . . . . . 20
6. Security Considerations . . . . . . . . . . . . . . . . . . . 21 6. Security Considerations . . . . . . . . . . . . . . . . . . . 21
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 21 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 21
8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 22 8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 22
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 24 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 23
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 24 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 23
10.1. Normative References . . . . . . . . . . . . . . . . . . 24 10.1. Normative References . . . . . . . . . . . . . . . . . . 23
10.2. Informative References . . . . . . . . . . . . . . . . . 24 10.2. Informative References . . . . . . . . . . . . . . . . . 24
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 26 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 25
1. Introduction 1. Introduction
Networking has long featured a variety of tunneling, tagging, and Networking has long featured a variety of tunneling, tagging, and
other encapsulation mechanisms. However, the advent of network other encapsulation mechanisms. However, the advent of network
virtualization has caused a surge of renewed interest and a virtualization has caused a surge of renewed interest and a
corresponding increase in the introduction of new protocols. The corresponding increase in the introduction of new protocols. The
large number of protocols in this space, ranging all the way from large number of protocols in this space, ranging all the way from
VLANs [IEEE.802.1Q-2014] and MPLS [RFC3031] through the more recent VLANs [IEEE.802.1Q-2014] and MPLS [RFC3031] through the more recent
VXLAN [RFC7348], NVGRE [RFC7637], and STT [I-D.davie-stt], often VXLAN [RFC7348], NVGRE [RFC7637], and STT [I-D.davie-stt], often
skipping to change at page 22, line 25 skipping to change at page 22, line 25
| 0x0104 | VMware | | 0x0104 | VMware |
| 0x0105..0xFFEF | Unassigned - First Come First Served | | 0x0105..0xFFEF | Unassigned - First Come First Served |
| 0xFFF0..FFFF | Experimental | | 0xFFF0..FFFF | Experimental |
+----------------+--------------------------------------+ +----------------+--------------------------------------+
8. Contributors 8. Contributors
The following individuals were authors of an earlier version of this The following individuals were authors of an earlier version of this
document and made significant contributions: document and made significant contributions:
T. Sridhar
VMware, Inc.
3401 Hillview Ave.
Palo Alto, CA 94304
USA
Email: tsridhar@vmware.com
Pankaj Garg Pankaj Garg
Microsoft Corporation Microsoft Corporation
1 Microsoft Way 1 Microsoft Way
Redmond, WA 98052 Redmond, WA 98052
USA USA
Email: pankajg@microsoft.com Email: pankajg@microsoft.com
Chris Wright Chris Wright
Red Hat Inc. Red Hat Inc.
skipping to change at page 26, line 8 skipping to change at page 25, line 43
<http://www.rfc-editor.org/info/rfc7637>. <http://www.rfc-editor.org/info/rfc7637>.
[VL2] Greenberg et al, , "VL2: A Scalable and Flexible Data [VL2] Greenberg et al, , "VL2: A Scalable and Flexible Data
Center Network", 2009. Center Network", 2009.
Proc. ACM SIGCOMM 2009 Proc. ACM SIGCOMM 2009
Authors' Addresses Authors' Addresses
Jesse Gross (editor) Jesse Gross (editor)
VMware, Inc.
3401 Hillview Ave.
Palo Alto, CA 94304
USA
Email: jgross@vmware.com
Email: jesse@kernel.org
Ilango Ganga (editor) Ilango Ganga (editor)
Intel Corporation Intel Corporation
2200 Mission College Blvd. 2200 Mission College Blvd.
Santa Clara, CA 95054 Santa Clara, CA 95054
USA USA
Email: ilango.s.ganga@intel.com Email: ilango.s.ganga@intel.com
T. Sridhar (editor)
VMware, Inc.
3401 Hillview Ave.
Palo Alto, CA 94304
USA
Email: tsridhar@vmware.com
 End of changes. 11 change blocks. 
24 lines changed or deleted 13 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/