Internet DRAFT - draft-aoch-nvo3-flow-split
draft-aoch-nvo3-flow-split
NVO3 WG Z. Chen
Internet-Draft China Telecom
Intended status: Standards Track T. Ao
Expires: January 4, 2018 ZTE Corporation
July 3, 2017
Flow split in Metro Area Network
draft-aoch-nvo3-flow-split-00.txt
Abstract
In the future, there will be some new application appeared known as
4K/8K high quality video or VR/AR application.These application needs
high bandwidth and low lantacy.In order to meet these requirements,
the flow model of traditional MAN should be changed. This article
describes a new device using in MAN to support spliting DC's and
Internet's flow, support to build edge DC in MAN and change MAN flow
model from pipe type to umbrella type.
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
(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
Chen & Ao Expires January 4, 2018 [Page 1]
Internet-Draft Flow split in Metro Area Network July 2017
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 . . . . . . . . . . . . . . . . . . . . . . . . . 2
3. Device model . . . . . . . . . . . . . . . . . . . . . . . . 2
4. Functionality . . . . . . . . . . . . . . . . . . . . . . . . 3
4.1. Forward and shunt . . . . . . . . . . . . . . . . . . . . 3
4.2. Interface . . . . . . . . . . . . . . . . . . . . . . . . 3
4.3. Other Function . . . . . . . . . . . . . . . . . . . . . 4
4.3.1. PUPVPVxLAN function . . . . . . . . . . . . . . . . . 4
4.3.2. Leaf switch function . . . . . . . . . . . . . . . . 4
4.3.3. VxLAN smart mapping to VxLAN . . . . . . . . . . . . 4
4.3.4. QoS function and rating limiting in VxLAN . . . . . . 4
4.3.5. EVPN protocol . . . . . . . . . . . . . . . . . . . . 4
4.3.6. DHCP snooping and relay function in VxLAN tunnel . . 4
5. Security Considerations . . . . . . . . . . . . . . . . . . . 4
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4
7. Information References . . . . . . . . . . . . . . . . . . . 5
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 5
1. Introduction
This document describes a type of device using in Metro Network to
distribute the user's flows,and forward them to different direction
of MAN. Service Provider can use this device to separate the
valuable flow from Internet flow,and redirect the flow to the edge
cloude.such as 4K/8K video or AR/VR application.
2. Terminology
FSD(Flow Split Device): device to split user flow according to the
control flow table, include forwarding plane and stack module.
3. Device model
FSD equipment's model is described as below.
Chen & Ao Expires January 4, 2018 [Page 2]
Internet-Draft Flow split in Metro Area Network July 2017
+----------------+ +-----------------+
| stack module +---> | SDN controller |
| | | |
+-------+--------+ +--------+--------+
^ |
| +-----------------+
| |
| ^
+--------+-----+--+
| forwarding plane| +---------------->
+------------> | |
+-----------------+ +---------------->
The forwarding plane is the datapath of the FSD. Before it working
,its forwarding table will be configurated by the SDN controller with
NATCONF or OFPCONFIG protocol.
User's data flow is sended to the forwarding plane. In normal
condition, the flow will be forwarded according to the preconfig
table in the forwarding plane.
4. Functionality
4.1. Forward and shunt
Forward and shunt For Internet flow,the packet will be forwarded by
FSD according to pre configuration flow table. The capacity of flow
table is a big problem to the shunt device if using MAC address
forwarding. In a large Metro network the number of the items of flow
table maybe up to one million, so the C/S VLAN(QinQ) forwarding
function will be considered to reducing the capacity of the flow
table.
For local flow,which is disposed in the edge cloud, should be shunted
in the FSD according to the dynamical flow table. The protocol such
as openflow should be supported to create the dynamical forwarding
flow table.
4.2. Interface
VxLAN tunnel should be supported in the uplink of the FSD to the edge
cloud direction, and IP interface should be supported in the uplink
to the Internet direction. In other word, FSD will separate the
east-west flow and south-north flow of the access network.
Chen & Ao Expires January 4, 2018 [Page 3]
Internet-Draft Flow split in Metro Area Network July 2017
There are three kinds of interface should be supported in the
downlink of the FSD, VLAN interface,QinQ interface and VxLAN
interface. VLAN interface is for enterprise subscriber to access in,
QinQ interface is for internet user,and VxLAN tunnel interface is for
some VxLAN private line service.
4.3. Other Function
Many other functions should be supported in FSD for different
requirements,as below:
4.3.1. PUPVPVxLAN function
For user isolation and VxLAN internal flow statistic and charging.
4.3.2. Leaf switch function
for realize the leaf-spine frame in DC Downlink port VLAN,QinQ,
4.3.3. VxLAN smart mapping to VxLAN
in uplink port for packet forward
4.3.4. QoS function and rating limiting in VxLAN
for Forwarding priority and service control in VxLAN
4.3.5. EVPN protocol
for the information synchronization in layer2 network
4.3.6. DHCP snooping and relay function in VxLAN tunnel
and so on...
5. Security Considerations
Service Gateway must have the capability of checking the validation
of user's address.
6. IANA Considerations
N/A
Chen & Ao Expires January 4, 2018 [Page 4]
Internet-Draft Flow split in Metro Area Network July 2017
7. Information References
[I-D.ietf-nvo3-arch]
Black, D., Hudson, J., Kreeger, L., Lasserre, M., and T.
Narten, "An Architecture for Data Center Network
Virtualization Overlays (NVO3)", draft-ietf-nvo3-arch-08
(work in progress), September 2016.
[I-D.ietf-nvo3-use-case]
Yong, L., Dunbar, L., Toy, M., Isaac, A., and V. Manral,
"Use Cases for Data Center Network Virtualization Overlay
Networks", draft-ietf-nvo3-use-case-17 (work in progress),
February 2017.
[RFC7365] Lasserre, M., Balus, F., Morin, T., Bitar, N., and Y.
Rekhter, "Framework for Data Center (DC) Network
Virtualization", RFC 7365, DOI 10.17487/RFC7365, October
2014, <http://www.rfc-editor.org/info/rfc7365>.
Authors' Addresses
Zhonghua Chen
China Telecom
No.1835, South PuDong Road
Shanghai 201203
China
Phone: +86 18918588897
Email: 18918588897@189.cn
Ting Ao
ZTE Corporation
No.889, BiBo Road
Shanghai 201203
China
Phone: +86 21 68897642
Email: ao.ting@zte.com.cn
Chen & Ao Expires January 4, 2018 [Page 5]
