Skip to main content

Service Function Controller/Orchestration Requirements and Templates
draft-cao-sfc-control-orchestration-00

Document Type Expired Internet-Draft (individual)
Authors Zehn Cao , DENG Hui
Last updated 2014-08-17 (Latest revision 2014-02-13)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text htmlized pdfized bibtex
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 can be found at:
https://www.ietf.org/archive/id/draft-cao-sfc-control-orchestration-00.txt

Abstract

Service Function Chain architecture further enables the modularity of network functions; network service functions can be split and chained together to compose complicated services. Network automation relies on a specific orchestrator to automatically deploy an end2end service or application. If this end2end service or application has a specific requirement to chaining several service functions, there is a need of an interface from the application to inform the orchestrator. This document investigates the problem.

Authors

Zehn Cao
DENG Hui

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