SFC environment Security requirements
draft-mglt-sfc-security-environment-req-02
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Daniel Migault , Carlos Pignataro , Tirumaleswar Reddy.K , Christopher Inacio | ||
| Last updated | 2017-05-01 (Latest revision 2016-10-28) | ||
| 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
This document provides environment security requirements for the SFC architecture. Environment security requirements are independent of the protocols used for SFC - such as NSH for example. As a result, the requirements provided in this document are intended to provide good security practices so SFC can be securely deployed and operated. These security requirements are designated as environment security requirements as opposed to the protocol security requirements.
Authors
Daniel Migault
Carlos Pignataro
Tirumaleswar Reddy.K
Christopher Inacio
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)