A Model of Security Capabilities for Network Security Functions
draft-baspez-i2nsf-capabilities-00
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Cataldo Basile , Diego Lopez | ||
| Last updated | 2016-07-08 | ||
| Replaces | draft-baspez-baspez-capabilities | ||
| Replaced by | draft-xibassnez-i2nsf-capability | ||
| 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-xibassnez-i2nsf-capability | |
| 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 presents a model of Security Capabilities. Security Capabilities are intended to describe the potentiality that Network Security Functions (NSFs) have for security policy enforcement purposes. Therefore, Security Capabilities are represented as abstract functionalities that a NSF owns in terms of enforcement actions, conditions that can apply in order to determine to which packet or traffic enforce the actions, and other mechanisms that NSF use to determine the actions to enforce. The proposed capability model defines without ambiguities the operations a function can do in term of security policy enforcement.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)