RFC 7364 on Problem Statement: Overlays for Network Virtualization
rfc-editor@rfc-editor.org Fri, 10 October 2014 20:47 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7D4161AD0D7; Fri, 10 Oct 2014 13:47:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.688
X-Spam-Level:
X-Spam-Status: No, score=-102.688 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.786, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id E7gkwwg5RYne; Fri, 10 Oct 2014 13:47:00 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) by ietfa.amsl.com (Postfix) with ESMTP id 163E51AD17F; Fri, 10 Oct 2014 13:47:00 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id BC786181C7C; Fri, 10 Oct 2014 13:46:04 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7364 on Problem Statement: Overlays for Network Virtualization
X-PHP-Originating-Script: 6000:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20141010204604.BC786181C7C@rfc-editor.org>
Date: Fri, 10 Oct 2014 13:46:04 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf-announce/EgtVcxfzqdYV8iYxXOR9gNN9ak4
Cc: drafts-update-ref@iana.org, nvo3@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: ietf@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Oct 2014 20:47:03 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 7364
Title: Problem Statement: Overlays for Network
Virtualization
Author: T. Narten, Ed.,
E. Gray, Ed.,
D. Black, L. Fang,
L. Kreeger, M. Napierala
Status: Informational
Stream: IETF
Date: October 2014
Mailbox: narten@us.ibm.com,
Eric.Gray@Ericsson.com,
david.black@emc.com,
lufang@microsoft.com,
kreeger@cisco.com,
mnapierala@att.com
Pages: 23
Characters: 57831
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-nvo3-overlay-problem-statement-04.txt
URL: https://www.rfc-editor.org/rfc/rfc7364.txt
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.
This document is a product of the Network Virtualization Overlays Working Group of the IETF.
INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/rfc.html
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC