Application-based Policy for Network Functions Gap Analysis
draft-tremblay-aponf-gap-analysis-00
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | JF Tremblay , Jun Bi | ||
Last updated | 2015-01-05 (Latest revision 2014-07-04) | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
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:
Abstract
As operators struggle to optimize their network for different applications while maximizing network resources usage, there's growing business pressure to minimize operational tasks and the deployment time of new services. New automation paradigms are meant to help reach these goals, including the optimization of network functions through application control. This control could be signaled directly by an application, through a proxy or orchestrated in a centralized manner. The current version of the Application-based Policy for Network Functions (APONF) proposed working group mentions the NSIS framework as a possible signaling protocol, through the definition of a new NSIS Signaling Layer Protocol (NSLP). The present memo analyses if this proposition is suitable for the designed purpose and if other protocols would be more suitable.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)