Internet DRAFT - draft-li-nvo3-clouddatacenter-requirement
draft-li-nvo3-clouddatacenter-requirement
Network Virtualization Overlays Chen. Li
Internet-Draft Rong. Gu
Intended status: Standards Track China Mobile
Expires: January 13, 2014 July 12, 2013
Network as a service requirement in cloud datacenter
draft-li-nvo3-clouddatacenter-requirement-00
Abstract
This document describes some specific features in CDC, especially in
the public cloud.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on January 13, 2014.
Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
This document may contain material from IETF Documents or IETF
Contributions published or made publicly available before November
Li & Gu Expires January 13, 2014 [Page 1]
Internet-Draft NAAS requirement in CDC July 2013
10, 2008. The person(s) controlling the copyright in some of this
material may not have granted the IETF Trust the right to allow
modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) controlling
the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other
than English.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Problem statement . . . . . . . . . . . . . . . . . . . . . . 2
3. Solution . . . . . . . . . . . . . . . . . . . . . . . . . . 3
4. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 3
5. References . . . . . . . . . . . . . . . . . . . . . . . . . 3
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 3
1. Introduction
CDC (Cloud Data Center) network has the fastest innovation of the
network standards and the most proposed technology. Especially in
the public clouds. From our prespective, there are several network
capacity can be sold by public clouds' operator: IP address, VLAN,
bandwidth, loadbalance, firewall and some other network resouces.
The target of NAAS(network as a service) is to provide end to end
virual network with above capacity for tenants in datacenter.
However, many taditional tochonlogy become the bottleneck of public
cloud service, such as the number of VLAN. It becomes unable to meet
the constantly updated needs of providing users with the hosted
networks for the data segregation.
In this draft, we forcus on proposing network requirement of NAAS.
2. Problem statement
NAAS is supposed to provide a virtual CDC network for a tenant. we
propose four specific network features of NAAS as follows
a. The isolation of different tenants
Different tenants are isolated by vpn, No matter layer 2 or layer 3,
no matter by vlan tag or mpls tag or some others. Meanwhile, the
network service devices, such as loadbalance and firewall, also need
to be isolated.tenants have a logical isolated network, which can be
implement any IP and VLAN by themselves (different tenants should
reused IP/VLAN).
Li & Gu Expires January 13, 2014 [Page 2]
Internet-Draft NAAS requirement in CDC July 2013
b. tenant's logical network in GUI
tenant's logical network GUI should be simple and intuitive. For
example it only display a L2 switch, a L3 gateway, a broader router,
a loadbalance, a firewall and some other security devices. All the
link is logical. VMs or servers connect to these logical network
devices.
c. bandwidth guarantee
Each logical network should allocate the specific end to end
bandwidth, including server uplink switch port rate, switch to
gateway link rate, gateway to LB/FW link rate and broader router link
rate.
all the logical bandwidth allocation should map in physical network
devices.
d. self network management
Each tenant manage and config their own logical network. While
operator is responsible for the physical one.
3. Solution
to be continued.
4. Acknowledgements
5. References
Authors' Addresses
Chen Li
China Mobile
Unit2, Dacheng Plaza, No.28 Xuanwumenxi Ave, Xuanwu District
Beijing 100053
P.R. China
Email: lichenyj@chinamobile.com
Li & Gu Expires January 13, 2014 [Page 3]
Internet-Draft NAAS requirement in CDC July 2013
Rong Gu
China Mobile
Unit2, Dacheng Plaza, No.28 Xuanwumenxi Ave, Xuanwu District
Beijing 100053
P.R. China
Email: arielgurong@gmail.com
Li & Gu Expires January 13, 2014 [Page 4]
