Internet DRAFT - draft-lee-vhs-usecases
draft-lee-vhs-usecases
TBD Y. Lee
Internet-Draft Comcast
Intended status: Informational C. Xie
Expires: May 14, 2015 China Telecom
November 10, 2014
Virtual Home Services Use Cases
draft-lee-vhs-usecases-02
Abstract
This draft states some high-level use cases of virtual home network.
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 May 14, 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
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.
Lee & Xie Expires May 14, 2015 [Page 1]
Internet-Draft VHN Use Cases November 2014
Table of Contents
1. Virtual Home Network Motivations . . . . . . . . . . . . . . 2
2. High-level Architecture . . . . . . . . . . . . . . . . . . . 2
3. Virtual Home Network Use Case . . . . . . . . . . . . . . . . 3
4. Security Considerations . . . . . . . . . . . . . . . . . . . 5
5. Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . 5
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 5
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 5
8.1. Normative References . . . . . . . . . . . . . . . . . . 5
8.2. Informative References . . . . . . . . . . . . . . . . . 5
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 5
1. Virtual Home Network Motivations
Traditionally Network Service Providers (NSP) implement services in
the Customer Premises Equipment (CPE). These services may include
but not limited to NAT [RFC2663], Voice over IP (VoIP) adapter, IP
management, personal firewall service, etc. This model requires NSP
updating the CPE firmware or upgrading the CPE hardware to add new or
modify existing services. This update or upgrade process often takes
a significant effort. To off-load this process, the industry is
researching the concept of Network as a Service (NaaS) and the
methodology to apply NaaS to virtualize the traditional CPE model.
Network functions such as VoIP and personal firewall can be
implemented as Virtual Network Function (VNF) and deployed in the NSP
network. This enables NSP to abstract the service logics from the
CPE and simplifies the CPE implementations. Services will be moved
to the network and decoupled from the CPE. The goal is to ease the
CPE upgrade effort and speedup service deployment to users.
Traditionally NSP serve an entire house behind a CPE as a functional
unit. Services are built around CPE but not around users or groups
behind a CPE. When virtualizing the CPE, NSP would be able to offer
more personalized services for individual users.
This Problem Statement discusses the background and motivations of
virtualizing home services. The objective of this architecture is
virtualizing home services and providing them in the network. This
draft will discuss some possible use cases that are required
supporting virtualizing home services.
2. High-level Architecture
Lee & Xie Expires May 14, 2015 [Page 2]
Internet-Draft VHN Use Cases November 2014
----------------------
/ User Configuration /
/ and Management /
/ System /
-----||--------||-----
|| || **************
|| Ib || / VNF Manager /
|| || **************
|| +--||-----------------------+ ||
|| | +----+ +----+ +----+ | || Ic
Ia || | |VNF1| |VNF2| .... |VNFx| |=======||
|| | +----+ +----+ +----+ |
|| | Virtual Network Functions |
|| +-------||------------------+
|| ||
|| ||
|| || Service Function Chain (SFC)
---- || || Ie
/CPE/==========\ || ||
---- \ || ||
\+||--||-------+ ///////////////
---- | | / /
/CPE/ =============| Packet |====================/ Internet /
---- Id | Forwarder | / /
/+-------------+ \\\\\\\\\\\\\\\
---- /
/CPE/=========/
---- Ia - SFC Provisioning API
Ib - Service Provisioning API
Ic - VNF Management API
Id - Encapsulation Specification
Ie - SFC Specification
Virtualizing Home Services High-Level Architecture Diagram
Figure 1
Figure 1 illustrates the high-level architecture. Problem Statement
describes the various functions defined in the diagram. Further
explanation can be found in [I-D.lee-vhs-ps]
3. Virtual Home Network Use Case
When virtualizing the home services and moving them to the network,
there are uses cases the new architecture must address:
Lee & Xie Expires May 14, 2015 [Page 3]
Internet-Draft VHN Use Cases November 2014
1. Local QoS Policy: In traditional CPE model, users manage local
Quality of Service (QoS) for their devices. For example: a user
can give higher priority to VoIP than other services. In Virtual
CPE, this service will be virtualized in the network. The
network must provide an interface for users to configure local
QoS policy.
2. Personal Firewall Policy: In traditional CPE model, users mange
their local firewall rules in the CPE. In VHN, this service will
be virtualized in the network. The NSP must provide an interface
for users to configure local firewall policy..
3. NAT Service: Almost all CPE provide NAT service. When NAT
service is virtualized in the NSP network, NSP must be able to
provision and manage NAT service for users.
4. IPv6 Transition Technology: Almost all IPv6 transition
technologies (e.g., DS-Lite, MAP-E, MAP-T, lw4over6) require some
functions defined in the CPE. Updating the CPE in large scale to
support the transition technologies is always a challenge that
leads to slower IPv6 deployment. Virtualizing IPv6 transition
technology can ease the requirement to the CPE.
5. Personal M2M Service: In traditional CPE model, CPE often is the
gateway of the M2M applications. In VHN, M2M application gateway
will be virtualized in the network. The NSP must provide an
interface to provision M2M devices and manage the M2M
applications to provide services to the users.
6. Local Storage: In traditional CPE model, users can attach a local
storage for personal contents. In VHN, NSP can offer "virtual
storage" to users over the network. The virtual storage must
appear local to the user's devices.
7. VPN Service: Some CPEs offer VPN (e.g., IPSec) service for home
office users to connect to their office internal networks. NSP
must be able to provision and manage VPN service for users.
8. Event Notification: When virtualizing CPE, CPE and NSP network
are tightly coupled. CPE must be able to generate events to
notify NSP when event occurs. NSP may leverage exciting
protocols such as [TR-69] for event notification.
9. Better Helpdesk Support: When NSP detects an IPv4-only device
behind CPE potentially being attacked by malwares, the NSP can't
identify the user which device. In VHN, NSP will be able to
gather use packet based data and steer a particular flow of data
to a VNF for inspection.
Lee & Xie Expires May 14, 2015 [Page 4]
Internet-Draft VHN Use Cases November 2014
4. Security Considerations
5. Conclusion
6. Acknowledgements
7. IANA Considerations
This memo includes no request to IANA.
8. References
8.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
8.2. Informative References
[I-D.lee-vhs-ps]
Lee, Y. and R. Ghai, "Problem Statements of Virtualizing
Home Services", draft-lee-vhs-ps-01 (work in progress),
September 2014.
[RFC2663] Srisuresh, P. and M. Holdrege, "IP Network Address
Translator (NAT) Terminology and Considerations", RFC
2663, August 1999.
Authors' Addresses
Yiu L. Lee
Comcast
One Comcast Center
Philadelphia, PA 19103
U.S.A.
Email: yiu_lee@cable.comcast.com
URI: http://www.comcast.com
Chongfeng Xie
China Telecom
Room 708 No.118, Xizhimenneidajie
Beijing 100035
P.R.China
Email: xiechf@ctbri.com.cn
Lee & Xie Expires May 14, 2015 [Page 5]
