Search RFCs

RFC Editor

File formats:

Status:

INFORMATIONAL

Authors:

T. Narten, Ed.
E. Gray, Ed.
D. Black
L. Fang
L. Kreeger
M. Napierala

Stream:

IETF

Source:

nvo3 (rtg)

Cite this RFC:TXT  | XML  |  BibTeX

DOI:  https://doi.org/10.17487/RFC7364

Discuss this RFC: Send questions or comments to the mailing listnvo3@ietf.org

Other actions:Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC 7364

Abstract

This document describes issues associated with providing multi-tenancy inlarge data center networks and how these issues may beaddressed using an overlay-based network virtualization approach. Akey multi-tenancy requirement is traffic isolation so that onetenant's traffic is not visible to any other tenant. Anotherrequirement is address space isolation so that different tenants canuse the same address space within different virtual networks.Traffic and address space isolation is achieved by assigning one ormore virtual networks to each tenant, where traffic within a virtualnetwork can only cross into another virtual network in a controlledfashion (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 theappropriate virtual network and maintaining that association as thevirtual machine is activated, migrated, and/or deactivated. Use ofan overlay-based approach enables scalable deployment on largenetwork infrastructures.

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.