The Architecture for Shared Unified Policy Automation (SUPA)
draft-zhou-supa-architecture-00
Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Cathy Zhou , Tina Tsou (Ting ZOU) , Georgios Karagiannis , Luis M. Contreras , Qiong Sun , Parviz Yegani | ||
Last updated | 2015-02-03 (Latest revision 2014-10-27) | ||
Replaced by | draft-zhou-supa-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-zhou-supa-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. SUPA considers two types of network services, the inter Data Center (DC) communication and Virtual Private Networks (VPN). This document describes the SUPA basic architecture, its elements and interfaces. The main SUPA architecture entities are the Network Service Agent (NSA) and the Application-based Policy Decision (ABPD). NSA is a functional entity that creates and runs network services/ ABPD is a functional entity, which 1) enables the generation, maintenance and release of i) actual/detailed network topologies and ii) VPN and inter DC service specific abstractions and 2) mapping between the VPN and inter DC service service specific abstractions and the network topology and configuration.
Authors
Cathy Zhou
Tina Tsou (Ting ZOU)
Georgios Karagiannis
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.)