draft-ietf-nvo3-geneve-15.txt   draft-ietf-nvo3-geneve-16.txt 
Network Working Group J. Gross, Ed. Network Working Group J. Gross, Ed.
Internet-Draft Internet-Draft
Intended status: Standards Track I. Ganga, Ed. Intended status: Standards Track I. Ganga, Ed.
Expires: September 1, 2020 Intel Expires: September 8, 2020 Intel
T. Sridhar, Ed. T. Sridhar, Ed.
VMware VMware
February 29, 2020 March 07, 2020
Geneve: Generic Network Virtualization Encapsulation Geneve: Generic Network Virtualization Encapsulation
draft-ietf-nvo3-geneve-15 draft-ietf-nvo3-geneve-16
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 42 skipping to change at page 1, line 42
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 https://datatracker.ietf.org/drafts/current/. Drafts is at https://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 1, 2020. This Internet-Draft will expire on September 8, 2020.
Copyright Notice Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the Copyright (c) 2020 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
(https://trustee.ietf.org/license-info) in effect on the date of (https://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 30, line 9 skipping to change at page 30, line 9
be used as a control plane for configuring and managing the Geneve be used as a control plane for configuring and managing the Geneve
NVEs. The data center operator is expected to use security NVEs. The data center operator is expected to use security
mechanisms to protect the communications between the NVA to NVEs and mechanisms to protect the communications between the NVA to NVEs and
use authentication mechanisms to detect any rogue or compromised NVEs use authentication mechanisms to detect any rogue or compromised NVEs
within their administrative domain. Data protection mechanisms for within their administrative domain. Data protection mechanisms for
control plane communication or authentication mechanisms between the control plane communication or authentication mechanisms between the
NVA and the NVEs are beyond the scope of this document. NVA and the NVEs are beyond the scope of this document.
7. IANA Considerations 7. IANA Considerations
IANA has allocated UDP port 6081 as the well-known destination port IANA has allocated UDP port 6081 in the Service Name and Transport
for Geneve. An early registration for Geneve has been made at the Protocol Port Number Registry [IANA-SN] as the well-known destination
Service Name and Transport Protocol Port Number Registry [IANA-SN] as port for Geneve based on early registration.
noted below:
Upon publication of this document, this registration will have its
reference changed to cite this document [RFC-to-be] and inline with
[RFC6335] the assignee and contact of the port entry should be
changed to IESG <iesg@ietf.org> and IETF Chair <chair@ietf.org>
respectively:
Service Name: geneve Service Name: geneve
Transport Protocol(s): UDP Transport Protocol(s): UDP
Assignee: Jesse Gross <jesse@kernel.org> Assignee: IESG <iesg@ietf.org>
Contact: Jesse Gross <jesse@kernel.org> Contact: IETF Chair <chair@ietf.org>
Description: Generic Network Virtualization Encapsulation (Geneve) Description: Generic Network Virtualization Encapsulation (Geneve)
Reference: This document Reference: [RFC-to-be]
Port Number: 6081 Port Number: 6081
Upon publication of this document, this registration will have its
reference changed to cite this document [RFC-to-be] and inline with
[RFC6335] the Assignee and Contact of the port entry should be
changed to IESG <iesg@ietf.org> and IETF Chair <chair@ietf.org>
respectively.
In addition, IANA is requested to create a new "Geneve Option Class" In addition, IANA is requested to create a new "Geneve Option Class"
registry to allocate Option Classes. This registry is to be placed registry to allocate Option Classes. This registry is to be placed
under a new Network Virtualization Overlay (NVO3) protocols page (to under a new Network Virtualization Overlay (NVO3) protocols page (to
be created) in IANA protocol registries [IANA-PR]. The Geneve Option be created) in IANA protocol registries [IANA-PR]. The Geneve Option
Class registry shall consist of 16-bit hexadecimal values along with Class registry shall consist of 16-bit hexadecimal values along with
descriptive strings, Assignee/Contact information and References. descriptive strings, assignee/contact information and references.
The registration rules for the new registry are (as defined by The registration rules for the new registry are (as defined by
[RFC8126]): [RFC8126]):
+----------------+-------------------------+ +----------------+-------------------------+
| Range | Registration Procedures | | Range | Registration Procedures |
+----------------+-------------------------+ +----------------+-------------------------+
| 0x0000..0x00FF | IETF Review | | 0x0000..0x00FF | IETF Review |
| 0x0100..0xFEFF | First Come First Served | | 0x0100..0xFEFF | First Come First Served |
| 0xFF00..0xFFFF | Experimental Use | | 0xFF00..0xFFFF | Experimental Use |
+----------------+-------------------------+ +----------------+-------------------------+
Inital registrations in the new registry are as follows: Initial registrations in the new registry are as follows:
+----------------+------------------+------------------+------------+ +----------------+------------------+------------------+------------+
| Option Class | Description | Assignee/Contact | References | | Option Class | Description | Assignee/Contact | References |
+----------------+------------------+------------------+------------+ +----------------+------------------+------------------+------------+
| 0x0100 | Linux | | | | 0x0100 | Linux | | |
| 0x0101 | Open vSwitch | | | | 0x0101 | Open vSwitch | | |
| | (OVS) | | | | | (OVS) | | |
| 0x0102 | Open Virtual | | | | 0x0102 | Open Virtual | | |
| | Networking (OVN) | | | | | Networking (OVN) | | |
| 0x0103 | In-band Network | | | | 0x0103 | In-band Network | | |
skipping to change at page 36, line 48 skipping to change at page 36, line 48
[RFC8293] Ghanwani, A., Dunbar, L., McBride, M., Bannai, V., and R. [RFC8293] Ghanwani, A., Dunbar, L., McBride, M., Bannai, V., and R.
Krishnan, "A Framework for Multicast in Network Krishnan, "A Framework for Multicast in Network
Virtualization over Layer 3", RFC 8293, Virtualization over Layer 3", RFC 8293,
DOI 10.17487/RFC8293, January 2018, DOI 10.17487/RFC8293, January 2018,
<https://www.rfc-editor.org/info/rfc8293>. <https://www.rfc-editor.org/info/rfc8293>.
[VL2] "VL2: A Scalable and Flexible Data Center Network", ACM [VL2] "VL2: A Scalable and Flexible Data Center Network", ACM
SIGCOMM Computer Communication Review, SIGCOMM Computer Communication Review,
DOI 10.1145/1594977.1592576, 2009, DOI 10.1145/1594977.1592576, 2009,
<http://www.sigcomm.org/sites/default/files/ccr/ <https://www.sigcomm.org/sites/default/files/ccr/
papers/2009/October/1594977-1592576.pdf>. papers/2009/October/1594977-1592576.pdf>.
Authors' Addresses Authors' Addresses
Jesse Gross (editor) Jesse Gross (editor)
Email: jesse@kernel.org Email: jesse@kernel.org
Ilango Ganga (editor) Ilango Ganga (editor)
Intel Corporation Intel Corporation
 End of changes. 11 change blocks. 
20 lines changed or deleted 19 lines changed or added

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