The Architecture for Application-based Policy On Network Functions
draft-zhou-aponf-architecture-03
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Cathy Zhou , Tina Tsou (Ting ZOU) , Diego R. Lopez , Georgios Karagiannis , Qiong Sun | ||
| Last updated | 2015-01-22 (Latest revision 2014-07-21) | ||
| 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
Currently, there are network management applications that present specific demands on a communication network. This document describes the APONF basic architecture, its elements and interfaces. The main APONF architecture entities are the Network Management Application Agent (NMAA), which is a network entity that creates and runs network services, and Application-based Policy Decision (ABPD), which supports classified application models. Each of these models support application demands that are similar in nature and therefore can be grouped/classified together. Moreover, the ABPD maps the classified application models into network capabilities, e.g., network management and controlling policies.
Authors
Cathy Zhou
Tina Tsou (Ting ZOU)
Diego R. Lopez
Georgios Karagiannis
Qiong Sun
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)