RFC 7364: Problem Statement: Overlays for Network Virtualization
In plain English — editorial summary, not part of the RFC
This document describes issues associated with providing multi-tenancy in large data center networks and how these issues may be addressed using an overlay-based network virtualization approach. A key multi-tenancy requirement is traffic isolation so that one tenant's traffic is not visible to any other tenant. Another requirement is address space isolation so that different tenants can use the same address space within different virtual networks. Traffic and address space isolation is achieved by assigning one or more virtual networks to each tenant, where traffic within a virtual network can only cross into another virtual network in a controlled fashion (e.g., via a configured router and/or a security gateway). Additional functionality is required to provision virtual networks, associating a virtual machine's network interface(s) with the appropriate virtual network and maintaining that association as the virtual machine is activated, migrated, and/or deactivated. Use of an overlay-based approach enables scalable deployment on large network infrastructures.
Document record
- Document ID
- RFC7364
- Published
- October 2014
- Authors
- T. Narten; E. Gray; D. Black; L. Fang; L. Kreeger; M. Napierala
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rtg
- Pages
- 23
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7365Framework for Data Center (DC) Network VirtualizationCurrent
October 2014
- RFC 7361LDP Extensions for Optimized MAC Address Withdrawal in a Hierarchical Virtual Private LAN Service (H-VPLS)Current
September 2014
- RFC 7367Definition of Managed Objects for the Mobile Ad Hoc Network (MANET) Simplified Multicast Framework Relay Set ProcessCurrent
October 2014
- RFC 7369GMPLS RSVP-TE Extensions for Ethernet Operations, Administration, and Maintenance (OAM) ConfigurationCurrent
October 2014
- RFC 7370Updates to the IS-IS TLV Codepoints RegistryUpdated
September 2014
- RFC 7358Label Advertisement Discipline for LDP Forwarding Equivalence Classes (FECs)Current
October 2014
- RFC 7357Transparent Interconnection of Lots of Links (TRILL): End Station Address Distribution Information (ESADI) ProtocolCurrent
September 2014
- RFC 7356IS-IS Flooding Scope Link State PDUs (LSPs)Current
September 2014
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?