The use case in Edge Datacenter network
draft-aoch-nvo3-edge-datacenter-01

Document Type Active Internet-Draft (individual)
Last updated 2017-07-03
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
NVO3 WG                                                            T. Ao
Internet-Draft                                           ZTE Corporation
Intended status: Standards Track                                 Z. Chen
Expires: January 4, 2018                                   China Telecom
                                                            July 3, 2017

                The use case in Edge Datacenter network
                 draft-aoch-nvo3-edge-datacenter-01.txt

Abstract

   This document introduces the Edge Datacentet network, and describe
   some use cases about Edge Datacenter, discusses an important
   component in the Edge Datacenter:Service Gateway and its functions,
   elaborates the requirements on Service Gateway.

   Service Gateway works as a Flow Split Device(FSD) in the Edge DC
   network, it needs to not only play a gateway of the edge Datacenter
   network, implementing coordination with existing technology, but also
   meets many new requirements.  For example, to make sure the packets
   goes into Edge DC or Metro network, SDN forwarding, and as a leaf in
   the leaf-spin architecture.

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 4, 2018.

Copyright Notice

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

Ao & Chen                Expires January 4, 2018                [Page 1]
Internet-Draft   The use case in Edge Datacenter network       July 2017

   (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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Problem statement . . . . . . . . . . . . . . . . . . . . . .   3
   4.  Edge Datacenter . . . . . . . . . . . . . . . . . . . . . . .   3
     4.1.  Use cases of the EDC  . . . . . . . . . . . . . . . . . .   5
       4.1.1.  Future video application  . . . . . . . . . . . . . .   6
       4.1.2.  Edge IOT control application  . . . . . . . . . . . .   6
       4.1.3.  Home Hybird Cloud . . . . . . . . . . . . . . . . . .   7
       4.1.4.  Light weight lease line based on application  . . . .   8
   5.  Service Gateway . . . . . . . . . . . . . . . . . . . . . . .   9
     5.1.  Functions . . . . . . . . . . . . . . . . . . . . . . . .   9
       5.1.1.  PPPoE proxy . . . . . . . . . . . . . . . . . . . . .   9
       5.1.2.  VxLAN encapsulation . . . . . . . . . . . . . . . . .   9
       5.1.3.  C/S VLAN forwarding . . . . . . . . . . . . . . . . .  10
       5.1.4.  Distribution  . . . . . . . . . . . . . . . . . . . .  10
   6.  Conclusion  . . . . . . . . . . . . . . . . . . . . . . . . .  10
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .  10
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  10
   9.  Information References  . . . . . . . . . . . . . . . . . . .  10
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  11

1.  Introduction

   With the challenge and the chances of the new network SDN/NFV and the
   development of the Datacenter, the provider is facing many changes
   from traditional network, which is representive by traditional CO.
   How to use the resource of the traditinal CO fully and achieve the
   transition to the SDN/NFV is the problem providers and vendors need
   to consider.  CO re-architection is the attractive to more and more
   providers and vendors.  and getting more and more attention.  Using
   lots of CO resource, the providers can re-architected CO to Edge DC,
   which is more adaptive in SDN/NFV.

   In this document, we will present some use cases of the Edge
   Datacenter and its main component, Service gateway.  As a result,
   some requirements are proposed for Edge DC and Service Gateway.
Show full document text