Virtual CPE Deployment Considerations
draft-pularikkal-virtual-cpe-02

Document Type Expired Internet-Draft (individual)
Last updated 2017-08-28 (latest revision 2017-02-24)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-pularikkal-virtual-cpe-02.txt

Abstract

Broadband Service Provider Industry has been gearing towards the adoption of Virtual CPE (vCPE) solutions. The concept of vCPE is build around the idea that the physical CPE device at the customer premises can be simplified by moving some of the key feature functionalities from the physical CPE device to the Service Provider Network. This document starts discussing the drivers behind vCPE adoption followed by Solution level requirements. Two key Architecture models for vCPE, which can address the service provider and subscriber requirements, are covered in this reference document. Document also touches up on some of the key deployment considerations, which can influence the adoption of the vCPE architecture models.

Authors

Byju Pularikkal (byjupg@cisco.com)
Qiao Fu (fuqiao1@outlook.com)
DENG Hui (denghui@chinamobile.com)
Ganesh Sundaram (gsundara@cisco.com)
Sri Gundavelli (sgundave@cisco.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)