The Framework of Simplified Use of Policy Abstractions (SUPA)

Document Type Replaced Internet-Draft (individual)
Last updated 2015-11-09 (latest revision 2015-05-08)
Replaces draft-zhou-supa-architecture
Replaced by draft-liu-supa-policy-based-management-framework
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 Replaced by draft-liu-supa-policy-based-management-framework
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


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.


Cathy Zhou (
Luis Contreras (
Qiong Sun (
Parviz Yegani (

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