APONF Use Case: Using Abstract View of Network by Application Developers
draft-liu-aponf-using-abstract-view-use-case-00
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Will (Shucheng) LIU , Tina Tsou (Ting ZOU) , Georgios Karagiannis , Jose Saldana | ||
Last updated | 2015-01-05 (Latest revision 2014-07-04) | ||
Replaces | draft-liu-aponf-abstract-network-view-use-case | ||
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
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.
Authors
Will (Shucheng) LIU
Tina Tsou (Ting ZOU)
Georgios Karagiannis
Jose Saldana
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)