Skip to main content

Requirements and Use Cases for Virtual Network Functions

Document Type Expired Internet-Draft (individual)
Expired & archived
Authors Liang Xia , Qin Wu , Daniel King , Hidetoshi Yokota , Naseem Khan
Last updated 2015-05-15 (Latest revision 2014-11-11)
RFC stream (None)
Intended RFC status (None)
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:


Network function appliances such as subscriber termination, firewalls, tunnel switching, intrusion detection, and routing are currently provided using dedicated network function hardware. As network function is migrated from dedicated hardware platforms into a virtualized environment, a set of use cases with application specific resilience requirements begin to emerge. These use cases and requirements cover a broad range of capabilities and objectives, which will require detailed investigation and documentation in order to identify relevant architecture, protocol and procedure solutions to ensure reliance of user services using virtualized functions. This document provides an analysis of the key reliability requirements for applications and functions that may be hosted within a virtualized environment. These NFV engineering requirements are based on a variety of uses cases and goals , which include reliability scalability, performance, operation and automation. Note that this document is not intended to provide or recommend protocol solutions.


Liang Xia
Qin Wu
Daniel King
Hidetoshi Yokota
Naseem Khan

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