Requirements and Framework of

VPN-oriented Data Center Services

http://datatracker.ietf.org/doc/draft-so-vdcs/

Ning So ning.so@verizonbusiness.com
Paul Unbehagen paul.unbehagen@alcatel-lucent.com
Linda Dunbar Linda.dunbar@huawei.com
Henry Yu Henry.yu@twtelecom.com
John M. Heinz john.m.heinz@centurylink.com
Norival Figueira nfigueir@brocade.com
Bhumip Khasnabish vumip1@gmail.com

IETF 81 Quebec City 1

 What Is VDCS
!   VPN-oriented Data Center Services (VDCS) are the
extensions to the existing L2 and L3 VPN services into
cloud data centers and to control the virtual resources
sharing functions
!  Strictly maintaining the secure, reliable, and logical isolation
characteristics of VPN
!  Making the data center resources as additional attributes to VPNs
!  Allowing end-to-end VPN-based service management
!  VPN having the control on how and what data center resources to
be associated with the VPN
This draft describes the characteristics of those services, the
service requirements, and the corresponding requirements to
data center networks.

2
VDCS Service Definition and Requirements
!   VPN-oriented DC computing services
!  Virtual Machines (VMs) and/or physical servers in a
virtualized carrier data center being attached to a customer
VPN
!  Requirements: auto-provisioning, VM and server instantiation
and removal, VM migration policy control, VM monitoring
!   VPN-oriented DC storage services
!  disk space, either virtual or actual blocks of hard drives in
data centers, being added to a customer s VPN
!  Requirements: content replication control, storage space
auto-provisioning, storage migration policy control, content
life cycle management

3
 Other Requirements
!   Intra-DC Network Requirements
!  Requirements when VPNs are extended into DC using VPN
Gateway
•  Traffic separation per VPN and per service
•  DC virtual resource assignment control and reporting
•  Dynamic configuration and provisioning control of DC virtual resources
•  QoS support

!   Virtual Resources Management Requirements

!  DC virtual resources include physical servers and VMs, disk
spaces, memories, intra-DC network connections and
bandwidth.
!  Requirements include
•  Resource partition and assignment
•  Resource accessibility control and management

4
 Other Requirements

!   Security requirements
!   Auto-configuration requirements
!   OAM requirements
!   And etc.

5
 L3-VDCS Physical Framework
– Virtual Machines attached to VPN

10.1 10.3.x
.x
Us User
Des er Desktops
kto
p
s
LA
Swi N CE IP/MPLS
tch VPN LAN
Rou V network
t E PN Edge
CE
er dge Rout Switch
Rou Route
te er
r r
User
Deskto
p
s
VPN 10.4.x
VPN Edge CE LAN
CE Data
LAN Edge Route R o ut Switch
R out e Center
Swit
ch Rout er
10.2.x User er r VPN GW r
tops
Desk Router
Data
Data Center
Center
LAN
Switch

VM

10.1.200.x 10.2.40.x 10.3.20.x 10.4.100.x

 Logical View of Routing Table at L3VPN Edge Routers

10.1 User
.x
Desktop
Us 10.3.x
Des er s
kto 3
s
p 1
IP/MPLS
VPN VPN
network
Edg Edge
Rou e Route
te
r r
User
4 Deskto
p
2 s
VPN 10.4.x
VPN Edge
Edge Route
e DC VPN GW
10.2.x Rout r
User r Router
top IP Address Next Hop
Desk
s IP Address Next Hop
10.1.200.x
IP Address DC VPN
NextGW Hop
10.1.200.x
IP Address DC VPN GW Hop
Next
IP Address Next Hop Data 10.1.x10.1.200.x VPN ER
IP Address DC 1VPN GW
10.1.x10.1.200.x VPN ER Next
1VPN GWHop
10.1.200.x DC VPN GW Center 10.2.20.x IP DC VPN
Address DC
GW Next Hop
10.1.x10.1.200.x VPN ERDC 1VPN GW
10.2.20.x IP DC VPN
Address
10.1.x10.1.200.x VPNGW Next Hop
10.1.x VPN ER 1 10.2.x10.2.20.x VPN ER
DC 2VPNER
DC
GW
1VPN GW
10.1.x10.1.200.x
10.2.x10.2.20.x VPN ER VPN ER 1VPN GW
10.3.20.x DC VPN DC2VPN DC
GW
10.2.20.x DC VPN GW 10.1.x
10.2.x10.2.20.x VPNGWER
DC
VPN
2VPN
ER 1
GW 1
10.3.20.x DC VPN
10.1.x
10.2.x10.2.20.x VPNGWER VPN
2VPNER
10.2.x VPN ER 2 VM 10.3.x10.3.20.x VPN ER 3
DC VPN DC
GW GW
10.2.x10.2.20.x
10.3.x10.3.20.x VPN ER VPN
3 ER
DC 2VPN GW
10.4.100.x DC VPN DC VPN GW 2
10.3.20.x DC VPN GW 10.2.x
10.3.x10.3.20.x VPNGWER
DC
VPN
3VPNERGW 2
10.4.100.x DC VPN
10.2.x
10.3.x10.3.20.x VPNGWER VPN
3VPNER
10.3.x VPN ER 3 10.1.200.x 10.2.40.x 10.3.20.x 10.4.100.x
10.4.x10.4.100.x VPN ER 4
DC VPN DC
GW GW
10.3.x10.3.20.x
10.4.x10.4.100.x VPN ER VPN
4 ER
DC 3VPN GW
10.4.100.x DC VPN GW 10.3.x VPN DC VPN
VPN GW 3
10.4.x10.4.100.x ER
DC 4VPNERGW
10.3.x VPN ER VPN
10.4.x10.4.100.x ER 3
10.4.x VPN ER 4 DC47 VPN GW
10.4.x10.4.100.x VPN ER 4
DC VPN GW
10.4.x VPN ER 4
10.4.x VPN ER 4
 L3VDCS Logical View
L3VDCS Logical View
10.1 User
.x
Desktop
Us 10.3.x
Des er s
kto 3
s
p 1
IP/MPLS
VPN VPN
network
Edg Edge
Rou e Route
te
r VPN
User
4 Deskto
p
2 s
VPN 10.4.x
VPN Edge
Edge Route
e DC VPN GW
10.2.x Rout VPN
User r Router
top
Desk
s

For end users of a VPN client, they see the VMs in data center as if
For end users of a VPN client, they see the VMs in data center as if
 Next Steps
!   As this drafts gets longer, it may need to be
  As this drafts gets longer, it may need to be
broken into two separate drafts: requirements
draft and framework
!   Welcome feedbacksdraft
and solution
development cooperation
  Welcome feedbacks and solution
development
  Still lookingcooperation
for a WG for the progression of
  Still looking for a WG for the progression of