Skip to main content

Requirements for Client-Facing Interface to Security Controller
draft-kumar-i2nsf-client-facing-interface-req-02

Document Type Replaced Internet-Draft (candidate for i2nsf WG)
Authors Rakesh Kumar , Anil Lohiya , Dave Qi , Nabil Bitar , Senad Palislamovic , Liang Xia
Last updated 2016-10-28
Replaces draft-kumar-i2nsf-controller-northbound-framework
Replaced by draft-ietf-i2nsf-client-facing-interface-req
Stream Internet Engineering Task Force (IETF)
Intended RFC status (None)
Formats
Expired & archived
Stream WG state Call For Adoption By WG Issued
Document shepherd (None)
IESG IESG state Replaced by draft-ietf-i2nsf-client-facing-interface-req
Consensus boilerplate Unknown
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 captures the requirements for the client-facing interface to the security controller. The interfaces are based on user constructs understood by a security admin instead of a vendor or a device specific mechanism requiring deep knowledge of individual products and features. This document identifies the requirements needed to enforce the user-construct oriented policies onto network security functions (NSFs) irrespective of how those functions are realized. The function may be physical or virtual in nature and may be implemented in networking or dedicated appliances.

Authors

Rakesh Kumar
Anil Lohiya
Dave Qi
Nabil Bitar
Senad Palislamovic
Liang Xia

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