APONF Use Case: Using Abstract View of Network by Application Developers

Document Type Expired Internet-Draft (individual)
Last updated 2015-01-05 (latest revision 2014-07-04)
Replaces draft-liu-aponf-abstract-network-view-use-case
Stream (None)
Intended RFC status (None)
Expired & archived
pdf htmlized (tools) htmlized 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


This document describes a use case of Application Policy on Network Functions (APONF) that presents how service developers can profit by using an abstract view of the network during the programming and development process, instead of manipulating individual devices. In this way one can write software that programs an arbitrary network. APONF can be used to interface the programmed arbitrary network into network management policies, i.e., device configuration models.


Will LIU (liushucheng@huawei.com)
Tina Tsou (tina.tsou.zouting@huawei.com)
Georgios Karagiannis (g.karagiannis@utwente.nl)
Jose Saldana (jsaldana@unizar.es)

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