Internet DRAFT - draft-huang-nvo3-naas-usecases

draft-huang-nvo3-naas-usecases







nvo3                                                       L. Huang, Ed.
Internet-Draft                                                R. Gu, Ed.
Intended status: Informational                              China Mobile
Expires: April 30, 2015                                           L. Xia
                                                     Huawei Technologies
                                                                   Q. Zu
                                                                Ericsson
                                                        October 27, 2014


             Network as a Service in datacenters use cases
                   draft-huang-nvo3-naas-usecases-00

Abstract

   Network as a Service (NaaS) is a new network business model in the
   cloud computing area where virtualized E2E connectivity to end users
   is provided to make the network more flexible and scalable.

   This draft describes Network as a Service (NaaS) system use cases in
   datacenters that are deployed typically for different applications.
   Considerations about the use cases are pointed out.

Status of This Memo

   This Internet-Draft is submitted to IETF 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 April 30, 2015.

Copyright Notice

   Copyright (c) 2014 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



Huang, et al.            Expires April 30, 2015                 [Page 1]

Internet-Draft               NaaS use cases                 October 2014


   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Definition of terms . . . . . . . . . . . . . . . . . . . . .   2
   3.  Use cases . . . . . . . . . . . . . . . . . . . . . . . . . .   3
     3.1.  Use cases 1 VPN . . . . . . . . . . . . . . . . . . . . .   3
     3.2.  Use cases 2 Intelligent traffic engineering across
           datacenters . . . . . . . . . . . . . . . . . . . . . . .   5
   4.  OAM considerations  . . . . . . . . . . . . . . . . . . . . .   6
   5.  Security considerations . . . . . . . . . . . . . . . . . . .   6
   6.  Summary . . . . . . . . . . . . . . . . . . . . . . . . . . .   7
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   7
   8.  Normative References  . . . . . . . . . . . . . . . . . . . .   7
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   7

1.  Introduction

   Network as a Service (NaaS) is a new network business model which
   describes services for network transport connectivity in the cloud
   computing area.  Considering network and computing resources as a
   whole, resource allocations are optimized.  The target of NaaS is to
   provide end to end virtual network with capacity for tenants in cloud
   datacenter, which is the essential part from the technical point of
   view.  In NaaS, operators' network infrastructure can be virtualized
   and multiplexed for selling, while clients can make the network
   provision and use their own virtual network according to specific
   requirements.

   In this draft, we focus on proposing network use cases of NaaS in
   datacenters.  Two typical use cases are provided.  One is about the
   virtual private cloud network and another is the intelligent traffic
   engineering across the datacenters.  In both use cases, basic network
   models are introduced and considerations about the use cases are
   pointed out.

2.  Definition of terms

   VPCN: virtual private cloud network

   FW: firewall

   NAT: network address translation

   LB: load balance



Huang, et al.            Expires April 30, 2015                 [Page 2]

Internet-Draft               NaaS use cases                 October 2014


   TS: tenant systems

   VM: virtual machine

   CE: customer edge

   PE: provider edge

3.  Use cases

3.1.  Use cases 1 VPN

   One of the typical use cases in NaaS is to construct the virtual
   private cloud network (VPCN) for tenants (i.e., enterprise,
   organization, etc) over the public cloud provided by the operators.
   Its main characteristic is that tenants can custom their own VPCN,
   i.e., network topology, VPN connection, network services, etc.
   Following Figure 1 is an logical network example for VPCN.



        .............................................................
        .  VPCN                             +----+---+              .
        .                                   |Internet|              .
        .                                   |        |              .
        .                                   +----+---+              .
        .                                        |                  .
        .          ...........                   |                  .
        .          .  +---+  .              +----+---+              .
        .          .  |NAT|  .              |Internet|              .
        .          .  +---+  .              |   GW   |              .
        .          .         .              +----+---+              .
        .          .  +---+  .                   |                  .
        .          .  |FW |  .                   |                  .
        .          .  +---+  .              +----+---+              .
        .          .         .              |   GW   |              .
        .          .  +---+  .------------- |        |              .
        .          .  |LB |  .              +----+---+              .
        .          .  +---+  .                   |                  .
        .          .         .                   |                  .
        .          .  +---+  .              +----+---+              .
        .          .  |...|  .              |   TS   |              .
        .          .  +---+  .              |        |              .
        .          ...........              +----+---+              .
        .............................................................

                          Figure 1: VPCN example




Huang, et al.            Expires April 30, 2015                 [Page 3]

Internet-Draft               NaaS use cases                 October 2014


   NaaS provides the network more convinent to the tenants.  In
   traditional service, it takes a long time for tenants to rent their
   own network, while it costs more time for tenants to configure their
   network.  Because the all the configurations are delivered by
   adminstrators manually.Besides, extensibility is limited to the
   number of vlan supported.Tenants are not avaliable to monitor their
   network.So it turns to NaaS in VPCN.

   In NaaS, the tenants can define their networks by themselves simply
   by Graphical User Interface.  And the network they construct can be
   controlled by themselves as well.  The administrators can take a
   global control from the management plane.  NaaS provides it available
   that networks rather than unique devices are for sale.

   In such a framework, the interface information from the tenants' side
   can be an issue, as the standard interface has several features.
   Tenants apply for the virtual network construction they need to
   deploy the end to end network.  Different tenants are isolated from
   each other with their access policies defined by themselves.  The
   virtual network can be managed, monitored and configured by tenants.
   Because of the open access of network to the tenants, the network
   model aimed at the tenants should be thoughtful.  The network model
   is constituted of node, link, flow and policy.  Node acts as the role
   of forwarding or processing the dataflow by some policies.Service
   node provides the service, while computer node refers to the VMs.
   Link connects two nodes.  The network model can be divided into
   several typical models to provide one of network service, something
   like LBaaS, FWaaS or DNSaaS and so on.























Huang, et al.            Expires April 30, 2015                 [Page 4]

Internet-Draft               NaaS use cases                 October 2014


                  ............................................
                  .   +----+----+                            .
                  .   |Mnagement|       ...................  .
                  .   |         |       . service node    .  .
                  .   +----+----+       .  +---+   +---+  .  .
                  .        |            .  |NAT|   |LB |  .  .
                  .   +----+----+ policy.  +---+   +---+  .  .
                  .   |  Router |-------.  +---+   +---+  .  .
                  .   |  node   | link  .  |FW |   |...|  .  .
                  .   +----+----+       .  +---+   +---+  .  .
                  .        |            ...................  .
                  .      ......                              .
                  .    ...    ...                            .
                  .  ... Subnet ...                          .
                  .    ...    ...       ...................  .
                  .      ......         . computer node   .  .
                  .        |            .  +---+   +---+  .  .
                  .       ...           .  |VM |   |VM |  .  .
                  .    ..   ..  policy  .  +---+   +---+  .  .
                  .   .  Port  .------  .  +---+   +---+  .  .
                  .    ..   ..   link   .  |VM |   |VM |  .  .
                  .      ...            .  +---+   +---+  .  .
                  .                     ...................  .
                  ............................................


                      Figure 2: VPCN logical network

3.2.  Use cases 2 Intelligent traffic engineering across datacenters

   The intelligent traffic engineering can be regarded as another
   typical use case of Network as a Service, such as the network
   management across the data center.  NaaS can provide the virtual
   network across datacenters with intelligent traffic engineering and
   load balancing.  With the virtualized network and centralized
   controlling, NaaS offers the capability of scheduling the traffic at
   different levels of traffic QoS, reliability and transparency in a
   flexible and scalable way.  Besides due to the virtual network,
   virtual machines can migrate from one datacenter to another flexibly.
   The network model is constituted of node, link, flow and policy as
   well.

   Superior to the traditional network with the condition of congestion,
   virtualized network provides the advantage of network bandwidth
   optimization.  By the statistical data of the current traffic,
   Network as a Service schedules the traffic based on centralized
   computing intelligently.




Huang, et al.            Expires April 30, 2015                 [Page 5]

Internet-Draft               NaaS use cases                 October 2014


   In addition, services and tenants can be labeled in different
   priority due to their features.  Thus QoS can be guaranteed.

 .......................................................................
 .                            +---------------+                        .
 .                            |+-+-+      IDC |                        .
 .                            ||VM |  +---+   |                        .
 .                            |+-+-+  |CE |   |                        .
 .                            |       +-+-+   |                        .
 .                            +---------+-----+                        .
 .                                    +-+-+                            .
 .                                    |PE |                            .
 .                                    +-+-+                            .
 .      load balancing at the output    |                              .
 .        bandwidth/QoS       .......................                  .
 .                   .........                      .........          .
 .               .........           IP/MPLS            .........      .
 .            .....                    WAN                     .....   .
 .               .........                              .........      .
 .                   .........                      .........          .
 .                     |      .......................     |            .
 .                     |                                  |            .
 .                   +-+-+                              +-+-+          .
 .                   |PE |                              |PE |          .
 .                   +-+-+                              +-+-+          .
 .           +---------+-----+                  +---------+-----+      .
 .           | IDC   +-+-+   |                  | IDC   +-+-+   |      .
 .           |       |CE |   |                  |       |CE |   |      .
 .           |+-+-+  +---+   |                  |+---+  +---+   |      .
 .           ||VM |          |                  ||VM |          |      .
 .           |+-+-+          |                  |+-+-+          |      .
 .           +--+------------+                  +--+------------+      .
 .              |----------- VM migration ---------|                   .
 .......................................................................



   Figure 3: Intelligent traffic engineering across the datacenter model

4.  OAM considerations

   TBD.

5.  Security considerations

   In NaaS, security can be a problem in several aspects.  To meet the
   requirement of the tenants, the virtual network should be secured and
   tenants' traffic should be isolated with each other.  On the other



Huang, et al.            Expires April 30, 2015                 [Page 6]

Internet-Draft               NaaS use cases                 October 2014


   side, the security in NaaS is reflected in that traffic access should
   be authorized.  Other security in such as VM migration can also be an
   issue.

6.  Summary

   This draft describes some typical use cases of NaaS in datacenters.
   NaaS provides network as a service to tenants.  Tenants can build
   their own network by NaaS easily with the basic network model
   provided.  Through NaaS, traffic across the datacenters can be
   optimized by intelligent traffic engineering.  It's expressed in
   given use cases that network virtualized with basic models can be
   helpful in providing NaaS.

7.  IANA Considerations

   The document does not require any IANA action.

8.  Normative References

   [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
              Requirement Levels", BCP 14, RFC 2119, March 1997.

Authors' Addresses

   Lu Huang (editor)
   China Mobile
   32 Xuanwumen West Ave, Xicheng District
   Beijing  100053
   China

   Email: huanglu@chinamobile.com


   Rong Gu (editor)
   China Mobile
   32 Xuanwumen West Ave, Xicheng District
   Beijing  100053
   China

   Email: gurong@chinamobile.com


   Fank Xia
   Huawei Technologies

   Email: frank.xialiang@huawei.com




Huang, et al.            Expires April 30, 2015                 [Page 7]

Internet-Draft               NaaS use cases                 October 2014


   Qiang Zu
   Ericsson
   8400, boul. Decarie Ville Mont-Royal
   QC
   Canada

   Email: Zu.Qiang@Ericsson.com












































Huang, et al.            Expires April 30, 2015                 [Page 8]