The Framework of Simplified Use of Policy Abstractions (SUPA)
draft-zhou-supa-framework-02
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Cathy Zhou , Luis M. Contreras , Qiong Sun , Parviz Yegani | ||
| Last updated | 2015-11-09 (Latest revision 2015-05-08) | ||
| Replaces | draft-zhou-supa-architecture | ||
| Replaced by | draft-liu-supa-policy-based-management-framework | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-liu-supa-policy-based-management-framework | |
| 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 services that impose specific demands on a communication network. This document describes the SUPA basic architecture, its elements and interfaces. The main SUPA architecture entities are the Service Management (SM) and the Network Manager/Controller (NM/NC). The SM is a functional entity that creates and runs network services by using a set of NM/NCs. The NM/NC is a functional entity that provides one or more of the following functions: (1) the generation, maintenance and release of network topologies, (2) the generation, maintenance, and release of network service-specific abstractions, (3) the mapping between network service-specific abstractions and the network topology, and (4) the mapping between network service-specific abstractions and network device configuration. Both the SM and the NM/NC may be made up of multiple distinct entities that collectively perform their functions.
Authors
Cathy Zhou
Luis M. Contreras
Qiong Sun
Parviz Yegani
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)