Simplified Use of Policy Abstractions (SUPA): Configuration and Policy Mapping
draft-pentikousis-supa-mapping-05
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Kostas Pentikousis , Dacheng Zhang | ||
Last updated | 2015-11-12 (Latest revision 2015-05-11) | ||
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
Nowadays, the underlying network infrastructure grows in scale and complexity, which make it challenging for network operators to manage and configure the network. Deploying policy or configuration based on an abstract view of the underlying network is much better than manipulating each individual network element, however, in this case, the policy and configuration cannot be recognized by the network elements. This document describes guidelines for mapping said abstract configuration and policy into device-level configuration and the way in which such models will be processed by software to produce configuration details for actual devices. The Simplified Use of Policy Abstractions (SUPA) framework overview, exemplary mechanism for exchanging service polices among the different elements participating in their deployment and enforcement, and primary procedures of mapping are described. Moreover, an exemplary mapping scenario is provided to illustrate the defined mechanism.
Authors
Kostas Pentikousis
Dacheng Zhang
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)